Installing Microsoft Windows 95 in DOSBox-X
Table of Contents
- Installing Microsoft Windows 95 in DOSBox-X
-
Overview
- CD-ROM editions this applies to
- External links
- DOSBox-X config file
- General installation Notes
-
Installation Method 1: FAT16 volume up to 2GB
- Requirements
-
Preparing the Harddisk image
- Mount as ISO image
- Mount as directory
- Mount from a CD-ROM drive
- Copying the contents of the CD-ROM
- Running SETUP.EXE
-
Installation Method 2: FAT32 volume
- Requirements
- Preparing the Harddisk image
- Format the drive
- Transfer Windows installation files
- Start the installation
- Booting Windows 95 after installation
- Steps to take after Installation
- Enabling networking
- Emulated video adapter and video mode
-
Emulated sound card
- Enabling General MIDI
- Enabling printing
- 3dfx Voodoo
- Hard Disk Read-ahead optimization
- Outstanding issues
Overview
This guide will give a general description of installing Windows 95 in DOSBox-X, in addition to addressing some common issues.
CD-ROM editions this applies to
-
Windows 95 (RTM; Original release)
-
Windows 95 OSR1 (aka 95A)
-
Windows 95 OSR2 (aka 95B)
-
Windows 95 OSR2.1 (aka 95B)
-
Windows 95 OSR2.5 (aka 95C)
Note: This guide will not work with the Windows 95 diskette versions, as those use a special format (DMF) which is not supported by DOSBox-X.
This guide also assumes a Full Retail or OEM version of Windows 95. Upgrade editions have additional requirements not covered by this guide.
External links
DOSBox-X config file
You first need to create a DOSBox-X config file.
[sdl] autolock=true [dosbox] title=Windows 95 memsize=64 vesa modelist width limit=0 vesa modelist height limit=0 [cpu] cputype=pentium_mmx core=normal cycles=60000 [sblaster] sbtype=sb16vibra irq=5 [ne2000] # If you want networking in Windows, set ne2000=true. # This also requires that you set realnic= to a suitable value for your PC ne2000=false nicirq=10 realnic=list [fdc, primary] int13fakeio=true int13fakev86io=true [ide, primary] int13fakeio=true int13fakev86io=true [ide, secondary] int13fakev86io=true cd-rom insertion delay=4000 [render] scaler=none [autoexec]
Copy the above config and save it as win95.conf
Notes
-
While Windows 95 should support up to 2048MB RAM, in reality more then 480MB can cause problems, as such memsize=480 is the largest safe value.
-
The [autoexec] section will need lines added later.
-
If you want networking in Windows, you need to set ne2000=true and change the realnic= value to one suitable for your PC. See:
Guide: Setting up networking for more information.-
By default if Windows 95 detects a network adapter during installation, it will only setup Novell’s IPX/SPX protocol with Windows Login, which is pretty useless nowadays. You will probably want to change this afterwards in the Network settings to TCP/IP, by adding the TCP/IP protocol.
-
General installation Notes
-
Some parts of the installation can take a considerable amount of time. You can speed this up somewhat by using the DOSBox-X Turbo mode. From the drop-down menu select «CPU» followed by «Turbo (Fast Forward)». But if you decide to use this, be sure to disable Turbo mode whenever you need to enter data or make choices, as it can cause spurious keypresses to be registered causing undesirable effects. It can also cause problems with double click with the mouse not working and audio will also not sound properly, so be sure to disable it when using Windows in DOSBox-X.
-
When creating your HDD image with
IMGMAKEIMGMAKE -
If you get a prompt stating that C:\WINDOWS already exists, ignore it, and continue the installation.
-
During the installation it may ask you if you have a CD-ROM, Network card or sound card that you want it to scan for. You may want to select to scan for a soundcard, as otherwise it may not detect your soundcard (sometimes it does, sometimes it doesn’t). Likewise, if you have NE2000 enabled in your DOSBox-X config file, you may also want to check the Network adapter box. Your DOSBox-X CD-ROM will be detected regardless if you check it’s box or not.
-
In case you installed Windows 95 OSR2.5 you may have noticed that you did not get IE4 and the Active Desktop features. This is because this is an optional install. On the CD, simply run \WIN95\IE4SETUP.EXE to install it. While there is no real advantage to either feature, installing it does bring some new and updated libraries such as MSVCRT.DLL and COMCTL32.DLL that some programs need.
Installation Method 1: FAT16 volume up to 2GB
This installation method only allows for a primary FAT16 volume, which cannot be greater then 2GB.
If you want a larger C: drive using FAT32, follow Method 2 below.
Requirements
-
DOSBox-X 0.83.2 or later, it will NOT work with earlier versions or other DOSBox forks.
-
Windows 95 CD-ROM image (named «Win95.iso» in the example below).
Getting the image file is outside the scope of this guide.
Preparing the Harddisk image
First you need to start DOSBox-X from the command-line, using the newly created win95.conf. This assumes that dosbox-x is in your path and win95.conf is in your current directory.
dosbox-x -conf win95.conf
Then in DOSBox-X you need to create a new harddisk image file, and mount it as the C: drive. We use a 2048MB (2GB) HDD for this purpose, as that is the maximum size for FAT16.
IMGMAKE hdd.img -t hd_2gig IMGMOUNT C hdd.img
You will also need to mount the Windows 95 CD-ROM. There are a few ways of doing so.
Mount as ISO image
If you have a copy of the Windows 95 CD-ROM as an ISO (or a cue/bin pair), you can mount it as follows:
Mount as directory
If instead you have the contents of the Windows 95 CD-ROM copied to your harddisk, in a directory ‘win95’, you can mount it as follows:
Mount from a CD-ROM drive
If your running Windows, you can put the Windows 95 CD-ROM in your CD or DVD drive and directly access it from DOSBox-X. In this example, we assume the optical drive is D: on your windows installation, and your also mounting it as D: in DOSBox-X.
Copying the contents of the CD-ROM
While not strictly necessary, as it is possible to run SETUP.EXE directly from the CD-ROM (as long as you have the CD-ROM automatically mounted in your [autoexec] section of the config file), it is recommended to copy the installation files (contents of the WIN95 directory on the CD-ROM) to your HDD image, as it will prevent Windows 95 from asking for the CD-ROM when it needs additional files later.
XCOPY D:\WIN95 C:\WIN95 /I /E
The files in the above example are copied to the C:\WIN95 directory.
You may want to use «C:\WINDOWS\OPTIONS\CABS» instead, as that is the directory that OEM installs normally use. But if you do, be aware that the installer will attempt to install into C:\WINDOWS.000 as C:\WINDOWS already exists. You will want to change this back to «C:\WINDOWS».
Running SETUP.EXE
We can now run SETUP.EXE.
Now run through the install process, until it reboots and your back at the DOSBox-X Z:\
IMGMOUNT C hdd.img BOOT C:
Save the config file, and at the command-prompt you can type the following to continue the installation process. This is also the command you use, after the installation is finished, to start Windows 95 in DOSBox-X.
dosbox-x -conf win95.conf
Installation Method 2: FAT32 volume
This installation method allows FAT32 volumes, which can be greater then 2GB.
Requirements
-
DOSBox-X 0.83.2 or later, it will NOT work with earlier versions or other DOSBox forks.
-
Windows 95 OSR2 (Win95B) or later CD-ROM image (named «Win95.iso» in the example below).
-
Windows 95 OSR2 (Win95B) or later bootdisk image (named «bootdisk.img» in the example below)
Getting these image files is outside the scope of this guide.
Preparing the Harddisk image
First you need to start DOSBox-X from the command-line, using the newly created win95.conf. This assumes that dosbox-x is in your path and win95.conf is in your current directory.
dosbox-x -conf win95.conf
Then in DOSBox-X you need to create a new harddisk image file, and mount it as drive 2 (IDE primary master). You cannot simply mount it a «C» until the drive is partitioned and formatted.
Technically the FAT32 filesystem is capable of supporting partitions up to 2TB, but the generic IDE driver in Windows 98 cannot handle volumes greater then 128GB.
Larger partition sizes may be possible with 3rd party drivers, but are not covered here.
In later Windows version, starting with Windows 2000, Microsoft won’t let you format a volume bigger than 32GB with FAT32 using its built-in formatting tool, this was presumably to push migrations to NTFS and exFAT.
IMGMAKE hdd.img -t hd_4gig -nofs IMGMOUNT 2 hdd.img -size 512,63,130,1023 -fs none IMGMOUNT A bootdisk.img VER SET 7.1 A:FDISK /FPRMT
If the HDD image you created is larger then 512MB, FDISK will prompt you if you want to enable large disk support.
Confirm that you want to enable large disk support by pressing Y.
Now your in the FDISK main menu, select the following options:
-
option 1 — Create DOS partition or Logical DOS Drive
-
option 1 — Create Primary DOS Partition
Confirm that you want to use the maximum available size for the primary DOS partition by pressing Y.
After this press ESC twice and your back at the MS-DOS prompt.
Do not reset the guest operating system, as FDISK implies.
Format the drive
Next you need to mount the Windows 95 CD-ROM image. This can be in ISO or CUE/BIN format.
And boot from the Windows bootdisk.
When booting from the Windows 95 bootdisk, it should ask if you want to start Windows 95 Setup, or start the computer with or without CD-ROM support. Select to start the computer with CD-ROM support.
Now run the following commands:
D:\WIN95\FORMAT C: /S /V:WIN95
Once the format is completed, you need to reset the guest operating system (Select «Main» followed by «Reset guest system» from the menu bar), such that your back at the DOSBox-X Z:\
Transfer Windows installation files
Once again, you need to mount the harddisk image, but because it is now partitioned and formatted you don’t need to specify the geometry any longer.
IMGMOUNT C hdd.img IMGMOUNT D Win95.iso
You will now copy the contents of the CD-ROM to the HDD image.
XCOPY D:\WIN95 C:\WIN95 /I /E
The files in the above example are copied to the C:\WIN95 directory.
You may want to use «C:\WINDOWS\OPTIONS\CABS» instead, as that is the directory that OEM installs normally use.
But if you do, be aware that the installer will attempt to install into C:\WINDOWS.000 as C:\WINDOWS already exists.
You will want to change this back to «C:\WINDOWS».
Start the installation
Your now finally ready to start the installation process.
VER SET 7.1 C: CD WIN95 SETUP
At the end of the first phase of the installation process, the setup program will reboot DOSBox-X and your again at the Z:\` prompt.
Now close DOSBox-X, and edit the win95.conf config file and add the following two lines to the [autoexec] section at the end:
IMGMOUNT C hdd.img BOOT C:
Start DOSBox-X from the command-line with the following command:
dosbox-x -conf win95.conf
DOSBox-X will start, and the Windows 95 installation will continue.
Booting Windows 95 after installation
After the installation is finished, you can start Windows 95 from the command-prompt with the following command:
dosbox-x -conf win95.conf
Steps to take after Installation
Once Windows 95 is installed, here is some additional software you may want to install or update:
-
Install Microsoft .NET framework version 1.0 and 1.1 (includes Visual C++ 2003 runtime)
-
Install Unofficial Windows 95 OSR2 Service Pack 1.05
-
Install/Update to Internet Explorer 5.5SP2 (rarely needed)
-
Install WinG 1.0 (needed by just a few games, and those games typically include it)
-
Install/Update to DirectX 8.0a (this will also update your video and audio drivers)
-
Install/Update to Windows Media Player 6.4
-
Install/Update to Adobe Flash Player 7.0.73
-
Install Apple Quicktime 5.0.5
-
Install the 3dfx Voodoo 3.01.00 reference drivers
Enabling networking
If you enabled NE2000 support in the DOSBox-X config file, you will probably want to enable TCP/IP.
Go to «Start», «Settings» and «Control Panel» and double-click on «Network».
On the Configuration tab, you should see a «NE2000 Compatible» network adapter listed.
If this is not the case, close the Network settings, and in «Control Panel», double-click «Add New Hardware», and let the wizard detect hardware.
It should find the NE2000 adapter and install the drivers.
Once it is finished, open the «Network» settings again.
In the Network settings, you can optionally remove the «IPX/SPX-compatible Protocol» that was automatically installed, as your unlikely to need it nowadays.
Now click the Add button, and select «Protocol» and click «Add…».
In the «Select Network Protocol» window, select «Microsoft» as the Manufacturer and «TCP/IP» as the protocol, and click OK.
By default it will try to get it’s network configuration over DHCP, if you need to manually specify the settings, highlight «TCP/IP», and click the «Properties» button.
Once your finished, Click OK to close the Network settings window, and the TCP/IP driver will be installed, and Windows will prompt you to restart your computer.
Confirm, and Windows 95 will reboot.
After the reboot you should have working TCP/IP networking.
Emulated video adapter and video mode
The default video adapter that DOSBox-X emulates is the S3 Trio64, which is the best emulated video adapter that DOSBox-X offers, with the widest range of resolutions and colour depths.
A few enhancements have been made, compared to a real S3 Trio64:
-
No real S3 Trio64 was ever produced with more then 4MB video memory, under DOSBox-X you can optionally configure 8MB.
-
The real cards never supported wide-screen resolutions, wide-screen VESA modes can optionally be enabled in DOSBox-X.
However, these enhancements cannot be used in Windows 95 with the S3 video driver due to driver limitations. As such you will be limited to 640×480 in 32bit colour, 1024×768 in 16bit colour or 1280×1024 in 8bit (256) colour.
vmemsize=8 allow high definition vesa modes=true allow unusual vesa modes=true allow low resolution vesa modes=false
Download and extract the latest VBEMP driver package and install the driver from the 032MB directory.
With these settings modes up to 1920×1080 in 32bit colour, or 1920×1440 in 16bit colour are possible.
Note, using the VBEMP driver does have a negative graphics performance impact, which when measured in WinBench96 Graphics WinMark, can be a reduction of up to 59%.
Emulated sound card
The emulated sound card used in this guide is the SB16 Vibra, instead of the default SB16. This is because the SB16 Vibra is a ISA PnP card, and therefore automatically detected by Windows. The emulated SB16 Vibra does not emulate the CQM, instead if uses the same OPL3 emulation as for the regular SB16 model.
However, for Windows 95 it is necessary to force the IRQ to 5 to prevent Window from complaining about a (non-existent) resource conflict.
An optional driver update to 4.38.14 is available on the VOGONS Vintage Driver Library (ignore that the download claims it is for Windows 98, the update is for both Windows 95 and 98).
Enabling General MIDI
If you have a working DOSBox-X General MIDI setup, either emulated or real, you can use that in Windows 95.
Open the «Control Panel», and then double-click on «Multimedia Properties».
Now on the «MIDI» tab, change the «Single instrument» option to «MPU-401 Compatible», and click OK to close the window.
Enabling printing
3dfx Voodoo
The emulated 3dfx Voodoo PCI device is enabled by default in DOSBox-X, but Windows 95 lacks drivers for it by default.
As such it will show in Device Manager with an error.
A driver package is available here (v3.01.00) to enable support.
If for some reason you do not want 3dfx Voodoo emulation, it can be disabled by adding the following lines to your DOSBox-X config:
Hard Disk Read-ahead optimization
In «System Properties», select the «Performance» tab, and click the «File System…» button.
A separate «File System Properties» window will open.
On the «Hard Disk» tab you can specify the Read-ahead optimization.
Based on benchmark results (WinBench 96), it seems that setting this to «None» gives the best performance in combination with DOSBox-X, although the difference is marginal.
This is no doubt because the host system is better at caching then the Windows 98 cache function.
Outstanding issues
-
Resolve «Drive A is using MS-DOS compatibility mode file system»
I installed Windows 95 in DosBox-X by following a guide: http://dosbox95.darktraveler.com/guide%20select.html
NOTE: THIS IS NOT A VIABLE SUBSTITUTE FOR VIRTUAL MACHINES.
It’s pretty cool going back in time once in a while.
To transfer files to Win95 you’ll need WinImage (DL Page) Installed or Portable, DosBox-x has to be closed for it to work.
Open WinImage;
Inside WinBox 95 OSR 2.5 folder drag Win95.img into the WinImage window;
Pick a directory where you want to drop the files and drag them into the WinImage window.
- Addeddate
- 2021-08-16 17:11:20
- Identifier
- windows-95-dosbox-x
- Scanner
- Internet Archive HTML5 Uploader 1.6.4
comment
Reviews
(10)
There are 10 reviews for this item. .
15,936
Views
36
Favorites
10
Reviews
DOWNLOAD OPTIONS
Uploaded by
LividBunny
on
Настройка эмуляции Gravis Ultrasound
Для начала необходимо скачать все файлы, которые потребуются нам для настройки Gravis Ultrasound под DOSBox:
Подготовка
- Скачиваем официальный драйвер: GUS Driver v4.10 и обновление v4.11[1].
- Скачиваем альтернативный набор сэмплов для драйвера: Pro Patches Lite v1.60
- Скачиваем обновление для патча: Update Pro Patches Lite v1.61
- Скачиваем фикс для обновления: FIX Pro Patches Lite v1.61
- Скачиваем утилиту для инициализации и загрузки инструментов в память:loadpats.exe и patches.ini
Установка драйвера GUS для DOS
- В конфиге DOSBoxа включаем эмуляцию Gravis Ultrasound (GUS). См. Dosbox.conf#.5Bgus.5D.
- Распаковываем в папку на жёсткий диск официальный драйвер и устанавливаем его в C:\ULTRASND, запустив «INSTALL.EXE». [2]
- Распаковываем обновление для драйвера и так же устанавливаем.
- В конфиге DOSBoxa, в секции [autoexec], добавляем: SET PATH=%PATH%;C:\ULTRASND\
- Распаковываем loadpats.zip и patches.zip’ в папку C:\ULTRASND.
- В разделе [autoexec] прописываем запуск loadpats.exe.
Установка «Pro Patches Lite»
- Распаковываем куда-нибудь патч, переименовываем эту папку в «PATCHES» и помещаем её в корень смонтированного диска «C».
- Распаковываем обновление для патча и кидаем файлы в папку «PATCHES» с заменой.
- Распаковываем фикс и тоже кидаем все файлы в папку «PATCHES» с заменой.
- Создаём в корне смонтированного диска «C» пустой файл «autoexec.bat».
- Добавляем в секцию [autoexec] конфига DOSBoxa строку: SET PROPATS=C:\PATCHES
- Заходим в папку «PATCHES», запускаем «INSTALL.EXE», жмём «Y» и инсталлируем.
- По окончании установки жмём «CTRL+F9» и перезапускаем DOSBox.
- Для более тонкой настройки звучания запускаем «PATMENU.EXE» и настраиваем. [3]
Примечание: Использование неоригинальных драйверов и патчей может ухудшать совместимость с играми.
Установка Windows 95/98 в DOSBox
В качестве примера работы с DOSBox и, в частности, работы с образами дисков в нем приведем руководство по установке Windows 9x в DOSBox.
Инструкция по установке windows 9x в DOSBox 0.73 (официальная сборка)
Для этого понадобится: дистрибутив Windows95/98, образ загрузочной дискеты с FDISK.EXE и FORMAT.EXE, утилиты bximage и WinImage.
- Утилитой bximage создать фиксированный образ жесткого диска на 504mb. [4][5][6]
- В dosbox.conf:
в разделе [cpu] сменить cputype=auto на cputype=pentium_slow; [7]
в разделе [autoexec] прописать команды монтирования созданного образа жесткого диска и загрузки с образа загрузочной дискеты. [8] - Запустить DOSBox. После загрузки с образа загрузочной дискеты создать раздел на образе жесткого диска (FDISK.EXE) и отформатировать его под fat [4] (FORMAT.EXE. Команда FORMAT C:). Закрыть DOSBox.
- На только что отформатированный образ жесткого диска перенести с помощью WinImage дистрибутив Windows. [9]
- Смонтировать отформатированный образ жесткого диска как C. [10]
- Запустить DOSBox. После загрузки с образа загрузочной дискеты запустить инсталлятор Windows (setup.exe) и начать установку ОС. [11]
- После того как на стадии «перезагрузка компьютера» DOSBox закроется, прописать загрузку DOSBox с диска C. [12]
Инструкция по установке windows 9x в DOSBox SVN Daum
Вам понадобится: сама сборка DOSBox SVN Daum (версия не младше 5.21.2012), образ CD с дистрибутивом win 9x, образ загрузочной дискеты с драйвером сд-рома.
- Запустите DOSBox, и в командной строке наберите imgmake с:\image.img -t hd_2gig. [13] Закройте DOSBox.
- В dosbox.conf:
в разделе [dosbox] установите machine=svga_s3, vmemsize=4, memsize=128;
в разделе [cpu] установите core=dynamic, cputype=pentium, cycles=max, isapnpbios=false;
в разделах [ide, primary], [ide, secondary], [ide, tertiary], [ide, quaternary] установите enable=true;
в разделе [autoexec] пропишите команды монтирования образа загрузочной дискеты, только что созданного образа жесткого диска и образа CD с дистрибутивом win 9x с ключами подключающими их к ide слотам, и загрузки с образа дискеты. [14] - Запустите DOSBox. После того как он загрузится с загрузочной дискеты, перейдите на виртуальный сд-ром и запустите инсталятор windows начав установку ОС.
- После того как по завершению установке DOSBox перезапустится — закройте DOSBox, и в dosbox.conf, в разделе [autoexec] измените команду загрузки с диска a на загрузку с диска c.
Примечания
- ↑ Так как gus_411up на официальном сайте пока битый, то может быть полезной тема на vogons
- ↑ Если GUS Driver v4.11 отказывается устанавливаться из-за конфликта порта, временно отключите в конфиге DOSBoxa эмуляцию Sound Blaster, включая FM-синтез.
- ↑ Если в некоторых играх хрипит музыка, запустите «PATMENU.EXE» и поиграйтесь с настройками. Для устранения хрипов в игре «Z» помогает настройка 4,5,6,B,C секций.
- ↑ 4,0 4,1 DOSBox не поддерживает динамические образы и более 1024 цилиндров (что в bximage = 504mb), а также работает только с fat.
- ↑
bximage v1.32 — Утилита для создания виртуальных жестких дисков и дискет, формата «.img», входит в состав эмулятора Bochs (Также в архиве пустой образ на 504mb, отформатированный под fat).Работа с утилитой:
- Выбрать создание образа жесткого диска «hd» (по умолчанию) или дискеты «fd».
- Выбрать тип образа жесткого диска, фиксированный «flat» (по умолчанию) или динамический «growing».
- Ввести размер жесткого диска в мегабайтах.
- Ввести имя файла образа («c.img» по умолчанию).
- Ввести подтверждение на создание образа «yes» («no» по умолчанию).
- Запомнить количество цилиндров «cylinders».
- ↑
Также, образ жесткого диска для DOSBox размером в 2гб можно создать при помощи сборки HAL9000’s. Для этого в окне запущенного HAL9000’s наберите команду imgmake c:\harddisk_2gb.img -t hd_2gig (образ будет создан на реальном диске C). Структура этого образа будет выглядеть так 512,63,64,1023. - ↑ С «auto» глючит драйвер «S3 Trio32/64 PCI», не устанавливается DirectX, после загрузки Win98SE завершается с ошибкой explorer.exe и ещё несколько компонентов
- ↑
imgmount 2 "путь к директории\образ жесткого диска.img" -size 512,63,16,ХХХ -t hdd -fs none BOOT "путь к директории\образ загрузочной дискеты.IMG"
(2 = master, 3 = slave. В место ХХХ вписать количество цилиндров)
- ↑
При загрузке сторонней ОС под DOSBox 0.73 будут доступны только образы жестких дисков и дискет. К примеру, если вы используете следующие команды:imgmount c "c.img" -size 512,63,16,1024 -t hdd -fs fat imgmount f "d.img" -size 512,63,16,1024 -t hdd -fs fat imgmount d "Gold Soft 7.iso" -t iso -fs iso mount e "l:\" -t cdrom -usecd 0 mount y "DOS-Games" BOOT "DOS622_1.IMG" "DOS622_2.IMG" "DOS622_3.IMG" -l c
Смонтируются 2 образа жестких дисков, образ CD, CD-ROM, директория, 3 образа дискет (которые можно переключать с помощью CTRL+F4) и произойдет загрузка с диска «C». Но, после загрузки ОС будут доступны только образы жестких дисков (как «C» и «D») и дискет (как «a»).
Поэтому для переноса файлов на образ жесткого диска используем WinImage. - ↑ В настройке DOSBox`а после [autoexec] заменить команду:
imgmount 2 "путь к директории\образ жесткого диска.img" -size 512,63,16,ХХХ -t hdd -fs none
на:
imgmount c "путь к директории\образ жесткого диска.img" -size 512,63,16,ХХХ -t hdd -fs fat
(Вместо ХХХ вписать количество цилиндров).
- ↑ Если запустить setup во встроенном ДОСе, повиснет скандиск, а если его пропустить (setup.exe /is), установочные файлы будут копироваться с ошибками.
- ↑ Для этого в настройке DOSBox’а (пункт [autoexec]) заменить команду:
BOOT "путь к директории\образ загрузочной дискеты.IMG"
на:
BOOT -l c
- ↑ На диске c: вашего компьютера будет создан пустой образ жёсткого диска размером в 2Гб с файловой системой fat.
- ↑ Пример команд:
imgmount a "c:\Boot.ima" imgmount c "c:\image.img" -t hdd -fs fat -ide 1m imgmount d "c:\win98se.iso" -fs iso -ide 2m boot -l a
См. также
- Тестирование игр, работающих в Windows 98, запущенной в DOSBox
I needed Windows to run SimTower, so I decided to try getting Win95 to run on DOSBox. The walkthroughs online had some skippable steps and I ran into some problems, and then I got distracted optimizing it.. Anyway, here are my terse, working steps for getting very nice Win95 DOSBox images.
In addition to a Win95 CD ISO and key, you’ll need:
- Empty FAT-16 HDD images
- S3 Video Driver
- DOS 6.22 Boot Disk
I’ve also packed up all of my DOSBox scripting, if you don’t want to copy and paste it from here.
Recommendations
Use Win95C (OSR 2.5)
I saw the fewest unhandled exceptions and other problems with the last Win95 release.
Trim the Win95 install CD
You can delete all of the files on the Win95C CD which aren’t on the Win95A CD to get the latest Win95 fixes, but without all of the optional software (IE, AOL, …). This also eliminated a few exceptions during the first boot. My scripting in Step 1 below copies the correct file list.
Make a Win95 install CD hard drive
I couldn’t mount the Win95 ISO so a DOS boot disk would see it. The walkthroughs copy the install directory to the target hard drive, but that means the target drive must be larger. Instead, I copied my (trimmed) Win95 setup folder to an empty hard drive image and then mount it along with the DOS Boot Disk and target drive to start setup.
Mount a second hard drive for each game
You have to boot from an “img” file in DOSBox to run Win95, but IMG files take up the whole drive size, not just the used space. I didn’t want to installing all of my games in the same Win95 image, which I could break easily, and I didn’t want a huge Win95 starting image to install each game. Instead, you can leave the Win95 image small and mount a second empty drive for each game that’s the right size to install the game to.
DOSBox.conf Template
This is the DOSBox.conf template I used for each step below. Rather than replacing the [autoexec] steps in the same file, making a separate file for each different kind of boot makes it easy to go back and forth again later.
# DOSBox configuration file for Win95 on DOSBox
[sdl]
# output=ddraw seemed to provide the lowest GPU use with the ability to scale the output
# windowresolution=1600x1200 (if double the Win95 resolution, scaling this way looks fine)
output=ddraw
[dosbox]
# 64MB is the maximum for normal DOSBox builds. The S3 Trio 64 is the most modern GPU you can emulate,
# and can run at 1600x1200 or lower resolutions in high color modes.
machine=svga_s3
memsize=63
[render]
aspect=true
[cpu]
# You need to set cputype=pentium_slow or Win95 thinks it's running on a 486 and won't install DirectX 8.
# cycles=max 80% is very fast but keeps my laptop fan from spinning wildly.
core=auto
cputype=pentium_slow
cycles=max 80%
cycleup=1000
cycledown=2000
[midi]
mpu401=intelligent
mididevice=default
[sblaster]
sbtype=sb16
sbbase=220
irq=7
dma=1
hdma=5
[autoexec]
@ECHO OFF
# Drive Geometries - DOSBOX must know the drive geometry to properly install Win95 and boot it
# <Drive Geometries> below
SET Size96MB=512,63,4,780
SET Size192MB=512,63,8,780
SET Size384MB=512,63,16,780
SET Size768MB=512,63,32,780
SET Size1536MB=512,63,64,780
SET Size64MB=512,63,4,520
SET Size128MB=512,63,8,520
SET Size256MB=512,63,16,520
SET Size512MB=512,63,32,520
SET Size1024MB=512,63,64,520
SET Size2048MB=512,63,128,520
# TODO: You must specify your Win95 and Game drive names and geometries.
SET NAME=Win95.img
SET SIZE=%Size256MB%
Step 1: Make the Win95 Install CD Hard Drive image
<DOSBOX.conf template>
...
[autoexec]
# Copy an empty 64 MB FAT-16 HDD image to 'Win95CD.img'
# Mount the image copy and a location with a Win95C (OSR 2.5) CD
imgmount c Win95CD.img -size 512,63,4,520 -t hdd
mount D ..\Sources
# Copy only Win95A setup file names for a small, patched setup.
MD C:\Win95
C:
CD Win95
COPY D:\Win95C\mini.cab .
COPY D:\Win95C\precopy*.cab .
COPY D:\Win95C\win95*.cab .
COPY D:\Win95C\extract.exe .
COPY D:\Win95C\oemsetup.exe .
COPY D:\Win95C\scandisk.exe .
COPY D:\Win95C\scanprog.exe .
COPY D:\Win95C\setup.exe .
COPY D:\Win95C\smartdrv.exe .
COPY D:\Win95C\wb15off.exe .
COPY D:\Win95C\xmsmmgr.exe .
COPY D:\Win95C\*.com .
COPY D:\Win95C\*.bin .
COPY D:\Win95C\readme.txt .
# Copy Drivers
MD C:\Drivers
COPY D:\Drivers\*.* C:\Drivers
ECHO.
ECHO Done. 'Win95CD.img' is now a trimmed Win95 CD image on a hard drive.
EXIT
Step 2: Run Win95 Setup
- Copy a 128 MB+ empty FAT-16 HDD image as ‘Win95.img’ to install the OS to.
- Get a DOS 6.22 Boot Disk to boot from to start setup.
<DOSBox.conf template>
...
[autoexec]
...
<Drive Geometries>
# TODO: Set the right img file name and size here
SET NAME=Win95.img
SET SIZE=%Size128MB%
ECHO.
ECHO 2. Boot DOS 6.22 disk and run Win95 setup from HDD
ECHO ==================================================
ECHO.
ECHO.
ECHO Inject latest INF into Win95 CD
imgmount d ..\Sources\Win95CD.img -size %Size64MB% -t hdd
mount e ..\Sources
COPY /Y E:\*.INF D:\Win95\
MOUNT -u E:
MOUNT -u D:
ECHO.
ECHO Inject setup command into boot disk
imgmount a ..\Sources\622c_Scratch.img -t floppy
ECHO D:\Win95\SETUP.EXE /im /is /IW > A:\autoexec.bat
MOUNT /u A:
ECHO.
ECHO Mount boot disk, hard drive, and Win95 install HDD
imgmount 0 ..\Sources\622c_Scratch.img -t floppy -fs none
imgmount 2 %NAME% -size %SIZE% -t hdd -fs none
imgmount 3 ..\Sources\Win95CD.img -size %Size64MB% -t hdd -fs none
ECHO.
ECHO Boot from boot disk; autoexec.bat will run Windows setup
ECHO [D:\Win95\setup.exe /im /is /IW]
boot -l a
During setup, make sure to pick ‘Yes’ if asked whether to detect hardware and check ‘Sound …’ to find the sound devices. Setup is otherwise very straightforward.
3. First Win95 Boot
<DOSBox.conf template>
...
[autoexec]
...
<Drive Geometries>
# TODO: Set the right img file name and size here
SET NAME=Win95.img
SET SIZE=%Size128MB%
# Mount new hard drive
imgmount 2 %NAME% -size %SIZE% -t hdd -fs none
# Mount source drive (for driver install)
imgmount 3 ..\Sources\Win95CD.img -size %Size64MB% -t hdd -fs none
# Boot from Windows (first boot)
boot -l C
During First Boot:
- You’ll see one unhandled exception during Control Panel setup
- Set your Time Zone
- Cancel Printer setup
- Clean up desktop icons
- Install Graphics Driver
- Right-click Desktop, click Properties
- In the ‘Settings’ tab, click ‘Advanced Properties’
- In ‘Adapter’, click ‘Change’
- ‘Have Disk’ -> ‘Browse’ -> D:\Drivers -> OK
- Select ‘S3 Inc. Trio32/64 PCI’ and click OK
- Shut Down
- Reboot again
- Confirm sound works
- Uncheck the checkbox for hints on startup
- Shut Down
- Make a ZIP of your (tiny!) blank Win95 image!
Step 4: Copy a Game
- Copy an empty FAT-16 HDD image for each game, with enough space to hold the setup files and the installed result.
<DOSBOX.conf template>
...
[autoexec]
...
<Drive Geometries>
# TODO: You must specify your Win95 and Game drive names and geometries.
SET NAME=Win95.img
SET SIZE=%Size256MB%
SET GAME=Game.img
SET GAMESIZE=%Size64MB%
# Mount the (scratch) Boot Disk, Hard Drive, Game Drive, and Host Folder
imgmount a ..\Sources\622C_Scratch.IMG -t floppy
imgmount c %NAME% -size %SIZE% -t hdd
imgmount d %GAME% -size %Size64MB% -t hdd
mount e .
- Install the game on D:\
Note: If the game adds to the registry or C:\Windows, you’ll have to boot the matching Win95.img for it to work later. You can save the Win95.img you installed the game with and go back to the fresh one to see if the game works.
- ZIP the Game image (and the Win95.img, if altered) to store the game compactly.
Step 4: Play a Game
<DOSBOX.conf template>
...
[autoexec]
@ECHO OFF
<Drive Geometries>
# TODO: You must specify your Win95 and Game drive names and geometries.
SET NAME=Win95.img
SET SIZE=%Size256MB%
SET GAME=Game.img
SET GAMESIZE=%Size64MB%
# Mount hard drive and game drive to boot
imgmount 2 %NAME% -size %SIZE% -t hdd -fs none
imgmount 3 %GAME% -size %GAMESIZE% -t hdd -fs none
# Boot from Windows hard drive
boot -l C
…and you’re done!
Troubleshooting
Win95 is showing a messed up screen on boot or running ScanDisk forever
This happens to me when I haven’t shut down Win95 properly. You can get your original Win95.img from your ZIP to go back to a working install.
Windows Setup Error “SU 0013”
This error blocked me in my previous walkthrough. It happens when you mount the hard drive image to write files to rather than to boot to, or you don’t specify the hard drive geometry. If you copy the Win95 setup files to the hard drive you’ll install to, you need to close DOSBox, and start again mounting the drive “boot style” before you run setup.exe.
# Mount 'copy files style'
imgmount c Win95.img -size %Size256MB% -t hdd
# Mount 'boot style'
imgmount 2 Win95.img -size %Size256MB% -t hdd -fs none
Note that to boot, you must mount to an IDE position number instead of drive letter (2 is ‘Primary Master’), you must provide the geometry (-size), and you must not let DOSBox try to read the file system (-fs none).
Opening Control Panel crashes
I saw this, but only for the first three or so boots of Win95. I know, weird. Anyway, try another reboot and it may work after that.
Bonus: Automating Win95 Setup
You really only need to install Win95 a few times (maybe once on a 256 MB, 512 MB, and 1024 MB hard drive) so you have template to use for various games. As long as you get the installs right and make backups of the images, you’re done.
However, in a past life I automated more modern Win95 setups, so I couldn’t help but look into how Win95 installs are automated.
There’s a tool on the Win95C CD in admin\nettools\bsetup called batch which will ask you for the answers to most questions setup.exe asks, and then write out a BSETUP.INF file you can use to automate. Pass this as an argument to setup.exe, and you’ve got an automated install:
D:\Win95\setup.exe /im /is /IW D:\Win95\BSETUP.INF
Here is the one I ended up with. I figured out everything except how to get it to look for a sound card, so I wasn’t able to leave it fully automated (and, it got stuck on the exception setting up the Control Panel also). [If anyone reading this knows how to do that, I’d love to know!]
Some settings in the INF and what they do (found by changing UI in the batch tool and re-exporting):
| Key Under [SETUP] | Purpose |
|---|---|
| Express=1 | Unattended [0 = Stop at every screen] |
| InstallDir=“C:\WINDOWS” | Install Directory |
| EBD=0 | Prompt to create (emergency) boot disk |
| ChangeDir=0 | ? |
| OptionalComponents=1 | Install any Optional Components |
| Network=1 | Configure Networking per below section |
| System=0 | ? |
| CCP=0 | ? |
| CleanBoot=0 | ? |
| Display=0 | ? |
| PenWinWarning=0 | “Enable PenWindows warning” [?] |
| InstallType=3 | Whether install is Disk or CD, upgrade or clean |
| DevicePath=0 | “Search source folder for devices” |
| TimeZone=“Pacific” | Time Zone to set on first boot |
| Uninstall=0 | Whether to save uninstall information |
| VRC=0 | “Auto-answer ‘No to all’ to version conflict dialogs” |
| NoPrompt2Boot=1 | “Automatically reboot PCI and PnP machines during setup” |
| ProductKey=XXX | Product Key to pre-fill in UX |
| ProductType=1 | OEM version indicator; only needed in separate MSBATCH.INF |
| [Printers]\r\n | (Separate from [SETUP]) Don’t prompt to install a printer |