| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | Deal- Modem Woes |
Matt Mc_Carthy wrote in a message to Wayne Chirnside: WC> I ran both of the enclosed executables in that Zipfile, one WC> installs "USR Winmodem" in my dialer and the other DOS based EXE WC> attempts to set the COM port address and IRQ. MMC> That DOS based EXE is for setting the modem in NVRAM when the MMC> jumpers are set to PNP. It is often touch-and-go, as the software MMC> finds all IRQs in use and doesn't accept sharing an IRQ at all. MMC> Much better to use the jumpers manually and keep the software in MMC> the desk drawer! :-)) Agreed, if I have a choice between PnP and not, with being able to set stuff up by jumpers in the latter case, that's what I'm gonna do here. The only time I use PnP is when I don't have a choice. And then I'll set it once and leave it alone... WC>> MSD doesn't see the modem in Win 3.1 nor does sysinfo in Norton WC>> but the dialer indicates the IRQ conflict with the LPT port when WC>> I attempt to dial so it's being seen there. MMC> This is normal for MSD when there is a conflict. No software can MMC> weed out a conflict, only tell that there IS a conflict. I seem to also recall that MSD will tell you that there's stuff on the first three com ports when in actual fact you might have something like 1, 2, and 4 in there... ---* Origin: TANSTAAFL BBS 717-838-8539 (1:270/615) SEEN-BY: 633/267 270 @PATH: 270/615 150/220 379/1 106/1 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™.