[Coco] System gen problem

[Aaron Wolfe]

On Tue, Feb 9, 2010 at 12:19 PM, Steven Hirsch <snhirsch at gmail.com> wrote:
> On Tue, 9 Feb 2010, Boisy G. Pitre wrote:
>
>>
>> FYI, I have just updated the SOURCE of the three platforms (win, linux &
>> mac) to accommodate the OP_VPORT_READ command.  It just responds with two
>> zeros and doesn't support any of the virtual port features of DriveWire 4.
>>  I don't know what server you're using, but if it's the Linux one, you
>> should be able to CVS update and recompile then use the new drivers.
>
> I'm a bit confused on the overall status.  What is Drivewire 4, and how does
> that relate to the images I've been working with (which date back a bit)?
>

We thought long and hard about what to call the new DriveWire server
and finally decided on DW 4 but confusion over the version number was
a major concern.

"DriveWire 4" is the new server, written in Java and so able to run on
most any platform.  This means no more separate servers for win, mac
and linux, and also that DW can run on many new platforms such as
small embedded devices and even wireless routers.

The DW 4 Server is backwards compatible with older DriveWire modules
and DW3 ROMs.  There is no such thing as a DW4 ROM.

Currently, to obtain this server you must check out the Java source
from CVS and build it for your platform.  This is not for the casual
user.  There are helpful docs in the wiki on the DriveWire project
page:  http://sourceforge.net/apps/mediawiki/drivewireserver/
We hope to have an easy to use version available very soon.

The DW drivers currently in the Nitros9 CVS have new features and do
not work well with any server other than the DriveWire 4 server.
However, the change needed to make these new drivers work with older
servers is very small and sounds like Boisy has updated the version 3
servers to be compatible.

So... if you have an "old" (as in not from today) DriveWire 3 server,
you will have issues if you try to use the newest drivers from CVS.
This is the only combination that should cause any trouble, and I
think would be rather rare.  If you do get into this combination, the
resolution is to update to the newest DriveWire 3 server for your
platform, or just don't use the new modules, or use the DW4 server.

>> Again, this is untested.
>
> I have to run out and will probably get back to this later today.
>
>> The E$BNam error has something to do with linking to the dw3 subroutine
>> module, I believe.
>>
>> One quick thing: once you boot to your hard drive, what happens if you
>> just iniz /x0 (and not do a dir on it?)  Does an error come back?
>
> Yes, ERROR #235.
>
> --
>
> --
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco
>