Commodore would never release a laptop, or really much of anything resembling the chunky luggable portable computers of the 1980s. This doesn’t mean a ‘Commodore LCD’ wasn’t designed – it’s sitting in [Bil Herd]’s basement. Of the entire Commodore lineup, the only computer that could remotely be called ‘portable’ is the SX-64, the ‘executive’ version that came with a built-in 5″ monitor, the usual C64 circuitry, one floppy drive, and an empty hole that could obviously hold a second floppy drive. Something must be done about that missing floppy drive, and it only took thirty years for someone to do something about it.
While the conversion requires mucking around in an already tight enclosure, the parts for this conversion are readily available thanks to a few people trying to repair an SX-64, giving up, and parting the whole thing out on eBay. These parts include the 1541 controller relabeled as the ‘FDD’ board in the SX-64, and of course the floppy drive itself. With the right teardown guide, putting the new drive in this old computer isn’t that hard; just remember to cut a jumper to assign the new drive a number other than 8.
The missing floppy drive of the SX-64 is what happens when marketing is put in charge of engineering. There were a few of these dual drive Commodore luggables back in ’83, and we have the computer magazine clippings to prove it. The official story is the power supply wasn’t beefy enough to handle the second drive. This mod, though, seems to work well enough, albeit with a distinct lack of somewhere to store a few floppies.
Find yourself getting sentimental while reading about this great hardware? Keep those feelings going by listening to [Bil] recount some stories from his time at Commodore.
There are a lot of malware programs in the wild today, but luckily we have methods of detecting and removing them. Antivirus is an old standby, and if that fails you can always just reformat the hard drive and wipe it clean. That is unless the malware installs itself in your hard drive firmware. [MalwareTech] has written his own frightening proof of concept malware that does exactly this.
The core firmware rootkit needs to be very small in order to fit in the limited memory space on the hard drive’s memory chips. It’s only a few KB in size, but that doesn’t stop it from packing a punch. The rootkit can intercept any IO to and from the disk or the disk’s firmware. It uses this to its advantage by modifying data being sent back to the host computer. When the computer requests data from a sector on the disk, that data is first loaded into the disk’s cache. The firmware can modify the data sitting in the cache before notifying the host computer that the data is ready. This allows the firmware to trick the host system into executing arbitrary code.
[MalwareTech] uses this ability to load his own custom Windows XP bootkit called TinyXPB. All of this software is small enough to fit on the hard drive’s firmware. This means that traditional antivirus cannot detect its presence. If the owner of the system does get suspicious and completely reformats the hard drive, the malware will remain unharmed. The owner cannot even re-flash the firmware using traditional methods since the rootkit can detect this and save itself. The only way to properly re-flash the firmware would be to use an SPI programmer, which would be too technical for most users.
There are many more features and details to this project. If you are interested in malware, the PDF presentation is certainly worth a read. It goes much more in-depth into how the malware actually works and includes more details about how [MalwareTech] was able to actually reverse engineer the original firmware. If you’re worried about this malicious firmware getting out into the wild, [MalwareTech] assures us that he does not intend to release the actual code to the public.
If you’re building a robot for off-road or rough terrain, chances are you’ve thought about using a tank-tread style drive. There are a ton of kits available with plastic tread and wheels, but they are typically really expensive or pretty flimsy. Instead of going with an off-the-shelf solution, [Paul B] designed a heavy-duty tank tread made with common bike chain and conduit.
Some DIY tread designs we’ve featured just use a single bike chain on either side of the tread pieces. This gets the job done, but each section of tread is usually bolted through the chain. This means that you can’t use a sprocket to drive the chain since all the bolt heads block where the teeth engage. Instead, these designs typically use drive wheels inside the tread, which are prone to slip under a heavy load. [Paul B]’s design is a bit different: it uses a DIY double-wide chain so he can bolt tread segments to the chain and still use a drive sprocket.
Constructing the double-wide chain took quite a bit of work. [Paul B] completely disassembled a couple of bike chains with a delinker tool and then reassembled the chain in a double-wide configuration with M3 bolts instead of the original chain pins. Each section of tread (made out of cut pieces of plastic conduit) bolts on the outside section of chain, and a sprocket runs on the inside. His DIY chain approach saves him money too, since double-wide chains are pretty expensive. Since his sprockets directly engage the drive train, his design should be able to handle as much torque as his drivetrain can put out.
[Gnif] had a recent hard drive failure in his home server. When rebuilding his RAID array, he decided to update to the ZFS file system. While researching ZFS, [Gnif] learned that the file system allows for a small USB cache disk to greatly improve his disk performance. Since USB is rather slow, [Gnif] had an idea to try to use an old i-RAM PCI card instead.
The problem was that he didn’t have any free PCI slots left in his home server. It didn’t take long for [Gnif] to realize that the PCI card was only using the PCI slot for power. All of the data transfer is actually done via a SATA cable. [Gnif] decided that he could likely get by without an actual PCI slot with just a bit of hacking.
[Gnif] desoldered a PCI socket from an old faulty motherboard, losing half of the pins in the process. Luckily, the pins he needed still remained. [Gnif] knew that DDR memory can be very power-hungry. This meant that he couldn’t only solder one wire for each of the 3v, 5v, 12v, and ground pins. He had to connect all of them in order to share the current load. All in all, this ended up being about 20 pins. He later tested the current draw and found it reached as high as 1.2 amps, confirming his earlier decision. Finally, the reset pin needed to be pulled to 3.3V in order to make the disk accessible.
All of the wires from his adapter were run to Molex connectors. This allows [Gnif] to power the device from a computer power supply. All of the connections were covered in hot glue to prevent them from wriggling lose.
There’s a whole lot of interesting mechanics, optics, and electronics inside a Blu-ray drive, and [scanlime] a.k.a. [Micah Scott] thinks those bits can be reused for some interesting project. [Micah] is reverse engineering one of these drives, with the goal of turning it into a source of cheap, open source holograms and laser installations – something these devices were never meant to do. This means reverse engineering the 3 CPUs inside an external Blu-ray drive, making sense of the firmware, and making this drive do whatever [Micah] wants.
When the idea of reverse engineering a Blu-ray drive struck [Micah], she hopped on Amazon and found the most popular drive out there. It turns out, this is an excellent drive to reverse engineer – there are multiple firmware updates for this drive, an excellent source for the raw data that would be required to reverse engineer it.
[Micah]’s first effort to reverse engineer the drive seems a little bit odd; she turned the firmware image into a black and white graphic. Figuring out exactly what’s happening in the firmware with that is a fool’s errand, but by looking at the pure black and pure white parts of the graphic, [Micah] was able guess where the bootloader was, and how the firmware image is segmented. In other parts of the code, [Micah] saw thing vertical lines she recognized as ARM code. In another section, thin horizontal black bands revealed code for an 8051. These lines are only a product of how each architecture accesses code, and really only something [Micah] recognizes from doing this a few times before.
The current state of the project is a backdoor that is able to upload new firmware to the drive. It’s in no way a complete project; only the memory for the ARM processor is running new code, and [Micah] still has no idea what’s going on inside some of the other chips. Still, it’s a start, and the beginning of an open source firmware for a Blu-ray drive.
While [Micah] want’s to use these Blu-ray drives for laser graffiti, there are a number of other slightly more useful reasons for the build. With a DVD drive, you can hold a red blood cell in suspension, or use the laser inside to make graphene. Video below.
Continue reading “Reverse Engineering a Blu-ray Drive for Laser Graffiti”
[Chris] sent us this fantastic tutorial, introducing beginners to H-bridge motor drivers. While many of you will consider this stuff basic, those who are trying to expand from building only things the arduino board can handle to bigger more expansive (and powerful) projects will find this quite helpful. [Chris’s] tutorial is very in depth, not only going through the construction of the basic circuit but also showing you how to make your own PCB. Pop on over there and learn some theory and some practice. Then you can build that battle bot you’ve always been dreaming of!
[Retromaster’s] Ultimate Floppy Emulator is a wicked display of hardware mastery. It is the culmination of several design stages aimed at replacing an Amiga floppy drive with a modern storage solution. You may be thinking that using an SD card in place of a floppy isn’t all that interesting but this hack does much more. The board, controlled by a PIC32, patches into the Amiga keyboard and monitor. This allows you to bring up an overlay menu for controlling the emulator in order to configure which virtual floppy disk is currently ‘in the drive’. He’s even gone so far as to add a piezo speaker to mimic the sounds the original drive head would make while reading a disk.