Re: Problems running Basic.system on hard drive

[Smarter%than%Spam@vuse.vanderbilt.edu (Tilghman Lesher)]

David de Sosa originally wrote:
> I have  GS/OS 6.01 on a hard drive with a Ramfast rev C
> 3.01c card.  When I click on the Basic.system icon, the
> Basic logo screen appears but there is no cursor (Basic
> ver 1.5).  If I hit return, then the applesoft cursor ']'
> appears.  If I type in a small basic program and run it,
> it prints out to the screen as if the 'trace' command has
> been activated.  If I type 'notrace' the output to screen
> acts normally.  When I am ready to exit Basic, typing
> 'BYE' crashes the system into the monitor mode every
> time.  If I boot GS/OS from the system disk, I have none
> of these problems.  The only difference between the hard
> drive and disk is that the hard drive must be utilizing
> the Ramfast driver file.  I have no file called 'startup'
> or anything else unusual that I am aware of that could be
> conflicting with Basic.system.

In article <5g93sc$cql@sf18.dseg.ti.com>, David de Sosa (dmds@msg.ti.com) wrote:
: 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.

This would tend to suggest that the RamFast is not your problem.

While the '8' key bypasses all drivers and FSTs, SetStart set to
Basic.System loads everything.

1)  What happens when you shift boot, then launch Basic.System?
2)  How much RAM do you have?  Which expansion card?  Results of
RAM test utilities?
3)  Can you provide a list of all the files in */System/System.Setup?
4)  Possibly (which would explain why launching from Finder screws
up), what Finder Extensions do you have?  One of them may be doing
something funky when passed FinderSaysOpen.

--
__ __|_) |       |                    
   |   | |  _` |   \   ` \   _` |   \ 
  _|  _|_|\__, |_| _|_|_|_|\__,_|_| _|
          ____/