Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!wuarchive!usc!samsung!sdd.hp.com!hp-pcd!hplsla!davidr
From: davidr@hplsla.HP.COM (David M. Reed)
Newsgroups: comp.windows.ms
Subject: Re: Networks using config.sys
Message-ID: <3130032@hplsla.HP.COM>
Date: 24 Aug 90 06:47:18 GMT
References: <13282@rouge.usl.edu>
Organization: HP Lake Stevens, WA
Lines: 26

# / hplsla:comp.windows.ms / dve@zooid.UUCP (David Mason) / 10:22 am  Aug 22, 1990 /
# davidr@hplsla.HP.COM (David M. Reed) writes:
# 
# > Our work-around is to configure the cards at interrupt 5 (LPT2).  We have
# > never had a problem after doing that.  However, we should never have a 
# > problem with interrupt 3 if MSWindows wouldn't touch things it is not
# > directly instructed to touch.
# 
# Try deleting all references to COM ports in WIN.INI. That's what Newbridge 
# recommended to us for our Easystreet (bleh) "network". Although Easystreet 
# uses the serial ports for the network Windows was causing problems, but 
# deleting the COMx:= lines seems to make Windows ignore them, and hopefullyu 
# their interupts. 
#  
# I hope this helps.

I have not tried this yet under MSWindows3, but I will.  Yet I suspect
that it will work (or didn't work) under version 2.11.  Yes, MSWindows
did seem to ignore the LAN card set to a COM port when the references
to the COM ports were removed from the WIN.INI file.  However, the entries
get put back in by MSWindows if a user should wander into "Ports" in
the "Control Panel".  And some applications (such as Terminal) would
also place them back into the WIN.INI file.  What often irritated me
was if I only set (with Control Panel or an application) COM1, an
entry from COM2 would also end up in the file with what must be "default"
values.  But maybe this is all fixed in MSWindows3...