mwdmeyer wrote on 2026-10-07, 08:14:

Oooh yes I have a 3dfx rush so should be possible.

Everything anyone asks for will be added to this driver!!

Bless you! Can't wait for more Intel iGPU support. That will make a ton of modern ish laptops very usable in Windows98 (and laptops with actually good screens - scaling / aspect ratio handling / supported video modes TBD).

marxveix wrote on Yesterday, 14:14:

One does not disturb other, they both can be there i think, just arb is newer and game chooses what it can use?

Pretty much. I think it should be possible to have both.

Well the GMA 950 is now running native Glide 2. I've got Need for Speed II SE running on it without any issues!

This will be in the next release, only for the Intel Gen3/GMA cards at this stage.

3dfx Glide 2 release https://github.com/michaeldale/velocity9x/rel … ses/tag/v0.14.0

Wow Glide is actually working on the Rage XL in 0.14 already, tested on UT99, its fast. Lol

mwdmeyer wrote on Yesterday, 23:05:

Well the GMA 950 is now running native Glide 2. I've got Need for Speed II SE running on it without any issues!

This will be in the next release, only for the Intel Gen3/GMA cards at this stage.

Nice. I was thinking about suggesting support for the Glide API, but you beat me to it. 😁

I'm interrupt7 on GitHub BTW, will try to do some more testing on the GMA 900 during this weekend.

Nice! Thank you for testing! So happy the GMA 900 even worked at all, seeing as I have no hardware for it.

I'm adding a new feature in 0.15, if you have networking/internet there will be an updater so you can easily get the latest driver and I am planning to add button to submit trace results.

mwdmeyer wrote on Today, 05:42:

Wow Glide is actually working on the Rage XL in 0.14 already, tested on UT99, its fast. Lol

I dont have UT99 at the moment, but NFS2SE did not run on my XL, OpenGL MultiTexture works.

marxveix wrote on Today, 11:19:

mwdmeyer wrote on Today, 05:42:

Wow Glide is actually working on the Rage XL in 0.14 already, tested on UT99, its fast. Lol

I dont have UT99 at the moment, but NFS2SE did not run on my XL, OpenGL MultiTexture works.

When I installed NFS2SE it didn't install the glide exe so needed to copy manually from CD I think. Did you get any specific error message?

My next version will make it much easier to submit issues.

Version 0.15 is now out, this has lots of fixes but the main new feature is an update checker/updater (so you can update directly) and a button to report issues.

After you are running 0.15 in Display Settings -> Velocity9x -> Click "Check for updates". When I release 0.15.1 or 0.16 this will find new version and update your driver automatically.

If you are running a 3d game and you have issues go to:

Display Settings -> Velocity9x Advanced -> Send Report. This will send me a bunch of counters, hardware info etc about your machine and what the 3d engine has been doing, this helps me fix the driver for games I haven't tested or hardware specific bugs.

The driver will never do any internet calls unless you press one of these buttons and there is a confirm before anything is sent.

It is very important to me that this driver is trusted and light weight.

mwdmeyer wrote on Today, 11:21:

When I installed NFS2SE it didn't install the glide exe so needed to copy manually from CD I think. Did you get any specific error message?

My next version will make it much easier to submit issues.

I dont have internet connected to that older pc at the moment, actually nfs2se did start and error is at exit, nfs2se 3dfx demo has error at start.

Velocity9x settings report
Version: 0.15.0
Build: 11d348f
Adapter: ATI 3D Rage XL AGP
PCI ID: 1002:474D
Revision: 65
Video memory: 8128 KB
Mini-VDD build: 11d348f
2D (GDI): CPU (Windows DIB Engine)
Last DirectDraw test: Complete, 3 of 3 pixel checks pass
Active mode: 800 x 600 x 16 bpp
Core / engine clock: Unavailable
Memory clock: Unavailable
Clock detector: ati-mach64-unavailable-v1
Driver stage: enable-ok
Framebuffer: Active - linear aperture mapped
Last GDI test: not run
Mode switching: Live, any depth
Direct3D: Hardware (the chip's own engine) (SYSTEM.INI Direct3D=0)
VSync: Not yet stamped by DirectDraw (SYSTEM.INI VSync=2)
Direct3D DDI: Not yet stamped by DirectDraw (SYSTEM.INI Direct3DDdi=0)
Baseline modes: 640x480, 800x600, 1024x768 at 8/16 bpp and 60 Hz
Runtime modes: 19 published
Mode scan: state=1 listed=40 queried=40 cached=30 flags=0107
Drop reasons: 12,2,0,0,0,9,0,0,0,0,7,0,0
EDID recommendation: 1280x1024 reason=edid-preferred
Inventory generation: 123
Registry sync: ok (generation 109)
Rendering: Windows DIB Engine (software GDI)
DirectDraw: CPU fill and copy, page flip
Direct3D: Hardware (the chip's own engine)
Mini-VDD callbacks: VESA, monitor power
Last report sent: none

NFS2SE 3Dfx Demo error at start

NFS2SEAD caused an invalid page fault in
module <unknown> at 0000:6c095210.
Registers:
EAX=00000000 CS=0187 EIP=6c095210 EFLGS=00010202
EBX=00000001 SS=018f ESP=006ffb84 EBP=00c58bc0
ECX=006ffb88 DS=018f ESI=00000002 FS=0d47
EDX=00000000 ES=018f EDI=00000008 GS=0000
Bytes at CS:EIP:
Stack dump:
0049a804 00562f10 00000000 00000001 00424274 00c40208 00000011 00476141 65465c2e 61746144 5c63705c 5c747241 64696c53 745c7365 656c7469 7366712e

NFS2SE error at game exit (menu not visible)

NFS2SEA caused an invalid page fault in
module KERNEL32.DLL at 0187:bff7b9a6.
Registers:
EAX=00000000 CS=0187 EIP=bff7b9a6 EFLGS=00000246
EBX=00000006 SS=018f ESP=0070fc50 EBP=00000002
ECX=c1580a10 DS=018f ESI=01650210 FS=0e77
EDX=00004de0 ES=018f EDI=00000001 GS=0000
Bytes at CS:EIP:
ff 76 04 e8 13 89 ff ff 5e c2 04 00 56 8b 74 24
Stack dump:
00000000 004883c7 01650210 c1580a10 00004de0 004a0eda 00487cd1 00000006 c1580a10 004df04a 00000060 00498aa1 00000018 0049acd4 004a959c 00000000

marxveix wrote on Today, 15:20:

I dont have internet connected to that older pc at the moment, actually nfs2se did start and error is at exit, nfs2se 3dfx demo […]
Show full quote

mwdmeyer wrote on Today, 11:21:

When I installed NFS2SE it didn't install the glide exe so needed to copy manually from CD I think. Did you get any specific error message?

My next version will make it much easier to submit issues.

I dont have internet connected to that older pc at the moment, actually nfs2se did start and error is at exit, nfs2se 3dfx demo has error at start.

Velocity9x settings report
Version: 0.15.0
Build: 11d348f
Adapter: ATI 3D Rage XL AGP
PCI ID: 1002:474D
Revision: 65
Video memory: 8128 KB
Mini-VDD build: 11d348f
2D (GDI): CPU (Windows DIB Engine)
Last DirectDraw test: Complete, 3 of 3 pixel checks pass
Active mode: 800 x 600 x 16 bpp
Core / engine clock: Unavailable
Memory clock: Unavailable
Clock detector: ati-mach64-unavailable-v1
Driver stage: enable-ok
Framebuffer: Active - linear aperture mapped
Last GDI test: not run
Mode switching: Live, any depth
Direct3D: Hardware (the chip's own engine) (SYSTEM.INI Direct3D=0)
VSync: Not yet stamped by DirectDraw (SYSTEM.INI VSync=2)
Direct3D DDI: Not yet stamped by DirectDraw (SYSTEM.INI Direct3DDdi=0)
Baseline modes: 640x480, 800x600, 1024x768 at 8/16 bpp and 60 Hz
Runtime modes: 19 published
Mode scan: state=1 listed=40 queried=40 cached=30 flags=0107
Drop reasons: 12,2,0,0,0,9,0,0,0,0,7,0,0
EDID recommendation: 1280x1024 reason=edid-preferred
Inventory generation: 123
Registry sync: ok (generation 109)
Rendering: Windows DIB Engine (software GDI)
DirectDraw: CPU fill and copy, page flip
Direct3D: Hardware (the chip's own engine)
Mini-VDD callbacks: VESA, monitor power
Last report sent: none

NFS2SE 3Dfx Demo error at start

NFS2SEAD caused an invalid page fault in
module <unknown> at 0000:6c095210.
Registers:
EAX=00000000 CS=0187 EIP=6c095210 EFLGS=00010202
EBX=00000001 SS=018f ESP=006ffb84 EBP=00c58bc0
ECX=006ffb88 DS=018f ESI=00000002 FS=0d47
EDX=00000000 ES=018f EDI=00000008 GS=0000
Bytes at CS:EIP:
Stack dump:
0049a804 00562f10 00000000 00000001 00424274 00c40208 00000011 00476141 65465c2e 61746144 5c63705c 5c747241 64696c53 745c7365 656c7469 7366712e

NFS2SE error at game exit (menu not visible)

NFS2SEA caused an invalid page fault in
module KERNEL32.DLL at 0187:bff7b9a6.
Registers:
EAX=00000000 CS=0187 EIP=bff7b9a6 EFLGS=00000246
EBX=00000006 SS=018f ESP=0070fc50 EBP=00000002
ECX=c1580a10 DS=018f ESI=01650210 FS=0e77
EDX=00004de0 ES=018f EDI=00000001 GS=0000
Bytes at CS:EIP:
ff 76 04 e8 13 89 ff ff 5e c2 04 00 56 8b 74 24
Stack dump:
00000000 004883c7 01650210 c1580a10 00004de0 004a0eda 00487cd1 00000006 c1580a10 004df04a 00000060 00498aa1 00000018 0049acd4 004a959c 00000000

If you can send me C:\V9XDIAG\V9XGLIDE.LOG straight after each crash.

It took some time, but i just tested the 0.15 S3 driver on my miro crystal S3 Trio32 VLB card in Win95B OSR 2.1

Desktop works like a charm. I miss frequency change if that will come someday that really would kick ass. Also AoE doesn't start and complains the card does not support DirectDraw.

I switched back to my original driver and AoE works again, and surprisingly i still have the Velocity control panels that seem to work with my stock driver.

I expected less so that is an awesome progress so far, well done

Interesting DirectDraw should work but I haven’t tested with my VLB card recently, I will try and get that fixed up.

mwdmeyer wrote on Today, 16:47:

If you can send me C:\V9XDIAG\V9XGLIDE.LOG straight after each crash.

Already did with some games.