Configuring Virtual PC 2007 to run Windows 3.11

1 of 100
  • 213295.png

    Virtual PC 2007 is a handy tool for running multiple operating systems. However, it's not without its limitations when running an older OS like Windows 3.1. Here's what it takes to get everything working.

    This screen shows a basic Windows 3.11 installation under Virtual PC. The emulated hardware under VPC isn't supported by Windows 3.x and you have to hunt around to get all of the drivers and stuff that you need.

    The Classics Rock blog on TechRepublic lists the file locations. You'll need.

    Caption by: John Sheesley

  • 213296.png

    Begin by putting together a CD-ROM with the files you needs. VPC under DOS can't access the host machine's hard drive, so this is the only way you can load the drivers you need.

    Caption by: John Sheesley

  • 213297.png

    PKUnzip is always a handy utility to have in DOS. Extract the files to your C:\DOS directory.

    Caption by: John Sheesley

  • 213298.png

    You'll need the S3 Trio64 drivers for Windows 3.1 to get better than basic VGA resolution and colors out of VPC.

    You get to this screen from the Windows Setup icon in the Main Group.

    Caption by: John Sheesley

  • 213299.png

    Select Other from the Display drop down box, and Windows 3.x prompts you for the location of your drivers.

    Caption by: John Sheesley

  • 213300.png

    Select the screen size and color depth you want. Unlike Windows 9x and better, you can't change this resolution on the fly and always have to go through Setup.

    Caption by: John Sheesley

  • 213301.png

    Caption by: John Sheesley

  • 213302.png

    Click OK after you make your selection.

    Caption by: John Sheesley

  • 213303.png

    Setup installs the fonts and video drivers after you click OK.

    Caption by: John Sheesley

  • 213304.png

    You must then restart Windows to make the new video driver take effect.

    Caption by: John Sheesley

  • 213305.png

    When Windows comes up, you should notice a color and resolution change.

    Caption by: John Sheesley

  • 213306.png

    The emulated sound card for VPC is a SoundBlaster 16. The following screens show the installation program for the card.

    Caption by: John Sheesley

  • 213307.png

    Caption by: John Sheesley

  • 213308.png

    Caption by: John Sheesley

  • 213309.png

    Caption by: John Sheesley

  • 213310.png

    Caption by: John Sheesley

  • 213311.png

    Caption by: John Sheesley

  • 213312.png

    Caption by: John Sheesley

  • 213313.png

    Caption by: John Sheesley

  • 213314.png

    Caption by: John Sheesley

  • 213315.png

    Caption by: John Sheesley

  • 213316.png

    Caption by: John Sheesley

  • 213317.png

    Caption by: John Sheesley

  • 213318.png

    After the DOS installation program finishes, the SoundBlasters Windows Setup program runs. It installs the Windows programs and configures the Windows drivers.

    Caption by: John Sheesley

  • 213319.png

    Caption by: John Sheesley

  • 213320.png

    Restart Windows again!

    Caption by: John Sheesley

  • 213321.png

    Caption by: John Sheesley

  • 213322.png

    Caption by: John Sheesley

  • 213323.png

    You can now begin configuring the Network Settings. In Windows For Workgroups 3.11, this screen is found by clicking Network Setup in the Network Group.

    Caption by: John Sheesley

  • 213324.png

    VPC emulates the Intel 21140 network card. Windows doesn't include a driver for this card, so you must download it. Select Unlisted to find it.

    Caption by: John Sheesley

  • 213325.png

    Give the location of the drivers

    Caption by: John Sheesley

  • 213326.png

    You only have one card to choose from.

    Caption by: John Sheesley

  • 213327.png

    Windows For Workgroups installs NetBEUI and IPX as the default protocols. TCP/IP is *not* a choice.

    I've removed IPX for now because you must have at least one protocol installed and I haven't installed TCP/IP yet.

    Caption by: John Sheesley

  • 213328.png

    Restart Windows yet again.

    Caption by: John Sheesley

  • 213329.png

    When the computer restarts, you can see the drivers for the card load.

    Caption by: John Sheesley

  • 213330.png

    When Windows starts this time, you'll see a login screen. The default password is blank.

    Caption by: John Sheesley

  • 213333.png

    Caption by: John Sheesley

  • 213331.png

    When you enter a password, it's added to Windows' password list.

    Caption by: John Sheesley

  • 213332.png

    Now you must download and extract the TCP/IP files for Windows 3.1.

    Caption by: John Sheesley

  • 213334.png

    Go back into Network Setup when Windows starts back up. This time click Add Protocol. Click Unlisted to load your TCP/IP drivers.

    Caption by: John Sheesley

  • 213335.png

    After giving the location of the drivers, you only have one choice.

    Caption by: John Sheesley

  • 213336.png

    NetBEUI and TCP/IP are both listed now. Remove NetBEUI.

    Caption by: John Sheesley

  • 213337.png

    Caption by: John Sheesley

  • 213338.png

    TCP/IP is all by itself. Now you must configure it.

    Caption by: John Sheesley

  • 213339.png

    You can statically assign IP Addresses by filling out the information on this screen. You can also use DHCP by clicking Enable Automatic DHCP Configuration.

    Caption by: John Sheesley

  • 213340.png

    I've chosen DHCP.

    Caption by: John Sheesley

  • 213341.png

    Unlike later versions of Windows, DHCP in Windows 3.x only sets the IP address and NetMask of the workstation. You must statically enter the address for the Default Gateway, WINS, and DNS servers.

    This defeats a lot of the purpose of DHCP unfortunately.

    Caption by: John Sheesley

  • 213342.png

    Click the DNS button to get here. Here you enter DNS information.

    Caption by: John Sheesley

  • 213343.png

    Caption by: John Sheesley

  • 213344.png

    TCP/IP is configured and ready to go.

    Caption by: John Sheesley

  • 213345.png

    Setup modifies necessary system files and tells you about it.

    Caption by: John Sheesley

  • 213346.png

    Basic Windows versions of some TCP/IP utilities appear.

    Caption by: John Sheesley

  • 213347.png

    Again you must restart Windows.

    Caption by: John Sheesley

  • 213348.png

    You should check the Network Settings for Virtual PC to make sure that the proper network card is enabled and chosen for your session. In machines with multiple network cards, the default session may not choose the proper card. Select it from the drop down box.

    Networking in the Windows 3.x session may not work if you don't check this.

    Caption by: John Sheesley

  • 213349.png

    Caption by: John Sheesley

  • 213350.png

    There's DOS based PING utility you can use to check connectivity when Windows restarts.

    Caption by: John Sheesley

  • 213351.png

    TCP/IP is working and we're connected to the Internet!

    Caption by: John Sheesley

  • 213352.png

    Now it's time to get a Web browser. The newest browser supported by Windows 3.1 is Internet Explorer 5.01.

    Start the Setup program from the Run dialog box.

    Caption by: John Sheesley

  • 213353.png

    Caption by: John Sheesley

  • 213354.png

    Caption by: John Sheesley

  • 213355.png

    Caption by: John Sheesley

  • 213356.png

    IE 5.01's setup program is similar to the old one for IE 6.0.

    Caption by: John Sheesley

  • 213357.png

    Caption by: John Sheesley

  • 213358.png

    Caption by: John Sheesley

  • 213359.png

    Caption by: John Sheesley

  • 213360.png

    Caption by: John Sheesley

  • 213361.png

    Even though you have a networked TCP/IP stack installed, IE 5.01's Setup program tries to configure a modem. Cancel out of it.

    Caption by: John Sheesley

  • 213362.png

    Caption by: John Sheesley

  • 213363.png

    Caption by: John Sheesley

  • 213364.png

    After the install completes, you must restart yet again.

    Caption by: John Sheesley

  • 213365.png

    When Windows restarts, IE 5.01 finishes its configuration.

    Caption by: John Sheesley

  • 213366.png

    You must choose a timezone.

    Caption by: John Sheesley

  • 213367.png

    Caption by: John Sheesley

  • 213368.png

    Caption by: John Sheesley

  • 213369.png

    With modern versions of IE, you may be tempted to use the Internet Connection Wizard to setup networked surfing.

    Caption by: John Sheesley

  • 213370.png

    Caption by: John Sheesley

  • 213371.png

    D'oh! IE *still* wants to only use a modem.

    Caption by: John Sheesley

  • 213372.png

    Caption by: John Sheesley

  • 213373.png

    Start IE 5.01 to fix the problem directly.

    Caption by: John Sheesley

  • 213374.png

    Select Tools | Internet Options. When you click the Connection tab, IE will complain about the connection settings.

    Caption by: John Sheesley

  • 213375.png

    Select Your Local Area Network. Now you don't have to worry about the modem.

    Caption by: John Sheesley

  • 213376.png

    The default homepage is a Lycos page that doesn't exist anymore.

    Caption by: John Sheesley

  • 213377.png

    Pick a new home page.

    Caption by: John Sheesley

  • 213378.png

    IE 5.01 may be the latest Web browser available, but it doesn't support Javascript well enough to render most Web sites. Be prepared for lots of errors and for many sites not to load.

    Caption by: John Sheesley

  • 213379.png

    Google finally loads. Search results will not launch however. AltaVista is a better search engine with IE 5.01.

    Caption by: John Sheesley

  • 213380.png

    You can load 32bit support for Windows 3.1 by installing Win32s. This will run some, but a vast minority, of 32bit Windows programs.

    Caption by: John Sheesley

  • 213381.png

    Caption by: John Sheesley

  • 213382.png

    Caption by: John Sheesley

  • 213383.png

    Caption by: John Sheesley

  • 213384.png

    Caption by: John Sheesley

  • 213385.png

    Caption by: John Sheesley

  • 213386.png

    Caption by: John Sheesley

  • 213387.png

    Caption by: John Sheesley

  • 213388.png

    Freecell is one of the few 32bit programs that work with Windows 3.x.

    Caption by: John Sheesley

  • 213389.png

    Caption by: John Sheesley

  • 213390.png

    As an alternative to IE, you can load Netscape 3.0. It won't do much better than IE in the long run however. It will crash your machine much less however. IE 5.01 sometimes will lock the session if it encounters a Web site with a lot of Javascript.

    Caption by: John Sheesley

  • 213391.png

    Caption by: John Sheesley

  • 213392.png

    Caption by: John Sheesley

  • 213393.png

    Caption by: John Sheesley

  • 213394.png

    Caption by: John Sheesley

1 of 100

Virtual PC 2007 is a handy tool for running multiple operating systems. However, it's not without its limitations when running an older OS like Windows 3.1. Here's what it takes to get everything working.

Read More Read Less

Virtual PC 2007 is a handy tool for running multiple operating systems. However, it's not without its limitations when running an older OS like Windows 3.1. Here's what it takes to get everything working.

This screen shows a basic Windows 3.11 installation under Virtual PC. The emulated hardware under VPC isn't supported by Windows 3.x and you have to hunt around to get all of the drivers and stuff that you need.

The Classics Rock blog on TechRepublic lists the file locations. You'll need.

Caption by: John Sheesley

1 of 100

Related Topics:

Enterprise Software Virtualization Cloud Big Data Analytics Innovation Tech and Work

Related Galleries

    • 1 of 3