[GH-ISSUE #12] [F.Req] DOSBOX-X Support/How-to. #12

New issue

Closed

opened 2026-03-03 18:48:09 +03:00 by kerem · 4 comments

kerem commented

2026-03-03 18:48:09 +03:00

Owner

Originally created by @yum13241 on GitHub (Sep 10, 2024).
Original GitHub issue: https://github.com/oerg866/win98-quickinstall/issues/12

Their official guide, method 1, cuz it's supposed to be bootable lol won't work, imgmount A -bootcd D* won't work, saying it cannot create a drive from the file.

DOSBOX-X is using floppy emulation boot, as it does not support otherwise AFAIK.

*D:\dosflop.img / any other .img file in the ISO.

DOSBOX-X Log: https://privatebin.net/?87248ebd3e8de583#HwvfGhK3LnLXKjmMmh78cYNEJnGpB8446jk8Y1xZHvu4

Important lines:
LOG: Rejecting image, boot sector has weird values not consistent with FAT filesystem

/usr/include/c++/14.1.1/bits/stl_vector.h:1130: std::vector<_Tp, _Alloc>::reference std::vector<_Tp, _Alloc>::operator[](size_type) [with _Tp = std::__cxx11::basic_string<char>; _Alloc = std::allocator<std::__cxx11::basic_string<char> >; reference = std::__cxx11::basic_string<char>&; size_type = long unsigned int]: Assertion '__n < this->size()' failed.

^C^CAborted (core dumped)

EDIT [2024-9-16]: Changed the link, old one was dead.

Originally created by @yum13241 on GitHub (Sep 10, 2024). Original GitHub issue: https://github.com/oerg866/win98-quickinstall/issues/12 Their [official guide, method 1, cuz it's supposed to be bootable lol](https://dosbox-x.com/wiki/#Guide:Installing-Windows-98) won't work, `imgmount A -bootcd D`* won't work, saying it cannot create a drive from the file. DOSBOX-X is using floppy emulation boot, as it does not support otherwise AFAIK. *D:\dosflop.img / any other .img file in the ISO. DOSBOX-X Log: https://privatebin.net/?87248ebd3e8de583#HwvfGhK3LnLXKjmMmh78cYNEJnGpB8446jk8Y1xZHvu4 Important lines: `LOG: Rejecting image, boot sector has weird values not consistent with FAT filesystem` ```/usr/include/c++/14.1.1/bits/stl_vector.h:1130: std::vector<_Tp, _Alloc>::reference std::vector<_Tp, _Alloc>::operator[](size_type) [with _Tp = std::__cxx11::basic_string<char>; _Alloc = std::allocator<std::__cxx11::basic_string<char> >; reference = std::__cxx11::basic_string<char>&; size_type = long unsigned int]: Assertion '__n < this->size()' failed.``` `^C^CAborted (core dumped)` EDIT [2024-9-16]: Changed the link, old one was dead.

kerem

2026-03-03 18:48:09 +03:00

closed this issue
added the
documentation
label

kerem commented

2026-03-03 18:48:10 +03:00

Author

Owner

@oerg866 commented on GitHub (Sep 22, 2024):

It seems DOSBOX expects the boot floppy image to be a valid FAT image which makes no sense because a disk is just a bunch of sectors and you can have arbitrary code and data in there... Our boot sector is custom and loads the kernel directly from the image, so obviously that won't work if it expects a FAT12 file system.

Please try to boot from dosflop.img with the ISO loaded, maybe that works?

@oerg866 commented on GitHub (Sep 22, 2024): It seems DOSBOX expects the boot floppy image to be a valid FAT image which makes no sense because a disk is just a bunch of sectors and you can have arbitrary code and data in there... Our boot sector is custom and loads the kernel directly from the image, so obviously that won't work if it expects a FAT12 file system. Please try to boot from dosflop.img with the ISO loaded, maybe that works?

kerem commented

2026-03-03 18:48:10 +03:00

Author

Owner

@yum13241 commented on GitHub (Sep 22, 2024):

Nope. @oerg866, should I make an issue over at DOSBOX-X's side, saying that they need to not assume that the boot image complies with FAT32?

@yum13241 commented on GitHub (Sep 22, 2024): Nope. @oerg866, should I make an issue over at DOSBOX-X's side, saying that they need to not assume that the boot image complies with FAT32?

kerem commented

2026-03-03 18:48:10 +03:00

Author

Owner

@oerg866 commented on GitHub (Jan 19, 2025):

Sorry I missed the 2nd comment. Yes, please do that :)

@oerg866 commented on GitHub (Jan 19, 2025): Sorry I missed the 2nd comment. Yes, please do that :)

kerem commented

2026-03-03 18:48:10 +03:00

Author

Owner

@yum13241 commented on GitHub (Jan 19, 2025):