oem32.inf correct for Modem Blaster?

[Mike Collins]

I am having intermittant problems (multiple dials necessary to
connect) with my Modem Blaster DI5633 and WinXP Pro. I have a line
from my connection log:

Modem inf path: oem32.inf

'oem32.inf' sounds like a default file. I see other log postings
and other modems seem to have a customized .inf file.

Does anyone know if this is the correct file for my modem?

Thanks,
Mike C.
-------
I keep trying to find a life of my own, apart from you.
DC Talk/Charlie Peacock, In the Light.
http://risensystems.com/ra/itlbegin.rm

[Art Jackson]

.inf files are nothing but text files. Find it in C:\windows\inf or
C:\windows\inf\other and open it up. See if your modem is listed in the
file. It probably is, or windows would not be using it. Also if the
modem is listed correctly in device manager, that's a good indication
the .inf file is correct for your modem. Many times a generic .inf file
will cover many modems built around a particular chipset. Good luck.

--
Art Jackson W4TOY Owensboro, KY USA
Life is God's open book test. In order to pass,
you must open His book to find the answers.

[Mike Collins]

Right. Yes it has my modem in it. From the sounds of the name, I
thought that it was a generic 32 bit inf file. But looking in
Windows\inf, there are many oemxx files, and that number just
happend to be 32. Thanks.

[svt]

I believe the correct file is OEM3.INF for the 5633. If you still have the
time to get a refund, go to the store and return this modem as soon as you
can. It is the biggest piece of crap ever put out there. Creative refuses
to acknowledge there is anything wrong with it. I have received literally
dozens of e-mails from people with similar problems. Creative will give you
a thourogh runaround and blame your PC. I have heard from some others that
if you run the generic Connexant HCF modem driver it works much better.
Unfortunately, it does not run in V92 mode and it also looses the other
features such as voice and fax. V90 can be significantly slower. I don't
believe it is OS specific but I do know it fails frequently under Win2000.

You can verify that the modem is the problem under Win2000 by running System
Info (mmc.exe) tool and ping the serial ports. Don't know what package that
tools comes from. About one out of 4 attempts to polll the modem will fail.
When it fails to dial the system freezes. When it actually rings the line,
almost always the first connection fails. I have no clue what is wrong
except Creative makes a horrible product.