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.
>>  
>>
>>     
>
>     Why are you surprised as our modems are different AFAICT?  Here is 
> the output from PCI.EXE for my Action Tec modem:
>
>   
Because your ActionTec has the same lucentchip as well.
> Vendor 11C1h Lucent/Agere Systems (Was: AT&T MicroElectronics)
> Device 0480h Venus WinModem (V90, 56KFlex)
> Command 0004h (Bus Access Disabled!!, BusMaster)
> Status 0290h (Has Capabilities List, Supports Back-To-Back Trans.,
>   Medium Timing)
> Revision 00h, Header Type 00h, Bus Latency 00h
> Self test 00h (Self test not supported)
> PCI Class Simple Communication, type Other
> Subsystem ID 05001668h 56K V.90 Call Waiting PCI Modem
> Subsystem Vendor 1668h Action Tec Electronics Inc
> Address 0 is a Memory Address (anywhere in 0-4Gb) : F5000000h
> Address 1 is an I/O Port : 0000D800h
> Address 2 is an I/O Port : 0000D400h
> Address 3 is an I/O Port : 0000D000h
> New Capabilities List Present:
>   Power Management Capability
>     Supports power state D1
>     Current Power State : D0 (Device operational, no power saving)
>
>   
mine is:

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.,
  Medium Timing)
Revision 01h, Header Type 00h, Bus Latency Timer 00h
Minimum Bus Grant FCh, Maximum Bus Latency 0Eh
Self test 00h (Self test not supported)
PCI Class Simple Communication, type Other
Subsystem ID 001213E0h LT WinModem 56k Data+Fax+Voice+VoiceView+Dsvd
Subsystem Vendor 13E0h GVC Corporation
Address 0 is a Memory Address (anywhere in 0-4GiB) : FB022000h
Address 1 is an I/O Port : 0000B800h
Address 2 is an I/O Port : 0000BC00h
CIS can read from device specific configuration space, offset 40h
System IRQ 4, INT# A
New Capabilities List Present:
  Power Management Capability, Version 1.1
    Supports low power State D2
    Supports PME# signalling from mode(s) D2, D3hot, D3cold
    PME# signalling is currently disabled
    Current Power State : D0 (Device operational, no power saving)
>> 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
>>  
>>
>>     
>
>   
With the N parameter fmd.sys accepts there is a vaild port anyway. I can 
assume you are running your  lucent device with Faxworks, can't I?.
>     What is the parameter, "N", used for?
>
>     I wonder if
>  1. placing the line for FMD.SYS before the one for LTMDMOS2.SYS in your 
> Config.Sys would allow Faxworks to use the modem
>     &/or
>  2. using a different port, i/o address, irq for the newly placed line 
> for FMD.SYS would force either LTMDMOS2.SYS or LT_MON.EXE to select the 
> same setting
>
>   
Not possible. ltmdos2.sys only accepts the /v parameter, and assigns the 
BC00 address in all instances. There is no way to have that altered.
The problem is that fmd.sys apparently can't parse 1,BC00,4 to faxworks. 
The port appears with these specs in the port settings, but Faxworks 
can't find it I think.
>
>     As stated above, my modem appears to be different than yours, as it 
> was purchased in March of 2000.
>
>   
But you have it stil running with faxworks, haven't you?

-- 
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/
 




---