use bochs

Or QEMU

It's DOSBox, not 95Box 😉

Don't let the others disencourage you! Try it out (maybe use HAL's CVS-Build instead of the official ones) and have fun. Experimenting is everything!

But you better don't ask these questions HERE because Windows 95 is not officially supported. Contacting HAL via PM might be helpful as he can certainly answer most of your questions.

Try all you want, just don't bitch here (or badmouth DOSBox) when it doesn't work .

Hey, it works! It did fine in normal .72.

In case anyone else needs it:
Since Dosfreak removed his guide, I decided to remove my miniguide. See the next page for details on said proper guide.

Now, to get Sonic CD working 😁

Also, can Windows 95 find a CD Drive? It doesn't come up anywhere as far as I can tell.

You'll have to use a CD emulator.

Also instead of using bximage you can use HAL9000's MegaBuild of DOSBox which includes IMGMAKE (HD image creation utility).

I'd stick with DOSBox 0.72 or HAL9000's MegaBuild if you want to run Windows 95a/b since the latest CVS builds of DOSBox are more unstable for guest Windows 95a/b.

Hmmm, Scratch that the latest CVS is fine as long as you install the latest S3 Win95 drivers you should be good to go. (and use pentium_slow for cputype).

If you still have instability then just use the standard video driver (no video driver) and it should be pretty stable.....at only 16 colors of course.

DosFreak wrote:

You'll have to use a CD emulator.

Also instead of using bximage you can use HAL9000's MegaBuild of DOSBox which includes IMGMAKE (HD image creation utility).

I'd stick with DOSBox 0.72 or HAL9000's MegaBuild if you want to run Windows 95a/b since the latest CVS builds of DOSBox are more unstable for guest Windows 95a/b.

Sorry for asking a very broad question, but how would I use and which one would I use for a CD emulator?

On a side note, DOSBox doesn't seem to have the 100% CPU usage issue that other virtual machines have.

You'd have to install Daemon Tools/Virtual CloneDrive/etc etc and copy an iso image of the CD to the hard drive image and mount it from there.

Also you'll have to use the older versions of those tools since the latest versions do not support Windows 9x anymore.

DOSBox doesn't use 100% of the CPU because it tries to give only as many cycles to the programs as they need (cycles=auto).

Other VM's mostly virtualize the processor instead of emulating it.

Dang...Sonic CD is a 750MB bin/cue (Mixed mode CD). Does that mean I can't mount it until DOSBox supports images over 512MB? Or does it already, and I just misheard?

Wait, can I mount a second HD image into Windows 95? I could probably split the the game's data between the two drives.

You can create 2gb images with IMGMAKE included in HAL 9000's DOSBox build. These images can also be used with the DOSBox CVS.

Excellent! I'll report back if Sonic CD works. Thanks for all of your help!

Dos4dinner,

Thank you for creating this post. I've been looking to do this for a long time but haven't gotten further than creating the image file.

Here's what I've done so far......

Successfully created a windows95 image via bximage and bochs. I can now run win95 in bochs. My image file is called c.img. It is currently located in my bochs directory.

I open up dosbox and type in "boot -l c" and I get this message "Unable to boot off drive C".

Do I need to create a subfolder somewhere and copy c.img to it?
Do I need run other commands prior to "boot -l c"? Such as mount c or something?
Would you mind giving me the step by step commands that you typed in dosbox to boot the c.img file?

I'm trying to run casino verite blackjack on my nokia n810 and the program only runs on windows 95 and up.

Any help would be greatly appreciated. I'd love to finally get this working.
😕 😕

You need to run "imgmount c c.img" and then "boot -l c".

Thanks for the reply dosfreak,

Here's what I did. Copied c.img into a subdirectory c:\win95\c.img
I then typed the following into dosbox:

"mount d c:\win95"
"d:"
"imgmount c c.img"
"boot -l c"

After that last command I get a message saying:
"Disk I/O error Replace the disk, and then press any key"
"
I must be missing a step here. Where should I place the c.img file. If I open up dosbox and immediately type "imgmount c c.img" I get a message "the image must be on a host or local drive"

Did I miss something?

LuckyCharms21 wrote:

Thanks for the reply dosfreak, […]
Show full quote

Thanks for the reply dosfreak,

Here's what I did. Copied c.img into a subdirectory c:\win95\c.img
I then typed the following into dosbox:

"mount d c:\win95"
"d:"
"imgmount c c.img"
"boot -l c"

After that last command I get a message saying:
"Disk I/O error Replace the disk, and then press any key"
"
I must be missing a step here. Where should I place the c.img file. If I open up dosbox and immediately type "imgmount c c.img" I get a message "the image must be on a host or local drive"

Did I miss something?

You don't need to mount D:. Just mount it directly (assuming you already used fdisk and format):
imgmount c C:\win95\c.img -fs fat
Then boot it. Note that once it's booted, you will have no other access to any other drives except the image.

Ok, so I opened up dosbox and typed the following:

imgmount c C:\win95\c.img -fs fat
boot -l c

I then get the following message:

"Booting from drive c......"
"Disk I/O error"
"Replace the disk, and then press any key"

Again, thanks for helping....what should I do next?

Forgot to add this....

I did use fdisk and format but only during my setup in bochs. Do I need to do this in dosbox as well?

(Assuming DOSBox says that it successfully mounted) Maybe. DOSBox is acting like it can't be booted, which means it probably isn't formated.

You could try fdisking/formating again. See the official guide Sample usage of a harddisc image in DOSBOX for properly setting a hard disk image. Also, normal DOSBox can only use 512MB images (Although I'd create a 500MB image, just to be safe--my first 512 image didn't work.)

Speaking of Normal DOSBox, it can't boot the 2 gig image I created now that Windows 95 is on it. HAL's can, but normal .72 won't--it just freezes. Is this because I told fdisk to use fat16 instead of fat32?