Why many DOS based tools in it's own image?
Posted: Wed Dec 24, 2008 4:18 pm
Only talking about the DOS bases part of UBCD...
I wonder why UBCD has such a big boot menu. Most of the entry does not seam necessary.
Some tools of their own place inside the boot menu, other tools are just hang around in the folder names dosapps.
Why not let the user choose in the bootmenu to boot either MS-, Free or WhateverDOS and after DOS is booted pop up a nice DOS based menu advertising all the DOS based application.
After the application terminated you could open that menu again and the user could start the next tool without need to reboot. But why any tool should get it's own image?
I think the work to update all images (for example if new version of ctmouse) is much bigger then updating a single DOS image (at the end of that image with the new menu I suggested...).
I wonder why UBCD has such a big boot menu. Most of the entry does not seam necessary.
Some tools of their own place inside the boot menu, other tools are just hang around in the folder names dosapps.
Why not let the user choose in the bootmenu to boot either MS-, Free or WhateverDOS and after DOS is booted pop up a nice DOS based menu advertising all the DOS based application.
After the application terminated you could open that menu again and the user could start the next tool without need to reboot. But why any tool should get it's own image?
I think the work to update all images (for example if new version of ctmouse) is much bigger then updating a single DOS image (at the end of that image with the new menu I suggested...).