wierd_w
-
Content Count
1,622 -
Joined
-
Last visited
Posts posted by wierd_w
-
-
Probably, but they will want the door.
-
1
-
-
my aquarium gifted me with some tasty mushrooms today.
-
1
-
-
I am going to spend the next few days sanding on this thing, and getting it all pretty.
There are some pretty significant X and Y positioning issues with my printer; I expect it is because it is a cheap chinese knockoff. That's OK, this is intended to be a part proving exercise. I am pretty satisfied with the models. The lettering just needs to be a little deeper now, and I should be able to release.
Still a LOT of sanding left to do; Been hitting this real hard with 80 grit to get the layer artifacts off.
-
2
-
-
The mixture of toner powder and UV resin appears to work but the text needs to be cut deeper.
Currently the letter groove depth is insufficient, as it is starting to sand through as I sand the surface smooth. I will revise to make the lettering depth deeper for this purpose.
-
5
-
-
Has more detailed info about Broadcom's 43xx chips, and how they work.
https://blog.quarkslab.com/reverse-engineering-broadcom-wireless-chipsets.html
-
1
-
-
The driver I posted supports the broadcom 43xx series, and is generic. It should work with PCMCIA devices, mini-pci devices, etc. As long as it is broadcom 43xx chipset based. (you can force the driver. It should work.)
I know that driver does do WPA2.
(Here's the deal with broadcom chips at least-- They contain a small bit of RAM inside them, that a binary blob from the driver gets loaded into. This allows the chip to be silently "Updated" along with the driver. This blob controls the radio, and all that stuff. The driver is really what determines a lot of function for broadcom chips. They are very common, so this is why not all drivers were created equal. It is also why on Linux, you have to use a "non-free firmware" ripped out of a windows driver, using a package called B43FW_Cutter. Without that binary blob, the card cannot work, and it is closed source.)
-
1
-
-
(there's a LOT of those on ebay right now...)
Theres a couple of these too.
(You can look up what chipset is inside one of the offers that strike your fancy on this site)
Be sure to pay attention to the version number, especially with those linksys offers. Look them up each time. the BCM43xx driver I posted should work with anything in the broadcom family that starts with 43. Such as the 4313 or the 4306. The chip in my lifebook is a 4335.
-
Glad it helped some-- It is not a magic bullet. (and it has a LOT of knobs)
-
2
-
-
Compatibility toolkit?
https://application-compatibility-toolkit.software.informer.com/5.6/
It's basically the "Compatibility mode" in win7 and up, on steroids.
https://docs.microsoft.com/en-us/windows/deployment/planning/act-technical-reference
-
If the issue is "File handler already in use" type errors, perhaps consider either softlinked or hardlinked files, presented in different folders?
(Logically, appears as 2 different files. Really, is the same file, with two NTFS indexes.)
That way the programs each think they are running independent instances from separate folders, but really the data files are the same ones.
https://www.maketecheasier.com/create-symbolic-links-windows10/
-
That's the same material as the base I printed (the large wast swatch that is)-- just with the flash turned on with the camera. My upstairs is kinda low-light.
The top is approaching the end of the print cycle-- at 98%. I have mixed some black toner powder with some UV reactive resin, and will fill the lettering in with it before sanding. That should give nice bold black letters.
Since the top portion is many solid layers, it will take some time to finish this last 2%. I will also have to sit the resin painted text in the sun for several hours (since it has decided to be overcast today) to cure. (I have misplaced my UV lamp)
The above comparison was to illustrate the contrast between the "wood" and the "Desert Tan"
-
Then all it needs, is some kind of abstracted display generator, and you have the full planned peripheral package.
Depending on the bandwidth, I would think something like X protocol would work.
-
I figured as much, as I also went down this rabbit hole. I had success with the BCM43xx chipset, which is very common.
As the initial post I made, linking to the MSDN forums, makes clear-- there are several "known to work" chipsets and drivers. You may avail yourself of any of them. BCM43xx is just VERY VERY common.-
1
-
-
For any board makers that would like to make this happen--- Here are the schematics he found and posted in Classic Computing.
I found images of what the original cards look like but it did not have traces for the backs. However, I was able to lift the RAM chip numbers, and grab a datasheet.
https://datasheetspdf.com/datasheet/TC5047AP-1.html
Armed with that, and if he offers money for the parts and work, it should be possible to manufacture what he needs, since I very much doubt he will find one of these in the wild.
-
1
-
-
The "wood" filament arrived. Investigating the roll, I was correct- it is wood COLORED filament, not "wood mixture" filament. Color wise, it is "Dark tan". I will clip a section and lay it on a bit of waste material made from the "Desert Tan", and some white paper. Give me a minute.
I find the color to be relatively complimentary, and fairly close to the "dark" accent color of the beige units.
Should I print another bottom from the "wood" color for the final product?
-
1
-
-
I am pretty sure he wants the "untethered" portable experience.
That said, here is my local downloaded copy of the Odyssey installer, and the BCM43xx (for win9x) driver I used.
(Note for providence: Odyssey client IS BUYWARE. The installer includes a temporary license for evaluation. Juniper Networks no longer has this old product on their download site, as it is a legacy product. This is why I put a link to this trial version download here.)
-
1
-
-
I would think you might be better sharing the wiring diagram schematics you found for the module, and asking one of the local builders to make you one. Getting a genuine article might prove... Next to impossible. There are many talented people here who could build the module for you with the schematics you found. Wave some dollars under them, and it might well happen.
-
Connect to the second tipi using SSH (via something like PuTTY), and do the rename that way. Connect direct to its IP address.
-
1
-
-
drivers being available for 9x is the kicker.
-
Be more specific.
The first one, will take any PS/2 keyboard or mouse, and present it to the computer as a generic HID compliant device.
The second one is not worth your time or money. There was once a time, back in the days of yore, when early USB mice could also be driven by PS/2 signals, and that is all that converter does. It does not do anything special, it just hooks the data pins of the USB device to the signal lines of the PS/2 connector, and hopes for the best. A bluetooth device that expects a full and proper USB stack is not going to work.
So, for a "Fits most cases" answer, I will say "no."
-
The Odyssey client is a little odd in how it works, and acts like it was really intended for use inside a large organization with some special servers running, but it still totally works as a generic AP management portal. It's just a bit cumbersome and obtuse.
The main claim to fame is that it can handle WPA2, *AND* is universal.
I have an old Fujitsu Lifebook e1000 (that was given to me for free!) that has a baked in BCM43xx wifi chip, which is why I have already been down this road. Sadly, said lifebook as an AC'97 based audio chip, so it's no good for retro dos gaming.
I have it running XUbuntu at the moment, since win9x proved to be... Problematic.
-
Enabling SMB1.0 also re-enables many exploitable holes in your network. SMB1.0 was developed before the (commercial) internet was a thing, and is a relic of the past, from a bygone era when people on the internet mostly knew how to behave themselves. You know, BEFORE the eternal september.
The real reason why you need to enable it for samba to work like that, is that MS changed how they do network announcing. It used to be that the master browser would accept messages from all hosts on the network, because they would do a broadcast advertising their shares, and then name resolution would be accomplished with WINS. However, SMB2.0 and newer uses a protocol much closer to apple's Bonjour protocol. SAMBA on Linux has not yet adopted this new announce method, but fully supports SMB2.0 and SMB3.0 core protocol. Since the only thing you get out of enabling SMB1.0 is being able to use the hostname to find the share, the enabling of the feature is not really worth the greatly increased risk. Just reserve an IP address for your Pi at your router, and have it be assigned a static IP address, then access the share via that IP address.
Example:
\\192.168.0.128\TipiThen you can live without the added security risks.
-
You will need a card that has win95 drivers, AAAND you will need a wifi client to broker connecting to access points.
Odyssey Client is buyware, but works. I have done it successfully with a broadcom based BCM43xx wifi card.
(After work, I will dig for the SPECIFIC win9x driver I used, since not all were created equal. It should still be on my NAS.)
-
1
-
-
Yeah, but then you have to hope that the UPS can send some kind of signal the Pi can recognize, so that it can gracefully shut down.
This is a BBS, after all. Leaving it unattended is kinda the use case. It needs to react to having the power go out, but do so in a safe and consistent manner. The various UPS pi hats out there can send a useful signal over one of the GPIO pins to the Pi to alert it that it has started using battery, and is supplying power. This can trigger a graceful shutdown script.
That one was just very well made; there are some that run on just some AA batteries! Any that supply a suitable "Now using batteries!" message would work.
Like us on Facebook
Follow us on Twitter
AtariAge on Instagram
Watch us on YouTube
Chat on Discord
OT: Dumping Thread
in TI-99/4A Computers
Posted · Edited by wierd_w
Fried is the best way i have eaten them so far.