[Coco] *SOLVED* Drivewire 4: nos96809l1v030209coco2_dw3.dsk format??

[Chad H]

So there isn't any DMODE adjustment or anything I can do under NitrOS-9 and
then COBBLER it back to a new image to change the baud rate?

-----Original Message-----
From: coco-bounces at maltedmedia.com [mailto:coco-bounces at maltedmedia.com] On
Behalf Of Aaron Wolfe
Sent: Saturday, September 28, 2013 11:47 AM
To: CoCoList for Color Computer Enthusiasts
Subject: Re: [Coco] *SOLVED* Drivewire 4: nos96809l1v030209coco2_dw3.dsk
format??

The "DW4" roms are experimental and unsupported at this time.  If you follow
the DW4 documentation, you will be instructed to use the DW3 roms.


On Sat, Sep 28, 2013 at 12:41 PM, Chad H <chadbh74 at hotmail.com> wrote:
> Ok, I should have realized this before, but oh well...  The Disk image 
> was based on "DW3" and I've been loading DW4 ROM's When I load the DW4 
> ROM it triggers the DW4 server into 230k "Turbo mode".
> Subsequent loading of the DW3 NitrOS-9 causes it to fail I think 
> because it's switching back to DW3 56k rate and the server is still in 
> 230k Turbo mode.
>
> * Disabling HDBDOS Translation had no effect.
>
> So I started over...
>
> Loading the old DW3 ROM and then DOS into the image...WORKS!
>
> SO I guess there is now DW4 variant of these images to allow Turbo 
> Mode?  :(
>
> -----Original Message-----
> From: coco-bounces at maltedmedia.com 
> [mailto:coco-bounces at maltedmedia.com] On Behalf Of Aaron Wolfe
> Sent: Saturday, September 28, 2013 11:32 AM
> To: CoCoList for Color Computer Enthusiasts
> Subject: Re: [Coco] Drivewire 4: nos96809l1v030209coco2_dw3.dsk format??
>
> Make sure you don't have HDBDOS translation turned on.
> Other than that, check for errors in the server log, they may reveal 
> something.
> Another possibility is that coco2 builds were broken when I generated 
> the disks I provide, and they are still broken today.
> Yet another is there is something not happy with your system.. cable 
> too long, serial port funky, RAM not ramming properly... ?
>
>
> On Sat, Sep 28, 2013 at 12:26 PM, Chad H <chadbh74 at hotmail.com> wrote:
>> Well I tried the other link and got the same thing...
>> http://www.mediafire.com/download/upw1g5462sk9edw/NitrOS9-DW4_problem.
>> wmv
>>
>> Any ideas?
>>
>> -----Original Message-----
>> From: coco-bounces at maltedmedia.com
>> [mailto:coco-bounces at maltedmedia.com] On Behalf Of Aaron Wolfe
>> Sent: Saturday, September 28, 2013 11:20 AM
>> To: CoCoList for Color Computer Enthusiasts
>> Subject: Re: [Coco] Drivewire 4: nos96809l1v030209coco2_dw3.dsk format??
>>
>> No
>>  On Sep 28, 2013 12:13 PM, "Chad H" <chadbh74 at hotmail.com> wrote:
>>
>>> Is there any settings that need to be set in DriveWire 4 since this 
>>> is not the typical 168k image?
>>>
>>> -----Original Message-----
>>> From: coco-bounces at maltedmedia.com
>>> [mailto:coco-bounces at maltedmedia.com]
>>> On
>>> Behalf Of Aaron Wolfe
>>> Sent: Saturday, September 28, 2013 11:10 AM
>>> To: CoCoList for Color Computer Enthusiasts
>>> Subject: Re: [Coco] Drivewire 4: nos96809l1v030209coco2_dw3.dsk format??
>>>
>>> All of the disks on the DriveWire 4 page are intended for use with 
>>> DriveWire 4.
>>> To use them, you insert them into a DW4 drive using the DW4 software.
>>> Do not write them to a physical floppy of any kind.
>>>
>>> If the disk does not boot properly when inserted in DriveWire disk 
>>> 0, we may have a bad disk image on the page, or your system may be 
>>> having some trouble.
>>>
>>> I do not have a coco 2, so cannot guess which might be happening.
>>>
>>> Anybody here using a coco 2 and can test the disk image in question?
>>>
>>>
>>>
>>> On Sat, Sep 28, 2013 at 11:24 AM, Chad H <chadbh74 at hotmail.com> wrote:
>>> > OK I found this .DSK image on the DriveWIre 4 Downloads page 
>>> > thought it would be what I need on my CoCo2 to run NOS9 with 
>>> > DriveWire
> 4.
>>> > However I haven't been able to get it to even boot yet.  I tried 
>>> > loading it into DriveWire 4, Drive 0 and DOS into it.after
>>> > "NitroOS9 Boot" it goes to garbage.  Same thing when I DISKINI'd 
>>> > it
> real floppy.
>>> > Then I realized it's a 433k image.  I tried writing it to a 
>>> > physical floppy as a double-sided disk.  Now when I issue DOS 
>>> > command, I just get "OK" right back.  Can someone tell me the 
>>> > specifics on this image as to  tracks/sides, etc and whether its
> intended for "real"
>>> > floppy use
>>> or
>>> loaded into DRiveWire?
>>> >
>>> >
>>> > --
>>> > Coco mailing list
>>> > Coco at maltedmedia.com
>>> > http://five.pairlist.net/mailman/listinfo/coco
>>>
>>> --
>>> Coco mailing list
>>> Coco at maltedmedia.com
>>> http://five.pairlist.net/mailman/listinfo/coco
>>>
>>>
>>> --
>>> Coco mailing list
>>> Coco at maltedmedia.com
>>> http://five.pairlist.net/mailman/listinfo/coco
>>>
>>
>> --
>> Coco mailing list
>> Coco at maltedmedia.com
>> http://five.pairlist.net/mailman/listinfo/coco
>>
>>
>> --
>> Coco mailing list
>> Coco at maltedmedia.com
>> http://five.pairlist.net/mailman/listinfo/coco
>
> --
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco
>
>
> --
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco

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