Windows 3.1 in browser windows#
Obtain an updated version of the application that is compatible with Windows version 3.0 or later." If I run it anyways it says there is not enough memory to start the application :|Ĭan't be a lack of memory, I've allocated like 50mb for this VM. I get a strange error: "This application has violated system integrity due to execution of an invalid instruction and will be terminated."įor Netscape, I get the error message "The application you are about to run, ns407.exe, was designed for a previous version of Windows. cpu load jumps to 100% and it stays like that forever (can still move the hourglass pointer though) When I try to run the installers for ie5, one of two things happen:
![windows 3.1 in browser windows 3.1 in browser](https://www.my-internet-explorer.com/wp-content/uploads/2019/03/IE-2.0-WEB.png)
![windows 3.1 in browser windows 3.1 in browser](https://classicreload.com/sites/default/files/win3x-windows-31-screen.png)
I've tried MSIE 3.01, 4.01, 5.0, 5.1 (got them from different sources), and also netscape 4.07. I've been able to set up WFW 3.11 with SVGA + networking (thanks to your guides), but so far I haven't been able to set up a browser. Hello again ghr :) I'm wondering if there is anything special about VirtualBox that would prevent me from installing IE or netscape. Revision/070728: moved to where it belongs: Windows Guests forum, Īddition/080201: this post is NOT maintained see the Windows Guests forum for additions. Once you 've got the packetdriver set up for Windows 3.1 you're almost there !
Windows 3.1 in browser how to#
Sketchy again, but know that the web still contains lots of info on how to do it, together with the necessary files.
Windows 3.1 in browser drivers#
In setting up MS TCPIP it will ask for NIC drivers (NDIS2, NDIS3): all these can still be found at the AMD website. Performance-wise it doesn't seem to make a big difference whether you use the MS TCPIP stack or Trumpet. It has a readme file with instructions making setting it up not too hard. It can still be ftp'd from the MS website, look for TCP32B.EXE (the slightly older MSTCPIP.EXE will also do). For fastest results MS IE 3.01 is recommended.įor those lucky enough to have their original WfW 3.11 floppies: there's an alternative in using Microsofts own TCPIP stack. Just ignore (or accept defaults on) all questions about mail and dialling. Browsers can be found on the web and their installation tends to be straightforward. TCP RWIN 4096 => for better performance in my case: 2048įor browsing the internet I chose MS IE 3.01 another one like Netscape 4.08 will also do fine if not slightly better. Note the following: From VirtualBox setup: Put all these files in one subdirectory and be sure to add this subdirectory to the PATH statement in AUTOEXEC.BAT. Note that WINPKT.COM may not be included in the Trumpet distribution. Part of the trick is in configuring it.įollow the instructions from the Trumpet Winsock Help file. I use Trumpet Winsock 2.11f for setting up TCPIP. His blog also contains many other items you may consider useful. To avoid your modern CPU being loaded fully by this small and old OS use an utility called WQGHLT.386 from Weiqi Gao. Hint: it may be rewarding to spend some time on (DOS) memory optimisation. CDROM and mouse should be detected automatically.
![windows 3.1 in browser windows 3.1 in browser](https://images.entertainment.ie/storage/images_content/rectangle/620x372/88505.png)
Not much for today's standards but the best you can get with the 'native' In this way you'll end up with a VGA display after setup this can be changed into SuperVGA (800*16, 16 colors). or copy the contents of all disks to a CDROM from where you can setup Win 3.1 (at the cost of having all aplications Windows setup can find, including those on the CDROM, in your Windows Applications group).įor the installation procedure itself run setup and go with defaults as much as possible. Hint: once you feel familiar with CDROM images you can collect all your drivers and applications there and significanctly speed up your installation processess.īased on a DOS machine WIN 3.1 can be installed in a few ways: The post builds on to my earlier one describing the setup of a DOS VM including CDROM and NIC drivers:Ĭontents of this new post were partially inspired by Weiqi Gao's observations. I used VirtualBox 1.4.0 (in 1.3.8 I never got the mouse going or it was running around like a madman). My host system is a typical WinXP machine with 1280*1024 display. Alternatively, with Windows for Workgroups 3.11 you can also use Microsofts TCPIP stack.