Modem, update drivers?

[River~]

I have a 56k pci voice modem, Rockwell/Conexant, model
number SF-1156iv R9a, with driver version 2.1.2.162.007
and have not been able to find newer drivers, or additional initialization strings, which is hard to believe because there are tons of them for just about every other model in this line.

Anyone else use this model modem, and if so, have you found an updated driver, initialization strings. I also believe this modem can be flashed for v90, anyone else aware of this?
thanks

[reboot]

It's a Rockwell/Conexant HCF chipset modem, thus a winmodem, and not "flashable", it's software controlled.
The driver you have is new enough, but not a very good one.
Try any of the 3 from my modems page, and you'll probably find that 2.1.2.135b is the best.
What init strings would you like? (what are you trying to accomplish?)

[River~]

Reboot,

thats why I was asking, as I knew it was software controlled but had no idea that meant winmodem too? I read that winmodem couldn't be flashed, but since I thought mine was not that, only software controlled, that I could take a flash, then use ini strings to invoke 56k or v90 as needed, to see which is better.

guess I was really wrong with those "ass"umptions..lol

thanks anyway,

the driver you recommend, can't get download going, won't connect...I use GoZilla so she just keeps trying, up to 99 but no luck yet.

why not the other driver versions? isn't the higher the number the newer the driver? the better the driver?
thanks~

[glc]

In this case, newer does not mean "better". The drivers since 135b have taken more and more toll on CPU resources, which is the bane of software controlled modems.

"Winmodem" is a trademark of US Robotics for their software controlled modems - but has become a euphemism for *all* software controlled modems, because the drivers require Windows.

You *can* use strings to switch them from V.90 to K56, etc. The Conexants use essentially the same command sets as their hardware controlled modems. The only real difference is that software controlled modems use the CPU to do their work instead of onboard ROM. Saves a buck this way (less components), but at the detriment of system efficiency.

[reboot]

No, newer is NOT always better.
I'll check the download link for that one.
Still want to know what init's you want, and why?

Here's a link that works:
http://www.zoltrix.multinet.pl/PUBLIC/MODEM/WIN95/212135.exe

[River~]

Reboot,

thanks for the link, it worked, appreciate that.

as to "why" I wanted the ini strings, that was BEFORE you told me that it was a winmodem, and i thought I could flash the modem, then put in a ini. string to envoke either 56k or v90. which is what I stated in a previous post.

as to ini.strings for volume, cutting down on kickoffs, not the case, understand all that.

as stated earlier, I just didn't realize that "winmodem" and "software controlled" modems were in the same category and could not be flashed, right?

thanks again,

[reboot]

Yes, a winmodem is a soft modem is a software controlled modem is a windows only modem........
Anyhow, if you find that V.90 is too fast, and you lose the connection, or it's too slow because of retrains, use this init:
+MS=K56,0
If you find that to laggy for gaming, try this:
+MS=V34,0
Otherwise, just use the 135b driver as is.

[River~]

Reboot,

the 135b modem driver will not work, no idea why? I install it the way they say to install (know how to install any way, but never the less after installing the new drivers for the modem it is not recognized and will not allow me to connect.

it really is not that big of a deal actually, I am able to connect to the 'net and with the 56k I have am connecting at 33.6, could be better I imagine but my old 28 was much slower than that. someday when cable prices come down (?) will go that route. What I would really like is big dish satelitte hookup, as I have the dish, be a few years before that is a possibility here I think.

thanks again for the comments, advice and assistance, always appreciated on this end~

[glc]

That wouldn't happen to be a factory installed modem in a Compaq, HP, e-Machine, or Packard Hell, would it? If so, the generic driver cannot be used :(

[River~]

no it's not one of those. it is a factory installed modem from Gateway. It is a Gateway Select, 600mhz,

In device manager there is a "HCFModem" line and then expanded there is PCI Modem Enumerator listed, and then the other line "Modem" where the PCI voice modem is listed, which as I said is the "SF 1156iv R9A model.

Have searched dozens of modem sites, have yet to find an updated driver for this modem, but have found sites where they say if you modem currently has this driver: 2 xxxxxxx, or similar to this, then use this driver (then they list the driver.) But in trying two, none of them have worked. I have yet to find a site that has my particular model listed and/or the specific driver version listed that I have, and a updated driver to take it's place.

like I said, no big deal, it works ok, but seeing hows I am a tweaker and such, I am always looking for new drivers to update system and tweak with things, this was one of those things :)

thanks for your input

[reboot]

Funny because Gateway has a link on their driver update page to my modems page... :confused: hmmmmm....
How about updating the PCI serial device controller using 2.1.2.135b then updating the modem itself?

[River~]

Reboot,

when you say update the pci controler device, are you refering to the pci modem enumerator?

haven't tried that, if that is what you mean then i will try that.
thanks~

[reboot]

I would remove the modem and PCI ennumerator in device manager, restart, and when prompted, install the new driver.
If that doesn't work, just go to modem properties, driver tab, update driver.
Do this for the ennumerator first, then the modem. Both drivers are included in the one you downloaded.

[River~]

Reboot,

not sure why it is not working, but it isn't :)

did as you said, removed both, rebooted, reinstalled both pci enumerator, the modem, and the wave device for the modem. the driver files from 135b were loaded, I checked both the enumerator and the modem, they were listed, but the modem would not dial my isp, received error message that modem was not installed. my isp connection did not recognize the modem.

removed isp connection, created new connection, still would not work.

not giving up, but taking a rest on this one for now....
thanks again for the assistance...

[reboot]

The drivers are installed correctly. You must now go into DUN, and either change the connection to use the new modem (see, your computer thinks it has a new modem), or just make a new connection using the new modem.
It's probably listed as a Rockwell HCF now instead of a Conexant HCF.

[River~]

Reboot,

ok, heres the situation, not necessarily in the order in which things took place.

1...removed the enumerator, modem, rebooted, let windows reinstall items, loaded new drivers for enumerator and modem, wave device for modem loaded them on it's own, and used some of the new 135b drivers. you were right, they went from being Conexant to Rockwell items.

Results: modem would dial in to isp but no dial tone, never connected, just kept showing "dialing" activity.

2...removed, enumerator, modem and isp icon in DUN, rebooted, and this time it showed all Rockwell "new devices found" and installed them, updated to make sure 135b drivers were loaded. made new isp connection through Internet Connection Wizard, as I always do.

Results: modem would dial in to isp but no dial tone, never connected, just kept showing "dialing" activity.

3...repeated the above two procedures at least three times.

Results: S. O. S. :)

4...deleted the same three items (enumerator, modem, isp connection) rebooted, same devices (Rockwell found, and reinstalled. updated drivers and went back to my Conexant 2.1.216.2.007. Made new isp connection through Internet Connection Wizard.

Results: am here now sending you this.

Consensus (party of one here) says that I have $@*&#% with this long enough, guess this is one tweak I just don't get to tweak on :)

again, your indulgence in this matter has been greatly appreciated, honest.

[reboot]

Going by your model #, it's a GVC modem.
It's either this driver: ftp://ftp.gvc.ca/gvc/modem/SF56HR19.EXE
or this one: ftp://ftp.gvc.ca/gvc/modem/SF56R21.EXE

[reboot]

Going by your model #, it's a GVC modem.
It's either this driver: ftp://ftp.gvc.ca/gvc/modem/SF56HR19.EXE
or this one: ftp://ftp.gvc.ca/gvc/modem/SF56R21.EXE
You can search for it by entering SF-1156 on this page: http://www.gvc.ca/support/downloads/DB_Manager/db_manager.cgi