[Coco] System gen problem
Steven Hirsch
snhirsch at gmail.com
Tue Feb 9 12:19:15 EST 2010
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)?
> 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.
--
More information about the Coco
mailing list