Re: [Freedos-user] generic bootsector as file? - versatility of grub4dos explained

2009-02-09 Thread Eric Auer
Hi! > No. You could just load the contents of the files and > execute them so you don't have to provide a letter. You cannot "just load ... and execute", you would have to do it at the right moment etc. In particular, you would load SHSUCDX after all DEVICE lines, so you had to keep it waiting i

Re: [Freedos-user] generic bootsector as file? - versatility of grub4dos explained

2009-02-09 Thread Christian Masloch
>> No. You could just load the contents of the files and >> execute them so you don't have to provide a letter. > > You cannot "just load ... and execute", you would have > to do it at the right moment etc. Of course, but my point was that you won't have to provide a drive letter. > In particular

Re: [Freedos-user] generic bootsector as file? - versatility of grub4dos explained

2009-02-09 Thread Eric Auer
Hi! > my point was that you won't have to provide a drive letter. ... > So that you could, say, debug your CONFIG.SYS not to load > SHSUCDX and/or ELTORITO.SYS? I was thinking more of a config.sys menu item to load them while the others would be for normal boot without them... > Why? After all,

Re: [Freedos-user] generic boot... - booting from raw cd/dvd

2009-02-09 Thread Eric Auer
Hi again, adding another idea to the possibilities of booting from CD/DVD without having to use 1.2 / 1.44 or 2.88 MB boot floppy images or MEMDISK in emulation mode: You could use the technology of Rayer's ROMOS which allows you to boot a FAT12 image directly from ROM. This image has only 1 FAT,

Re: [Freedos-user] generic boot... - booting from raw cd/dvd

2009-02-09 Thread Bernd Blaauw
Eric Auer schreef: > mode: You could use the technology of Rayer's ROMOS > which allows you to boot a FAT12 image directly from > ROM. This image has only 1 FAT, so MS DOS 6 does not > I wonder how large such expansion ROM images can be (64K? more?). The Coreboot project (www.coreboot.org , for

Re: [Freedos-user] generic bootsector as file? - versatility of grub4dos explained

2009-02-09 Thread Christian Masloch
>> Why? After all, it would be a special kernel binary used to >> boot CD-ROMs only, so you would usually want to load both. > > Oh okay. Well in THAT case I think I would prefer one of two > other methods: 1. Add very basic readonly root directory file > read ability for ISO9660 CD/DVD to the kern

Re: [Freedos-user] generic boot... - booting from raw cd/dvd

2009-02-09 Thread Michael Reichenbach
Bernd Blaauw schrieb: > Eric Auer schreef: >> mode: You could use the technology of Rayer's ROMOS >> which allows you to boot a FAT12 image directly from >> ROM. This image has only 1 FAT, so MS DOS 6 does not >> > I wonder how large such expansion ROM images can be (64K? more?). The > Coreboot

Re: [Freedos-user] generic bootsector as file? - versatility of grub4dos explained

2009-02-09 Thread Eric Auer
Hi, >> 1. Add very basic readonly root directory file >> read ability for ISO9660 CD/DVD to the kernel, > > However this requires major code re-writing for this new driver, instead > of relying on working drivers. (Which only requires the kernel to have > this drivers's files embedded or on

Re: [Freedos-user] generic boot... - booting from raw cd/dvd

2009-02-09 Thread Eric Auer
Hi Bernd, >> ... You could use the technology of Rayer's ROMOS >> which allows you to boot a FAT12 image directly from >> ROM. This image has only 1 FAT, so MS DOS 6 does not >> > I wonder how large such expansion ROM images can be (64K? more?). Standard method has a limit of 64 kB according

Re: [Freedos-user] generic boot... - booting from raw cd/dvd

2009-02-09 Thread Michael Reichenbach
Michael Reichenbach schrieb: > Bernd Blaauw schrieb: >> Eric Auer schreef: >>> mode: You could use the technology of Rayer's ROMOS >>> which allows you to boot a FAT12 image directly from >>> ROM. This image has only 1 FAT, so MS DOS 6 does not >>> >> I wonder how large such expansion ROM images

Re: [Freedos-user] generic bootsector as file? - versatility of grub4dos explained

2009-02-09 Thread Tom Ehlert
> Yes, but that appends only one file. Appending two files to the kernel > raises the need to find where the second file begins. (If possible without > unreliable signature searchs.) using the SYS CONFIG mechanism, you could easily have SYS CONFIG /AndThe1stAttachedFileIsHasSize12345 /AndThe2n