[Coco] False alarm was Re: Becker boot disks and 6309 lg labeling

[Robert Gault]

Becker booting now works perfectly with 6309 labels. The problem was an oversight on my part.

There are two ways to boot a Becker disk from an emulator. 1) Use the Becker HDBDOS ROM. 2) Use the 
emulator RGBDOS ROM and have the boot track on a .vhd Basic "disk".
I was using the second and that caused the problem as track34 did not have the correct kernel for 
the new NitrOS-9. It would however, still boot a Becker disk where no 6309 labels were in use.

So, I copied T34 from the new Becker disk to my VCC .vhd and could boot the Becker disk with 6309 
labels. I could also switch VCC to the Becker HDBDOS and boot the Becker disk with 6309 labels.

Robert

Robert Gault wrote:
> I have been able, using a snapshot of the NitrOS-9 project June10,2019 to create normal and
> Drivewire disks which have 6309 lg labeling on most if not all files having 6309 code. These disks
> boot and behave normally.
>
> A Becker disk will not complete the boot process. There is not much difference between a Drivewire
> and Becker boot disk. The essence is just dwio_becker.sb vs dwio.sb. I don't see anything in the
> dwio.asm file that would cause this problem. I don't see boot_dw_becker being involved as all the
> modules in OS9Boot load and the boot process stops with .... Clock2 i2x  .
>
> This is more of a challenge than anything I consider important, so I am quite happy having all
> modules labeled as 6809 code. Anyone have some ideas?
>
> Robert
>