It's not your fault. What you have done should work. Having said that, I'm not surprised Glidos has problems on win98se. I haven't had a win98se installation to test on for years, so years of changes haven't been tested there. On the other hand, people quite recently have reported having it work (which surprised me).

The Glidos.bat problem is very odd. That's something I wont have changed and so will have worked at some point in its current form. Can you maybe send a screen shot of the error.

Also, how close to this is your installation directory:

i got it sorted. installing to the dafault program files location (or any location with spaces) breaks glidos under win9x. the dynamic .bat files that glidos generates don't use quotes for any the paths. i moved the glidos folder directly under c:\ to resolve.

that being said, i still can't get glidos working on my system for any of the 3 games in either opengl or d3d mode due to some incompatibility (presumably with my radeon 9800). the games do sort of start, but quickly crash (often the entire system) when any 3d rendering is attempted. there might be some magic combination of settings to make it work, but i haven't found it yet.

is glidos more than a frontend for openglide and psvoodoo? could i attempt to get (older) versions of those working independantly and integrate them back into glidos or is that too simplistic? (i suppose i will try older releases of glidos as well.)

there's no uninstaller for glidos. it appears everything is done in ini & bat files so is the installer only copying files to the install directory and creating shortcuts on the start menu & desktop? no registry or windows folder modifications?

stanwebber wrote on 2026-09-09, 08:07:

is glidos more than a frontend for openglide and psvoodoo? could i attempt to get (older) versions of those working independantly and integrate them back into glidos or is that too simplistic? (i suppose i will try older releases of glidos as well.)

there's no uninstaller for glidos. it appears everything is done in ini & bat files so is the installer only copying files to the install directory and creating shortcuts on the start menu & desktop? no registry or windows folder modifications?

It's a little more than a frontend. OpenGlide and psVoodoo are for WIndows-based Glide games. DOS games cannot use them. Glidos uses a replacement Glide2x.ovl to receive the DOS game's graphics commands, serialises them, sends them down a data pipe and calls into OpenGlide or psVoodoo. It also does the texture, FMV overriding if you want TRX textures and the higher quality cut scenes.

I installed W98SE on 86Box, and sort of got it working with TR I, but it was a fiddle:

, As you mention there's a problem with install locations with spaces in. Must have worked at some stage because the first version of Glidos was 98/95 only. Looks easy to fix. I'll have a go sometime soonish.

In my experience Glidos 1.59+ doesn't work reliably in Win 98SE (and earlier) while seem to work correctly in WinME (both in OpenGL ad D£D), no matter if you're using VMware or Virtualbox.

If one wants rock solid experience the solution is to use a version that doesn't came with DOSBOX like 1.35, 1.41 .... (easy to spot given the installer size difference)

As you mention there's a problem with install locations with spaces in

Strangely enough I never had troubles with spaces, but I noticed that the installer doesn't obey to the localization setting.

The installer (by default) installs in \program files\Glidos instead (say) \programmi\Glidos for the Italian version.

Obviously you can change that manually, but it's easy to get distracted ad not notice the problem, a problem that's bigger than appears given the 8.3 name which become progra~2, and may lead to unexpected consequences in programs other than Glidos.

In my experience Glidos 1.59+ doesn't work reliably in Win 98SE (and earlier) while it seems to work correctly in WinME (both in OpenGL ad D3D), no matter if you're using VMware or Virtualbox.

If one wants rock solid experience the solution is to use a version that doesn't came with DOSBOX like 1.35, 1.41 .... (easy to spot given the installer size difference)

As you mention there's a problem with install locations with spaces in

Strangely enough I never had troubles with spaces, but I noticed that the installer doesn't obey to the localization setting.

The installer (by default) installs in \program files\Glidos instead (say) \programmi\Glidos for the Italian version.

Obviously you can change that manually, but it's easy to get distracted ad not notice the problem, a problem that's bigger than appears given the 8.3 name which become progra~2, and may lead to unexpected consequences in programs other than Glidos.

@stanwebber

Anyway did you select windows rather than dosbox in the settings (dosbox is meant for the NT branch of the windows family)

I was fooling myself before. It looked like I had it working because the emulator had a voodoo graphics card. It's actually all sorts of broken. v1.32 seems to work though, so I'm hopeful to be able to work out how I broke it.

i installed glidos v1.41 and achieved partial success in win98se. the games are completely playable under both opengl & direct3d except for 1 issue: the command prompt window (or fullscreen) is not capturing any mouse events so i'm stuck with keyboard control only. is there an easy fix for this or do i have to go looking for more compatible glidos versions?

Glidos wrote on 2026-09-09, 22:39:

I was fooling myself before. It looked like I had it working because the emulator had a voodoo graphics card. It's actually all sorts of broken. v1.32 seems to work though, so I'm hopeful to be able to work out how I broke it.

Just use VMware or Virtualbox + SoftGPU, both work perfectly

VMware doesn't play the initial blink video (black or striped screen) but is more convenient because the vmware tools can be installed (custom install, exclude the vga driver).

You can even have the FSAA enabled , if the application ask for it.

On my, not so powerful, Ryzen 2400G with it's integrated VGA I get 16~20 FPS in D3D @1400x1050 or 30 FPS (the upper limit) @1280x1024, using custom textures.

P.S. speaking of FSAA would be a nice improvement to have a flag to enable it.

P.S2. I'm not sure about the status of 1.31 or so, but maybe it didn't yet understand the new style custom textures, better to use something newer like 1.4x.

stanwebber wrote on 2026-09-10, 23:20:

i installed glidos v1.41 and achieved partial success in win98se. the games are completely playable under both opengl & dirrct3d except for 1 issue: the command prompt window (or fullscreen) is not capturing any mouse events so i'm stuck with keyboard control only. is there an easy fix for this or do i have to go looking for more compatible glidos versions?

What mouse are you talking about? It's Tomb Raider not quake, there isn't mouse support.

The Solutor wrote on Yesterday, 05:34:

What mouse are you talking about? It's Tomb Raider not quake, there isn't mouse support.

i'm trying to play blood.

The Solutor wrote on Yesterday, 05:32:

Just use VMware or Virtualbox + SoftGPU, both work perfectly […]
Show full quote

Just use VMware or Virtualbox + SoftGPU, both work perfectly

VMware doesn't play the initial blink video (black or striped screen) but is more convenient because the vmware tools can be installed (custom install, exclude the vga driver).

You can even have the FSAA enabled , if the application ask for it.

On my, not so powerful, Ryzen 2400G with it's integrated VGA I get 16~20 FPS in D3D @1400x1050 or 30 FPS (the upper limit) @1280x1024, using custom textures.

Interesting. My first attempt was under KVM, but ran into problems (my memory these days... I've forgotten exactly what the problems were!). I avoided VMware because (perhaps wrongly) recollecting that it didn't play well with Hyper-V. I need Hyper-V for WSL2, and I need WSL2 for work.

P.S. speaking of FSAA would be a nice improvement to have a flag to enable it.

I might look into that... if I can get this all working again.

P.S2. I'm not sure about the status of 1.31 or so, but maybe it didn't yet understand the new style custom textures, better to use something newer like 1.4x.

I eventually found that 1.45 is where it first got broken. 1.44 works and has the texture support. Still, I'd like to get it working again in the main release.

Glidos wrote on Yesterday, 08:28:

Interesting. My first attempt was under KVM

KVM is useless when you need 3D or multimedia in Windows guest, just there aren't (yet) drivers for windows that are stable and/or usable.

I avoided VMware because (perhaps wrongly) recollecting that it didn't play well with Hyper-V. I need Hyper-V for WSL2, and I need WSL2 for work.

VMware works inside Hyper-V starting from VMware workstation 15.5.x and starting from Windows 2004 (to be pedantic since build 19041.2xx)

Virtualbox (I think) works since 6.1.x and since Windows 1803

Both are slower than w/o Hyper-V, but VMware usually runs acceptably even for way more demanding tasks than Win9x, on the other hand Virtualbox inside Hyper-V becomes unbearably slow (it has even a turtle icon to make the point clear)

In any case is pretty easy to dualboot the host with or w/o hyper-V, no need to install or uninstall anything

I eventually found that 1.45 is where it first got broken. 1.44 works and has the texture support. Still, I'd like to get it working again in the main release.

Thanks, good to see that you have still a bit of love to dedicate to Glidos

Been fighting VMware and Win98SE all day. Sort of working now, but the FMVs play black - sound but no video.

Glidos wrote on Yesterday, 19:09:

Been fighting VMware and Win98SE all day. Sort of working now, but the FMVs play black - sound but no video.

I warned you of that limitation in previous messages, maybe you overlooked that detail, whatever that's the current status, not your fault.

Virtualbox shows the blink videos correctly, but like I said it's slow if used inside hyper-V.

The good news is that you can just copy the Win98.vmdk you already have, and use it to boot a virtualbox machine, just reinstall SoftGPU the get the settings tailored for it, and you're ready to go, in matter of 5/10 minutes.

I have no idea of how powerful your host machine is, maybe vbox works fast enough for you, even if Hyper-V is enabled.

BTW if nothing else helps

This is how to add a boot entry to boot the host machine with or w/o hyper-v at will

https://dev.to/deadlybyte/switch-off-hyper-v- … in-windows-5gpc

Not sure if it's feasible in your case (maybe you're running something in WSL2 that can't be interrupted) but anyway is something that can come handy in a variety of scenarios.

Ah yes, I'm hopeless at picking up detail. That's good. I'm happy so long as my set up is running as it should, and good to know I can swap to virtualbox so easily. Thanks for the info.

Glidos wrote on Yesterday, 21:20:

Ah yes, I'm hopeless at picking up detail. That's good. I'm happy so long as my set up is running as it should, and good to know I can swap to virtualbox so easily. Thanks for the info.

You're welcome.

P.S. Unlike the Hyper-V case, Vbox and vmware normally don't fight each-other, so you can run any combination of VMs (if needed), and when powered off they don't have any side effect other than having some virtual additional network cards installed.