Hello!
Isn't the "real bootable partition" always assigned to C:?
BTW, I think this (slightly) misleading, when (boot) partition from secondary disk becomes C:. Again, I suggest, probably, better to _not_ make it C:, but in main.c:FreeDOSmain() make it
default (to allow process (fd)config.sys from it).
Not a bad idea.
Let's concentrate on bgfixing before the imminent FD1 release.
I not object, but this question may be studied _for future releases_. Isn't? :)
Sure. All suggestions here are for a "post-FD1.0" release.
EA> the config file can contain a (processed in "0th pass") EA> BOOTDRIVE=X line which makes FreeDOS select drive X: and EA> load the config file from there for the other passes.
Or it can even implement the ROM-DOS's NEWFILE= CONFIG.SYS command. Below is the relevant for NEWFILE excerpt from http://www.rtdusa.com/NEW_manuals/software/cpumodules/ROMDOS_manual.pdf
Lucho __________________________________________________________________
NEWFILE
CONFIG.SYS Command
The NEWFILE command allows you to continue CONFIG.SYS file processing from a new file. The file can be located in another directory or even on a different drive.
Syntax
NEWFILE=filename[,device]
Remarks
The NEWFILE command is especially useful when the CONFIG.SYS file is located on an inaccessible drive or in ROM. Additional device drivers or instructions can be added easily to the new file and is processed along with the main CONFIG.SYS file upon starting the system.
When the NEWFILE= instruction is processed, control passes from the present file (the one containing the NEWFILE instruction) to the file specified in the command. Any commands placed after the NEWFILE instruction in the original file are not processed. If the specified filename cannot be located, CONFIG.SYS processing returns to the original CONFIG.SYS file and the next instruction is processed. The next instruction can even be a second NEWFILE= statement, allowing flexibility for systems which may have a variety of drives installed or not installed at boot time. The first successful NEWFILE statement is processed, transferring control to the specified filename. The remaining instructions in the original CONFIG.SYS file, including NEWFILE= statements, are not processed.
When NEWFILE is used, it is also created as an environment variable, retaining the value assigned by the NEWFILE= statement. This can be used in an AUTOEXEC.BAT file for further boot-up decision-making.
The presence of [,device] on the NEWFILE command line will tell the ROM-DOS kernel to load this device driver before trying to process this NEWFILE statement. The format of this parameter is exactly the same as the parameter for a DEVICE= statement.
Examples
NEWFILE=C:\BIN\NEWCFG.SYS
Causes instructions in the file NEWCFG.SYS, located in the C:\BIN directory, to be executed as part of the CONFIG.SYS file.
NEWFILE=C:\BIN\NEWCFG.SYS,ROMDRIVE.SYS C000
Causes the device driver, ROMDRIVE.SYS, to be executed prior to processing the instructions in the file NEWCFG.SYS as part of the CONFIG.SYS file.
Also, the environment will contain the following entry:
NEWFILE=C:\BIN\NEWCFG.SYS
Verify this by running the SET command with no parameters.
NEWFILE commands can be nested. That is, your original CONFIG.SYS can call a second set of instructions via the NEWFILE command. The second file can, in turn, call a third file by using the NEWFILE command, and so on. Be sure that each filename in the successive steps has a unique name, otherwise, you will create an infinite loop as control is passed back to the same file repeatedly.
------------------------------------------------------- SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media 100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33 Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift. http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285 _______________________________________________ Freedos-kernel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-kernel
