 |
Modemsite's Forum56 - The Modem Board Main | profile | register | search | help | Ad-free Login |
| Forums | Agere (Public) | DSP 1673 based modem | Watch |
| Author | Topic |
| duffsparky Tl Posts: 6 United Kingdom | Posted - 12/17/2004 10:18:41 AM    I have an external VDF modem which will not work properly on XP Pro SP1 or SP2. Forgetting internet connection, I have resorted to Hyper Terminal. Using HT to 'Connect to' using com1, I can get a dial tone and dial out and get my second phone line to ring using the AT commands. But if I try 'Connect to' using my modem and click the 'Dial' button I get a quick flash of, 'Connecting' followed by 'Dialing' followed by 'No Answer', if I then reclick the 'Dial' button the system usually connects to the number dialed and rings the number (in this case my second line phone). I have tried allsorts to correct the problem, but have got nowhere. Can any one help. |
| Pi Tl Posts: 89 USA | Posted - 12/17/2004 11:02:34 AM If DUN "Dial Up Networking " is not set to "Wait For Dial Tone" and your local phone system is slow to bring up a dial tone the modem is dialing before the dial tone. Set DUN to "Wait For Dial Tone" or place a W in front of the number dialed. This will make the modem wait for a dial tone before dialing. |
| duffsparky Tl Posts: 6 United Kingdom | Posted - 12/17/2004 2:50:02 PM Thanks, had some success with W command before telephone number. Is it possible putting this command in could have altered something for the better, cos now my dial-up to ISP works after a retry (with the W command removed). Hyper Terminal connects after retry same as before. Command ATD <return> gives me instant dial tone, whereas internet dialup and Hyper Terminal dial up give me no tone on the first try, but tone after about 8 seconds on retry. Below is results from ATI3 to ATI5 & AT&V. OK OK OK I was going to post the AT&V results but they will require a lot of editing, cos cut and paste jumble the result up. Modem is an external Paradise 56K Modem Pro. Paradise is now out of business and I cant find any good support. DSP chip is a Lucent(now Agere) 1673 t28. Most modem sites make reference to this chip being used in ISA cards which XP does not support. |
| Pi Tl Posts: 89 USA | Posted - 12/17/2004 4:13:00 PM The quick answer to this is to reinstall or update the modem driver with the original Paradise (Wavecom) 56K Modem Pro driver inf file. I think the Service Packs reinstalled the modem using a generic Lucent Venus driver. When you click on update driver the current and the original driver used to install the modem should be listed. Use the Paradise or Wavecom driver INF. If the original driver is not listed or you no longer have the install disk there are several driver web sites that have it. """Philips Paradise WaveCom 56K""" """Paradise 56K Modem Pro Drivers from original installation cd rom version 1.40 english""" |
| duffsparky Tl Posts: 6 United Kingdom | Posted - 12/18/2004 3:24:24 AM I have done this before, and again just now with a fresh download from driverguide. Same result. Here is the info from the modem properties dialog:- From Driver tab Driver File Details I guess this is the generic driver from XP SP2. Each time I try to reinstall the driver i get the same result. If I delete or rename Modem.sys in the drivers folder will this force XP to look elsewhere for a driver? |
| Pi Tl Posts: 89 USA | Posted - 12/18/2004 6:43:47 AM Don't rename modem.sys. This is either a TAPI or WinSock II driver and Windows loads these drivers for all modems. Windows installs Lucent Venus (1673 chip) modems from a INF (information file). I assume you deleted the modem and rebooted and Windows reinstalled the modem automatically. Instead of deleting the modem "update" the driver from Device Manager. When Windows asks for the driver location browse to the driver package you downloaded and pick the 56pro.inf file. You should get a warning that the driver is not "Digitally Signed " Click to install driver anyway. The name Windows gives to the modem "after" the driver install is taken from the INF file and should not be a generic one like "Lucent Venus Modem". Very important;. If the driver appears not to be updating. |
| duffsparky Tl Posts: 6 United Kingdom | Posted - 12/18/2004 3:41:40 PM Where do I find the modem drivers that are actually being used? I've used the 'Update Driver' command from the modem properties dialog via 'Modem & Phone Options', also tried same via 'Device Manager'. Picked 56K.inf, from recent download, copied to HD and floppy. Modem shown in properties is 56K External Modem PRO. "Driver Signing " is not set to "Block" it was set to 'Warn' also tried 'Ignore' setting. My normal login has full admin rights, I tried all the above and more from 'Administrator' login as well. One thing I haven't tried is installing the Generic Lucent Venus driver. Think I'll give that ago!!! |
| duffsparky Tl Posts: 6 United Kingdom | Posted - 12/19/2004 5:33:25 AM Tried generic Lucent drivers with same results as before except:- With Lucent Venus Modem connected first time with Internet DUN but could only connect second time on subsequent attempts. With 56K External ModemON BVRP PhoneTools would not connect. |
| duffsparky Tl Posts: 6 United Kingdom | Posted - 12/19/2004 5:55:45 AM Ammendment to previous posting. Tried generic Lucent drivers with the following results:- With Lucent External Voice Modem - Internet DUN failed to connect first time but connected on redial. BVRP PhoneTools connected first time but after a very long wait. HyperTerminal would only connect on redial (same as DUN). With Lucent Venus Modem - Same as for Lucent External Voice Modem above. With Lucent Venus Modem PNP - Internet DUN connected first time, and on redial but would only connect on redial for subsequent attemps. BVRP PhoneTools connected first time but after a very long wait. HyperTerminal would only connect on redial (same as DUN). With 56K External ModemON - Internet DUN failed to connect first time but connected on redial. BVRP PhoneTools would not connect at all. HyperTerminal would only connect on redial (same as DUN). |
| Pi Tl Posts: 89 USA | Posted - 12/19/2004 9:13:02 AM Did the modem dial correctly with Windows XP before SP1 or SP2 was installed. The modem firmware might be having trouble detecting the local phone companies dial tone. You can try to uncheck "Wait for Dial Tone" in the DUN settings and add comas to the phone number.. ,,,,5555555. The comas add approximately 1 second pause (each) before the modem dials and the modem does not try to detect the dial tone. This is some times needed in countries where the dial tones are not consistent. I had a similar problem with a Actiontec V90 PCI V90 Call Waiting modem (VEnus 1673 chipset) "Where do I find the modem drivers that are actually being used?" "Modem shown in properties is 56K External Modem PRO." P/S You can override the registry setting, based on the country code , by placing the S11=100 in the modem extry settings. Remember the higher the number the slower the modem dials. Edited by - Pi on 12/19/2004 9:33:42 AM |
Click Here To Close Thread, Administrators & Moderators Only.
Show All Forums |