Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!mit-eddie!uw-beaver!ssc-vax!shuksan!tahoma!hrsw2!bakken
From: bakken@hrsw2.UUCP (David E. Bakken)
Newsgroups: comp.sys.amiga
Subject: my A1000 hangs in 2 different ways
Message-ID: <21@hrsw2.UUCP>
Date: Tue, 24-Nov-87 01:35:10 EST
Article-I.D.: hrsw2.21
Posted: Tue Nov 24 01:35:10 1987
Date-Received: Sun, 29-Nov-87 15:57:35 EST
Organization: Boeing Commercial Aircraft Co., Seattle, Wa.
Lines: 46
Keywords: hang, vd0:, popcli, rtclock, facc, Insider, memory, etc.
Summary: help!!!


I am having two apparently unrelated problems with Amy and would appreciate
any help in solving them.  I am running a 1000 with 1.2 and an Insider.

1)  	The startup script that works fine on my C-CLI disk fires up vd0:,
	popcli, rtclock (the Insider clock read program), and facc, in
	that order.  But then I was trying to set up a Vizawrite workbench
	disk, so I copied over the appropriate programs and changed the
	firing up of the shell to loadwb (I do binddrivers right before
	loadwb).  All the programs get fired up but then it hangs and the
	workbench never appears.  Deleting binddrivers does nothing, so
	I played with all combinations of mounting vd0: and firing up
	popcli, rtclock, and facc.  whenever popcli or facc was fired up
	it would hang as mentioned before.  When neither popcli or facc
	was fired up, if vd0: was not mounted it would work fine.  If vd0:
	was mounted, however, the workbench would appear normally, but when
	a CLI was fired up (by clicking its icon) the CLI window would
	appear for an instant and then disappear.

	I don't know if I'm overlooking something obvious or what.  But
	it seems like popcli and facc collide with my workbench.  I have
	never been able to get popcli to work with my OnLine! workbench
	environment so I gave up many moons ago.

2)	My OnLine! disk has worked well for a long time.  But now all of
	a sudden when I click open the disk icon it draws a few drawers
	and then the mouse freezes and the internal drive makes a horrible 
	grind, and then the screen is red, then green, then ...  (It's really 
	quite pretty but not what I'd like to see).  The disk has no
	errors on it and I did not munch anything to my knowledge.  And I
	can fire up OnLine! through the shell and it works fine.  Oh yeah,
	through all the color cycling the internal drive is whirring.

	The color cycling makes me wonder if an Insider connection is
	flaky (I didn't do the techy solder job), but I don't understand
	why this would happen only in one spot on one disk.  The top meg
	of my memory definitely works.  I'd better take it to my dealer
	to have it checked, I guess.

Any helpful hints for diagnosing the above problems would be greatly
appreciated.  Thanks!!!

-- 
Dave Bakken
uw-beaver!ssc-vax!shuksan!tahoma!hrsw2!bakken
(boring) disclaimer: these views are my own, not my employers.