[Freedos-devel] Strange behaviour when booting FreeDOS from BIOS 81h drive.
I tried several ways how to create a multiboot system on my PC. I use simple boot manager BOOTMGR from this site: http://www.bttr-software.de/products/ bootmgr/ 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. 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. The C:\ partition is on 80h drive although it was not the boot drive. So my question is if this behaviour is planned or not. For my needs is this OK but isn't it a bug? And we should test if the KERNEL.SYS from 81h drive is loaded complete. It is possible that some parts are loaded from 81h drive and some from 80h drive as I have this file on both disks. -- 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
[Freedos-devel] Bug in Freecom
FreeCom allows this command: "COPY CON" After that I can write text which echoes after enter in next line and it can't be interrupted nor with CTRL-Z nor with any other key combination. The only I can do is a restart with CTRL-ALT-DEL. MSDOS does not suffer with this bug - it does not allow "COPY CON" but writes the error message that file cannot be copied in itself. The FreeCOM version I tested is 0.84-pre2 XMS_swap [Aug 28 2006] -- 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
Re: [Freedos-devel] Strange behaviour when booting FreeDOS from BIOS 81h drive.
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