Roger C. Scudder Jr. on Fri, 11 Jun 1999 22:22:27 -0400 (EDT) |
Before I make any suggestions for getting your modem working under windows again I'd like to bring up a couple of things. Most newer modems support PnP and hard jumper setting. When you buy a modem make sure it supports both. I prefer to always set the modem to com 2 (cua1) and interrupt 3. I know Windows tells you that may cause a problem, but I don't take Microsoft's advice very seriously. The advantage of doing it this way is that the modem works correctlly in both Windows and Linux (I have been dule booting for years). This leads to my next point... why don't you use the PII for all of your OS needs? The obivious is that you can't run both at the same time.... well, still run Linux on the other box, you can't have too many Linux boxes, but even one Windows is too many! Ok, now... that said... You didn't say which version of Windows you are using. I noticed that 98 insists on an inf file for modems where as 95 is a little more flexable. Try deleting the old modem settings and reboot windows. It should detect the modem and ask you to configure it. Did you get through all of this yet? On Thu, 10 Jun 1999, Pham Long Trung Duy wrote: > I had my modem on a windows box, running just fine (not a winmodem). I > start play around with PPP and IPmasq on my linux box, so I move the > modem over linux box, buying a another (unfortunately, pnp win-) modem > for windows. After a few test rides, I decided it's not the one for me, > as when windows get heavily loaded the connection broke. Taking it back > to the store and getting the refund is not the problem! However, the > problem is, when I tried to re-install my old modem onto the windows box > (remember? I cannot get IPmasq working yet), the darn thing won't work. > > Thinking that I probably killed it by static, I still, desperately, > moved it back to the linux box. And voila! It worked! I could telnet > to a unix account 2000 miles away. I'd love to blame Windows and > Microsoft for it, but I couldn't: Hate to lose the battle, I bring it > back to Windows machine, but this time boot it into plain DOS mode, and > use Telix (minicom-like comm sw for DOS). Telix can open the COM4 > (supposingly my modem), but the CTS signal is dead, hence unsuccessfully > communicate to the modem. > > My next step was to go into BIOS, turning off all the pnp feature. But > it doesnt help. My linux box is a old 486 with ISA/VESA motherboard, no > pnp at all. The DOS machine is Pentium 200 Tyan with PCI/ISA and pnp > BIOS. I think the problem is at hardware level, but cannot understand > what difference on the PentiumII motherboard that make the modem won't > work. Is it that the software driver for the winmodem reconfigure all > the pnp things, putting my system (my old modem is also pnp) in wierd > configuration ? Or Does BIOS do any pnp configuring at boot even before > DOS gets loaded? How come it still work on the old 486? I even tried > removing all cards from windows box, leaving just the video and the > modem card, to eliminate resource conflicts, but still no luck. What > went wrong? What else should I try? > > I hate pnp. Just give me back my the jumpers. I CAN read the table! > > I'll try anything to get me out of this mystery! > > thanks for you feedback, btw. > duy > > _______________________________________________ > Plug maillist - Plug@lists.nothinbut.net > http://lists.nothinbut.net/mail/listinfo/plug > _______________________________________________ Plug maillist - Plug@lists.nothinbut.net http://lists.nothinbut.net/mail/listinfo/plug
|
|