If NO IMAGES will be shown, use www.z80.eu/blog instead of blog.z80.eu

Please note also - THIS BLOG ENDS HERE WITH THE LAST ENTRY FROM NOVEMBER 9th 2021.

I have prepared a new blog with wordpress at https://vintagecomputing.info !!!

Thank you.

Looking at the wonderful bootscreen of a DEC PWS 433 during BIOS boot phase, I had the idea to preserve this image. Looking around for the image file, I wasn't successful.
So I made a picture with my Nikon and cropped & scaled for Win7 Boot Updater, see
http://www.coderforlife.com/projects/win7boot/
Download the program (no installation required), and choose "complete" for the background picture:

You do not have to choose other options (let the animated windows logo as is).
And here's the background image file itself you have to choose:


Happy DEC PWS booting...

After my short intermezzo with a Mac SE/30, I tried my luck with a Macintosh Colour Classic.
This machine, untruly called the ugly duck of all all-in-one Macs, has a real cute Trinitron color display CRT, and in contrast to a Macintosh Plus or a Macintosh SE, has also a LC PDS slot for some real interesting expansion cards. Btw - it was also the first Mac with a build-in microphone.
You need an external Apple CD-ROM drive for easy MacOS installation also.


At the moment only 8MB of RAM are recognized, but for MacOS 7.5.5, this is enough for work. I am still trying to get 10MB (this is unfortunately already the limit).
For more infos about RAM compatibility, take a look at http://www.jagshouse.com/ram_guide.html

I was also thinking about installing MacOS 7.1.1, but too many convinient features are missing in MacOS 7.1.1, and some programs require at least MacOS 7.5 ...

Meanwhile I got the Apple IIe card also. I am very curious about the results working with this card, which can fully emulate an Apple IIe without any compatibility issues.

To work with a 5.25" floppy drive, I have to solder my own drive cable adapter with a rare 26pin D-SUB connector, but this should be manageable.

For more infos about this card, visit http://www.vintagemacworld.com/lc_card_faq.html
or better http://www.vectronicsappleworld.com/app ... ecard.html ...

I will post my results with this card asap also in this blog, be patient.

I've needed to test floppy disk tools with my modern i7 equipped PC.
Unfortunately I have no real floppy drive built in.
So I "googled" for it, and I found one, which runs supposedly smooth with Windows 7 64bit.
http://www.ltr-data.se/opencode.html/#ImDisk
But the software "imdisk" is faulty. I've tested it by using/mounting an image file, created by winimage
( http://www.winimage.com ).
Try to install an 1.2MB or even a 360KB disk drive, go into command line, and try to format this new virtual drive with "FORMAT A: /T:80 /N:15" or "FORMAT A: /T:40 /N:9".
The result ? Always missing bytes, proof it with CHKDSK, e.g. formatting a 1.2MB disk results in 1.1MB total capacity.


So I restarted my search and found "vfd" at sourceforge: http://sourceforge.net/projects/vfd/
But this project is not supported anymore, if using 64bit Vista or Windows 7, you will fail to install the driver, even with "Administrator" rights.
This did the trick:
I've downloaded vfd_x64.zip from http://levicki.net/downloads/
I've looked for dsao13b.exe / dsao13b.zip - a tool for driver developer.
I started dsao13b, selected "Test Mode" (which allows to run non microsoft signed drivers), signed vfd.sys, and then started vfdwin with Administrator rights. That worked, I was able to format a virtual 1.2MB floppy disk running Windows 7 command line, see screenshot.

It works, but what an ugly way to manage it...

P.S.: You should change it back disallowing unsigned drivers to be working, if you do not need to use that driver. Otherwise you opened a new possible door for malware.

P.P.S.: Meanwhile I guess what's wrong with imdisk. Regardless of what I am selecting in imdisk.cpl, I got a "Partition" with a "start offset", not a "Floppy". Usually this happens only for a harddisk. See also this comparison:

I realized that I didn't made anything meaningful with my Apple ][ Europlus, so I decided to exchange it for another vintage computer - an older Macintosh.
My first choice was a Mac SE/30, because this one can handle up to 128MB RAM, and it's capable to run A/UX. But....

A serious flaw of this model (SE/30) is an unreliable firmware ROM module/SIMM.
You can be lucky if you got a moment of a stable working condition, see here:

Unfortunately getting access to the logic board is not too easy. Opening the case would be very easy - except these two upper deep counter-sunk TORX screws:


This is a schematic picture of the place where you can find that ROM SIMM:

But to get the logic board in your hands, you had to follow a strange method of releasing the board itself from the frame. First you have to draw it a bit, but then you have to lift it on one side, to pull it in all - but SCSI, loudspeaker and floppy drive cable are still connected and will keep it in place. Very ugly.


After discovering that no sound is made from this macintosh, and because the ROM module makes often trouble, I decided to bring it back and take a Colour Macintosh (will be described in next blog entry).


Btw.: A good article about repairing a Mac SE/30 can be found at www.biwa.ne.jp

That was really tricky.
I buyed an old but autonomous working Eprom Burner, a Needham's SA-20 (Wilke Technology), and I hoped to work with it connected to my modern PC (which has a COM1 interface).
Unfortunately only a DOS program exists so far for it (but there is hope, source code of that DOS program is included). So I decided to give it a chance by using VMWare Player with installed Windows 98 SE. I tried also pure DOS mode. But it worked only partly and slow.
It seemed my key strokes were eaten somewhere, or another reason exists for a painful slow remote PC control via serial interface (115K baud,N,8,1 - that's fast enough usually).
Trying to use it with a Intel 486 driven Siemens Notebook and DOS from Windows 95B worked like a charm. But look at this beauty. It can copy 8 EPROMs at once !

If someone has an explanation for that strange serial interface behaviour, I would really please you to share your knowledge. Serial port setup in VMWare used "host device" mode.

I found also a very helpful site describing made expirience with a parallel port connection, so I tried only using it via serial interface.

See related link below for that article...