Be careful taking it apart.
I recommend removing the disk drive, still on the bracket
first. Then remove the monitor on its sled.
Then it will be easier to get the keyboard out of the way.
It is a lot easier then trying to lower the processor board
from the bottom to remove the battery. The keyboard connection
will pull off and you'll need to disassemble it anyway.
I also recommend disassembling the drive and reinforce the
piece of plastic finger holding the rod that guides the head.
I completely replace these on my drive. When they fail, ( and
they will fail ) you'll be tempted to yank the disk out.
This will destroy the head, making the drive
useless. If the disk gets stuck take the drive apart, remove
the disk and repair the rod mount. It will save the disk drive.
Do note that the cable does not pull off the drive, it is fixed
to the drive. You need to pull the IDC connector from the
With the current firmware, if you need to replace the drive,
you need to find one with the DriveReady signal instead of the
DiskChange signal or at least one that can be jumpered. These drive are
This is a possible reason for changing to 2.40. We have source code for
Another reason is to change a printer driver to work with a printer
you have. With the disk drive problem, you'd need to change the
firmware but it is possible to patch the printer on a disk image
without replacing the firmware.
If you have a Canon printer that matches one of the listed types,
you are fine. The one listed as the "Common" printer is FX80 compatible.
Most all of those are dot matrix printers.
I have made a custom 2.40 with HP pcl5 escape codes. If your printer
needs some other escape codes, you may need to modify the ROM.
it is not that hard to modify the code but recompiling requires
modifications to the machine. You need to increase the RAM
and also add SRAM somehow. IA used a buddy board but I used
some SRAM that I piggy backed on the empty sockets near
the SRAM and Spell checker ROM.
Of course, you can always edit the code and I can compile it for
you, then send it.
If one really wants, one could write a cross compiler and use a
An alternative is to write Forth code to patch the code from the disk
that you load. The code in the machine is designed to allow
patching. I did that initially, before Sandy made the source code
available. You just have to be careful to make
sure you put the compiled code on each disk you intended to print
from. It self installs if you put that disk in.
An alternative is to just export to a PC and print from there.
This can also got to a printer but
some of the formatting may be lost. It does require a serial input
to the printer though. I don't recall if it can send rare text to
the parallel without a patch.
I hope this all makes sense.