- #WHERE CAN I DOWNLOAD WINDOWS 3.1 ISO FOR VIRTUALBOX INSTALL#
- #WHERE CAN I DOWNLOAD WINDOWS 3.1 ISO FOR VIRTUALBOX DRIVER#
- #WHERE CAN I DOWNLOAD WINDOWS 3.1 ISO FOR VIRTUALBOX TORRENT#
I just noticed that it saved with a different virtualDev setting.
#WHERE CAN I DOWNLOAD WINDOWS 3.1 ISO FOR VIRTUALBOX INSTALL#
my sound config is like this now, but SB16 install still shows "Wrong base i/o address or audio card is not detected at 220H." error message.
and I'm going to test now something I've read there: I need to put the sound.virtualDev = "sb16" config in there.
#WHERE CAN I DOWNLOAD WINDOWS 3.1 ISO FOR VIRTUALBOX TORRENT#
I downloaded those same packages, only through torrent instead of http. I added those "sound." configs you said on my. I only did this because I wanted to run an old Windows 3.11 game that came with a book by Scott Flansburg called "The Human Calculator." Unfortunately, despite my efforts, I cannot make this (poorly written) game work in VMWARE DOS or DOSBOX. Is MIDI even supported by VMWARE 6 emulation?Īny comments or suggestions about getting MIDI to work? The only problem I have is that I do not have MIDI sound. After a successful installation and reboot, both DOS and Windows applications will have sound. This installer will modify your autoexec.bat and the Windows 3.11 win.ini and system.ini files.
If you did everything correctly, you should not encounter a "Wrong Base I/O" error message. Go to the Sound Blaster folder and run the DOS install.
#WHERE CAN I DOWNLOAD WINDOWS 3.1 ISO FOR VIRTUALBOX DRIVER#
Boot to DOS, go to the CD-ROM (ISO image) - of course, I am assuming you are using device=aoatapi.sys (file found in above link) for your cdrom driver todetect = "FALSE" <- MY FUJITSU LIFEBOOK. Sound.fileName = "SigmaTel Audio" <- NOTE THIS IS SPECIFICALLY FOR iso file (and have it mount with your emulation) First download the SB16 driver from one of the following sites (additional tips may be found as well): Adding sound to a DOS/Windows 3.11 emulation is fairly straight forward. mpack Site Moderator Posts: 34948 Joined: 4.Hello folks, this topic seems to have been almost hashed to death so I thought would would throw in my experience. Unless we know the reason for the failure then everything here is speculation: we have no strong evidence that VBox rejects fully legal ISO images, and in fact from the small number of complaints relative to the number of users I suspect the problem is not with VBox, it's with some errant ISO-generator.Īs for an ISO being a raw dump of a CD or DVD - well of course, but the ISO 9660 specification defines headers with specific ranges for legal values in the fields in those headers, likewise with various extensions built on the original standard.Ībout the only way to resolve this would be to get an example of a "bad" ISO into the hands of the devteam - if someone could reference an ISO that could be downloaded from somewhere then that would help a lot. I'm not saying that the ISO images have been corrupted, I'm suggesting that they may be technically illegal - and were so before the MD5 sum was calculated. Dec 2009, 23:23 Primary OS: MS Windows Vista VBox Version: OSE other Guest OSses: Win 2000/XP/2003/Vista/2008/Win7/2008R2 There are other dumped-disc image formats which do have a format with their own specific metadata.
I say this with a wee bit of knowledge on this subject, having written a shipping device driver which mounts. They're just a raw sector-by-sector dump of the disc contents. ISO-file-specific metadata (not to be confused with the metadata of the 9660/UDF/etc file system stored on the disc) as some previous users have suggested. Maybe I'm wrong here, but as far as I know. We tested with this same ISO using VirtualBox 3.0.8 and it worked just fine. ISO file itself is indeed good) and VirtualBox 3.1.0 throws an error. ISO file from Microsoft whose MD5 hash verifies - so the. Point the guest CD drive to an OS install. We are also seeing this same issue with VirtualBox 3.1.0.