See PM and this post.
Originally Posted by JNABK
Sorry, sometimes I'm to lazy to explain it, but then I "correct" my posts here and there and it looks puzzled,...
If they have Auto-Boot-Disc on and also an Auto-ELF, instead of the hacked OSD, they insert a disc to start it. Else it starts the Auto-ELF (like HDLoader).
Again, this is user option on what they want to do. If they want to boot a disc when they access the OSD screen each time, from whatever way they access it...then why would they set Skip Disc to ON? That would be pretty dumb.
If they press a button to reach the OSD now, the inserted disc will boot (regardless, what Fastboot says) because it loads through the hacked OSD, so (OSD-)Skip-Disc-Function must be turned on. But this permits Fastboot if on (in newest Betas), so the users must re-configure there CNF every time, they wan't to use the OSD, or disc.
The other way, they even can have there discs in drive.
It gives much more freedom, to not permit it by the core, but make a user-option for FMCB-Configurator.
No user must go so often, to the configurator and it still works for both groups.
It isn't a cut off, but more like a feature,...
Lets look at a few other scenarios with that thought:
If you want to run an ELF automatically and set it to Autoboot , but press a button on startup, wouldnt the Button press option CUT OFF the automatic option?
Button-Press is more important, cause it let's users the choice, to boot to OSD, or another ELF than.
Not a cut off, but this is the Fastboot.
If you want to boot to the OSD Menu and set Autoboot to ON, doesnt that CUT OFF the OSD menu?
It starts even before the file of OSD gets loaded.
(File-load-time is mainly the cause of delays,...)
Button-Launch is even prior to Fastboot.
If you want to automatically run a disc on start up but press a button, doesnt this CUT OFF the automatic disc boot?
After RESCUE.ELF and loading of CNF (if present) the button-check is running and than starts the corresponding "mode" if a button is pressed, be it loading of an ELF, or the hacked OSD.
That was the wanted structure.
Theres 3 scenarios where one option cuts OFF another option.
-Buttonlauch as prior function, cause it ever let's a choice, which mode to start
-then the "fastboot/autoboot-disc" to work with discs, regardless if the OSD-Hack works.
-then the OSD-Hack, if Autoboot-Disc is off, or no disc is in (and skip-disc can permit the start-up from OSD).
It does take 6-7Seconds, to took me to the OSD.
- 2-3Seconds: Loading rom0:OSDSYS --> loading MC-Update -->
- 2Seconds (PAD-Delay set to 0) for the overall working and hacking-process. Most of the time is the loading-process from OSD-file from rom0:/OSDSYS again here (I think,...).
2-Seconds till it shows the Device-Browser (takes more seconds on other functions, but is OSD-Related).
FMCB-Fastboot and DMS3-Fastboot is much likely the same.
Maybe 2-3 Second longer (which is as long as the loading-time and working doesn't take up a second to this point).
ESR-Discs are even a bit faster recognized, than original PS2 (also tested on NoMod-PS2).
Yes, as written in PM. If that is, what you wanted to see,...
Oh, i didnt know you changed the subject, thought we we still on about the options.
It was a FMCB-Core-Function, so it ever works.
yep, me too...but the current Autoboot option you've been saying to put back in doesnt do those things. But i hope these will be created and added in as a real FASTBOOT option. Not just a few seconds Autoboot option like it was.
It isn't related to the OSD in any way, so it really should work ever, regardless, if the OSD-Hack works, or not.
...of course, I wanted to see Fastboot for ALL DISCS. ^^
I never said, that I wanted the old one, which only works for PS2-Discs.
It should work for all, but that the (osd-)skip-disc-function is permitting the Fastboot if turned on is not a good Idea thought, because the OSD-Releated Skip-Disc does permitting a FMCB-Core-Function.
Like I said, if you wanted a general disc-stop-function, it could be done in another way (proposed per PM).
Same way, as vice versa...
Maybe there is a better solution with an improved FastBoot option yet to come, I'm all for it. But the current Autoboot option isnt worth adding back in as it will only be a confilct if both are set to ON, so why give this possible conflict to the users to cause a new Noob headache?
suloku explained it in a better way than I even could. ^^
And i never said i wanted to disable the autoboot, only that its still an option of autobooting if the Skip Disc is OFF, so why add the second option to autoboot to add to confusion when the whole problem of conflict is removed along with that extra option choice.
That's why I don't have a point-of-view, just for one group of users.
Im not against improvemnets in any way, so sure we can find another way to have Skip Disc and FastBoot options, but in the meantime, i suggest leave that Autoboot Disc option out.
This is why we have betas and tests.....to find those solutions that work best for all in general, not for just a few users MIGHT want to do. We first create a working structure that is stable...then we look for ways to improve on that structure, not change it around each and every time.
It is possible, that the OSD-Hack won't work properly.
The OSD-Hack rejects to the "FMCB-Core" and loads all options added&available at the OSD through the FMCB-Core.
You can see the "hacked OSD" as a GUI for FMCB-Core.
Like Windows (9x) for DOS.
The rejecting from OSD to FMCB works from loading the mc-update with args.
That means, that permitting this option, or "removing" is not very helpful, because it won't free up many space, but only restricts the core-functions, while it is also possible, to simply restrict it by the CNF (without expanding the CNF, that's why it is compatible to old FMCBs), but with expanding the configurator with this function.
Agreed, that's why I think, we shouldn't implement these kind of "permitting" in the FMCB-Core, but more likely in the configurator, where we can add the same kind of option.
What we have is a good structure, so we should be focusing on making it a stable structure as it is and bug free first.
The "Core" would remain as it was before, but the configurator becomes a new option, which than is also compatible with older FMCB's again.
I really hope, I get it right about general disc-prevention.
So,... If we come across and the idea proposed in PM is good for ya, we simply post it here and then Jimmi might add it that way (or even more to "add" by suloku to his configurator, but Jimmi can remove his last addition... or "permition" in FMCB-Core).
Edit.2: JNABK pmed me yippie.
Last edited by TnA; 08-30-2008 at 01:27 PM.
PS2 V7/DMS3 V2 (FW:2.4b7); Seagate Baracuda 200GB
PS2 V7/CC1.0 (FW:34 hacked v2 BM:2.1.6); Maxtor DiamondMAX9 PLUS 160GB
PS2 SCPH-30004R; NoMod+NoLaser
3xSony MC 8MB
MAX/Datel 16MB with Boot-CD
Custom FMCB 1.8b+ Beta-Build, my AIO 0.5, Sony&xRhino-Linux