[Coco] Glenside IDE booting problems

[Little John]

I should have been paying more attention....

----- Original Message ----- 
From: "Don Johnson" <coco at fivejohnsons.com>
To: "CoCoList for Color Computer Enthusiasts" <coco at maltedmedia.com>
Sent: Friday, December 03, 2010 11:08 AM
Subject: Re: [Coco] Glenside IDE booting problems



>

> On 2010-12-03, at 7:23 AM, Little John wrote:

>

>> I was wondering if the OS-9 L2 CC3HDisk supports the Glenside Interface? 

>> I don't know a lot about OS-9 - I use Nitros9 frequently. Anyway, I was 

>> just thinking that CC3HDisk was likely intended for Tandy's crappy Hard 

>> Disk Interface which uses a Tandy "primary" drive (MFM I think). Wouldn't 

>> it have to be patched to use the Glenside interface? I could be 

>> completely off here - I just thought I'd ask :)

>

> No the CC3HDisk module in my OS9Boot is the driver supplied by Glenside 

> with the IDE Interface.  It is the 1.0 version though, and it may have 

> it's own problems as pointed out in other responses, but I would expect 

> that any problems it has would be in controlling the IDE drive and not 

> just booting up the OS9 floppy.

>

>

>> -JohnT-

>> ----- 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 7:00 AM

>> 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

>

>

> --

> Coco mailing list

> Coco at maltedmedia.com

> http://five.pairlist.net/mailman/listinfo/coco