PCBUILD Archives

Personal Computer Hardware discussion List

PCBUILD@LISTSERV.ICORS.ORG

Options: Use Forum View

Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Will Stephenson <[log in to unmask]>
Reply To:
PCBUILD - Personal Computer Hardware discussion List <[log in to unmask]>
Date:
Fri, 26 Feb 1999 07:34:06 -0500
Content-Type:
text/plain
Parts/Attachments:
text/plain (37 lines)
Hello!

It sounds like Win95 is not providing a driver for this mouse, perhaps
because it can't find it. One way to find a device that has worked for me is
to load a driver through the autoexec.bat file (DOS lives whether we like it
or not) like:

        set mouse=c:\mouse
        mouse=c:\mouse\mouse.exe

(Please forgive me if the syntax is not quite right...are there others out
there with better memories?)

Anyway, loading the device through DOS can sometimes nudge Win95 into seeing
the mouse itself.

HTH

Will Stephenson   ><>
[log in to unmask]

-Subject: [PCBUILD] weird mouse behavior


I am working on a clients PC Express older 486 running Win95 a.  Everytime
it gets in windows, windows does not detect a mouse.  It is a serial mouse
on com1.

Com 1 shows up in the device manager fine, no conflicts on irq 4.  The mouse
works great on my linux machine.  I installed a different i/o card and still
no mouse.  The cmos is older, so there is no mention of IRQ or pnp, or
anything of the sort.

                Curious about the people moderating your
                   messages? Visit our staff web site:
                     http://nospin.com/pc/staff.html

ATOM RSS1 RSS2