😀 thanks

No worries.
Just let me know it works 😀

I'm not sure when - but I will test this. Love your work!

I mostly got through everything just fine.

Tested Dos 6.22 + Win3.11 for workgroups

I had a section of the install that unmounted the cd and just booted to dos with only smartdrv installed, remounted in VMware player and rebooted and it continued on its merry way. I think this was in between the dos and win install.

Because I chose to use SVGA and W311FW the login screen would cause the graphics corruption noted in the notes. I did at least figure out if you go change the IRQ for the AMD network card it will allow a graceful boot with SVGA + Network. That helped a lot and the only think that will bug out the screen is dos prompt.

What irq did you use?
It's set to.... 9? Or 11?in the network inf
Might need to test it with your setting

It's supposed to unmount the CD but it's supposed to continue... Hmm

myne wrote on 2024-04-15, 21:38:

What irq did you use? It's set to.... 9? Or 11?in the network inf Might need to test it with your setting […]
Show full quote

What irq did you use?
It's set to.... 9? Or 11?in the network inf
Might need to test it with your setting

It's supposed to unmount the CD but it's supposed to continue... Hmm

This is what I ended up on and everything seems to be stable, dns etc works and no weirdness with login prompt. Everything seems pretty good if you stay away from the dos prompt.

If you're comfortable editing infs, I'd be curious if it works better at to that to start with.

Just search for vmware in the network.inf

I won't be able to access a real computer for at least a few days

myne wrote on 2024-04-15, 21:56:

If you're comfortable editing infs, I'd be curious if it works better at to that to start with.

Just search for vmware in the network.inf

I won't be able to access a real computer for at least a few days

Yeah sure, I'll give it a try later.

Cheers. I know I said no support, but I do want it to work.
I'm kinda hoping people will see the inf changes and add more hardware/patches etc. Or maybe even fix some of the gaps in the bats. I don't really like the invalid media type error, but it's all I could do that worked.
I left notes in the tricky parts of the infs.
The basic "slipstreamed" template with TCP, is, I think, a good foundation.

Got linked here from that other thread. Haven't actually tested this template yet, but I noticed that it attempts to integrate the TCP/IP-32 stack (for "Windows for Workgroups 3.11") with what keeps being called just plain "Windows 3.11" (no "for Workgroups"). Both of those exist, but are different things - yet people keep confusing them, and I suspect this may have happened here, too. flynnsbit [technically deviated from the instructions and] had success using it with WfW; no surprise there since that's the intended platform. Can anyone confirm whether or not this also works with the non-Workgroups version?

It only takes a few minutes to build a iso and test in vmware.
The install is literally under 5 mins.

I don't think there were substantial differences so I expect it would work.

myne wrote on 2024-12-10, 12:36:

It only takes a few minutes to build a iso and test in vmware.

I don't think there were substantial differences so I expect it would work.

I read that as "I dunno lol go figure shit out for yourself", which coming from the code's author isn't a good sign, then wasted a good 40 minutes doing just that. My findings:

The modified infs replacing the stock ones are clearly based on Windows for Workgroups 3.11, not Windows 3.11. Let's try it anyways.

The whole process indeed relies heavily on VMware's behavioral quirks. VMware doesn't work on my system, so I used QEMU instead and had to fiddle some things (manually change boot order at some points, sometimes manually reboot, stuff like that). That's out of scope for the template though, so - fair enough. I eventually worked my way past all of that.

A disc made from WfW floppies worked, but Windows 3.11 refused to install at all. "The version of setup.inf is not valid for this, yada yada...", soon followed by "The file setup.inf is damaged." Obviously this also means no TCP/IP-32, which, well, at least answers my initial question. Still unsure whether the TCP stack would install when doing it manually, but that's for another day (and thread). Doubt it though.

TL;DR: 100% gotta use Windows for Workgroups for this, not "vanilla" Windows, despite of what the instructions say.

Oh snarky. See title and point 8 and 9.

The 3.1 infs can probably be modified with the additions I made. It's commented.
But it's not something I'm interested in pursuing.