Thank you for sharing you improvements.
Just to show one possible way to handle the options, I am attaching 2 screenshots.
The specific aesthetics of the boot menu is less important.
In the “first step”, the user chooses which test to run (one of the tests, or cpuinfo, or help, or tips about possible commands).
After the user presses [ENTER] on the selected test, a second selection appears, which only corresponds to the options offered by that specific test.
All is done in one cfg file only, optionally adding the two DISPLAY files that Explorer09 already prepared.
As said, there are other ways. This is just one possibility (with pros and cons).
Now, regarding the help, ubcdcmd=helpinfo, cmdhelpinfo=* (and I may be forgetting some other option), it seems a little bit confusing. Reading the help files, it is not so clear why there is a need for both "ubcdcmd=helpinfo" and "cmdhelpinfo=*", and that's in addition to the "ubcdcmd=menu" option.
Once again, thank you Explorer09![8)]( "Cool")
.
Best Regards,
Ady.
Just to show one possible way to handle the options, I am attaching 2 screenshots.
The specific aesthetics of the boot menu is less important.
In the “first step”, the user chooses which test to run (one of the tests, or cpuinfo, or help, or tips about possible commands).
After the user presses [ENTER] on the selected test, a second selection appears, which only corresponds to the options offered by that specific test.
All is done in one cfg file only, optionally adding the two DISPLAY files that Explorer09 already prepared.
As said, there are other ways. This is just one possibility (with pros and cons).
Attachment:
cpustress1.jpg
Attachment:
cpustress2.jpg
Now, regarding the help, ubcdcmd=helpinfo, cmdhelpinfo=* (and I may be forgetting some other option), it seems a little bit confusing. Reading the help files, it is not so clear why there is a need for both "ubcdcmd=helpinfo" and "cmdhelpinfo=*", and that's in addition to the "ubcdcmd=menu" option.
Once again, thank you Explorer09
.Best Regards,
Ady.