I think I have an old laptop with a VX800 chipset. Would this also work?

Maybe, but more likely not, I might try to port it over if I have a device, what device do you have that has vx800?

a Samsung NC20 netbook

I ordered 2x hp 5545, so I'll try at some point, we're still hammering out the 3d engine. After that, more game tests, then possible family ports.

Nobody else brave enough to make a comment?

Right now I'm target Quake2, the lattice screensaver, and GTA3 as performance targets. Right now Quake2 at 800x600 is about 32.4 fps with texture quality slider at the default 90%.

The source now to big to post here, I will upload to github at some point.

**What changed since v10.449.** From v10.450 to v10.479 the work was Direct3D for GTA3 and 3DMark2001. The vertex path got faster (TEXONLY, FASTVV, PFVV2, TEXHINT), and indexed triangle lists go to the engine as indexed packets (`ACCEL_D3D_INDEXED`, with a vertex area in video memory). The command ring got more robust (`RINGPROG`, `RINGCAP`, ring waits counted by length). Textures can now be render targets (`RTTEX`, ARGB8888 targets), and a copy into or out of one no longer waits for the engine first (`RTNOWAIT`; GTA3's per-frame copy went from 2.94 to 0.43 ms). A stale `VXGL.DLL` was found to be behind the screen saver lockup. VXFETCH, VXFORMAT and VXRTT were added as test tools, and a review round in v10.479 fixed the render-target and flip error paths.

From v10.480 to v10.493 the work moved to OpenGL's CPU-side vertex work, with Lattice as the target:
- **Flat shading on the engine:** flat strips go to the engine as strips, with the engine's first-vertex colouring, and from v10.492 without copying the vertices.
- **Mesa's own stages:** faster float-to-integer conversion, square roots by SSE, a single lighting loop, and strips split at the window's edge.
- **The SSE pass:** one pass per vertex that does transform, clipping, lighting, fog and output four vertices at a time. It now skips draws wholly outside the view (also from a bounding box), does the specular lookup and byte packing in SSE, and keeps its setup between draws.
- **Strip output:** a culling run that appends one vertex per triangle.
- **Two real Mesa 7.0.3 bugs fixed:** a read of a freed buffer after a display list is deleted, and per-vertex materials read from the wrong place.
- **VXFLAT:** checks every switch against the template pixel for pixel.

I implemented as many features as possible before handing the driver over to Fable 5.2 and GPT-6.1 Sol for independent, ground-up rebuilds. I then fed both implementations back into Fable and Sol for further analysis, refinement, and integration. The result is a hybrid driver that combines the best of both approaches.

At this point, I consider the VX855 driver feature-complete. The next phase is to expand hardware compatibility by porting it to the VX800 and VX900, with potential support for the CN896 as well.

I want to also point out that you must have at least dx7 installed for d3d to work.

I can't seem to get Win98 booting on Vx900, I have 2 separate boards. So I guess this may end up being VX800/Vx855 which are functionally almost the same. In my testing the VX855 is about 10%-15% faster.

okay, here it is on GITHUB:

https://github.com/360alaska/via-chrome9-win9/

thanks to @pyrogx for pushing me work on VX800, it was very easy once vx855 was built out.

I tried to use Win98 with a HP T5565 thin client in the past and got nothing but Windows Protection Errors. Since it has a hardware serial port, maybe you could hook Claude up to the kernel debugger and figure out what's going wrong?

If you get vx900 to boot I will work on a win98 driver, but realistically, it may never be supported.

Here is the really cool part, Since I documented my work someone could put the code into another AI and perhaps make it better or even backport back to Linux

I've worked with GPT to get Vx900 Booting to W98, I will have to release a patcher at some point:

GPT (asked for a summary):
We got Windows 98 SE to boot on the VIA VX900 by patching two drivers and starting Windows from the DOS prompt.

- The VDD patch skips VGA BIOS mode changes 10h and 03h, where Windows hung during startup.
- Temporarily renaming HSFLOP.PDR helped get past floppy initialization.
- The VMPOLL patch uses the driver’s built-in fallback to skip startup calibration.
- The startup Logo itself must be bypassed or windows will not boot.

The startup logo looked normal at first, then distorted and the machine hung.

It took me the better part of a day to work with Claude and ChatGPT to determine why the VX900 would not boot Windows 98, but I have found the issues and we have vibe coded a patch.

https://github.com/360alaska/vx900-win9x-bootfix

The issue I was having on the T5565 was a Windows Protection Error upon loading CONFIGMG if I remember correctly (both when using Win98 QuickInstall and when swapping the storage from another thin client since Setup wouldn't work). Though I did also see the problem with hanging at the startup screen at some point.

Also, do you have any way of fixing the ugly nearest-neighbor display scaling for DOS video modes on the Wyse Cx0? This might require a BIOS patch.

"Also, do you have any way of fixing the ugly nearest-neighbor display scaling for DOS video modes on the Wyse Cx0? This might require a BIOS patch."

send pictures!