Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/5/84; site dmcnh.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!gamma!epsilon!zeta!sabre!petrus!bellcore!decvax!ittatc!sii!dmcnh!mark
From: mark@dmcnh.UUCP (Mark Roddy)
Newsgroups: net.micro.atari
Subject: Re: Re: 1meg upgrade
Message-ID: <217@dmcnh.UUCP>
Date: Mon, 13-Jan-86 09:38:38 EST
Article-I.D.: dmcnh.217
Posted: Mon Jan 13 09:38:38 1986
Date-Received: Wed, 15-Jan-86 07:55:34 EST
References: <1241@gitpyr.UUCP> <33@calgary.UUCP> <116@druhi.UUCP>
Organization: Datamedia Corp, Nashua, NH
Lines: 29

> > 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?