[Coco] Hard disk image

Fri Oct 16 15:23:03 EDT 2015

Hi,
why I didn't though of using toolshed ...
I will try this after I finish with part3 of manually making a
bootable nitros-9 hard disk image :)

On Fri, Oct 16, 2015 at 3:15 PM, Bill Pierce via Coco
<coco at maltedmedia.com> wrote:
> Mathieu, the max size for a NOS9 partition is about 128meg, but by setting the "Cluster Size" higher than 1, you can actually go up to 4 gigs!! I have 2 x 4g partitions on my Glenside IDE HD. This requires a little knowledge of the RBF system as well as intimate knowledge of your drives (and drivers).
>
> As for creating a VHD, the easiest way is to copy an existing one and format it. BUT... the standard size for the DW drive descriptors (/x0-/x3) is NOT the same size as most VHDs you'lll find so problems can arise doing that unless you set you descriptors to the same size as the VHD, especially since you are planning to mount in various systems.
> I have all my VHD descriptors set for 128meg (/x0-/x3, /h0(emudsk),/DD (which ever I decide to use)) so formatting across systems is the same.
>
> To avoid the problem, you can use ToolShed and create a vhd of the size you need.
> To do this, you need cmd line access (console mode on most OS's). Here is the cmd to create a 128meg VHD:
>
> os9 format OS9diskname.vhd -e l524288 ss dd
> (note: the first character in the size (l524288) is lowercase "L", not "1")
>
> Keep in mind, this creates a single partition, 128meg, OS9 VHD. To create a different size, just change the size to suit your needs.
> To create a 256 disk (partition) RSDOS formated vhd for HDBDOS use:
>
> decb dskini RSDOSdiskname.vhd -h256
>
>
> As far as I know, there is no cmd that creates a "dual partitioned" vhd (OS9,RSDOS), so you have do both of the above, then use:
>
> cat OS9diskname.vhd RSDOSdiskname.vhd >DUALdiskname.vhd
> (notice, OS9 comes first)
>
> All but "cat" are in the ToolShed bundle. If using Linux, then you should have cat. Is using Windows, I suggest using MinGW and then "cat" will be present from the cmd line.
>
> The ToolShed manual explains all this pretty well, but cat is part of Linux or MinGW and is just the "merge" cmd.
>
>
>
>
> 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: Mathieu Chouinard <chouimat at gmail.com>
> To: CoCoList for Color Computer Enthusiasts <coco at maltedmedia.com>
> Sent: Fri, Oct 16, 2015 1:05 pm
> Subject: Re: [Coco] Hard disk image
>
>
> I have it working with the Master330.dsk
> via drivewire. Now I just need to
> figure out
> how to build a hdd image. if I just need to have
> boot floppies for my
> various use case. so be it
>
> Speaking of hdd image, what is the maximum
> size?
> Mathieu
>
> On Fri, Oct 16, 2015 at 1:01 PM, David Ladd
> <davidwladd at gmail.com> wrote:
>> The CoCo3FPGA version that has the serial port
> should be able to use the
>> Becker HDBDOS and the Becker based DriveWire image.
> As I do not have a
>> CoCo3FPGA board I can not confirm this, but the Becker port
> was originally
>> developed on the CoCo3FPGA project and that was the reason the
> support for
>> this interface was requested on VCC, xroar, and MESS.
>>
>>
> +----------+
>> |David Ladd|
>> +----------+
>>
>>
>>
>>
>> On Fri, Oct 16, 2015 at
> 11:28 AM, Barry Nelson <
>> barry.nelson at amobiledevice.com> wrote:
>>
>>> Ok, well
> now, that is at least two different bootable images, if not
>>> three. VCC can
> boot from a DriveWire server using the Becker Port, or from
>>> an image directly
> using the Emu Disk driver. The CoCo3FPGA boots from
>>> DriveWire, not sure about
> the specifics though. The CoCoSDC uses it's own
>>> boot track, and is unique. I
> have boot disk images for the CoCoSDC, Emu
>>> Disk, and DriveWire.
>>> A Becker
> Port image is available here:
>>>
> http://nitros9.sourceforge.net/latest/nos96809l2v030300coco3_becker.dsk
>>> A
> regular DriveWire image is here:
>>>
> http://nitros9.sourceforge.net/latest/nos96809l2v030300coco3_dw.dsk
>>> A CoCoSDC
> image for a physical CoCo3 is here:
>>>
> http://nitros9.sourceforge.net/latest/nos96809l2v030300coco3_cocosdc.dsk
>>> I
> can send you an Emu Disk bootable image for VCC without DriveWire if you
>>> want
> that.
>>>
>>> > Mathieu Chouinard chouimat at gmail.com
>>> > Fri Oct 16 10:22:30
> EDT 2015
>>> > Hi,
>>> > I'm trying to build a bootable nitros-9 hard disk image,
> that could be
>>> > used with Vcc 2.0.1, cocosdc and the coco3fpga. Anybody has
> some
>>> > instructions on how to do it?
>>> >
>>> > Mathieu
>>> >
>>> > --
>>> > A te
> quaeso, sicut in Aeneidos libro quarto Aeneas, elocutus
>>> > desiderium erigendi
> suum obeliscum in templo Venereo Didonis, ab ea
>>> > quaesivit, tuae domi an
> meae?
>>>
>>>
>>> --
>>> Coco mailing list
>>> Coco at maltedmedia.com
>>>
> https://pairlist5.pair.net/mailman/listinfo/coco
>>>
>>
>> --
>> Coco mailing list
>>
> Coco at maltedmedia.com
>> https://pairlist5.pair.net/mailman/listinfo/coco
>
>
>
> --
> A
> te quaeso, sicut in Aeneidos libro quarto Aeneas, elocutus
> desiderium erigendi
> suum obeliscum in templo Venereo Didonis, ab ea
> quaesivit, tuae domi an
> meae?
>
> --
> Coco mailing
> list
> Coco at maltedmedia.com
> https://pairlist5.pair.net/mailman/listinfo/coco
>
>
>
> --
> Coco mailing list
> Coco at maltedmedia.com
> https://pairlist5.pair.net/mailman/listinfo/coco

-- 
A te quaeso, sicut in Aeneidos libro quarto Aeneas, elocutus
desiderium erigendi suum obeliscum in templo Venereo Didonis, ab ea
quaesivit, tuae domi an meae?