VOGONS


First post, by Edmond Dantes

User metadata
Rank Newbie
Rank
Newbie

So, awhile ago I built an old gaming PC which I have dubbed Mazinkaiser. I recently bought a Logitech PS/2 optical mouse for it, and so have been playing mouse-driven games. I use the cutemouse driver, and most MS-DOS games detect the mouse just fine.

I have my comp set up to give me a boot menu, offering either to boot into Windows 98(SE) or into one of several MS-DOS configurations. (this is REAL dos, not an emulator).

So I decided to play Space Quest IV. I remember from my old PC that this game had speed issues, so I disable the cpu cache. I also remember that it would only play voices correctly if I told it my SB16 was a "Thunderboard"--I tested, and that's still true here (and this, too, requires disabling the CPU cache). So I sit down, watch the opening cinematic, and then try to play...

... It's not registering my mouse movement. So I decide to use the keyboard, but holy smokes, its not seeing THAT either. So I can't even exit the game.

So I press my PC's reset button. And try again. This time I notice that it sees the mouse at first, for like a split-second, but then stops seeing it. And when this happens, I can press whatever keys I want and nothing happens--even CTRL ALT DELETE does nothing.

I tried different memory settings, and even using the MS-DOS mouse driver to see if that was it, but the same thing happened.

At the moment, I only have two theories:

1. Since Mazinkaiser is 700mhz (the last PC that SQ4 worked fine on was 500mhz) I may need to slow the game down even more.

2. The game doesn't like that both my keyboard and my mouse use PS/2 inputs and will only work with COM mice. Seems unlikely, as every other MS-DOS game I have works fine with my current keyboard and mouse, but still.

But on the off-chance that I test these theories and neither turns out true, I was hoping you guys could come up with something. Anyone have any ideas? Thanks in advance.

Reply 1 of 6, by Malik

User metadata
Rank l33t
Rank
l33t

If you have other Sierra VGA games, have you tried with them and is this problem replicated with them too?

If only SQ4 is giving you problems, have you tried these patches? : http://www.sierrahelp.com/Patches-Updates/Pat … iesUpdates.html

Also, don't choose the thunderboard to select your sb16. Use one of these EXE patchers (GOSIERRA or SBSIERRA) to enable fast systems to recognize sound blaster cards properly and to utilize the digitized effects on those systems. : http://www.sierrahelp.com/Utilities/SoundUtilities.html

Generally fast systems are not very friendly with Sierra games.

And finally, what CuteMouse driver are you using? Have you tried with the older 2.0 Alpha driver? 2.0 branch accesses the mouse hardware directly. 2.1 accesses the mouse via BIOS and gave me some problems with games like Seek and Destroy (Jerky and "stuck" mouse.)

5476332566_7480a12517_t.jpgSB Dos Drivers

Reply 2 of 6, by Edmond Dantes

User metadata
Rank Newbie
Rank
Newbie

First, an update:

When I plugged in an old-style serial mouse, the game worked. But I had to completely unplug the ps/2 mouse.

Also, the game works fine with Dosbox.

Now, to answer your questions, Malik.

1. I had actually tried those patches and alternative drivers in the past, and they didn't solve this issue, which is why I've always used the Thunderboard solution. I haven't tried them on my new PC tho.

2. Yes, as far as I know its only SQ4--I think I also tried the SQ1 VGA remake and it played fine.

3. Where can I get the older version of Cutemouse? I was not aware of that difference.

Reply 3 of 6, by Mau1wurf1977

User metadata
Rank l33t++
Rank
l33t++

I swear by the Logitech driver! You can find them online without too many issues...

Also can you lower the FSB and see if it makes a difference?

http://www.uwe-sieber.de/util_e.html

Looking at Mazinkaiser, I must say it's a very very fast machine and IMO not ideal for DOS slow down projects.

A Pentium (Socket 7 for example) based system is what I usually recommend.

My website with reviews, demos, drivers, tutorials and more...
My YouTube channel

Reply 4 of 6, by Edmond Dantes

User metadata
Rank Newbie
Rank
Newbie

Okay, I'll try those drivers. Hopefully one of them will work.

Mazinkaiser wasn't really meant exclusively for Dos, it was more general-purpose classic computer gaming, and my emphasis when building was on preventing overheating (I forget if I said this in the video, but my old PC used to overheat all the damn time). It seems to work fine with most of the Dos games I've thrown at it though.

Reply 5 of 6, by Malik

User metadata
Rank l33t
Rank
l33t

The cutemouse v2.0 driver can be downloaded from the CuteMouse homepage.

I'm using this driver with the Logitech wireless optical PS/2 keyboard + mouse, connected to my Pentium II 400.

5476332566_7480a12517_t.jpgSB Dos Drivers

Reply 6 of 6, by Edmond Dantes

User metadata
Rank Newbie
Rank
Newbie

Okay, so...

I tested both Cutemouse20 and 21, plus Logitech driver 730, and... same thing happened.

If I don't load any mouse driver at all tho, then I can play the game with the keyboard and the audio and everything (when set with SFX to Thunderboard) works fine.

I noticed tho that when I ran the install and set sound effects to "Soundblaster," the mouse worked fine. Unfortunately the sound glitches and the game will eventually lock up, so this solves one problem but introduces another (and yes, I tried using GoSierra as well as other patches I found elsewhere to fix this... didn't help on my old comp, and it didn't help on Mazinkaiser).

I read somewhere that you should set Sierra programs to "Don't use machines extra memory" but I haven't tested that yet. I'm not sure it would help tho.

So yeah, it looks like the only way to play Space Quest IV with a PS/2 optical mouse is to run it through Dosbox.

(Also, I checked, Space Quest IV is the ONLY game in the Space Quest series that had problems with my mouse... none of the other games did.)

(I'm betting that King's Quest VI and Laura Bow II are also gonna give me issues, since those are other games where I had to set the audio to Thunderboard).