Windows 9x is NOT officially supported under DOSBox.STABILITY OF WINDOWS 9x GUEST IN DOSBOX IS HIGHLY DEPENDENT ON VIDEO DRIVERS. INSTALL THE ATTACHED DRIVERS FOR S3 CARD.WINDOWS 9X WILL FREEZE OR CRASH OCCASIONALLY. LEARN TO LOVE IT OR FIX IT YOURSELF. ONLY USE CPUTYPE=PENTIUMSLOW in DOSBOX.CONF. USE NO OTHER PARAMETERS WINDOWS ME DOES NOT WORK IN DOSBOX. USE VMWARE VIRTUALPC ETC.
Downloads Needed: Latest DOSBox version (DOSBox 0.74 as of this guide) or DOSBox SVN (7-23-2011 as of this guide) HAL9000 Megabuild v6 Gulikoza or Yhkwong DOSBox build (for Glide support) Winimage ImDisk or equivalent WinPcap (for builds of DOSBox with NE2000 support) GENERIC WINDOWS 9x INSTALLATION INSTRUCTIONS.WITH WINDOWS 95B+ YOU WILL EXPERIENCE DIALOG ERRORS DURING INSTALL. JUST CONTINUE THE INSTALL SHORT INSTRUCTIONS 1. Download and install DOSBox 0.74 2. Download 2GBFreeDOS.zip attached to this post. Unzip the contents to the DOSBox directory. Add this line to the autoexec section in dosbox.conf imgmount 2 2gbfreedos.img -t hdd -fs none -size 512, 4. Open the 2GBfreedos.img with Winimage or IMDISK.
Copy the 9x installation files to the '9xinst' directory. Execute DOSBox and boot the image with the command 'boot -l c' 6. Go to the 9xinst directory on the image and type in 'setup /NM /IS' to start the install. When setup is done with the first part of setup it will close DOSBox. (This is normal) 8. Start DOSBox again and run 'boot -l c'.
When setup is done it will go straight to the Windows desktop and you are done installing! Shut down DOSBox and make a backup of the image so you don't have to reinstall again. LONG INSTRUCTIONS 1. Download and install DOSBox 0.74 (Overwrite DOSBox 0.74 files with SVN if you want to use the SVN) 2. Download HAL9000 MegaBuild v6 and install: 3. Execute HAL9000 MegaBuild v6.
Create a Hard Drive image by typing 'Imgmake test.img -t hd2gig -nofs -bat' inside of DOSBox. (Refer to the documentation for other options for imgmake) This command will create 'test.img' in the same directory as HAL9000 MegaBuild that is 2gb in size. Make a backup copy of the image so you don't have to bother recreating it again if you wish. (Use NTFS compression on it or compress it with a compression program to save space if needed). Move 'test.img' and 'test.bat' to the DOSBox 0.74 directory (if you are not going to use HAL9000's DOSBox Build to run the OS) 6. Next you will next need a floppy image of MS-DOS. I'm not sure that it matters which version, as long as it's MSDOS 5.00+ then you should be good to go.
If you don't already have an image then use Winimage to create one or you can download an image from the internet. Name the floppy image something small like 'dos622.ima'. Copy the floppy image to the DOSBox directory. Copy the Windows 9x CD to a folder in the DosBox directory. Put it in a directory with a short name like '9xinst'.
Open DosBox.conf and make sure that the Autoexec section looks like this: (use the values from 'test.bat' for -size) imgmount 0 dos622.ima -t floppy -fs none imgmount 2 test.img -t hdd -fs none -size 512,63,xx,xxxx (This will automatically mount the image whenever you launch DosBox) 10. Execute DOSBox and verify that it mounted the images correctly. If it didn't then you have done something wrong.
(Either bad images or you still have it open in another program) 11. Type in 'Boot -l a' to boot your floppy image. Go into FDISK and partition your HD.
Close DOSBox 13. Open DOSBox and execute 'Boot -l a'. Run 'format c: /s' to format the HD and to make it bootable.
Exit DOSBox 16. REM the below line in the autoexec section in dosbox.conf since it is no longer necessary: imgmount 0 dos622.ima -t floppy -fs none 17. Open 'test.img' with Winimage and copy the 9x folder you copied to your hard drive to the image. (or you could mount the image with DOSBox and copy the files over but DOSBox may become unresponsive so you may think it froze.using a program like Winimage you will see a progress bar or similar so you know that it's actually working) 18. Adobe language pack download.
Execute DosBox and type in 'Boot -l c' to boot your HD image. Go to the directory on the image where you copied Windows and type in 'setup /is' to install Windows.
When setup is done copying Windows files it will close DOSBox. (This is normal) 21. Start DOSBox and run the command 'boot -l c' again to resume setup. When setup is done it will go straight to the Windows desktop and you are done installing! Shut down DOSBox and make a backup of the image so you don't have to reinstall again.
INSTALLATION ERRORS DOSBox 0.74 and 7-23-2011 SVN Windows 98SE Will throw up error during 'Updating System Settings'. 'An error or exception occurred while calling the function 'DllRegisterServer' in 'C: Windows system mshtmled.dll'.
After that you will receive a ton of error dialogs. Keep hitting close. Using core=Pentiumslow will reduce most of these errors but not all. Windows 95C May experience an error or two during the 'Control Panel - Startmenu, Windows Help, etc screen. Windows 95 95A Only versions of Windows to complete the installation process without errors. May experience an error on first logging into the desktop. POST INSTALL VIDEO AFTER INSTALL IMMEDIATELY BOOT INTO SAFE MODE AND INSTALL THE S3 VIDEO DRIVERS.
For some Windows versions you may have video corruption when you boot to the desktop. This is due to the video driver that Windows 9x is trying to use (it's not compatible with the video card that DOSBox emulates) Change the color depth to 16 colors until you can install a better graphics driver. (This way you'll at least be able to navigate the interface). When installing the S3 drivers use any model from the list.
The driver does not care. Other video drivers to try: Use the 'Universal' drivers. AUDIO The audio card emulated by DosBox is a SoundBlaster 16. Windows 95C detects the sound card just fine but the included Windows audio drivers are old dated 8-24-1996. Attached are SB16 drivers from 3-20-1997 (v4.35.21) and they seem to work fine.
The last version of DirectX to include drivers for devices was Direct 6. After installing DirectX 6 the SB16 may not work anymore.
DirectX 6 may update the audio drivers to v4. Which is incompatible with DOSBox. SO DO NOT INSTALL DirectX 6 AND IF YOU DO REINSTALL THE AUDIO DRIVER CD EMULATION Windows 9x under DOSBox does not support CD emulation so you need to use a program like Daemon Tools to emulate a CD-ROM. Use Daemon Tools 3.47.
(Requires Windows Installer v2.0) TCP/IP SUPPORT Verify that WinPCap is installed on the host. Verify that DOSBox.conf is configured correctly INTERNAL D3D GLIDE SUPPORT For Glide/D3D support download yhkwong DOSBox Build: 1. Unzip yhkwong DOSBox Build. Copy your Windows.img to the same directory. Add 'imgmount 2 x.img -t hdd -fs none -size 512,63,xx,xx to the autoexec section of DOSBox.conf 4. Change glide=true to glide=emu in dosbox.conf 5.
Download attached Voodoo 1 drivers. Add Voodoo driver to image.
Extract driver to C: TEMP 9. Run 'Add New Hardware' Wizard and then reboot. (It should install 'PCI bus' which is needed for the Voodoo card) 10. Go into Device Manager and install the Voodoo driver. The above caused Windows to freeze and graphics corruption with Windows 95 and 95a.
Works fine with 98SE. EXTERNAL GLIDE SUPPORT 1. Use a glide enabled build (Gulikoza or yhkwong) 2. Verify glide=true in dosbox.conf 3. Download glide2x.zip from here: 4.
Copy glide2x.dll to where your game is located in the DOSBox image. Modify autoexec.bat on the image. Add set glide=0x600. (No voodoo drivers required).Only some glide and MiniGL games supported.Change glide2x.dll on host windows to any other wrapper if you want. List of Glide Wrappers: dgVoodoo Nglide PSVoodoo OpenGlide Zeckensack JOYSTICK Joystick needs to be set manually Windows wants to use address 200-207, but it needs to be 201-201. Go to Device Manager-Joystick Switch from 'Basic Configuration 1' to 'Basic Configuration 0' in 'Resources' in device properties for joystick.
WINDOWS UPDATES AND ADDONS Windows 95 Install Windows 95 SP1 Install DirectX 8.0 Install DCOM95 NOTES HOW TO INSTALL WINDOWS 9x USING FREEDOS ALTERNATE WAY TO COPY FILES TO A.IMG USING DOSBOX (Not recommended due to DOSBox appearing to hang and being very slow at copying the files) Close DOSBox Edit imgmount like in DOSBox.conf to look like this: imgmount d x.img -t hdd -size 512,63,x,x Open DOSBox Type in 'Mount c.' To mount your host DOSBox directory. Switch to D: Type in 'MD '9xinst'. Switch to 'C:' and go to where you copied your Windows files. Do a 'Copy. D: 9xinst' to copy your Windows files to the HD image. S3 driver is really for PCI video card but driver does not require it.
'Voodoo' output in DOSBox console does not mean the game is using Glide. Could be either D3D or Glide. If you see 'Glide:Activated' in DOSBox console then game uses Glide. Only HAL9000 DOSBox build can autodetect image parameters. When not using his build you MUST specify the size parameters. As of DOSBox 0.74 the emulated video card in DOSBox is a S3 Trio64 PCI NOT a Trio64V+ which are not driver compatible.
The drivers included with Windows will appear to work but will cause issues. Need verification on model of emulated video card.
MSDOS.SYS modification 2GB image template uses 512, The first always has to be 512 (should be omitted imo), the second can't be more than 63, the third is limited to 255 and the 4th to 1023. These are the old BIOS limits DOSBox also implements. To get disks larger than 500MB the number of heads has to be increased.
DOSBOX ISSUES WITH GUEST OS WINDOWS ME INSTALLATION IN DOSBOX May receive error during install about disk issue. Quit to DOS and run scandisk.
Install will eventually freeze. USING COPIED OVER WINDOWS ME INSTALL 1. Install Windows ME in Vmware 2.
Mount vmdk in Host OS 3. Copy ALL files on the vmdk to the.img file 4. Mount Windows ME bootable floppy and.img in DOSBox 5. Run SYS C: 6.
Freezes DOSBox in normal and safe mode. Tested with 0.74, 7-23-2011 SVN, HAL9000 Megabuild 6, yhkwong 7-5-2011.
ERRORS DXDIAG will crash DOSBox. If Windows constantly crashes causing Scandisk to always run and you want to disable Scandisk then read the following.
(THIS IS NOT RECOMMENDED) Windows 95 Download TweakUI for Windows 95. Install TweakUI Open TweakUI Go to 'Boot' Tab. Select 'Autorun Scandisk'.
Select 'Never' Windows 98+ Open 'MSCONFIG', Click the Advanced button. Select 'Disable Scandisk after bad shutdown' If you receive the following error message then either your IMGMOUNT settings or your image are incorrect: 'Message SU0013 Setup cannot create files on your startup drive and cannot setup Windows 98.'
![]()
- Attached are 4 2GB images created using IMGMAKE from HAL9000 Megabuild (Thanks HAL!). These images are provided so that you do not need to bother with creating, partitioning, formatting and making bootable your own image. 2GBPartitioned = 2GB.IMG parititioned with MS-DOS 6.22 FDISK into one Primary. 2GBFreeDOS = 2GB.img partitioned and formated FAT16 with FreeDOS system files. 2GBFAT16NO-OS.zip = 2GB.img partitoned and formated FAT16.
2GBunpartitioned = 2GB.img not paritioned and not formated. Attachments (166.53 KiB) Downloaded 4864 times (2.36 MiB) Downloaded 4328 times (2.46 MiB) Downloaded 8468 times (2.36 MiB) Downloaded 3637 times (568.76 KiB) Downloaded 4841 times. Need to go over guide again. Need to test machine=vgaonly stability Need to try LDGFXROM from HAL9000 Megabuild to load S3 BIOS. Possibly would increase 9x stability.
Daemon Tools requires Windows 95B and the USB Supplement. Also requires IE4 Desktop Update Networking info Need to mention mounting additional hard drives. Need to verify Windows 98 installs with FreeDOS system files. Look into providing smaller images for crazy mobile phone users. Windows ME reporting as working in yhkwong DOSBox build as of 8-25-2011 by Robertmo 1. Install Windows ME in Vmware Virtual PC 2.
![]()
Copy over files to DOSBox.img 3. Run Windows ME in Safe mode. Remove all devices from Device manager. Reboot and run in normal mode. Mount image files on host.
Windows 9x is NOT officially supported under DOSBox.STABILITY OF WINDOWS 9x GUEST IN DOSBOX IS HIGHLY DEPENDENT ON VIDEO DRIVERS. INSTALL THE ATTACHED DRIVERS FOR S3 CARD.WINDOWS 9X WILL FREEZE OR CRASH OCCASIONALLY. LEARN TO LOVE IT OR FIX IT YOURSELF. ONLY USE CPUTYPE=PENTIUMSLOW in DOSBOX.CONF.
USE NO OTHER PARAMETERS WINDOWS ME DOES NOT WORK IN DOSBOX. USE VMWARE VIRTUALPC ETC. Downloads Needed: Latest DOSBox version (DOSBox 0.74 as of this guide) or DOSBox SVN (7-23-2011 as of this guide) HAL9000 Megabuild v6 Gulikoza or Yhkwong DOSBox build (for Glide support) Winimage ImDisk or equivalent WinPcap (for builds of DOSBox with NE2000 support) GENERIC WINDOWS 9x INSTALLATION INSTRUCTIONS.WITH WINDOWS 95B+ YOU WILL EXPERIENCE DIALOG ERRORS DURING INSTALL. JUST CONTINUE THE INSTALL SHORT INSTRUCTIONS 1.
Download and install DOSBox 0.74 2. Download 2GBFreeDOS.zip attached to this post.
Unzip the contents to the DOSBox directory. Add this line to the autoexec section in dosbox.conf imgmount 2 2gbfreedos.img -t hdd -fs none -size 512, 4.
Open the 2GBfreedos.img with Winimage or IMDISK. Copy the 9x installation files to the '9xinst' directory. Execute DOSBox and boot the image with the command 'boot -l c' 6. Go to the 9xinst directory on the image and type in 'setup /NM /IS' to start the install. When setup is done with the first part of setup it will close DOSBox. (This is normal) 8.
Start DOSBox again and run 'boot -l c'. When setup is done it will go straight to the Windows desktop and you are done installing!
Shut down DOSBox and make a backup of the image so you don't have to reinstall again. LONG INSTRUCTIONS 1. Download and install DOSBox 0.74 (Overwrite DOSBox 0.74 files with SVN if you want to use the SVN) 2.
Download HAL9000 MegaBuild v6 and install: 3. Execute HAL9000 MegaBuild v6. Create a Hard Drive image by typing 'Imgmake test.img -t hd2gig -nofs -bat' inside of DOSBox. (Refer to the documentation for other options for imgmake) This command will create 'test.img' in the same directory as HAL9000 MegaBuild that is 2gb in size. Make a backup copy of the image so you don't have to bother recreating it again if you wish. (Use NTFS compression on it or compress it with a compression program to save space if needed).
Move 'test.img' and 'test.bat' to the DOSBox 0.74 directory (if you are not going to use HAL9000's DOSBox Build to run the OS) 6. Next you will next need a floppy image of MS-DOS. I'm not sure that it matters which version, as long as it's MSDOS 5.00+ then you should be good to go. If you don't already have an image then use Winimage to create one or you can download an image from the internet. Name the floppy image something small like 'dos622.ima'. Copy the floppy image to the DOSBox directory. Copy the Windows 9x CD to a folder in the DosBox directory.
Put it in a directory with a short name like '9xinst'. Open DosBox.conf and make sure that the Autoexec section looks like this: (use the values from 'test.bat' for -size) imgmount 0 dos622.ima -t floppy -fs none imgmount 2 test.img -t hdd -fs none -size 512,63,xx,xxxx (This will automatically mount the image whenever you launch DosBox) 10. Execute DOSBox and verify that it mounted the images correctly.
If it didn't then you have done something wrong. (Either bad images or you still have it open in another program) 11. Type in 'Boot -l a' to boot your floppy image. Go into FDISK and partition your HD. Close DOSBox 13.
Open DOSBox and execute 'Boot -l a'. Run 'format c: /s' to format the HD and to make it bootable.
Exit DOSBox 16. REM the below line in the autoexec section in dosbox.conf since it is no longer necessary: imgmount 0 dos622.ima -t floppy -fs none 17. Open 'test.img' with Winimage and copy the 9x folder you copied to your hard drive to the image. (or you could mount the image with DOSBox and copy the files over but DOSBox may become unresponsive so you may think it froze.using a program like Winimage you will see a progress bar or similar so you know that it's actually working) 18. Execute DosBox and type in 'Boot -l c' to boot your HD image. Go to the directory on the image where you copied Windows and type in 'setup /is' to install Windows. When setup is done copying Windows files it will close DOSBox.
(This is normal) 21. Start DOSBox and run the command 'boot -l c' again to resume setup. When setup is done it will go straight to the Windows desktop and you are done installing!
Dosbox Turbo Windows 95
Shut down DOSBox and make a backup of the image so you don't have to reinstall again. INSTALLATION ERRORS DOSBox 0.74 and 7-23-2011 SVN Windows 98SE Will throw up error during 'Updating System Settings'. 'An error or exception occurred while calling the function 'DllRegisterServer' in 'C: Windows system mshtmled.dll'. After that you will receive a ton of error dialogs.
Keep hitting close. Using core=Pentiumslow will reduce most of these errors but not all. Windows 95C May experience an error or two during the 'Control Panel - Startmenu, Windows Help, etc screen. Windows 95 95A Only versions of Windows to complete the installation process without errors. May experience an error on first logging into the desktop. POST INSTALL VIDEO AFTER INSTALL IMMEDIATELY BOOT INTO SAFE MODE AND INSTALL THE S3 VIDEO DRIVERS. For some Windows versions you may have video corruption when you boot to the desktop.
Windows 95 On Dosbox Turbo
This is due to the video driver that Windows 9x is trying to use (it's not compatible with the video card that DOSBox emulates) Change the color depth to 16 colors until you can install a better graphics driver. (This way you'll at least be able to navigate the interface).
When installing the S3 drivers use any model from the list. The driver does not care. Other video drivers to try: Use the 'Universal' drivers.
AUDIO The audio card emulated by DosBox is a SoundBlaster 16. Windows 95C detects the sound card just fine but the included Windows audio drivers are old dated 8-24-1996. Attached are SB16 drivers from 3-20-1997 (v4.35.21) and they seem to work fine. The last version of DirectX to include drivers for devices was Direct 6. After installing DirectX 6 the SB16 may not work anymore. DirectX 6 may update the audio drivers to v4.
Which is incompatible with DOSBox. SO DO NOT INSTALL DirectX 6 AND IF YOU DO REINSTALL THE AUDIO DRIVER CD EMULATION Windows 9x under DOSBox does not support CD emulation so you need to use a program like Daemon Tools to emulate a CD-ROM.
Use Daemon Tools 3.47. (Requires Windows Installer v2.0) TCP/IP SUPPORT Verify that WinPCap is installed on the host. Verify that DOSBox.conf is configured correctly INTERNAL D3D GLIDE SUPPORT For Glide/D3D support download yhkwong DOSBox Build: 1. Unzip yhkwong DOSBox Build. Copy your Windows.img to the same directory. Add 'imgmount 2 x.img -t hdd -fs none -size 512,63,xx,xx to the autoexec section of DOSBox.conf 4. Change glide=true to glide=emu in dosbox.conf 5.
Download attached Voodoo 1 drivers. Add Voodoo driver to image. Extract driver to C: TEMP 9.
Run 'Add New Hardware' Wizard and then reboot. (It should install 'PCI bus' which is needed for the Voodoo card) 10. Go into Device Manager and install the Voodoo driver.
The above caused Windows to freeze and graphics corruption with Windows 95 and 95a. Works fine with 98SE.
EXTERNAL GLIDE SUPPORT 1. Use a glide enabled build (Gulikoza or yhkwong) 2. Verify glide=true in dosbox.conf 3. Download glide2x.zip from here: 4. Copy glide2x.dll to where your game is located in the DOSBox image. Modify autoexec.bat on the image.
Add set glide=0x600. (No voodoo drivers required).Only some glide and MiniGL games supported.Change glide2x.dll on host windows to any other wrapper if you want. Langenscheidt online. List of Glide Wrappers: dgVoodoo Nglide PSVoodoo OpenGlide Zeckensack JOYSTICK Joystick needs to be set manually Windows wants to use address 200-207, but it needs to be 201-201.
Go to Device Manager-Joystick Switch from 'Basic Configuration 1' to 'Basic Configuration 0' in 'Resources' in device properties for joystick. WINDOWS UPDATES AND ADDONS Windows 95 Install Windows 95 SP1 Install DirectX 8.0 Install DCOM95 NOTES HOW TO INSTALL WINDOWS 9x USING FREEDOS ALTERNATE WAY TO COPY FILES TO A.IMG USING DOSBOX (Not recommended due to DOSBox appearing to hang and being very slow at copying the files) Close DOSBox Edit imgmount like in DOSBox.conf to look like this: imgmount d x.img -t hdd -size 512,63,x,x Open DOSBox Type in 'Mount c.'
To mount your host DOSBox directory. Switch to D: Type in 'MD '9xinst'. Switch to 'C:' and go to where you copied your Windows files.
Do a 'Copy. D: 9xinst' to copy your Windows files to the HD image.
S3 driver is really for PCI video card but driver does not require it. 'Voodoo' output in DOSBox console does not mean the game is using Glide. Could be either D3D or Glide. If you see 'Glide:Activated' in DOSBox console then game uses Glide.
Only HAL9000 DOSBox build can autodetect image parameters. When not using his build you MUST specify the size parameters. As of DOSBox 0.74 the emulated video card in DOSBox is a S3 Trio64 PCI NOT a Trio64V+ which are not driver compatible. The drivers included with Windows will appear to work but will cause issues. Need verification on model of emulated video card. MSDOS.SYS modification 2GB image template uses 512, The first always has to be 512 (should be omitted imo), the second can't be more than 63, the third is limited to 255 and the 4th to 1023. These are the old BIOS limits DOSBox also implements.
To get disks larger than 500MB the number of heads has to be increased. DOSBOX ISSUES WITH GUEST OS WINDOWS ME INSTALLATION IN DOSBOX May receive error during install about disk issue. Quit to DOS and run scandisk. Install will eventually freeze. USING COPIED OVER WINDOWS ME INSTALL 1. Install Windows ME in Vmware 2.
Mount vmdk in Host OS 3. Copy ALL files on the vmdk to the.img file 4.
Mount Windows ME bootable floppy and.img in DOSBox 5. Run SYS C: 6. Freezes DOSBox in normal and safe mode. Tested with 0.74, 7-23-2011 SVN, HAL9000 Megabuild 6, yhkwong 7-5-2011. ERRORS DXDIAG will crash DOSBox. If Windows constantly crashes causing Scandisk to always run and you want to disable Scandisk then read the following.
(THIS IS NOT RECOMMENDED) Windows 95 Download TweakUI for Windows 95. Install TweakUI Open TweakUI Go to 'Boot' Tab. Select 'Autorun Scandisk'. Select 'Never' Windows 98+ Open 'MSCONFIG', Click the Advanced button.
Select 'Disable Scandisk after bad shutdown' If you receive the following error message then either your IMGMOUNT settings or your image are incorrect: 'Message SU0013 Setup cannot create files on your startup drive and cannot setup Windows 98.' - Attached are 4 2GB images created using IMGMAKE from HAL9000 Megabuild (Thanks HAL!). These images are provided so that you do not need to bother with creating, partitioning, formatting and making bootable your own image. 2GBPartitioned = 2GB.IMG parititioned with MS-DOS 6.22 FDISK into one Primary. 2GBFreeDOS = 2GB.img partitioned and formated FAT16 with FreeDOS system files.
2GBFAT16NO-OS.zip = 2GB.img partitoned and formated FAT16. 2GBunpartitioned = 2GB.img not paritioned and not formated. Attachments (166.53 KiB) Downloaded 4864 times (2.36 MiB) Downloaded 4328 times (2.46 MiB) Downloaded 8468 times (2.36 MiB) Downloaded 3637 times (568.76 KiB) Downloaded 4841 times. Need to go over guide again. Need to test machine=vgaonly stability Need to try LDGFXROM from HAL9000 Megabuild to load S3 BIOS.
Possibly would increase 9x stability. Daemon Tools requires Windows 95B and the USB Supplement. Also requires IE4 Desktop Update Networking info Need to mention mounting additional hard drives. Need to verify Windows 98 installs with FreeDOS system files. Look into providing smaller images for crazy mobile phone users.
Windows ME reporting as working in yhkwong DOSBox build as of 8-25-2011 by Robertmo 1. Install Windows ME in Vmware Virtual PC 2.
Copy over files to DOSBox.img 3. Run Windows ME in Safe mode. Remove all devices from Device manager. Reboot and run in normal mode. Mount image files on host.
Windows 9x is NOT officially supported under DOSBox.STABILITY OF WINDOWS 9x GUEST IN DOSBOX IS HIGHLY DEPENDENT ON VIDEO DRIVERS. INSTALL THE ATTACHED DRIVERS FOR S3 CARD.WINDOWS 9X WILL FREEZE OR CRASH OCCASIONALLY. LEARN TO LOVE IT OR FIX IT YOURSELF.
ONLY USE CPUTYPE=PENTIUMSLOW in DOSBOX.CONF. USE NO OTHER PARAMETERS WINDOWS ME DOES NOT WORK IN DOSBOX. USE VMWARE VIRTUALPC ETC. Downloads Needed: Latest DOSBox version (DOSBox 0.74 as of this guide) or DOSBox SVN (7-23-2011 as of this guide) HAL9000 Megabuild v6 Gulikoza or Yhkwong DOSBox build (for Glide support) Winimage ImDisk or equivalent WinPcap (for builds of DOSBox with NE2000 support) GENERIC WINDOWS 9x INSTALLATION INSTRUCTIONS.WITH WINDOWS 95B+ YOU WILL EXPERIENCE DIALOG ERRORS DURING INSTALL.
JUST CONTINUE THE INSTALL SHORT INSTRUCTIONS 1. Download and install DOSBox 0.74 2. Download 2GBFreeDOS.zip attached to this post. Unzip the contents to the DOSBox directory. Add this line to the autoexec section in dosbox.conf imgmount 2 2gbfreedos.img -t hdd -fs none -size 512, 4. Open the 2GBfreedos.img with Winimage or IMDISK.
Copy the 9x installation files to the '9xinst' directory. Execute DOSBox and boot the image with the command 'boot -l c' 6. Go to the 9xinst directory on the image and type in 'setup /NM /IS' to start the install. When setup is done with the first part of setup it will close DOSBox. (This is normal) 8.
Start DOSBox again and run 'boot -l c'. When setup is done it will go straight to the Windows desktop and you are done installing! Shut down DOSBox and make a backup of the image so you don't have to reinstall again. LONG INSTRUCTIONS 1.
Download and install DOSBox 0.74 (Overwrite DOSBox 0.74 files with SVN if you want to use the SVN) 2. Download HAL9000 MegaBuild v6 and install: 3.
Execute HAL9000 MegaBuild v6. Create a Hard Drive image by typing 'Imgmake test.img -t hd2gig -nofs -bat' inside of DOSBox. (Refer to the documentation for other options for imgmake) This command will create 'test.img' in the same directory as HAL9000 MegaBuild that is 2gb in size. Make a backup copy of the image so you don't have to bother recreating it again if you wish. (Use NTFS compression on it or compress it with a compression program to save space if needed). Move 'test.img' and 'test.bat' to the DOSBox 0.74 directory (if you are not going to use HAL9000's DOSBox Build to run the OS) 6. Next you will next need a floppy image of MS-DOS.
I'm not sure that it matters which version, as long as it's MSDOS 5.00+ then you should be good to go. If you don't already have an image then use Winimage to create one or you can download an image from the internet. Name the floppy image something small like 'dos622.ima'. Copy the floppy image to the DOSBox directory. Copy the Windows 9x CD to a folder in the DosBox directory. Put it in a directory with a short name like '9xinst'.
Open DosBox.conf and make sure that the Autoexec section looks like this: (use the values from 'test.bat' for -size) imgmount 0 dos622.ima -t floppy -fs none imgmount 2 test.img -t hdd -fs none -size 512,63,xx,xxxx (This will automatically mount the image whenever you launch DosBox) 10. Execute DOSBox and verify that it mounted the images correctly. If it didn't then you have done something wrong.
(Either bad images or you still have it open in another program) 11. Type in 'Boot -l a' to boot your floppy image. Go into FDISK and partition your HD. Close DOSBox 13.
Open DOSBox and execute 'Boot -l a'. Run 'format c: /s' to format the HD and to make it bootable. Exit DOSBox 16. REM the below line in the autoexec section in dosbox.conf since it is no longer necessary: imgmount 0 dos622.ima -t floppy -fs none 17.
Open 'test.img' with Winimage and copy the 9x folder you copied to your hard drive to the image. (or you could mount the image with DOSBox and copy the files over but DOSBox may become unresponsive so you may think it froze.using a program like Winimage you will see a progress bar or similar so you know that it's actually working) 18.
Execute DosBox and type in 'Boot -l c' to boot your HD image. Go to the directory on the image where you copied Windows and type in 'setup /is' to install Windows. When setup is done copying Windows files it will close DOSBox. (This is normal) 21. Start DOSBox and run the command 'boot -l c' again to resume setup. When setup is done it will go straight to the Windows desktop and you are done installing! Shut down DOSBox and make a backup of the image so you don't have to reinstall again.
![]()
INSTALLATION ERRORS DOSBox 0.74 and 7-23-2011 SVN Windows 98SE Will throw up error during 'Updating System Settings'. 'An error or exception occurred while calling the function 'DllRegisterServer' in 'C: Windows system mshtmled.dll'. After that you will receive a ton of error dialogs. Keep hitting close. Using core=Pentiumslow will reduce most of these errors but not all.
Windows 95C May experience an error or two during the 'Control Panel - Startmenu, Windows Help, etc screen. Windows 95 95A Only versions of Windows to complete the installation process without errors. May experience an error on first logging into the desktop.
POST INSTALL VIDEO AFTER INSTALL IMMEDIATELY BOOT INTO SAFE MODE AND INSTALL THE S3 VIDEO DRIVERS. For some Windows versions you may have video corruption when you boot to the desktop.
This is due to the video driver that Windows 9x is trying to use (it's not compatible with the video card that DOSBox emulates) Change the color depth to 16 colors until you can install a better graphics driver. (This way you'll at least be able to navigate the interface).
When installing the S3 drivers use any model from the list. The driver does not care. Other video drivers to try: Use the 'Universal' drivers.
AUDIO The audio card emulated by DosBox is a SoundBlaster 16. Windows 95C detects the sound card just fine but the included Windows audio drivers are old dated 8-24-1996. Attached are SB16 drivers from 3-20-1997 (v4.35.21) and they seem to work fine. The last version of DirectX to include drivers for devices was Direct 6.
After installing DirectX 6 the SB16 may not work anymore. DirectX 6 may update the audio drivers to v4. Which is incompatible with DOSBox. SO DO NOT INSTALL DirectX 6 AND IF YOU DO REINSTALL THE AUDIO DRIVER CD EMULATION Windows 9x under DOSBox does not support CD emulation so you need to use a program like Daemon Tools to emulate a CD-ROM. Use Daemon Tools 3.47. (Requires Windows Installer v2.0) TCP/IP SUPPORT Verify that WinPCap is installed on the host. Verify that DOSBox.conf is configured correctly INTERNAL D3D GLIDE SUPPORT For Glide/D3D support download yhkwong DOSBox Build: 1.
Unzip yhkwong DOSBox Build. Copy your Windows.img to the same directory. Add 'imgmount 2 x.img -t hdd -fs none -size 512,63,xx,xx to the autoexec section of DOSBox.conf 4. Change glide=true to glide=emu in dosbox.conf 5. Download attached Voodoo 1 drivers. Add Voodoo driver to image. Extract driver to C: TEMP 9.
Run 'Add New Hardware' Wizard and then reboot. (It should install 'PCI bus' which is needed for the Voodoo card) 10. Go into Device Manager and install the Voodoo driver. The above caused Windows to freeze and graphics corruption with Windows 95 and 95a. Works fine with 98SE. EXTERNAL GLIDE SUPPORT 1.
Use a glide enabled build (Gulikoza or yhkwong) 2. Verify glide=true in dosbox.conf 3. Download glide2x.zip from here: 4. Copy glide2x.dll to where your game is located in the DOSBox image. Modify autoexec.bat on the image.
Add set glide=0x600. (No voodoo drivers required).Only some glide and MiniGL games supported.Change glide2x.dll on host windows to any other wrapper if you want. List of Glide Wrappers: dgVoodoo Nglide PSVoodoo OpenGlide Zeckensack JOYSTICK Joystick needs to be set manually Windows wants to use address 200-207, but it needs to be 201-201. Go to Device Manager-Joystick Switch from 'Basic Configuration 1' to 'Basic Configuration 0' in 'Resources' in device properties for joystick.
WINDOWS UPDATES AND ADDONS Windows 95 Install Windows 95 SP1 Install DirectX 8.0 Install DCOM95 NOTES HOW TO INSTALL WINDOWS 9x USING FREEDOS ALTERNATE WAY TO COPY FILES TO A.IMG USING DOSBOX (Not recommended due to DOSBox appearing to hang and being very slow at copying the files) Close DOSBox Edit imgmount like in DOSBox.conf to look like this: imgmount d x.img -t hdd -size 512,63,x,x Open DOSBox Type in 'Mount c.' To mount your host DOSBox directory. Switch to D: Type in 'MD '9xinst'. Switch to 'C:' and go to where you copied your Windows files. Do a 'Copy. D: 9xinst' to copy your Windows files to the HD image.
S3 driver is really for PCI video card but driver does not require it. 'Voodoo' output in DOSBox console does not mean the game is using Glide. Could be either D3D or Glide. If you see 'Glide:Activated' in DOSBox console then game uses Glide. Only HAL9000 DOSBox build can autodetect image parameters. When not using his build you MUST specify the size parameters. As of DOSBox 0.74 the emulated video card in DOSBox is a S3 Trio64 PCI NOT a Trio64V+ which are not driver compatible.
The drivers included with Windows will appear to work but will cause issues. Need verification on model of emulated video card. MSDOS.SYS modification 2GB image template uses 512, The first always has to be 512 (should be omitted imo), the second can't be more than 63, the third is limited to 255 and the 4th to 1023.
These are the old BIOS limits DOSBox also implements. To get disks larger than 500MB the number of heads has to be increased. DOSBOX ISSUES WITH GUEST OS WINDOWS ME INSTALLATION IN DOSBOX May receive error during install about disk issue. Quit to DOS and run scandisk. Install will eventually freeze. USING COPIED OVER WINDOWS ME INSTALL 1. Install Windows ME in Vmware 2.
Mount vmdk in Host OS 3. Copy ALL files on the vmdk to the.img file 4. Mount Windows ME bootable floppy and.img in DOSBox 5. Run SYS C: 6. Freezes DOSBox in normal and safe mode. Tested with 0.74, 7-23-2011 SVN, HAL9000 Megabuild 6, yhkwong 7-5-2011.
ERRORS DXDIAG will crash DOSBox. If Windows constantly crashes causing Scandisk to always run and you want to disable Scandisk then read the following. (THIS IS NOT RECOMMENDED) Windows 95 Download TweakUI for Windows 95. Install TweakUI Open TweakUI Go to 'Boot' Tab.
Select 'Autorun Scandisk'. Select 'Never' Windows 98+ Open 'MSCONFIG', Click the Advanced button. Select 'Disable Scandisk after bad shutdown' If you receive the following error message then either your IMGMOUNT settings or your image are incorrect: 'Message SU0013 Setup cannot create files on your startup drive and cannot setup Windows 98.' - Attached are 4 2GB images created using IMGMAKE from HAL9000 Megabuild (Thanks HAL!).
These images are provided so that you do not need to bother with creating, partitioning, formatting and making bootable your own image. 2GBPartitioned = 2GB.IMG parititioned with MS-DOS 6.22 FDISK into one Primary.
2GBFreeDOS = 2GB.img partitioned and formated FAT16 with FreeDOS system files. 2GBFAT16NO-OS.zip = 2GB.img partitoned and formated FAT16. 2GBunpartitioned = 2GB.img not paritioned and not formated. Attachments (166.53 KiB) Downloaded 4864 times (2.36 MiB) Downloaded 4328 times (2.46 MiB) Downloaded 8468 times (2.36 MiB) Downloaded 3637 times (568.76 KiB) Downloaded 4841 times. Need to go over guide again. Need to test machine=vgaonly stability Need to try LDGFXROM from HAL9000 Megabuild to load S3 BIOS.
Possibly would increase 9x stability. Daemon Tools requires Windows 95B and the USB Supplement. Also requires IE4 Desktop Update Networking info Need to mention mounting additional hard drives. Need to verify Windows 98 installs with FreeDOS system files. Look into providing smaller images for crazy mobile phone users.
Windows ME reporting as working in yhkwong DOSBox build as of 8-25-2011 by Robertmo 1. Install Windows ME in Vmware Virtual PC 2. Copy over files to DOSBox.img 3. Run Windows ME in Safe mode. Remove all devices from Device manager. Reboot and run in normal mode.
Mount image files on host.
Old guide wrote:You just can't do it while in DOSBox's own DOS shell-you need to boot up from pure DOS. Let me know if you want anything elaborated; I kind of wrote this in a hurry since I've got a ton of other work to get done today and should really be getting started 1. Get a boot disk First off, get an MS-DOS boot disk. You'll need a.img file.
I myself used from. I don't know exactly which versions of MS-DOS will work, but I suppose 7 should be fine too. I've read that you can cheat Windows into accepting a different version by using set ver 6.0, but I can't confirm this myself since if you use 6.22 you'll never run into this problem. Make sure this file is in your DOSBox directory.
Make a hard disk image You can do this using the bximage program that comes with Bochs. Contains a built in command for creating these from within DOSBox.
(Would be awesome if that could be merged with the main branch.) Making an image using bximage is extremely straightforward. There's a section on using it too. All you really need to remember when using bximage is the cylinder count, since everything else is standardized and shouldn't be changed.
In my example I'm making a 400 MB image which has 812 cylinders. Only flat images are supported (as of this time of editing). Sparse images will not be recognized. However, it's possible to still compress flat files using your host OS's filesystem; in Windows XP, this is the default behavior (hence the blue filename). Copy this file (let's call it c.img) to your DOSBox directory.
Mount and format your new hard disk image So now we have a hard disk image that we're going to be installing Windows 95 on. The problem is it doesn't have a filesystem yet. This is where our boot disk first comes in. Start up DOSBox and type the following: Code: imgmount 2 c.img -size 512,63,16,812 -t hdd -fs none Note: you may need to replace c.img with the name you gave your image file, and replace 812 with the cylinder count you used when creating the file using bximage. It should say Drive number 2 mounted as c.img. You might notice that we're not giving it a drive letter: basically, every drive needs to have a filesystem, which is a sort of file index, before it can be used properly.
Without a filesystem (like FAT32, NTFS, HFS+, etc.) a filesystem is just empty, unorganized space that the operating system can recognize but can't really do anything with, so until we fix this problem we can't mount it under C or any other drive letter yet. Modifying filesystems on a drive is called partitioning. Now type the following: Code: boot 622c.img DOSBox will now boot up from the MS-DOS boot disk. The first thing we'll do is use fdisk to create a filesystem. Run fdisk, choose option 1 (Create DOS partition or Logical DOS Drive), then option 1 (Create Primary DOS Partition). When asked if you want the new partition to comprise the whole hard disk, choose Y. A system restart will be prompted.
The printed ways. Orion tv1333 manual is one of the products of those books. This book model can be downloaded from the site link that we provide in this website. Orion Tv Model 1333 Manual Please Note. The TV code set-up procedure will cancel itself if no keys are TV Set up by manually entering code. Turn on Some brands. Orion tv manual download. As well as service mode entry, make to. Orion tv model 1333 manual precevretafileswordpresscom, orion tv model 1333 manual please note the tv code.
Press enter; DOSBox will quit. Now that we have our newly partitioned drive, we need to format it to effectively bring it to a completely empty and consistent state so that we can start putting files on it. To do so, we need to restart DOSBox and boot back into MS-DOS. This time, however, we'll mount our drive differently: Code: imgmount c c.img At this point, DOSBox should say 'Drive C is mounted as c.img'.
If something is wrong, start this step over. Don't attempt to access the C drive from DOSBox's own DOS shell or you might make it unreadable for pure DOS. Now boot into MS-DOS by using the same command as last time: Code: boot 622c.img When you enter the DOS prompt, format your new C drive by typing: Code: format c: Note: if at this point DOSBox is incorrectly reporting the size of your hard disk, that may be due to either a DOSBox bug or a problem with MS-DOS. I don't know exactly which one, but I've found that hard disk images with a size of over 512 MB (or a cylinder count of over 1000?) tend to be problematic. They'll work, but you'll only be able to use a portion. Copy over setup files and start Windows 95 installation At this point you should have your Windows 95 disc ready.
The version should not matter all that much; I'm using a Dutch OEM version myself, the same one I got with my first Pentium computer about 17 years ago. It doesn't really matter if it's an image or not. The trick here is to copy the installation files over to your newly formatted hard disk and then perform the install from there.
(If you don't have an image already, consider making one anyway. Discs degrade over time and will become unreadable, especially if it's already a home made copy to begin with.) The easiest way to do this (to my knowledge, anyway) is to mount the c.img file in your operating system.
Qbix mentioned that mount -o loop dos622.img /mnt should do it on Linux. I'm on Mac OS X myself and can mount it by double clicking on the image file in the Finder. On Windows, I'm not entirely sure if this is possible, but a program like Isobuster should work too.
Dominus recommends using which is free. Make sure you close DOSBox before you move the files. All you need to do is move over the entire WIN95 directory (the one containing all the CAB files) from the CD to your mounted and now formatted image. It should be only about 34 MB in size. Unmount c.img and restart DOSBox.
We'll now start the installation. Mount c.img like we did the last time and boot 622c.img. To start the installation, type the following: Code: c: cd win95 setup /is (The /is flag will prevent Scandisk from running, which is unnecessary.) Note: if the mouse is not working at this point, exit setup and run mouse.com from the A: drive. Windows 95 will now begin installation. To have Windows start up automatically when starting DOSBox, you could edit your config to contain the following under autoexec: Code: autoexec imgmount c c.img boot c.img In a little while, Windows 95 will be installed.
If you find that DOSBox isn't running anymore after a while, that's because Windows setup prompted a restart. Simply restart DOSBox and reboot into your c.img (if you haven't already added the above lines to your autoexec). Caveats and finishing up Note that the best way to run Windows 95 under DOSBox is with machine=svgas3, core=normal and cputype=pentiumslow.
I'm actually not sure about core=normal being the best choice (qbix mentioned that the dynamic core is probably as safe to use as the normal core), but it's the oldest and most tested. In the past, core=simple was used to run Windows 95, but these days it does more harm than good. The simple core emulates less instructions and causes visual glitches today. It's possible to get working using HAL9000's, but it requires compiling your own version or using his Megabuild. I'll update this guide later when I get that working.
On Mac OS X, make sure you don't set the screen bit depth to anything over 8-bit (256 colors). 16-bit and 32-bit are broken and causes visual glitches.
I've also found that it's MUCH faster in full-screen mode when using the opengl output system. Hardware detection should work just fine, so don't worry about DOSBox locking up. To qbix, Dominus, h-a-l-9000 and the rest of the IRC gang for helping me get this working. Visit #dosbox @ irc.freenode.net. Post here if you're having trouble so I can add fixes to the guide.
TODO. Get internet working. Get CD-ROM drive working (is this possible?). Find out how to easily move win95 dir to disk image on Windows host operating system.
Svenne wrote:Nice guide, but I can't get MS-DOS to detect the image file. I'm using a MS-DOS 7.1 boot floppy. The image file is on 500 mb and 1015 cylinders. What kind of error message are you getting? Does the image mount successfully under the DOSBox prompt but then fail to show up in fdisk (actually, causing fdisk to say 'no fixed disks present')? EDIT: well, this is strange.
I just tried doing this myself a couple of times with a 500 MB image of 1015 cylinders, but apparently I can't get fdisk to recognize disk images that were set to 'sparse' or 'growing'. The 'flat' image type works consistently, which is strange considering I do believe my own install is on a sparse image. Anybody know what might cause this? Member Posts: 154 Joined: 2009-4-26 @ 12:09 Location: Rotterdam, The Netherlands.
I am getting a wonky error trying to follow this guide when trying to mount the image, specifically. I have a 512MB image - 1040 cyl. I try using the line: imgmount 2 c c.img -size 523, -fs none It returns 'The image must be on a host or local drive.' I have also tried imgmount 3, imgmount 2 c x: c.img (where x: is the dosbox directory where c.img is located mounted in dosbox), imgmount 2 c c: dosbox c.img, and every other logical combination I can think of. I am using that special build w/ glide, NE2000, and etc. Support by one of the members here. Not the MBL, the other - his name escapes me but starts with a 'G'.
Member Posts: 191 Joined: 2010-5-29 @ 18:39. Yushatak wrote:I am getting a wonky error trying to follow this guide when trying to mount the image, specifically. I have a 512MB image - 1040 cyl. I try using the line: imgmount 2 c c.img -size 523, -fs none It returns 'The image must be on a host or local drive.'
I have also tried imgmount 3, imgmount 2 c x: c.img (where x: is the dosbox directory where c.img is located mounted in dosbox), imgmount 2 c c: dosbox c.img, and every other logical combination I can think of. First of all, your bytes per sector in that command is set to 523, it should be 512. Also, when mounting the image the first time, you're not supposed to specify a drive letter but a device type instead (hence the 2; the c in your command shouldn't be there, it should only be used later after partitioning). You also need to make sure you add the -t hdd part. Try this: imgmount 2 c.img -size 512, -t hdd -fs none Member Posts: 154 Joined: 2009-4-26 @ 12:09 Location: Rotterdam, The Netherlands.
Comments are closed.
|
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |