[Coco] Glenside IDE booting problems

Don Johnson coco at fivejohnsons.com
Fri Dec 3 00:22:23 EST 2010


On 2010-12-02, at 6:38 PM, Robert Gault wrote:

> Don Johnson wrote:
>> Robert
>> 
>> Okay, well let me restate my problem and try to fill in some of your questions.
>> 
>> For a first step I copied the drivers available from the Glenside disk to the module directory on a copy of the OS-9 Boot disk.  I re-named the cc3hdisk_16_50.dr driver to cc3hdisk.dr because after many failed attempts the config utility program in the next step seemed to be looking for that name. I did not re-name the h0_16.dd.
>> 
>> I then called the config command from the Boot disk and followed the instructions as directed on screen, as described in the OS-9 manual, Chapter 7, on how to create a new system diskette.  During that process I selected to include the module for printer (P), PIPE, /d0_35S, /d1_35S, and /h0_16.  I selected the TERM_WIN with all the available windows.  I put in a newly formatted floppy and let the work begin in created a new system disk.
>> 
>> When I tried to boot into OS-9 with that system disk (floppy),  which I believe to have been built with a hard drive device, it starts off normal enough with the 'OS-9 BOOT' message on the screen, and then shortly after that the word 'FAILED' appears below and the floppy stops.
>> 
>> That is as far as I have gotten.
>> 
> 
> Don,
> 
> OK, it would seem you would like to boot into OS-9 from a floppy and then have access to the hard drive. That would require you to use the normal Boot module for floppies and Init and Sysgo should point to the floppy as the default directories; /D0 and /D0/CMDS.
> For this to work, all you need to do is add a Glenside driver and descriptor to the OS9Boot file. Not having the Glenside package, I've no idea how easy their documentation is to follow. Gene and Willard can offer advise on that score.
> 
> As Gene requested, please post the contents of your new OS9Boot file. That is easily obtained. Once you have created the new boot disk enter
> ident /d0/os9boot

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
13	$D1		$F946CA	.	SCF
12	$E1		$CC3EA4	.	PRINTER
83	$F1		$FE3BAE	. 	P
16	$E1		$F737C2	.	CC3IO
14	$C1		$6E4441	.	GrfInt
83	$F1		$EC1C40	.	Term
83 	$F1		$75DEBB	.	 W
83	$F1		$7CD180	.	W1
83 	$F1		$8EE4C6	.	W2
83 	$F1		$E42902	.	W3
83	$F1		$119408	.	W4
83	$F1		$C109F3	.	W5
83	$F1		$A3C36E	.	W6
83	$F1		$AC6B4B	.	W7
  4	$D1		$AD6718	.	PipeMan
  2	$E1		$5B2B56	.	Piper
80	$F1		$CC06AF	.	Pipe


I produced this list with the -s option, but without it all the CRC checks showed (Good).



> and a list of the contents will be printed to the screen. Each module listed should say Good and you should list all the module names. The list should look exactly like any other OS9Boot file you have created, except for the presence of the Glenside driver and descriptor.
> Can we assume you have been able to create any boot disks that work for a pure floppy system and actually boot you into OS-9?
> 
> Make sure that your new boot disk contains a shell and gfrdrv in the CMDS directory.

I created the system disk with a full copy of the commands from the original System disk, and I verified that both the shell and gfrdrv commands were there.


> 
> --
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco




More information about the Coco mailing list