[Coco] DriveWire 4 server version 3.9.98

[Aaron Wolfe]

Hi Coconuts,

I've posted an updated DW4 server at:

https://sites.google.com/site/drivewire4/beta


This update includes some bug fixes and performance improvements, as well as
some new features specifically for use with Brett's CoCoBoot,
docs at:

https://sourceforge.net/apps/mediawiki/drivewireserver/index.php?title=Using_DriveWire#Use_with_CoCoBoot


This is an update on the server side only, so it is not platform dependent.
 Just replace DriveWire.jar with the new version and you're ready to go.

One feature that has been asked for is a way to automatically sync changes
made to the source image into the buffered version.  For instance
maybe you load diskA.dsk, try it out on the CoCo, and decide to put a new
version of some file onto it from the PC using the Toolshed.  In the
past, you would then need to tell the DW server to reload the disk image
into it's buffer before the CoCo would see the change.  There is a new
per drive setting, "syncfromsource", that will tell the server to look at
the original image any time it's asked to read a sector.  If the last
changed
timestamp according to the OS is newer than the server expected, it will
automatically reload it's buffer prior to answering the read request.

You can set this per disk in a disk set definition, i.e.:

<diskset>
  <Name>mydiskset</Name>
  <disk>
    <drive>1</drive>
    <path>file:///F:/CoCo/mydisk.dsk</path>
    <syncfromsource>true</syncfromsource>
  </disk>
</diskset>

You can also enable it for all disks in an instance:

<DiskSyncFromSource>true</DiskSyncFromSource>

This is somewhat experimental so please use with caution until it's well
tested.  Especially with disk images from remote source (web sites, ftp,
etc) the last modified date may not be reliable.
If the server finds that the source timestamp has changed whilst it has
uncommitted changes in it's buffer, it will warn you in the log but it
*will* overwrite the source with it's version.

-Aaron