| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 1405.1 | Sportster name is like a Brand name | UNIFIX::HARRIS | Juggling has its ups and downs | Wed Aug 21 1996 18:43 | 17 |
| 1405.2 | Bad mistake .... | SLOAN::HOM | | Fri Aug 23 1996 15:16 | 167 |
| 1405.3 | | ACISS2::LEECH | Terminal Philosophy | Fri Feb 28 1997 13:55 | 52 |
| I have a problem with a USR Sportster 33.6 modem (with the X2
technology), mainly that the best I can do is get it to dial but it
never actually connects (you get the screachy noises, but then
nothing).
Here's what I've tried:
1. Tried following the directions. Took off the jumpers and let Win95
detect it, then chose the drivers from the menu, as directed.
Win95 finds it, knows exactly what it is, but when I tried to use it,
Win95 could not find the modem (the message was "modem not hooked up or
is being used by another application). Needless to say, the modem WAS
indeed hooked up, and was not subject to use by any other application
(using the <control> <alt> <delete> combo, I brought up all
applications currently running, and shut down everything that could
even remotely be related to COM2 - where the modem was installed).
2. Went into the BIOS to disable COM2. COM2 was already disabled.
Reboot... same problem.
3. Set jumpers on modem to COM2, IRQ3, manually. Modem is detected,
Win95 installs it on COM4 (??), modem dials out but does nothing but
screach then go silent.
4. Delete all modem software. Del all old and new modem installs.
Reinstall USR 33.6 via directions in maual. (See 1. for results)
5. De-install modem once more. Put jumpers back on. Check BIOS
(nothing has changed). Install modem (Win95 puts modem on COM4).
Modem dial out but does not connect (screachy noises, but no sign that
it is actually communicating with the other modem).
Any other suggestions before I call USR to see if I have a defective
modem? Is Win95 on cyber-drugs or something? I'm completely lost. I
don't know what else to try (and since it's my home system, calling USR
in the wee-hours is unlikely to result in finding support; I'll have to
call them during the day and tell them what I've already done and hope
they have a suggestion I can try when I get home).
At this point I'm not sure whether it is the modem itself or Win95
screwing things up (or a sinister third option that elludes me).
Thanks for any suggestions!
-steve
|
| 1405.4 | | SKYLAB::FISHER | Gravity: Not just a good idea. It's the law! | Fri Feb 28 1997 14:45 | 10 |
| Which IRQ does Windows PnP put it on when it hits COM4? Hopefully not 2 (which
is the "official" IRQ for COM4, I think, but is also what is used for COM1).
I use COM4/IRQ5.
Also, do you have the latest .ini file for USR? You can get it from the USR
BBS or (I think) their web site. The default .INI files that came with W95
don't have the exact models that USR now sells. Sigh.
Burns
|
| 1405.5 | | ACISS2::LEECH | Terminal Philosophy | Mon Mar 03 1997 09:48 | 7 |
| I'm not sure what IRQ PnP sets it at. I'll see if I can get it to use
IRQ5. I'll check out USR's webpage, too. I didn't know that the .INI
files for Win95 were not completely compatible with the newer USR
modems (my modem was a Christmas present, so it was likely bought in
November or December).
Thanks.
|
| 1405.6 | | SKYLAB::FISHER | Gravity: Not just a good idea. It's the law! | Mon Mar 03 1997 12:37 | 8 |
| > files for Win95 were not completely compatible with the newer USR
> modems (my modem was a Christmas present, so it was likely bought in
> November or December).
I don't honestly know how important the new ones are...if there are any new
commands that they tell W95 to use or what. But it can't hurt...
Burns
|
| 1405.7 | maybe graphics card? | SLOAN::HOM | | Mon Mar 03 1997 13:50 | 10 |
| When I first installed Win95, the OS hang on COM4 (external modem). According
to MS, there was a conflict between the graphics driver
and the interrupt routine for COM4. Sure enough, when I disabled COM4 and
used COM2, the modem worked fine.
The symptoms were exactly the same, Win95 PnP found and identified the
modem but it wouldn't work with an application.
Gim
|
| 1405.8 | S3 video? | SMURF::PBECK | Paul Beck | Mon Mar 03 1997 16:24 | 5 |
| There's a well-known conflict between S3-based video boards and
COM4, so any time you have a problem with COM4 that's the first
thing to look at. I think some other kinds of chipsets have a
similar problem, but it's definite with S3 (the conflict is with the
I/O address, not the IRQ).
|
| 1405.9 | | LEFTY::CWILLIAMS | CD or not CD, that's the question | Mon Mar 10 1997 16:52 | 6 |
| Another possible problem is the modem handshaking... the Com port must
be set up for HW handshaking, not SW or XON/XOFF. Having this set up
incorrectly will do this.
Chris
|
| 1405.10 | | ACISS2::LEECH | Terminal Philosophy | Wed Mar 12 1997 08:44 | 4 |
| <-- Is this done in the BIOS?
-steve
|
| 1405.11 | | SKYLAB::FISHER | Gravity: Not just a good idea. It's the law! | Wed Mar 12 1997 12:29 | 3 |
| No, in software. I think it is a modem property in Win95.
Burns
|