strange dos mouse behaviour in win2k
I have a strange problem with my mouse in certain dos games under win2k. In about four or five of them (some run just fine), the mouse cursor appears to be confined to a rectangular portion of the screen, usually the top left, and the cursor will not move out of that area (but it will move within it).
I have a strange problem with my mouse in certain dos games under win2k. In about four or five of them (some run just fine), the mouse cursor appears to be confined to a rectangular portion of the screen, usually the top left, and the cursor will not move out of that area (but it will move within it). The size of this area of different for each game but it does not change between reboots/reloads for any one game. No combination of tweaks and voodoo magic that I've tried can to anything to change this. Does anyone have this problem, is able to fix it or has even heard of anything like this?
Participate on our website and join the conversation
This topic is archived. New comments cannot be posted and votes cannot be cast.
Responses to this topic
Nope, no fix.
Http://vogons.zetafleet.com
Go the the VDMSound forum and post this post there.
This is the author's forum of a tool that I seem to remember that he made. Hopefully he can give ya better advice....
Most likely tho the program will not work and your best bet would be Windows XP with it's very few added VESA modes or Connectix Virtual PC or real DOS (Ranked in order from least support to most support for the game)
Http://vogons.zetafleet.com
Go the the VDMSound forum and post this post there.
This is the author's forum of a tool that I seem to remember that he made. Hopefully he can give ya better advice....
Most likely tho the program will not work and your best bet would be Windows XP with it's very few added VESA modes or Connectix Virtual PC or real DOS (Ranked in order from least support to most support for the game)
crap! I was afraid of that.
I've heard of this VDMS thiing just by briefly skimming the forums here, but it's a sound emulator, is it no? I don't know how it would be able to help me. I'll give it a shot, though. Is this a common problem, anyway? It seems like more games have it than not...
Yarrr, tis not good to be postin' as drunk as I am at the moment. :x Aw crap, and now jhiccups. Tha'll learn me good for having too many scredrivers. bah...
I've heard of this VDMS thiing just by briefly skimming the forums here, but it's a sound emulator, is it no? I don't know how it would be able to help me. I'll give it a shot, though. Is this a common problem, anyway? It seems like more games have it than not...
Yarrr, tis not good to be postin' as drunk as I am at the moment. :x Aw crap, and now jhiccups. Tha'll learn me good for having too many scredrivers. bah...
I was just curious if this was occuring about you toggled out of your game. Perhaps you should mono-task and just stay in your game until your done if that's happens to be what's causing your problems.
Good Luck,
Christian Blackburn
;(
Good Luck,
Christian Blackburn
;(
No, I'm not switching between the game and windows.
Also, unforunately, the mouse fix doesn't work, at least not for the game I'm fighting with now (Ascendancy). I've tried changing the parameters (X x Y) to various numbers, from 640x480 all the way to 1024x768 and it doesn't make any difference at all in the game.
I've also thought of messing with the code for mouseset (not the assembler part - the c part; the assembler bit is just plain scary), just to see what I could break, but MSVC++ doesn't like this code a lot, denying me my fun. Probably something about messing with registers that Mr. Gates doesn't apperciate.
Also, unforunately, the mouse fix doesn't work, at least not for the game I'm fighting with now (Ascendancy). I've tried changing the parameters (X x Y) to various numbers, from 640x480 all the way to 1024x768 and it doesn't make any difference at all in the game.
I've also thought of messing with the code for mouseset (not the assembler part - the c part; the assembler bit is just plain scary), just to see what I could break, but MSVC++ doesn't like this code a lot, denying me my fun. Probably something about messing with registers that Mr. Gates doesn't apperciate.
With your mouse you might try uninstalling any proprietary drivers and just use the ones that came with Win2K. Also you could move your USB mouse to PS/2, PS/2 to Serial, etc..
Hey I used to test Windows 98SE (4 months) and 2000 (only for 2 weeks). We had access to almost all the OS symbols, far more than the public will ever get, but they didnt' teach us how to debug. Developers would just connect remotely over our network and try to debug things. Sometimes the remote debugging wouldn't work and then they'd have to come watch it crash in first person. It was cool on Windows 98 everybody else would see blue screens, but with the symbols installed you could see what was running and which .exe and line of code trapped the system.
¡Qué tengas suerte! (Good Luck)
Hey I used to test Windows 98SE (4 months) and 2000 (only for 2 weeks). We had access to almost all the OS symbols, far more than the public will ever get, but they didnt' teach us how to debug. Developers would just connect remotely over our network and try to debug things. Sometimes the remote debugging wouldn't work and then they'd have to come watch it crash in first person. It was cool on Windows 98 everybody else would see blue screens, but with the symbols installed you could see what was running and which .exe and line of code trapped the system.
¡Qué tengas suerte! (Good Luck)
Quote:With your mouse you might try uninstalling any proprietary drivers and just use the ones that came with Win2K. Also you could move your USB mouse to PS/2, PS/2 to Serial, etc..
Hey I used to test Windows 98SE (4 months) and 2000 (only for 2 weeks). We had access to almost all the OS symbols, far more than the public will ever get, but they didnt' teach us how to debug. Developers would just connect remotely over our network and try to debug things. Sometimes the remote debugging wouldn't work and then they'd have to come watch it crash in first person. It was cool on Windows 98 everybody else would see blue screens, but with the symbols installed you could see what was running and which .exe and line of code trapped the system.
¡Qué tengas suerte! (Good Luck)
sounds cool bro
but then again i am quite drunk
but it still sounds cool
but doesn't nt give you all the info you need
bsod equals find the problem and find the solution to me
it is those little errors that don't crash the system that piss me off
Hey I used to test Windows 98SE (4 months) and 2000 (only for 2 weeks). We had access to almost all the OS symbols, far more than the public will ever get, but they didnt' teach us how to debug. Developers would just connect remotely over our network and try to debug things. Sometimes the remote debugging wouldn't work and then they'd have to come watch it crash in first person. It was cool on Windows 98 everybody else would see blue screens, but with the symbols installed you could see what was running and which .exe and line of code trapped the system.
¡Qué tengas suerte! (Good Luck)
sounds cool bro
but then again i am quite drunk
but it still sounds cool
but doesn't nt give you all the info you need
bsod equals find the problem and find the solution to me
it is those little errors that don't crash the system that piss me off
I have a friend who can decompile .exes and remove dialogs and what not. I wish I knew how to do likewise. I understand it can be rather time consuming though. So he isn't very eager to do it as a favor for me . Oh well perhaps I will just have to learn how to do it one of these days.
