At 03:17 PM 6/10/01 +0100, robert w hall wrote:
>In article <[EMAIL PROTECTED]>, Raymond Shwake
><[EMAIL PROTECTED]> writes
> > A message was posted a few days back suggesting that internal modems
> >are not supported under Win4Lin. That struck me as curious, not only because
> >I was pretty certain I'd worked with such a modem (I have one licensed and
> >one eval installation) but also because I couldn't see any reason to
> >distinguish internal vs. external using standard hardware addresses.
> >
> > Sure enough, I've got a US Robotics V.90 Courier Internal in an
> >IBM 365 desktop operating as COM2. (I disabled an onboard device at IRQ 3
> >before installing the modem.) Once I installed the right modem driver,
> >Win4Lin 3.0 seems to handle this internal modem just fine.
>
>is it driven by a VxD? I suspect not.
>Some (but not many) internals use neither Host Signal Processing (these
>usually need an MMX pentium or better) nor Host Control Processing
>(these will run on a 386, but still use a VxD to access control
>functions in ring 0)
i suspect there's some confusion here between internal modems (which look
just like COM1 or whatever) and internal win-modems (which require software).
_______________________________________________
Win4Lin-users mailing list
[EMAIL PROTECTED]
https://lists.netraverse.com/mailman/listinfo/win4lin-users
