Re: Problems running Basic.system on hard drive

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

>    Question: does this program have any statements of the following
>form: 'if (...) then flash'? In one of the old Nibble Magazines (Jan
>86, or thereabouts), Sandy Mossberg's _Disassembly Lines_ covers a bug
>where a 'THEN FLASH' could force Basic.system into a trace mode.
>
No.  The program I am referring to is just something I typed up in a couple of
minutes to test out this problem i.e. a couple of print statements and a 
simple do loop.  Any Basic program would show the same symptoms I'm sure.     
 
>    Other than that, I'd recommend making sure that the copy of ProDOS
>and Basic.system are the same between thge working system disk and
>your HD.
>
They are.  I just finished re-initializing my hard disk because my directory 
had gotten corrupted recently and I wasn't able to write to the drive anymore. 
I reloaded GS/OS 6.01 using the Installer, then added the Ramfast driver, 
ZipGS Init and other ZipGS files (CDA, CDEV).  I've always had this problem 
trying to use Basic.System off the hard drive since day one.

I really think it has something to do with using the ZipGS or Ramfast drivers
because everything else loaded is identical to what's on the system disk 
files. 

In the past someone suggested that I may have a rogue 'startup' file but there
is no 'startup' file (there is a 'start' file however).  Also, someone 
suggested booting directly into Prodos (holding down the 8 key while booting) 
to see if Prodos commands would be recognized from Basic.  They are so what
does this tell me? Nothing.  I wish I could get into the ZipGS and Ramfast 
driver files to see what the hell is going on.

David