 |
 | Home | Contact Us | FAQ | Search & Site Map | Link to Us |
 | Sign In | Join | Other 45 Sites in Network |
Windows Forum / Windows 98 / Internet / September 2004HSF modem on WIN98 installs but fails to operate
I have a Dell 4550 2.4 Gh P4 PC designed for use with Windows XP. Windows XP SP2 is doing just fine including both installed modems. However, it does not fully support my JamCam digital camera software (proprietory download twain program) or my HP Deskjet 882C Printer (no fully functional HP driver for Windows XP). Thus, I installed WIN98SE on a spare drive (not dual boot; but, capable of booting either XP disk or WIN98 disk). After a lot of adjustments, I seem to have everything on the WIN98 system working except the modems. I did have to disable two extended portions of ACPI (in device manager) in order to get my nVidia GeForce4 MX420 64MB AGP4 graphics board to operate. Also have integrated Intel 10/100 LOM ethernet and pci D-Link WIFI card installed. I have two V92 HSF modems (both are fully functional on WIN XP and I am using WIN98 drivers on the WIN98 side). If I try booting WIN98SE with my Conexant modem installed the boot fails (not concerned with this one for now). My other modem (the one I actively use on XP) is an Intel 536EP. It installs just fine on WIN98. The modem diagnostics say all is good; but, it has no hardware id and thus is not accessible by the DUN program my ISP, JUNO, provides. Therefore, I have two problems. One is to fix the modem situation. Alternatively is to find a way to update WIN98SE without using Windows Update (I believe internet access is required for Windows update). Any ideas ? There could be a FREE Google invite for someone with the solution to both problems. Hope this makes sense to someone, Tom ________________________________________________________________________________ FURTHER CLARIFICATION: 1) Both modems work fine when I boot my WIN XP drive (no forcing needed). 2) I am using drivers designed for WIN98 when I boot the WIN98 drive for both modems. I am using drivers designed for WIN XP for both modems when I boot the XP drive. 3) The Intel 536EP installs fine and the modem diagnostics (Control panel;Modem;Diagnostics) indicate there are no problems. 4) Other software (DUN) cannot address the 536EP modem due to the lack of a hardware id. Ie. When I go to modems in control panel, no modems are shown n the window where modems are usually listed. However, the diagnostics button is there and does access the 536EP successfully. The missing modem name in that window seems to be the only problem with the 536EP modem. There is an error message on the modems page saying the hardware id is missing. I have examined the install and the id is there. Not sure where else it needs to be. I imagine in the regustry somewhere. 5) Telnet addresses it fine because it uses the comm port (3) address instead of its hardware name. Hardware name is ==> " Intel? 536EP Modem " on WIN XP. >I have a Dell 4550 2.4 Gh P4 PC designed for use with Windows XP. Windows XP >SP2 is doing just fine including both installed modems. [quoted text clipped - 52 lines] >instead of its hardware name. >Hardware name is ==> " Intel® 536EP Modem " on WIN XP. I can't help except to say that a failed install of your Conexant HSF modem may be upsetting your Intel HaM. Try completely uninstalling your HSF modem. FWIW, the registry key for modem parameters is: HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\Modem\000n Some HardwareIDs are located at this key: HKEY_LOCAL_MACHINE\Enum What do you see at Control Panel -> System -> Device Manager -> Modem? Try running the built-in hwinfo utility. Go to Start -> Run and type "hwinfo /ui". - Franc Zabkar  SignaturePlease remove one 's' from my address when replying by email. How can telnet use the COM3 port addresses ? > >I have a Dell 4550 2.4 Gh P4 PC designed for use with Windows XP. Windows XP > >SP2 is doing just fine including both installed modems. [quoted text clipped - 70 lines] > > - Franc Zabkar To be quite honest with you, I am not really certain. I do know that I used the Telnet application referred to as Hyperterminal. I did set up a new connection and in doing so found a way. I do also remember that I was using the WIN98SE modem troubleshooter and that it was around 4 in the AM and I was very, very tired. Sorry. I think Hyperterminal is in WIN98 Help or in the WIN98 Resource Guide. Also seem to remember that there used to be a better version of Hyperterminal on the web, for free, than the one shipped with WIN98. | How can telnet use the COM3 port addresses ? > To be quite honest with you, I am not really certain. Yes. > I do know that I used > the Telnet application referred to as Hyperterminal. telnet and hyperterminal are two entirely different animals although both can do terminal emulation. Read the RFC for tenet and see what it really is e.g. it does not have file transfer capability (that's in ftp) like Hyperterminal does. Hyperterminal is a terminal emulation program similar to the old Kermit, Procomm, etc. > I did set up a new > connection and in doing so found a way. I do also remember that I was using > the WIN98SE modem troubleshooter and that it was around 4 in the AM and I Not the best time to work on a system <vbg> > was very, very tired. Sorry. I think Hyperterminal is in WIN98 Help or in > the WIN98 Resource Guide. Also seem to remember that there used to be a > better version of Hyperterminal on the web, for free, than the one shipped > with WIN98. There was indeed. Why are you focused on hyperterminal ? > | How can telnet use the COM3 port addresses ? >Why are you focused on hyperterminal ? If the modem works with Hyperterminal, but not with DUN, then that can narrow down the source of the problem. - Franc Zabkar SignaturePlease remove one 's' from my address when replying by email. That would show the modem hardware is OK but I thought this poster originally thought the software was talking to a hardware port address. Confused me. > >Why are you focused on hyperterminal ? > > If the modem works with Hyperterminal, but not with DUN, then that can > narrow down the source of the problem. > > - Franc Zabkar I think you are a bit off topic. However, if you logon to a Windows XP machine click start then help then search on Telnet; possibly you are capable of understanding why I have drawn a relevance between Telnet and Hyperterminal. I haven't had the need or desire to use either of them for a good number of years and possibly will not for many more. However, this is totally off topic and I would prefer focusing on the matter at hand. That would be getting a modem to work on this WIN98 system. I simply tried to answer your question. For that SFB, I do apologize. ----------------------------------------------------------------------------- | > To be quite honest with you, I am not really certain. | [quoted text clipped - 28 lines] | | > | How can telnet use the COM3 port addresses ? Thanks Franc, I have been suspecting a problem with the Conexant driver entries. Conexant has a program that is supposed to remove the old driver; but, it also installs a different driver. That hasn't helped. I originally installed Conexant drivers from my Dell drivers CD. I think it was a WINME driver. The replacement I tried to load was a generic HSF one for WIN98 from Conexant. I have, when playing with the Conexant on WIN98, had mice show up in the control panel;modem window. It seems to really confuse the issue. I have been removing the Conexant physically as well as in device manager when testing with the Intel. Don't know that it matters; but, the Conexant is HSF and the Intel appears to be HCF. I ran a utility from Conexant that identified the chips. I bought the Intel modem on Ebay and the seller disappeared. It is from a firm in China. I have misplaced the CD that came with it and thus am using the Intel site as a source for the drivers. The utility ids the modem as pure Intel. WINXP and WIN98 modem diagnostics also do. I really do not know what the registry modem entries should look like. I had looked at the ENUM location you mentioned and the entries all looked okay to me ... hardware id and modem name included. I will look at the additional location you mentioned as soon as I get a chance to do so. The Intel modem looked fine in device manager. I have not had time to get back on WIN98 to evaluate it any further. When I get time, I will look more closely at the items you have mentioned. Wish I could compare the XP registry entries to the WIN98 registry; but, I think they may be like apples to oranges in comparison. Do you know if they are supposed to be similar ? Tom ----------------------------------------------------------------------------- | >I have a Dell 4550 2.4 Gh P4 PC designed for use with Windows XP. Windows XP | >SP2 is doing just fine including both installed modems. [quoted text clipped - 70 lines] | | - Franc Zabkar >Thanks Franc, > >I have been suspecting a problem with the Conexant driver entries. Conexant >has a program that is supposed to remove the old driver; but, it also >installs a different driver. I don't understand. If you physically remove the Conexant modem, and then run the uninstall utility, why would a new driver be installed? > That hasn't helped. I originally installed >Conexant drivers from my Dell drivers CD. I think it was a WINME driver. The >replacement I tried to load was a generic HSF one for WIN98 from Conexant. >I have, when playing with the Conexant on WIN98, had mice show up in the >control panel;modem window. I'm at a loss to explain this. Perhaps it has something to do with the fact that softmodems install their own serial port driver, and some mice are serial devices? > It seems to really confuse the issue. I have >been removing the Conexant physically as well as in device manager when >testing with the Intel. > >Don't know that it matters; but, the Conexant is HSF and the Intel appears >to be HCF. HCF is Conexant's terminology for its controllerless modem line. Intel's controllerless modems are referred to as HaM, ie Host Accelerated Modem. > I ran a utility from Conexant that identified the chips. I bought >the Intel modem on Ebay and the seller disappeared. It is from a firm in [quoted text clipped - 15 lines] > >Tom I haven't had much to do with XP, but IIRC many entries are similar. The key name may be different, though. I would use regedit to search for appropriate text strings and export any relevant registry keys to a text file. You can then analyse the data with a text editor. - Franc Zabkar SignaturePlease remove one 's' from my address when replying by email. > HCF is Conexant's terminology for its controllerless modem line. > Intel's controllerless modems are referred to as HaM, ie Host > Accelerated Modem. This is directly helpful. But what is an HSF Modem ? -- under which my new modem identifies itself as AOpen PCI Modem Enumerator (and separately in / Device Manager as AOpen FM56 SLM which is what is printed on its card . . . ) This is an old unit, swapped for an FM56 PLC (Controllerless) which simply never behaved right. Is there a reliable web site that answers these sort of questions e.g. defines TAPI. (Agenda: try to get WinFax.v.8 to recognize this modem. The instal routine tests the modem as OK, then asks my selection of items from a blank menu. Is TAPI a feature of controllerless modems that the SLM simply lacks?) SignatureDon Phillipson Carlsbad Springs (Ottawa, Canada) What is your processor speed ? TAPI is the MS Telephony API. Take a look at: http://www.modemsite.com/56k/soft56.asp > > HCF is Conexant's terminology for its controllerless modem line. > > Intel's controllerless modems are referred to as HaM, ie Host [quoted text clipped - 18 lines] > of items from a blank menu. Is TAPI a feature of > controllerless modems that the SLM simply lacks?) >> HCF is Conexant's terminology for its controllerless modem line. >> Intel's controllerless modems are referred to as HaM, ie Host >> Accelerated Modem. > >This is directly helpful. >But what is an HSF Modem ? HSF is Conexant's terminology for its softmodem line. My understanding of the different chipset designs is as follows. There are three types of internal modem, "soft", controllerless, and "hard" (controller based). Softmodems have a DAA (telephone line interface), controllerless modems have a DAA and DSP (digital signal processor), and "hard" modems have a DAA, DSP, and controller. Among other things, a modem's controller handles AT command parsing, UART emulation, data compression and error correction. These functions do not impact significantly on the host CPU. OTOH, the functions of a DSP are highly CPU intensive, so a softmodem (which emulates the DSP in software) may impact noticeably on CPU performance. Examples of softmodem chipsets are PCtel HSP, Motorola SM56, Smartlink, and Conexant HSF. Controllerless examples include Conexant HCF, Intel HaM, Lucent Win Modem, and USR Winmodem. - Franc Zabkar SignaturePlease remove one 's' from my address when replying by email. |
Reply to this Message |
 Sign In
 Join
 My Latest Posts My Monitored Threads My Blog My Photo Gallery My Profile My Homepage Start New Thread Enable EMail Alerts Rate this Thread
|
©2008 Advenet LLC Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.