[Coco] This did not work adding t2

[plt]

I need /t2 and should have never been removed from Nitros9. There has to
be a way to work around the issue?

On Mon, March 3, 2025 21:57, Christopher R. Hawks via Coco wrote:
> On Mon, 3 Mar 2025 14:26:48 -0600
> Allen Huffman via Coco <coco at maltedmedia.com> wrote:
>
>
>>> On Mar 3, 2025, at 1:32 PM, plt via Coco <coco at maltedmedia.com>
>>> wrote:
>>>
>>>
>>> The two files got inserted but vcc is failing to reboot.
>>>
>>
>>
>> I have never worked with VCC, so I will have to turn this over to
>> others with more experience. If the goal is just to add the driver and
>> descriptor to an existing boot that works, that should do it — unless
>> it is the old Boot List Order Bug. That would make boot files “just
>> not work” and no one understood why. You just had to move things
>> around int he boot file until it started working. -- Allen
>
> Phil:
>
>
> I can't do anything about getting VB to talk Drivewire. (Since I
> retired, Microsquat products are not allowed in my house, HI GENE !!!)
>
> Adding the driver and descriptor to an existing bootfile will not
> allow Drivewire to use them. You should use one of the existing disks from
> the NitrOS9 tree. (Like NOS9_6809_L2_v030300_coco3_rs232pak.dsk for a CoCo
> 3,) The kernel (boot track) on these disks will load the
> bootfile using drivewire (using the rs232 pack) and that bootfile will do
> all its I/O  thru drivewire. Once you have that verified and working, you
> can write the VB app to be a drivewire server.
>
> If you need specific VCC steps, I'm sure someone can provide
> details...
>
> Christopher R. Hawks
> HAWKSoft
> --
> You can't have everything.  Where would you put it?  -- Stephen Wright
> ----------------------------------------
> \   ^__^
> \  (oo)\_______
> (__)\       )\/\
> ||----w |
> ||     ||
>
>
> --
> Coco mailing list
> Coco at maltedmedia.com
> https://pairlist5.pair.net/mailman/listinfo/coco
>
>