Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!thunder.mcrcim.mcgill.edu!snorkelwacker.mit.edu!spool.mu.edu!uwm.edu!rpi!uupsi!sunic!news.funet.fi!ra!abo.fi!ahamalainen From: ahamalainen@abo.fi Newsgroups: comp.windows.ms Subject: Re: Windows and COM3 Message-ID: <7286.27bc3c5c@abo.fi> Date: 15 Feb 91 19:54:04 GMT References: <1991Feb12.190322.22184@gpu.utcs.utoronto.ca> <12126@helios.TAMU.EDU> Organization: Abo Akademi University, Finland Lines: 48 In article <12126@helios.TAMU.EDU>, n117be@tamuts.tamu.edu (Eugenio Ulian) writes: > I was having problems with my com3, my internal modem, and Terminal until > yesterday. I called Microsoft and they faxed me a few problem solving sheets > for the message that reads: "The port is being used by a DOS application" or > something like that. > I went through their instructions step by step and after 6 months I am finally > able to use Terminal. > I had called them before, and the answer I got at that time (6 months ago) was > that I wouldn't be able to use my com3 since my machine did not have micro > chaneling ? capability. I guess they are learning to fix their bugs. > > Eugenio Ulian > ecu7967@tamvenus I also encountered 'whole-loota-troubles' trying to make my internal modem work. Finally after re-re-re-- reading the sysini*.txt files for the umpteenth time I found out what really was wrong. Windows expects the base-memory addresses to be quite different from the real ones e.g. I had.. To show the details: the default value (base-address) for com3 is 2e8 (hex) - in my system (opti motherboard) the value should read 3e8.. somewhat of a difference, ay? Also the responding Irq-values caused me serious head-aches.. there is a setting in system.ini to change the value (but in small print - and in the _real_advanced_users_section_ (?)).. You can use the same irq in com3/4 as well as in com1/2 - but be carefull... the commands to use in your sys.ini [386enh section] Com3Base=
def 2e8 Com3Irq=