-
Notifications
You must be signed in to change notification settings - Fork 40
Open
Labels
bugSomething isn't workingSomething isn't working
Description
Checklist
- I have searched the issue tracker and was unable to find an open or closed issue matching what I'm seeing.
- (If the issue occurs AFTER or DURING Windows 9x's hardware detection phase) I have tried to install with
Skip legacy non-PnP hardware detection phaseto[OFF]and the issue still occurs. - (If the issue occurs AFTER or DURING Windows 9x's hardware detection phase) I have tried to install with the integrated driver library set to
[OFF]and the issue still occurs. - I understand that support is provided voluntarily for free, and that the author is not Microsoft and can/will probably not fix bugs in the operating system code itself. I also understand that it is impossible to support every single hardware combination out there.
What happened?
If you have a huge environment (for example if using something like mise, which likes to store internal data in environment variables), the msdos.exe tool explodes with the error too many environments - This is even documented in msdos.txt!
It seems it can be fixed as documented in the msdos.txt: Add -e in the 2 subprocess.run lines: msdos_exe, '-e', regedit_exe
Linux dmesg output
No response
Target Motherboard, CPU and RAM
No response
Target GPU and Sound card(s)
No response
Target Storage Devices
No response
Boot method
ISO image
Reference image
None
Additional context
No response
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
bugSomething isn't workingSomething isn't working