Add npm run qemu / qemu:cdrom scripts#368
Merged
Merged
Conversation
Boots images/windows95.img with the same device set the image was configured against: - ne2k_isa at iobase=0x300, irq=10 (matches the NE2000 ForcedConfig in SYSTEM.DAT and v86's port 0x300 / PIRQA->IRQ10) - vmport=on so VBMouse picks up the VMware backdoor for absolute pointer - sb16, pentium, acpi=off as before qemu:cdrom forwards an ISO path: npm run qemu:cdrom -- /path/to.iso
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds two convenience scripts for booting
images/windows95.imgin QEMU with the device set the image is actually configured for.npm run qemune2k_isa,iobase=0x300,irq=10— matches the*PNP80D6ForcedConfig baked intoSYSTEM.DAT(and v86, whose ne2k sits at port0x300with PIRQA→IRQ 10). Usingne2k_pcihere makes Win95 pop the "NE2000 Compatible (0000) is not working properly" dialog.vmport=on— explicit so VBMouse's VMware-backdoor detection finds it (Found VMware protocol version 6/VMware integration enabled); QEMU's monitor then shows* vmmouse (absolute)as the active pointer.-drive ...,format=rawinstead of-hdato drop the "probing guessed raw" write-restriction warning.npm run qemu:cdrom -- <iso>Same boot plus
-cdrom <iso>, e.g. for mounting an installer ISO as D:.