Dec 4, 2015 - Download my Win 95 AC97 driver from but do *NOT* run it. Simply right click and use. VirtualBox QEMU Manager VMWare Virtual PC 2007 Help/FAQ Website updates/news. Windows 95 C with VBEMP 9x display drivers installed to support high color depth. Windows NT 4.0. You can download Windows 7 straight from Microsoft here. Windows ME (32 bit) Notes: Windows ME with VBEMP 9x display drivers installed to.
It’s been much longer between my posts than I’d like. We had a re-org at work a little while back and now I’m up for another position that I’m waiting to hear on. It’s like a desktop administrator position but more. I have a bit of a nostalgia bug and I found my old copy of Windows 95 a while back.
I’ve been wanting to install it in a VM so I could play around with it again and remember old times. I made an ISO from it, mounted it, and attempted an installation. I forgot back then that CD’s weren’t bootable and I didn’t still have the boot disk. I do, however, still have my old Win98 boot disk. I think it has corrupted, however. It wouldn’t matter tho, I don’t think, as I only have an external floppy drive and the software back then didn’t support USB!
So I looked on the net and found some boot disk images. I also did a quick google search to see how complicated it was for other folks. There sure are a lot of folks that had a lot of problems!
I found it to be farely simple, to be honest. I did get a few tidbits of info that helped me along in my adventure to figure it out. I’ll have several links at the end of the post. But here’s how I did it: I’m running VirtualBox 4.1.2 r73507 on Windows 7 Ultimate, 64-bit I have Windows 95 “A” (although the boot disk I found will work for either, I believe) Boot Disk and Installation CD.
If you don’t have the original boot floppy you’ll need to get a copy of the boot disk image from:. Make an ISO of your Win95 CD and save it somewhere. You can mount this directly in VirtualBox which is nice. If you don’t want to do it that way, you can make another virtual drive and mount it in MagicDisc (another free app). An alternative is to create a single ISO that includes the boot disk and Win 95.
I’ve outlined that below, or you can skip to step 4. You can also burn both the boot disk and the Win 95 files to the same disc (but this as issues) to make one, bootable CD!. To do this in ImgBurn launch the program and select “Write files/folders to Disk”.
On the window that comes up, the left space is where you add the folders and files (don’t forget both, they are separate icons) from the Win 95 CD. The icons are have magnifying glasses over a sheet of paper and one over a folder. I added the files and then each of the folders individually so that they will be at the root of the file structure. Also add the program xcopy!. Click on the “Advanced” tab on the left and then on “Bootable Disc” below that. Check the box “Make Image Bootable”. Emulation Type: Floppy Disk 1.44MB.
Boot Image: add the.img file you downloaded from above. That should be it for your discs.
I highly recommend having two ISO’s and just mounting them in VB, but hopefully the steps above will help you if for some reason you can’t do that VirtualBox Setup. Started off by creating a new 5GB VDI Hard disk and making it Windows 95. I configured mine to use 512MB of RAM. BEFORE LAUNCHING THE NEW DISK you need to change some configuration. Right click on the new VDI in your list and go to Settings. Select System on the left and you can configure your RAM size if you didn’t already. Also change the Boot order so that the CD/DVD-ROM is first.
Click on the Acceleration tab and UNCHECK “Enable VT-x/AMD-V”. If you don’t do this step, when you go to boot after installation of Win 95 you’ll hang at a black screen.
Click on Storage on the left so we can add the ISO’s we’ll be using. Click the icon that has a plus sign over a single disk (not a disk stack) to add a CD/DVD Device. Add the Bootable image FIRST so that it is the primary slave (which is what it will try to boot from). Then add the Win 95 installation iso. Click OK to save the settings.
Launch the new VDI!. PAY ATTENTION to the initial boot screen.
It’s going to list two drives right above the A: prompt. The first drive letter is your Win 95 installation CD (Mine is set to R: ). The boot disc is automatically mounted to the A: drive. Since this is a brand new VDI there is no partitioned drive. Win95 setup isn’t capable of creating one so you have to do that. Type format c: at the prompt and hit enter.
Type Y for yes when it asks if you’re sure and hit enter. You can enter anything for the Volume label.
The Win95 setup doesn’t mount your CD drive after you reboot, thus the continued setup for Windows can’t complete because it cant find the Win95 CD. You’ll get a bunch of dll errors.
The OS will still boot but it’s a lot of errors. To fix this we need to copy the Win95 CD to the C drive so we can access it later. From the A: prompt type xcopy R: C: WIN95 /S. Remember to substitute R: for the drive letter that yours is.
Now switch to your C: drive to run the setup. Type C: and hit enter. Type cd win95 and hit enter. Type setup and hit enter.
It will tell you it has to do a scan before it can install, hit enter to proceed. You should now be in the setup wizard for Win 95. I’ll trust you can follow the prompts from here. When it prompts you to restart after install is a good time to click on “Devices” and unmount your bootable iso. When I restarted after that I got a boot failure, but I just used “ Reset” in the Machine menu to reset the box and then it was fine. It should then proceed with the usual setup and ask you a bit of input. After another reboot you should be all set to use Windows 95!
Getting on the Internet I wasn’t sure if this would work but I was easily able to get on the internet. The bad part is most pages are using code that Internet Explorer 4 can’t render. However, if the site still uses just basic HTML you should be able to render it fine. Please note you’ll have wanted to install the virtual networking driver when you initially installed VirtualBox on your machine. Launch the “The Internet” icon. Select to connect via your LAN.
Use DHCP. Your DNS server will be your router IP. Your Gateway will be your router IP. Save it and reboot like it says One “old school html” page you can load to try it out is And that’s it! I did a lot of trial and error trying to figure out the best way to make the ISO’s and mount. It wasn’t until I got the xcopy idea that it all became beautifully simple. But if I had looked in the first place, I would have seen xcopy was part of the downloaded boot image all along: It was fun though!
Here are the links where I got a few tidbits of info to help me along: (this is really the only one that helped me) (sort of, it pointed me in a different direction which made me realize I needed to pursue a different path) (I tried installing DOS 7.1 first but didn’t want to mess around with mounting my drive). Thank you very much! This information helped me and the company where i work alot! We have some control units with technical problems for a hydroelectric plant in Colombia. And the only way to recover them is through windows 95, this tutorial was really helpful.
For the record i had two problem, first the same problem of bonezore, but i solved it with your reply and second was that i couldnt find the install file inside the C druve after i coppied it, problem was i had put it in 2 win95 folders, the root was win95/win95 hehe but i solved it. After you create the VM (and with it shutdown) you want to right click it from the VM Manager, go to Settings, and then the Storage tab. Select the “Controller: IDE Controller” line and then click the disk with the plus sign to add a CD/DVD. Select Choose Disk and then browse to the ISO file.
It should then be highlighted automatically and on the right side, under attributes, change the drop down. If it’s not an option in the dropdown, that means one of the other disks/drives in your storage tree is already set to primary slave, you need to find it and change it to something else.
Just like on a physical PC, you can only have one device as each config. Hope that helps.
Hey there, I'm a newb to VirtualBox, and so you'll have to pardon me if this question is dumb, ignorant, already asked (though I couldn't find it after looking at the 10 most recent pages of this forum), etc. In fact, when I registered for this forum so I could ask this question, I began to think that using VB is a bit beyond my abilities. I didn't even understand how to find out what VBox Version I'm using (OSE Debian?
I haven't a clue what any of those are, and put 'OSE other' finally. Isn't it enough that I know I'm using version 4.0.4 r70112?) Anyhow, here's the problem: I'm trying to use VB to run Windows 95 on Windows 7 host computer using an ISO file I downloaded. I open up the VirtualBox Manager and hit run (or double-click 'Windows 95,' as I've named it, in the left window panel) and a dos window comes up with a list of operating systems to choose from. I move the cursor down to number 5, Windows 95. That's where I'm stuck. The WIndows 95 OS does not start running. If I hit Enter, some info about the device and driver comes up, followed by 'unidade especificada n =o e valida' - something to the effect of unit specified not valid, I'm guessing - and a prompt: A: So what exactly am I supposed to be doing at this point to bring Windows 95 up on my virtual machine?
All I want to do is play an old computer game, and this is becoming a lot more complicated that merely using an emulator to run rom files. I don't know if it was necessary in this version for me to do - as a lot of the ins and outs of this technical stuff goes right over my head - but I went under SettingsStorage and, used the Add CD/DVD for the ISO file, and Add Hard Disk for the VDI file so that those two files are now listed under IDE Controller Panel. However, this had no effect on making it work. What am I doing wrong?? Thanks in advance for any info you can provide.
(If any of the above doesn't make sense - and no one would blame you if you thought that - screenshots can be provided to clarify the matter) Posts: 9 Joined: 17. Apr 2011, 09:14 Primary OS: MS Windows 7 VBox Version: OSE other Guest OSses: Windows 95.
My understanding way back then was the product key is what you really purchased to be able to run the product. If you still have a valid key and can find the OS then it should be fine to use. However that may prove hard to do since it has long past been retired. I would be careful downloading anything from the web though. It would be a lot safer asking some of you friends if they still have the original install CD.
You might even be able to ask Microsoft if you can still purchase the CD. They did have them available for a while but here again you may not succeed and even if you do the OS will not run properly in a virtualizer as it was based on DOS and is not supported. Site Moderator Posts: 34374 Joined: 6. Sep 2008, 22:55 Primary OS: Linux other VBox Version: OSE self-compiled Guest OSses:.NIX. Thanks for the info, Perryg. I see in the VirtualBox User Manuel it says, DOS / Windows 3.x / 95 / 98 / ME Limited testing has been performed. Use beyond legacy installation mechanisms not recommended.
No Guest Additions available. Again, this is another place where the terminology goes over my head. According to searchdatacenter.com, 'legacy installation mechanisms' means 'legacy applications and data are those that have been inherited from languages, platforms, and techniques earlier than current technology.' OK, I think I understand that, but I'm not sure exactly what that means in the above context. If Windows 95 will have as much trouble working in VirtualBox as you say, another possibility for the game I'm trying to play would be to install a later OS, such as Windows 2000 or XP and hope my game will play on it. Posts: 9 Joined: 17.
Apr 2011, 09:14 Primary OS: MS Windows 7 VBox Version: OSE other Guest OSses: Windows 95. Thanks again for the info. Using the Windows XP iso, I somehow managed to make it work (after initially having the same problem - it just giving me a OS list to chose from rather than just booting up the OS), miracle of miracles. Now I have a different problem: the guest machine doesn't recognize the game disc in the E drive (the host computer does, so I know the disc is being read). On the guest computer, it reads NOVO (E:) and has these folders listed as being on that drive: HD OEMLogo PMagic8 Powertoys Util Win95 Win98 WinMe It's very frustrating to win one major battle and then lose the next! BTW, I can get rid of NOVO by 'ejecting' the 'disk' though it still won't recognize that there's actually a disk physically present in the E drive.
Posts: 9 Joined: 17. Apr 2011, 09:14 Primary OS: MS Windows 7 VBox Version: OSE other Guest OSses: Windows 95.