Apologies in advance if this is an old issue, but just stumbled on this ng!
Didn't find any reference to my problem in a ng search, tho.

I'm randomly getting a "program error" box with the error message
"3cmlink.exe has generated errors" when I'm online, then must reboot my
win2000 pro machine to get it to reinialize the modem. This typically
happens after I've been on for varying lengths of time, not at initial
startup or connection or anything like that. I'll be working along just
fine, then boom! It dies Everything else on the machine seems to be
working OK, tho, other than the fact that it's no longer actually connected
to the 'net. The browser doesn't close, nor do I get any other messages or
indicators of a problem. It says there's a log entry, but I'm not sure where
that would be. I've looked in the events log, but saw nothing relevant.

I've done a little research on this, but about all I could find was that
this may indicate some kind of device conflict. I'm new enough to win2K that
I'm not sure how to troubleshoot this. I'm stuck with this modem, which
otherwise works fine, btw, as replacing it isn't an option at this time. I
did NOT have a problem with this on an earlier Win98 machine, btw, with a
different winmodem.

TIA for any suggestions.
--
Elaine Pack, Web Analyst
Charlottesville, VA
elaineATpackwebs.net

On Wed, 1 Oct 2003 08:52:25 -0400, "EPPack" <epack@packwebs.net>
wrote:


http://groups.google.com/groups?selm...&output=gplain

See if you can get an updated Win2k driver for your modem. If you can
post the modem model number, then folks like Hooda and others can
probably zero in on the exact driver you need at the USR site. If
it's an OEM modem, then we can try to get a link to the right driver
based on the modem number and other information about your machine,
such as who manufactured it.

Gary E

|Gary A. Edelstein
|edelsgNO@SPAMyahoo.com.invalid (remove NO SPAM and .invalid to reply)
|"We have met the enemy and he is us." - Walt Kelly's Pogo

Hi Gary! Any help you can find for me will be *greatly* appreciated, I
assure you!

It shows up in the properties as a "US Robotics 56K fax win int" on COM 4.
The machine is a '97 Gateway, but was fairly recently reloaded with Windows
2000 Pro, current system version is 5.00.2195 SP4 with 256MB RAM and tons of
disk. The modem is an internal OEM, but was given to me as a replacement for
my original one that had just been fried by a lightning storm at that time,
essentially as a favor We are an IT shop, so we have a LOT of loose stuff
like that laying around. I'd already tried for a driver at USR, but couldn't
find anything relevant to that product ID other than "built into the OS".
Gateway won't support it either, because the system is LONG out of warranty,
and no longer loaded with the shipped OS (win98), and the new one I did not
get from them. A query to USR just came back with "it's built into the OS
now so we don't support it".. Well, duh, I'm sure, but there is still a
buried driver file(s) out there.

Here's what I get from the USR Modem Identification Wizard:

Product ID :265699A
Model Number :
Serial Number :
ATI3
U.S. Robotics 56K Fax Win Int RS Rev. 4.01.021
OK
ATI7
U.S. Robotics 56K Fax Win Int Configuration Profile...
Product Type US/Canada Internal
Product ID 265699A
Data Option V.32bis,V.34+,V.90,V.80
Fax Option Class 1/Class 2.0
Line Options Caller ID, Distinctive Ring
DSP Freq 34.0Mhz
DSP Ram 32K
Code Date 04/20/2000
Code Rev 4.01.021

You know, I also have a random problem where the entire system just
*freezes* with absolutely no warning messages or anything and only a power
restart can unfreeze it, but this only seems to happen when I've been online
for a while, far as I can tell (it's *always* online, tho I wonder if
this might also be fixed with a newer driver?? Hmm.

BTW, there is nothing at all in any of the event logs when the modem goes
down, so I'm afraid the link you gave me didn't help However, I do
appreciate it!

Thanks!
elaine




"Gary A. Edelstein" <edelsgNO@SPAMyahoo.com.invalid> wrote in message
news:da2mnvo51gqusalesslmv3175hq6jlbmkj@4ax.com...

"EPPack" <epack@packwebs.net> wrote in message
news:blg1jb$bkod4$1@ID-127512.news.uni-berlin.de...
OEM version of the 5699A Winmodem but I didn't find out who uses the "26"
code.

You might want to look at this page:

http://www.usr.com/support/doc-popup...log/3cmlink.ht
ml

Also, consider going to this page:

http://www.usr.com/support/s-main-menu.asp

Selecting 56K/33k Internal then Winmodems then 3cm5699A. You will see
several selections, one of which is the link I provided above. Remember,
however, that these are for the non-OEM version and that any drivers or
updates found may not work for you. If we could find out who the "26" code
is for, you might be able to get something from that company's support
pages.


--

Hooda Gest
"The only thing I do immediately is procrastinate."

Hi Hooda! What typically would the "26" refer to? The OEM PC vendor? If so,
that's almost certainly Gateway, since we were a 100% Gateway shop at that
time, and the modem came from one of those machines (it shipped with a
modem, but it was not given to the eventual user). There is nothing on their
site relating to this modem but I did check with them at one point, tho, and
they refused to help me because I no longer had the shipped OS, and that
effectively voided the warranty. Of course the warranty was already long
since expired but still. The most I got out of them after whining a bit
was that since I was now using windows 2K, the driver was built into the
OS and I needed to talk to Microsoft. MS was unresponsive since I didn't get
my new OS directly from them and I found nothing in a site search
relating to this modem. Also, I'd already done the disable of the fax
service as mentioned in that link (I never used it anyway). Who's on first?


I will try the 2K drivers mentioned on that link but will that mess up my
modem if it doesn't work for it, do you think? It at least works now, so I
don't want to create a new problem! Would reinstalling the modem go back to
the original drivers in that case?

Thanks!
elaine


"Hooda Gest" <Be@One_With.Calm> wrote in message
news:qmOeb.166624$3o3.12032795@bgtnsc05-news.ops.worldnet.att.net...

"EPPack" <epack@packwebs.net> wrote in message
news:blh55r$c60sl$1@ID-127512.news.uni-berlin.de...
According to the USR website, Gateway's code is "87". Not that it can't have
had a "26" at some time, just that I can't get that confirmed.

It should. The drivers, since this is a Winmodem, are loaded from the HD and
are not contained within the modem. You may want to back things up (I
certainly would) before trying it; Registry, driver folders, etc. That way,
you can put everything back the way it was. Additionally, you should be
aware that the system may not match the drivers up with that modem and not
use them with it.

And did you read the Note with that procedure?

"If the error does not disappear, individually set each service to "manual"
until you find the corresponding service that conflicts with the 3cmlnk.exe
file."

So, it may not be just the Fax software but something else.

--
Hooda Gest
"In a New York minute, everything can change..."

"Hooda Gest" <Be@One_With.Calm> wrote in message
news:xHWeb.166901$3o3.12066006@bgtnsc05-news.ops.worldnet.att.net...
Hmm, dunno. I don't really know the age of this particular modem,
unfortunately. It could have been sitting around the office for some while,
for all I know There is a possibility it *might* be from Dell, come to
think of it, since we have very recently changed over to Dell equipment. I
had thought the modem was older than the switchover, but maybe it wasn't,
just dunno!

Dang! If the driver is "contained" in the OS, wouldn't it still look to some
specific file for the driver? <sigh> nothing's easy

I did, but I know enough about win2K that some of those services are most
likely essential to the system, right? And if they are disabled, *nothing*
would run? Fax service makes sense to me since it is modem-related, but many
of those services aren't. Then again, I guess they could still conflict, but
the real trick is to know *which* services to set off without hurting the
remainder of the system.

elaine

"EPPack" <epack@packwebs.net> wrote in message
news:blien9$cpkj0$1@ID-127512.news.uni-berlin.de...
Here's what USR shows as examples:

66 Generic OEM - no manufacturer

67 Micron

83 Dell

87 Gateway

But, as I said, the info may not be complete.


Yes, you have to uninstall the modem, clean out any files in a folder
created for it (I believe there will be one) and then re-install the modem
with the new software/drivers. You would also need to delete (or rename) the
two files; drvdata.bin and drvidx.bin in the windows/inf folder.

I would limit it to any services which might use communications services or
a device sharing the IRQ the modem is using.

That is another thing to consider; conflicts. The port the modem emulates is
one that should not otherwise exist in the system. That is, if the modem is
on Com1 then Com1 should not exist in the system prior to installing the
modem. If the modem is on a previously unassigned port then the IRQ may be
shared with some other peripheral and that can create some conflict. Check
the IRQs and the com port used.

I had an odd situation once that may or may not pertain to yours. I had a
Winmodem (5683) which somehow got tangled up with the video card IRQ
assignments. I don't recall the exact IRQs that were used but it was
something like this:

The BIOS assigned the modem to IRQ 5 and the video card to IRQ10.
Win98 assigned them the opposite. That is, the modem got IRQ10 and the video
card got IRQ5.

The end result was random lockups. When I forced the same assignments in
both the BIOS and Win98, the trouble went away. I'm a little ashamed to
admit it took me quite some time before I noticed the IRQ conditions.


--

Hooda Gest
"The only thing I do immediately is procrastinate."

Just happened to think about something else. When our support guys installed
win2K on my machine, they also added a network card and configured it for
our network, so that if I needed to bring it in again, it would already be
set up (for backups, etc). That said, I've *never* done that, and removed
the card, rightly or wrongly. I also didn't do anything else re the network
config. I kinda doubt that this is the problem, but com is com, and maybe
there is some sort of conflict relating to this? Unfortunately, I don't know
how to check this in win2K.

Oddly, I see 2 icons in the CP for network config, one says "Network and
Dialup connections" and the other just says "Network connections". Both go
to the same place, where there's an option to "make a new connection". And
to muddy the waters further, I'm forced to use ao-hell on this machine
('cause I can't pry it out of my husband's grip). I'm well aware it has its
own major peculiarities, but it was working essentially OK before w/win98.
*I* use "real" apps for my own 'net activities (Eudora and IE etc) tho.

I remember there was a place in 98 to get to the networking options to check
the network adapters etc, but I'm not sure how to do that in 2K. I had
thought it was under the network connections icon mentioned above, but nada.
It may not be enabled in some way, tho, I dunno. And yes, I am signed on as
Admin.

elaine
who feels stupider and stupider by the minute

"Hooda Gest" <Be@One_With.Calm> wrote in message
news:AX7fb.167593$3o3.12144597@bgtnsc05-news.ops.worldnet.att.net...

"EPPack" <epack@packwebs.net> wrote in message
news:blk9qa$dcsk7$1@ID-127512.news.uni-berlin.de...
Don't feel stupid. I have no direct knowledge about Win2000 either,
especially in this area.

I did find this at:
http://www.microgate.com/us/manuals/...l/mgwn21rf.htm


"Configure Network Options (Windows 2000)

----------------------------------------------------------------------------
----

Select Control Panel from Settings of Start menu.

Open Network and Dialup Connections.

Open the Local Area Connection icon associated with the WAN virtual adapter.
Selecting each connection icon displays the associated device on the left
side of the window.

Configure networking options as necessary (TCP addresses, etc). See the
Windows documentation for more information on configuring network connection
options.

Click OK to close connection options."

Doesn't tell you much, though. You need TCP/IP enabled and its should be
bound to Dial Up Networking. But without a network card, I don't know what
else you might need.

I don't know if this is associated with the problem either. It would be
helpful if someone with a bit more knowledge about W2K chimed in...


--
Hooda Gest
"In a New York minute, everything can change..."

But I don't SEE any of that! The ONLY thing in Network and Dialup
Connections is an icon for "Make New Connection". I don't know why I'm not
seeing any of the local area connection or adapter etc info. I remember when
I was using win98 I could see/modify the various TCP/IP and adapter and
bindings, etc etc, but then, at one time I used to have a pure (non-aohell)
dialup local ISP. When the machine was reloaded with 2K, and all I had
available was the aol adapter (that came with that install) I've not seen
the bindings config et al since then. I don't know how to enable TCP/IP on
this system, nor if it should even BE enabled.

I agree, if someone with a LOT more knowledge of 2K would step in here, that
would be terrific!

elaine

Jack, I sent you a private msg about this, but the ng msg you quote here
shows as not available.

If the msg you quoted states to r/click on the "network and dialup
connections" or the "make new connection" icons, it is not working for me.
All that shows up is "open" or "make shortcut". Clicking on open just tries
to set up a new connection to some ISP or whatever, which I'm fairly sure
isn't what I need to do.

I'm wondering if because of the way my system was set up, I may not have
dialup networking installed. I know how to get that in win98, but I thought
that was built into 2000? Yes? No?

elaine

"Jack D. Russell, Sr." <jackru$$ell2@notmail.com> wrote in message
news:blmjqc$duip2$1@ID-120468.news.uni-berlin.de...
Re: news://www.news.cis.dfn.de/bll2bc$dn196$1@ID-127512.news.uni-berlin.de

In XP, right click on the individual connetoid. click "Properties" and go to
the "Networking" tab. I'd assume that it should be the same with Win2000.
--
Jack

??>> Open Network and Dialup Connections.
E> adapter.
??>> Selecting each connection icon displays the associated device on
E> But I don't SEE any of that! The ONLY thing in Network and Dialup
E> Connections is an icon for "Make New Connection". I don't know why
E> I'm not seeing any of the local area connection or adapter etc info.
E> I remember when I was using win98 I could see/modify the various
E> TCP/IP and adapter and bindings, etc etc, but then, at one time I
E> used to have a pure (non-aohell) dialup local ISP. When the machine
E> was reloaded with 2K, and all I had available was the aol adapter
E> (that came with that install) I've not seen the bindings config et
E> al since then. I don't know how to enable TCP/IP on this system, nor
E> if it should even BE enabled.

E> I agree, if someone with a LOT more knowledge of 2K would step in
E> here, that would be terrific!

E> elaine

E> for
??>>> our network, so that if I needed to bring it in again, it would
E> be
??>>> set up (for backups, etc). That said, I've *never* done that, and
E> removed
??>>> the card, rightly or wrongly. I also didn't do anything else re
E> maybe
??>>> there is some sort of conflict relating to this? Unfortunately, I
E> go
??>>> to the same place, where there's an option to "make a new
E> And
??>>> to muddy the waters further, I'm forced to use ao-hell on this
E> w/win98.
??>>> *I* use "real" apps for my own 'net activities (Eudora and IE
E> adapter.
??>> Selecting each connection icon displays the associated device on
E> connection
??>> options.
E> what
??>> else you might need.
E> shop
??>> at
E> come
??>>> to
E> built
??>>>> into
E> I
??>>>> didn't
E> the
??>>> fax
E> Who's
??>> on
E> should
??>>> be
E> rename)
??>>> the
E> hurting
??>>> the
E> services
??>>> or
E> modem
??>>> is
E> the
??>>>> modem. If the modem is on a previously unassigned port then the
E> may
??>>> be
E> had
??>> a
E> in
??>>>> both the BIOS and Win98, the trouble went away. I'm a little
E> to
??>>>> admit it took me quite some time before I noticed the IRQ

I ran a search on my system for any .inf file that contained the string
265699A and turned up just one, Mdm3cPci.inf Now I'm not sure if this is
actually the right install file, as a search at driverguide.com shows it as
being for a 33.6 modem numbered 0056867. Don't ask me why MY version of this
file has MY modem product ID inside of it I also found a file in my winnt
folder that was a modem log for my modem! Here's some selected lines:

10-02-2003 21:45:31.995 - File: C:\WINNT\system32\unimdm.tsp, Version
5.0.2195 - Retail
10-02-2003 21:45:31.995 - File: C:\WINNT\system32\unimdmat.dll, Version
5.0.2195 - Retail
10-02-2003 21:45:31.995 - File: C:\WINNT\system32\uniplat.dll, Version
5.0.2195 - Retail
10-02-2003 21:45:32.125 - File: C:\WINNT\system32\drivers\modem.sys, Version
5.0.2195 - Retail
10-02-2003 21:45:32.145 - File: C:\WINNT\system32\modemui.dll, Version
5.0.2195 - Retail
10-02-2003 21:45:32.165 - Modem type: U.S. Robotics 56K Fax Win Int
10-02-2003 21:45:32.165 - Modem inf path: mdm3cpci.inf
10-02-2003 21:45:32.165 - Modem inf section: Modem1807_2K

Now, noting the comment above about the 33.6 I'm not sure I know how to
interpret all this, but I also turned up a mention of file mdm3cpci.inf in
my registry coupled with another string value for 265699A. Does any of this
help? The date on the file is 4/2000. BTW, I sent a help request to USR
asking what the "26" refers to, plus another asking who is the OEM vendor
for the 265699A, but so far, the silence is deafening...

elaine

"Hooda Gest" <Be@One_With.Calm> wrote in message
news:4hjfb.162873$0v4.12270141@bgtnsc04-news.ops.worldnet.att.net...

I did a little wandering around on the USR support site, hoping to glean
some useful info. I found this page but it pertains to non-OEM, as far as I
can tell..

http://www.usr.com/support/downloads...asp?prod=s-win

However, it does not have the install files for W2K and the non-OEM version
of your modem. That bothers me. There is a Win-NT package and that may be
useful for "stare and compare" purposes.


Doing a Google on "265699a", I came up with this page:

http://www.modem-drivers.com/drivers/19/19019.htm

I also checked a Russian link and came up with a blank, though it had a
category for it.

As far as I can tell, there are no available drivers for this model and W2K,
though there are some for NT, apparently, and it is often suggested that NT
drivers be tried where W2K drivers are not available. I still can't find the
specific ones for NT and the 265699a, however except for the first link I
gave you.


--
Hooda Gest
"In a New York minute, everything can change..."




"EPPack" <epack@packwebs.net> wrote in message
news:blntcj$egd8j$1@ID-127512.news.uni-berlin.de...

I finally (mine sent 10/2!) got a response back from USR today (10/13).
Here's the relevant part of the exchange:

ME: Trying to find out if my OEM modem is upgradeable to V.92, but the
number of models with very similar product codes is bewildering. Your Modem
ID Wizard identifies mine simply as 265699A but there are a number of modems
shown on your site, including 3CP325699A, 3C9265699A-VAR20, 3CP5699A-B,
3C95699A, 005699-B0, 005699-50, 005699-00. Are any of these numbers the same
as my modem? Can mine be updated?

USR: I can't say specificly for your OEM modem, we do not provide any
support or upgrades for OEM modems. The support/upgrades come from the
vendor who you purchased it through. But from the product ID you listed the
3CP5699A-B would be the one you'd want to try if any. I definitly suggest
contacting your OEM vendor to see if they have an upgrade for it first
though.

Me again, now I don't know if this helps any, but reading between the lines,
whoever made that ID he mentions must be the one that made my
modem.Obviously I don't HAVE an OEM but this is progress, I guess. I'll
try upgrading the modem as he suggests and see if that helps any. Still
waiting on a response on the Product ID prefix question

elaine


"Hooda Gest" <Be@One_With.Calm> wrote in message
news:K8Wfb.165156$0v4.12474530@bgtnsc04-news.ops.worldnet.att.net...