Doesn't the Logitech software and Windows both have sensitivity settings for the mouse?

I'd try stopping the Logitech software from executing on bootup and see if that fixes it.

DosFreak wrote:

Doesn't the Logitech software and Windows both have sensitivity settings for the mouse? I'd try stopping the Logitech software from executing on bootup and see if that fixes it.

I'm not using the Logitech software, but rather the stock PS2 Logitech driver that comes with Windows XP.

As far as the mouse sensitivity settings in Windows, I have that jacked all the way up. That's the way I've always had the mouse set in Windows, and the speed "feels" right to me within Windows.

Indeed there's an issue especially when the aspect ratio of the screenmodes change (most dramatic is going to 320x400/360x480)

leileilol wrote:

Indeed there's an issue especially when the aspect ratio of the screenmodes change (most dramatic is going to 320x400/360x480)

I suppose that would explain why some games do it, and others don't (I suppose you're refering to the windowed verses fullscreen mode differences).

Although, it's still a mystery as to why (at least on my PC) in fullscreen the mouse sensitivity goes down to so little sometimes, yet other times not.

As an example, during the course of writing my first (and second) message posts in this thread, I fired up DOOM quite a few times. Each time, the problem was there.

Shut the PC down, did a bit of housework <ugh>, fired it up, and currently it works perfectly! I tried DOOM 4 or 5 times (i.e start DB/run DOOM/exit DOOM/exit DB/etc...) and it worked fine each time. *Also*, now the "sensitivity=" line in the DOSBox.conf file seems to working as well (apparently though, not from the command-line within DOSBox, but definately in the DOSBox.conf file).

I have a good hunch though, If I reboot (or powerdown), it won't be working again.

whats your priority setting in dosbox? try modifying it.-

lightmaster wrote:

whats your priority setting in dosbox? try modifying it.-

Per my first message post, I tried that. When the problem is rearing it's ugly heard, I tired setting DOSBox's priority to all of the available settings (lowest, lower, normal, higher, highest/etc...). Unfortunately, that didn't help though.

P.S. (re: reboots and such) Yep, just fired up DOSBox and DOOM, and the mouse sensitivity is extremely low/slow, and the "sensitivity=" line is having no effect whatsoever.

When the mouse condition is occuring, try this: open a command console window (cmd.exe) and type "SET SDL_VIDEODRIVER=WINDIB" and then run dosbox.exe from that same console window. The DOSBox Status Window should display "SDL_Init: Starting up with SDL windib video driver." From the name of the environment variable it might not seem that it would be related, but it does relate to directinput and the mouse.

If the mouse condition improves, it suggests a SDL+directinput issue; and would at least be something to go on for further research into the problem. If it does help, you could also use it as a workaround by creating a batch file that sets the env. var and runs DOSBox.

How many mice have you got in your devices manager?

robertmo wrote:

How many mice have you got in your devices manager?

Only one, "Logitech PS/2 Port Mouse"

ripsaw8080 wrote:

When the mouse condition is occuring, try this: open a command console window (cmd.exe) and type "SET SDL_VIDEODRIVER=WINDIB" and then run dosbox.exe from that same console window. The DOSBox Status Window should display "SDL_Init: Starting up with SDL windib video driver." From the name of the environment variable it might not seem that it would be related, but it does relate to directinput and the mouse.

If the mouse condition improves, it suggests a SDL+directinput issue; and would at least be something to go on for further research into the problem. If it does help, you could also use it as a workaround by creating a batch file that sets the env. var and runs DOSBox.

Thanks for the info, I definitely be giving that a try 😀 Heh, it figures... it's working properly right now!

(edit) P.S. Although it is currently working properly (without setting the environment variable), I noticed the following in the DOSBox status screen:

1SDL_Init: Starting up with SDL windib video driver.
2Try to update your video card and directx drivers!

Dunno if that helps or not, and currently not sure if it says the same thing when the mouse sensitivity isn't working properly (as right now it is).

P.P.S. Currently running DirectX v9.0c, if that helps any.

('nuther edit, and another P.S.) One thing that I noticed:

When the mouse sens. is acting up, I can load the old "Cute Mouse Driver" (CTMOUSE.EXE) within DOSBox, and then the mouse sens. is just fine, and "feels" right to me. I can even use the command line parameters that the CTMOUSE driver supports for changing the sens., and they work fine as well.

As soon as I unload the CTMOUSE driver, it's back to the same slow mouse sens. (that is, when the problem is happening).

Not sure if that info is any help though.

rfnagel wrote:

robertmo wrote:

How many mice have you got in your devices manager?

Only one, "Logitech PS/2 Port Mouse"

check HID devices too

robertmo wrote:

check HID devices too

None for the mouse. The only things that are listed for HID devices are "Generic Game port Device" and "HID-compliant game controller".

Normally you should not see anything about windib in the status window if you don't have that environment variable set... would be interesting if its appearance coincided with the mouse condition.

BTW, CTMOUSE adds some acceleration, while DOSBox's internal mouse driver is more "flat" in its response.

ripsaw8080 wrote:

Normally you should not see anything about windib in the status window if you don't have that environment variable set... would be interesting if its appearance coincided with the mouse condition.

As soon as it starts acting up again, I'll post the info/results here.

ripsaw8080 wrote:

BTW, CTMOUSE adds some acceleration, while DOSBox's internal mouse driver is more "flat" in its response.

The default when loading the CTMOUSE driver feels about the same to me as having DOSBox's "sensitivity=" line set to 250. I'm not 100% sure, but I think that CTMOUSE's defaults are "3" (the range is 1 to 9 on the command line).

When I just booted up the PC tonight, the mouse sensitivity was extremely slow again. Unfortunately (or rather, I suppose, 'fortunately' <grin>) it started behaving properly rather quickly... so I didn't have enough time to test the "SET SDL_VIDEODRIVER=WINDIB" thing (before the mouse starting behaving properly on it's own).

But, I *was* able to have a look at the info in the DOSBox status screen when the mouse sensitivity was acting up:

1DOSBox version 0.73
2Copyright 2002-2009 DOSBox Team, published under GNU GPL.
3---
4CONFIG:Loading primary settings from config file C:\DOSBox\dosbox.conf
5MIDI:Opened device:win32
6Serial1: Opening com1
7Serial1: Serial Port "com1" could not be opened.
8The specified port is already in use.
9Using joystick Gravis GamePad with Gravis GamePad with 4 axes, 4 buttons and 0 hat(s)
10MAPPER: Loading mapper settings from C:\DOSBox\mapper.txt
11Failed to create hardware surface.
12Restarting video subsystem with windib enabled.

...and as soon as the mouse started behaving properly (which was rather quick this time, the second time that I ran DOSBox), here is the info form the DOSBox status screen (similar to what I posted previosuly, but the following is the entire thing):

1DOSBox version 0.73
2Copyright 2002-2009 DOSBox Team, published under GNU GPL.
3---
4SDL_Init: Starting up with SDL windib video driver.
5          Try to update your video card and directx drivers!
6CONFIG:Loading primary settings from config file C:\DOSBox\dosbox.conf
7MIDI:Opened device:win32
8Serial1: Opening com1
9Serial1: Serial Port "com1" could not be opened.
10The specified port is already in use.
11Using joystick Gravis GamePad with Gravis GamePad with 4 axes, 4 buttons and 0 hat(s)
12MAPPER: Loading mapper settings from C:\DOSBox\mapper.txt

As soon as I can reliable test it when the mouse is not working peoperly, I'll try the "SET SDL_VIDEODRIVER=WINDIB" environment variable, and post the results here.

P.S. The "Serial1: Serial Port "com1" could not be opened." was due to me being online... as I have an external modem on COM1, which I have setup in DOSBox as well.

OK, this is sort of hard to describe... I'll try not to ramble on too much <grin>.

First of all, I powered down the PC and restarted. I then started DOSBox and DOOM2 (via my normal DOSBox start menu shortcut), and the mouse was slow. Exited DOOM2 and DOSBox, restarted DOSBox and DOOM2, and the mouse was still slow.

I then set the "SDL_VIDEODRIVER=WINDIB" environment variable from the command prompt, started DOSBox within the command prompt window (in my case, "C:\DOSBox\dosbox.exe -conf C:\DOSBox\dosbox.conf"), and ran DOOM2. The mouse sensitivity was fine then.

I did this two more times, each time exiting and restarting the command prompt window (set env. variable from the command prompt, run DOSBox using the above commands in a CMD.EXE window, and ran DOOM2)... and each time the mouse sensitivity was OK.

I then tried running DOSBox from my regular start menu shortcut (which is the same as the command line I used above; "C:\DOSBox\dosbox.exe -conf C:\DOSBox\dosbox.conf"), and the mouse sensitivity was slow again. Tried this two more times, and each time the mouse sensitivity was slow.

Then I did this:

I started DOSBox from my start menu shortcut and ran DOOM2. As DOOM2 was runing I ALT+ENTER(ed) to put DOSBox (and DOOM2) in a window, and then ALT+ENTER(ed) again to put it in fullscreen. Same results... the mouse sensitivity was slow in fullscreen (although, as I've mentioned previously, when DOSBox is running in a window it's fine).

After that, I did this:

I started DOSBox from my start menu shortcut, and ran DOOM2. Mouse was slow.

Then, I ALT+TAB(ed) to the DOSBox status window, which brought the status window fullscreen.

Lastly, I ALT+TAB(ed) back to DOSBox; which at this point was running in a window; and then ALT+ENTER(ed) to switch DOSBox to fullscreen..................

THE MOUSE SENSITIVITY WAS FINE THEN!

Exited DOOM2 and DOSBox, and repeated the above several times, each time with the same above results:

DOSBox and DOOM2 was running fullscreen, mouse sensitivity was slow;

Then, after ALT+TAB(ing) to the fullscreen DOSBox status window, ALT+TAB(ing) back to DOSBox (which at that point was running in a window), and then ALT+ENTER(ing) to bring DOSBox back to fullscreen, the mouse sensitivity was fine each time I ran DOSBox like that 😀

Weird, huh?

what are your PC specifications? (mainly gfx card and latest drivers)
enclose your dosbox's config file (you use fullscreen=true, what if you use fullscreen=false?)

robertmo wrote:

what are your PC specifications? (mainly gfx card and latest drivers)

I have a Dell Dimension 4600:

Intel P4 2.66 GHz CPU
512MB RAM
Onboard Intel 82865G Graphics Controller with 64MB shared video memory

Latest/last digitally signed video drivers from Dell's site;
Provider: Intel Corp
Date: 7/19/2005
Version: 6.14.10.4363

SBLive Value (static 96MB RAM dedicated for SoundFonts)/USB 2.0 ports/LPT port/Serial port (hooked to an external modem)/Logitech PS2 MouseMan/etc...

Running Windows XP SP2

robertmo wrote:

enclose your dosbox's config file

Here is my usual DOSBox.conf that I use for most everything (except for quite a few games that I have that require additional "tweaking"):

1# This is the configurationfile for DOSBox 0.73.
2# Lines starting with a # are commentlines.
3# They are used to (briefly) document the effect of each option.
4
5[sdl]
6#       fullscreen: Start dosbox directly in fullscreen.
7#       fulldouble: Use double buffering in fullscreen.
8#   fullresolution: What resolution to use for fullscreen: original or fixed size (e.g. 1024x768).
9# windowresolution: Scale the window to this size IF the output device supports hardware scaling.
10#           output: What video system to use for output.
11#                   Possible values: surface, overlay, opengl, openglnb, ddraw.
12#         autolock: Mouse will automatically lock, if you click on the screen.
13#      sensitivity: Mouse sensitivity.
14#      waitonerror: Wait before closing the console if dosbox has an error.
15#         priority: Priority levels for dosbox. Second entry behind the comma is for when dosbox is not focused/minimized. (pause is only valid for the second entry)
16#                   Possible values: lowest, lower, normal, higher, highest, pause.
17#       mapperfile: File used to load/save the key/event mappings from.
18#     usescancodes: Avoid usage of symkeys, might not work on all operating systems.
19
20fullscreen=true
21fulldouble=false
22fullresolution=original
23windowresolution=original
24output=surface
25autolock=true
26sensitivity=250
27waitonerror=true
28priority=highest,highest
29mapperfile=mapper.txt
30usescancodes=true
31
32[dosbox]
33# language: Select another language file.
34#  machine: The type of machine tries to emulate.
35#           Possible values: hercules, cga, tandy, pcjr, ega, vgaonly, svga_s3, svga_et3000, svga_et4000, svga_paradise, vesa_nolfb, vesa_oldvbe.
36# captures: Directory where things like wave, midi, screenshot get captured.
37#  memsize: Amount of memory DOSBox has in megabytes.
38#             This value is best left at its default to avoid problems with some games,
39#             though few games might require a higher value.
40#             There is generally no speed advantage when raising this value.
41
42language=
43machine=svga_s3
44captures=capture
45# memsize=16
46memsize=31
47
48[render]
49# frameskip: How many frames DOSBox skips before drawing one.
50#    aspect: Do aspect correction, if your output method doesn't support scaling this can slow things down!.
51#    scaler: Scaler used to enlarge/enhance low resolution modes. If 'forced' is appended,the scaler will be used even if the result might not be desired.
52#            Possible values: none, normal2x, normal3x, advmame2x, advmame3x, advinterp2x, advinterp3x, hq2x, hq3x, 2xsai, super2xsai, supereagle, tv2x, tv3x, rgb2x, rgb3x, scan2x, scan3x.
53
54frameskip=0
55aspect=false
56scaler=normal2x
57
58[cpu]
59#      core: CPU Core used in emulation. auto will switch to dynamic if available and appropriate.
60#            Possible values: auto, dynamic, normal, simple.

61#   cputype: CPU Type used in emulation. auto is the fastest choice.
62#            Possible values: auto, 386, 386_slow, 486_slow, pentium_slow, 386_prefetch.
63#    cycles: Amount of instructions DOSBox tries to emulate each millisecond. Setting this value too high results in sound dropouts and lags. Cycles can be set in 3 ways:
64#              'auto'          tries to guess what a game needs.
65#                              It usually works, but can fail for certain games.
66#              'fixed #number' will set a fixed amount of cycles. This is what you usually need if 'auto' fails.
67#                              (Example: fixed 4000)
68#              'max'           will allocate as much cycles as your computer is able to handle
69#            
70#            Possible values: auto, fixed, max.
71#   cycleup: Amount of cycles to increase/decrease with keycombo.
72# cycledown: Setting it lower than 100 will be a percentage.
73
74core=auto
75cputype=auto
76# cycles=auto
77cycles=max
78cycleup=500
79cycledown=20
80
81[mixer]
82#   nosound: Enable silent mode, sound is still emulated though.
83#      rate: Mixer sample rate, setting any device's rate higher than this will probably lower their sound quality.
84#            Possible values: 22050, 44100, 48000, 32000, 16000, 11025, 8000, 49716.
85# blocksize: Mixer block size, larger blocks might help sound stuttering but sound will also be more lagged.
86#            Possible values: 2048, 4096, 8192, 1024, 512, 256.
87# prebuffer: How many milliseconds of data to keep on top of the blocksize.
88
89nosound=false
90# rate=22050
91rate=44100
92blocksize=2048
93prebuffer=10
94
95[midi]
96#     mpu401: Type of MPU-401 to emulate.
97#             Possible values: intelligent, uart, none.
98# mididevice: Device that will receive the MIDI data from MPU-401.
99#             Possible values: default, win32, alsa, oss, coreaudio, coremidi, none.
100# midiconfig: Special configuration options for the device driver. This is usually the id of the device you want to use. See README for details.
101
102mpu401=intelligent
103mididevice=default
104midiconfig=
105
106[sblaster]
107#  sbtype: Type of sblaster to emulate.
108#          Possible values: sb1, sb2, sbpro1, sbpro2, sb16, none.
109#  sbbase: The IO address of the soundblaster.
110#          Possible values: 220, 240, 260, 280, 2a0, 2c0, 2e0, 300.
111#     irq: The IRQ number of the soundblaster.
112#          Possible values: 7, 5, 3, 9, 10, 11, 12.
113#     dma: The DMA number of the soundblaster.
114#          Possible values: 1, 5, 0, 3, 6, 7.
115#    hdma: The High DMA number of the soundblaster.
116#          Possible values: 1, 5, 0, 3, 6, 7.
117# sbmixer: Allow the soundblaster mixer to modify the DOSBox mixer.
118# oplmode: Type of OPL emulation. On 'auto' the mode is determined by sblaster type. All OPL modes are Adlib-compatible, except for 'cms'.
119#          Possible values: auto, cms, opl2, dualopl2, opl3, none.
120#  oplemu: Provider for the OPL emulation. compat or old might provide better quality (see oplrate as well).
121#          Possible values: default, compat, fast, old.
122# oplrate: Sample rate of OPL music emulation. Use 49716 for highest quality (set the mixer rate accordingly).
123#          Possible values: 22050, 49716, 44100, 48000, 32000, 16000, 11025, 8000.
124
125sbtype=sb16
126sbbase=220
127irq=5
128dma=1
129hdma=5
130sbmixer=true
131oplmode=auto
132oplemu=default
133# oplrate=22050
134oplrate=44100
135
136[gus]
137#      gus: Enable the Gravis Ultrasound emulation.
138#  gusrate: Sample rate of Ultrasound emulation.
139#           Possible values: 22050, 44100, 48000, 32000, 16000, 11025, 8000, 49716.
140#  gusbase: The IO base address of the Gravis Ultrasound.
141#           Possible values: 240, 220, 260, 280, 2a0, 2c0, 2e0, 300.
142#   gusirq: The IRQ number of the Gravis Ultrasound.
143#           Possible values: 5, 3, 7, 9, 10, 11, 12.
144#   gusdma: The DMA channel of the Gravis Ultrasound.
145#           Possible values: 3, 0, 1, 5, 6, 7.
146# ultradir: Path to Ultrasound directory. In this directory
147#           there should be a MIDI directory that contains
148#           the patch files for GUS playback. Patch sets used
149#           with Timidity should work fine.
150
151gus=true
152# gusrate=22050
153gusrate=44100
154gusbase=240
155gusirq=5
156gusdma=3
157ultradir=C:\ULTRASND
158
159[speaker]
160# pcspeaker: Enable PC-Speaker emulation.
161#    pcrate: Sample rate of the PC-Speaker sound generation.
162#            Possible values: 22050, 44100, 48000, 32000, 16000, 11025, 8000, 49716.
163#     tandy: Enable Tandy Sound System emulation. For 'auto', emulation is present only if machine is set to 'tandy'.
164#            Possible values: auto, on, off.
165# tandyrate: Sample rate of the Tandy 3-Voice generation.
166#            Possible values: 22050, 44100, 48000, 32000, 16000, 11025, 8000, 49716.
167#    disney: Enable Disney Sound Source emulation. (Covox Voice Master and Speech Thing compatible).
168
169pcspeaker=true
170# pcrate=22050
171pcrate=44100
172tandy=auto
173# tandyrate=22050
174tandyrate=44100
175disney=true
176
177[joystick]
178# joysticktype: Type of joystick to emulate: auto (default), none,
179#               2axis (supports two joysticks),
180#               4axis (supports one joystick, first joystick used),
181#               4axis_2 (supports one joystick, second joystick used),
182#               fcs (Thrustmaster), ch (CH Flightstick).
183#               none disables joystick emulation.
184#               auto chooses emulation depending on real joystick(s).
185#               Possible values: auto, 2axis, 4axis, 4axis_2, fcs, ch, none.
186#        timed: enable timed intervals for axis. (false is old style behaviour).
187#     autofire: continuously fires as long as you keep the button pressed.
188#       swap34: swap the 3rd and the 4th axis. can be useful for certain joysticks.
189#   buttonwrap: enable button wrapping at the number of emulated buttons.
190
191joysticktype=ch
192timed=true
193autofire=false
194swap34=true
195buttonwrap=true
196
197[serial]
198# serial1: set type of device connected to com port.
199#          Can be disabled, dummy, modem, nullmodem, directserial.
200#          Additional parameters must be in the same line in the form of
201#          parameter:value. Parameter for all types is irq.
202#          for directserial: realport (required), rxdelay (optional).
203#                           (realport:COM1 realport:ttyS0).
204#          for modem: listenport (optional).
205#          for nullmodem: server, rxdelay, txdelay, telnet, usedtr,
206#                         transparent, port, inhsocket (all optional).
207#          Example: serial1=modem listenport:5000
208#          Possible values: dummy, disabled, modem, nullmodem, directserial.
209# serial2: see serial1
210#          Possible values: dummy, disabled, modem, nullmodem, directserial.
211# serial3: see serial1
212#          Possible values: dummy, disabled, modem, nullmodem, directserial.
213# serial4: see serial1
214#          Possible values: dummy, disabled, modem, nullmodem, directserial.
215
216serial1=directserial realport:com1
217serial2=dummy
218serial3=disabled
219serial4=disabled
220
221[dos]
222#            xms: Enable XMS support.
223#            ems: Enable EMS support.
224#            umb: Enable UMB support.
225# keyboardlayout: Language code of the keyboard layout (or none).
226
227xms=true
228ems=true
229umb=true
230keyboardlayout=auto
231
232[ipx]
233# ipx: Enable ipx over UDP/IP emulation.
234
235ipx=true
236
237[autoexec]
238# Lines in this section will be run at startup.
239@ECHO OFF
240MIXER MASTER 75:75
241MOUNT C C:\GAMES -FREESIZE 1000
242# VER SET 5 0
243VER SET 7 10
244SET PATH=C:\;C:\DOS;C:\FED;GM_RESET;C:\NC;C:\NE;C:\NU;C:\PATH;C:\PKZIP;C:\TEMP;Z:\
245SET TEMP=C:\TEMP
246SET TMP=C:\TEMP
247C:
248CLS

robertmo wrote:

(you use fullscreen=true, what if you use fullscreen=false?)

Same thing. Luckily (or rather, unluckily <grin>) I'm currently having the mouse problem; so I edited my DOSBox.conf to "fullscreen=false", ran DOSBox, and then DOOM2. As before, windowed mode was fine, but after ALT+ENTER(ing) to fullscreen mode, the mouse sensitivity was slow again.

Hey folks, long time, no type.

Hate to dig up this ancient thread, but I'm still plagued by this exact same problem. Something that I've recently discovered though (re: ALT+TABbing to the DOSBox "Status" window):

I usually run DOSBox with the "-noconsole" command-line parameter. I noticed that it I run DOSBox with that, then I experience the problem. If I run DOSBox *WITHOUT* the "-noconsole" command-line parameter (allowing DOSBox to start up it's "Status" window in the background), the problem was *NOT* there.

I tested this quite a few times with the exact same results... add the command-line parameter, the problem was there. Remove the command-line parameter, the problem was not there.

I didn't even have to ALT+TAB to the "Status" window, and then back to the game again (like I had previously mentioned in this message thread); without the "-noconsole" command-line parameter, it worked perefectly every time 😀

Any idea as to what could cause this weird behavior? There's been several other messages here in the forums over the past 2 years or so refering to the horizintal axis mouse response problem.

(Edit) P.S. Forgot to mention... I noticed that when using the CTMouse driver (my "quick fix" that I've mentioned previously), my middle mouse button doesn't function at all (so I'd prefer not to use that driver, as I also use the middle mouse button in all of the WAD-based games in question).

how exactly do you start dosbox with and without "-noconsole". Do you doulble click dosbox icon, run from cmd... sth else? How do you start both cases exactly?