3 ms·
The BearWindows VESA driver (for 9x[1] and NT[2]) works well on QEMU. The last version of VBEMP that won’t nag you on each boot is G. Of course, that does nothi
by mananaysiempre 4y ago
The BearWindows VESA driver (for 9x[1] and NT[2]) works well on QEMU. The last version of VBEMP that won’t nag you on each boot is G. Of course, that does nothing about the rather poor support for resolution independence on historical Windows, so 1280x1024 is about the largest practical resolution.
(Unfortunately, Sound Blaster 16 emulation is known to be broken in combination with the Gtk UI[3], so no / choppy sound for you, but things should work over SPICE. I’ve yet to find a SPICE client that will maintain a fixed 2:1 display scale with no interpolation.
A helpful HN user described[4] how to enable SMB1 on recent versions of Samba and so share files over something other than floppy images, TFTP, or active FTP. I haven’t found a better way to do this with QEMU’s native Samba integration than launching it, then finding the generated smb.conf somewhere in /tmp and patching it.)
[1] https://bearwindows.zcm.com.au/vbe9x.htm https://bearwindows.zcm.com.au/vbe9x.htm
[2] https://bearwindows.zcm.com.au/vbemp.htm https://bearwindows.zcm.com.au/vbemp.htm
[3] https://gitlab.com/qemu-project/qemu/-/issues/469 https://gitlab.com/qemu-project/qemu/-/issues/469
[4] https://news.ycombinator.com/item?id=29260861 https://news.ycombinator.com/item?id=29260861
- jeroenhd 4y agoI've been real spoiled with the auto-resolution switching support with the QEMU guest agent and libvirt drivers and that becomes painfully obvious when I resize a Win2k/Win98 VM and scroll bars appear... I haven't had much trouble with the virt-manager GUI in terms of sound. For Win2K I could install the server edition and remote into it over RDP if it ever becomes an issue.