Re: Problems running Basic.system on hard drive

[dmds@msg.ti.com (David de Sosa)]

In article <33257D12.3A04@swbell.net>, rubywand@swbell.net says...
>
>>     Maybe; first, it does no harm to unplug and securely replug the SCSI 
>cable to your hard disk.
>
Problem still exists.

>     Zip's CDEV is known to be buggy. Also, it is unclear why you would 
>have Zip.init installed on a hard disk. Normally, Zip.init is used only 
>on diskettes to make changes in Zip's settings to accommodate diskette 
>boots. It may be a good idea to wipe both the Zip CDEV and the Zip init.
>
I used the latest patch to fix CDEV last year.  Okay deleted Zip init from 
System.setup folder.  No affect even after turning of computer and restarting.

>     If the above does not help, then, before doing hardware-related 
>checks, you may want to retry BASIC.SYSTEM after wiping the 'usual 
>suspects': AppleTalk (drivers, inits), CloseView Init, ICONS/Desktop, 
>screen savers, any other weird inits, NDA's, etc..
>
I tried some other things last night which may give someone some clues to my 
problems.  I tried booting the hard drive holding down the '8' which launches 
directly into Prodos.  This causes Basic.system to work normally when 
selected.

Also, by configuring the Setstart utility to launch directly into Basic.system 
instead of the Finder, Basic.system seemed to work normally again.  What 
file(s) are actually being bypassed or what sequence of events is occurring 
when the '8' key is pressed during bootup and also when the Setstart is 
configured as I have described.  It is a pain to have to boot into 
Basic.system everytime and then exit Basic.system to get to the desktop.

David