>> 3) I'm quite determined to use "winmodems" (sic) without loading the
>> GUI. In this case, a PCMCIA (PCIC) card is involved, also. I think this
>> bus is 32bits wide, requires PnP type post codes, etc.. If needed, I'll
>> find (or if necessary, write) a 32 bit I/O service for DOS. I've not
>> dealt with protected mode before, so any input will be appreciated, on
>> or off list. I will get this done. Even if I need a Y2.3K fix by then.
>> ;)
> I think, even after loading DOS card and socket services, the modem will
> still refuse to work until the correct drivers for the card are running -
> in other words, Windows. Bit like my blasted HP printer...
I'm sure you're right about the modem not working until a proper driver
is found. I'll get one one way or another (and keep in mind Windows is
not a "proper" anything :P ). That goes for the HP printers too, but
I'll get to them last, as HP is "partnered" with M$, now.
Microsoft has done a good job of making it difficult to find software
that doesn't require Windows. Now they're trying to do the same for
hardware. Microsoft just doesn't know the "guts" of computers well
enough to pull that one off *if someone will act now*.
I've been looking at Windows "drivers" and most are just comm or I/O
protocols that, except for the manufacturer's failure to publish to
anyone else, are not at all Windows specific. Where copyrights exist,
they are owned by the hardware manufacturer, not M$.
Writing DOS drivers for these devices will be difficult, as most require
true 32 bit access. Chances are applications will have to be written
with this in mind. Another option which may work is to write drivers
which are a virtual 16 bit device to DOS, and provide 32 bit I/O to the
actual hardware, but this will be slow. New applications would be
better.
boB
-- Arachne V1.50;beta, NON-COMMERCIAL copy, http://home.arachne.cz/
To unsubscribe from SURVPC send a message to [EMAIL PROTECTED] with
unsubscribe SURVPC in the body of the message.
Also, trim this footer from any quoted replies.
