Hi,
I'm trying to install Windows 3.11 for Workgroup on Virtual PC 2004 Trial but it refused to install. The setup program froze when it tried to detect the network card, I've tried setup/f to bypass hardware detection but got stuck at the question asking the name (keyboard & mouse not responding).
DOS 6.22 has no problem and able to detect my PS/2 mouse. Any help will be much appreciated. Thanks Daniel.

Try to skip the network setup when you install by by pressing cancel when it asks you if you want set it up now. I had a similar problem it didn't freeze but it didn't detect any network card, I had to install it later in Windows Setup. If you don't have the driver for the network card i can send it to your E-Mail.

Thanks for your reply, Robin. However there seems no option to cancel the network setup. After Windows Setup asked for disk#2, it loaded the GUI then went straight to the network card detection process, then stopped responding. I've disabled the network card from Virtual PC setting but still no luck. Is there any coommand line parameter to bypass the network card? Regards, Daniel.

Entering

setup /?

will give you a list of command line switches:

/I - Ignores hardware detection. During Setup, the user will need to check accuracy of settings on the System Information screen

setup /f actually forces network detection

I'm just looking for clues at the scene of the crime

Report Offensive Follow Up For Removal

I've tried to use setup/i (in the first message actually I meant "setup/i") but then it froze when asking the name and company name, I presumed it was caused by Setup did not detect any keyboard or mouse. Is there any way for ignoring network detection only?

I think that the only options are those given by the help ( /?) switch.

Can't say what the issue might be - lot of factors involved when installing an 11 year old graphical application on a machine that the original programmers could not even envision.

I'm just looking for clues at the scene of the crime

Report Offensive Follow Up For Removal

remove EMM386.EXE from the config.sys line.

That worked for me.

--rob