[Coco] NitrOS9 L1 Coco 2b 32 col 330 04-13-2014.vhd on XRoar

[William Carlin]

I changed the boot_dw_becker to boot_1773_6ms and left /dd pointing to /x0
and now the procedure I described above will allow me to boot using DOS
200.  I wanted to remove the dw printer drivers and add three additional
virtual serial drivers so I can have two telnet sessions (one incoming and
one outgoing) and still have a free channel to use the dw command to manage
the DriveWire 4 server.

Thanks,

William

On Mon, Jan 2, 2017 at 10:15 PM, Bill Pierce via Coco <coco at maltedmedia.com>
wrote:

> William, the boottracks used on those disks point to the VHD for their
> OS9Boot file (boot_becker). The only thing used from the HDBDOS disk image
> (disk 200) IS the boottrack. The "boot_becker"n will always look to DW
> drive 0 (OS9 partition).
> Try Copying the OS9Boot file (not the kernel) from the disk you created to
> the VHD.
> It's a common mistake when using boots for HDs and such. The way it works
> is the "boot" file used in the boottrack (in L1, Rel, krn, krnp2, init, &
> boot) determines on what device rel looks for the OS9Boot. The boot I used
> on the XRoar Starter Kits is the "boot_becker" which looks to the VHD0, not
> the floppy which holds the boottrack. A standard floppy boot could be used
> and then it would boot from the intended floppy image on the HDBDOS drive.
> I hope this makes sense.
>
> Feel free to email me off list anytime :-)
>
>
>
>
>
>
> Bill Pierce
> "Charlie stole the handle, and the train it won't stop going, no way to
> slow down!" - Ian Anderson - Jethro Tull
>
>
>
> My Music from the Tandy/Radio Shack Color Computer 2 & 3
> https://sites.google.com/site/dabarnstudio/
> Co-Contributor, Co-Editor for CocoPedia
> http://www.cocopedia.com/wiki/index.php/Main_Page
> Global Moderator for TRS-80/Tandy Color Computer Forums
> http://www.tandycoco.com/forum/
>
> E-Mail: ooogalapasooo at aol.com
>
>
>
>
>
>
> -----Original Message-----
> From: William Carlin <whcarlinjr at gmail.com>
> To: CoCoList for Color Computer Enthusiasts <coco at maltedmedia.com>
> Sent: Mon, Jan 2, 2017 9:03 pm
> Subject: [Coco] NitrOS9 L1 Coco 2b 32 col 330 04-13-2014.vhd on XRoar
>
> I hate to be a bother Bill but I cannot figure out how to get my
> ownOS9Boot to be recognized by the system.  The same procedure I use for
> VCCis not working.Here is what I am doing:Insert a 35 track single sided
> disk image into Xroar Drive 1 making sure itis writableCreate my 35 track
> single sided boot disk in /d0Hard reset XRoar.Press 6 to exit to BASICMake
> sure that drives 1-4 are turned off.  DRIVE OFF(Do a DIR 0 to make sure the
> disk image is seen)BACKUP 0 TO 200 ( I know that 255 is supposed to be the
> currently linkeddrive because the program listing for the AUTOEXEC.BAS does
> a DOS 255command when you press '5' to boot NitrOS-9)DRIVE 254 (Where the
> HDB-DOS tools reside)NEW:RUN"LINK.BAS"When prompted what drive to link to I
> type '200'.Hard reset XRoarPress 6 to exit to BASICDOS 200NitrOS-9 boots
> and I do a 'mdir" command. It's not my OS9Boot that hasloaded.  It's still
> the default OS9Boot.I have tried backing up to drive 255 and booting both
> with and withoutrunning the LINK.BAS program.Deleting the OS9Boot from the
> DriveWire drive /x0 and replacing it with myOS9Boot makes NitrOS-9 crash
> before the version information is displayed.Deleting my OS9Boot and
> replacing it with the original OS9Boot also causesNitrOS-9 to crash before
> the version information is displayed.  Is there adocumented procedure for
> creating you own OS9Boot?Thanks,William Carlin-- Coco mailing
> listCoco at maltedmedia.comhttps://pairlist5.pair.net/mailman/listinfo/coco
>
> --
> Coco mailing list
> Coco at maltedmedia.com
> https://pairlist5.pair.net/mailman/listinfo/coco
>