[Coco] Glenside IDE Hard Drive Interface --- HOW-TO

Sun Nov 4 19:41:22 EST 2007

At 04:32 PM 11/4/2007, you wrote:
>You need to load syscall *before* you run Basic09. If you have the 
>NitrOS9 (or the Tandy OS-9) distro disk(s), the syscall module 
>should be in the CMDS directory.

Looking on the Tandy OS-9 floppy #2, I do see the command.  I don't 
know if this will cause a "collision" with NitrOS9 if
I use it.  Let me try and see what happens.

>--
>Regards, Bob Devries, Dalby, Queensland, Australia
>
>Isaiah 50:4 The sovereign Lord has given me
>the capacity to be his spokesman,
>so that I know how to help the weary.
>
>website: http://www.home.gil.com.au/~bdevasl
>my blog: http://bdevries.invigorated.org/
>
>----- Original Message ----- From: "Randy Just" <randyjust at comcast.net>
>To: "CoCoList for Color Computer Enthusiasts" <coco at maltedmedia.com>
>Sent: Monday, November 05, 2007 10:25 AM
>Subject: Re: [Coco] Glenside IDE Hard Drive Interface --- HOW-TO
>
>
>>At 04:18 PM 11/4/2007, you wrote:
>>>Randy, you'll need to LOAD the SYSCALL module into memory before 
>>>executing the Basic09 program.
>>>
>>>I would assume that the syscall module is on the same disk with 
>>>basic09? (/d0?)
>>
>>OK --- clueless question on my part.  How do I load the module and 
>>load makedesc.b09?  I have been
>>loading makedesc.b09 and then typing run.
>>
>>
>>
>>>--
>>>Regards, Bob Devries, Dalby, Queensland, Australia
>>>
>>>Isaiah 50:4 The sovereign Lord has given me
>>>the capacity to be his spokesman,
>>>so that I know how to help the weary.
>>>
>>>website: http://www.home.gil.com.au/~bdevasl
>>>my blog: http://bdevries.invigorated.org/
>>>
>>>----- Original Message ----- From: "Randy Just" <randyjust at comcast.net>
>>>To: "CoCoList for Color Computer Enthusiasts" <coco at maltedmedia.com>
>>>Sent: Monday, November 05, 2007 10:15 AM
>>>Subject: Re: [Coco] Glenside IDE Hard Drive Interface --- HOW-TO
>>>
>>>
>>>>
>>>>Here is the latest.  After thinking there might be read errors, I 
>>>>went ahead and made a back-up of
>>>>the floppy giving problems.  I tried a few different drives I 
>>>>have sitting around here and seem to have
>>>>been able to copy the files to another floppy giving better results.
>>>>
>>>>makedesc.b09 is now loading without errors.
>>>>
>>>>However, after going through the series of questions, it is 
>>>>erroring out at:
>>>>
>>>>#4A18   RUN Syscall($17, regs)
>>>>ERROR #043
>>>>BREAK: PROCEDURE Makedesc
>>>>
>>>>I am trying to do this on a single drive machine.
>>>>
>>>>Please advise.
>>>>
>>>>At 03:01 PM 11/4/2007, you wrote:
>>>>>Randy,
>>>>>is there any way you can get that code to me, so I can PACK it 
>>>>>into a runb-type module?
>>>>>Even if you snd a disk image of the source disk, I could work with it.
>>>>>
>>>>>
>>>>>--
>>>>>Regards, Bob Devries, Dalby, Queensland, Australia
>>>>>
>>>>>Isaiah 50:4 The sovereign Lord has given me
>>>>>the capacity to be his spokesman,
>>>>>so that I know how to help the weary.
>>>>>
>>>>>website: http://www.home.gil.com.au/~bdevasl
>>>>>my blog: http://bdevries.invigorated.org/
>>>>>
>>>>>----- Original Message ----- From: "Randy Just" <randyjust at comcast.net>
>>>>>To: "CoCoList for Color Computer Enthusiasts" <coco at maltedmedia.com>
>>>>>Sent: Monday, November 05, 2007 8:49 AM
>>>>>Subject: Re: [Coco] Glenside IDE Hard Drive Interface --- HOW-TO
>>>>>
>>>>>
>>>>>>
>>>>>>Doing a list /d1/IDE2.1/makedesc.b09 displays readable code.
>>>>>>
>>>>>>I tried the #24K --- still no go.
>>>>>>
>>>>>>Very frustrating.  I don't really care if I go the makedesc.b09 
>>>>>>route or ezgen route to get the hard drive up and running.  Just
>>>>>>would like to be able to use it at some point here.  The hard 
>>>>>>drive is sitting alongside my Coco looking both happy and depressed
>>>>>>all at the same time.  Happy it is recognized, but depressed it 
>>>>>>can't start storing Coco files.
>>>>>>
>>>>>>At 02:43 PM 11/4/2007, you wrote:
>>>>>>>Randy,
>>>>>>>Gene's comment certainly makes some sense, although with a 
>>>>>>>.B09 extension, I'd be confident that it is a Basic09 source 
>>>>>>>file. If that's the case, you should be able to do this:
>>>>>>>
>>>>>>>list /d1/IDE2.1/makedesc.b09
>>>>>>>
>>>>>>>If this results in garbage all over the screen, then it is a 
>>>>>>>PACKed module, and must indeed be executed by RUNB (although 
>>>>>>>Basic09 *does* know how to execute packed modules).
>>>>>>>
>>>>>>>For the life of me, I don't understand why the source code 
>>>>>>>wasn't supplied in packed form in the first place, *unless* it 
>>>>>>>was meant to be modified by the end user, which is IMHO not a good situation.
>>>>>>>
>>>>>>>TO ALL:
>>>>>>>Are there any users here which have done what Randy is trying 
>>>>>>>to do with the Glenside IDE controller software?
>>>>>>>
>>>>>>>--
>>>>>>>Regards, Bob Devries, Dalby, Queensland, Australia
>>>>>>>
>>>>>>>Isaiah 50:4 The sovereign Lord has given me
>>>>>>>the capacity to be his spokesman,
>>>>>>>so that I know how to help the weary.
>>>>>>>
>>>>>>>website: http://www.home.gil.com.au/~bdevasl
>>>>>>>my blog: http://bdevries.invigorated.org/
>>>>>>>
>>>>>>>----- Original Message ----- From: "Randy Just" <randyjust at comcast.net>
>>>>>>>To: "CoCoList for Color Computer Enthusiasts" <coco at maltedmedia.com>
>>>>>>>Sent: Monday, November 05, 2007 8:27 AM
>>>>>>>Subject: Re: [Coco] Glenside IDE Hard Drive Interface --- HOW-TO
>>>>>>>
>>>>>>>
>>>>>>>>
>>>>>>>>Thanks for your response.
>>>>>>>>
>>>>>>>>Tried using /d0/BASIC09 #16K
>>>>>>>>
>>>>>>>>Unfortunately, it seems to have gone from bad to worse.  Now 
>>>>>>>>I get an ERROR #032 followed by
>>>>>>>>about 15-20 ERROR #074 messages.
>>>>>>>>
>>>>>>>>At 02:17 PM 11/4/2007, you wrote:
>>>>>>>>>Randy,
>>>>>>>>>
>>>>>>>>> From that error report, I'd suggest that basic09 does not 
>>>>>>>>> have enough memory for the size of the basic09 procedure 
>>>>>>>>> file that you're trying to run.
>>>>>>>>>
>>>>>>>>>load basic09 with extra memory, like this:
>>>>>>>>>
>>>>>>>>>/d0/BASIC09 #16K
>>>>>>>>>
>>>>>>>>>then proceed with loading the file as you describe.
>>>>>>>>>
>>>>>>>>>--
>>>>>>>>>Regards, Bob Devries, Dalby, Queensland, Australia
>>>>>>>>>
>>>>>>>>>Isaiah 50:4 The sovereign Lord has given me
>>>>>>>>>the capacity to be his spokesman,
>>>>>>>>>so that I know how to help the weary.
>>>>>>>>>
>>>>>>>>>website: http://www.home.gil.com.au/~bdevasl
>>>>>>>>>my blog: http://bdevries.invigorated.org/
>>>>>>>>>
>>>>>>>>>----- Original Message ----- From: "Randy Just" 
>>>>>>>>><randyjust at comcast.net>
>>>>>>>>>To: "CoCoList for Color Computer Enthusiasts" <coco at maltedmedia.com>
>>>>>>>>>Sent: Monday, November 05, 2007 7:52 AM
>>>>>>>>>Subject: Re: [Coco] Glenside IDE Hard Drive Interface --- HOW-TO
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>1347 ERROR #069
>>>>>>>>>>111A ERROR #069
>>>>>>>>>>10CF ERROR #069
>>>>>>>>>>0FF5 ERROR #069
>>>>>>>>>>0FBC ERROR #069
>>>>>>>>>>ERROR #032
>>>>>>>>>>
>>>>>>>>>>The above are errors encountered when trying to load 
>>>>>>>>>>makedesc.b09 from a floppy disk.  No files are
>>>>>>>>>>being read from the hard drive at this time..  I am trying 
>>>>>>>>>>to get a boot diskette set-up so I can format the
>>>>>>>>>>hard drive.  At least I believe that is the process.  At 
>>>>>>>>>>this point I have a virgin hard drive.
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>At 01:41 PM 11/4/2007, you wrote:
>>>>>>>>>>>Randy Just wrote:
>>>>>>>>>>>><snip>
>>>>>>>>>>>>I am working with the assumption I load BASIC09 (i.e. 
>>>>>>>>>>>>/d0/BASIC09) up first and then do a
>>>>>>>>>>>>load /d1/IDE2.1/makedesc.b09
>>>>>>>>>>>>Doing the above results in errors.
>>>>>>>>>>>><snip>
>>>>>>>>>>>>Using idedetect.b09, the drive is detected, so I am 
>>>>>>>>>>>>assuming I am good there.
>>>>>>>>>>> ><snip>
>>>>>>>>>>>
>>>>>>>>>>>Whenever you are trying to get help with a problem, you 
>>>>>>>>>>>must supply as much information as possible on the 
>>>>>>>>>>>problem. So, what errors are you getting? The specific 
>>>>>>>>>>>errors, number or text content, is crucial information.
>>>>>>>>>>>
>>>>>>>>>>>Your problem could be bad hardware, drive or interface. It 
>>>>>>>>>>>could be software corruption, bad disk. It could be 
>>>>>>>>>>>missing driver and descriptor, mismatched OS-9 boot file. 
>>>>>>>>>>>The errors produced in attempting to load makedesc.b09 can 
>>>>>>>>>>>help narrow down the choices. That idedetect.b09 works, 
>>>>>>>>>>>does suggest as you mentioned that the hardware is good.
>>>>>>>>>>>
>>>>>>>>>>>Without more information, it seems strange that a required 
>>>>>>>>>>>file to access the hard drive would be placed on the hard 
>>>>>>>>>>>drive. That would be a "catch-22" situation. You ought to 
>>>>>>>>>>>have access to makedesc.b09 from the same location as idedetect.b09.
>>>>>>>>>>>
>>>>>>>>>>>--
>>>>>>>>>>>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
>>>>>>>>
>>>>>>>>
>>>>>>>>--
>>>>>>>>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
>>>>>
>>>>>
>>>>>--
>>>>>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
>>
>>
>>--
>>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