[Coco] becker and VCC1.43beta

[Bob Devries]

Thanks once again, Aaron.

I am now able to read the vhd from VCC both on the same computer, and on my 
laptop via a wifi network connection.

@Bill Pierce: Thanks for that patch location. I'm sure I would've found them 
myself, but it's quicker to ask ;)

No the last challenge is to be able to boot NitrOS9 from this setup.

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: Sunday, April 21, 2013 5:56 PM
Subject: Re: [Coco] becker and VCC1.43beta


> On Sat, Apr 20, 2013 at 4:46 AM, Bob Devries <devries.bob at gmail.com> 
> wrote:
>
>> 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?
>>
>
> No... you would only change the IP address in VCC.
>
> I've added a diagram to the Ports documentation in the DW4 wiki. Maybe
> it will help clear things up?
>
> https://sourceforge.net/apps/mediawiki/drivewireserver/index.php?title=Using_DriveWire#Ports
>
> I think maybe you're not understanding that the server IP and port the
> UI uses to talk to the server is an entirely different thing than the
> server IP and port that VCC uses to talk to an instance on the server.
> They will never be the same, as they are different processes
> entirely.  If you're doing everything on one computer they will both
> use localhost or 127.0.0.1 as the server IP, but the ports will always
> be different.
>
> You could run all three parts on different computers.  For instance,
> maybe you want to run the server on a tiny Raspberry Pi with address
> 192.168.1.10, the UI on your Windows computer with address
> 192.168.1.20, and VCC on another machine with address 192.168.1.30.
> In this case, the UI would have a server setting of 192.168.1.10 port
> 6800, and VCC would have a server setting of 192.168.1.10 port 65504.
> The DriveWire server itself doesn't need to know any of the client's
> addresses in any case.
>
> --
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco