It is possible to install Windows ME properly without crashing. It requires some workarounds and changing parameters per boot, but it is possible. Boot into a disk image with a base DOS os on it (MS-DOS 6.22 or Win 9x DOS mode). Your dosbox.conf should have core=dynamic and IDE emulation enabled.
Make sure the v86io hack is enabled so that Windows ME can use the same INT 13h detection method to enable it's IDE driver. Also make sure that apmbios=false at this stage so that Windows ME does not install the APM driver (which is incompatible with DOSBox and can be a major source of BSODs). Run the first setup phase of the Windows ME setup program. When it reboots, shut down the DOSBox emulator. Do NOT let it boot.
Change your dosbox.conf to core=normal or core=full. Start DOSBox and let Windows ME run through it's setup and autodetection. This will take a long time because you are not using the dynamic core. But because of some issues with the dynamic core and some floating point tests carried out by Setup, you cannot use the dynamic core at this stage. When the setup and detection phase is complete, let Windows ME reboot.
It will begin the normal desktop, but may insist on running the Setup and autodetection phase again before allowing the desktop to show. When the desktop finally appears, shut down Windows ME.
Edit your dosbox.conf to change core=dynamic. You may also set apmbios=true at this point if you want Windows shutdown to close DOSBox automatically-but make sure you do not allow WinME to install the APM driver! Alternative method (faster): Run Windows ME setup with core=dynamic. Let it go as far as it can. When you can no longer proceed without crashing, reboot WinME into safe mode, force your way to the desktop, and use regedit.exe to delete all startup keys from registry location HKEYLOCALMACHINE SOFTWARE Microsoft Windows CurrentVersion RunOnce This will allow Windows ME to boot, though with a lot of missing driver functionality. It is very likely in this mode that you will forever be stuck in 640x480 16-color mode, and every time you boot, Windows ME will complain the display is not configured correctly and any attempt to remedy that will fail (evil voice) MWAHAHAHAHAHAHAAAA! THAT'S WHAT YOU GET FOR BEING SO IMPATIENT SUCKER!.
![]()
Copy lines. Copy permalink. Go.
Contents. Wine Main article: Wine is for Linux, various BSDs, and OS X and allows Windows applications to run on those systems. Support for Windows 3.x and 9x programs is quite strong, though since it focuses more on modern games, they're the lowest priority. DOSBox Main article: Windows 3.x, 95, and 98 can be installed in DOSBox. Windows ME can also be installed, but in comparison to the other versions of Windows listed here, it is unstable and runs very poorly in DOSBox. DOSBox was not designed to run Windows. Windows 3.x runs very smoothly, but 95 and 98 require more legwork (for instance, Windows 3.x will run games from a mounted CD drive just fine, while 9x require Daemon Tools to be installed inside the OS) and are much more clunky.
They also run slower than unaccelerated QEMU. Running DOS games from inside Windows caused problems with a real copy. It is much worse inside DOSBox so do not run DOS games from Windows on DOSBox. There is no 3D acceleration available. Some games will not detect Windows properly and refuse to install.
All the problems and bugs Windows had by itself will only be made worse using it in an emulator and without a real copy of DOS. Step by step guide to installing Windows on DOSBox. There has been interest in creating a spin off version of DOSBox that incorporates compatibility with Windows 95/98/ME called, but as of now it has not passed the theoretical stage. PCem Main article: PCem is an emulator for old x86 PCs that can emulate actual old hardware fairly accurately. Configuration is not the easiest, but once it's running, it works quite well. Needs somewhat powerful hardware to run.
Currently, it only emulates up to a Pentium processor on the latest stable release, but if you have the muscle for it, you can also emulate an S3 ViRGE, or even a 3dfx Voodoo. Bochs/Qemu Both of these emulators are good for general purpose x86 emulation.
Dosbox Emulator Online
3D acceleration isn't that great right now so it's better to use another option until 3D acceleration improves. References.
3D-Acceleration in VM: VMware Workstation 5.5 - Experimental support for DirectX 8; also supported with VMGL VMware Workstation 7.0 and 8.0 - Support for DirectX 9.0c Shader Model 3 and OpenGL 2.13D Oracle VirtualBox - with Extension Pack and Guest Additions (PUEL) - OpenGL 2.0 and Direct3D 8/9 VMware and VirtualBox supports 3D-Acceleration only in DX 8 and 9 games. Games with lower DirectX will not work. From other forum: Last time I tested it, it was not a great deal. Virtualbox only supports DirectX8 and later, in 2000 and later guests. That means that: - Windows 9x has no 3D acceleration. Games using DirectX 7 or earlier (Final Fantasy VII, Diablo II, those things) won't work. You can try this with dxdiag.
It works, but fails some tests. I think that VMWare has the same limitations, but I've not tried.
Vmware is the same. DX8+ and OGL in Windows 2000+ guests.
Windows 3.1 - Microsoft (1992) Tested By: iamthejake2000 runnable - playable - supported DOSBox version: 0.65 ( supported) This Battle Station is Fully Operational (2011-05-14 18:12) Floppy6 Managed to get install of 3.1 running flawlessly. No crashing after using DOS programs and no hangs. In your config, set up with svgas3 and sb16 audio. I installed the vga drivers for the S3 Trio 64V, which allows 64,000 color (high color) at 1024x768 resolution. For the audio, make sure to use the win3.1 installer for sound blaster 16 -the DOS installer messes up, so you must use the installer made for 3.1. If you find the legit installer, the file name on the actual install folder should read 'sb16w31'. Unfortunately, I don't know exactly where to scoop these drivers from on the internet.
I own a legitimate copy of win 3.1 on floppies, and the drivers I have are literally from my old PC that I used to run back in 1998. Darkromis (2008-07-17 00:05) darkromis i had the same problem as bob bobato, but i found a webpage explaining about windows 3.1 with dosbox and besides explaining you all the installation proccess, that pages got links to drivers and using s3 driver resolve the problem of crashing after using a dos program and also it gives you the chance of changing your resolution and also you can use 256 colors. By the way the webpage is Works well enough (2008-04-25 00:02) bob bobato Works well enough, but if you try to use a DOS program through windows 3.1, it will work, but DOSbox will crash when you exit the program. Note: (2006-06-02 12:39) iamthejake2000 Works fine in VGA 640x480 16 color mode, can get SB16 drivers installed and working.
In the original Emacspeak HOWTO, James Van Zandt provided instructions on how to install Linux from a DOS machine using a null-modem cable. As with the other instructions in this HOWTO, I tried, unfortunately without success, to duplicate this procedure.
However, I have provided the information gathered during testing in the following section. If you successfully install Linux from a Windows™ or DOS™ machine over a null-modem cable, please let me know the procedure you followed and I'll include it here. Please note that the original instructions for installing Linux over a null modem cable were written for a DOS machine. I first attempted to reproduce these instructions with my Windows 2000 machine (from the DOS prompt) and Red Hat 7.1. Although I successfully downloaded and installed JAWS for DOS (available from Freedom Scientific at ), I was unable to get a DOS VT100 terminal emulator installed.
I tried using TELIX, which was popular several years ago, but when I tried to install TELIX version 3.51, I got a runtime error. Since I was unable to find any other DOS terminal emulators, I decided to try using a Windows screenreader and terminal emulator instead. This section documents the procedure I tried with the Windows machine. For this process, you will need a machine with a working speech synthesizer and a terminal emulator program. For my test, I used a Windows 2000 machine and tried both Narrarator (which comes with Windows 2000) and JAWS for Windows v.3.5. For the terminal emulator, I used tried both Hyperterminal (which comes with Windows) and CRT (which can be downloaded from ). You will also need a second machine (on which to install Linux), a null modem cable, and a copy of your preferred Linux distribution on either floppy disk or CD-ROM.
If you still have trouble downloading harvest moon back to nature iso psp or any other file, post it in comments below and our support team or a community member will help you! Free download harvest moon back to nature bahasa indonesia psx iso. If file is deleted from your desired shared host first try checking different host by clicking on another file title.
To connect the two computers, you need a 'null modem' cable. A 'null modem' cable is a serial cable that connects ground to ground and transmits on each end to receive on the other. The cable that comes with the DOS application LapLink will work fine. The LapLink cable is particularly handy because it has both a 9 pin and a 25 pin connector on each end. Alternatively, you may be able to find a null modem cable at your local computer store, or you can have one made. If you choose to have one made, here are the required connections:.
For two 9 pin connectors, connect pin 2 (receive data) to pin 3, pin 3 (transmit data) to pin 2, and pin 5 (signal ground) to pin 5. For two 25 pin connectors, connect pin 2 (receive data) to pin 3, pin 3 (transmit data) to pin 2, and pin 7 (signal ground) to pin 7. For a 9 pin connector (first) to a 25 pin connector (second), connect pin 2 (receive data) to pin 2 (transmit data), pin 3 (transmit data) to pin 3 (receive data), and pin 5 (signal ground) to pin 7 (signal ground). Once you have your null modem cable, you'll need to connect the two machines while both of them are off. It's easiest to use COM1 on both machines.
Once you've got them connected, you're ready to start them up, as discussed in the next section. Once your machines are connected via the null modem cable, boot the DOS/Windows machine, then start the terminal emulation program. For my test, I tried both Hyperterminal (which comes with Windows 2000) and CRT (which can be downloaded from.
For some reason, the arrow keys did not work in HyperTerminal, making navigation within the HyperTerminal window impossible. However, the arrow keys (as well as Tab and Return) do work in CRT, so I recommend using CRT as your terminal emulator. Set the terminal emulator for 9600 baud, no parity, eight data bits, 1 stop bit. If 'Flow control' is an option, select Hardware. Also be sure to set your terminal emulation mode to VT100. Start the terminal emulator connection (you won't get any data at this point, as your Linux machine should still be off).
Once you've set up the terminal emulator on your DOS/Windows machine, insert the 'boot' floppy or CD into your Linux machine and boot the machine. With Red Hat, at the boot: prompt, I typed in the command linux text console=ttyS0. Note that the 's' in 'ttyS0' is capitalized, and that's a 'zero' at the end of the string, not a capital letter 'o.' Other distributions may require other strings, so if you know the syntax required for distros other than Red Hat, please let me know and I will include that information here. Once you've typed in this string at the boot: prompt and hit Return, you should get output in your terminal emulator program on your DOS/Windows machine. Unfortunately, at this point I discovered that neither JAWS for Windows nor Narrarator produces speech output in either the HyperTerminal or CRT terminal windows.
![]()
This ultimately stymied my attempts to install Linux over a null modem cable.
Comments are closed.
|
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |