[Coco] wdir command? A FIX

Bill Pierce ooogalapasooo at aol.com
Thu Feb 4 20:01:20 EST 2016

Robert, you are correct as usual.... BUT... you made a mistake.
The next-to-the-last change "xxlonglinexx count=4" and "xxlonglinexx count=5" are backwards. The "new" should be the "original".

After making that change, it work perfectly. Now to make the same mods to the C code. The only thing I missed in my attempt was the above "count" change which apparently was making it go off into lala land :-)



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
Co-Contributor, Co-Editor for CocoPedia
Global Moderator for TRS-80/Tandy Color Computer Forums

E-Mail: ooogalapasooo at aol.com



-----Original Message-----
From: Robert Gault <robert.gault at att.net>
To: CoCoList for Color Computer Enthusiasts <coco at maltedmedia.com>
Sent: Thu, Feb 4, 2016 6:06 pm
Subject: Re: [Coco] wdir command? A FIX

Bill Pierce via Coco wrote:> Chis & Robert, I've even tried editing both Kevin's Basic09 and McDowell's C versions of wdir to use NitrOS9... No luck so far. >Just changing the "cc3io" reference to "vtio" should have done the trick (theoretically), but apparently, in the splitting of >cc3io into the vtio, keydrv snddrv, & joydrv, this may have made the system calls that are used in wdir to react differently. >I may compare the system calls used with those I use in enumerating the RBF drives in Mshell to see if maybe a new util with >the same function of wdir could be written for NitrOS9. It would actually be usefull to me as (from what I saw in both sources) >it not only displays the windows in use, but window type, the palette settings, the color settings, the overlays, as well as the >CWArea (current work area) assigned to each window.> In the kind of projects I work on, this is good stuff to know :-)>> Bill PierceOK, I think I've managed to edit Kevin's program so that it works with NitrOS-9 Level2. Since I already posted the original code, I'll just post the required changes.originalTYPE table=V_Driv,V_Stat,V_Desc,V_FMgr:INTEGER; V_Usrs:BYTEnewTYPE table=V_Driv,V_Stat,V_Desc,V_FMgr:INTEGER; V_Usrs:BYTE; V_DriveEx, V_FMgrEx:INTEGERoriginalDIM DrvName:STRING[5]newDIM DrvName:STRING[4]originalDIM cc3io:STRING[5]newDIM vtio:STRING[4]originalcc3io="CC3I"+CHR$($CF)newvtio="VTI"+CHR$($CF)originalREM Check Each Device Entry for CC3IO Driver.new cosmeticREM Check Each Device Entry for VTIO Driver.original check COUNTREM And Then the Name Itself:destination=ADDR(DrvName)offset=M_Name+devtable(DE).V_Drivcount=4newREM And Then the Name Itself:destination=ADDR(DrvName)offset=M_Name+devtable(DE).V_Drivcount=5originalIF DrvName=cc3io THENnewIF DrvName=vtio THENRobert-- Coco mailing listCoco at maltedmedia.comhttps://pairlist5.pair.net/mailman/listinfo/coco

More information about the Coco mailing list