[Coco] Glenside IDE booting problems
coco at fivejohnsons.com
Fri Dec 3 15:45:33 EST 2010
On 2010-12-03, at 12:12 PM, Don Johnson wrote:
> On 2010-12-03, at 5:00 AM, Robert Gault wrote:
>> 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?
> Well the Glenside disk includes a shareware copy of EZGen to help add the modules to the OS9Boot file, and a couple other programs that will detect the ide drive and recluster it if necessary. I don't see anything that will customize the descriptor.
> However, I did as you suggested and added the CC3HDisk and H0 modules to the end of a fresh copy of my favourite System Disk (startup modifications and white on blue windows included) that I know works, and the OS9 booted up off the floppy just fine, but when I tried to use the Glenside disk included lformat program to format the hard drive I got a #221 error (module not found). I then moved the two modules up the list to just behind the disk drive descriptors, and once again the OS9Boot from the floppy worked. This time using the lformat program found my hard drive and formatted it (4.3 GB hard drive formatted to 2062 MB, so not bad).
> Not believing it actually worked I did a dir /h0 on it and it showed me nothing (empty of course but no errors). I copied a couple files off the Glenside Disk to /h0 and another dir /h0 call showed they were there.
> My success was only short lived though.
> After I copied the files over to the hard drive I decided to reboot it one more time, and this time it failed. Now, it always seems to fail just when it is going to ask me to enter the date, so maybe it is this clock module issue that Gene mentioned. Also, because I did not adjust the h0.dd in any way, and it failed after the hard drive was formatted, maybe that is a problem?
Okay, latest update. The new System Disk I created with the Hard Disk modules installed will boot up only if the Hard Drive is turned off during boot up. I find this to be weird considering everything in the Glenside Documentation suggested that it needed to be on during boot up or else if would fail. To add to the weirdness if I turn the hard drive on after the boot up process has completed I can still access the hard drive at /h0.
> Any suggestions on how I can modify the device descriptor?
>> Coco mailing list
>> Coco at maltedmedia.com
> Coco mailing list
> Coco at maltedmedia.com
More information about the Coco