Hi! > As you maybe know the MSDOS is not able to boot from 81h drive. Even if you > run the bootsector using bootmanager the IO.SYS is not able to load itself > and work.
This is a MS DOS specific problem because there, the kernel is 2 files. > In FreeDOS kernel (tried with 2041) it is quite different because it > succesfully boots from 81h drive but (FD)CONFIG.SYS is loaded from the > first primary partition on 80h drive. The same with AUTOEXEC.BAT. Almost correct: You can put command.com options in config.sys to tell it that autoexec.bat is at another location in FreeDOS command.com :-) > The C:\ partition is on 80h drive although it was not the boot drive. As far as I know, that is intentional. C: by definition is the first DOS partition on the first (according to BIOS numbering) harddisk :-) > So my question is if this behaviour is planned or not. For my needs > is this OK but isn't it a bug? I think this is intentional. It would be interesting to know if the kernel can be configured (with FreeDOS SYS, you can patch some flag bytes in FreeDOS kernels) to use the boot drive as C:, instead of the BIOS 80h drive. After all, the boot sector can pass the number of the boot drive to the kernel using registers, so it could work. > And we should test if the KERNEL.SYS from 81h drive is loaded complete. The FreeDOS kernel is only one file, so yes, it is completely loaded :-) Cheers, Eric ------------------------------------------------------------------------------ What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic patterns at an interface-level. Reveals which users, apps, and protocols are consuming the most bandwidth. Provides multi-vendor support for NetFlow, J-Flow, sFlow and other flows. Make informed decisions using capacity planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e _______________________________________________ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
