| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 2855.1 | | TARKIN::LIN | Bill Lin | Tue Mar 18 1997 08:32 | 12 |
| re: SUBSYS::MSOUCY
Mike,
Did you think of NOT moving the mouse while dialing? ;-)
It may be tied to a higher priority on your mouse port and bad software
design such that if the dialout is interrupted by a higher priority
task, it gets completely lost when control is given back. Just
guessing...
/Bill
|
| 2855.2 | Hmm, diff between vlb video + DX4-100/P133 #9GXE? | SUBSYS::MSOUCY | MentalmETALMike | Tue Mar 18 1997 14:15 | 20 |
|
re: -1
;-)
I am going to de-install Netscape again tonight, remove my modem from
the device drivers list, change it from com4 to com3 and let W95 pick
it up again (and prior to that delete the shared files W95 can't remove
so I can reinstall them too when Netscape goes back in) as COM3 since I
heard from a few people over here that the S3 chipset has a tendency to
overstep resources into COM4 area or something along those lines.
Memory resources/addressing conflict? I don't see ANY conflicts when
Dev Mgr is initially brought up but I also haven't checked out all the
other viewables, which I might do first. But as I said before, on a
DX4-100 w/VLB video I had NO problems with this modem! Now I go to
faster cpu/video and this is what I catch? It certainly installs and
uncompresses a whole hell of a lot faster too! ;-) I'll check back in
here with results tomorrow if I get the chance to do all this tonight.
|
| 2855.3 | | WRKSYS::TATOSIAN | The Compleat Tangler | Tue Mar 18 1997 16:22 | 6 |
| re: .0
Well Device Manager notwithstanding, that sure sounds like a classic case
of interrupt conflict to me. Is this a Plug'n'Pray modem, or can you
jumper it to use a *known-to-be-not-currently-used* IRQ? (my Sportster
Vi allows on-board jumpers to override the stupid PnP crapola).
|
| 2855.4 | changed modem to COM3, workie workie! | SUBSYS::MSOUCY | MentalmETALMike | Thu Mar 20 1997 07:23 | 22 |
|
re: last few
I ended up deleting the modem from DM, de-installed ATT Worldnet,
shutdown and re-jumpered the modem for COM3, rebooted system and did
add new hardware, found it, installed the driver from floppy (most
likely newer than what came with W95 CD), did another reboot and viola!
No more problems moving the window while dialing. I am happy now that
the P133 is cruising along like it should be. Now to afford a 17"
monitor (one of these day.....).
The funny thing is prior to this I had no trouble on my DX4-100 with it
at COM4 (but had VLB video card) and there were no indications in
device manager of any conflict whatsoever....which was interesting....
Chock it up to the S3 chipset/COM4 address area which someone mentioned
to me on monday here at SHR. It must have been the problem since it
works fine now and no IRQ conflicts then/now.
Thanks for the suggestions.
Mike
|
| 2855.5 | We usually catch this problem here 8^} | WRKSYS::TATOSIAN | The Compleat Tangler | Thu Mar 20 1997 16:19 | 10 |
| Mike: Sorry not to have picked that up earlier - and I just re-read
your .3 and this time realized that COM4 was where the modem *was* when
it wasn't working...
Yes, indeed, the S3 uses an IO address that'll overlay on the address
for COM4. Moving the mouse was causing the graphics driver to want to
move the cursor "sprite", and apparently that code/function uses the
overlaying IO address. Not the mouse's conflict, the graphic card's...
/dave
|