[Coco] I've got DriveWire 4 installed

[Wayne Campbell]

Before I setup DW, I was booting from a floppy and then transferring
control to the vhd. My OS9Boot file looks like this:

Header for:  KrnP2
Module size: $0C1B    #3099
Module CRC:  $DC8FA7 (Good)
Hdr parity:  $E9
Edition:     $12      #18
Ty/La At/Rv: $C0 $86
System mod, Data, re-en, R/O

Header for:  IOMan
Module size: $0916    #2326
Module CRC:  $4C82AC (Good)
Hdr parity:  $E3
Edition:     $0D      #13
Ty/La At/Rv: $C1 $85
System mod, 6809 obj, re-en, R/O

Header for:  Init
Module size: $0077    #119
Module CRC:  $6BB345 (Good)
Hdr parity:  $A8
Edition:     $01      #1
Ty/La At/Rv: $C0 $80
System mod, Data, re-en, R/O

Header for:  RBF
Module size: $128F    #4751
Module CRC:  $FF54C3 (Good)
Hdr parity:  $71
Edition:     $25      #37
Ty/La At/Rv: $D7 $83
File Man mod, 6309 obj, re-en, R/O

Header for:  rb1773
Module size: $054E    #1358
Module CRC:  $6809E7 (Good)
Hdr parity:  $90
Exec. off:   $00CC    #204
Data Size:   $00BD    #189
Edition:     $01      #1
Ty/La At/Rv: $E1 $81
Dev Dvr mod, 6809 obj, re-en, R/O

Header for:  D0
Module size: $002F    #47
Module CRC:  $045CD6 (Good)
Hdr parity:  $CA
Edition:     $52      #82
Ty/La At/Rv: $F1 $80
Dev Dsc mod, 6809 obj, re-en, R/O

Header for:  D1
Module size: $002F    #47
Module CRC:  $803FAD (Good)
Hdr parity:  $CA
Edition:     $52      #82
Ty/La At/Rv: $F1 $80
Dev Dsc mod, 6809 obj, re-en, R/O

Header for:  D2
Module size: $002F    #47
Module CRC:  $BF6E4C (Good)
Hdr parity:  $CA
Edition:     $52      #82
Ty/La At/Rv: $F1 $80
Dev Dsc mod, 6809 obj, re-en, R/O

Header for:  EmuDsk
Module size: $00BC    #188
Module CRC:  $85815B (Good)
Hdr parity:  $66
Exec. off:   $0021    #33
Data Size:   $00FF    #255
Edition:     $01      #1
Ty/La At/Rv: $E1 $81
Dev Dvr mod, 6809 obj, re-en, R/O

Header for:  DD
Module size: $002F    #47
Module CRC:  $BDBB72 (Good)
Hdr parity:  $CB
Edition:     $52      #82
Ty/La At/Rv: $F1 $81
Dev Dsc mod, 6809 obj, re-en, R/O

Header for:  H0
Module size: $002F    #47
Module CRC:  $BE79DA (Good)
Hdr parity:  $CB
Edition:     $52      #82
Ty/La At/Rv: $F1 $81
Dev Dsc mod, 6809 obj, re-en, R/O

Header for:  SCF
Module size: $077D    #1917
Module CRC:  $88EE58 (Good)
Hdr parity:  $93
Edition:     $11      #17
Ty/La At/Rv: $D1 $80
File Man mod, 6809 obj, re-en, R/O

Header for:  VTIO
Module size: $093F    #2367
Module CRC:  $8E884F (Good)
Hdr parity:  $EC
Exec. off:   $0013    #19
Data Size:   $0100    #256
Edition:     $02      #2
Ty/La At/Rv: $E1 $80
Dev Dvr mod, 6809 obj, re-en, R/O

Header for:  KeyDrv
Module size: $024A    #586
Module CRC:  $518799 (Good)
Hdr parity:  $B1
Edition:     $04      #4
Ty/La At/Rv: $C1 $80
System mod, 6809 obj, re-en, R/O

Header for:  SndDrv
Module size: $00C0    #192
Module CRC:  $334815 (Good)
Hdr parity:  $39
Edition:     $03      #3
Ty/La At/Rv: $C1 $80
System mod, 6809 obj, re-en, R/O

Header for:  JoyDrv
Module size: $0199    #409
Module CRC:  $13C173 (Good)
Hdr parity:  $61
Edition:     $07      #7
Ty/La At/Rv: $C1 $80
System mod, 6809 obj, re-en, R/O

Header for:  CoWin
Module size: $1D27    #7463
Module CRC:  $216153 (Good)
Hdr parity:  $C3
Edition:     $02      #2
Ty/La At/Rv: $C1 $80
System mod, 6809 obj, re-en, R/O

Header for:  Term
Module size: $0044    #68
Module CRC:  $012B5D (Good)
Hdr parity:  $B6
Edition:     $53      #83
Ty/La At/Rv: $F1 $80
Dev Dsc mod, 6809 obj, re-en, R/O

Header for:  W
Module size: $0041    #65
Module CRC:  $3B6153 (Good)
Hdr parity:  $B3
Edition:     $53      #83
Ty/La At/Rv: $F1 $80
Dev Dsc mod, 6809 obj, re-en, R/O

Header for:  W1
Module size: $0042    #66
Module CRC:  $A9B825 (Good)
Hdr parity:  $B0
Edition:     $53      #83
Ty/La At/Rv: $F1 $80
Dev Dsc mod, 6809 obj, re-en, R/O

Header for:  W2
Module size: $0042    #66
Module CRC:  $6A4A21 (Good)
Hdr parity:  $B0
Edition:     $53      #83
Ty/La At/Rv: $F1 $80
Dev Dsc mod, 6809 obj, re-en, R/O

Header for:  W3
Module size: $0042    #66
Module CRC:  $4820E4 (Good)
Hdr parity:  $B0
Edition:     $53      #83
Ty/La At/Rv: $F1 $80
Dev Dsc mod, 6809 obj, re-en, R/O

Header for:  W4
Module size: $0042    #66
Module CRC:  $EDD571 (Good)
Hdr parity:  $B0
Edition:     $53      #83
Ty/La At/Rv: $F1 $80
Dev Dsc mod, 6809 obj, re-en, R/O

Header for:  W5
Module size: $0042    #66
Module CRC:  $2085DE (Good)
Hdr parity:  $B0
Edition:     $53      #83
Ty/La At/Rv: $F1 $80
Dev Dsc mod, 6809 obj, re-en, R/O

Header for:  W6
Module size: $0042    #66
Module CRC:  $BE6732 (Good)
Hdr parity:  $B0
Edition:     $53      #83
Ty/La At/Rv: $F1 $80
Dev Dsc mod, 6809 obj, re-en, R/O

Header for:  W7
Module size: $0042    #66
Module CRC:  $7CE8AB (Good)
Hdr parity:  $B0
Edition:     $53      #83
Ty/La At/Rv: $F1 $80
Dev Dsc mod, 6809 obj, re-en, R/O

Header for:  W8
Module size: $0042    #66
Module CRC:  $D8A2AB (Good)
Hdr parity:  $B0
Edition:     $53      #83
Ty/La At/Rv: $F1 $80
Dev Dsc mod, 6809 obj, re-en, R/O

Header for:  W9
Module size: $0042    #66
Module CRC:  $355C4D (Good)
Hdr parity:  $B0
Edition:     $53      #83
Ty/La At/Rv: $F1 $80
Dev Dsc mod, 6809 obj, re-en, R/O

Header for:  W10
Module size: $0043    #67
Module CRC:  $EF9F26 (Good)
Hdr parity:  $B1
Edition:     $53      #83
Ty/La At/Rv: $F1 $80
Dev Dsc mod, 6809 obj, re-en, R/O

Header for:  W11
Module size: $0043    #67
Module CRC:  $86F664 (Good)
Hdr parity:  $B1
Edition:     $53      #83
Ty/La At/Rv: $F1 $80
Dev Dsc mod, 6809 obj, re-en, R/O

Header for:  W12
Module size: $0043    #67
Module CRC:  $BF0130 (Good)
Hdr parity:  $B1
Edition:     $53      #83
Ty/La At/Rv: $F1 $80
Dev Dsc mod, 6809 obj, re-en, R/O

Header for:  W13
Module size: $0043    #67
Module CRC:  $D7EA1E (Good)
Hdr parity:  $B1
Edition:     $53      #83
Ty/La At/Rv: $F1 $80
Dev Dsc mod, 6809 obj, re-en, R/O

Header for:  W14
Module size: $0043    #67
Module CRC:  $CE2D25 (Good)
Hdr parity:  $B1
Edition:     $53      #83
Ty/La At/Rv: $F1 $80
Dev Dsc mod, 6809 obj, re-en, R/O

Header for:  W15
Module size: $0043    #67
Module CRC:  $82760E (Good)
Hdr parity:  $B1
Edition:     $53      #83
Ty/La At/Rv: $F1 $80
Dev Dsc mod, 6809 obj, re-en, R/O

Header for:  VRN
Module size: $01FB    #507
Module CRC:  $80060E (Good)
Hdr parity:  $20
Exec. off:   $0012    #18
Data Size:   $00FC    #252
Edition:     $01      #1
Ty/La At/Rv: $E1 $80
Dev Dvr mod, 6809 obj, re-en, R/O

Header for:  VI
Module size: $001F    #31
Module CRC:  $DD55E6 (Good)
Hdr parity:  $C2
Edition:     $01      #1
Ty/La At/Rv: $F1 $80
Dev Dsc mod, 6809 obj, re-en, R/O

Header for:  FTDD
Module size: $0021    #33
Module CRC:  $6F5C22 (Good)
Hdr parity:  $FC
Edition:     $01      #1
Ty/La At/Rv: $F1 $80
Dev Dsc mod, 6809 obj, re-en, R/O

Header for:  PipeMan
Module size: $0253    #595
Module CRC:  $3A6141 (Good)
Hdr parity:  $B8
Edition:     $05      #5
Ty/La At/Rv: $D1 $80
File Man mod, 6809 obj, re-en, R/O

Header for:  Piper
Module size: $0028    #40
Module CRC:  $895C5F (Good)
Hdr parity:  $F2
Exec. off:   $0014    #20
Data Size:   $0006    #6
Edition:     $02      #2
Ty/La At/Rv: $E1 $80
Dev Dvr mod, 6809 obj, re-en, R/O

Header for:  Pipe
Module size: $0026    #38
Module CRC:  $D512FB (Good)
Hdr parity:  $F1
Edition:     $50      #80
Ty/La At/Rv: $F1 $80
Dev Dsc mod, 6809 obj, re-en, R/O

Header for:  Clock
Module size: $0203    #515
Module CRC:  $9FEAFA (Good)
Hdr parity:  $F0
Edition:     $09      #9
Ty/La At/Rv: $C1 $88
System mod, 6809 obj, re-en, R/O

Header for:  Clock2
Module size: $00A0    #160
Module CRC:  $CA949B (Good)
Hdr parity:  $B9
Edition:     $01      #1
Ty/La At/Rv: $21 $80
Subr mod, 6809 obj, re-en, R/O

When I boot, the data and exec dirs are set to /DD and /DD/CMDS and I'm on
the vhd. I would like to do something similar with the DW boot floppy, or
if possible, boot directly from the vhd and still have DW access.


On Mon, May 29, 2017 at 10:12 AM, Bill Pierce via Coco <coco at maltedmedia.com
> wrote:

> Wayne, being an OS9 only vhd will not matter.
> If you plan on booting from the VCC vhd, you will need the "boot_emu" in
> your kernel, that is in the same folder as emudsk in the repo, again, not
> on any disks. If you boot from dw, and /dd is /h0, then grfdrv and shell
> need to be in /dd/cmds and sysgo and startup needs to be in the root of /dd
>
>  I'm not sure how you're booting, so I don't quite know how to tell you to
> set it up.
> Oh, and BTW... it's best to have emudsk and dd (h0) following the dw
> descriptors and before any ramdisk (or scf) in the os9boot.
> It gets kinda tricky when you boot from one disk with the system on
> another.
>
>
>
> 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
>
> E-Mail: ooogalapasooo at aol.com
>
>
>
>
>
> -----Original Message-----
> From: Wayne Campbell <asa.rand at gmail.com>
> To: CoCoList for Color Computer Enthusiasts <coco at maltedmedia.com>
> Sent: Mon, May 29, 2017 12:42 pm
> Subject: Re: [Coco] I've got DriveWire 4 installed
>
> Oh, and FWIW, my vhd is OS-9 only, not hdbdos and OS-9. Will this
> impactusing the dd descriptor for the vhd?On Mon, May 29, 2017 at 9:40 AM,
> Wayne Campbell <asa.rand at gmail.com> wrote:> I remember this from when I
> had my real CoCo2 and 3. It was stated in the> manuals that the boot file
> needed to have everything in it. I just wanted> to see if it worked the way
> Robert described first. Now I need to see if I> can add the emudsk driver
> and descriptors to the boot file, or am I going> to have to create a new
> boot file due to ordering constraints. I haven't> made a custom boot in
> many many moons. Thanks for the reminder, Bill.>>> On Mon, May 29, 2017 at
> 7:01 AM, Bill Pierce via Coco <> coco at maltedmedia.com> wrote:>>> Wayne,
> first, it is never a good idea to load drivers "after" the boot>> file.
> This advise comes from many OS9 users past and present. The OS9>> manual
> even states as much. This meaning loading temp drivers after you've>>
> booted into NitrOS9. Yes, it works, but yes, it can eventually fail. It's>>
> ok for testing or a quick fix for something temporary, but not for
> regular>> use. When OS9 boots, memory is allocated to the drivers and
> their>> descriptors in a permanent location in system memory. When you load
> them>> later instead, these locations are just temp locations in user
> memory and>> can easily be corrupted by other software being loaded. Not to
> mention they>> use much more system memory when loaded later.>> The best
> solution is to have the drivers in the bootfile.>>>> 2nd, the emudsk driver
> is 100 times faster than the DW drivers so I would>> use /h0 as /dd. This
> gives you the fastest system drive possible. I've>> found through tests
> that the "TCP" port in DW4 for emulators is actually>> slower than the
> Serial port transfers used by a real Coco and DW4.>>>> 3rd, the emudsk
> driver and descriptors ARE in the repo under>> "3rdparty/drivers/emudsk".
> If you build your own NitrOS9 disks, these>> drivers are assembled, but NOT
> put on any dsk image. The assembled files>> can be found in the above
> folder after doing a complete build of the>> repository. Hopefully I will
> get a chance soon to create the patches need>> to have the repo build disk
> images for the emulators. This has been needed>> for a very long time.>>>>
> In my "Starter Kits" for VCC & DW4, the VHDs are setup so that the system>>
> starts it's boot from DW4, then finishes on the native VCC HD using /h0
> as>> /dd. This makes VCC the system drive, leaving you 4 data drives which
> can>> be swapped out at will.>> These Starter Kit packages are "turnkey"
> systems in that after>> installation, the only setup required is to mount
> the 2 VHDs (one in DW4,>> on in VCC). NitrOS9 is already setup and ready to
> run.>>>>>>>>>>>> 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>>>>
> E-Mail: ooogalapasooo at aol.com>>>>>>>>>>>> -----Original Message----->>
> From: Wayne Campbell <asa.rand at gmail.com>>> To: CoCoList for Color
> Computer Enthusiasts <coco at maltedmedia.com>>> Sent: Sun, May 28, 2017
> 11:14 pm>> Subject: Re: [Coco] I've got DriveWire 4 installed>>>> Thank you
> Bill, Barry and Robert. I already have the emudsk disk image,>> soI just
> merged the H0.dd and EmuDsk.dr files together and put them in>> theCMDS
> directory on the boot disk in DW. It works, so now I have access>> tothe
> vhd image.On Sun, May 28, 2017 at 6:21 AM, Robert Gault <>>
> robert.gault at att.net> wrote:> Wayne Campbell wrote:>>> Thanks, Robert.>>
> That's done, so now how do I access my harddisk image? I>> did a mdir and>>
> see that /h0 and emudsk are not there. I'm guessing this>> means I have
> to>> build a custom boot?>>>>> Wayne,>> Yes, unfortunately there probably
> aren't>> many default .vhds for mounting> on VCC which will access DW4
> disks nor>> disks for DW4 that once booted have> access to the default VCC
> hard drives.>> So, you will need to build a custom> boot file for
> best/safest access to>> both DW drives and VCC hard drives.>> There is one
> other thing you can try>> which may work but is not the best> approach. :)
> You can merge emudsk and>> h0 into a single file in your CMDS> directory.
> Set the merged file for>> execution ex.> attr VCCvhd e pe> and after
> booting from the DW4 disk, load>> the merged file however it is> named.>
> You should then be able to read the>> OS-9 partition of the .vhd mounted
> on> VCC.>> Now EmuDsk and H0 will not be>> on the nightly build Becker
> disk. You will> need to get those from your VCC>> .vhd or I can send them
> to you. The merged> file will need to be>> transferred to the DW4 boot
> disk.>> I just checked and Bill Pierce at>>>
> https://sites.google.com/site/dabarnstudio/the-color-compute>>>
> r-drivewire4-hdbdos-nitros9-starter-kit> in one of the VCC .vhd drives>>
> should have both the EmuDsk and DW driver> sets installed.>>> Robert>>>
> -->>> Coco mailing list> Coco at maltedmedia.com>
> https://pairlist5.pair.net/mai>> lman/listinfo/coco>-- WayneThe Structure
> of I-Codehttp://>> www.cocopedia.com/wiki/index.php/The_Structure_of_I-
> Codedecodehttp://>> cococoding.com/wayne/-- 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>>>>>> --> Wayne>> The
> Structure of I-Code> http://www.cocopedia.com/wiki/
> index.php/The_Structure_of_I-Code>> decode> http://cococoding.com/wayne/>--
> WayneThe Structure of I-Codehttp://www.cocopedia.com/wiki/index.php/The_
> Structure_of_I-Codedecodehttp://cococoding.com/wayne/-- 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
>



-- 
Wayne

The Structure of I-Code
http://www.cocopedia.com/wiki/index.php/The_Structure_of_I-Code

decode
http://cococoding.com/wayne/