stone@calgary.UUCP (Glen Stone) (01/09/86)
I did the 1meg upgrade, and so far everything is working fine. I have not installed the TOS ROMs. I used the method that involved adding 6 68 ohm resistors. A side note: with the additional memory I have made extensive use of the RAM DISK ( from Michitron ) and have encountered something I can not explain. After some random amount of compiling, editing, and copying of files to the RAM DISK something happens in which I can no longer access my floppy drives A and B. Anyone else encountered something like this ???
lbl@druhi.UUCP (LocklearLB) (01/09/86)
>I did the 1meg upgrade, and so far everything is working fine. I have >not installed the TOS ROMs. I used the method that involved adding 6 >68 ohm resistors. A side note: with the additional memory I have >made extensive use of the RAM DISK ( from Michitron ) and have encountered >something I can not explain. After some random amount of compiling, editing, >and copying of files to the RAM DISK something happens in which I can no >longer access my floppy drives A and B. Anyone else encountered something >like this ??? Not to worry - this is the result of a bug in the memory management routines in the current TOS. I understand the problem has been fixed in the ROM version of TOS. This is one of several reasons I want to get my hands on those ROMs ASAP!!! Barry Locklear AT&T Information Systems Labs Denver, CO ihnp4!druhi!lbl (303)451-7245
mark@dmcnh.UUCP (Mark Roddy) (01/13/86)
> > A side note: with the additional memory I have > >made extensive use of the RAM DISK ( from Michitron ) and have encountered > >something I can not explain. After some random amount of compiling, editing, > >and copying of files to the RAM DISK something happens in which I can no > >longer access my floppy drives A and B. Anyone else encountered something > >like this ??? > > Bug in RAM TOS. If you double click on the disk ICON, and then RAPIDLY click again, the mouse clickard will start auto-repeating. After a while, magically, the desktop wakes up and reopens the drive. It is irritating but less painfull than reboot. And now for something totally different. Anticipating a hard drive, I have started writing backup utilities. Step one was a mandatory clock verification routine for the boot sequence. It works fine, but the !@#$%^&* desktop gets loaded after the auto directory contents get run, and the brain damaged piece of code sets the clock to May something-or-other 1985. I know that one of the applications allows me to reset the clock after the desktop starts running. That is fine, but I've thrown all the desktop applications out to get more RAM. Also, if I don't have to set the clock, I will forget to do so, and files get timestomped with the wrong date. So the question is: does anyone with the ROM TOS know if this feature is retained? or, has anyone got some hack to fix this?