Mouse in DOS

I have win98 and am trying to get my mouse to work in DOS mode, but I can't find a utility or setting to allow it's use in DOS? I used to use a program called MOUSE.COM back in the 6,2 days, but when I try it now, it can't find the serial port. What do I need to do to get the mouse to work in MS-DOS mode.

Also, HOW could I get it to automatically be set when I boot to DOS?

This brings up another related question which is not hardware but DOES have to do with auto setting:
-I tried to set DOSKEY in my AUTOEXEC.BAT program in the root directory, but it doesn't get run when I boot to DOS. WHERE do have to put the autoexec.bat *OR* what do I have to do to set the PATH, add programs to be pre-run for DOS (like DOSKEY) so that they run and work in DOS mode.

thx,

 

I have an old Logitech Mouse.exe in the root folder.

And a line like

C:\Mouse.exe

in the Dosstart.bat that is in the Windows folder.

To use the DOS commadn in the Autoexec,bat you need to put a path statement BEFORE the commands.

Path=C:\;C:\WINDOWS;C:\WINDOWS\COMMAND

Then the DOS commands should run OK.

Or you could put

C:\WINDOWS\COMMAND\DOSKEY.XXX

But the Path make it easier.

But if you are unsing Windows ME the commands may not work from the autoexec.bat. I am not sure about the DOSSTART.bat in ME. Never used ME that long.

The path may stay but the commands may not.

BillyBob

 

Check this page and get msmouse.exe, a mouse for dos.

 

I did add the PATH statement before, but it never runs the autoexec.bat at bootup. I tried changing DOSSTART.BAT and will see what happens at boot time.

As for the MOUSE.EXE program, I have one but it can't find the serial port. i'm looking for a generic DOS program that will allow my mouse to work in DOS.

Thx,

 

??????????? Say What ????? That is a new one on me.

With Win98 NO WAY ( that I know of ) that it does not process the autoexec.bat at boot up. The DOS side of the house needs it. and sometimes the Config.sys also.

Or if you have the Exit To DOS .pif properties set to use a speciific set of files ( instead of existing ) then it might not work.

If it can't find the serial ports, are they possiblely disabled or not set properly in the BIOS ?

If they are dsiabled in the BIOS I would think carefully about re-enabling them as on * SOME * machines they may be disabled in order to allow an Internal Modem to work. The Modem may be using IRQ 3 or 4.

--I am having problems here myself as I have not had a problem with either a PS2 or serial port Mouse. USB in DOS is usually a no go. But I do not have an Internal Modem either

And I am also using a Logitech DOS Mouse.exe with Microsoft PS2 Mouse.

I just removed the REM from in front of C:\Windows\Mouse.exe in the Autoexec.bat and it works fine on a restart.

BillyBob

 

Well, the AUTOEXEC.BAT is in the root dir and I added DOSKEY to it along with its path. BUT, when I open a dos window OR boot to MS-DOS, doskey is not loaded. This to me means that the autoexec is not being run at boot time, otherwise why isn't doskey present?
Which begs another question: WHERE do I put the statement (DOSKEY) for it to work in the two DOS modes? I tried putting it in the DOSSTART.BAT as well, but it still isn't loaded.

As for the PIF properties, I haven't changed anything on my own.

They are not disabled and all my IRQs and DMAs are fine. Also, I have no internal modem. The serial ports work fine in windows. I think that it was just an old version of MOUSE.EXE. I have tried using a new one, a MOUSE.COM, that I found, and it finds the ports, but still have to test it in MS-DOS mode.
Don't know what else to change at this point. It's the only AUTOEXEC.BAT on the system.

 

OK. I have to DOUBLE check something.

You are using WIn98 First Edition or 98 SE and not Windows ME. Is the correct.

If you are using ME then I could see why the DOSKEY or Mouse would not work in the Autoexec.bat

Also if using ME quite a few DOS commands ( files ) are missing.

If there are errors in the path statement it will mess things up also.

This would be my autoexec.bat if it had DOSKEY.com in it.
---------------------------------------------------------------
C:\PROGRA~1\NORTON~1\NAVDX.EXE /startup
SET BLASTER=A220 I7 D1 H7 P330 T6
SET SBPCI=C:\PROGRA~1\CREATIVE\AUDIO\DOSDRV
SET TMP=C:\WINDOWS\TEMP
SET TEMP=C:\WINDOWS\TEMP
SET CLASSPATH=D:\Program Files\PhotoDeluxe 2.0\AdobeConnectables
SET MSINPUT=C:\MSINPUT
PATH=C:\;C:\WINDOWS;C:\WINDOWS\COMMAND;D:\IMS;D:\QTW\BIN
C:\WINDOWS\MOUSE.EXE
C:\WINDOWS\COMMAND\DOSKEY.COM ( new command )
-------------------------------------------------------------

I will check this out to make sure it works. Will be back in a few.

OK.
I edited my autoeexec.bat to the same as above. ( last line only )

Restarted Windows and saw the message " DOSkey installed as it flew by. I have the logo turned off so I can keep track of what is going on at bootup.

Restarted in the MSDOS Mode and it showed as loaded into RAM there.

So. As of this moment I am fresh out of ideas. Other than the *possibility* of you using ME instead of 98.

Also * sometimes * DOS does not read lower case letters properly


BillyBob

*****Edit and ADD*****

I also changed the last two lines to read

MOUSE.EXE
DOSKEY.COM

And they also loaded.

BB

 

Using win98, not ME.
OK, I'm going to try them both with the paths as well and in CAPs as you did and see what happens.

SO I take it your AUTOEXEC is in the ROOT dir too (i.e. C:\)?

 

SO I take it your AUTOEXEC is in the ROOT dir too (i.e. C:\)?

Yes it is.

 

Well, it still wouldn't use the autoexec, so I had to physically put a reference to it in the shortcut for the MS-DOS prompt under the PROGRAM tab and in the BATCH FILE field.

As for booting to MS-DOS mode, I had to run autoexec in the DOSSTART.BAT file for it to run. Unfortunately the PATH statement in the autoexec gets overwritten somewhere AFTER the DOSSTART.BAT run, but I can't figure out which file it is (the find command shows nothing re: the new PATH values).

Got it to work, but the workaround seems excessive, shouldn't have to do it in my opinion

 

but the workaround seems excessive,

Certainly is

shouldn't have to do it in my opinion

That is correct also.

But it reads like you have the Properties of the Exit to DOS .PIF set to Specify a NEW DOS configuration and not Use Existing.

But this could also be an Auto set because of the apparent NON-USE of the Autoexec.bat in the root folder.

I am VERY puzzled about this as I have never had to use the SPECIFY NEW setting.

And as you see I can just add anything I wish to the Autoexec and have it work.

BTW. a question.

What are you using to edit the autoexec.bat ?

I myself use SYSEDIT from the Start/Run Line. That makes for a better chance of getting the right one.

BillyBob

 

The standard path for windows is c:\windows;c:\windows\command, to add to it effectively you would need the line:
Set Path=%PATH%;C:\
or
Set Path=C:\;%PATH%
%PATH% would represent the current default path, everything else is added in the order as the two lines represent. This should keep your path from being overwritten.
Another example, BillyBob's path line could be shortened in his autoexec.bat file as:
Set Path=C:\;%PATH%;D:\IMS;D:\QTW\BIN
A way to test if your autoexec.bat file is running is to first add the line below to your msdos.sys file, you'll have take the Read Only attributes from it, and that is a zero:
Logo=0
then add the lines below to the beginning of the autoexec.bat file:
Echo Autoexec is running
Echo right now
Echo at this moment.
This should appear on the screen during bootup. The Logo line will prevent the "Windows is starting up screen" from showing up.

 

I you have Tweakui you can also stop the Logo from showing up.

markp62

That is why I have the Logo turned off so that I can see everything that the autoexec is doing ( or not doing. )

I have tried your suggestion about the path with both good and not so good results. That is why I left it the way it shows.

This is one of the MANY things that do not work the same for all. Sure would be nice if it did.

mikenowo Could also put a PAUSE line inbetween various lines of the autoexec and after the last line.

I am very surprised that a couple of them did not show up in mine. But I must have removed them.

BillyBob

 

ARG! Well, Billy Bob, I think I know why the autoexec wouldn't run based on your suggestion to use sysedit:

I have win98 on my G: drive (have alot of logical drives as I have 3 OSs on my system). On C: I have win2000, and win98 seems to be using the one on C: (shouldn't in my opinion as it's installed on G: and uses evreything else there). Will try changing the C: one and see what happens. When I run Sysedit, it opens up most of the sys files on G: but the DOS ones (config.sys, autoexec.bat) are opened from C: <sigh>. Just old DOS defaults ******** up again.

That's also why the PATH statement was different too, as the one on C: drive is diff.

 

I have win2000, and win98 seems to be using the one on C: (shouldn't in my opinion as it's installed on G:

No matter where the OS files them selves are located the boot files should and must be in the root directory of the C: drive.

Unless you are using somthing like Boot Magic and each OS is on its own separate C: Drive ALL boot files for ALL systems are in the Root folder of the C: drive. And all Dual Boot does is rename a bunch of files and God forbid that anything go wrong during that process.

I am assuming here that you are using a Dual Boot and not Boot Magic. ( entirely different animals )

Boot Magic keeps each OS on its own separate C: drive . Dual Boot does not.

I am not 100% sure about this but In a Dual Boot setup Win98 must be install first and be on the C: drive.

I have win2000, and win98 seems to be using the one on C

That is the one it should use. as ALL OSs in a dual boot, boot from the C: drive.


When I run Sysedit, it opens up most of the sys files on G:

Wrong ones.

but the DOS ones (config.sys, autoexec.bat) are opened from C: <sigh>. Just old DOS defaults ******** up again.

Right ones. No DOS is not ******** Up. Both files that Windows uses for the DOS side should be there two.

Again, unless your are using some Boot Manager ALL BOOT FILES FOR ALL OSs are in the Root folder of the C: drive. And use the renaming provess to go from one to the other.

I have 3 OSs on my system).

I see only 2K and 98 mentioned. What is the third ?

BillyBob

 

I was going to add this to the other post but changed my mind.

If indeed they are ?

how did the 98 config.sys and autexec.bat get onto the G: drive in the first place ?

They do not belong there. And it looks like 98 is using them which it should not be.

I have a strange feeling that something is not quiite right.

A question that I do have to ask.

Did you put 98 on first and then 2K. If not you may have other problems.

BTW. You will need to edit the Config.sys and Autoexec.bat so the they do point to the actual drive and location of the Windows files.

Such as
C:\;G:\Windows;G:\windows\command

 

Linux (Red Hat 7.1)

 

Yes.

They do point to G:.

 

OK.

If all is working as it should then you should be able to add the Mouse to the Autoexec.bat in the C: root folder and it should work. As that is the one that Windows 98 should be using.

Other than this I have no idea why the mouse won't work ind DOS.

But I still do not understand ( AT ALL ) why the autoexec.bat in the root folder is not being used. And I am totaly lost now.

Unless some part of one of the other OS is messing things up.

Also what I ran into when I had three OS ( each was hidden from the other ) if I did not COLD BOOT between them things did not always work properly as RAM did not have time to clear out fully.

BillyBob