4 and 5 are still saying insufficient memory as the inks are being
merged with the bitmaps. I'll do some tinkering with those and see if
I can figure out what the problem is. It may just be a matter of
making the entire drive identical to a working unit as Jason suggested,
which will be very time-consuming, but if that doesn't fix it, nothing
probably will. It's also a dangerous operation without a floppy drive
because I could end up rendering the unit completely unbootable if I
make a slight mistake at a crucial point or if power was interrupted
during the transfer or something. For now I had to load those inks
onto a different unit for merging.
3 loses the time. Yes Jason, that's the one we fixed earlier today.
It's back to "normal." I'll open up the CMOS again and check the
connections. Maybe I didn't push the batteries in well enough, but I
doubt that's it. I'm beginning to think we have gremlins getting into
those. This seems to be a recurring problem on the Toshibas.
Classpad also seems to freak if someone generates an ink file for a
slide that doesn't actually contain anything. I guess maybe they made
a little dot and then erased it. It causes a general protection
fault. I just had to erase one of the ink files to stop that.
That's the unit status for now. They're dropping like flies. Have a
nice weekend!
Dale
dalee@cc.gatech.edu
http://www.cc.gatech.edu/people/home/dalee/