Again, because I can’t get the NT 4 guest (or the NT 3.51 guest, or the 98 guest) to connect to the QEMU-launched smbd and I can’t be arsed to configure Samba and the relevant NAT and/or bridging myself, whereas the builtin FTP client mostly works out of the box except that I need to set up some network interface stuff on the host. (The last memory I have of seriously investigating Samba is when I read the entirety of the Samba HOWTO with a view of assisting the school network admins back when I was around 15 years old and—as I now recognize—knew next to nothing about networking. I probably still have something of an
ugh zone around it.) I expect it’s because NT 4 only talks some sort of obsolete version of SMB or its underlying stack that modern Samba doesn’t enable by default, but again I just can’t bring myself to care when it’s a 30-minute hack whose only purpose is to get IE onto the VM and then I can bootstrap my way to saner things.
If you just happen to know the solution off the top of your head, please share it, by all means, that’s half the reason I posted that in the first place. But today is not the day I delve into the guts of old-style Microsoft/IBM networks.
The thing with mouse desync is similarly weird, because for me the mouse doesn’t desync when connecting to the VM over VNC using MultiVNC on Android, on a frickin’ touchscreen, but always desyncs when using either builtin Gtk, builtin SDL, or SPICE on Vinagre (which uses VNC under the hood supposedly?..) locally on Gnome Wayland, except the HiDPI-host bugs are different for each of those. In all cases QEMU is emulating a normal PS/2 mouse that shouldn’t have any support for absolute positioning. I mean, what? How does that even work? It’s not even the fun kind of “how does that even work”, just a lot of imperfect, subtly mismatched emulations stacked on top of one another. Monkey sad.