[Coco] VCC, VHD, NitrOS09 3.2.6 and RGD Dos question

[Robert Gault]

Ed Orbea wrote:
> Thanks for the information, I am currently working thought the items you 
> identified.
> There are a few things I do need to correct.
> (1) I said that I "saved d0 as d0_emu.dd", what I meant to say was that 
> I saved dd and dd_emu.dd.
Is this a typo? Do you mean you saved dd as dd_emu.dd?
> (2) I am working from a copy of vhd, not the original
> 
> Here is a dump of /h0:
> 
> Address   0  1 2 3  4 5  6 7  8 9  A B  C D  E F 0 2 4 6 8 A C E
> -------- ---- ---- ---- ---- ---- ---- ---- ---- ----------------
> 00000000 87CD 002F 0021 F181 CB00 2300 26FF 07FF .M,/.!q.K.#.&...
> 00000010 800F 0100 0080 0100 5A40 0100 4000 4003 ........Z at ..@. at .
> 00000020 2048 B052 42C6 456D 7544 73EB BFE6 96    H0RBFEmuDsk?F.
> 
> Here is the ident from the 40tkdsdd 3.8.6 floppy that boots to VHD. This 
> is the 40tkdsdd boot I made to "test" things. WHen I try to make a 
> 35tksdss version of the disk (dmode: cyl=23 sid-1 dns=1), it formats and 
> is created successfully, but then I try to boot from it (doesn't matter 
> if these is a vhd or not, nor does it matter if I am using RGBDOS or 
> not), it fails during boot, right after the 6th "." is displayed as part 
> of the boot process. It is my understanding that each "." signifies the 
> successful read of a LSNO sector.
This should not be happening. The VCC distributed hard drive does not in 
my hands display dots during the boot process. You must have the wrong 
boot module installed on your floppy.

> 
>  18 $C0 $A08C87 . KrnP2
crc OK
>  13 $C1 $310A4A . IOMan
crc OK
>   1 $C0 $3F9827 . Init
crc OK
>  37 $D1 $09EDE5 . RBF
crc OK
>   1 $E1 $85815B . EmuDsk
crc OK
>  82 $F1 $BFE696 . H0
crc OK
>   1 $E1 $2F617B . rb1773
crc OK
>  82 $F1 $37B271 . DD
crc Bad. I can't match this to any drive descriptor.
>  82 $F1 $37A8D9 . D0
crc OK for 40 track double sided
>  82 $F1 $B3CBA2 . D1
crc OK for 49 track double sided
>  82 $F1 $BF6E4C . D2
crc OK for 40 track double sided
>  16 $D1 $3F50A2 . SCF
crc OK
>   2 $E1 $CD4489 . VTIO
crc OK
>   4 $C1 $CF4A25 . KeyDrv
crc OK
>   3 $C1 $918510 . SndDrv
crc OK
>   7 $C1 $A4C5CC . JoyDrv
crc OK
>   2 $C1 $C3E661 . CoWin
crc OK
>  83 $F1 $012B5D . Term
crc OK
>  83 $F1 $3B6153 . W
>  83 $F1 $A9B825 . W1
>  83 $F1 $6A4A21 . W2
>  83 $F1 $4820E4 . W3
W# are OK
>   5 $D1 $6F9717 . PipeMan
crc OK
>   2 $E1 $895C5F . Piper
crc OK
>  80 $F1 $D512FB . Pipe
crc OK
>   9 $C1 $A9E4A4 . Clock
crc OK
>   1 $21 $484309 . Clock2
crc OK for Cloud9
> 
> So if I understand correctly, I do not need rb1773.dr in the boot file.
> 

You do need rb1773.dr because without it, you can't access floppies.

The contents of os9boot looks correct except for DD. It is not the CRC 
from the distributed VCC .vhd image which is $BDBB72. If sysgo is set to 
use DD, then the boot most likely would fail.

There is still no information on Rel, Krn, and Boot. These are on track 
34 and you would need special software to check the CRCs on the boot 
disk. You can check the CRC of Boot when you save it to the Boottrack 
directory. It should be $2B0B09.

This disk would fail to boot as a floppy unless it was also on the .vhd 
and LINK had been run when the hard drive would be used as soon as the 
kernel started to run. It could only be used to boot strictly from the 
floppy if the normal floppy boot module was on track 34.

===========================================
Why not e-mail me your boot disk? That's the fastest way for me to tell 
what is wrong.