It seems that if i install Win98SE SP2 on a system that has a USR winmodem installed, the modem driver begins to act up. You can successfully dial and connect ONCE. But if you disconnect then try to reconnect you get a "DUN 630 error - modem not responding"
If you reboot you can dial again, but still only once.
I've primarily noticed on USR 5699 winmodems but also a few odd other USR winmodems.
Do you have any thoughts or suggestions?
Andy
Full Version: Win98SE SP2 Modem problem
MSFN Forums > Microsoft Software Products - Discussion & Support > Windows 95/98/98SE/ME > Windows 9x Member Projects
QUOTE (redwingtech @ Sep 14 2005, 08:30 AM)
It seems that if i install Win98SE SP2 on a system that has a USR winmodem installed, the modem driver begins to act up. You can successfully dial and connect ONCE. But if you disconnect then try to reconnect you get a "DUN 630 error - modem not responding"
If you reboot you can dial again, but still only once.
I've primarily noticed on USR 5699 winmodems but also a few odd other USR winmodems.
Do you have any thoughts or suggestions?
Andy
If you reboot you can dial again, but still only once.
I've primarily noticed on USR 5699 winmodems but also a few odd other USR winmodems.
Do you have any thoughts or suggestions?
Andy
I found a good site for answers to this error issue, but my first impulse is to say, don't use a Winmodem. They aren't worth it. If that's not possible, then you can try troubleshooting -- it sounds like a driver issue, as suggested below:
http://groups.google.com/group/microsoft.p...1ac689e5e1ed672
QUOTE
Simon Chapman Jan 9 2002, 5:00 am
Newsgroups: microsoft.public.win98.comm.modem
From: "Simon Chapman" <simon.chap...@mtservices.co.uk>
Date: Wed, 9 Jan 2002 11:56:30 -0000
Local: Wed, Jan 9 2002 4:56 am
Subject: Error 630 on 2nd Dial Up Connection (DUN)
On a first attempt to dial up to an ISP Internet Connection, the 3Com
Internal Modem will dial and connect with no issues. Collection of mail
and/or internet access is fine.
On disconnection to the internet, should another session be attempted when
the modem attempts to dial, an error code of 630 is shown and a message
saying no modem is installed or is available.
The machine then has to be restarted before another dial up connection can
be established.
Any help people can offer would be appreciated.
Regards
Simon
George M. Winford \(MVP\) Jan 9 2002, 8:32 am
Newsgroups: microsoft.public.win98.comm.modem
From: "George M. Winford \(MVP\)" <gwinf...@mvps.org>
Date: Wed, 9 Jan 2002 08:30:15 -0700
Local: Wed, Jan 9 2002 8:30 am
Subject: Re: Error 630 on 2nd Dial Up Connection (DUN)
Hello, Simon,
For the 630 error, I suggest that you replace serial.vxd using either
Version Conflict Manager or System File Checker.
Both of these utilities are available by going to Start>Run and typing
"msinfo32" and then hitting <Enter>. When MSinfo opens, click on Tools for a
list of other programs, including Version Conflict Manager and System File
Checker.
While you are in Microsoft Information, you might also want to check for
hardware conflicts by expanding Hardware Resources and clicking on
Conflicts/Sharing.
Also, you might need to replace your telephon.ini file. Here is the KB
article that tells you how to rebuild it:
http://support.microsoft.com/support/kb/ar...s/q120/2/21.asp
And, here are two more links that should provide some help:
http://808hi.com/56k/duns645.htm
http://808hi.com/56k/tshoot.htm .
I hope this helps you,
--
geo. - George M. Winford - MS MVP (Windows 9x )
Microsoft Certified Professional
Associate Expert
Expert Zone - www.microsoft.com/windowsxp/expertzone
Newsgroups: microsoft.public.win98.comm.modem
From: "Simon Chapman" <simon.chap...@mtservices.co.uk>
Date: Wed, 9 Jan 2002 11:56:30 -0000
Local: Wed, Jan 9 2002 4:56 am
Subject: Error 630 on 2nd Dial Up Connection (DUN)
On a first attempt to dial up to an ISP Internet Connection, the 3Com
Internal Modem will dial and connect with no issues. Collection of mail
and/or internet access is fine.
On disconnection to the internet, should another session be attempted when
the modem attempts to dial, an error code of 630 is shown and a message
saying no modem is installed or is available.
The machine then has to be restarted before another dial up connection can
be established.
Any help people can offer would be appreciated.
Regards
Simon
George M. Winford \(MVP\) Jan 9 2002, 8:32 am
Newsgroups: microsoft.public.win98.comm.modem
From: "George M. Winford \(MVP\)" <gwinf...@mvps.org>
Date: Wed, 9 Jan 2002 08:30:15 -0700
Local: Wed, Jan 9 2002 8:30 am
Subject: Re: Error 630 on 2nd Dial Up Connection (DUN)
Hello, Simon,
For the 630 error, I suggest that you replace serial.vxd using either
Version Conflict Manager or System File Checker.
Both of these utilities are available by going to Start>Run and typing
"msinfo32" and then hitting <Enter>. When MSinfo opens, click on Tools for a
list of other programs, including Version Conflict Manager and System File
Checker.
While you are in Microsoft Information, you might also want to check for
hardware conflicts by expanding Hardware Resources and clicking on
Conflicts/Sharing.
Also, you might need to replace your telephon.ini file. Here is the KB
article that tells you how to rebuild it:
http://support.microsoft.com/support/kb/ar...s/q120/2/21.asp
And, here are two more links that should provide some help:
http://808hi.com/56k/duns645.htm
http://808hi.com/56k/tshoot.htm .
I hope this helps you,
--
geo. - George M. Winford - MS MVP (Windows 9x )
Microsoft Certified Professional
Associate Expert
Expert Zone - www.microsoft.com/windowsxp/expertzone
If the above isn't enough, you can try this link:
http://www.modemhelp.net/dunerror/error_630.shtml
Roving
USR made good hardware modems but dropped the ball when it came to software modems (aka winmodems). I'd junk it and pick up a new non-USR winmodem.
I've had very good results with Lucent/Agere based winmodems and also with recent PCTel winmodems.
You can get a new lucent/agere modem for less than $20.
It will support V.92/V.44 features including modem-on-hold, quick connect, PCM upstream, and improved compression on calls to V.92-compatible ISPs.
I've had very good results with Lucent/Agere based winmodems and also with recent PCTel winmodems.
You can get a new lucent/agere modem for less than $20.
It will support V.92/V.44 features including modem-on-hold, quick connect, PCM upstream, and improved compression on calls to V.92-compatible ISPs.
QUOTE (redwingtech @ Sep 14 2005, 05:30 PM)
It seems that if i install Win98SE SP2 on a system that has a USR winmodem installed, the modem driver begins to act up. You can successfully dial and connect ONCE. But if you disconnect then try to reconnect you get a "DUN 630 error - modem not responding"
If you reboot you can dial again, but still only once.
I've primarily noticed on USR 5699 winmodems but also a few odd other USR winmodems.
Do you have any thoughts or suggestions?
Andy
If you reboot you can dial again, but still only once.
I've primarily noticed on USR 5699 winmodems but also a few odd other USR winmodems.
Do you have any thoughts or suggestions?
Andy
redwingtech, Could you try to re-install your (latest) modem drivers? Also, please don't miss Roving's post.
Also tap ctrl,alt,delete and see if you have a program that may be holding the modem open. End task RNAAPP and try the connection again. Have you added anything to extra settings? Might also delete you connection icon in dialup networking and make a new one.
Thanks for the replies guys.
Roving : Ya it's definitely a driver issue. But the problem is that this problem didn't happen before the SP2 install and has always happened after, in particularly with the USR 5699 winmodem.
krick : I totally agree with you guys on the winmodem vs HDW modem issue. Problem is that these are customers computers. And we sold a lot of 5699 winmodems back in the day. I didn't notice this problem for about 2 wks or so since i usually do a single connection test. Can't really tell them to just buy a new modem.
I've stopped using SP2 on systems with USR winmodems since.
Gape : Latest drivers, hehe, the USR driver on the website is years old and has always worked. No updates available.
charles__ : yup i had thought of that one, but sadly no. No fax programs either.
So do you guys have any other ideas? Maybe a clue as to what possible changes SP2 makes to how a modem driver works? It seems that it's only the USR winmodem i'm having difficulties with.
Cheers
RedwingTech
Roving : Ya it's definitely a driver issue. But the problem is that this problem didn't happen before the SP2 install and has always happened after, in particularly with the USR 5699 winmodem.
krick : I totally agree with you guys on the winmodem vs HDW modem issue. Problem is that these are customers computers. And we sold a lot of 5699 winmodems back in the day. I didn't notice this problem for about 2 wks or so since i usually do a single connection test. Can't really tell them to just buy a new modem.
I've stopped using SP2 on systems with USR winmodems since.
Gape : Latest drivers, hehe, the USR driver on the website is years old and has always worked. No updates available.
charles__ : yup i had thought of that one, but sadly no. No fax programs either.
So do you guys have any other ideas? Maybe a clue as to what possible changes SP2 makes to how a modem driver works? It seems that it's only the USR winmodem i'm having difficulties with.
Cheers
RedwingTech
Do older versions of SP2 exhibit the same problem?
Maybe we can pin it down to a specific update.
Maybe we can pin it down to a specific update.
I've only used the release versions of SP2 ( 2.0 - 2.0.1 - 2.0.2 )
Didn't use any of the beta's
As far as i can remember all of them had the problem.
RedwingTech
Didn't use any of the beta's
As far as i can remember all of them had the problem.
RedwingTech
Short Answer: Well let me say athe obvious and I hope you are using the latest (last) WinModem driver available. If that doesn't work spend the $20 to get a new modem but DO NOT blame your problems on the fact it's a WinModem.
Long Answer: I have to disagree with the myth, there's nothing wrong with WinModems. They only got a bad rep because back when they were invented and people still had 486's, a WinModem could easily eat 5%-12% of your CPU. Of course a P1 is upto 7x faster than a 486 on the same MHZ so even on the slowest Pentium this was no longer an issue.
I've used the USR WinModem extensively back in the day and can vouch they are perefctly fine, in fact WinModems were a good thing for the industry because it made modems cheaper because many of the parts inside a WinModem could be done in software. Mass producing software is almost free, mass producing hardware costs $.
The only negative aspect for a WinModem is that they only work in the OSs that have a drivers for (ex: Windows only) but that's been true for pretty much all modems in the first place, although at least in Linux you could have tried to use a generic driver on a normal hardware modem.
Long Answer: I have to disagree with the myth, there's nothing wrong with WinModems. They only got a bad rep because back when they were invented and people still had 486's, a WinModem could easily eat 5%-12% of your CPU. Of course a P1 is upto 7x faster than a 486 on the same MHZ so even on the slowest Pentium this was no longer an issue.
I've used the USR WinModem extensively back in the day and can vouch they are perefctly fine, in fact WinModems were a good thing for the industry because it made modems cheaper because many of the parts inside a WinModem could be done in software. Mass producing software is almost free, mass producing hardware costs $.
The only negative aspect for a WinModem is that they only work in the OSs that have a drivers for (ex: Windows only) but that's been true for pretty much all modems in the first place, although at least in Linux you could have tried to use a generic driver on a normal hardware modem.
Rhelic : I tend to agree with _most_ of what you say. We sold USR 5699 winmodems for _years_ with no problems. And your correct about the CPU usage. However you can find really _cheap_ winmodems with zero quality control and they suck ( but that's NOT the issue here ). I'm sure we can all put this debate behind us.
My problem is not a hardware vs software modem. It's a specific model of USR modem that doesn't work correctly after the installation of SP2.
I would be estatic if there was another driver that fixes the issue, but i'm afraid i have not found one. Plus i have seen a few other non-5699 USR modems that do this. I have not had this problem with any other brand of modem ( including very cheap winmodems ).
Does anyone have a clue what else might change with SP2 that would have this affect on the modem.
Just random observations:
- it's not motherboard chipset specific ( happens on Via, Intel ... )
- reinstalling the MDM DRV makes no difference
- changing the COM port makes no difference
Redwing Tech.
My problem is not a hardware vs software modem. It's a specific model of USR modem that doesn't work correctly after the installation of SP2.
I would be estatic if there was another driver that fixes the issue, but i'm afraid i have not found one. Plus i have seen a few other non-5699 USR modems that do this. I have not had this problem with any other brand of modem ( including very cheap winmodems ).
Does anyone have a clue what else might change with SP2 that would have this affect on the modem.
Just random observations:
- it's not motherboard chipset specific ( happens on Via, Intel ... )
- reinstalling the MDM DRV makes no difference
- changing the COM port makes no difference
Redwing Tech.
my 2 ¢
I recall reading that Microsoft [and most hardware vendors followed suit] dropped support for winmodems a few years back, especially since everybody started pushing xDSL and Cable as the next best thing.
That's why [probably] a newer version of a system file installed by SP2 removes compatibility with [certain] winmodems. [?]
It's a long shot and time consuming, but one can tell with a little luck which file(s) is (are) the "culprit":
the best bet is to "look" inside %windir%\INF\*.INF files with Notepad or better text editor/viewer:
http://www.mdgx.com/toy.htm#TXT
and inside related system files with a hex or resource editor/viewer:
http://www.mdgx.com/toy.htm#HEX
These freeware tools may also help determine system files interdependencies:
Dependency Walker:
http://www.dependencywalker.com/
Process Explorer:
http://www.sysinternals.com/utilities/processexplorer.html
Hope this helps.
I recall reading that Microsoft [and most hardware vendors followed suit] dropped support for winmodems a few years back, especially since everybody started pushing xDSL and Cable as the next best thing.
That's why [probably] a newer version of a system file installed by SP2 removes compatibility with [certain] winmodems. [?]
It's a long shot and time consuming, but one can tell with a little luck which file(s) is (are) the "culprit":
the best bet is to "look" inside %windir%\INF\*.INF files with Notepad or better text editor/viewer:
http://www.mdgx.com/toy.htm#TXT
and inside related system files with a hex or resource editor/viewer:
http://www.mdgx.com/toy.htm#HEX
These freeware tools may also help determine system files interdependencies:
Dependency Walker:
http://www.dependencywalker.com/
Process Explorer:
http://www.sysinternals.com/utilities/processexplorer.html
Hope this helps.
QUOTE (MDGx @ Sep 17 2005, 01:46 AM)
I recall reading that Microsoft dropped support for winmodems a few years back...
IIRC, WinModems are 100% driver based, Microsoft has no "support" to remove. And even if they did, trust me, they wouldn't break support. Backwards compatibility has been the crutch of Windows since Win95 and hasn't stopped yet and won't stop anytime soon. WinXP tooks huge steps to have backwards compatibility, Windows Vista improves on backward compatibility, and Windows 2010 will continue to support legacy apps.
Oneday we might not even need DosBox, who knows.
MDGx
Thanks for the reply.
Great utilities you've pointed out, i use them all the time. Don't really have to do much hunting to find the INF file. I just don't know what i'm doing with it.
Thanks for the reply.
Great utilities you've pointed out, i use them all the time. Don't really have to do much hunting to find the INF file. I just don't know what i'm doing with it.
I also use a USR Winmodem (but model no. 5699B), and encountered a 630 error message a few times. What I did was remove the modem driver, shut down the PC, take out the USR modem and insert it into another PCI expansion slot, turn on the PC and re-installed the drivers. the modem worked flawlessly and I can reconnect after disconnecting.
maybe the modem might be inserted into an unreliable slot. try removing the modem and put it into a different slot. Good thing I've been reading my brother's computer repair book on how to change computer parts.
maybe the modem might be inserted into an unreliable slot. try removing the modem and put it into a different slot. Good thing I've been reading my brother's computer repair book on how to change computer parts.
or perhaps the USR 5699 modem driver needs to be un-installed and then re-installed and you dont have to move the modem into a different slot. DON'T put in any Extra Settings for the USR modem, especially if you are using Netzero as your internet service.
redwingtech, try removing the USR modem driver from Add/Remove programs or from Device Manager. Then re-install the modem driver using the correct .INF file that came with the driver pack.
redwingtech, try removing the USR modem driver from Add/Remove programs or from Device Manager. Then re-install the modem driver using the correct .INF file that came with the driver pack.
erpdude8 : Ya i've tried the driver uninstall and reinstall to no avail. I'll try moving it to another PCI slot and see how goes.
Cheers
RedwingTech
Cheers
RedwingTech
QUOTE (redwingtech @ Oct 1 2005, 02:25 PM)
erpdude8 : Ya i've tried the driver uninstall and reinstall to no avail. I'll try moving it to another PCI slot and see how goes.
Cheers
RedwingTech
Cheers
RedwingTech
Before you actually move the modem to another slot, un-install the USR modem drivers first. then shut down your PC and move the modem to a different PCI slot, turn on PC, and re-install drivers. you might also try un-installing Win98se's Dialup Networking software and re-installing it. I read somewhere in the USR modem manual that the modem may not work properly if it is sharing an IRQ with another device and thus may require transferring the modem into another available slot.
and if you still have problems after trying the suggestions above, you might as well have to live without Gape's 98se pack or use another modem. try asking a friend who also owns a US robotics modem to see if yours could be defective. it is quite possible that the USR modem you have might be defective. You can also try testing your modem on a different computer with either 98se or a different version of Windows to see if the problem is specific to your computer.
You may want to post here ALL the system resource settings that your USR modem uses.
Look in Device Manager or the MS System Information tool to see what resources your devices are using.
erpdude8
Thanks for going the extra mile here. This problem has happened with multpile different computers and multiple different 5699 modems. I've made it a priority to test the functionality of them out before running SP2 and no problems. But once SP2 installed the modem has the problem.
I haven't run into another one yet but as soon as i do i'll try SP2 and try another PCI slot. I'll keep things posted.
Cheers
RedwingTech.
Thanks for going the extra mile here. This problem has happened with multpile different computers and multiple different 5699 modems. I've made it a priority to test the functionality of them out before running SP2 and no problems. But once SP2 installed the modem has the problem.
I haven't run into another one yet but as soon as i do i'll try SP2 and try another PCI slot. I'll keep things posted.
Cheers
RedwingTech.
QUOTE (redwingtech @ Oct 5 2005, 01:22 PM)
erpdude8
Thanks for going the extra mile here. This problem has happened with multpile different computers and multiple different 5699 modems. I've made it a priority to test the functionality of them out before running SP2 and no problems. But once SP2 installed the modem has the problem.
I haven't run into another one yet but as soon as i do i'll try SP2 and try another PCI slot. I'll keep things posted.
Cheers
RedwingTech.
Thanks for going the extra mile here. This problem has happened with multpile different computers and multiple different 5699 modems. I've made it a priority to test the functionality of them out before running SP2 and no problems. But once SP2 installed the modem has the problem.
I haven't run into another one yet but as soon as i do i'll try SP2 and try another PCI slot. I'll keep things posted.
Cheers
RedwingTech.
Also, RedwingTech try testing out the modems with different versions of Windows such as Windows 2000, Millennium or XP even. the problem may be Windows related and may just occur with Win98se only w/ the SP.
You may also want to run SFC.EXE (system file checker) from the Windows\System folder to check if some of the Win98se system files may be corrupted.
Another thing you may want to do is after installing the Win98se SP2 pack, try using the original 98SE released version of the VCOMM.VXD file. This file is stored in the Windows\System\Vmm32 folder. open System File Checker [sfc.exe] and click on the button to extract a system file from the Win98se setup .cab files, specify the vcomm.vxd file and save it into the 'Windows\System\Vmm32' folder.
btw - about the 630 error problem I had with my USR 5699B modem. I was using WinME, not Win98se. sorry for not specifying what version of Windows I was using.
the USR modem I have uses IRQ 10 and it's on COM3. I had to make sure that serial port 2 is disabled from BIOS setup so that Windows can properly detect and operate the modem on COM3.
btw - about the 630 error problem I had with my USR 5699B modem. I was using WinME, not Win98se. sorry for not specifying what version of Windows I was using.
the USR modem I have uses IRQ 10 and it's on COM3. I had to make sure that serial port 2 is disabled from BIOS setup so that Windows can properly detect and operate the modem on COM3.
erpdude8
Got another one of these 5699 modems.
Fresh install Win98SE
Tested modem BEFORE SP2 install - connects and reconnects ok
AFTER SP2 install connects but 630 error if you try to reconnect. Have to reboot to connect again.
- tried another PCI slot - no joy
- re-install 98SE and DID NOT install MDM DRV. Then updated to SP2 and installed MDM DRV -- no joy
will note more as i try it
RedwingTech
Yikes!
ran sfc - no problems
log notes;
104 folders examined.
1268 files examined.
397 files added to verification data file.
0 files removed from verification data file.
330 files updated in verification data file.
0 files restored.
0 file changes ignored.
Got another one of these 5699 modems.
Fresh install Win98SE
Tested modem BEFORE SP2 install - connects and reconnects ok
AFTER SP2 install connects but 630 error if you try to reconnect. Have to reboot to connect again.
- tried another PCI slot - no joy
- re-install 98SE and DID NOT install MDM DRV. Then updated to SP2 and installed MDM DRV -- no joy
will note more as i try it
RedwingTech
Yikes!
ran sfc - no problems
log notes;
104 folders examined.
1268 files examined.
397 files added to verification data file.
0 files removed from verification data file.
330 files updated in verification data file.
0 files restored.
0 file changes ignored.
Try this,click ctrl,alt delete and end task rnaapp and try to reconnect. Please post a modem log also. Do you have a nic or lan card installed? What port is the modem on,might disable that port in the bios and reinstall the modem. You do not need the modem port listed in the device manager because these modems use software ports. If is is disable it. Check for any programs in the startup folder also. make sure you do not have any modem strings in extra setting.
QUOTE (redwingtech @ Oct 13 2005, 07:47 AM)
erpdude8
Got another one of these 5699 modems.
Fresh install Win98SE
Tested modem BEFORE SP2 install - connects and reconnects ok
AFTER SP2 install connects but 630 error if you try to reconnect. Have to reboot to connect again.
- tried another PCI slot - no joy
- re-install 98SE and DID NOT install MDM DRV. Then updated to SP2 and installed MDM DRV -- no joy
will note more as i try it
RedwingTech
Yikes!
ran sfc - no problems
log notes;
104 folders examined.
1268 files examined.
397 files added to verification data file.
0 files removed from verification data file.
330 files updated in verification data file.
0 files restored.
0 file changes ignored.
Got another one of these 5699 modems.
Fresh install Win98SE
Tested modem BEFORE SP2 install - connects and reconnects ok
AFTER SP2 install connects but 630 error if you try to reconnect. Have to reboot to connect again.
- tried another PCI slot - no joy
- re-install 98SE and DID NOT install MDM DRV. Then updated to SP2 and installed MDM DRV -- no joy
will note more as i try it
RedwingTech
Yikes!
ran sfc - no problems
log notes;
104 folders examined.
1268 files examined.
397 files added to verification data file.
0 files removed from verification data file.
330 files updated in verification data file.
0 files restored.
0 file changes ignored.
have you tried restoring the VCOMM.VXD file to the original version after installing the 98se SP2 pack?
there are 3 kinds of 5699 modems, one is 5699, one is 5699A, the other is 5699B; I use the third one.
also, RedwingTech can you specify what resources your 5699 modems are using (like IRQs, memory addresses and I/O settings). Run System Information or Device Manager to get the resource settings of your modem.
See any of the following USR Support pages on the 5699 modems---
005699-00 support page:
http://www.usr.com/support/product-template.asp?prod=5699
3CP5699A support page:
http://www.usr.com/support/product-template.asp?prod=5699a
USR5699B support page:
http://www.usr.com/support/product-template.asp?prod=5699b
...and if problems continue after restoring the vcomm.vxd file, remove the SP2 pack for Win98se.
or upgrade to Win2000 or XP. I think Win2k or WinXP handles 5699 modems a little better than Win9xME systems.
or upgrade to Win2000 or XP. I think Win2k or WinXP handles 5699 modems a little better than Win9xME systems.
Thanks for all your help guys. I think this issue is dead. I've tried restoring vcomm.vxd after installing SP2 - no joy.
I took the time to play around. The 5699 ( not A or B ) works fine with no unofficial service packs. I dug up SP1 v1.6.2 had the same problem. I guess i just never noticed before.
I appriciate all the time you guys made giving suggestions.
RedwingTech
I took the time to play around. The 5699 ( not A or B ) works fine with no unofficial service packs. I dug up SP1 v1.6.2 had the same problem. I guess i just never noticed before.
I appriciate all the time you guys made giving suggestions.
RedwingTech
QUOTE (redwingtech @ Oct 15 2005, 08:27 AM)
Thanks for all your help guys. I think this issue is dead. I've tried restoring vcomm.vxd after installing SP2 - no joy.
I took the time to play around. The 5699 ( not A or B ) works fine with no unofficial service packs. I dug up SP1 v1.6.2 had the same problem. I guess i just never noticed before.
I appriciate all the time you guys made giving suggestions.
RedwingTech
I took the time to play around. The 5699 ( not A or B ) works fine with no unofficial service packs. I dug up SP1 v1.6.2 had the same problem. I guess i just never noticed before.
I appriciate all the time you guys made giving suggestions.
RedwingTech
your welcome, RedwingTech. I can assume you are really using the 5699 [model # 005699-00] and neither 5699A nor 5699B. The 5699 modem drivers are more than 5 1/2 years old and the modem I think may not be compatible with Win98 and higher versions of Windows as I've checked the 5699 modem downloads page. The 5699 drivers are only for Win95 & NT4.
I think you should dump that 5699 modem (since it is too old & maybe past its prime) and get the one I have [5699B] which should be fully compatible with the 98SE SP2 pack and the latest drivers are more than a year old. My longtime friend has a US Robotics 56k modem [model no, 5660] which is fully compatible with Win98se, 2000, ME & XP and the 5660 modem drivers are WHQL logo'ed (aka. digitially signed) by Microsoft. I bought the US Robotics 5699b modem at a computer electronics store in the summer of 2004. you should buy a newer USR modem than the one you have since newer 56k modems may be fully V.92 compliant.
-erpdude8
Did anyone ever figure out an answer for, a new user, to this problem ? Short of replacing the modem ?
Should I have missed it while reading the postings, a pointing in the right direction is appreciated.
Been awhile since last post So hoping joy
QUOTE (Fennco @ May 10 2006, 05:48 PM)
Did anyone ever figure out an answer for, a new user, to this problem ? Short of replacing the modem ?
Should I have missed it while reading the postings, a pointing in the right direction is appreciated.
Been awhile since last post So hoping joy
what kind of modem do you use, Fennco. If it is an old USR modem, you might want to get a new one or a different brand of 56k modem (internal modems are really cheap and affordable; some internal modems sold are between $10 to $30).
I no longer any dialup modems anymore as my brother got the wireless router/DSL modem from AT&T/SBC last week. now using broadband internet connection [YAY! WOO-HOO!]
QUOTE (erpdude8 @ May 10 2006, 10:24 PM)
I no longer any dialup modems anymore as my brother got the wireless router/DSL modem from AT&T/SBC last week. now using broadband internet connection [YAY! WOO-HOO!]
As a long-term denizen of the no-phone-line-modem-limited Internet, I officially welcome you! 
Happy downloading!
cjl (Optimum Boost - Upload 2.1 MBps, Download 28.4 MBps, FIOS not yet available)
[quote name='CLASYS' date='May 11 2006, 12:24 AM' post='505396']
[/quote]As a long-term denizen of the no-phone-line-modem-limited Internet, I officially welcome you!
Happy downloading!
cjl (Optimum Boost - Upload 2.1 MBps, Download 28.4 MBps, FIOS not yet available)
[/quote]
You said it, CLASYS. My brother and I are NEVER going back to dialup internet. Dialup is so last century. Broadband is the presnet and the wave of the future.
I need to explain to Fennco that the US Robotics modem drivers for model no. 005699-00 are for Win95/NT4 only and those drivers (and the actual modem itself) may not even be fully compatible with Win98, 2000 & higher versions of Windows. even a firmware update for the USR 005699-00 modem may not be good enough to work with Win98se with the unofficial 98se SP2.x pack. Therefore, it would be best to just get a newer 56k modem or even upgrade to broadband internet service such as cable or DSL since the 5699 modem drivers are never going to be updated for full compatibility with Win98/2k/ME/XP.
-erpdude
[/quote]As a long-term denizen of the no-phone-line-modem-limited Internet, I officially welcome you!
Happy downloading!
cjl (Optimum Boost - Upload 2.1 MBps, Download 28.4 MBps, FIOS not yet available)
[/quote]
You said it, CLASYS. My brother and I are NEVER going back to dialup internet. Dialup is so last century. Broadband is the presnet and the wave of the future.
I need to explain to Fennco that the US Robotics modem drivers for model no. 005699-00 are for Win95/NT4 only and those drivers (and the actual modem itself) may not even be fully compatible with Win98, 2000 & higher versions of Windows. even a firmware update for the USR 005699-00 modem may not be good enough to work with Win98se with the unofficial 98se SP2.x pack. Therefore, it would be best to just get a newer 56k modem or even upgrade to broadband internet service such as cable or DSL since the 5699 modem drivers are never going to be updated for full compatibility with Win98/2k/ME/XP.
-erpdude
My modem is USR 2974. And I've got the same problem. It disappears only if I uninstall SP...
QUOTE (Biolog @ May 12 2006, 01:25 PM)
My modem is USR 2974. And I've got the same problem. It disappears only if I uninstall SP...
Is this perhaps a vcomm.vxd problem?cjl
QUOTE (erpdude8 @ Sep 26 2005, 12:13 PM)
I also use a USR Winmodem (but model no. 5699B), and encountered a 630 error message a few times. What I did was remove the modem driver, shut down the PC, take out the USR modem and insert it into another PCI expansion slot, turn on the PC and re-installed the drivers. the modem worked flawlessly and I can reconnect after disconnecting.
maybe the modem might be inserted into an unreliable slot. try removing the modem and put it into a different slot. Good thing I've been reading my brother's computer repair book on how to change computer parts.
maybe the modem might be inserted into an unreliable slot. try removing the modem and put it into a different slot. Good thing I've been reading my brother's computer repair book on how to change computer parts.
I never had that problem.
But before getting another US Robotics 5699B modem, after a T-storm, a US Robotics 5699B I had acted possessed, Windows all of a sudden would most of the time say "There was no dial tone" or similar and refuse to even dial, even when the telephone line was fine and after reinstalling Windows!! Then sometimes, it will dial and Windows says that it's connected, but all of the web browsers fail to find any web site, no matter what!!
Obviously, that was because the modem got damaged by a spike. That was the only time that I ever had Windows refuse to dial with a US Robotics 5699B modem.
Did anyone ever figure out an answer for, a new user, to this problem ? Short of replacing the modem ?
Seems the short answer is no, replace video card.
excuse me meant to say replace modem.
The problem is, after installing unofficial windows 98 se sp, dial-up connection loses the modem after disconecting from a previos use.
So here is what happens, after doing a clean install of windows 98 se , modem works fine, install unofficial windows 98 se sp, user connects,user does thier thing, user disconnects.
After reasonable time, user tries to connect, dial-up connection reads out; Could not detect modem.It maybe in use, turned off, or installed improperly.
So close out of everything restart and open control panel, open modem, go more info everythings OK, close out of all.
Reopen control, modem, more info, get; OpenCom [title], Port already open {message}, and a default active button labeled OK
click on OK and am sent to the More Info... window which shows Port Information box and a box with modem identifier and an empty white rectangle then has another OK button click OK and sent back to Modems Properties page.
Close out restart and as with dial-up am good for one opening of modem port then must restart to close modem.
Have tried reinstalling and updating modem drivers.
While port is open phone works fine.
The above has been repeated 3 times.
Platform info: Gateway G6-350
350 Pentium II processor
160 MB RAM
formated hard drive
drivers downlowded from Gateway
Modem is; U.S. Robotics 56k Voice Win.
Seems this happened after a microsoft update, done on a previos machine at microsofts update win98 se site, back when microsoft still supported 98se.
So this may not be in the unoffical windows 98 se sp, rather a update from microsoft?
A Thanks for the welcome from erpdude8 and clasys.
Seems the short answer is no, replace video card.
excuse me meant to say replace modem.The problem is, after installing unofficial windows 98 se sp, dial-up connection loses the modem after disconecting from a previos use.
So here is what happens, after doing a clean install of windows 98 se , modem works fine, install unofficial windows 98 se sp, user connects,user does thier thing, user disconnects.
After reasonable time, user tries to connect, dial-up connection reads out; Could not detect modem.It maybe in use, turned off, or installed improperly.
So close out of everything restart and open control panel, open modem, go more info everythings OK, close out of all.
Reopen control, modem, more info, get; OpenCom [title], Port already open {message}, and a default active button labeled OK
click on OK and am sent to the More Info... window which shows Port Information box and a box with modem identifier and an empty white rectangle then has another OK button click OK and sent back to Modems Properties page.
Close out restart and as with dial-up am good for one opening of modem port then must restart to close modem.
Have tried reinstalling and updating modem drivers.
While port is open phone works fine.
The above has been repeated 3 times.
Platform info: Gateway G6-350
350 Pentium II processor
160 MB RAM
formated hard drive
drivers downlowded from Gateway
Modem is; U.S. Robotics 56k Voice Win.
Seems this happened after a microsoft update, done on a previos machine at microsofts update win98 se site, back when microsoft still supported 98se.
So this may not be in the unoffical windows 98 se sp, rather a update from microsoft?
A Thanks for the welcome from erpdude8 and clasys.
QUOTE (CLASYS @ May 13 2006, 12:30 PM)
QUOTE (Biolog @ May 12 2006, 01:25 PM)
My modem is USR 2974. And I've got the same problem. It disappears only if I uninstall SP...
cjl
2 CLASYS: How can I find it out?
These modems use a software port not hardware. I have see this problem before ,fix was to disable the com ports in the bios and reinstall. If com port in the bios is enabled and the modem is installed to that port windows thinks the port is already in use. That is why moving the modem to another pci slot works some times it installs to another port. Might also go to safe mode and see if there is any ghost modem still listed there and remove all and reinstall the modem. Myself I would get a modem with a Agere chip set or use to be lucent. If you have more than one dial up icon in the dial up folder might remove them all and make a new one. Also make sure that log on to network is disabled in the dial up properties and only tcip is check. You will find that with Agere chipset you can get more updated drivers and they will take line noise allot better.
http://www.usr.com/support/product-template.asp?prod=oem
Note the age of the drivers and USR will not ever up date them. If you look in the WINMODEM.INF file you can find out more about you modem. You can also run regedit go to local machine,enum,pci
Last Modified 02/03/99, CS, OEM R&D
Check here also.
http://support.microsoft.com/kb/q150619/
http://support.microsoft.com/kb/q191444/
http://www.usr.com/support/product-template.asp?prod=oem
Note the age of the drivers and USR will not ever up date them. If you look in the WINMODEM.INF file you can find out more about you modem. You can also run regedit go to local machine,enum,pci
Last Modified 02/03/99, CS, OEM R&D
Check here also.
http://support.microsoft.com/kb/q150619/
http://support.microsoft.com/kb/q191444/
QUOTE (Fennco @ May 14 2006, 10:19 AM)
Did anyone ever figure out an answer for, a new user, to this problem ? Short of replacing the modem ?
Seems the short answer is no, replace video card.
Seems the short answer is no, replace video card.
maybe, maybe not. replace video card? that may not be possible if the video feature is built-in the motherboard. why cant you replace the modem? replacing the video card is more expensive than replacing the modem, I guarantee that.
try disabling one of the serial or COM ports in BIOS setup but un-install the modem drivers first then reboot. If internal modem is connected to COM1 or COM3, disable COM1 in BIOS setup. if internal modem is connected to COM2 or COM4 or higher, disable COM2 in BIOS setup. now reboot to win98se and let windows redetect the modem and it'll install the modem using the COM resources that were disabled in BIOS setup. That seem to work on one of my old 98SE computers, even with the 98se service pack installed.
Also Fennco, check the actual internal modem itself. If the modem still does not work then it might have been damaged by a power spike RJARRRPCGP described in his post and should be replaced because the power spike can cause modems to malfunction.
QUOTE (erpdude8 @ May 19 2006, 08:40 PM)
QUOTE (Fennco @ May 14 2006, 10:19 AM)
Did anyone ever figure out an answer for, a new user, to this problem ? Short of replacing the modem ?
Seems the short answer is no, replace video card.
maybe, maybe not. replace video card? that may not be possible if the video feature is built-in the motherboard. why cant you replace the modem? replacing the video card is more expensive than replacing the modem, I guarantee that.
also replacing the video card 99.99% of the time does NOTHING to resolve the modem problem with 98se service pack installed. that's barely a dumb solution. changing the modem with a newer and a different brand is the more logical, more economic and more intelligent solution since many internal modems cost less than buying new graphics cards.
Resolved! Final Fix for Win98SE SP2 Modem Error 630, 2nd DUN-Connection Attempt Requiring Reboot
01. Save a copy of Vcomm.vxd file in C:\WINDOWS\SYSTEM\VMM32\ into the same folder and rename it to Vcomm.vxd.new
02. Save a copy of WINMODEM.VXD file in C:\WINDOWS\SYSTEM\ into the same folder and rename it to WINMODEM.VXD.new
03. Click on >Start>Run, type sfc.exe and >OK button to open System File Checker; and
04. Click on the button to extract a system file from the Win98se setup .cab files, specify the Vcomm.vxd file and save it into the same C:\WINDOWS\SYSTEM\VMM32\ folder.
05. Close all, properly restart, and your 2nd DUN-Connection attempt should fail again.
06. Click on >Start>Run, type sfc.exe and >OK button to open System File Checker; and
07. Click on the button to extract a system file from the Win98se setup .cab files, specify the WINMODEM.VXD file and save it into the same C:\WINDOWS\SYSTEM\ folder.
08. Close all, properly restart, and now even your FIRST DUN-Connection attempt should fail and generate a new error! (Don't panic! Apparently, this is needed to finalize the restoration of the new Vcomm.vxd file with the old one!)
09. In Windows Explorer, rename the restored, old WINMODEM.VXD file in C:\WINDOWS\SYSTEM\ as WINMODEM.VXD.old and
10. Rename the WINMODEM.VXD.new copy file in C:\WINDOWS\SYSTEM\ as WINMODEM.VXD (i.e. use the new one again!)
11. Close all, properly restart, and now your modem should work like a charm! (No more "error 630"!)
Post your successes/failures or your questions.
I wish you good luck!
Wiz
P.S. This fix is partly based on solution by erpdude8, posted on 10-10-05 on this very topic (Thank you, erpdude8 & others who tried their best to help):
"[T]ry using the original 98SE released version of the VCOMM.VXD file... stored in the Windows\System\Vmm32 folder. open System File Checker [sfc.exe] and click on the button to extract a system file from the Win98se setup .cab files, specify the vcomm.vxd file and save it into the 'Windows\System\Vmm32' folder."
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.