wrote:Not very helpful..
So you can raise the cycles count on your own now?
Yeah.. and it didn't help anything.
So you went higher than 30001, like 35000 or what?
So this mouse problem affects all DOS applications and DOSBox v0.72 itself on your WinXP (SP3) system?
Conversely, does your WinXP desktop and Win32 applications have no ill effects concerning any rapid mouse movement? No Win32 application or Explorer crashes? Only DOSBox and DOSBox hosted application crashes?
In the past there were problems between certain nVidia display drivers and the Logitech mouse drivers. Perhaps you have updated both the Logitech SetPoint mouse drivers for your G7 mouse and the nVidia XP drivers for your 7950GTs in the past year? There was just a SetPoint 4.72 release... The nVidia display driver version is not hard to find, you can use the WinXP Device Manager or right click the desktop to get the Display Properties window, then look under the Settings tab for the Advanced button which can take you to the nVidia info...
Heck, if you have another non-Logitech USB mouse you might try that to see if the mouse rapid movement problem goes away, or remains the same no matter what type of mouse or mouse-driver is used.
dvwjr
wrote:So you went higher than 30001, like 35000 or what?
30000, 35000, 40000 and so on up to 50000
wrote:So this mouse problem affects all DOS applications and DOSBox v0.72 itself on your WinXP (SP3) system? […]
So this mouse problem affects all DOS applications and DOSBox v0.72 itself on your WinXP (SP3) system?
Conversely, does your WinXP desktop and Win32 applications have no ill effects concerning any rapid mouse movement? No Win32 application or Explorer crashes? Only DOSBox and DOSBox hosted application crashes?
In the past there were problems between certain nVidia display drivers and the Logitech mouse drivers. Perhaps you have updated both the Logitech SetPoint mouse drivers for your G7 mouse and the nVidia XP drivers for your 7950GTs in the past year? There was just a SetPoint 4.72 release... The nVidia display driver version is not hard to find, you can use the WinXP Device Manager or right click the desktop to get the Display Properties window, then look under the Settings tab for the Advanced button which can take you to the nVidia info...
Heck, if you have another non-Logitech USB mouse you might try that to see if the mouse rapid movement problem goes away, or remains the same no matter what type of mouse or mouse-driver is used.
dvwjr
Currently, what I can tell, I'm running 6.14.11.8208. That's what's listed under damn near every file versoin number under the nvidia control panel.
Setpoint's version is 4.72.40 as is the driver it is using.
I've updated both my nVidia drivers and Logitech drivers several times over the past year. Currently, DOSBox is the only one showing a problem related to mouse movement of any sort. After thinking, could it possibly be the fact I'm running multiple displays on both of my 7950 GT's? As I said, I am stumped and am probably grasping at straws, but for good measure, I am going to go update both my logitech drivers and nvidia drivers, if there are updates that is.
Another thing to try would be booting into Windows Safe mode and trying DOSBox there.
If it works fine in there then it could be Video/Mouse/Some other program/driver loading in Normal mode.
wrote:Another thing to try would be booing into Windows Safe mode and trying DOSBox there.
If it works fine in there then it could be Video/Mouse/Some other program/driver loading in Normal mode.
Took your advice and first booted in safe mode. Dosbox ran without the glitch. Then ran msconfig and disabled startup items, agian, ran without the glitch. I've done a systematic process of elimination, or attempted to anyway. The four culprates I'm left with are NvCpl, NvMcTray, nwiz and the dreaded DLLML. The first three turned up as nVidia services on google, while anyone with a creative card could tell you what DLLML is. So, it's possible it's a confliction with nVidia and Logitech, or nVidia and DOSBox. Or Creative's tossed into the mix. I'll let you know momentarily.
Hmmm, If you are using XP then there should be an option to boot into VGA mode in the boot menu. This will load a generic SVGA drive but everything else about your system will be the same (That way you don't have to worry about uninstalling your video drivers)
wrote:Hmmm, If you are using XP then there should be an option to boot into VGA mode in the boot menu. This will load a generic SVGA drive but everything else about your system will be the same (That way you don't have to worry about uninstalling your video drivers)
I don't think that will be needed. I loaded up everything until all that remained was nwiz. The line in the startup file reads nwiz.exe /install
Upon activating it and rebooting, the glitch reappared. Google says this is Nvidia's Desktop Manager, or something related to it. Since I am running a dual display I do not know if this is a vital process, could anyone shed light.
http://www.neuber.com/taskmanager/process/nwiz.exe.html
Hard to say. I haven't used an Nvidia card in quite awhile. It may or may nor be needed for using dual monitors and it may or may not control fan speed?
Only way to find out is to disable it and see.
wrote:http://www.neuber.com/taskmanager/process/nwiz.exe.html
Hard to say. I haven't used an Nvidia card in quite awhile. It may or may nor be needed for using dual monitors and it may or may not control fan speed?
Only way to find out is to disable it and see.
I disabled it and the glitch is gone, it's used for fancy effects and desktop managing when running more than one monitor from what I can tell. It's the nVidia nView desktop manager exe. But, now comes the hard question.. I don't want to have to leave it disabled.
Has there been a history of the nView manager conflicting with dosbox in the past? If so is there a fix? If not.. can someone find one? Heh. Main reason I want to keep it is for the handy rightclick feature that allows me to send a program instantly from one monitor to another, and the quick shortcuts it provides.
let me pm you something
Water flows down the stream
How to ask questions the smart way!
wrote:Has there been a history of the nView manager conflicting with dosbox in the past? If so is there a fix? If not.. can someone find one? Heh. Main reason I want to keep it is for the handy rightclick feature that allows me to send a program instantly from one monitor to another, and the quick shortcuts it provides.
Looks as if you are not the only one to have problems with the nVidia NWIZ.EXE and a Logitech mouse in the recent past. Here is a link to another possible NWIZ.EXE problem and solution using the Registry for nVidia based systems. May not help in your case, but would not hurt to try if you wish to retain the NWIZ.EXE functionality...
dvwjr
