[Coco] Glenside IDE booting problems

[Don Johnson]

On 2010-12-03, at 1:54 PM, Bob Devries wrote:

> Robert Gault said:
> 
>> OK, while I agree that a switch to NitrOS-9 is advisable, here is what you can start with for testing purposes. Do not place cc3hdisk and H0 after RBF. Use the exact order of modules found in your most recent working OS9Boot list with cc3hdisk and h0 AT THE END. This will avoid the "boot order bug" that Gene referred to. Even if there might be a problem with the location of cc3hdisk and h0, you should at least be able to boot from the floppy without hard drive access.
>> 
> 
> Don told us he was using the CONFIG programme from the original OS9 release. That being so, I don't think he has control over the order of modules in the OS9Boot file.
> 

Correct I was using the Config utility to create a new System Disk, but the disk that came with the IDE Interface included a copy of EZGen as well.  With that program I was able to add the Glenside drivers and descriptor directly to a backup of a System Disk, and in doing so control which module I added them behind in the OS9Boot file, thus controlling the module order.

I found that putting the hard disk modules lower in the list than the floppy disk drive modules worked and I was able to boot OS9 from the floppy drive with the Hard Drive modules included.  I've run into a couple other problems since then, but I was able to move the modules around with EZGen to help solve the initial problem.


> Regards, Bob Devries
> 
> ----- Original Message ----- From: "Robert Gault" <robert.gault at att.net>
> To: "CoCoList for Color Computer Enthusiasts" <coco at maltedmedia.com>
> Sent: Friday, December 03, 2010 11:00 PM
> Subject: Re: [Coco] Glenside IDE booting problems
> 
> 
>> Don Johnson wrote:
>>> 
>> 
>>> Okay, so this is good stuff, and useful as well.  I ran the ident command as you suggested and compared it to my other system disks that I created that work, but without the hard disk drivers and descriptors.  The lists were the same except for the CC3HDisk and H0 modules existing in the non-working System Disk, and not there on the working System Disks.  From other responses I realized that the DD module was not there before because I did not add it during the Config process, so I went back and did the same steps over again.  Here is the list of modules in the newly created OS9Boot file (that still does not work so for sanity sake at least I'm consistent).
>>> 
>>> 17 $C0 $47B370 . OS9p2
>>> 12 $C1 $FD1FEA . IOMan
>>> 67 $C0 $0B2322 . Init
>>>   5 $11 $1006FE . CC3Go
>>>   9 $C1 $D28AFD . Clock
>>> 28 $D1 $EFBE13 . RBF
>>>   5 $E1 $02BF2A . CC3HDisk
>>> 82 $F1 $0C9F6C . H0
>>>   9 $E1 $759161 . CC3Disk
>>> 82 $F1 $FC1918 . D0
>>> 82 $F1 $9F46Ca . D1
>>> 82 $F1 $E6B118 . DD
>> 
>> OK, while I agree that a switch to NitrOS-9 is advisable, here is what you can start with for testing purposes. Do not place cc3hdisk and H0 after RBF. Use the exact order of modules found in your most recent working OS9Boot list with cc3hdisk and h0 AT THE END. This will avoid the "boot order bug" that Gene referred to. Even if there might be a problem with the location of cc3hdisk and h0, you should at least be able to boot from the floppy without hard drive access.
>> 
>> To rephrase, you must do this enhancement step by step so that only one thing is changed at a time or you will never discover the location of the actual problem. So, your new boot disk must be identical to the latest working boot disk but with cc3hdisk and H0 at the end of OS9Boot.
>> Tell us if you can get at least this far and boot OS-9.
>> 
>> It will be crucial that your H0 descriptor match the capabilities of your hard drive. If the descriptor is wrong, you will never get the hard drive to work. What utilities are provided with the Glenside package to read the hard drive capabilities and create a custom descriptor?
>> 
>> --
>> Coco mailing list
>> Coco at maltedmedia.com
>> http://five.pairlist.net/mailman/listinfo/coco 
> 
> 
> --
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco