Well, you CAN autoboot a file...
But AFAIK only in two ways:
1. Either select it and press B. It will autoboot when you turn on the GP for the next time. Won't work with multiple SMCs though, cause every SMC usually needs to autoboot a different file. You can select the new one and press B again, so it will autoboot as long as you don't change the SMC... not suitable for me
2. Give the same name to the file you want to autoboot on every SMC... not a nice solution, in my opinion.
Here's some explanation what I found out about how the new multifirmware works:
1. You have a bios with PacRom, YAFL/WindUps and EuroFW on your GP32.
It also features a nice launcher when you turn it on, which you can configure.
2. The main configuration of the launcher is stored in the internal memory of the GP32. So you always have a completely configurable default menu.
(you can create your manu using ZPR Maker and saving it as conf.zpr on the main dir of your SMC. When you boot into the launcher and press L, the conf.zpr updates the configuration in your GP32 and you have a new default menu).
3. Every item in the default launcher menu can be set to autoboot by pressing B.
4. When you are in autoboot mode, press select while turning your GP on to skip autoboot and start the launcher.
5. You can also directly boot into a different bioses or run "boot.fxe" on your SMC by pressing various directions while turning on (ie. pressing down while turning on runs the boot.fxe)
This is a perfectly configurable and very flexible Launcher
Very nice.
If you only have one SMC, you can have all the programs you love directly implemented in the default menu of the launcher
Great!
But if you have more than one SMC, you need custom menus, right?
Right!
*** HOW TO HAVE DIFFERENT MENUS FOR DIFFERENT SMCs: ***
You can have them this way:
a. Create a default boot config which autoboots a ZPR file (eg. boot.zpr)
(You know, as described above: ZPR Maker, conf.zpr on default dir, go into launcher, press L, select the ZPR entry in the launcher and press B)
I'd suggest you create a simple conf.zpr which includes PacRom, EuroFW, YAFL/Windups and boot.zpr
b. Now every time you turn your GP32 on, it tries to autoboot boot.zpr
You can easily create different zpr files for every SMC so you automatically
get custom menus
If the GP32 doesn't find boot.zpr, it will automatically go into the launcher.
Nice.
Now I have described two different possibilities:
Create and use a config file for guys with just one SMCs (pretty fast booting
)
Create and use a config which automatically loads a custom config from your SMC.
The only problem left is:
You can't configure an autoboot item using ZPR Maker. You can ONLY turn on the autoboot option with the B button of your GP32 when you're in the launcher.
But you can ONLY turn it on, when you're in the DEFAULT MENU configuration.
You CAN'T turn it on when a custom configuration has already been autobooted.
Example:
I have configured my GP32 as described above. It automatically loads the custom menu "boot.zpr" from the SMC when I turn it on.
I have created a "boot.zpr" which only includes gp:\\gpmm\fgb32.fxe.
Now when I insert the SMC and turn the GP32 on, this happens:
1. The BIOS looks for the file boot.zpr, finds it and automatically loads it.
2. Then the boot.zpr-configured launcher shows up - showing only one item: fgb32.fxe. I can run it by pressing A, but I CAN'T configure a boot.zpr which autoloads fgb32.fxe.
So this is the only feature I'd like to add: Include autoboot option in the ZPR-configs
Everything's clear?
