[Coco] Problem with dw command

[Fred D. Provoncha]

I apologize that I haven't been clearer about what I'm trying to accomplish. A couple of weeks ago I successfully created a NitrOS9 boot disk using the scripts on the most recent nos96809L2v030300coco3_dw.dsk image. The boot disk I created is a 35 track, SSDD disk that resides on Drive 255 of HDB-DOS and boots NitrOS9 entirely from my hard drive. It worked well, but didn't include Drivewire drivers & descriptors. I'm trying to add them so I can access virtual drives on my PC, to facilitate transfer of files from the PC to my Coco. I don't actually need to boot from Drivewire. So now I'm trying to create a new boot disk using the scripts from the aforementioned disk image, with additional modules added from that disk so I can access Drivewire using the DW command. I succeeded in adding rbdw, dwio, x0, & x1, enabling me to access the x0 & x1 drives, but I found I still couldn't use the DW command from NitrOS9. I inquired here on the List, and you suggested that I add scdwv, n, & n1, which I added successfully, and it worked! Thank you! But it only worked because I removed a couple modules from the bootfile, notably KrnP3. I found that if I didn't remove something, then not all the modules in the boot file successfully loaded during the boot process. The last few modules failed to load (notably the Clock modules), which caused the computer to hang or crash during bootup. When I removed Krnp3 & a couple other modules I deemed nonessential, the system booted successfully. So there appears to be a "limit" to how large my bootfile can be.
I did another test today. Using the same disk image, and using the same scripts from that image, I constructed a boot disk containing the following modules:krnp2krnp3_perriomaninitrbf.mnrbdw.drdwio.sbx0.ddx1.ddrbsuper.drlltc3.drdds0_tc3.ddsh_tc3.ddrb1773.drd0_80d.ddd1_80d.ddscf.mnvtio.drkeydrv_cc3.sbsnddrv_cc3.sbjoydrv_joy.sbcowin.ioterm_win80.dtv1.dwscdwp.drn_scdwv.ddn1_scdwv.ddvrn.drvi.ddftdd.ddpipeman.mnpiper.drpipe.ddclock_60hzclock2_cloud9w.dww1.dww2.dww3.dww4.dww5.dww6.dww7.dww8.dww9.dwI copied the boot disk (35T SSDD) to Drive 255 of HDB-DOS, then attempted to boot. I got the following on the boot screen:
KREL Boot Krn tb0......................................................................................................................bKrnP2 KrnP3 IOMan Init RBF rbdw dwio X0 X1 RBSuper lltc3 DD SH rb1773 D0 D1 SCF VTIO KeyDrv SndDrv JoyDrv CoWin CoVDG i2xo*]
NITROS9 BOOT FAILED
So for some reason the system quit loading modules after CoVDG. I figure it must've reached some sort of limit.
Fred ProvonchaStansbury Park, UT
 

     On Wednesday, February 18, 2015 7:22 AM, Bill Pierce <ooogalapasooo at aol.com> wrote:
   

 Fred, if you use the current Nitros9 distro dsk image that is set up for Drivewire, everything is already included. These are the disks with names ending in "_dw", such asnos96809L2v030300coco3_dw.dskThese are stocked with all the drivers and descriptors needed for Drivewire.I usually start with one of these dsk images and build my boot from there. That way, all I have to add is the optional things I need.The dw disk comes with the standard floppy descriptors (wd1773, d0, d1) which I don't use (floppies all dead), so I eliminate the floppy driver and descs then add my ramdisk and IDE hd driver and desc.

If you use an external clock (such as smartwatch or a disto controller with clock), you'll want to change the dw clock to the proper module. You only change the 2nd clock module of the 2.

BTW... What have you got in your boot to make it so large that you have to "shoehorn" in something new? I have a fairly large boot and have no problems at all.Here's my bootlist on my Coco 3:RELBootKrnKrnP2IOManInitRBFrbdwdwioX0X1X2X3RBSuperllideDDI0I1RAMR0SCFVTIOKeyDrvJoyDrvSndDrvCoWinTermWW1W2W3W4W5W6W7scdwvNN1N2N3N4MIDIZ1Z2scdwpPPipeManPiperPipeClockClock2

Then bootup loads shell & grfdrv.
And before, I even had the floppy driver and descr. I've had no problems running software or during software developemnt using the C compiler system. Bill Pierce"Today is a good day... I woke up" - Ritchie Havens 
My Music from the Tandy/Radio Shack Color Computer 2 & 3https://sites.google.com/site/dabarnstudio/Co-Contributor, Co-Editor for CocoPediahttp://www.cocopedia.com/wiki/index.php/Main_PageE-Mail: ooogalapasooo at aol.com
  -----Original Message-----
From: Fred D. Provoncha via Coco <coco at maltedmedia.com>
To: coco <coco at maltedmedia.com>
Sent: Wed, Feb 18, 2015 2:04 am
Subject: Re: [Coco] Problem with dw command

Original Message:>Date: Tue, 17 Feb 2015 10:03:58 -0500
>From: Aaron Wolfe <aawolfe at gmail.com>
>It's a good idea to use one of the premade stock NitrOS9 disks or to build
>your own from the current NitrOS9 source.  There are many bug fixes in many
>parts of the latest NitrOS9 release and depending on how old a system
>you're shoehorning things into, they might not be fixed on your system,
>potentially leading to all kinds of strange and hard to track down issues.
>If you must update an existing disk, it would be best to update everything,
>not just stick currently DW modules into an old system (I don't mean to
>assume this is what happened in this case, just general advice)
Thanks for the advice Aaron! Actually, yes, I have been using the most-recent 
premade stock NitrOS9 disks from Sourceforge. I'm customizing them using the 
included scripts, just trying to add more functionality to my system, using the 
most recent modules from the latest release.
Thanks,Fred ProvonchaStansbury Park, UT

-- 
Coco mailing list
Coco at maltedmedia.com
https://pairlist5.pair.net/mailman/listinfo/coco