Dosbox windows 3.1 archive
- #Dosbox windows 3.1 archive install
- #Dosbox windows 3.1 archive code
- #Dosbox windows 3.1 archive plus
- #Dosbox windows 3.1 archive windows
Up to 800圆00 the color depth can be set to up to 24-bit (16,7 million colors), up to 1024x764 to 16-bit (65 thousand colors), the higher resolutions (up to the highest supported 1600x1200) only permit 8-bit color depth.
#Dosbox windows 3.1 archive windows
If you want, you can change that under Main > Windows Setup > Options > Change System Settings > Display. * The display is set to a 640x480 resolution with 8-bit color depth (256 colors). I found it caused some issues with MIDI music in Windows games. * You might consider disabling MPU-401 emulation in DOSBox. * Dragging & Dropping the batch file over DOSBox executable probably won't work. It most likely will not work properly in older versions. * This package is meant to be used with DOSBox 0.73 and newer. * Again, do not unpack this to the root of your system drive. Unpack to the Windows directory (the one from the above package, not the one where your computer's actual operating system is installed), optionally also the game directory and see if it works. This is an experimental fix that should solve problems with games requiring a Borland DPMI server: You don't want to overwrite your copy of Windows, trust me on that.įrom now on, all it will take to run Windows 3.11 in your DOSBox is - once you mount the directory you extracted the package into - entering windows.bat from the command line. So when trying to display the About box, those versions of SHELL.DLL call said API function and since it's not implemented, end up crashing all of Windows.Įdit: Corrected a statetement - it's the API for obtaining version/Build number from USER.EXE that is missing in 034e, the API for obtaining user name/company certainly exists in 034e.All you have to do is unpack the thing to the location you mount as DOSBox' virtual C drive, unless that location is the root of your system drive. It seems the USER.EXE of 034e, and even that of 043d, going by the behavior of SHELL.DLL, does not implement the API which later versions of SHELL.DLL call to obtain the version/Build number from USER.EXE. Watson, is present in my latest fix of 034e.Īlso, regarding Program Manager crashing when you try to get the About dialog box with some versions of the SHELL.DLL, I have since understood why that happens.
#Dosbox windows 3.1 archive plus
It, plus a TOOLHELP.DLL dated May 1991 that I found with a Google search, and which is compatible with 034e's Dr.
#Dosbox windows 3.1 archive code
Well, I've tested files, and transplanted the code and logo bitmap from the 043d SHELL.DLL into the 026 one to make a SHELL.DLL that's as close as possible to the 034e one. It uses OLECLI.DLL, OLESVR.DLL and SHELL.DLL from Word for Windows 2.0a. I can't test it because I don't have any VM available over here right now.
#Dosbox windows 3.1 archive install
You have to rename it to *.mvb, but it works just the same.Ĭarlaum1 wrote:Can someone please test this? Install 34e using this Disk 2 image. Here's the Windows Multimedia viewer, looking at the same file. "This Product is licenced to" is coming from the host windows (2000). The copyright under that (Wendy Krieger 1988), is coming from the help file itself. The help version is 3.07, running from the Win30MME source. The left screen shows the help screen at one of its start points. It's running under Win2000, so shell.dll comes from that OS. Here is my help file 'welcome', from the custom win31 build. You can even add your own line to this, too.