[Coco] Can Drivewire connect two computers

[Aaron Wolfe]

On Mar 15, 2014 1:49 PM, "Bill Pierce" <ooogalapasooo at aol.com> wrote:
>
>
> @Aaron,
> You are saying then if I load a VHD in instance 0 (real Coco3), then load
the same VHD in instance 1 (Vcc 1.4.3b), that if I save a file to that VHD
in instance 0, it will appear in that same VHD in instance 1?
>

You can do this.  Remember that DW is *sector* based, it doesn't understand
files.  If you allocate sector X to one file in one instance and to another
in the other instance, you're going to have a Bad Time.

The key to happiness is using the Sync From and Sync To settings
appropriately.  Most things are documented here:

http://sourceforge.net/apps/mediawiki/drivewireserver/index.php?title=Using_DriveWire#Disk_Buffers

One additional point is that Sync From ensures the coco always sees the
most current sector written to the source (regardless of whether that write
was done by drivewire) on every read.

> I was under the impression that each instance loaded it's own copy of the
VHD file into the server's memory and the actual "file" on the server HD
would not be updated until the VHD is ejected or DW4 is shut down.
> If so, then the VHD in instance 1 would not reflect the changes made in
the VHD in instance 0 until either eject or a dw4 shutdown.
>

That is the default behavior, but there are lots of settings provided to
adjust this for various scenarios.

> Please correct me if I'm wrong as this would save me quite a bit of "VHD
swapping".
> OR, is the UI cmd "ui sync" needed for this to work properly?

Ui sync is something else entirely, it writes an event stream that the UI
uses to reflect the current state of the server.

>
>
> Bill Pierce
> "Today is a good day... I woke up" - Ritchie Havens
>
>
> 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: Sat, Mar 15, 2014 2:48 am
> Subject: Re: [Coco] Can Drivewire connect two computers
>
>
> On Mar 14, 2014 11:32 PM, "Brian Goers" <briang0671 at sbcglobal.net> wrote:
> >
> > Is it possible to connect two Color Computers to one Drivewire server?
>
> DriveWire 4 supports an essentially unlimited number of CoCos, emulators,
> FPGAs, etc connected to a single server.
>
> > Could they write/read the same directory but different files?
>
> If you're talking about different disk images in the same directory of the
> server, absolutely no problem.
>
> If you're talking about different DECB or OS9 files inside the *same* disk
> image mounted in multiple drives and/or multiple cocos, the answer is
still
> yes, but with a HUGE caveat:
>
> It is your own responsibility to avoid destroying your disk image.  DW4
> provides all the tools you need to do this, but DW4 cannot make it safe,
> automatic, or at all foolproof.  If you misuse these tools or don't fully
> understand the ramifications of what you do with them, you will destroy
the
> data on your disk.  Not for casual users.
>
> That said, it is often convenient to have the same disk image mounted in
> multiple cocos or a real coco and an emulator at the same time, and DW4
can
> certainly help you do that kind of thing.  When writing/testing coco
> programs I often do exactly that.
>
> >
> > --
> >
> >  Brian Goers     Vice President of Special Events
> >                     http://glensideccc.com/newindex.shtml
> >
> >              The 23nd Annual "Last" Chicago CoCoFEST!
> >
> >     Fairfield Inn & Suites Lombard           April 26 & 27, 2014
> >     645 West North Avenue                 Saturday 10 am to 5 pm
> >     Lombard, IL 60148                 Socialize - 8 pm to 10 pm or
beyond
> >     1-630-629-1500                       Sunday 10 am to 3 pm or beyond
> >
> >
> >
> >
> > --
> > 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