ScreenLock V3.07 interoperability notes — 2026-11-04

Independent C# implementation, GPL-3.0-or-later.
The original ScreenLock executable is not embedded, invoked or redistributed.
This is an offline integration awaiting validation against the actual device.

Evidence
User-supplied ScreenLock_V307.exe, PE32 native MFC.
SHA256 c03fc1053d22961f4234967e458465ed5b09d64758e2c50537cc009228281353
Supplied HDMI-HDMI manual V306: connect, import or study, preview, then Write.
Learning stages EDID; writing is a separate action.
Original code addresses: connect 0x411ba0; export 0x40dbc0;
study 0x40e750; preview write 0x410e70; frame exchange 0x4132a0;
additive checksum 0x413090; response receive 0x4139c0.

Transport
USB virtual serial port; 115200 baud, 8 data bits, no parity, one stop bit.
No handshake, DTR/RTS disabled. Candidate WCH serial bridges are not proof of
device type: identify response and explicit physical wiring confirmation required.
Native CH341 parallel/I2C firmware flashing is deliberately not implemented.
The original separate CH341A EEPROM page remains unchanged.

Request frame
FA 00 payloadLengthLo payloadLengthHi command payload checksum
Checksum is the sum of every preceding frame byte, modulo 256.
0x02 identify, zero payload: FA 00 00 00 02 FC
0x16 read saved EDID, zero payload: FA 00 00 00 16 10
0x17 write saved EDID, payload is full declared EDID (128/256/384/512 bytes).
0x18 study downstream Display, payload 0x80 | zero-based port (0..3).
Port 1 request: FA 00 01 00 18 80 93

Response
Header FA, length at 2..3, command at 4, payload at 5.
Original receiver accepts header + declared payload without requiring a trailer.
This implementation accepts an optional additive checksum, validates it if present,
and waits up to 40 ms for it. Header byte 1 is required to be zero.
Actual hardware timing and response header/trailer behavior are still unverified.
Identify payload: at least seven bytes; [0..1] hardware, [2..3] firmware,
[4] == 0x10 for HDMI ScreenLock. The DP model 0x11 is not enabled.
Read and study responses are limited to 512 bytes. Declared blocks, structure and
each 128-byte checksum are validated; missing blocks are never invented.
Read payload padding is normalized to declared EDID length; writes must match
that declared length exactly and cannot carry undeclared trailing bytes.

Transaction rules
No protocol probes are sent merely to scan COM ports or change connection mode.
Binding requires selected HDMI, one-use read token, user wiring confirmation,
correct serial instance, supported model and stored EDID matching HDMI prefix.
Binding and study do not issue 0x17. Study must leave saved EDID unchanged.
Write is explicit, backed up, checked against a fresh stable saved value, sent
once and verified by two saved-value reads. Failed writes only restore when
current contents equal the original or requested value; unknown states stop.
Read/learn/write use one hardware lock shared with other device operations.
Replug HDMI after writing and check system enumeration separately. A matching
prefix is not proof that two otherwise identical devices are the same hardware.

Driver packages supplied by user
CH341PAR.EXE SHA256
7f8d4c822b4a5f1bd146e90df17666f0c435878f488c5d0828a00254b65ccf77
CH341SER-RS232.EXE SHA256
391a615225980f5e93bb9a6196f82a6b03b67a001b9dd3a64353f4b0ba2884b8
Vendor signature and extracted catalogs verified valid locally.
Unmodified Windows packages: parallel 2.4.2023.10 then serial 3.7.2022.01.
All 20 embedded package files are pinned by SHA256 in ScreenLockDrivers.cs.
Existing fusion serial 4.0 and CH341A programmer package are separate resources.
Installation uses pnputil with admin approval, no forced downgrade/reboot.
Removal matches exact package INF hashes, not generic WCH vendor names.
No actual installation/uninstallation or physical device write performed in QA.
