mwdmeyer wrote on 2026-11-04, 09:52:

... 0.35 is out https://github.com/michaeldale/velocity9x/rel … ses/tag/v0.35.0 […]
Show full quote

...
0.35 is out https://github.com/michaeldale/velocity9x/rel … ses/tag/v0.35.0

AMD Radeon HD 7660D + NVIDIA RIVA 128ZX (not finished) + Intel GMA
...

Thanks, nice to see support for a TeraScale 3 GPU/APU!

Duffman wrote on 2026-11-04, 13:05:

It's definitely something windows related as DOS is fine.

I started going through every device in device manager and I did find the culprit, but it's bad news for debugging/testing though.

It's the 3Com NIC built in to the laptop, disabling the NIC in device manager stops the freezing, but that also means that we won't be able to run debugging on it with it disabled.

I suspect that the 3Com NIC share some resources with other devices that might cause a problem. Open "Device Manager", select "Computer" and click on "Properties" and have a look at the resources, especially the IRQs.

Otr try another NIC in another PCI slot with onboard disabled.

It's a laptop.
I'll need a 98SE compatible Ethernet dongle or wifi dongle.

10baset might help

Hi All,

I'm looking for someone with an Intel HD3000 GPU I can use to help add support for that card. PM me.

Unfortuntelly my Sandy and Ivy machines has P67 chipset that don't support iGPU output, I'll have a look if I could find some H6x MB...

EDIT: sorry I don't have any SB/Ivy MB with VGA out.

https://www.techpowerup.com/gpu-specs/?archit … eneration%206.0

Wouldn't hd2000 be basically the same?

Also, I noted in the chat to dev window, the chats aren't persistent. I rebooted, and if you replied, I cant tell.
There's also seemingly no status/log. I see that you/agent changed the driver to the VBE, but it'd be nice for testers to have some kind event log clientside or somewhere.
I see the decisions record in github, but that's recorded after the fact.

I realise they're not priorities.

eg:
DATETIME agent connected
DATETIME agent idle (reboot/shutdown ok)
DATETIME agent connected, probing.
DATETIME probing complete
DATETIME agent idle (reboot/shutdown ok)
DATETIME agent attempting driver test ##
DATETIME agent reboot requested
DATETIME agent connected

etc

myne wrote on 2026-11-06, 02:10:

https://www.techpowerup.com/gpu-specs/?archit … eneration%206.0 […]
Show full quote

https://www.techpowerup.com/gpu-specs/?archit … eneration%206.0

Wouldn't hd2000 be basically the same?

Also, I noted in the chat to dev window, the chats aren't persistent. I rebooted, and if you replied, I cant tell.
There's also seemingly no status/log. I see that you/agent changed the driver to the VBE, but it'd be nice for testers to have some kind event log clientside or somewhere.
I see the decisions record in github, but that's recorded after the fact.

I realise they're not priorities.

eg:
DATETIME agent connected
DATETIME agent idle (reboot/shutdown ok)
DATETIME agent connected, probing.
DATETIME probing complete
DATETIME agent idle (reboot/shutdown ok)
DATETIME agent attempting driver test ##
DATETIME agent reboot requested
DATETIME agent connected

etc

Good ideas! I will get them added.

mwdmeyer wrote on 2026-11-06, 02:27:

myne wrote on 2026-11-06, 02:10:

https://www.techpowerup.com/gpu-specs/?archit … eneration%206.0 […]
Show full quote

https://www.techpowerup.com/gpu-specs/?archit … eneration%206.0

Wouldn't hd2000 be basically the same?

Also, I noted in the chat to dev window, the chats aren't persistent. I rebooted, and if you replied, I cant tell.
There's also seemingly no status/log. I see that you/agent changed the driver to the VBE, but it'd be nice for testers to have some kind event log clientside or somewhere.
I see the decisions record in github, but that's recorded after the fact.

I realise they're not priorities.

eg:
DATETIME agent connected
DATETIME agent idle (reboot/shutdown ok)
DATETIME agent connected, probing.
DATETIME probing complete
DATETIME agent idle (reboot/shutdown ok)
DATETIME agent attempting driver test ##
DATETIME agent reboot requested
DATETIME agent connected

etc

Good ideas! I will get them added.

Remote Agent 0.15 adds these and I will update remote machines once they are free.

So fast. Are you bored at work with unlimited tokens btw?
I notice your decisions file just went up for HD4000 and it looks decently fast!
Any overall intel improvements or is it just pure hardware grunt?

myne wrote on 2026-11-06, 05:14:

So fast. Are you bored at work with unlimited tokens btw?
I notice your decisions file just went up for HD4000 and it looks decently fast!
Any overall intel improvements or is it just pure hardware grunt?

Yeah lots of improvements in core for Gen7/7.5, also it is a lot faster.

I have a branch for fixes on GMA 950 but it is more complex.

Yeah I own IT/software company and often work odd hours haha. Clade on Opus 5.5 medium doesn't use many tokens. I'm patching my Dual Radeon AI R9700s boxes at the moment with latest vLLM and fixes!

Great project. Finally gives me something to do with my old netbooks.

Everything seems to be working fine with preliminary testing on the Eee PC 901. However, the Eee PC 701 with the GMA 900 has some significant geometry garbling when I tested 3DMark99. Starcraft runs perfectly so far, so 2D isn't a problem.

Installation gets a bit iffy though. Didn't install correctly on either machine the first time. Would remain stuck at 16 colors. But if I install the universal VBE driver first, and then switch over to yours, it all then works fine. No idea why.

Looking forward to the GMA 950 improvements. Thanks for working on it.

Mylegbig wrote on 2026-11-07, 06:01:

Great project. Finally gives me something to do with my old netbooks. […]
Show full quote

Great project. Finally gives me something to do with my old netbooks.

Everything seems to be working fine with preliminary testing on the Eee PC 901. However, the Eee PC 701 with the GMA 900 has some significant geometry garbling when I tested 3DMark99. Starcraft runs perfectly so far, so 2D isn't a problem.

Installation gets a bit iffy though. Didn't install correctly on either machine the first time. Would remain stuck at 16 colors. But if I install the universal VBE driver first, and then switch over to yours, it all then works fine. No idea why.

Looking forward to the GMA 950 improvements. Thanks for working on it.

Thanks for testing! The 16-colour first install is a known problem: Windows keeps the standard VGA driver’s 16-colour setting, which Velocity9x doesn’t offer, so it falls back to VGA. Installing the VBE package first works around it because that changes the setting. I’ll fix it so a direct install works in a future version.

The 3DMark 99 garbling on the 701’s GMA 900 is new. 3DMark 99 hasn’t been run on a GMA 900 myself yet. Could you send, from the 701 right after a garbled run: the Velocity9x version, the resolution and colour depth, which 3DMark 99 test it happens in, a photo or screenshot, and the files in C:\V9XDIAG (V9XHW.INI, V9XBOOT.INI and the newest V9XSNA*.INI)? A GitHub issue is the easiest place to attach them, otherwise if you have internet on it you can go into the Display Settings -> Velocity9x Advanced -> Send Report and it will give you a code to give to me to reivew.

I have a cheap USB VGA capture device that operates basically like a webcam. Would it be helpful for development to have that hooked up to the Riva 128 machine and transmitting a live video feed using another computer?
And if so, what software would you want me to use to transmit it? Seems like it'd be simple to join something like a discord video channel and just leave it running.

I'm 99% sure it captures raw frames from the frame buffer.
It's unlikely to be corrupted after that point, but I suppose it's possible.

IIRC the 701 had some odd screen size like 900x600 so it could theoretically be a scaling issue in the hardware past the gpu, but I can't imagine the driver hasn't compensated for it.

MWD, maybe add a diagnostic mode to capture say 2 minutes of raw... Every 10th frame?
I did the math on every frame and at 60fps it would probably fill the hdd in 30 seconds 🤣

Setup a website https://velocitydrivers.org

These two cards cannot be installed on Windows 95 because their proprietary drivers are only compatible with Windows 98 or later.

I hope they can be part of the project.

BTW, the Velocity VBE driver doesn't work very well with these cards.

vico wrote on Yesterday, 06:27:

These two cards cannot be installed on Windows 95 because their proprietary drivers are only compatible with Windows 98 or later.

I hope they can be part of the project.

BTW, the Velocity VBE driver doesn't work very well with these cards.

Yeah had a few requests for the 9200 so I will add. Which version of the VBE driver did you test with? The latest version has lots of improvements.

mwdmeyer wrote on Yesterday, 06:55:

[Yeah had a few requests for the 9200 so I will add. Which version of the VBE driver did you test with? The latest version has lots of improvements.

I tried version 0.48, but it displayed 16 illegible thumbnails of the screen simultaneously; I’m going to try version 0.49 instead.

vico wrote on Yesterday, 12:20:

mwdmeyer wrote on Yesterday, 06:55:

[Yeah had a few requests for the 9200 so I will add. Which version of the VBE driver did you test with? The latest version has lots of improvements.

I tried version 0.48, but it displayed 16 illegible thumbnails of the screen simultaneously; I’m going to try version 0.49 instead.

Wow really odd, is this on Windows 95? Can you take a photo? I have seen this once before with the S3 Trio, but that was fixed, Win 95 might be different though.

I've found a Radeon 9000 RV250 card I own, so will do testing in future.

EDIT:

Can you tell me:

Which Windows it is (95 retail, 95 OSR2 or 98).
The desktop resolution and colour depth at the time, and whether this was the first boot after installing the driver.
Whether 640x480 at 256 colours shows it too, and whether any colour depth draws correctly.
A photo of the screen.
The files V9XBOOT.INI, V9XHW.INI and V9XDD.INI from C:\V9XDIAG, copied after the bad boot (Safe Mode is fine for copying them).

In Device Manager, please also check that the driver is on the first Radeon entry and not on the card’s secondary device.