Kris Steenhaut wrote as follows on 11/02/06 02:12:

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

    Why are you surprised as our modems are different AFAICT?  Here is 
the output from PCI.EXE for my Action Tec modem:

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)

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

    I will have to dig out the CD from 'Action Tec', but don't recall 
seeing the above driver and utility anywhere on it.

>However, Faxworks can't see the modem at all, not even with the entry
>
>DEVICE=E:\APPARATEN\FMD.SYS N 1,BC00,4
>  
>

    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

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

    As stated above, my modem appears to be different than yours, as it 
was purchased in March of 2000.

>Anyone else using succesfully a Lucent winmodem and Faxworks?
>

-- 
 Aloha,
         Kenn
 _____________________________________________________________________
        Always act as if life is a joyous journey. - Kenn Yuill
                __________ A Quote for Today __________
In real life, unlike in Shakespeare, the sweetness of the rose depends
      upon the name it bears.  Things are not only what they are.
      They are, in very important respects, what they seem to be.
- Hubert H. Humphrey [1911-78, US Senator & Vice-President, 1965-69]
 _____________________________________________________________________
              * TagZilla 0.059 * http://tagzilla.mozdev.org>


 
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/
 




---