TIP: Click on subject to list as thread! ANSI
echo: tech
to: Jim Holsonback
from: Charles Angelich
date: 2003-09-22 02:09:00
subject: Deal- Modem Woes

1237cffd8e65
tech



Hello Jim - 

JH> Hello, Wayne. Not quite sure why we're talking about this
JH> here vs. in emails, but your choice - - 

WC>> The USR 460 modem really does appear to be a Winmodem, the
WC>> file 

JH> You must have some error(s) at your end, Wayne. I say again
JH> that the USR Sportster Internal Model 460 is _not_ a
JH> WinModem. 

Most of 'us' have worked in a tech oriented job at one time or
another, or most of our lives. We really shouldn't use
terminology that is of no real value. "Model 460" seems to be
of little/no help when trying to locate information about this
modem. Even at USR's website the number draws a blank when
searching their webspace. I know, USR should'nt put it on the
box then ignore it in their own database but we all know this
is typical behaviour (and evil IMO). :-) 

WC>> the file to install the driver identifies it so as does
WC>> any number of hits on Google. 

I'm getting such random garbage doing a Google search using any
combination of "USR", "model 460" and
"internal" that I don't
really even care to sort them out. :-\ 

JH> Another 'negative' from here. The file named MDM3COM.INF
JH> which I emailed you has several choices of Win95 drivers in
JH> there. None of them has anything to do with any doggone
JH> "Winmodem". The proper choice there is - - "U.S. Robotics
JH> 56K FAX INT" 

This might be a part of the problem. I find at
http://www.modem-drivers.com/drivers/45/45266.htm a driver
'package' available from 'drivers.com' that includes several
files, not just the one. 

>============
>
>  Length     Date   Time    Name
> --------    ----   ----    ----
>    50890  04-17-98 15:36   mdm3com.inf
>    51105  05-25-99 20:34   mdm3comv.inf
>     2401  02-12-98 16:49   mdm3comw.inf
>    52681  04-17-98 16:56   mdmv3com.inf
> --------                   -------
>   157077                   4 files
>
>============

The above is at:
http://www.driverguide.com/guide/go2driverpg.php?id=45266 but
'free registration is required' by going to:
http://www.driverguide.com/join.htm 

JH> "Negative" on what you think you got for Google hits. Model
JH> 460 is simply not a Winmodem. 

I say again, "model 460" is not a useful designation for
checking on this at all. 

WC>> At the price I'm still happy though it seems one must send
WC>> USR a non-trivial sum to upgrade it to higher speed. 

JH> We seem to have some kind of a communications problem
JH> between me and thee, Wayne. I bought it for a 56K-X2, and
JH> it is still under warranty from my Ebay seller. I also
JH> emailed to you a program to Re-Flash it from 56K X2 to 56K
JH> V.90. No money needs to go to USR for this, so I'm clueless
JH> as to why you're veering off on that tangent. 

If the modem isn't being detected properly he may not be
able/willing to attempt to 'flash' the modem? 

JH> But our deal was "satisfaction guaranteed, or your money
JH> back", so unless I hear from you sometime fairly soon that
JH> you've had success in getting this Model 460 reflashed to
JH> V.90 and so recognized, I'll just send you a refund and a
JH> box or padded envelope with prepaid stamps, and you can
JH> just send the pooch back to me. 

Seems this is something that can be resolved. If you are going
to get more of these "Model 460's" may as well find out what
they are _really_ referred to by USR at their website and get
_all_ of the mdm3com.inf files? ;-) 

WC>> MSD doesn't see the modem in Win 3.1 nor does sysinfo in
WC>> Norton but the dialer indicates the IRQ conflict with the
WC>> LPT port when I attempt to dial so it's being seen there. 

W31 can have 'problems' with COM4 in not predictable ways. I
have some utilities to take care of that problem. Above COM4 is
very 'iffy' for DOS or W31? 

JH> So what are the jumpers set to, and what have you flashed
JH> it to? Aha, I see below that you don't know what it is
JH> jumpered to. The "drivers" I sent are for Win9x. Your
JH> Mileage in Win3.1 may vary, and I guess it does. The README
JH> file indicates that the Windows version of the flasher
JH> software I sent will work under Win3.x, but I think that
JH> won't fix much if the jumpers aren't correctly set to match. 

True, we need to know where the jumpers are at present. There
is mention of older drivers for some USR modems at their
website but being unable to tie into the "Model 460" from there
I can't say if they apply or not. 

WC>> I'm going to see about locating a JPG of the 460 modem so
WC>> I can find the jumper to enable the IRQ and port setting
WC>> program to take so I can set it to what I want which is
WC>> COM3 IRQ 4 instead of the current IRQ 5. 

JH> Will putting the modem on IRQ 4 not interfere with whatever
JH> you may have on COM1? 

I think most put the mouse on COM1 and it doesn't send many
interrupts to the CPU. :-) 

JH> Since by email you indicate you want 3 COM ports and 2 LPT
JH> ports on the 486 machine, I'm wondering what your plan is
JH> to use for an IRQ if you try to put one of those "freebie"
JH> Ethernet cards in there in order to network the 486 to one
JH> of your other machines. 

JH> Repeating - - on Model 460 I've seen, jumper settings for
JH> COM and IRQ are stencillled in white on back of the card.
JH> Maybe they aren't there on the one you got? If there and
JH> you can't read them, try a mag glass or some reading
JH> glasses. (serious, not just poking fun). 

JH> I'm expecting another Model 460 to arrive here from that
JH> same Ebay seller tomorrow afternoon. Maybe I'll have time
JH> to look at it and do some testing by TUE or so. I'll let
JH> you know. 

If either you or Wayne can come up with the _real_ model
designation that USR uses, product code?, I will try to help
locate a diagram for the jumpers. 

>
>        ,                          ,
>      o/      Charles.Angelich      \o       ,
>       __o/
>     / >          USA, MI           < \   __\__
 

___ * ATP/16bit 2.31 * 
... DOS the Ghost in the Machine! http://www.undercoverdesign.com/dosghost/

--- Maximus/2 3.01
* Origin: COMM Port OS/2 juge.com 204.89.247.1 (281) 980-9671 (1:106/2000)
SEEN-BY: 633/267 270
@PATH: 106/2000 633/267

SOURCE: echomail via fidonet.ozzmosis.com

Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.