ELSE GOTO BOOT$MENU$OPT
Where the $MENU variable and $OPT variable are combined to goto a specific label (e.g. BOOT39:).
I was able to get the script to work by changing to the following:
ELSE GOTO BOOT$(MENU)$OPT
Now, I'm wondering why I had to make that change. The documentation says the parenthesis is optional ("Optionally, you can enclose the variable name in parenthesis.") I'm guessing it has something to do about the reverse script parsing?
Now, some other things:
1. "Diskemu can now emulate multiple floppy images at once, and emulate a floppy without booting it (noboot mode)."
How would one emulate multiple floppy images at once? I'm guessing this would be used for times when normally you boot from two or more floppies? How do we use this command?
2. "Reverse and selective input parsing, for more powerful yet faster running scripts."
How do we control the parsing? Also, how does this effect the scripts (as per my problem above with the multiple variables)?
3. "Updated/new interface modules for isolinux (memdisk), Ranish Partition Manager, and Memtest86+.
I use Memtest86+ quite regularly and know about Ranish Partition Manager (but don't use it). I question whether it's a wise idea to branch CD Shell away from just boot-type functions. I mean, there are tons of tools that could be added; but I feel this takes away from the development of CD Shell and the endusers can add the tools to their CD as they see fit. Obviously, it's your project and you can do as you'd like; but I thought I'd add my 2 cents worth.
4. "Ability to neatly pack all CD Shell files into an iso, so only one file need be placed on your disc."
Has this changed from the old way of creating and .iso and hiding the files? If so, what's the new way? The documentation on the website describes this as "OUTDATED INFORMATION!".
Mike, let me just end by saying thank you for such a wonderful piece of software. I know it's been extremely helpful to me and a lot of others. I appreciate all your hard work in creating and supporting it.