[Coco] Now using VCC as well as MESS

Bill Pierce ooogalapasooo at aol.com
Mon Oct 7 16:37:45 EDT 2013 

Aaron, I think Boisy was making things more "neutral" to all the different systems. It's the only thing I can figure. I just wished he would've finished it. Here's some of the changes (the dw ones at least):

rbdw3.dr = rgdw.dr
dw3.sb = dwio.sb
scdwn.dr = scdwv.dr
and all descriptors referring to scdwn, now refer to scdwv (in name and internally)

The names actually make sense... but wreck havoc on those of us who have built up our HDs with dirs for making custom boots and custom bootlists and scripts. You just about have to trash 'em and start over.

Bill Pierce
My Music from the Tandy/Radio Shack Color Computer 2 & 3
https://sites.google.com/site/dabarnstudio/
Co-Webmaster of The TRS-80 Color Computer Archive
http://www.colorcomputerarchive.com/
Co-Contributor, Co-Editor for CocoPedia
http://www.cocopedia.com/wiki/index.php/Main_Page
E-Mail: ooogalapasooo at aol.com




-----Original Message-----
From: Aaron Wolfe <aawolfe at gmail.com>
To: CoCoList for Color Computer Enthusiasts <coco at maltedmedia.com>
Sent: Mon, Oct 7, 2013 4:21 pm
Subject: Re: [Coco] Now using VCC as well as MESS


Sorry, I don't think I was involved in the name changes in NitrOS9 so
I can't explain that part.  Probably just an effort to clean
up/standardize.  I would suggest throwing away any old disk you got
from me and using the nightly OS9 disks so that you're in sync with
everybody else.


On Mon, Oct 7, 2013 at 4:02 PM, Wayne Campbell <asa.rand at gmail.com> wrote:
> Thanks for the response, Bill. I understand what you are saying. I found
> the scdwn files on the disk Aaron made for me. Problem is, the n_scdwn.dd
> descriptor is missing. I may need Aaron to answer this, but, is the only
> difference between the scdwv and scdwn versions the name of the file? In
> other words, if I copy the n_scdwv.dd descriptor and rename it to
> n_scdwn.dd, will it work?
>
> Wayne
>
>
>
>
> On Mon, Oct 7, 2013 at 12:49 PM, Bill Pierce <ooogalapasooo at aol.com> wrote:
>
>>
>> Wayne
>> This is an issue that needs to be worked on in the nitros9 repository.
>> Some of the modules have been renamed, dw modules in particular (?WHY?). I
>> think the problem in making a boot from the NITROS9 dir on the distro disks
>> is that the bootlists and scripts have not been updated to reflect the name
>> changes. Also there are modules listed in the bootlist that are not in
>> their directories (or any where else on the disk). A good example is the
>> bootlist has "emudsk.dr", "h0.dd", and "dd_h0.dd" listed nut they are not
>> in the RBF directory. There are some others as well. Most of those missing
>> modules are being built in the repo, but are not being copied to the disks.
>>
>> First, build your boot from the disk the modules came from. Do not mix
>> modules from different builds. The 6309 becker disk you just downloaded is
>> the one you should be building a boot from.
>> 2nd, the "dw" command has nothing to do with "normal" drivewire
>> operations. You can read/write to/from disks, use dw4midi, print to the
>> virtual printer "/p" etc.
>> The "dw" command is for "directly" accessing dw to set parameters without
>> leaving the Coco. To use this command, you must know the protocol of the dw
>> cmd set.
>>
>> Just typing dw<enter> will get the following:
>>
>> Possible commands:
>> config    disk      instance  log       midi      net
>> port      server
>>
>> typing dw server<enter> will get:
>>
>> Possible commands:
>> dir        help       list       print      show       status     terminate
>> turbo
>>
>> Typing dw server dir<enter> will get you:
>>
>> Error 10: dw server dir requires a URI or path as an argument
>>
>> BUT.. typing dw server dir C:/users  <enter> (in my windows) will get you;
>>
>> Directory of file:///c:/users
>> All Users     Default       Default User  desktop.ini   Galapas
>> Public
>>
>> Which is mu C;/users directory on my PC :-)
>>
>> If a "dw" error tells you it needs a "URI" or "path" it is usually
>> referring to an FTP address or PC pathname (not Coco). Yes, if DW4 is
>> connected to the net, it will list the contents of an FTP. And yes, your
>> Coco can read you PC's directories and files.
>> NOTE: the FTP address IS case sensitive.
>>
>> Just try "dw server dir ftp://os9archives.rtsi.com/RSDOS/" <enter>
>> (internet connection to PC required)
>> You'll have to be patient, as this one will take a while. It'll look like
>> it's doing nothing, but it will finally list.
>>
>> "scdwn" HAS been renamed to "scdwv" so you have the driver. you'll most
>> likely have to change THAT in the bootlist too. As well as THIS:
>> The "14th" "/N" descriptor is named "/MIDI" and is used for... ummm...
>> errr.... Midi.
>>
>> Bill Pierce
>> My Music from the Tandy/Radio Shack Color Computer 2 & 3
>> https://sites.google.com/site/dabarnstudio/
>> Co-Webmaster of The TRS-80 Color Computer Archive
>> http://www.colorcomputerarchive.com/
>> 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, Oct 7, 2013 1:41 pm
>> Subject: Re: [Coco] Now using VCC as well as MESS
>>
>>
>> Well, it seems I am having an issue whether or not I want one. It turns out
>> the disk Aaron made me included the dw3 driver and descriptors in the
>> modules directory, but the bootfile did not have them. I made a custom boot
>> file. There is a entry in the bootlist that shows RBF/dw3,sc that does not
>> exist in that directory. I'm not sure what that module does, but I could
>> not include it. In VCC 142 the new bootdisk boots fine, and a mdir shows
>> the dw3 driver and x0-x3 descriptors. However, in VCC 143 I get the
>> following screen as soon as I type DOS and press [ENTER]. Can someone help
>> me determine what is going on here? Oh, and I did set the bitbanger in 143
>> to use the Becker interface, and I have dw4 installed and running. I never
>> get past the boot.
>>
>> cococoding.com/wayne/vcc_window.PNG
>>
>> Wayne
>>
>>
>>
>> On Mon, Oct 7, 2013 at 9:38 AM, Wayne Campbell <asa.rand at gmail.com> wrote:
>>
>> > Thanks, Tom. I now have both VCC sites bookmarked.
>> >
>> > I have DW4 installed, as well as VCC 1.4.3. I will be testing things
>> > today, and I'll post what I discover here. I am hoping I will have no
>> > issues, but if a few occur I consider that part of the learning curve.
>> >
>> > Thanks Bill for the help you have given.
>> >
>> > Wayne
>> >
>> >
>> >
>> > On Mon, Oct 7, 2013 at 8:49 AM, Tom Seagrove <tjseagrove at writeme.com
>> >wrote:
>> >
>> >> http://vcc.cococoding.com
>> >>
>> >> On Oct 7, 2013, at 11:35 AM, Wayne Campbell <asa.rand at gmail.com> wrote:
>> >>
>> >> I have been searching for vcc143.zip but cannot locate it on the
>> internet.
>> >> Someone please provide the url?
>> >>
>> >> Wayne
>> >>
>> >>
>> >>
>> >> On Sat, Oct 5, 2013 at 8:37 PM, Bill Pierce <ooogalapasooo at aol.com>
>> >> wrote:
>> >>
>> >> >
>> >> > Chad... not the "headless" disks. Just the one's ending  in becker.The
>> >> > headless disks are for running a Coco from a remote... they have no
>> >> display
>> >> > drivers
>> >> >
>> >> > Bill Pierce
>> >> > My Music from the Tandy/Radio Shack Color Computer 2 & 3
>> >> > https://sites.google.com/site/dabarnstudio/
>> >> > Co-Webmaster of The TRS-80 Color Computer Archive
>> >> > http://www.colorcomputerarchive.com/
>> >> > 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: Sat, Oct 5, 2013 11:27 pm
>> >> > Subject: Re: [Coco] Now using VCC as well as MESS
>> >> >
>> >> >
>> >> > I still thank you for the response anyway, Bill. :)
>> >> >
>> >> > I will be looking at it more closely tomorrow. I already found out
>> today
>> >> > that 1.4.2 is not the correct version for use with the Becker port. I
>> >> found
>> >> > the 1.4.3 beta earlier. I will download it tomorrow. I also found all
>> >> the
>> >> > vhd images of NOS9 L1/2/6809/6309/becker/beckerheadless. What I really
>> >> need
>> >> > to know is, is there something on those images not found on the image
>> I
>> >> > have?
>> >> >
>> >> > Wayne
>> >> > On Oct 5, 2013 11:11 PM, "Bill Pierce" <ooogalapasooo at aol.com> wrote:
>> >> >
>> >> >>
>> >> >> Chad, this sounds like (from both threads), that you don't even need
>> >> >> hdbdos but you need dwdos which allows most of what you want. I
>> haven't
>> >> >> used it so I can't tell you how, but the docs are "supposed" to be on
>> >> >> cloud9 and the zip for hdbdos there contains the dwdos files.
>> >> >>
>> >> >> Bill Pierce
>> >> >> My Music from the Tandy/Radio Shack Color Computer 2 & 3
>> >> >> https://sites.google.com/site/dabarnstudio/
>> >> >> Co-Webmaster of The TRS-80 Color Computer Archive
>> >> >> http://www.colorcomputerarchive.com/
>> >> >> 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: Sat, Oct 5, 2013 10:45 pm
>> >> >> Subject: Re: [Coco] Now using VCC as well as MESS
>> >> >>
>> >> >>
>> >> >> Thanks, Bill. Now the 6809$ question... do I have to use HDBDOS, or
>> >> can I
>> >> >> do this with just NitrOS9? I don't use HDBDOS because I don't use
>> >> > RS-DOS. I
>> >> >> am strictly a OS9 user.
>> >> >>
>> >> >> When I was attempting to help Aaron document DriveWire4 back in
>> 09-10,
>> >> he
>> >> >> helped me setup the NOS9 boot floppy I use now. It has dw built in.
>> I'm
>> >> > not
>> >> >> sure if that was dw3 or dw4, but I do have the driver and descriptors
>> >> in
>> >> > my
>> >> >> boot file.
>> >> >>
>> >> >> Wayne
>> >> >> On Oct 5, 2013 10:33 PM, "Bill Pierce" <ooogalapasooo at aol.com>
>> wrote:
>> >> >>
>> >> >>>
>> >> >>> Wayne, in the VCC 1.4.3beta zip, there a small text file. It
>> explains
>> >> >> most
>> >> >>> of what needs to be done to set up the becker port. DW4 "should"
>> give
>> >> > you
>> >> >>> the telnet capabilities you want. That's one aspect of DW I've yet
>> to
>> >> >>> explore, but will soon have to.
>> >> >>> The only thing is the current hdbdos does not support the becker
>> port
>> >> >>> functions other than disk access unless you use ML to access the
>> >> >> read/write
>> >> >>> routines directly and know the dw protocol.
>> >> >>>
>> >> >>> To enable the becker port in VCC 1.4.3b:
>> >> >>> In "Configuration"/"Config"/"Bitbanger" you must check "Enable
>> Becker
>> >> >> Port"
>> >> >>> These next ones should be set but always good to check
>> >> >>> IP Address of DriveWire server = 127.0.01
>> >> >>> TCP port = 65504
>> >> >>>
>> >> >>> In "Cartridge"/"FD-502 Config"
>> >> >>> "Dos Image"/ check "External Rom Image"
>> >> >>> "External Rom Image" (at bottom)
>> >> >>> Click browse, go to the VCC dir, and select the "hdbdwbc3.rom" not
>> the
>> >> >>> "hdbdwbck.rom". That one's for running time critical games & Coco 2
>> >> >> (XRoar).
>> >> >>>
>> >> >>> Start DW4  server on your PC, do the "Simple Configuration Wizard"
>> >> > select
>> >> >>> "Emulator or other TCP/IP". click next and leave all else at the
>> >> >> defaults.
>> >> >>> Inset a disk in slot 0.
>> >> >>> Now in VCC, hit "F9" twice (cold start)
>> >> >>> You should be in hdbdos and have dw4 access.
>> >> >>> If you're using partitioned VHDs, then you need to set your offsets.
>> >> >>> Note: In this mode, you lose the VCC default VHD in hdbdos, But you
>> >> can
>> >> >>> gain it back in Nitros9 with the emudsk drivers installed in your
>> >> > becker
>> >> >>> boot.
>> >> >>>
>> >> >>> Bill Pierce
>> >> >>> My Music from the Tandy/Radio Shack Color Computer 2 & 3
>> >> >>> https://sites.google.com/site/dabarnstudio/
>> >> >>> Co-Webmaster of The TRS-80 Color Computer Archive
>> >> >>> http://www.colorcomputerarchive.com/
>> >> >>> 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: coco <coco at maltedmedia.com>
>> >> >>> Sent: Sat, Oct 5, 2013 9:26 pm
>> >> >>> Subject: [Coco] Now using VCC as well as MESS
>> >> >>>
>> >> >>>
>> >> >>> I decided today was the day to see if VCC would run on this PC. I
>> >> > started
>> >> >>> using MESS 1.36b on my laptop because VCC wouldn't even launch on
>> it.
>> >> >> This
>> >> >>> computer is different hardware, but the same XP Pro I installed on
>> the
>> >> >>> laptop. I figured the hardware difference could do the trick, and I
>> >> was
>> >> >>> right.
>> >> >>>
>> >> >>> Instead of downloading the 3.2.8 vhd image on the site, I set the
>> >> > FD-502
>> >> >>> drive 0 to my 80-track boot floppy image, and the HD drive 0 to my
>> vhd
>> >> >>> image. I set the keyboard to OS9 mapping and started the emulation.
>> It
>> >> >>> worked flawlessly.
>> >> >>>
>> >> >>> I am wanting to see if I can get the Becker port working, but
>> there's
>> >> >>> nothing in the emulation help about it, and nothing in the way of
>> >> > options
>> >> >>> in the config or devices menus.
>> >> >>>
>> >> >>> I will research that more tomorrow. My question is, will I be able
>> to
>> >> > use
>> >> >>> the Becker port as a way to telnet to another location, such as
>> IRC. I
>> >> > am
>> >> >>> (not at this moment) writing a IRC client, and being able to telnet
>> >> >> through
>> >> >>> the Becker port would allow me to test the software locally.
>> >> >>>
>> >> >>> Wayne
>> >> >>>
>> >> >>> --
>> >> >>> 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
>> >>
>> >>
>> >>
>> >> --
>> >> The Structure of I-Code
>> >> http://www.cocopedia.com/wiki/index.php/The_Structure_of_I-Code
>> >>
>> >> decode
>> >> http://cococoding.com/wayne/
>> >>
>> >> --
>> >> 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
>> >>
>> >
>> >
>> >
>> > --
>> > The Structure of I-Code
>> > http://www.cocopedia.com/wiki/index.php/The_Structure_of_I-Code
>> >
>> > decode
>> > http://cococoding.com/wayne/
>> >
>>
>>
>>
>> --
>> The Structure of I-Code
>> http://www.cocopedia.com/wiki/index.php/The_Structure_of_I-Code
>>
>> decode
>> http://cococoding.com/wayne/
>>
>> --
>> 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
>>
>
>
>
> --
> The Structure of I-Code
> http://www.cocopedia.com/wiki/index.php/The_Structure_of_I-Code
>
> decode
> http://cococoding.com/wayne/
>
> --
> 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

More information about the Coco mailing list