[syslinux] Planning a 2.08 release

[Murali Krishnan Ganapathy]

I dont know if adding that feature (making memdisk force BIOS to choose 
the last possible drive letter), would help in any situation except the 
situation I described. Right now, having a 10MB floppy image is more 
than enough for me.

BTW, Thanks to the new MEMDISK interrupt, I have one DOS image which 
does a whole lot of things depending on the arguments it gets. I have 
implemented an an rc.d style autoexec.bat and that makes things really 
useful. The key is a program which parses the boot time arguments and 
sets appropriate environment variables (a simple modification of the 
sample program which comes with syslinux). This is also available for 
download (http://people.cs.uchicago.edu/~gmurali/gui), in case anyone is 
interested.

This feature has reduced the number of DOS images in my CD and hence 
maintaining them is a lot easier.

- Murali

H. Peter Anvin wrote:

>>BTW, if I give memdisk a hard disk image, can one make sure that DOS
>>recognizes it not as C: but some thing later, i.e. make DOS assign drive
>>letters to the regular hard disks first and then assign one to the
>>memdisk image?
>>    
>>
>
>That might not be too hard to do.  There are a few caveats, however:
>
>a) MEMDISK must be a BIOS drive, so if there are non-BIOS drives in the
>system (device drivers, in other words), they will always come after the
>MEMDISK.
>
>b) MEMDISK must be adjacent to all the real drives, i.e. if the BIOS has
>real drives C: (80h) and D: (81h) MEMDISK could be C:, D: or E:, but
>not, for example, F: or Q:.
>  
>