Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!ucbvax!pasteur!ames!oliveb!sun!pepper!cmcmanis
From: cmcmanis%pepper@Sun.COM (Chuck McManis)
Newsgroups: comp.sys.amiga
Subject: Re: Strange Happenings...
Message-ID: <100808@sun.Eng.Sun.COM>
Date: 24 Apr 89 20:03:38 GMT
References: <4110@crash.cts.com>
Sender: news@sun.Eng.Sun.COM
Reply-To: cmcmanis@sun.UUCP (Chuck McManis)
Organization: Sun Microsystems, Mountain View
Lines: 62

[I'm guessing here of course, take that for what it's worth.]

In article <4110@crash.cts.com> (Lawrence Greenwald) writes:
>What happened follows:
>
>I was playing around with Deluxe Paint II (not III) trying to load some
>pictures (some with 64 colors). I was getting junk (I didn't care really
>what I was getting).

	This really says "I was using DPaint II with some pictures that it
	had no idea how to handle, EA probably never tested this stuff at
	EA either."

> Anyway all of a sudden I get a requester: AmigaFF has
>a read/write error (Retry/Cancel). Well, I hit retry and get my garbled
>picture. "Oh well, enough of that" and I leave Dpaint.

	After confusing the heck out of Dpaint, I get a *disk* error. 
	[Have you ever seen these before?]

> Then close my disk icon and remembering what I want to do, start 
> up ARPshell (1.3) and run DiskMan (the PD version of DiskMaster) 
> and click on FH0: box.

	Does this imply a FastFileSystem partition (FH0?).

>Surprise 1: Get the read/write error requester again. Hit retry a few times
>before hitting cancel and bringing back Diskman with directory of FH0:.

	At this point I would say, oh great, Dpaint has screwed the FFS
	handler but not enough to break it completely, just enough to 
	make it act weird. I WOULD REBOOT. 

>It gets better. [More bizarre behaviour deleted]

>Enough of that, so shut down and get out of the house for a while...

	Maybe you should have done this first.

>It's now Thursday, April 20. Fire up machine and open disk, still got that
>missing space. So, now copy the entire drawer to new directory 'Qback'.
>Then try 'copy Empty.info to Qback.info'. NOW IT WORKS!! Directory is there
>as well as access via Workbench icon.

	This is the biggest clue that Dpaint just subtly corrupted memory
	and hosed your system. It is a hazard of multitasking without 
	memory protection, and one of the reasons why GOMF is so dangerous.
	I'd bet that your disk is now corrupt (mostly because you tried
	to write on it before rebooting) and that the next time it validates
	(could be in a couple of weeks) you'll get the "Use DiskDoctor"
	requester. The lesson to be learned here is that when your doing
	something and the system starts acting "funny" then you should 
	take the time to reboot. 

>Can anyone figure this??

	Those are my guesses.

--Chuck McManis
uucp: {anywhere}!sun!cmcmanis   BIX: cmcmanis  ARPAnet: cmcmanis@sun.com
These opinions are my own and no one elses, but you knew that didn't you.
"A most excellent barbarian ... Genghis Kahn!"