[Coco] becker and VCC1.43beta

Sat Apr 20 04:46:55 EDT 2013

OK,

I have DW4 and VCC talking at the very lowest level. If I click 
Config->Instance Manager, I get a diagalog saying:

TCP Server listening on port 65504
Ready, Client at localhost connected.

What I do *not* have is a bootable Nitros9 disk with becker support.

Now, if I wanted to use a *different* computer to run VCC, would I change 
the IP number from 127.0.0.1 to whatever the client computer is, e.g. 
192.168.1.4 in both DW4 and VCC?

@Gene, I'm using whatever Boot module is precompiled into the .dsk image 
nos96309l2v030209coco3_becker.dsk
I'm fairly sure that all the necessary modules are the correct ones to use 
in a becker setup. (of course, I could be wrong)

Regards, Bob Devries
Dalby, QLD, Australia

----- Original Message ----- 
From: "Aaron Wolfe" <aawolfe at gmail.com>
To: "CoCoList for Color Computer Enthusiasts" <coco at maltedmedia.com>
Sent: Saturday, April 20, 2013 4:12 AM
Subject: Re: [Coco] becker and VCC1.43beta

> On Apr 19, 2013 5:06 AM, "Bob Devries" <devries.bob at gmail.com> wrote:
>>
>> Hello, Aaron.
>>
>> Well, I did the config wizard in DW4, and also set up the becker port in
> VCC.
>> VCC responds correctly, with DW ConnOK, and then R 00.0 W 00.0 (thos
> characters are SOOO small).
>>
>> If I try to select the server in DW5, it presents me with 
>> 127.0.0.1:65504,
> so that part is correct, but
>
> Actually that is incorrect and the source of your trouble.
>
> The server you want to select is 127.0.0.1:6800 (the default)
>
> If choosing this does not solve the problem, please just delete the DW
> installation you have now and start fresh with the instructions in my last
> email... I'm afraid too much has changed in your install for me to be sure
> what is happening.
>
>>
>> The file nos96309l2v030209coco3_becker.dsk will not boot in VCC. It reads
> the boot track "KREL Boot Krn tb" then hangs, or sometimes adds *m. This
> happens whether or not DW4 is running.
>>
>> I'm sure I'm still doing something wrong.....
>>
>>
>> Regards, Bob Devries
>> Dalby, QLD, Australia
>>
>> ----- Original Message ----- From: "Aaron Wolfe" <aawolfe at gmail.com>
>> To: "CoCoList for Color Computer Enthusiasts" <coco at maltedmedia.com>
>> Sent: Friday, April 19, 2013 4:16 PM
>> Subject: Re: [Coco] becker and VCC1.43beta
>>
>>
>>
>>> On Apr 19, 2013 1:54 AM, "Bob Devries" <devries.bob at gmail.com> wrote:
>>>>
>>>>
>>>> Hello all.
>>>>
>>>> Well, I hate to admit it, but I can't get the becker part of VCC
> working.
>>>>
>>>> Is there anyone in a position to give a detailed HOW-TO on what goes
>>>
>>> where in both VCC and DW4?
>>>>
>>>>
>>>> My DW4 has DriveWire - 127.0.0.1:6800 at the top. Is this supposed to 
>>>> be
>>>
>>> different from the port that's set in VCC (65504). Which ROM image
> should I
>>> be using in VCC, and is that for 6809 or 6309?
>>>
>>> The drivewire UI is using the title bar to tell you what drivewire 
>>> server
>>> it is managing, not related to how Vcc and that server are 
>>> communicating.
>>>
>>> If you open the simple wizard and choose Emulator/Tcpip on the first
> page,
>>> and then directly click Finish, you will have a perfect config for doing
>>> everything on one computer.
>>>
>>> So, those two clicks and you are done configuring Drivewire.   To set up
>>> Vcc, open the configuration dialog and select the bitbanger page.  Click
>>> the check box to enable the Becker interface.  Enter 127.0.0.1 as your
>>> server IP, and 65504 as your server port (these may already be set, they
>>> are the defaults).  Click Apply and/or OK.  You're now done configuring
>>> things as far as the connection goes.
>>>
>>> You should see DW: label in the Vcc status bar, and it should say OK and
>>> give two numbers.  These measure the read and write speed of the
> interface.
>>> If you see Error or do not see DW ConnOK and numbers, stop as we have
>>> failed to get the connection set up correctly.  Go directly to jail, do
> not
>>> pass Go, etc.
>>>
>>> Assuming you get this far, the rest is really up to you.  What are you
>>> hoping to do?  If you want to use OS9 (where most of the fun drivewire
>>> stuff is) you need to attach a boot disk or hard disk image that 
>>> includes
>>> one or more DriveWire OS9 modules built for Becker mode to Vcc as usual
> and
>>> boot it as you would boot any OS9 system in Vcc, nothing special 
>>> required
>>> beyond the os9 drivers.  I believe Bill posted links to some images
>>> containing his awesome SoundChaser music player and songs.
>>> If I understand correctly you can just attach to Vcc, boot, and you're
>>> ready to play MIDI music via the DriveWire server, no special config
> needed
>>> there.
>>>
>>> HDBDOS is also available, there are instructions in the readme and on 
>>> the
>>> Vcc.cococoding.com page, its just a matter of telling the fd502 to use
> the
>>> included ROM, essentially just like sticking a real DW ROM into a real
>>> fd502.  Using HDBDOS this way you would insert disks via drivewire 
>>> rather
>>> than vcc,  they do not need to be special disks, any decb disk should
> work
>>> fine.
>>>
>>> David may have more to add, I know he is working on some additional
>>> updates.  Hope that gets you started at least.
>>>
>>>
>>>
>>>>
>>>> What disk(s) should be in DW4's drives? Should I have a VHD file in 
>>>> VCC?
>>>>
>>>> A lot of questions, I know, but any leads towards a working system 
>>>> would
>>>
>>> be great.
>>>>
>>>>
>>>> Regards, Bob Devries
>>>> Dalby, QLD, Australia
>>>>
>>>> --
>>>> 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 