-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
Yes, the DOS 7.1 (the one that comes with Windows 98) has also the capability (the actual IO.SYS or the bootsector code) to boot even if the IO.SYS and MSDOS.SYS are not the first files on the volume (unlike last "real" DOS 6.22).
In case, there is still bootpart (by Gilles Vollant) that can rewrite the root so that IO.SYS and MSDOS.SYS are first files:
https://www.winimage.com/bootpart.htm
To manage partition ID's, active and hidden status, etc, I would suggest instead grub4dos that has all the needed commands and of course a whole lot of (sometimes useful) booting capabilities, including the capability to boot a MS-DOS IO.SYS by directly chainloading it (i.e. bypassing the bootsector code, either the last 0.4.5c:
http://grub4dos.chenall.net/downloads/grub4dos-0.4.5c-2016-0...
or any more recent 0.4.6a version (legacy, not "for UEFI"):
https://github.com/chenall/grub4dos/releases
should be fine .
Of course in case of booting troubles you need to boot it from an external media.
The page by jdebp, as well as the article in the topic are all about "ancient" MS-DOS versions, they are very useful if you are trying reproducing the past, but they (fortunately) do not apply to latest DOS or NT systems, though there are still - here and there - a number of little quirks, even on NT based systems, only as a side note in some cases you need to disable the CHS checks in order to be able to boot NT/2K/XP (and possibly later):
https://clemens.endorphin.org/2007/12/removing-chs-based-acc...
http://reboot.pro/topic/8528-how-to-patch-fat32-boot-sector/...