Both "int" and "raw" launch properly, but "bigint" gives the same ol' "Invalid Opcode" loop.
VirtualBox doesn't have an explicit setting for AHCI versus IDE, but you can get the same effect through what type of storage controller you add to your virtual machine; if you want it handled as AHCI, you add a SATA controller, and if you want IDE, you add an IDE controller. The VirtualBox BIOS has no "Setup" interface of which I'm aware. Boy, I wish it did! Sent with ProtonMail Secure Email. ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ On July 31, 2018 4:42 AM, Eric Auer <e.a...@jpberlin.de> wrote: > Hi! > > > To further isolate the Invalid Opcode issue, I extracted the floppy > > image (FDBOOT.IMG from the ISOLINUX folder) from the ISO and booted > > it as a floppy disk in VirtualBox which launched the installer > > flawlessly. > > Thanks for the testing! So apparently NOINVLPG would not have helped. > How about the memdisk "int" instead of "bigint" or "raw" options? > > Does VirtualBox have options to select AHCI versus IDE or to change > the int 15 memory access styles? > > Cheers, Eric > > > --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- > > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > > Freedos-user mailing list > Freedos-user@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/freedos-user ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
