VOGONS


First post, by 360alaska2

User metadata
Rank Newbie
Rank
Newbie

Hello all.

I'm vibe-coding and debugging a vx855 driver for Win98 from scratch. I'm curious if there is anyone with a wyse c10 (or similar) who wants to run win98 and help me debug. The driver is mostly stable, 2d and open gl work pretty good, but d3d is very slow at this point.

Eventually, when I'm satisfied with the 3d engine I will try to port to vx900.

The attachment Screenshot 2026-11-03 134241.png is no longer available

If you're willing I want you to test period correct games/screensavers and report bugs, if you find any please comment with bugs and a link to the game or screensaver on archive.org

You can also you your ai or coding skills to audit the source and reply with bugs.

Reply 1 of 8, by pyrogx

User metadata
Rank Member
Rank
Member

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

Reply 2 of 8, by 360alaska2

User metadata
Rank Newbie
Rank
Newbie

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?

Reply 3 of 8, by pyrogx

User metadata
Rank Member
Rank
Member

a Samsung NC20 netbook

Reply 4 of 8, by 360alaska2

User metadata
Rank Newbie
Rank
Newbie

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.

Reply 5 of 8, by 360alaska2

User metadata
Rank Newbie
Rank
Newbie

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.

Reply 6 of 8, by 360alaska2

User metadata
Rank Newbie
Rank
Newbie

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.

Reply 7 of 8, by 360alaska2

User metadata
Rank Newbie
Rank
Newbie

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

Reply 8 of 8, by 360alaska2

User metadata
Rank Newbie
Rank
Newbie

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.