Claude:
His log confirms .598 fixed the cursor and the flicker, and it also exposed one mistake of mine and the cause of the missing 1024x768. Both are corrected in `VIA_Chrome9_599.zip`.
## What his log confirms
- **Routing:** the driver saw the panel on the second pipeline and wrote all 254 flip addresses to it.
- **Pointer:** visible, with its tip in the right place, at 1280x800 and at 640x480 stretched to the panel.
- **Flips:** red, green and blue screens were steady, and the moving bar ran clean at 60.0 flips a second.
## What .599 fixes
**1. I read the panel's vsync signal the wrong way round.**
The status bit turned out to be 1 while the picture is drawn and 0 during the blank; .598 assumed the opposite. His log shows it set in 98.06% of samples, and his panel draws 800 of 816 lines, which is 98.04%. The effect in .598: a flip counted as "shown" almost immediately, so a game with a single back buffer could draw into the buffer still on screen. His tests didn't hit that (3DMark and my bar test weren't affected), but some games would have flickered. .599 reads it correctly.
**2. 1024x768 was missing because of the panel's EDID.**
His panel's EDID lists only its native 1280x800 and nothing else. The driver's "does the monitor list this size" rule therefore refused 1024x768 at 16 and 32 bits and 800x600 at 32 bits. Windows wasn't offering them either; his log shows 1024x768 only at 8 bits, so the desktop mode he remembered working was probably 256 colours. .599 accepts 640x480, 800x600 and 1024x768 whenever they fit inside the monitor's native size. This applies to any monitor with an EDID that sparse, not only laptops.
Checks: 2244 verification checks pass, and the full test suite has 0 failures with the three reference hashes unchanged.
## For him
VXPANEL is now v1.1. It adds a moving-bar test with one back buffer (the case .598 would have got wrong), tries 800x600 and 1024x768 on the panel, and logs how often the driver sees the blank, which should be about 2%.
```
Great news, thanks for testing. Your log showed two more things, both fixed
in build .599 (attached):
- I was reading the panel's vsync signal inverted. Your tests didn't show it,
but games with a single back buffer could have flickered.
- 1024x768 (and 800x600 in 32 bit) were missing because your panel's EDID
only lists 1280x800 and my driver was too strict about that. They should
now appear on the desktop and in Direct3D.
Same procedure: replace the five driver files, restart, run
tools\VXPANEL.EXE and send VXPANEL.TXT. It asks one more question than before
and tries 800x600 and 1024x768 as well.
When you test further, I'm especially interested in the full-screen DOS box
and in PCPlayer's missing fog and transparent textures. Those are still on
my list.
```
## Still open
- **Full-screen DOS box:** not looked at yet.
- **PCPlayer (no fog, no transparent textures, no 1280x800):** not looked at yet.
- **Code 12 at install:** cause unknown; his manual fix stands.
- **Your boards:** neither .598 nor .599 has run on a VX855 or VX800 of yours. The EDID change affects every monitor, so I'd run RUNALL on one before this goes on GitHub.
The cookbook's section 37 has the corrected blank sense, the EDID rule, and a new rule from this: sample a status bit and compare its duty cycle with the timing before trusting which way round it reads.
Please test this driver further, then I can test it on my other systems, I suspect an edid bypass registry key might be the fix for your panel issues... But please keep test, if you perfer you can emial me directly 360alaska(@)gamil.com