VOGONS


First post, by w0lf42

User metadata
Rank Newbie
Rank
Newbie

I want to play MechWarrior 2 Windows 98SE in 800x600 resolution. The problem is that every time I increase the resolution from 640x480 to 800x600 and start moving the mouse, the system crashes. I've installed other games on this system (Diablo II, FreeSpace 3, MDK, MDK2) and none of them have issues with the mouse at any resolution.

Operating System:
Windows 98SE

MechWarrior 2 Version:
MECHWARRIOR 2: Enhanced for the Diamond Monster 3D

I've attempted to use Microsoft Intellimouse , Logitech MouseWare 9.7.9.1, and no mouse drivers/utilities.

I'm using the FastVoodoo2 V4.6 drivers. I've also tried the 3D Blaster Voodoo2.

Added these files to my MW2 installation directory. Got them from the Diamond Monster 3D V4.10.01.1600
Glide.dll
Sst1init.dll

I created this Batch File. I found these settings on VOGONS Wiki
set SST_GRXCLK=90
set SST_FT_CLK_DEL=0x4
set SST_TF0_CLK_DEL=0x6
set SST_TF1_CLK_DEL=0x6
set SST_VIN_CLKDEL=0x1
set SST_VOUT_CLKDEL=0x0
set SST_TMUMEM_SIZE=2

I've seen (I can't remember were) someone suggesting this batch file (but I haven't used it):
set SST_GRXCLK=90
set SST_FT_CLK_DEL=0x4
set SST_TF0_CLK_DEL=0x6
set SST_TF1_CLK_DEL=0x6
set SST_VIN_CLKDEL=0x1
set SST_TMUMEM_SIZE=2
set SSTV2_FASTMEM=1
set SSTV2_FASTPCIRD=1
set FX_GLIDE_ALLOC_COLOR=3

Honestly, I don't really understand what the different settings/commands in the batch file do.

Motherboard
Shuttle AV18E AC18V31

CPU
CPU Intel Pentium III EB Coppermine Socket 370 933 MHz

RAM
512MB.

Video
1 x AGP GeForce2 Ultra 64MB (This looks like a generic reference card.)
2 x PCI Creative Labs Voodoo2 12MB (running in SLI)

Sound
1 x ISA Yamaha YMF719E-S
1 x PCI Creative Labs Sound Blaster Live! 5.1
1 x Creative Sound Blaster CT4660 Expansion Board

Network / Storage
1 x PCI Linksys 10/100 Etherfast Network Card
1 x PCI Fast Trak 100 Ultra ATA/100 Raid Card (Running in Raid1)
1 x IDE Pioneer DVD-105S DVD-Rom Drive DVD-Rom
1 x IDE Generic 3.5" Floppy Drive
2 x IDE Maxtor Basics 7200RPM ATA/100 160GB Hard Drive

Last edited by w0lf42 on 2020-09-28, 14:56. Edited 1 time in total.

Reply 2 of 26, by vetz

User metadata
Rank l33t
Rank
l33t
Carrera wrote on 2020-09-28, 09:23:

That version will probably only work with the Diamond Voodoo...

No, this version works on any Voodoo 1 or Voodoo 2 card.

If the game runs fine in 640x480 and not 800x600 I guess its due to not having all the variables needed.

The settings I've used previously is:

set SST_GRXCLK=90 set SST_FT_CLK_DEL=0x4 set SST_TF0_CLK_DEL=0x6 set SST_TF1_CLK_DEL=0x6 set SST_VIN_CLKDEL=0x1 set SST_TMUMEM_S […]
Show full quote

set SST_GRXCLK=90
set SST_FT_CLK_DEL=0x4
set SST_TF0_CLK_DEL=0x6
set SST_TF1_CLK_DEL=0x6
set SST_VIN_CLKDEL=0x1
set SST_TMUMEM_SIZE=2
set SSTV2_FASTMEM=1
set SSTV2_FASTPCIRD=1
set FX_GLIDE_ALLOC_COLOR=3
mech2.exe

From my previous comments:

1. FastVoodoo drivers does NOT work. Install these from 3DFX (3.03): http://falconfly.vogonswiki.com/downloads/voodoo2-30300.zip
2. Copy Glide.dll and ss1init.dll from the driver to the game installation directory.
3. Make a .bat file using notepad with the following: (see above)
4. Enjoy!

3D Accelerated Games List (Proprietary APIs - No 3DFX/Direct3D)
3D Acceleration Comparison Episodes

Reply 3 of 26, by w0lf42

User metadata
Rank Newbie
Rank
Newbie

I appreciate the quick response.

I tried both changing the variables in my batch file and using the voodoo driver that you linked. Unfortunately, this did not work.

Do you or anyone else have any other suggestions?

Thanks

Reply 4 of 26, by vetz

User metadata
Rank l33t
Rank
l33t

Do other games work at 800x600?

Also try running the CPU at 100mhz FSB. I have had issues with Voodoo cards at 133mhz fsb.

3D Accelerated Games List (Proprietary APIs - No 3DFX/Direct3D)
3D Acceleration Comparison Episodes

Reply 5 of 26, by w0lf42

User metadata
Rank Newbie
Rank
Newbie

Do other games work at 800x600?

Quite a few actually:

  • Diablo 2
  • Unreal
  • MDK
  • MDK2
  • Earthworm Jim 3D
  • FreeSpace2

Also try running the CPU at 100mhz FSB. I have had issues with Voodoo cards at 133mhz fsb.

I've tried the following processors:

  • Intel Celeron 850 (100MHz FSB)
  • Intel Pentium III 1 GHz (133MHz FSB)
  • Intel Pentium III 933 MHz (133MHz FSB)

Reply 6 of 26, by vetz

User metadata
Rank l33t
Rank
l33t

Do you have any Z buffer settings switched on the Voodoo interface? Mechwarrior 2 does not use Z-buffer in 800x600

3D Accelerated Games List (Proprietary APIs - No 3DFX/Direct3D)
3D Acceleration Comparison Episodes

Reply 7 of 26, by kjliew

User metadata
Rank Oldbie
Rank
Oldbie

Was it only the problem at 800x600 or the standard 640x480, too?

I recalled that I couldn't use mouse on the Mech2 3Dfx version. It would crash after some rapid shooting with mouse clicks. Just moving mouse was fine. I was playing inside QEMU VM though. I couldn't remember if mouse would work on real PC with Voodoo1 since I didn't play with mouse back then, just pure keyboard controls. I finished the entire game both Jade Falcon and Wolf missions back then without using mouse at all.

The Titanium series collector's version works fine with mouse point-and-shoot. Prior to Quake2 and Half-Life, it wasn't very common to play games with mouse point-and-shoot. My friends finished Quake1 with just keyboard controls.

Reply 8 of 26, by kjliew

User metadata
Rank Oldbie
Rank
Oldbie

Interesting, I just replayed Jade Falcon mission 1 inside QEMU KVM checking out the mouse point-and-shoot. I was able to complete the mission flawlessly, so it actually worked. Using mouse control, there is a new technique of controlling a mech by constantly re-adjusting torso to reticle with the 'M' key to have the mech move into the direction. It could mimic the game in FPS-style. 😁

Reply 9 of 26, by w0lf42

User metadata
Rank Newbie
Rank
Newbie

Do you have any Z buffer settings switched on the Voodoo interface? Mechwarrior 2 does not use Z-buffer in 800x600

I don't see any Z buffer settings. Here are my Advance 3Dfx settings via the control panel
EdRt0YN.png
I got a program called Voodoo 2 Tweaker and here are the settings I see
xxC2cg8.png

Was it only the problem at 800x600 or the standard 640x480, too?

only at 800 x 600

Prior to Quake2 and Half-Life, it wasn't very common to play games with mouse point-and-shoot.

I remember that period as a time when players switched from keyboard only to keyboard and mouse. In fact, the Doom II manual suggests that people play with the mouse:

When you're comfortable playing the game, try using the keyboard and the mouse simultaneously. The mouse provides fine control for aiming your weapon (allowing you to smoothly rotate right or left) while the keyboard permits you to activate the many useful functions of the game.

Reply 11 of 26, by w0lf42

User metadata
Rank Newbie
Rank
Newbie

So, more fun. Not sure if this is another issue or somehow related to the same one.

I have been jumping between drivers. I got my system back and up and running stable (or, "Win98 stable").

  • Launched Diablo II (in 800x600 with glide) and it worked fine.
  • Launched MechWarrior2 (in 800x600 with glide) with a hard lock and some artifacts of Diablo II on the screen.
  • Turned off the computer and turned it on again.
  • Launched MechWarrior 2 (in 800x600 with glide) and it hard locked with artifacts of Diablo II.

Ys5P3Wo.jpg

Reply 12 of 26, by vetz

User metadata
Rank l33t
Rank
l33t

I guess those artifacts come from the environment variables you enable when running Mech2 which does not like it when you then run Diablo 2.

When you powered down I dont think it was off long enough for all the memory to clear.

Might also be a hardware problem with one of your Voodoo's. I'd first try to disable the SLI and that does not help, swap the cards around.

3D Accelerated Games List (Proprietary APIs - No 3DFX/Direct3D)
3D Acceleration Comparison Episodes

Reply 13 of 26, by w0lf42

User metadata
Rank Newbie
Rank
Newbie

Okay. I've tried some more things.

  • New keyboard and mouse
  • Keyboard/mouse in USB and PS/2 connections (both are compatible with the USB-PS/2 adapter)
  • Removing all other ISA/PCI cards (except my Raid controller card)
  • New memory (and trying it in different RAM locations)
  • Only using one Voodoo2 card (I tried both)
  • Voodoo2 card in a different PCI location
  • New DVD/CD Drive
  • Unplugged my Floppy drive

Some things that I will try when stuff arrives

  • PCI primary video card
  • Installing Whiplash - another Voodoo1 game that should work with the same work around as MW2

Some of the following questions may show my complete lack of knowledge.

  • Do I need to have any of my DOS config.sys and autoexec.bat settings?
  • If I do, does this go in the Exit To DOS -> Properties -> Advanced?
  • Do I need to manage the DOS memory?

autoexec.bat

DEVICE=C:\WINDOWS\HIMEM.SYS /TESTMEM:OFF REM DEVICE=C:\WINDOWS\HIMEM.SYS DOS=HIGH,UMB DEVICE=C:\WINDOWS\EMM386.EXE RAM AUTO I=B […]
Show full quote

DEVICE=C:\WINDOWS\HIMEM.SYS /TESTMEM:OFF
REM DEVICE=C:\WINDOWS\HIMEM.SYS
DOS=HIGH,UMB
DEVICE=C:\WINDOWS\EMM386.EXE RAM AUTO I=B000-B7FF
REM DEVICE=C:\WINDOWS\EMM386.EXE RAM
DEVICEHIGH=C:\DRIVERS\CDRom\VIDECDD.SYS /D:OPTICAL

FILES=30
BUFFERS=30
LASTDRIVE=Z
DEVICE=C:\WINDOWS\SETVER.EXE

config.sys

SET PROMPT=$p$g SET winbootdir=C:\WINDOWS SET PATH=C:\WINDOWS;C:\WINDOWS\COMMAND SET BLASTER=A220 I7 D1 H5 P330 T6 LH C:\WINDOWS […]
Show full quote

SET PROMPT=$p$g
SET winbootdir=C:\WINDOWS
SET PATH=C:\WINDOWS;C:\WINDOWS\COMMAND
SET BLASTER=A220 I7 D1 H5 P330 T6
LH C:\WINDOWS\COMMAND\MSCDEX.EXE /D:OPTICAL
LH C:\DRIVERS\Mouse\CTMOUSE.EXE /R9
DOSKEY
C:\DRIVERS\Ekm049\Ek1m.exe -f C:\Drivers\EKM049\Ek1m.cfg
C:\Drivers\SETYMF\Setymf.exe /INITONLY

I have tried CuteMouse 1.9, 2.0, and 2.1

Reply 14 of 26, by Gamecollector

User metadata
Rank Oldbie
Rank
Oldbie

Well, glide.dll and sst1init.dll were last updated before Voodoo2 release so bad compatibility is expected...
Voodoo2 control panel and SSTV2 variables not affect this interface.
1) Try another winglide1x game.
2) Download the SDK (2.1.1) from VogonsDrivers and try glide.dll, sst1init.dll and fxmemmap.vxd from the SDK. Then glide.dll and sst1init.dll w|o fxmemmap.vxd.
3) Try 2.1.1 SDK tests. IIRC there is a test for resolutions and refresh rates. And this test supports 800×600...

Asus P4P800 SE/Pentium4 3.2E/2 Gb DDR400B,
Radeon HD3850 Agp (Sapphire), Catalyst 14.4 (XpProSp3).
Voodoo2 12 MB SLI, Win2k drivers 1.02.00 (XpProSp3).

Reply 15 of 26, by kjliew

User metadata
Rank Oldbie
Rank
Oldbie

If you have a very, very fast CPU, then you can use my Glide 2.1.1->Glide 2.4 wrapper from here
Or, you need to find Voodoo2 drivers that actually include GLIDE.DLL and try that, and hopefully it is a OEM vendor officially packaged driver instead of community re-packaged.

Voodoo2 does not officially support Glide 2.1.1 which is used by Mechwarrior 2.

It is more convenient to play the game with Glide wrappers or through emulation such as (QEMU, PCem) nowadays on modern PCs.

Reply 17 of 26, by w0lf42

User metadata
Rank Newbie
Rank
Newbie

Okay, I think that I've looked on virtually every page on the internet 😀

I landed on a 3dfx archive and see some files that look promising.

You mentioned the Glide 2.1.1 SDK. I grabbed the 3dfx Software Developer's Kit V1.0. If I should try something else, please let me know. Thanks.

Reply 18 of 26, by Gamecollector

User metadata
Rank Oldbie
Rank
Oldbie

http://falconfly.3dfx.pl/downloads/webrelease-glide211.zip

Asus P4P800 SE/Pentium4 3.2E/2 Gb DDR400B,
Radeon HD3850 Agp (Sapphire), Catalyst 14.4 (XpProSp3).
Voodoo2 12 MB SLI, Win2k drivers 1.02.00 (XpProSp3).

Reply 19 of 26, by firage

User metadata
Rank Oldbie
Rank
Oldbie

A quick general thing to check with environment variables since it wasn't mentioned: make sure you're not out of environment space and the variables are in memory.

My big-red-switch 486