I recently acquired a shiny Model 100 portable with necessary accessory. I played a bit with the machine before cleaning it and I was a bit surprised that it could retain data in the RAM disk for minutes after disconnecting the power. That gave me the impression that there was a backup battery inside, which scared me enough to open the machine immediately… and yes, although the battery still provided some voltage, it started destroying itself and the computer. I removed the residue from both the backup battery and the battery compartment for AA cells and cleaned the rest of the machine. It looks almost like new now.
I have to say that I am very impressed with the Model 100. The user experience is closer to professional computers of that time than home 8-bit machines. The programs in ROM can read/write the same files, switching between them is fast and there is even a shared clipboard. I particularly like the built-in terminal emulator with handy access to download/upload features and easy configuration. This was a true mobile companion for those working on the road and accessing the company minicomputer over modem.
My version does not have the modem, but at least the null-modem communication works flawlessly. I think I should install an old UNIX somewhere and try accessing it like in the old days. Somebody even created a Model 100 termcap definition file, so it is possible to use control functions of its terminal emulator in UNIX.
A guy contacted me that he found a complete TRS-80 Model 100 at the recycling center, ready to be destroyed. He was not a vintage computer collector but realized that it could have value for some, so he started to google somebody who can appreciate it and found my Czech blog. He wrote me a message that I could take it for free if I was interested.
… and I indeed was. This particular machine travelled to our country during the socialism era and it is quite rare here. I love portable computers of all kinds, so I am very curious to see whether this 1983 ultra-mobile machine was just a useless toy or a valuable companion on the road. The next step is to clean everything. The original suitcase started to disintegrate, and everything is covered with the black filth.
TIGA is a strange beast. Texas Instrument’s TMS34020 (introduced in 1990) was the holy grail of 2D graphics acceleration for a certain period in the world of PCs. This chip is fully programable general purpose processor, so you can offload even non-graphics tasks to it (my low-cost SPEA Graphiti HiLite 1024 has 1MB of program/data memory in addition to 1MB of framebuffer memory). If you add a floating-point coprocessor (like Intel i860 or TMS34082), you can create a 3D accelerator that processes both rasterization and geometry processing.
On the other side, fixed-function graphics cards soon became cheaper and faster, which took the mass-market appeal away from TIGA. There were also multiple reasons, why TIGA was not a user-friendly standard. Unlike CGA, EGA and VGA, TIGA has a vendor specific part of the graphics driver. That means that you cannot just put a TIGA card in your computer and hope that programs or operating systems listing TIGA among supported graphics standards will work. That’s the reason why most TIGA collectors not even try if their cards are in a working condition.
This SPEA card (like many other TIGAs) is supported in DOS and Windows 3.x only. You need to configure the card (the configuration is stored in its EEPROM), initialize it during every boot using a vendor specific driver and load a generic TIGA library. Once all the steps are done, you can run any TIGA-enabled program.
This approach means that there cannot be any generic TIGA driver for UNIX, Linux, Windows NT and other operating systems that cannot work with drivers loaded from DOS. Windows 3.x has a generic TIGA driver and one can be installed also in Windows 95, but that’s all.
SPEA didn’t bank on the generic TIGA support in programs. They provided “direct” drivers for multiple DOS CAD programs (including AutoCAD) and Windows 3.1. These drivers work only on compatible SPEA cards and bypass all TIGA libraries. SPEA made them more performance optimized for CAD work. The Windows driver also offers an easy way to change resolution and color depth. Only 256-color (8-bit) and true color (32-bit) modes are supported, so my entry-level board with just 1MB of framebuffer memory can show millions of colors in resolutions no higher than 640×400.
(The first photo shows the SPEA card compared to a standard “dumb” ISA SVGA card. This SVGA card is one of the best choices from the early 90s thanks to its fast Tseng ET4000AX chip and 1MB of 32-bit video memory.)
Although mounting remote HDDs over a serial cable to my Olivetti Quaderno was a nice solution, it was not very fast. I wanted to add persistent storage using a PCMCIA card, but Quaderno has just PCMCIA 1.0. I used to work a lot with PCMCIA, but it was always the newer standard (2.0) typical for 386/486 laptops. PCMCIA 1.0 does not support IO devices (so no ethernet cards) or CompactFlash cards (as they are IO cards in the ATA mode). PCMCIA 1.0 can work only with linear memory mapped cards. For linear flash cards, there were two incompatible standards (FTL and MS FFS). SRAM cards had just a single standard. In addition to all of this, simpler devices (industrial, embedded) required attribute memory on the card in order to work at all (fortunately, this laptop supports full Card Services and does not need it).
I took a 4MB PCMCIA SRAM expansion from my Amiga 600 and put it in Quaderno. The ROMDOS drive contains a Microsoft program called MEMCARD.exe (very similar to FDISK.exe, but for early PCMCIA cards), so I used it to format the card, rebooted the machine and got 4MB of persistent storage (the SRAM card has a battery to retain the data even after removing the card from the computer).
These early PCMCIA cards don’t work in Windows out of the box. However, there is already a DOS driver included in Windows 9x. You just need to add two lines in the config.sys and you can use the SRAM card in a “more modern vintage computer” (it still allows you to use the slot with other cards and use hot-plug features). Btw these direct mapped SRAM cards have one big advantage – they are super-fast.
I know it’s almost 30 years late, but I finally understood, how these old PCMCIA devices work…
You might think that the machine is useless without a working HDD and no floppy drive, but that is not true. Quaderno has a small bootable “ROMDOS” drive with basic system files, COMMAND.COM, a RAMDISK driver (up to 320KB of EMS memory can be used and you still have full 640KB of conventional memory) and Interlink software. This drive is interesting, because it acts like a read-write one. You can edit config.sys and autoexec.bat (the changes are there even after shutdown, if the CMOS battery is ok or AC is connected). You can even copy files there, but if it’s more than a few KB, the system will crash hard (requiring you to reinitialize the ROMDOS).
With Interlink, you can mount remote HDDs over a serial port. I used it to run VC (Volkov Commander) to edit the config.sys (no EDIT.COM in ROMDOS) and enable the RAMDISK driver. After this, I had my small but fast local storage (non-persistent) and everything bigger was started directly out of the remote HDD from another computer. This is a good way to test the computer before fixing the HDD or installing a flash/SRAM card in PCMCIA 1.0.
This little machine is an XT-class computer with 16MHz NEC V30HL, 1MB of RAM, double-CGA 640×400 graphics (AT&T6300/Toshiba compatible), MS-DOS in ROM and a 20MB Conner HDD (working in 8-bit mode). Its size and weight are halfway between regular laptops and handhelds (it is ultra-portable even by today’s standards). I got one three years ago and it was dead like almost all of them nowadays. The issue was “easily” fixable by replacing all the SMD capacitors. We replaced the ones on the logic board and the computer booted. However, the screen was not able to retain the contrast value, which made it hardly usable. Also the Conner drive had the head stuck (a common issue, that I want to fix later). We disassembled the lid and replaced a capacitor on the display board. Everything worked flawlessly when disassembled. As soon as we assembled the machine together, it stopped working. We were tired and put the whole thing into storage.
Recently, after three years, we gave the machine another chance. Disassembled it, booted and everything worked ok (except the HDD of course). After assembling it back? No sign of life… The issue was caused by too long legs on the new capacitor in the display board. The legs were sharp and went through the insulation layer on the (metalized) screen cover and shorted the capacitor (I know, shame on us…). Once we fixed this, we were able to put the machine back together and enjoy it. David also replaced cracked internal plastic parts using a 3D printer.
Now we have a trouble-free machine in a perfect shape with just one flaw – a faulty hard drive (and no floppy drive). However, that is not as big issue as one might think…
I was silent for a while as some things required my attention more than old computers. We extended the list of implementations of our Sieve Benchmark and it now supports even 6502. It was developed on Atari 800XL without any modern hardware or software (it’s written in ATMAS II macro-assembler). And it was a pain.
We all remember the lovely days of being young and playing with these simple computers, where programming was often the best way to spend time. These nostalgic memories don’t say the truth how horribly inefficient the development was on these machines in comparison with what came a decade later. David told me that his productivity was about 20 times lower in comparison with developing an assembly program of similar complexity and size on PC. These were one of the biggest reasons for your entertainment:
It was easy to fill whole available memory with the source code text. There was a situation when only 100 characters could be added to the text buffer, but about 2000 were needed. That caused that multiple parts were optimized for source code length (except, of course, the sieve routine itself, which was optimized for speed).
At the end, it was necessary to split the source code into two parts anyway.
Unlike with PCs, the Atari keyboard doesn’t support roll-over on standard keys. It is necessary to release the key before pressing another one (otherwise the key-press is not properly recognized).
Having a disk drive was a big advantage over tapes. However, the implementation on Atari was very slow and everything took incredible amount of time. Boot into editor? 20 seconds. Loading the first part of the source code? 5 seconds. Loading the second part? 30 seconds. Storing it back? 60 seconds (for just 17 KB). You needed about 160 seconds before trying to run the program after every larger change (including 20 seconds for compiling). Often a minute more if the program crashed the whole computer.
Although David never started to use “modern” features like syntax highlighting and code completion and he still programs mostly in the 80×25 text-mode, he said that this was too much for him so I don’t think we will repeat this again soon.
Regarding the results: A 1.77-MHz MOS 6502 in Atari 800XL/XE (PAL) required about 66 CPU cycles to go through a single inner-loop step. If graphics output was disabled during the test, this decreased to just 49 CPU cycles. A 4.77-MHz Intel 8088 needed about 73 CPU cycles to do the same. Thus, 6502 is faster if running on the same clock.
On the other side, the original IBM PC is clocked 2.7x higher than the Atari and 4.7x higher than other important 6502 machines (Apple IIe, Commodore 64). Thus, IBM PC was at least twice as fast in this type of tasks (similar to compiling, XML parsing…). I’m not surprised, but it is nice to see the numbers.
Interestingly, the heavily optimized assembly code running on Atari provides the same performance as compiled BASIC (MS QuickBasic 4.5) running on 20MHz 386DX (interpreted version would be three times slower). This was one of the fastest BASICs out there so it gives you good perspective on how these high-level languages killed the performance back then. David spent a lot of time optimizing the code for both CPUs and used the available tricks for each architecture (like self-modifying code…). If you feel that your favorite CPU should have been faster, you can download the project folder and check the source code. If you create a faster version, please send it to me (but please read the README first, especially the part called “Allowed tricks”).
Also if somebody is able to port the code to Commodore 64, it would be nice to compare the results with Atari (only the disk access, timer and console input/output need to be rewritten). Any expert/volunteer?
Working with old Amiga computers with their original color monitors is always a painful experience. Especially here in Europe where these screens run at 50Hz. Fortunately, my Amiga 2000 is equipped with a Multivision 2000 scan-doubler card that not only doubles H-sync from 15.75kHz to 31.5kHz (to make the output compatible with VGA monitors) but it also allows a user to increase refresh rates up to 100Hz.
I wanted to show this computer on Bytefest (a vintage computer show) and I decided to show it with a CRT (LCDs always ruin the experience). That created an ideal situation to check how this “software controllable refresh rates” feature works. The manufacturer of the card (3-State) bundled a diskette with a simple program that allows you to find the optimum refresh rate using multiple sliders and the way it works is compatible even with old simple VGA screens from the early 1990s.
The picture frequency is increased when a user decreases the number of video lines. Speed of drawing of each line is still the same. The computer just generates fewer lines, which means that a single frame takes less time and the next one can start sooner.
I switched Workbench into the interlaced mode (512 lines instead of 256) and then used the bundled Sync Master tool to decrease the number of lines close to the original non-interlaced resolution. As a result, I got nice and steady 80Hz on a standard VGA screen, which allowed me to work with the computer for hours without eye strain. This is a perfect setup for office/productivity work. However, be prepared that this tool doesn’t work well with applications that open their own screens a display outside Workbench (you need to revert it to default before starting such application).
Digital (DEC) always made interesting computers and their PC laptops were no exception. DECpc 325SLC was a laptop with the first generation of color passive-matrix displays. The picture quality (aside the ability to display colors) was on par with monochrome passive-matrix screens with all the drawbacks they had. On the other side, the computer was equipped with a 25-MHz Intel 386SL and SVGA graphics for just $2.100 – the price where other laptops from most other brands have just monochrome screens and VGA graphics.
The 386SL is the first CPU specifically designed by Intel for use in laptops. It integrates almost a whole PC into two chips, with the main chip containing (among other things) a 386SX core (with 16-bit data bus) and 64kB of cache (16-bit as well). Intel built the platform to support then new power management functions like the sleep mode (“suspend to RAM”). The performance of this CPU is halfway between 386SX and 386DX.
Graphics chip was not integrated in the two Intel chips. Digital decided to use a chip from Western Digital with 512kB of video memory and the support for 256 colors with a resolution up to 800×600. The chip was attached using the ISA bus and had no acceleration. On the other side, the support for VESA VBE 1.2 and ~3MB/s throughput to video memory made it a good mainstream solution among ISA based cards of the time.
There was also a detachable trackball module available for the computer. It’s not hot-plug and you need to reboot the system, but it works surprisingly well even after decades. Note the mouse icons on the arrow keys and Z/X – these are for the mouse emulation. The laptop with no trackball or mouse attached transparently emulates PS/2 mouse on these keys and the result is way more usable than the Windows feature called “MouseKeys”.
It took me two years to find some time to disassemble the machine and then another year to start fixing it. Repairing the PSU with the blown EMI suppression capacitor was an easy task and that’s what we started with. Worse part was the instability – machine often crashed to a guru meditation error during certain tasks and sometimes a restart resulted in a “color screen” error.
David created and programmed a small device with eight differential inputs for voltage measurement (and logging) so we could check if the electrolytic capacitors did their job properly. To our surprise, they were fine. We also tried different programs to test memory and other hardware but the computer successfully passed all the tests.
Based on the Guru error codes, we found the root cause in the faulty EPROM chip (Kickstart 3.1). It started to lose data and reading of certain regions of the chip was sometimes affected. Thus, CPU executed faulty code (like a word or long word access on an odd address boundary).
The system is now running with Kickstart 1.3 and Workbench 1.3 and all original upgrades are inside except one. The Commodore A2630 accelerator card (25MHz 68030+98882, 2MB 32-bit RAM) crashes with dark blue and green screens and I’m afraid that there is a mechanical issue.
Next steps: Fix A2630 and reprogram the EPROM chip.