Hi Roy.

23-Sep-03 20:01:30, Roy J. Tellason wrote to Matt Mc_Carthy


 RJT> 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
 MMC>> software finds all IRQs in use and doesn't accept sharing an IRQ
 MMC>> at all. Much better to use the jumpers manually and keep the
 MMC>> software in the desk drawer!   :-))

 RJT> Agreed,  if I have a choice between PnP and not,  with being able
 RJT> to set stuff up by jumpers in the latter case,  that's what I'm
 RJT> gonna do here.  The only time I use PnP is when I don't have a
 RJT> 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
 MMC>> can weed out a conflict, only tell that there IS a conflict.

 RJT> I seem to also recall that MSD will tell you that there's stuff
 RJT> on the first three com ports when in actual fact you might have
 RJT> something like 1, 2, and 4 in there..

The BIOS never skips COM-port numbers.  if you have  ports on 3F8 2F8  and
2E8  it'll number them com1 com2 com3  even though the last one (2E8) is the
"com4" address.

Dos follows the BIOS, MSD may be following the DOS naming of the ports.

  -=> Bye <=-

---