home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.os.ms-windows.programmer.misc
- From: tfj@apusapus.demon.co.uk (Trevor Jenkins)
- Path: sparky!uunet!pipex!demon!apusapus.demon.co.uk!tfj
- Subject: Serial port access with AMI bios
- Distribution: world
- References: <1992Sep8.093437@axion.bt.co.uk>
- Organization: Job hunters use Parachute
- Lines: 25
- Date: Tue, 8 Sep 1992 18:59:46 +0000
- Message-ID: <715978786snx@apusapus.demon.co.uk>
- Sender: usenet@gate.demon.co.uk
-
-
- In article <1992Sep8.093437@axion.bt.co.uk> jpennell@axion.bt.co.uk writes:
-
- > I am trying to install 3.0 on a 386SX-25 with AMI BIOS.
- >
- > Just once, it appeared to work, however, now the mouse doesn't
- > respond (it is a standard serial mouse). I am confused because
- > I have heard rumours that the AMI BIOS causes problems with
- > serial port access under Windows. Is this my problem (probably)?
- >
- > Any suggestions like, does 3.1 have the same problem - much appreciated.
-
- I'm running Windows 3.1 on a 386DX with an AMI BIOS (dated 5/5/90 I think).
- In the box I have two serial cards (two ports each). I am running with a
- MickeySoft mouse (and the latest version of the mouse driver) on port # I
- have a V32.bis modem stuck on port 4. I've not experienced any problems
- with the mouse or modem. I conclude therefore that if there was a problem
- with 3.0 it's been fixed in 3.1.
-
- -------------------------------------------------------------
- Trevor Jenkins Radio: G6AJG
- 134 Frankland Rd, Croxley Green, Rickmansworth, WD3 3AU
- email: tfj@apusapus.demon.co.uk
- phone: +44 (0)923 776436
-
-