Kenn Yuill wrote:
>   
>> Kenn Yuill wrote:
>>  
>>
>>     
>>>>     As written previously on this or other lists, my
internal "Action 
>>>> Tec Call Waiting PCI Modem" works fine with COM.SYS,
ver. 1.2 and 
>>>> Faxworks' driver, FMD.SYS.  It is identified as above and as a 
>>>> "Lucent/Agere Venus WinModem" by PCI.EXE (PCI_VK).
>>>>
>>>>         
Now I'm even more surprised.
>>>>   
>>>>         
>>>    
>>>
>>>       
>> As is mine:
>>
>>  
>>
>>     
>>>> Vendor 11C1h Lucent/Agere Systems (Was: AT&T MicroElectronics)
>>>> Device 044Ah LT WinModem 56k
>>>> Command 0007h (I/O Access, Memory Access, BusMaster)
>>>> Status 0290h (Has Capabilities List, Supports Back-To-Back Trans.,
>>>>         
>>>    
> DEVICE=C:\OS2\BOOT\COM.SYS (1,3F8,4) (2,2F8,3) (4,D800,10)
> DEVICE=E:\FAXWORKS\FMD.SYS (1,03F8,4) (2,02F8,3) (4,D800,10)
>
> plus the following one was used with Ray Gwinn's 1.60d driver on my old box,
>   REM DEVICE=C:\SIO\SIO.SYS (COM4:230400,D800,IRQ11)
> which worked normally, AFAIR.
>
>   
So, after a few days messing around I had to came to the conclusion the 
lucent modem even doesn't use com.sys (as ever, the readme is half 
baken, it says ltmdmos2.sys has to come before com.sys, and other than 
that you're on your own.

So, with these two line (and no com.sys):

DEVICE=E:\os2\boot\ltmdmos2.sys /v
RUN=E:\os2\boot\lt_mon.exe

the modem works perfect with Injoy, ZOC and Dialer/2. ltmdos2.sys 
triggers the modem to com1, IRQ4, BC00.

However, Faxworks can't see the modem at all, not even with the entry

DEVICE=E:\APPARATEN\FMD.SYS N 1,BC00,4

So, I keep being amazed you've got Faxworks running through this modem.

Anyone else using succesfully a Lucent winmodem and Faxworks?

-- 
Groeten uit Gent,

   Kris




 
Yahoo! Groups Links

 To visit your group on the web, go to:
    http://groups.yahoo.com/group/os2hardware/

 To unsubscribe from this group, send an email to:
    os2hardware-unsubscribe{at}yahoogroups.com

 Your use of Yahoo! Groups is subject to:
    http://docs.yahoo.com/info/terms/
 




---