I understand. 😀 Thanks for the emulator links. And yeah, I know better than to ask where to pirate an OS on a public forum. 😜 (Even if such WEREN'T against the rules, the PTB would doubtless turn up the post, given that they read everything we USians put on the Internet.)

bregolin wrote: Check this out: http://www.toptensoftware.com/win3mu/ - I've read it on another thread here, and this may solve your problem. Except it doesn't seem to exist, currently. 😒 If there's a Win 3.1 emulator or suchlike that IS available now, though, that'd be awesome.

Good job!....until the boot setup.exe To run programs in DOSBox just type in the name of the program, so "hello.exe" or "hello.com" or "hello.bat". Usually setup.exe files are Windows installation programs so likely if you run that program in DOSBox then it will complain because the executable …

Ah. Part of the problem is I'm not finding the command to just...run the EXE file. Again, if this is about needing that "frontend" thing, that may be the problem. I've basically been the Underpants Gnomes of installing this thing. Step 1: Tell it where to install to. Step 2: Tell it where to install …

So I told it to boot setup.exe and got THIS: Opening image file: setup.exe Image file is read-only! Might create problems. Booting from drive A... How do I stop it looking for drive A? I told it D was the CD-ROM like the 60-second guide says. There should be no "drive A" business going on. (Yeah, …

Thank you SO MUCH. I wasn't sure where the beginners' stuff was, and wasn't sure where to search. And of course, "install windows 3.1" doesn't call up any search results, because of the common words, lol. (Also, hello to a fellow Sierra fan! My first DOSBox install was for the Kings Quest series re- …

I'm having the darnedest time here, and the fact that I'm completely unfamiliar with DOS isn't helping one bit. All previous applications I've used DOSBox with, were re-releases of old games specifically coded so that when you opened them, DOSBox just automatically opened up and then automatically …

I think wine breaking programs (ie: regressions) are unusual Not really related, but years ago the Linux kernal ( v.3.14 ) had broken 16-bit PM support (got fixed by Linus ?), As far as WINE compatibility is concerened.. well.. Windows 1.x and 2.x NE executables are nolonger recognized properly …