- Before we begin, I am assuming you have GCC, kernel-devel, if you do not; go to https://wiki.centos.org/HowTos/I_need_the_Kernel_Source to get kernel and the rpm build parts.
- Go to link.sandisk.com, register, and login
- Browse to the software download page, https://link-app.sandisk.com/Home/SoftwareDownload
- Download the “iomemory-vsl4-126.96.36.1997-1.0.src.rpm” source package
- In a terminal, change to the directory you downloaded it to
- Extract the contents of the RPM to disk
- That gives us some metadata and a tar, extract the contents of the tar.gz file
tar xvzf iomemory-vsl4-188.8.131.527.tar.gz
- Change directory to the kernel modules folder
- Using your favorite file editor, edit kblock.c
- Edit line 2592
- Save the file, and quit the text editor
- Compile the kernel module
- If that completes without errors, then install
sudo make modules_install
- Let’s add the module to the running kernel
sudo modprobe iomemory_vsl4
- If you have issues, you may need to do “sudo modprobe -r iomemory_vsl4” to force a reload of the module if one was already present
- You should now have the fio in /dev/, or after installing the utils from the Sandisk site, see the card under “fio-status”
A bit ago I picked up a PDP-8 replica kit, the PiDP-8. A kit can be picked up here http://obsolescence.wixsite.com/obsolescence/pidp-8-get-one . They are under $200, and I always found older computers interesting so I thought I would give it a shot. I also find The Digital Equipment Corporation and interesting tale of a far gone computing era. (There were t-shirts with the DEC logo on Amazon, but they are gone now)
The kit itself is a little smaller than the original control panel; photo from the creators blog above. This is not a real PDP-8, it is a front panel with a Raspberry Pi on the back of it. The Raspberry Pi has an image that is on the user forums (which are incredibly helpful as well as a nice community) which boots very quickly and dives right into the modified emulator. The design is wonderful and just uses the pinout on the Pi.
I got the kit, then ended up moving across the country and did not setup the kit for several months. When I got to building the kit (2015 version, pictured above) it was 2016 and instructions were up for both version. Not many differences except the switches, and how they are mounted. My version needed me to remove pins from each switch then mount each on a rod to keep them aligned. The 2016 version also has more authentic looking switches. I got the switch rod put together with no difficulties.
Then it was down to soldering the trillions, well it felt that way, LEDS to the PCB that came on the kit. Small soldering is not my favorite thing, so this took a bit; but in the end it was done and I was happy with it.
I wanted to test my soldering skills, or lack there of. I plugged the Pi in, and started the image. A few of the lights dimly came up, the rest of them just were dead. Darn this means somewhere it’s broken. I did some traces with a multi-meter, and couldn’t find the fault. Then I realized while it was plugged in the one integrated circuit that handles the LEDs were was getting very hot. I emailed Oscar who made the project and he quickly responded and said it sounded like the integrated circuit was dead and he would mail one the next day or so.
He was extremely helpful and kind, and I got the new chip a few days later. I had to go to Radioshack, (I was surprised I could find one! And its no longer there a few months later) to get a desoldering wick. I haven’t used this before, but it helped me remove the old chip. I soldered the new chip in, and powered it up. Instantly it all came online! I wanted to check all the LEDs, to verify if the OS was keeping some off, or if the circuit was bad, I got a diagnostic program that was written for this system. It did indeed show there was a error, and after resolding a small point then everything was working!
Now that the system works, and I sized it in the box; it was time to paint the switches! I covered half of them with painters tape and painted some brown. Then later did another coat. Then did the white ones so they were not off white or having the red dots on them.
After it dried, I cut a hole in the side of the case so that I could access the USB ports of the Pi. I just had a tiny hobby hack saw and a drill, these were not the best tools to cut the hole but it worked out. I also put electrical tape over the edges of the hole to cover up my handiwork. Then I mounted the PCB with wooden blocks for support into the box. I got some velcro with tape on the back so attach the front panel; that way I can remove it whenever I want for service and easily reattach it.
I got a power switch that is inline with a USB cable. That way I can have a switch to power on and off the device. Then I thought the blinky lights were neat, so I mounted it on my wall for now. It boots directly into OS/8 and in idling does a little light show.
The project came out well, and I am excited for Oscar to release his PDP-11 clone he has been working on in the background. I haven’t spent that much time programming it, but it is nice to have a piece of computer history above my desk. A big part of this project has been the awesome community over at the forum https://groups.google.com/forum/#!forum/pidp-8 and the kindness of the project owner and his willingness to help. Oscar’s blog has some cool stuff as well, http://obsolescenceguaranteed.blogspot.com/ .
Next I want to do an Altair 8080 kit, while I wait for the PDP11 version! https://www.altairduino.com
I recently restored my Compaq Portable II. If you haven’t read Open (Link) about the forming of Compaq I would suggest it, I highly enjoyed it. In doing so I thought I would transfer some files to the 286 via serial, instead of taking the Compact Flash card it ran on out of the adapter, and then copying new software.
I started my journey thinking I would use the old Microsoft Interlnk software that came with MS-DOS 6.22, and then perhaps a virtual machine on laptop to serve the files. The laptop I had on hand was a Macbook Pro, I thought I could do a MS-DOS vm, then hook the USB serial adapter up to the vm allowing MS-DOS to see it as COM1. This turned into a giant headache, VMware and Virtualbox (I tried both) kept giving me errors. They really didn’t like the USB serial adapter (who does), after a few hours of playing with it I made a silly decision of: the easier way would be write a new InterLnk server in Java and let my modern OS talk to DOS directly.
I spent some time configure two Vmware Fusion vms’ to have virtual serial lines go to named pipes. Then I had socat interconnect the two pipes and log the traffic, (I put the command below if anyone is interested). On one hand, I found it interesting researching debugging serial communications using virtual machines. On the other hand, after more time than I care to admit, I didn’t see a clear pattern to the serial data, along with was getting the data going between the systems but not in a super clear format, Wireshark has spoiled me. I finally decided it was time to try another plan. A quick detour to try to decompile the app made me more confused than ever, and we were back searching for a new method of connection.
socat -v -x GOPEN:/Users/Dan/DOS/pipe GOPEN:/Users/Dan/DOS/pipe2
After researching different methods of serial file transfer, such as xmodem, ymodem, and Kermit; I thought I would give Kermit a try. I have used xmodem for dead Cisco devices, and thought Kermit would be easiest to server from my Mac. It allows things like packets in the protocol, which makes it be able to speed up and slow down transfers as the transfer goes on.
To configure the server on the laptop I used Homebrew, installing with:
brew install c-kermit
Then I loaded the app via the Compact Flash card for the Portable. I got Kermit for DOS off of http://www.bttr-software.de/freesoft/comm1.htm . Version 4 for DOS works mostly the same as version 9 from Homebrew. The app lets you change directory to a folder you want to operate out of, set your connection settings, which I have below. Then you hit the command “receive” or just “r” on one side to receive. The other side then pushes whichever file you want.
set port com1 # Or COM2 or whatever the port is
set carrier-watch off # Assume there is no carrier signal
set speed 57600 # Or whatever the speed has to be
set port /dev/tty.usbserial
set carrier-watch off # Assume there is no carrier signal
set speed 57600 # Or whatever the speed has to be
I selected 57600 because I was not sure if the Compaq could handle the next jump to 115200. This page has a lot of info about setting up the program, there are a lot of dials and knobs that can be moved. http://www.columbia.edu/kermit/k95faq.html
You can bring up a serial connection between the two and just type messages, but in the end I remembered how slow serial links were. I ended up powering off the system, pulling the Compact Flash card and then loading most files that way. Sort of felt like cheating, but when transferring the Windows 3.0 install files were going to be a 15 minute plus affair, I want to the good ol’ USB 3.0 Compact Flash Reader.
Someone years ago gave me a Compaq Portable II. I always have loved this machine. Coming from the days of “luggable” computers, it weights over 20 lbs, and has a tiny CRT. The model I have has a “Type 2” (20MB) hard drive, and 640KB of RAM. For a little bit I thought my parents had accidentally thrown it away, as I was storing it at their house. Then it was found again and much rejoicing was had. The system is a Intel 286, with no math co processor.
Recently the one I have has come down with a few problems, so after seeing a brave young soul take their apart (https://www.youtube.com/watch?v=DqaWCobAbQ4) I decided I should give it a go. First the battery on the motherboard started to fail, not only resetting the clock when it lost power, but also forgetting the type of hard drive it had. This made it so every time the system was used, you would boot a 5 1/4″ floppy of MS-DOS, then change floppies to the Compaq Diagnostic disk, and configure the BIOS, and finally go back to the MS-DOS disk. I was lucky that some places still have the disc images online; http://yesterbits.com/2012/09/23/booting-the-compaq-portable-ii/ . I attached those disks to the bottom of this page just so there is another mirror online for others.
I knew that the BIOS battery needed replacement, but when I recently turned the system on the old hard drive had finally given up. At about 30 years old I can not blame it. A fun fact about the drive in this system, it is actually a MiniScribe MFM hard drive (more info here http://www.seasip.info/VintagePC/compaq2.html) that has a MFM->IDE conversion board on it. The drive is also shock mounted, this computer is portable after all! Knowing that, I decided it was time to swap that dead drive for a Compact Flash -> IDE adapter. This would be a size and speed improvement over this old hdd. Luckily someone else had already attempted this! http://tkc8800.com/post/compaq-portable-ii-restoration
Armed with all that info (and the manual – http://www.minuszerodegrees.net/manuals/Compaq%20Portable%20II%20-%20Maintenance%20and%20Service%20Guide.pdf) I took the system apart, and very carefully avoided the high voltage CRT area. After getting the top cover off, then the front bezel; I needed to remove was the floppy and hdd caddy. I removed the cover of the caddy as well as the rear card cover. Then I could get access to the ISA cards. This system has the standard IDE control board, the video board, then a blank, and finally a board called EVEREX with a crazy connector. I have no idea what that last board ever went to. Some quick googling says it may be a tape controller card, or an special external monitor. My plan was to use the third slot to put the Compact Flash adapter, that way I can access it externally. (Here is it being tested)
I got a 8gb card off Amazon because it was fairly inexpensive and that would be so much more than plenty. After looking through all the options the system gave me, I settled on a “Type 41” hard drive even though the system auto detected it as a “Type 14” This gave me around 250MB of storage, for my uses that was plenty.
Now to replace the BIOS battery. The manual covered this. The battery is under the cover, where the extra RAM would be, IF I HAD IT. I took the bottom off, cut the zip tie that held the battery, and replaced it with one off Amazon. That first battery lasted about 25 years before it finally stopped remembering, I think that is a good battery.
One thing that stood out was the battery. I got a battery from the same company as the original, photo above; the battery on the left is the new one, the one on the right is the 30 year old battery. These batteries are 30 years apart, yet they look almost identical. I think that’s hilarious and interesting.
It came time to close up the case, mostly replacing metal covers around the system then placing the cover over it all. I ran into a little problem replacing the ISA card cover, there are little feet that hold the cards in place, but my IDE cable and power cable were in the way. I had to push the cables closer to the ends of the cards to make the cover fit. Then I used plastic twist ties to hold the power cable in place.
Right before sealing it up again, I cleaned the cases because it was already off. Below are some photos of the final system. The next thing I would need to do is replace the keyboard cable, the plastic is chipping off. I did a quick glance at how hard that repair would be, the issue is the cable goes into the monitor compartment (high voltage capacitors are scary) and I will need to solder a new cable to the keyboard/cable which is more than I was looking to do in this first repair session. I also one day should get a ISA RAM expansion card. A giant benefit to having the Compact Flash card slot on the side, is if I want to load more software I can just take the card out and plug it into a modern PC. I also can create a VM and use that card as the hard drive, making for easy dsk file image installation. This is close to infinite times faster than serial connections to transfer files.
This system has a Intel 286 with 640KB of RAM. To run Windows 3.1, you need extended memory; which I currently do not have. If I had a 386, then I could create a page file, and use disk space as memory, but a 286 does not have this ability. To have some version of Windows I installed Windows 3.00a off of https://winworldpc.com/product/windows-3/30, they have a great collection of Windows versions, with different languages and builds. I have a ton of old Windows versions in packaging, but this was simply easier. I also got a MS-DOS 6.22 bootable installation image off of https://www.kirsle.net/blog/entry/ms-dos-and-windows-3-1 and installed that as my base.
All in all, this PC got some much needed attention and is now back to its old self. The Compaq Portable II is back to its old brilliance with Windows 3.0 on its 250MB SDD (technically it is a SSD), 5 1/4″ drive, and tons of games, as it should be.
Random bonus: I enjoy the Compaq Setup Disk load screen, it has a animation with the logo that uses the slow refresh time for an interesting effect. Below is a Imgur upload of it.
- Setup Disk
- Compaq DOS 3.1 Disk 1
- Compaq DOS 3.1 Disk 2
I was very excited to see Susan Kare borrow of of the mini Macs from a friend and give it a shout out on Twitter! These kind words from someone responsible for a lot of the original Macintosh design are quite humbling. 🙂
In building the project I wanted the computer to have the closest to the original feel as I could get. There were a few difficulties in the project, from the TFT screen, to the OS configuration. Yet in the end, I got a cute little replica running on top of a Raspberry Pi. I am not trying to break copyright, or profit from this. I simply do it as a fan of good hardware and past operating systems.
To start I want to mention that there are areas of this “guide” where I have been short, if you are unfamiliar with Linux, some of the parts in this config may give you problems. This project includes compiling code, adding scripts to boot, and configuring systems like VNC.
I loaded the standard Debian install onto a SD card to start (which at the time was Debian 6 or 7), then I started investigating the different original Motorola Mac emulators. The two main ones I found were Basilisk II and Mini vMac. Basilisk offers features such as Color, networking, and advanced features over Mini vMac. A very useful feature that Basilisk has is supporting a shared drive. You can tell the emulator that a folder on your Pi or any PC should show up as a hard drive in Mac OS 7. That way you can easily download games/software from archive.org or other locations, then load it onto the virtual system!
Mini vMac did offer greater compatibility for apps, while only being black and white, it seems to do a much deeper level of emulation; this makes it slower, but some apps that wont work on Basilisk will work on it. My solution in the end was to put both of the emulators on the box, pointing to the same virtual hard drive.
A script wraps the system, by default it auto boots into Basilisk, but if you “shutdown” the Mac in the emulator, you get a options screen that will allow you to switch modes the emulator is running in, the emulator itself, or some other settings. Some of the other settings including pairing Bluetooth, shutting down, or dropping to the console.
These files are available under https://github.com/daberkow/minimacparts. There is a SYSINIT script that starts the script, aka the wrapper, and gets the session started under the “pi” user, this goes in the /etc/init.d folder. Then there are folders for the different emulators in the /opt/mac folder.
Note: I used the current Raspberry Pi Debian build when I did this project, which at the time was using SYSINIT over the newer SystemD. If you want to use a newer build (which you probably should) you will have to translate my crummy SYSINIT script into a SystemD script. Feel free to pull request the repo! 🙂
One of the larger issues that had to be overcome was screen scaling. The screen I used is 480×320, but the original Macintosh resolution was 512 × 342. This had some of the emulators either cut off, or scrolling around the screen when the mouse got to a corner, which was not great. I could run the emulators at a smaller resolution, but some software was designed with that screen in mind and applications were cut off!
My solution was to use VNC, the system starts the emulator in a VNC session running at the native resolution, then the Pi screen connects to that session and enables scaling mode, shrinking it to the proper size. This way VNC worries about all the scaling, at a minor speed loss. I looked at different X configs to try to do the scaling that way, but the way this screen works, it gets upset and has problems very easily. The screen does not have a scaler of any sort, so you HAVE to send that resolution of 480×320 to it. The VNC solution works well. The different emulators have VNC config files that are copied to the running config right before its run depending on the emulators properties.
At this point we should discuss dependencies; TightVNC server was used for VNC. A quick minor note about VNC, you need to config the VNC users password, and then setup the script to auto-login with that password for the above script to work. Bluez Bluetooth stack and utils were used to be able so use Bluetooth peripherals. Basilisk and Mini vMac were compiled from source on the Pi 2 so that I could squeeze the most performance out of the little PC. Also its hard to find the latest versions ARM compiled online.
Basilisk has a good make file that you can use on the Pi as long as you have standard development environment setup, https://github.com/cebix/macemu/tree/master/BasiliskII.
The authors website offers a nice little service to have the website compile to code for you, or you can compile it yourself. Depending on your screen and how you want the app to start (a lot of those settings are hard coded in at compile time) http://www.gryphel.com/c/var/index.html.
I made one virtual hard drive, that both emulators used. Luckily they use a compatible hard drive image format. I set the first image up on my desktop just because it was easier. Then copied it over once I got the image in a good state. For years Apple gave out for free on their website Mac OS 7.5.3, then after a website update it seem to break a lot of the links. A few still worked but most over the years have stopped working. A lot of different sites have mirrors of those disks available though, if you search “System_7.5.3_01of19.smi.bin”, that should bring you to one of the mirrors. The one other thing you need is a ROM for a original Macintosh. I have some classic Macs at home, and you can dump the ROM from those. Or there are sites out there that have them hosted, I would guess that would not be to hard to find.
I put the virtual hard drive, and the ROM in a folder called “Shared” in the /opt/mac directory. You may have to tweak some of the configs/scripts to get everything working your way.
Once you get it working, there are a ton of games and pieces of software on archive.org for the old Macintosh, just make sure you get the 680*0 versions not the PowerPC versions. There are also a ton of abandonware sites, since half the companies that made this software are out of business, I doubt they will mind you taking a look, though legally its a grey area.
Those are the basics for how I got the system setup. One item that gave me a bunch of problems was the TFT screen. At the time you needed to load separate kernel modules and configure boot parameters for it. I think newer kernel images have added this, so that should be a simpler task for everyone.
HipChat 4 has recently come out, and then shortly after it was released to my companies internal HipChat server. Being a Linux user I hoped that the aged HipChat 2 client was finally updated for Fedora or Red Hat or CentOS 7 so I could just use yum to install it. When I went to the download page the old yum instructions were replaced by only Ubuntu/Debian instructions! After playing around with the Debian package and getting it to load, I thought I would look at the repo a little more. Low and behold, Atlassian is making a yum repo! Just not publishing instructions on how to use it! The downside is they seem to not be signing the repo, but the code below works with yum to download the latest version.
sudo bash -c ‘cat > /etc/yum.repos.d/hipchat.repo << EOF_hipchat
sudo yum update
sudo yum install hipchat4