🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Article View: comp.os.ms-windows.setup.win95
Article #264

Re: Help: Com2 and Win95

#264
From: Kai Hsieh
Date: Fri, 26 Jan 1996 00:00
87 lines
4894 bytes
Me too, have a very similar problem.
Jon here are giving an excellent and correct resolution, thank you
Jon.
But for me, I have one more problem which is related to my Dell
computer combine with a S3 graphic card driver.
So, if someone is using a computer with a S3 graphic card driver.
Change your modem jumper to COM3 before you follow Jon's resolution.
You can NOT use COM4 (COM1 or COM2 is still questionable).  The reason
that I got from Dell's technical support is Window95 will behave very
strange, if I don't use COM3, and IRQ4.
With some investigation of myself.  The real answer I believe is
hardware-conflict between the graphic card and COM4.
For a detail explanation, take a look at the following www site:
"http://www.castrop-rauxel.netsurf.de/homepages/mschoebel/faqmode"

Kai-Chun

jlgwinn@ix.netcom.com wrote:

>Kkim,

>   I also had a similar problem, all under Windows95. I had a GVC 14.4 modem
>on Com2 - worked great. Plus, I had a trackball on Com1 - worked fine. Then,
>I replaced the GVC with a Boca 28.8 and Win95 installed it on Com2 - no problem.

>  Here's where the trouble started... I bought an MS Mouse plus my Boca modem
>crapped out, so I returned it to the store and swapped for a SupraExpress 288i
>PnP. For whatever reasons, the mouse got installed on Com3 and the new modem
>on Com4! 

>  After much gnashing of teeth,  cursing, trial and error, prayers to the
>computer gods and endless reboots, here is what I figured out:

>  a. Under Control Panel, Device Manager, Comm Ports, Com1 and Com2 were
>     listed. I don't know how they got there.

>  b. It "appears" ( I'm qualifying this because it was my experience and
>     not substantiated by any official information that I know of ) that
>     Windows95 will not install any new hardware onto ports that are listed
>     in device manager. If Comm ports are listed there, Windows95 considers
>     them "spoken for."

>  c. I removed Com1 and Com2 from device manager PLUS removed my mouse and
>     modem from their respective locations in device manager and rebooted.

>  d. Upon reboot, Windows95 cheerfully installed my mouse on Com1 and modem
>     on Com2!!! 

>  Everything has been fine since. You shouldn't need to go through any sort
>  of process every time you reboot. Try removing your modem AND any com ports
>  listed in device manager and reboot. If Win95 doesn't immediately recognize
>  your modem and install it, you may have to run the Install New Hardware
>  application.

>  Hope this helps...

>  Jon

>> kkim@ids2.idsonline.com wrote:

>  [...snipped the long story about troubles getting the modem to work on Com2...]

>>  I have to go through the entire process every time I turn on the
>> :computer, if I want to use the modem.
>> :I hate it.  I hate it.  I hate it.
>> 
>> :Tonight, I wish, I hope some one would answer to my wishing star.

>>   Then Bill Branczek wrote...
>> 
>> I had a similar problem.  Here's the fix I came up with.  
>> 
>> First, go into Device Manager and remove all com ports and the modem.
>> Then reboot and go into your bios setup and disable all com ports,
>> then boot.  Win95 will add the com ports back in, may ask you to
>> re-boot again and then it will add the modem.  Then check in Device
>> manager to see where it all landed and if there's any conflicts.  You
>> may get a conflict on a com port that's not in use, if so disable it.
>> I installed a Supra a few months ago and thru trial and error came up
>> with this.  The key for me was disabling the com ports in the bios
>> setup.  Give it a try.
>> 
>> Bill Branczek
>> bilbran@teleport.com
>> bilbran@worldnet.att.net
>> Salem,OR
>> 
Technical Details
Message-ID: <4ebic1$rrt@agate.berkeley.edu>
Path: arc1-ca.pugleaf.net!unknown!not-for-mail
References: <4dsa9l$5sr@news.cais.com> <4dsr54$g9h@mtinsc01-mgt.ops.worldnet.att.net> <N.012196.170309.94@bal-md4-23.ix.netcom.com>

Show Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 1025cc,fccc75135f49772c
X-Google-Attributes: gid1025cc,public
X-Google-Thread: 10c888,fccc75135f49772c
X-Google-Attributes: gid10c888,public
X-Google-Thread: 10d516,fccc75135f49772c
X-Google-Attributes: gid10d516,public
X-Google-Thread: fad41,fccc75135f49772c
X-Google-Attributes: gidfad41,public
X-Google-Thread: 105a37,fccc75135f49772c
X-Google-Attributes: gid105a37,public
X-Google-Thread: 1103cc,fccc75135f49772c
X-Google-Attributes: gid1103cc,public
X-Google-Thread: 104cb0,fccc75135f49772c
X-Google-Attributes: gid104cb0,public
From: kchsieh@uclink4.berkeley.edu (Kai Hsieh)
Subject: Re: Help: Com2 and Win95
Date: 1996/01/26
Message-ID: <4ebic1$rrt@agate.berkeley.edu>
X-Deja-AN: 136552719
references: <4dsa9l$5sr@news.cais.com> <4dsr54$g9h@mtinsc01-mgt.ops.worldnet.att.net> <N.012196.170309.94@bal-md4-23.ix.netcom.com>
organization: University of California, Berkeley
newsgroups: comp.os.ms-windows.setup.win95,comp.os.ms-windows.win95.misc,demon.ip.support.win95,kiel.computer.windows.win95,thenet.support.windows95,tw.bbs.comp.mswindows.win95,uk.comp.os.win95