Free McBoot Configurator

[suloku]

Version 1.2.3 - FMCB 1.7 compatible
-Fixed bug regarding ESR path config. It always mapped to mc?. Also selecting a file from B?DATA-SYSTEM dir lead to messing the first path of the first 3 OSD items. Thanks TnA for noticing.
-Updated CNF parser with that of uLaunchELF 4.29.

Version 1.2.2 - FMCB 1.7 compatible
-Return to loader was only working for mass and mc:/BOOT/ locations. Fixed.
-Added copy and paste OSD item. Over and OSD entry press L2 to copy it, browse to the entry you want and press R2 to paste. A prompt will show the current entry number and what it holds, press OK or CANCEL to decide overwriting.

Version 1.2.1 - FMCB 1.7 compatible
-Default config loading bug wasn't totally solved. It nows fully respects your configuration.

Version 1.2 - FMCB 1.7 compatible
-Added all new CNF entries which FMCB 1.7 makes use of.
-Updated some previous CNF entries to new FMCB 1.7 naming.
-Added credits at startup (no time losing).
-Fixed a bug regarding "Return to loader". The option didn't really work when having the mc at slot 2.
-Re-organized the options so they fit in the screen and are more easily found (mainly OSD hacking options).
-Fixed a bug regarding default config loading.
-Added hability to reset to default configuration by pressing SELECT over the loading options.
-Now only used entries for OSD items and launch keys will be written to the final cnf file. All other options are always written.
-Removed USB drivers from elf file. They are now read from mc?:/SYS-CONF/ (same location as FMCB).
-CNF parser updated with newest changes on uLE by Dlanor.

Version 1.1 - FMCB 1.6 compatible
-Added all new CNF entries which FMCB 1.6 makes use of.
-Updated some previous CNF entries to new FMCB 1.6 naming.
-Added startup promt asking for the button layout (circle for OK or cross for OK).
-Checks for SYS-CONF folder and icons, creating them if not present.

Version 1.0 - FMCB 1.5 compatible
-Initial public release.

Note: version 1.0 may be suitable for older FMCB versions supporting CNF files, but it's not recommended to use FMCB configurator with other versions of FMCB other than the one it's made for, as there is a high risk of losing your configuration, as the app doesn't modify the CNF file, a new one with all the settings is created in its place. You have been warned.


------------------
Credits and thanks
------------------

Everyone involved in the Free McBoot project (Jimmikaelkael and Neme as heads).
Dlanor, E P and everyone who contributed to uLaunchELF project, on which this program is highly based on.
Dlanor for betatesting and helping with the code.
Everyone who I may be missing now.

[TnA]

THX, to be 1st (in this thread). ^^

I tested it and like I assume (when dlanor is beta-tester), it seems to work flawlessly.

THX, that both:

-Loading CNF + Modifying and
-Create CNF with settings...

Features are there from the beginning!
No fancy playing around with texteditors, just through a simple, full functional GUI.
N1 suloku & all related to configurator. :)

[kevstah2004]

Thanx I was editing it with ULaunch's text editor before but couldn't add the slashes "/" so this works similar to ULaunch's button configurator where you just browse for an elf an it's automatically mapped to the button you selected? this would've been great as extra option on the initial MCBoot install elf.

[jimmikaelkael]

Nice work Suloku ;)
Can I add this to be Official FMCB releases thread, before to go ?

[suloku]

kevstah2004@:
Yes, it works like ule.

jimmikaelkael@:
Of course you can.
It may confuse people if I update the file here (which I'm not gonna do for now, there's no real need for it atm) and the other one is still on the official release thread, but I'm sure a mod can change the file on that thread if it's necessary, so go on.

[kevstah2004]

it seems to work flawlessly.

co-sign no problem whatsoever, nice one suloku :applaud:

[darthkamikaz3]

Great work suloku..thanks for this configurator..


kamikaz3

[amp2006]

good work keep it up

[kevstah2004]

I grouped your beta releases

v1.1b
http://psx-scene.com/forums/freevast/57899-free-vast-continues-post429536.html

v1.2b
http://psx-scene.com/forums/freevast/57899-free-vast-continues-post429664.html

v1.22b
http://www.ps2-scene.org/forums/429707-post2635.html

v1.23b_fixed
http://psx-scene.com/forums/freevast/57899-free-vast-continues-post429760.html

v1.24b
http://psx-scene.com/forums/freevast/57899-free-vast-continues-post429827.html

[Bootlegninja]

Thanks for doing that. :) I don't know why one of us didn't sticky this one. :chinscrat

[suloku]

I grouped your beta releases


Thanks for that. I wanted to keep this thread for non beta releases, which will be the ones for the non beta fmcb releases, so I didn't post anything here.

Just to warn people: newest beta releases won't work with fmcb 1.5, the genereated config file isn't compatible for some settings.

[kevstah2004]

1.6 works great ;) French people rule :p

[Bootlegninja]

dude, you're going to have to get more to the point and on topic with your posts. You're all over the place with no subject, ryhme or reason.

[kevstah2004]

Version 1.1 doesn't load from any location with FMCB's 1.6b test 4 button launcher "untested with the actual release of fmcb v1.6" all previous config releases work fine however.

[urbigbro]

@suloku- I'm experimenting with making text based art to personalize the BIOS screen. I have used some simple one line text art, emotes, kirbies, but want to make some multi-line art.
Do you know what encoding formats (Unicode, UTF-8, Shift JIS, etc.) are supported for proper display. Also is there a font that exactly matches the one used in the BIOS screen. While making the art I want to make sure it displays correctly before putting it into the .cnf file.

After experimenting I think the BIOS is using double byte character spacing, because I have to space the text differently than when viewing it in word or notepad. Some of the text also showed up as Japanese characters in the BIOS. Is there an editor that supports double byte characters and lets me see what combination of text will be read as an Asian character (so I can avoid these combinations), and give the proper spacing.

I know I already posted this question in the main FMBC thread, but I thought perhaps it is better suited for here. Wherever it gets answered I'll link to the answer in the unanswered post.
Thanks again for this great tool!

Here's one I whipped up through trial and error.

[suloku]

Here's 1.2 beta 1, ready for next fmcb release.

I think all is OK, I haven't had any problem, this is mainly to help testing.

BTW I would like to ask for help in organizing the menus. Lately I've been putting the options harshly and where I thought they would fit better without having too much trouble adding them, but I think There needs to be some order in the menus.

Maybe this is just a thought and everyone thinks the menus are ok as they are :p

[kevstah2004]

^ Does it work with the fmcb button launcher? you broke it in v1.1.

[suloku]

Any problem you had being unable to boot the elf file wasn't related to configurator (well, that's what I think since I didn't change anything that would break the elf bootup).

Anyway I just tried the start and circle buttons, with a pad delay of 4 seconds and I haven't had any problem when booting.

BTW this newest beta is totally compatible with current fmcb 1.6.

[JNABK]

I think the menu order is just fine as is, with the exception of the new option added. It pushes down the last line and causes an overlapping effect over the border and into the next line of text.

I would suggest removing the top line : Free McBoot Settings as this line isnt really needed and the whole configurator program is only used for Free McBoot Settings. :)
This should allow everything to move up and display correctly once again. ;)
http://home.comcast.net/~jnabk/configurator.JPG

Or remove the AutoBoot Disc option, since it isnt going to be used anymore.

[Mozgus]

Or remove the AutoBoot Disc option, since it isnt going to be used anymore.

Woah, wait. Does this mean you guys weren't able to figure out how to keep the PS2 from autobooting discs from the OSDSYS screen? I sure hope not. I'm very anxious for the ability to turn off the autobooting.

[JNABK]

With the Skip Disc option, you can choose not to have the disc autoboot with it set to ON, but if its set to OFF, it autoboots a disc anyway, so its not a required option for AutoBoot Disc, since it doesnt really make much difference in 'autobooting' anyway. ;)


Yes in our tests, Skip Disc works just fine..;)

[Mozgus]

Hmm, it sure doesn't have any effect for me.

[JNABK]

The Skip Disc option isnt fixed in the current release, so you'll have to wait for the next release for it. :)

[suloku]

About the problem with display:

My console is PAL. NTSC has less vertical space, I didn't even think about it.

Removing Free McBoot Settings line is OK, I only added that because the first configurator was directly coded withing ule.

About autoboot disc:

You are going way too fast, as well as jimmi. You are forgotting that not all of us want to always use hacked osdsys. Removing autoboot option is forcing me to use the hacked osdsys to boot my discs.

In my opinion it is a very useful option, it has been disabled on newest beta, but I hope it won't be on the next one.

BTW the skip disc makes the ps2 go to the inner browser whenever it tries to boot the disc (but you can launch it from there). It's not what I thought it would be, but of course I can't complain about their work, they're doing their best and I thank them.

[JNABK]

About autoboot disc:

You are going way too fast, as well as jimmi. You are forgotting that not all of us want to always use hacked osdsys. Removing autoboot option is forcing me to use the hacked osdsys to boot my discs.

In my opinion it is a very useful option, it has been disabled on newest beta, but I hope it won't be on the next one.In my tests, with the OSD Hack set to OFF, this still auto boots a disc if the Skip Disc option is OFF, so it shouldnt make any differences there. ;)

BTW the skip disc makes the ps2 go to the inner browser whenever it tries to boot the disc (but you can launch it from there). It's not what I thought it would be, but of course I can't complain about their work, they're doing their best and I thank them.Yep, i noticed that too and mentioned it to jimmi, so i dont know if its just a bug or not yet.

[suloku]

In my tests, with the OSD Hack set to OFF, this still auto boots a disc if the Skip Disc option is OFF, so it shouldnt make any differences there. ;)


It does make the difference if you don't have set any launcher option to OSDSYS (i.e. straight boot to ule unless disc in drive) ;)

[JNABK]

Well, if there is no disc in the drive either way, it wouldnt matter if there is an autoboot option set to on/off. :)

[jimmikaelkael]

You are going way too fast, as well as jimmi. You are forgotting that not all of us want to always use hacked osdsys. Removing autoboot option is forcing me to use the hacked osdsys to boot my discs.

In my opinion it is a very useful option, it has been disabled on newest beta, but I hope it won't be on the next one.

BTW the skip disc makes the ps2 go to the inner browser whenever it tries to boot the disc (but you can launch it from there). It's not what I thought it would be, but of course I can't complain about their work, they're doing their best and I thank them.

Ok no problem I will just uncomment AutoBoot_Disc :)
But Maybe we should just rename (my fault) its text to "Ps2 Game Fastboot" in the configurator to avoid confusing people.

For the skip disc, maybe we can make it not go to inner menu, but I tought that when user insert a disk, it's to launch it (most of the time)...

[Neme]

Does it still go to inner menu with the newest update though? I expected it to completely ignore any disc including invalid ones.

[jimmikaelkael]

Yeah it's still bringing them to inner menu when inserting a disc, But I was not seeing it as a bug...
But the problem with "DVD player not configured" message is fixed.

We still too have the Ps2 DVD retail game freezing after Ps2 logo when Skip Disc Boot is ON on older ps2... I plan to overwrite ps2 dvd function pointer to make it FastBoot and see if it's working this way or not.

[TnA]

@JNABK: You forgot the users, which use Auto-Boot-ELF. Those are than also restricted to use another app, to start the disc (it will work, if it is an app like ule, which can start discs, but what about ELFs like DMS-HDD-Explorer, for example,....), or the hacked OSD, as suloku said.

All my suggestions have a sense. ^^
No need to rip out more. :lol:


@Jimmi: Yes, please rename it to "Fastboot (Disc)", or similar.
Modchip-Creators also name it this way and it is commonly known (what it is).

[JNABK]

Im cool with keeping it, i was just saying if it werent to be used, that could be removed to bring the menu up.

I personally havent used that option since i onlu use retail game discs in the consoles that use Free McBoot and it hasnt yet made any difference to me on or off.

But if its making a definite difference for other processes, then by all means it should be kept. I was under the impression it only forced an automatic boot and bypassed the MC menu loading.

[TnA]

o.k. based on JNABK Pic...


http://home.comcast.net/~jnabk/configurator.JPG


...I suggest an idea. ^^

- Configuration-Submenu for OSD-Settings, so the Skip-Functions are in OSD-Settings (they are OSD-Related).
- Config-Submenu for FMCB-"Core"-settings, like: "PAD-Delay", "DS", Fastboot and "Button-/KeyLaunch-Keys" (these are for the process, which is done before the hacked OSD is started, so FMCB-"Core-Settings", or something).
- Not sure, where the ESR-Path should be, but I think, it could stay in main-config-screen.

[JNABK]

Configuration-Submenu for OSD-Settings, so the Skip-Functions are in OSD-Settings (they are OSD-Related).
That makes sense TnA...i'd have to agree!

Of course that would mean i'd have to re-do the Guide a bit, but its no biggie to change...:p

[TnA]

o.k. to keep the FreeVast-Thread more clean.

Here the collected suggestions, to make the configurator (and FMCB) even better.


-Move OSD-Related Items (OSD-Skip-disc; OSD-Skip-MC[-Update-Check]; OSD-Skip-HD[-UC]; Skip-Sony-Logo) to OSD-Submenu.
-Create a new Option (full disc prevention <-- Sorry can't find a good name for it) in FMCB-Configurator-Main-screen which switches Autoboot to "off" and OSD-skip-disc to "on".
If one of those settings is different, the Configurator shows it (full-disc-prevention) as "off".
...or if the settings are like these, it shows it as "on", but fastboot and osd-skip-disc remind configurable.
The FMCB-Structure remains, all is as flexible as before and this option can also be used without updating the FMCB-Core (osdmain.elf).
-MAYBE create a sub-menu for Configuration (FMCB-Core) and Advanced Configuration, but moving OSD-Items to OSD-Submenu is currently enough.


So I hope this is a good way and most agree with it.

[suloku]

-Move OSD-Related Items (OSD-Skip-disc; OSD-Skip-MC[-Update-Check]; OSD-Skip-HD[-UC]; Skip-Sony-Logo) to OSD-Submenu.
Totally agreed.
-Create a new Option (full disc prevention <-- Sorry can't find a good name for it) in FMCB-Configurator-Main-screen which switches Autoboot to "off" and OSD-skip-disc to "on".
If one of those settings is different, the Configurator shows it (full-disc-prevention) as "off".
...or if the settings are like these, it shows it as "on", but fastboot and osd-skip-disc remind configurable.
The FMCB-Structure remains, all is as flexible as before and this option can also be used without updating the FMCB-Core (osdmain.elf).
I'll wait to see what jimmi does about that, IMO these conflicts between have to be handled by the launcher, and I think that gives more flexibility to configuration, even thought it seems it doesn't.
-MAYBE create a sub-menu for Configuration (FMCB-Core) and Advanced Configuration, but moving OSD-Items to OSD-Submenu is currently enough.
I'm not sure what do you mean, and I don't think it is needed right now, but it will be as long as more options are added.

[TnA]

Totally agreed.


That will clear-up the screen enough for now. :)


I'll wait to see what jimmi does about that, IMO these conflicts between have to be handled by the launcher, and I think that gives more flexibility to configuration, even thought it seems it doesn't.


Well, me too.
But the main-thing is, that I don't know, why Fastboot should be permitted by the launcher itself (when OSD-Skip-Disc is on), if it could also handled by the Configurator and OSD-Skip-disc also doesn't interfere with the other option.
If it is interfering due to a bug-reason, I would also agree on disable it, but afaik it is no bug,...


I'm not sure what do you mean, and I don't think it is needed right now, but it will be as long as more options are added.

Anyway,... It wouldn't help now, to add more Sub-Menus to the configurator.
Like said at the beginning of my post "OSD-Settings" in one menu is enough. :)

[TnA]

Due to all those changes and additions to the OSD-Hack, I think it is good to have 1Submenu for "OSD-Settings" (for real options and hacks like skip-disc, skip-mc, skip-hd, assigned ELFs and so on,...) and another Submenu for "OSD-Visuals", or something (for the visual-only-hacks),...

[suloku]

This is what you testers have been waiting for :p

Please tell me about menu_y, max_velocity and scroll_speed settings, about their increase numbers and if they should have a max value.

Currently menu_y goes from 0 to 220, max velocity 0 to the max value an integer can hold :p, in/decreased by 100 and scroll speed goes the same, but in/decreased by 10.

[Bootlegninja]

Looks great, but I'm noticing a couple things off with it.

It'll only allow me to configure the 1st OSDSYS option

Also, the y adjustment in the OSDSYS config screen doesn't exist.

other than that, damn nice. :)

[TnA]

N1 @suloku

@bootleg: Press left and right and you could switch to the next item, or the one before.

Hope we can see the name of the given OSD-Item,... (before pressing x or o, to enter the configure-panel for the selected Item) ^^
I also hope for config-support from mass,...

[suloku]

It'll only allow me to configure the 1st OSDSYS option
TnA already answered, press left and right. It's on the tooltip section :p

Also, the y adjustment in the OSDSYS config screen doesn't exist.

It does, it is at the Scroll menu settings screen. I put it there since that setting only applies for scroll menu.

Hope we can see the name of the given app the,... (before pressing x or o, to enter the configure-panel for the selected Item) ^^
That's really easy to implement, you'll see it when I implement the mass CNF reading (too lazy to upload just for that).

I also hope for config-support from mass,...
Didn't think of it, it'll take more time as I don't remember how to handle the mass device, lol

[Neme]

This is what you testers have been waiting for :p

Please tell me about menu_y, max_velocity and scroll_speed settings, about their increase numbers and if they should have a max value.

Currently menu_y goes from 0 to 220, max velocity 0 to the max value an integer can hold :p, in/decreased by 100 and scroll speed goes the same, but in/decreased by 10.

If jimmi integrates the latest h@ck, the scroll speed setting can be removed. And it will hopefully be the last change in this version. :) The others sound good to me, maybe some experimenting will be needed to find the right values.

[suloku]

Yes, jimmikaelkael already told me about removing the scroll_speed setting.

For the meantime i'll keep it, here you have another version with new things:

-OSD item entry name is displayed next to the selected entry.
-Cnf support from mass device. Priority at first load is mass->mc0->mc1.

I think TnA will be happy for now :D

[kevstah2004]

I was thinking of doing away with the key press launch options altogether since we have the osdmenu option now to boot ELF's instead, for the On/Off settings we could simply have press
Select = FMCB Configurator
Start = uLaunchELF
L1 = Hacked OSD = On + AutoBoot disc = Off
and if no buttons are pressed it AutoBoot's the inserted disc without the PS2logo or returns to hacked OSDMenu if no disc is inserted with AutoBoot disc = Off & Skip Sony Logo = On.
I'm not sure why you'd want Skip MC & HDD turned off anyway unless a program didn't already contain drivers for the MC & HDD so this option should be hard coded to always be On.

[JNABK]

Yes, jimmikaelkael already told me about removing the scroll_speed setting.

For the meantime i'll keep it, here you have another version with new things:

-OSD item entry name is displayed next to the selected entry.
-Cnf support from mass device. Priority at first load is mass->mc0->mc1.

I think TnA will be happy for now :D

Exellent!!:D

edit:

Dont know if your aware, but there are 2 entries for "Free McBoot Configurator" , @ Item 30 and Item 100 with the same filepath of mc?:/SYS-CONF/FMCB_CFG.ELF as a default setting in the OSD settings menu when you save. So you get 2 displays in the OSD Menu by default, if you didnt change those 2 Items.

[TnA]

I think TnA will be happy for now :D

I am,.. hrhr :D
No nasty configuring with a text-editor anymore (only for the extra-long OSD-Item-Names ^^ )

Works very good. I noticed the same issue, like JNABK.

[JNABK]

I have a suggestion:

Maybe put in something like this as a default:

OSDSYS_menu_top_delimiter = ---===[ Free McBoot ]===---
OSDSYS_menu_bottom_delimiter = ---===[ Version 1.7 ]===---

OR

OSDSYS_menu_top_delimiter = ---===<< Free McBoot >>===---
OSDSYS_menu_bottom_delimiter = ---===<< Version 1.7 >>===---

Change the version number for each new version that follows.
This shows everyone its the next version they just installed, when they see it on the screen. Of course it can be changed by the users, but its just a thought. ;)

[TnA]

I have "Free McBoot 1.6b Test 51" (for now on mass and mc) in my top-delimiter and "FMCB-USB-Extension 1" as my bottom-delimiter (only, if I plug in my USB-Stick with my extra-elfs and CNF on mass).

That was the first thing, I've re-configured. ^^
I'll do the same with my "FMCB-Final-Release-Only-MC", but with next final release-name,...

Edit: Hm,... Maybe I move the "Test 51" to bottom and re-call it "Test-Bulid 51" (for MC-Config).

[JNABK]

I have "Free McBoot 1.6b Test 51" (for now on mass and mc) in my top-delimiter and "FMCB-USB-Extension 1" as my bottom-delimiter (only, if I plug in my USB-Stick with my extra-elfs and CNF on mass).

That was the first thing, I've re-configured. ^^
I'll do the same with my "FMCB-Final-Release-Only-MC", but with next final release-name,...

Edit: Hm,... Maybe I move the "Test 51" to bottom and re-call it "Test-Bulid 51" (for MC-Config).

lol, thats exactly what i did too! I put the CNF with 'Test 51' at the bottom and have it on the USB root. Mine just says Free McBoot at the top. :p

[TnA]

lol, thats exactly what i did too! I put the CNF with 'Test 51' at the bottom and have it on the USB root. Mine just says Free McBoot at the top. :p

Not exactly,...
The Beta-CNF I've putted to my MC looks like this:


(...changed it right now to this...)

Top: "Free McBoot 1.6b"
Bottom: "Test-Build 51"


...on mass:

Top: "Free McBoot 1.7" (I assume, it comes as 1.7-release, instead of 1.6b or not?)
Bottom: "FMCB-USB-Extension 0.1"

I can clearly see the difference,... (not only in the different OSD, but also in the text,...) :D

[JNABK]

Not exactly,...
The Beta-CNF I've putted to my MC looks like this:


(...changed it right now to this...)

Top: "Free McBoot 1.6b"
Bottom: "Test-Build 51"
Well maybe not the same words you use, but you get the idea of what i mean....;)



(I assume, it comes as 1.7-release, instead of 1.6b or not?)

Im assuming it will, but no absolute confirmations have been mentioned afaik.

[suloku]

Exellent!!:D

edit:

Dont know if your aware, but there are 2 entries for "Free McBoot Configurator" , @ Item 30 and Item 100 with the same filepath of mc?:/SYS-CONF/FMCB_CFG.ELF as a default setting in the OSD settings menu when you save. So you get 2 displays in the OSD Menu by default, if you didnt change those 2 Items.

I knew someone would say that, I forgot to mention it. This is the same that happened before: default installed cnf has configurator in item 30. Your cnf files when you first used the new configurator didn't have any entry for item 100, so it was set by default by the configurator (i think default place for configurator should be last OSD entry).

As before, it won't happen again as long as I keep writing the hole cnf file. I wanted to keep non used OSD and launch key items out of the file but jimmi had some bugs in fmcb's parsing code and that's why your cnf files have up to 100 entries.

Should I try to find some solution to this (maybe there isn't one) or just write the hole cnf file so all works OK? CNF file takes space, but that ensures there will be always space for configuring.

[TnA]

I knew someone would say that, I forgot to mention it. This is the same that happened before: default installed cnf has configurator in item 30. Your cnf files when you first used the new configurator didn't have any entry for item 100, so it was set by default by the configurator (i think default place for configurator should be last OSD entry).


I handle it the same way,...
The idea about jumping back to last item, if first item is reached (or vice versa) isn't that bad, if we have 100 Items. :)


As before, it won't happen again as long as I keep writing the hole cnf file. I wanted to keep non used OSD and launch key items out of the file but jimmi had some bugs in fmcb's parsing code and that's why your cnf files have up to 100 entries.

Should I try to find some solution to this (maybe there isn't one) or just write the hole cnf file so all works OK? CNF file takes space, but that ensures there will be always space for configuring.

Well,... I think, it can be done, after the new source is release,...
But really,... Every CNF-Entry should be optional,... I agree in this point,... (so a big-fix should be found, I think.)

[JNABK]

I knew someone would say that, I forgot to mention it. This is the same that happened before: default installed cnf has configurator in item 30. Your cnf files when you first used the new configurator didn't have any entry for item 100, so it was set by default by the configurator (i think default place for configurator should be last OSD entry). i agree the last Item should be the configurator.

As before, it won't happen again as long as I keep writing the hole cnf file. I wanted to keep non used OSD and launch key items out of the file but jimmi had some bugs in fmcb's parsing code and that's why your cnf files have up to 100 entries.

Should I try to find some solution to this (maybe there isn't one) or just write the hole cnf file so all works OK? CNF file takes space, but that ensures there will be always space for configuring.
I think writing the whole CNF is the best solution , so when someone has an older CNF file, even if they installed it by mistake, they will always get a compatible CNF for the current release its for. If it turns into a file size problem, you can just go back to writing only the changes in the CNF until a better solution is found. :p

[suloku]

i agree the last Item should be the configurator.

I think writing the whole CNF is the best solution , so when someone has an older CNF file, even if they installed it by mistake, they will always get a compatible CNF for the current release its for. If it turns into a file size problem, you can just go back to writing only the changes in the CNF until a better solution is found. :p

Well, there's no kind of uncompatibility regardless complete cnf is written or not.

Anyway this one does write a full cnf, so after first configuration it should always load and preserve the settings, even blank ones.

I also added the credits jimmi was asking for, but I need someone to try it on a NTSC device to make sure it's displayed OK.

[katananja]

TNA

About your b51 test, i did not noticed any difference in the 90K model, the FMCB config has a few problems with alignment, the menu text is a little off at the lower menu frame.

In the 10K is another story:

1 - I can't launch FMCB config from the installer.
2 - FMCB install OK.
3 - FMCB crash at the logo screen if i press R1/START or any other shortcut that I've made.
4 - FMCB logo changed to a more higher resolution (??) Because the letters and logo is a bit smaller but much more smooth in the 10K, in the 90K still jaggy.
5 - FMCB goes to browser fine, but I still can't do nothing, the controller doesn't work.
6 - If i disable the OSD hack at the configuration, I still can't do nothing, the controller doesn't work.

All the modules and DVDELF.BIN that I use in this version was the same used in the previos (working) version.

That's it :D

[katananja]

Well, there's no kind of uncompatibility regardless complete cnf is written or not.

Anyway this one does write a full cnf, so after first configuration it should always load and preserve the settings, even blank ones.

I also added the credits jimmi was asking for, but I need someone to try it on a NTSC device to make sure it's displayed OK.
Working fine here ;)
The menu is in the right place!

[TnA]

@katananja: Can you try to specify ESR in your CNF and also try to run a ESR-disc, or another one with fastboot enabled?

Btw.: Lets move to FreeVast-Thread. :)

[JNABK]

I also added the credits jimmi was asking for, but I need someone to try it on a NTSC device to make sure it's displayed OK.

Its just a little off to the left and down of the screen, but otherwise can be seen well enough.

Heres an exact screenshot as seen on my TV for NTSC.


Edit:

Heres what i came up with as a default idea, if my suggestion (http://psx-scene.com/forums/433854-post48.html) is taken:

OSDSYS_menu_top_delimiter = -=< Free McBoot >=-
OSDSYS_menu_bottom_delimiter = -=< Version 1.7 >=-

I attached screen shot, its what im going to use. :p

[kevstah2004]

The blue OSDMenu is starting to remind me of the old betamax players with the blue led displays.

[jimmikaelkael]

As before, it won't happen again as long as I keep writing the hole cnf file. I wanted to keep non used OSD and launch key items out of the file but jimmi had some bugs in fmcb's parsing code and that's why your cnf files have up to 100 entries.


It's now fixed with the test51.
You can have only the entry used...

[artdevil]

guys, please make it AUTO:NTSC for non multi-system TV...

[suloku]

It's now fixed with the test51.
You can have only the entry used...
I'll make some tests, I thought only change was scroll_speed removal as stated in changelog.
guys, please make it AUTO:NTSC for non multi-system TV...
What problem are you having? Is it detecting PAL for you? Do you have this problem with latest version of ulaunchelf?

[dlanor]

As before, it won't happen again as long as I keep writing the hole cnf file. I wanted to keep non used OSD and launch key items out of the file but jimmi had some bugs in fmcb's parsing code and that's why your cnf files have up to 100 entries.
That will be a real pain each time someone needs to edit the file by hand (which will inevitably happen sometimes, at least in debugging setups). But why do all the unused entries have to exist at all ?

The general usage needs here are a little reminiscent of the PathPad array of uLE, for which unused entries are never included in the saved LAUNCHELF.CNF.

Should I try to find some solution to this (maybe there isn't one)
The best solution IMO would of course be to fix the parsing problem at jimmi's end.

Edit: And apparently he has now done so, as stated in his post#62 above :)

Since we are talking about a parsing problem here, this means that the 'syntax' of the CNF entries may need to be adjusted though, just like the PathPad usage in the LAUNCHELF.CNF differs from that of all other CNF variables, so that only those PathPad entries which are non-blank need to be included in the CNF file. The parsing routine reading that file just initializes the entire PathPad array to hold blanks for all entries, and then inserts only those PathPad entries really found in the file. (Each PathPad variable name in the CNF includes its position index for the array.)

The exact same method should work fine for the OSD menu definitions of FMCB, except that there would be more than one string for each OSDSYS entry, but that is very simple to implement. All four variables would use slightly different names, but identical index, just like in the current FREEMCB.CNF. The only real change would be that the indexes need to go higher, and that all four variables for each unused index could be suppressed.

or just write the hole cnf file so all works OK?
This will work too of course. And I assume you really meant "whole set of OSD menu entries", rather than "hole cnf file". We obviously need to write the whole file, regardless of how we define the subsection of its content holding the OSD menu entries.

CNF file takes space, but that ensures there will be always space for configuring.
No it doesn't. It only ensures that the number of entries will be the same. But the space needed for the entries may still be much larger. (Unless you plan to use max-length strings of spaces for each default entry.)

Best regards: dlanor

[suloku]

This version should work OK.

- Blank OSD items and launch keys aren't written.
- Default values for OSD items and launch keys will only be put on failed CNF loading. Note that all other values will fall to default if not present in the CNF.

This will only work properly on test 51. Oh, and tell me if it displays correctly on NTSC now.

Best Regards

[JNABK]

Very nice and yes it displays great on NTSC now. :)


Oh and a request idea if its possible to do without too much trouble. Could an option be added to reset all defaut options? {kinda like uLaunchELF's skin reset option}

I figured this might be a very useful option to have for those who have extensively configured a CNF and wish to start over with a fresh copy without having to go thru the 'delete existing CNF and restart configurator and save a new one' process.


Its not a big deal, but thought it might be a useful option to add. ;)

[suloku]

It's an easy matter. What I have been doing for that is try to load a cnf from a location where it doesn't exist.

I.E now if there's no mass storage device holding a cnf file on its root you can try to load cnf from there and you'll have all set to default.

Anyway I can make that pressing start over the loading cnf entries reset to default values.

[JNABK]

Cool, i'll add this to the Guide. :)

Didnt know that an attempt to load a non-existant CNF would result in setting a default one.:oops:

[JNABK]

Found some bugs in the Scroll Settings menu:

1 - When setting Left cursor to more than 9 chars, it will auto clear the right cursor setting. Changelog states max 10 chars can be used.

2 - Right Cursor is spelled {rigth} instead of 'right'.....:lol:

3 - When setting the Right Cursor to more than 9 chars, it will clear the Top Delimiter setting. Changelog states max 10 chars can be used.

Shouldnt it stop after 10 are selected and not allow more to be added?

Also if the max 10 chars are used in the Left Cursor and you put a max 10 in the Right Cursor afterwards, it will add the 10 left chars to the right, giving it 20 chars

Without changing the above settings, i set the Top Delimiter with 34 chars.,for testing {changelog says max 80 chars} it added the 34 chars to both cursor settings too.

Then i went back up to Right Cursor and just cleared it and it removed the added 10 chars from the Left Cursor setting {leaving the first 10 } , then set 9 chars and it cleared the Top Delimiter.

Any chars set in the Top Delimiter will now get added to to the Right Cursor,but not to the Left Cursor anymore.:crazy:

[TnA]

@suloku: It worked well for me.
I didn't try change my OSD-Setting again.

OSD-Settings for OSD-Items worked well for me.
Launch-Key-Mapping also,...

With the Configurator, it is very fast and easy to switch options and settings (even, if it looks a bit like a "labyrinth" ^^).
Thank you for your efforts suloku. :)

[JNABK]

Agreed, it is a very organized menu and so far i've only found the above bugs, since i have to go thru everything to see what happens to make the info for the Guide.

Oh i really like the Cursor Max Velocity and Cursor Acceleration...thats pretty cool! :D

Well, if i find anymore, i'll be sure to report them. ;)

[suloku]

Thanks, that bug was a though one, but in the end ti was just a silly little thing I forgot (as always).

New version:

-Corrected that bug and fixed max cursor text to 10 chars (delimiters are limited to 33 chars, if you want something longer you'll have to edit manually).
-Pressing SELECT over loading entries will restart all values to default settings.

Hopefully all works OK with no bugs now.

[JNABK]

Works great! :)

So far its flawless, good work bro!.........:D

[suloku]

Advancing to the events, new beta (should work OK and be ready for final release atm)

Changes:
-Added new setting "Video Mode" under OSDSYS menu.
-Updated CNF parser with the latest changes to ule by Dlanor.

That's all folks!

[suloku]

I've just thought that since fmcb itself has moved usb drivers to mc?:/SYS-CONF/, should I just get the drivers from there and save some space?

[dlanor]

I've just thought that since fmcb itself has moved usb drivers to mc?:/SYS-CONF/, should I just get the drivers from there and save some space?
Well, since the configurator will only need to access USB if configuring FMCB for use with USB, the drivers should always be there then. Anyone removing those drivers should realize that FMCB can then no longer be used for USB access, and thus it would no longer make any sense to try using the configurator to do that either. Just make sure that it is not dependent on successful loading of the USB drivers for cases where the user doesn't attempt to browse to "mass:". (Just like uLE which doesn't even try to load the drivers until needed.) This way users who have no USB devices can save even more MC space.

But uLE will continue to have internal drivers (with external ones a configurable option), as I don't want uLE to be dependent on drivers supplied by unrelated tools and removable by the user.

Best regards: dlanor

[suloku]

Well, since the configurator will only need to access USB if configuring FMCB for use with USB, the drivers should always be there then. Anyone removing those drivers should realize that FMCB can then no longer be used for USB access, and thus it would no longer make any sense to try using the configurator to do that either.

That's what I realized, so I'll make usb drivers load from fmcb location, and of course ule has to keep having internal usb drivers, as it is a totally stand alone app.

EDIT:

Here you get it.

Changes:
-Removed usb drivers from elf. Now it uses the same ones as fmcb from SYS-CONF (mc can be at any slot).

That means file size is reduced by 33 kb, enjoy.

[TnA]

Good idea and choice. :)
THX you.

[JoeUser38]

That's what I realized, so I'll make usb drivers load from fmcb location, and of course ule has to keep having internal usb drivers, as it is a totally stand alone app.

EDIT:

Here you get it.

Changes:
-Removed usb drivers from elf. Now it uses the same ones as fmcb from SYS-CONF (mc can be at any slot).

That means file size is reduced by 33 kb, enjoy.
Ah, thank you! That's a very nice space savings.

[suloku]

Configurator 1.2 for Free MCBoot 1.7 uploaded at first post.

This means fmcb 1.7 will come soon ^^

[dlanor]

Configurator 1.2 for Free MCBoot 1.7 uploaded at first post.

This means fmcb 1.7 will come soon ^^
Yep.

The final(?) v1.7 release version seems to be up (since yesterday) on the usual test site, but it has a new password, so I haven't been able to try it yet.

Best regards: dlanor

[guxtabo]

Iuuuuuhuuuu! :)

[suloku]

I hate this, just released a final and already had to update it :p
Thanks TnA for his exhaustive testing and jimmikaelkael for telling me.

Yep.

The final(?) v1.7 release version seems to be up (since yesterday) on the usual test site, but it has a new password, so I haven't been able to try it yet.

Best regards: dlanor

I saw it too, maybe jimmi had a typo when inserting the pass.

[TnA]

The FMCB-"Release Candidate" was updated (same file). Some bugs are fixed.
The Configurator work like a charm with it.

But I still have one suggestion, I mention you later. :D

[JNABK]

I saw it too, maybe jimmi had a typo when inserting the pass.

No it is a completely new password, but by the time you read this, the final should be getting released, so you probably wont be needing the test anymore.

[TnA]

Hopefully he got the pass for the new folder,...
I didn't read the names, which the PM was send to. :(

[suloku]

But I still have one suggestion, I mention you later. :D

Ears opened (or eyes). Being you I can't think what this suggestion is about.

[TnA]

What if "Load from device" and "Save to device" only have 1 "entry" each (instead of 3)?
I have to ideas for now, how to implement it with given things from ule, or the configurator, itself.

1st.:

Build like the menu, which switches the color for OSD-Items.

e.g.
Load from device: --> "mass" "mc0" "mc1" (the arrow selects the device)


2nd.: Another one,...

You know the "pop-up-window" in ule, if you press L1 to change the settings in ule's filebrowser? Like this,...
Be it with Button-Press to choose the device, or with an arrow and manual selection (+ pressing "ENTER"-Key [ X/O ] to save).
After saving is complete, the pop-up "auto-closes".

[JoeUser38]

It would be useful to be able to re-order the program list in the OSDSYS section... of course, to do this, we would need to see the return of the "old" menu for it; perhaps include it as an "Advanced" section?

Also, I don't see a way to add an ELF with a path that does not exist, being able to add using the "mc?:" notation, or a way to add OSDSYS (maybe I'm just missing them somewhere?).

Perhaps we could have a "Template"... give the ELF name, and it fills out the the default paths of "mass:/BOOT/", "mc?:/BOOT/" and "mc?:/B?DATA-SYSTEM/" for you?

[TnA]

It would be useful to be able to re-order the program list in the OSDSYS section... of course, to do this, we would need to see the return of the "old" menu for it; perhaps include it as an "Advanced" section?


I don't think so (old menu).
But I agree, that this is a useful option (already mentioned anywhere, or not?).

It also could pop-up a list, where all OSD-Items from 1-100 are listed (like in ule Pad-Path-Function).
Then there are many ways, to edit the list.
A move-item from-to option, or simply press "ENTER"-Button [ X/O ], to drag an item move to the item, where it should be and press "Enter"-Button again, to drop the item there.

There are so many ways (without old FMCB-Configurator/OSD-Item-Options-Menu), that I couldn't expect all.


Also, I don't see a way to add an ELF with a path that does not exist, being able to add using the "mc?:" notation, or a way to add OSDSYS (maybe I'm just missing them somewhere?).


First of all,... Where do you want to add OSDSYS?
mc? is available, if you browser for your ELF with SQUARE, instead of ENTER-Button.

There is a list of options at the bottom.

The other thing, to add ELF-Paths...
You need to do it manually, with the Texteditor in ule.
How would you do it else?
If you couldn't find the ELF through the "filebrowser" of FMCB-Configurator, you must type the name manually in there anyway.


Perhaps we could have a "Template"... give the ELF name, and it fills out the the default paths of "mass:/BOOT/", "mc?:/BOOT/" and "mc?:/B?DATA-SYSTEM/" for you?

Can you explain that in another way? ^^

[JoeUser38]

I don't think so (old menu).
But I agree, that this is a useful option (already mentioned anywhere, or not?).

It also could pop-up a list, where all OSD-Items from 1-100 are listed (like in ule Pad-Path-Function).
Then there are many ways, to edit the list.
A move-item from-to option, or simply press "ENTER"-Button [ X/O ], to drag an item move to the item, where it should be and press "Enter"-Button again, to drop the item there.

There are so many ways (without old FMCB-Configurator/OSD-Item-Options-Menu), that I couldn't expect all.



First of all,... Where do you want to add OSDSYS?
mc? is available, if you browser for your ELF with SQUARE, instead of ENTER-Button.

There is a list of options at the bottom.

The other thing, to add ELF-Paths...
You need to do it manually, with the Texteditor in ule.
How would you do it else?
If you couldn't find the ELF through the "filebrowser" of FMCB-Configurator, you must type the name manually in there anyway.



Can you explain that in another way? ^^
Yes, of course it can be done on the PC, and probably easier, but there are times when you don't have one handy (I even know a few people that don't have one... made a Free MC Boot memory card for one of them last week. :) ). I'm just trying to think of ways to do anything you want with the configuration file using only the PS2. BTW, thanks, must have been blind not to see the Sqaure listed at the bottom.

On the OSDSYS, it seems it would not be needed... I just realized that any item will "fall through" to going to OSDSYS anyways.

On the "Template" idea I had... The "standard" entries all seem to follow the pattern of searching these locations
mass:/BOOT/
mc?:/BOOT/
mc?:/B?DATA-SYSTEM/
so it will find it wherever you have it stored. It seems to me that you could pick your ELF file, and then tell it to fill in the other two locations for you. Alternately, have it bring up a text input box, type in, say, "XMB", and have it fill it in as
mass:/BOOT/XMB.ELF
mc?:/BOOT/XMB.ELF
mc?:/B?DATA-SYSTEM/XMB.ELF

[TnA]

Hm,... Maybe like ule does it,...
instead of mc?, or mass, it could be e.g. "fmcb:/NAME.ELF".

"fmcb:/" =

mass:/BOOT/(NAME.ELF)
mc0:/BOOT/
mc1:/BOOT/
mc0:/B?DATA-SYSTEM/
mc1:/B?DATA-SYSTEM/
...


Btw.: You don't need a PC at all.
There is the ule-texteditor.
ule = unofficial LaunchELF

[suloku]

1st.:

Build like the menu, which switches the color for OSD-Items.

e.g.
Load from device: --> "mass" "mc0" "mc1" (the arrow selects the device)


2nd.: Another one,...


I don't really like second option, first one seems more suitable, but the popup may be indeed a quicker way for it...maybe we should make a poll for that?

Anyway I like it the way it is until I need more space on the main screen, all has its pros and cons.

It would be useful to be able to re-order the program list in the OSDSYS section... of course, to do this, we would need to see the return of the "old" menu for it; perhaps include it as an "Advanced" section?

This is funny, because this afternoon I was thinking about adding something like that.

The easies thing to implement this "entry copying" is to use one button to store the entry we want to copy (i.e. L2), then you browse with the arrows the entry where you want to paste and press another key (i.e. R2).

Maybe instead of copying it should "move" (it would be a matter of erasing the entries after they have been set to the new item).

I can add a prompt asking for entry overwrite, but that will take a little more work (just a little :p).

Also, I don't see a way to add an ELF with a path that does not exist, being able to add using the "mc?:" notation, or a way to add OSDSYS (maybe I'm just missing them somewhere?).

Cancel button clears the entry, square button maps to mc?, SELECT button sets OSDSYS (that won't work for osdsys items, it has no sense at all).

[TnA]

I don't really like second option, first one seems more suitable, but the popup may be indeed a quicker way for it...maybe we should make a poll for that?

Anyway I like it the way it is until I need more space on the main screen, all has its pros and cons.


Yepp. Fully agreed.
It was an idea for later, to save some space in main-menu. ;)


This is funny, because this afternoon I was thinking about adding something like that.

The easies thing to implement this "entry copying" is to use one button to store the entry we want to copy (i.e. L2), then you browse with the arrows the entry where you want to paste and press another key (i.e. R2).


Hrhr,... Looks the same to me, as I described.
(Only difference... I said "Enter"/X/O-Button for Drag&Dropping the files. :D)
But if you think the same way, it is nice (I don't care how, but IF it is implemented later.).
It wouldn't be necessary, but really cool stuff for easier user-handing.


Maybe instead of copying it should "move" (it would be a matter of erasing the entries after they have been set to the new item).


Yes, moving is a good choice (vs. copying thought...).


I can add a prompt asking for entry overwrite, but that will take a little more work (just a little :p).


Just looking forward. :)


...SELECT button sets OSDSYS (that won't work for osdsys items, it has no sense at all).

Yepp, that's right, it wouldn't make a sence, but in betas, it causes the OSD to crash, if you try it.
That is fixed and you also can reload OSD from OSD. ^^ lol

[JoeUser38]

...
Yepp, that's right, it wouldn't make a sence, but in betas, it causes the OSD to crash, if you try it.
That is fixed and you also can reload OSD from OSD. ^^ lol
Funny you should say that... I just put in a "Reboot PS2" pointing to OSDSYS before reading this post. Doesn't really "reboot", but it's as close as I've been able to come so far.

[TnA]

Yes as I said "reload". ^^
But I also wanted to write a sentence, that I think, it might be better if it reloads rom0:/OSDSYS.
I thought the same, maybe for "IGR" (load rom0:/OSDSYS on Button-Combination.).

But both isn't really necessary.
Next days are bug-fix-days only, I guess.

Just wait for Test-Reports and Videos on Net.

[suloku]

Funny you should say that... I just put in a "Reboot PS2" pointing to OSDSYS before reading this post. Doesn't really "reboot", but it's as close as I've been able to come so far.

You may be interested in this:

http://psx-scene.com/forums/434986-post3320.html

Simple app that reboots the ps2. BTW not that I think maybe it should reset iop...but fmcb does it for me so no need to worry :p

[eustolio]

ummmm...good work, suloku xdd ;)
(tu siempre en el ajo, xdd :D)

[suloku]

Version 1.2.2 - FMCB 1.7 compatible
-Return to loader was only working for mass and mc:/BOOT/ locations. Fixed.
-Added copy and paste OSD item. Over and OSD entry press L2 to copy it, browse to the entry you want and press R2 to paste. A prompt will show the current entry number and what it holds, press OK or CANCEL to decide overwriting.

http://psx-scene.com/forums/attachment.php?attachmentid=14599&stc=1&d=1221989160

[TnA]

Some users reported, that the configurator (1.2.1) destroys their files on mass.

What do you think about some "eye-candy"-options for Configurator (to define some things found in "Share your FMCB.CNF"-Thread ;) ).

[suloku]

Some users reported, that the configurator (1.2.1) destroys their files on mass.

Please expand that point. What do you mean by destroy? Which files? Do that happen with 1.2?

[urbigbro]

What do you think about some "eye-candy"-options for Configurator (to define some things found in "Share your FMCB.CNF"-Thread ;) ).
I second that idea! A separate screen that would list all the special characters supported by the PS2 BIOS would be awesome. I have partially documented the encoding SJIS in that thread and I have put all the .cnf files with the 1000 possibilities of ALT+Num7 combinations available. I'm not sure if ULE can actually support displaying the same characters though as I don't know what encoding it supports or if it would require a Japanese translation font to be used. From opening my .cnf in the latest uLE it doesn't seem to support any of the ALT+Num7 combinations.

[suloku]

ule uses its own font for character display, so what you see its all there is.

I dunno anything about character encoding nor how to handle that in C. I'll search some info about that.

[Bootlegninja]

ule uses its own font for character display, so what you see its all there is.

I seem to recall that it does and that there were issues of implementing the font from the bios as the reason behind that.

[suloku]

Version 1.2.3 - FMCB 1.7 compatible
-Fixed bug regarding ESR path config. It always mapped to mc?. Also selecting a file from B?DATA-SYSTEM dir lead to messing the first path of the first 3 OSD items. Thanks TnA for noticing.
-Updated CNF parser with that of uLaunchELF 4.29.

http://psx-scene.com/forums/attachment.php?attachmentid=14662&stc=1&d=1222874510

[kevstah2004]

What symbols can be added to the osdmenu?, I tried to make the full PS2 logo "PlayStation ® 2" but the "®" wasn't recognized.

[TnA]

THX for the update.
The bug in ESR-Path (mc?-bug) was noticed by someone other on ps2tools before (just to mention him/it. ;) ).

[suloku]

THX for the update.
The bug in ESR-Path (mc?-bug) was noticed by someone other on ps2tools before (just to mention him/it. ;) ).

More than noticing I wanted to say alert, but the propper word didn't come up at that moment :p

BTW It was all because of a copy-paste problem, I may have went to do something else when I pasted the code and I forgot to modify it.

[peat1980]

@kevstah:
I tried to make the full PS2 logo "PlayStation ® 2" but the "®" wasn't recognized.
This Works for me as TopDelimiter:
c0y-99r1.25PlayStationr0.00o004r1.252r0.00y+00

[kevstah2004]

@kevstah:

This Works for me as TopDelimiter:
c0y-99r1.25PlayStationr0.00o004r1.252r0.00y+00

I can't see the character set properly it's coming up as box with 0 & 1's
Also a suggestion for suloku could you please double the amount of letters available in configurator for the top and bottom delimiter because when I've made customized ones in notepad an then gone back to re-edit my config later with the configurator and saved it only takes into account the amount off letters it was originally set to.

[suloku]

Also a suggestion for suloku could you please double the amount of letters available in configurator for the top and bottom delimiter because when I've made customized ones in notepad an then gone back to re-edit my config later with the configurator and saved it only takes into account the amount off letters it was originally set to.

I don't understand your problem. What do you mean with "the amount off letters it was originally set to"?

[kevstah2004]

I don't understand your problem. What do you mean with "the amount off letters it was originally set to"?

When you type them in using the configurator. If I make a custom .CNF with more characters than the configurator can handle for the top and bottom deliminator next time I save with the configurator it chops off the extra characters so it uses the same amount of characters as if you'd typed them using the configurator.
Also version 1.2.3 has run into the problem again where it won't load off the osdmenu but will with the button launcher and uLE.

[JoeUser38]

I can't see the character set properly it's coming up as box with 0 & 1's
...
That's what it's supposed to show up as (assuming you mean in the post, not on the PS2). I just did a cut-and-paste of it into Notepad++, and they show up as the "BEL" character (ASCII 7, or Ctrl-G).

[kevstah2004]

That's what it's supposed to show up as (assuming you mean in the post, not on the PS2). I just did a cut-and-paste of it into Notepad++, and they show up as the "BEL" character (ASCII 7, or Ctrl-G).

?, I just get a black dot's.
In hex the rights reserved sign is AE?
.o004 = reserved sign how? do you have a character table?

[JoeUser38]

?, I just get a black dot's.
Yes, I just tried it in Notepad, and that is how it shows it. Notice, I said I tried it in Notepad++ in the previous post. Just to be sure, I pasted it into Notepad (showed as black dots), saved it, and opened it in Notepad++; they showed up as "BEL". That tells us that the black dots ARE actually the "BEL" character (exactly what you want).

[kevstah2004]

How does it distinguish between that then an a full stop?

[JoeUser38]

?, I just get a black dot's.
In hex the rights reserved sign is AE?
.o004 = reserved sign how? do you have a character table?
Take a look at this thread, that character is specifically mentioned in post #15:
http://psx-scene.com/forums/freevast/58935-share-your-freemcb-cnf.html

[kevstah2004]

Take a look at this thread, that character is specifically mentioned in post #15:
http://psx-scene.com/forums/freevast/58935-share-your-freemcb-cnf.html

lol, Alt+num7 my fingers aren't that long.

[JoeUser38]

lol, Alt+num7 my fingers aren't that long.
Actually, it doesn't mean Alt+NumLock+7, it just means Alt+(the 7 on the number pad). Or just copy and paste one from a post here, and copy and paste it as many times as you need from then on.

Edit:
I just realized you may have thought it meant Alt + n + u + m + 7! Great practice for playing piano!

[kevstah2004]

Actually, it doesn't mean Alt+NumLock+7, it just means Alt+(the 7 on the number pad). Or just copy and paste one from a post here, and copy and paste it as many times as you need from then on.
"Alt Gr" is the closet to the numpad and even then I have to stretch my fingers Alt is at other side of the keyboard near the windows key and Ctrl:badpc:

[JoeUser38]

"Alt Gr" is the closet to the numpad and even then I have to stretch my fingers Alt is at other side of the keyboard near the windows key and Ctrl:badpc:
Ah, I didn't realize... I take it you only have the use of one hand? That would definitely make it more difficult.

[kevstah2004]

Ah, I didn't realize... I take it you only have the use of one hand? That would definitely make it more difficult.

no, :lol: currently as you say i'm trying alt+numpad 7 + 00?
00?= numbers but it does nothing and I have to turn my fingers into the middle of the keyboard to reach the 1-0 numbers beneath the F keys.
http://img.photobucket.com/albums/v477/kevsta2004/keyboard.png

[JoeUser38]

no, :lol: currently as you say i'm trying alt+numpad 7 + 00?
00?= numbers but it does nothing and I have to turn my fingers into the middle of the keyboard to reach the 1-0 numbers beneath the F keys.
http://img.photobucket.com/albums/v477/kevsta2004/keyboard.png
Ah, I see... Now, take this with a grain of salt, because I haven't tried these codes myself, but this is the way I read it...

It's Alt+numpad7, then release that, you get the "special character" (ASCII 7), then just TYPE the rest, plain text.

So, to do the (R) character for the PS2 you could do

Press and release Alt+numpad7
Type o004 (that's the letter o, the two following are the number 0)

[kevstah2004]

When I release Alt+Num 7 it just does that BEL dot.

[JoeUser38]

When I release Alt+Num 7 it just does that BEL dot.
Ah, I just tried it on the PS2 on my end, and found that Alt+num7 is actually giving the wrong character (looked like some chinese or japanese character, followed by the 004).

To get the "BEL" symbol, do Alt+07 (don't hold down 0 and 7, but hold the Alt, and type 0 then 7 while still holding Alt). That, followed by o004 (no longer holding Alt) produced the (R) symbol on the PS2 as expected.

Edit:
Oh, you still use the numpad for this. Also, don't expect to see the (R) symbol on the PC. You won't, you see some symbol for that BEL, then o004.

[kevstah2004]

Guess I'll plugging my usb keyboard back into my ps2 then :rolleyes:
You doing this with uLE?

[suloku]

When you type them in using the configurator. If I make a custom .CNF with more characters than the configurator can handle for the top and bottom deliminator next time I save with the configurator it chops off the extra characters so it uses the same amount of characters as if you'd typed them using the configurator.

I thought FMCB was supposed to be limited to 80 chars. I tried manually adding 80 and 81 chars, both cases where handled ok with the configurator. I'll test it further.
Also version 1.2.3 has run into the problem again where it won't load off the osdmenu but will with the button launcher and uLE.

Again? What problem do you refer?

[guxtabo]

Maybe it a silly question, but could fmcb configurator handle all te symbols you are talking about in the next version?. I mean, registered colors and transparencies.

[kevstah2004]

I thought FMCB was supposed to be limited to 80 chars. I tried manually adding 80 and 81 chars, both cases where handled ok with the configurator. I'll test it further.


Again? What problem do you refer?

80? the configurator only let's me enter 33.
Two versions of the configurator including this one won't load off the FMCB osdmenu but it loads fine with the FMCB button launcher and uLE, I think it has something to do with the way you pack your ELF's didn't you mention it before when I said about it?

[Bootlegninja]

I don't know what your doing wrong, but all versions have loaded fine from anywhere on my ps2. OSDSYS or uLE, mc or USB. pick any combo and it loads on any version.

[kevstah2004]

It's only v1.1 and v1.2.3 that do it.

[Bootlegninja]

then you got one or more problems.

1. naming issue on your config file
2. your FMCB install is FUBAR.
3. This Alt+num7 stuff is screwing with the CNF too much and is negating any operability on some menu items.

[kevstah2004]

CNF_version = 1
Debug_Screen = 0
FastBoot = 0
ESR_Path_E1 = mass:/ESR_GUI_test2.elf
ESR_Path_E2 =
ESR_Path_E3 =
pad_delay = 3000
LK_Start_E1 = mc?:/BOOT/BOOT.ELF
LK_Select_E1 = mc?:/SYS-CONF/FMCB_CFG.ELF
hacked_OSDSYS = 1
OSDSYS_video_mode = PAL
OSDSYS_Skip_Disc = 1
OSDSYS_Skip_Logo = 1
OSDSYS_Inner_Browser = 0
OSDSYS_selected_color = 0x10,0x80,0xE0,0x80
OSDSYS_unselected_color = 0x33,0x33,0x33,0x80
OSDSYS_scroll_menu = 1
OSDSYS_menu_x = 265
OSDSYS_menu_y = 120
OSDSYS_cursor_max_velocity = 1000
OSDSYS_cursor_acceleration = 100
OSDSYS_left_cursor = >>
OSDSYS_right_cursor = <<
OSDSYS_menu_top_delimiter = c0y-99r1.25PlayStationr0.00o004r1.252r0.00y+00
OSDSYS_menu_bottom_delimiter = c0r0.60y+99Use o006/o007 to browse list.y-00r0.00
OSDSYS_num_displayed_items = 3
OSDSYS_Skip_MC = 1
OSDSYS_Skip_HDD = 1
name_OSDSYS_ITEM_1 = Codebreaker
path1_OSDSYS_ITEM_1 = mass:/Codebreaker v9.3 Original.elf
name_OSDSYS_ITEM_2 = Codebreaker + ESR
path1_OSDSYS_ITEM_2 = mass:/Codebreaker v9.3 + ESR.elf
name_OSDSYS_ITEM_3 = Codebreaker + HDLoader
path1_OSDSYS_ITEM_3 = mass:/Codebreaker v9_3 + HDLoader 0_8CP.elf
name_OSDSYS_ITEM_4 = Simple Media System
path1_OSDSYS_ITEM_4 = mass:/SMS Version 2.8 (Rev.5).elf
name_OSDSYS_ITEM_5 = Swap Magic v3.8
path1_OSDSYS_ITEM_5 = mass:/Swap Magic/Swap Magic Plus Coder v3.8/DVD_Swap_Magic_Plus_Coder_v3.8_Packed.ELF
name_OSDSYS_ITEM_6 = In-game Reset
path1_OSDSYS_ITEM_6 = mass:/IGR_mc.elf
name_OSDSYS_ITEM_7 = PGEN
path1_OSDSYS_ITEM_7 = mass:/PGEN151.ELF
name_OSDSYS_ITEM_8 = MC Loader
path1_OSDSYS_ITEM_8 = mass:/mcloader.elf
name_OSDSYS_ITEM_9 = FMCB Configurator
path1_OSDSYS_ITEM_9 = mc?:/SYS-CONF/FMCB_CFG.ELF
name_OSDSYS_ITEM_10 = HDLoader
path1_OSDSYS_ITEM_10 = mass:/HDLoader_v0_8CP.elf
name_OSDSYS_ITEM_11 = Zoneloader
path1_OSDSYS_ITEM_11 = mass:/Zoneloader v0.5b.elf
name_OSDSYS_ITEM_100 = uLaunchELF
path1_OSDSYS_ITEM_100 = mc0:/BOOT/BOOT.ELF

[JoeUser38]

Guess I'll plugging my usb keyboard back into my ps2 then :rolleyes:
You doing this with uLE?
No, you misunderstood... I was typing them in on the PC. I meant "tried it on my PS2" as in I verified the results of the .CNF file on the PS2.

[JNABK]

80? the configurator only let's me enter 33.


Yep, it will only do 33 chars.....over that needs to be done on the PC. I think thats was in the read me or the release thread.

[JoeUser38]

Yep, it will only do 33 chars.....over that needs to be done on the PC. I think thats was in the read me or the release thread.
Given that, it does seem to be a reasonable request to increase that limit, especially now that some will have longer ones with these codes.

[suloku]

33 Char limit is there because the function used is gotten straight from ule, and it has that limit. Also normall text input goes off the screen for so many chars, so I thought it was ok to leave that limit.
I'll look into expanding the popup to make it fit.

Still, I can't reproduce that error kevstah2004 is experiencing. I open the configurator, load your CNF, open the dialog, erase a char, accept, save the CNF, load it again and there are still all the chars but the one I erased.

Would you mind describing the exact procedure that chops your settings?

Also here is 1.2.3 packed with ps2-packer 0.4.4, I made sure i packed the same file as the one released, check if it loads OK at your ps2.

[peat1980]

My menu looks like this:
...
OSDSYS_left_cursor = c5o009
OSDSYS_right_cursor = c5o008
OSDSYS_menu_top_delimiter = c0y-99r1.25PlayStationr0.00o004r1.252r0.00y+00
OSDSYS_menu_bottom_delimiter = c4y+99r0.50o006 c8Auf c4o007 c8Abr0.00y+00
...
:lol:
Note cfg editing only works on pc for me. :(
If i edit it with configurator after transferring to my ps2 it deletes the  at the beginning of a new line an then shows weird numbers. :)

[kevstah2004]

33 Char limit is there because the function used is gotten straight from ule, and it has that limit. Also normall text input goes off the screen for so many chars, so I thought it was ok to leave that limit.
I'll look into expanding the popup to make it fit.

Still, I can't reproduce that error kevstah2004 is experiencing. I open the configurator, load your CNF, open the dialog, erase a char, accept, save the CNF, load it again and there are still all the chars but the one I erased.

Would you mind describing the exact procedure that chops your settings?

Also here is 1.2.3 packed with ps2-packer 0.4.4, I made sure i packed the same file as the one released, check if it loads OK at your ps2].

When you input more than 33 char's by making a custom cnf
in a text editor the next time you change one of the settings in the
configurator it deletes and chops off all the char's after 33 when you save so any custom made cnf has to be updated / maintained in a text editor if you plan to use more than 33 char's for the top or bottom deliminator .

This one loaded off the osdmenu fine :ups: what was the previous one packed with?
Can you do one with ps2-packer 0.4.5 (http://www.usaupload.net/d/jh1g7z81o0n) and ps2-packer-1.0rc2 (http://www.usaupload.net/d/rocvi2tw7xl) as well please just for test purposes, I missed the 1.0rc1 release.
Also move the keypad box under "Return" so it doesn't overlap like this pic unless your planning on adding more options. You could maybe have another box to the right of it as well to show the inputted text and leave the text after ":" blank for all the text editable options as well.
Sorry for the poor pic quality it's my camera hopefully you get the gist though.

[Flipmc]

Thanks for this yo.

[urbigbro]

Note cfg editing only works on pc for me. :(
If i edit it with configurator after transferring to my ps2 it deletes the  at the beginning of a new line an then shows weird numbers. :)
I have the same problem with my SJIS encoded .cnfs. If this were related to the 33 char limit, shouldn't it cut off chars at the end not the beginning? This particular problem happens on every line no matter how long when using the config prog on the 1.7b beta.

[suloku]

Getting up to date for the upcoming FMCB 1.8

-Updated CNF parser to FMCB 1.8's (handle's \7 char)
-Added new FMCB 1.8's entries.
-Added "FASTBOOT" to selectable items. Use select to set it (cycles with OSDSYS entry).

[suloku]

Only 2 things to note with the new configurator:

1- When setting it back to default {press SELECT} the new enter/version settings didnt change. {I didnt change any other settings, so other settings might not change either}

2- when deleting the cnf from the sysconf folder, then saving a fresh default cnf, the delimiters & cursors revert back to what the 1.7 looked like, except saying 1.8 instead.


This shall fit those two things.

[JNABK]

Yep...that did the trick! :)

[Bootlegninja]

Just one thing that I see that needs to be removed is the skip disc option since it's now merged with the fastboot option. :)

[dlanor]

Just one thing that I see that needs to be removed is the skip disc option since it's now merged with the fastboot option. :)
Unless you're talking about a newer test version than v1.8 beta test11 I have to disagree.

On my v7 the FastBoot option alone is enough to prevent the boot of an ESR disc in the tray, making the "Skip Disc Boot:" option redundant just as you say.

But on my v15 using identical settings still causes the disc in tray to be booted.
Not even a button-press set up for OSDSYS can prevent that disc boot.
(IMO an error, as a button input by user should override all else.)

The only way for me to reach the OSDSYS menu on my v15 PStwo, while having a disc in the tray, is to have both FastBoot set to OFF and "Skip Disc Boot:" set to ON. So on this model (and others with similar behaviour) both settings are still needed.

NB: As implied above, this was tested with FMCB_1.8_beta_test11

Best regards: dlanor

[TnA]

About switching both options at once,...
---------------------------------------------


I said it a month ago, or so. The easiest option, is to turn/switch both at once in the configurator (with a new switch) and not by the core (Only problem,... suloku needs to see a point why adding it, or open the source. :D).

I still don´t see, why it even should work this way. ^^
Why permitting it in the loader, when it can be done by the CNF?
...and why should an OSD-Hack turned on, when a loader-function is off or vice versa?

I understand why it maybe should work this way, if the Auto-Boot-ELF is set to OSDSYS (no sence, to have Fastboot and OSD-Skip-Disc on at once...).

It even could be the standard-config (Fastboot off, Skip-Disc on), cuz I don´t care to much about the changeable CNF-vars.
Everyone can change them back manually, but most noobs can´t even compile an ELF, which is why I care about if it is a (hardcoded) loader-restriction, or a CNF-Var-Change which is a 2Byte-Change for the CNF (and maybe some bytes in the installer will change, if you recompile it with a new [embedded] CNF...).

[Bootlegninja]

Unless you're talking about a newer test version than v1.8 beta test11 I have to disagree.

On my v7 the FastBoot option alone is enough to prevent the boot of an ESR disc in the tray, making the "Skip Disc Boot:" option redundant just as you say.

But on my v15 using identical settings still causes the disc in tray to be booted.
Not even a button-press set up for OSDSYS can prevent that disc boot.
(IMO an error, as a button input by user should override all else.)

The only way for me to reach the OSDSYS menu on my v15 PStwo, while having a disc in the tray, is to have both FastBoot set to OFF and "Skip Disc Boot:" set to ON. So on this model (and others with similar behaviour) both settings are still needed.

NB: As implied above, this was tested with FMCB_1.8_beta_test11

Best regards: dlanor

I forget which version it was implemented on, but my desription to jimmi was for it to default like this.

if fastboot is on, skip disc is automatically set to off.
if fastboot is off, skip disc is automatically set to on.

even though the skp disc option isn't there, I was hoping that is how it would behave.

it is one of the later tests that I suggested it on.

[suloku]

I already discussed this with jimmi and concluded to leave it as is.

That's because there's still some use to have the two options ON: when you insert a disc you may not want it to boot straight if you are in OSD, but still may want it to boot if inserted at power on.

(Only problem,... suloku needs to see a point why adding it, or open the source. :D).


Well, the idea was to clean it and remove not used ule parts from it (there may be some unused parts of the codig eating up space), but I've had no time to shrink it more, so I'll release it as is with the next non beta version so you all can mess all you want or change its colors :p

[suloku]

-Limited Enter and Version X/Y values to its higher values.
-Cross over an OSD item erases all it's values.
-Pasting over an empty OSD item won't ask for overwritting. Added button layout to the prompt.

Let's hope this is the last one ^^

[TnA]

Let's hope this is the last one ^^

I don´t think so. :lol:

[suloku]

Source included (was about time). It should be compiled with the same environment as ulaunchelf 4.16 (and up to current 4.30 I assume since I can compile 4.30).

-Added "OSDMENU" to configurable LK_?_E? entries.
-Added "OSDSYS" and "FASTBOOT" as configurable OSD items (press select to cycle).
-Added the 0x07 (\7) character to the virtual keyboard and made a font for it. It's represented by an inverted "L" (thus it looks somewhat like this "_|").
-Enhanced virtual keyboard to support up to 99 characters. It works, but the display has some bugs I haven't been able to solve yet, I can't succesfully erase the display of the second and third text lines (chars 34 to 66 and 67 to 99 respectively).

I hope I can solve the virtual keyboard problem soon, I've been more than an hour trying to figure it out with no result. I'm releasing this because the problem is related to the display, not to the actual input/output to the cnf file.

[TnA]

With source (complete, or part?). :)

THX suloku.
That´s a real feature, I was looking forward before (Num7-Support).
...and it should be also backward-compatible,... ^^

[TnA]

If I select one of the "Special Options" (OSDSYS, FASTBOOT, OSDMOD <-- I only tested the last one, but assume it matches to all...) and then use the "run"-command/press start, it goes to BSOD (I would say of course... But it maybe should just permit execution of those.).

Btw.:I hope, Num7-Support gets more expanded/userfriendly.

e.g. pressing a button on pad or visual keyboard, to reach another keyboard with Num7-Chars.

[suloku]

With source (complete, or part?). :)

Complete. In fact you could get ule 4.16 from there. It's all commented in order to be able to retrieve ule's removed features, such as hdd support.

Inside the "not used" dir you have all source file which aren't used atm, but in the used sources there are lots of commented non used ule functions or simplified versions of an existing function.

If I select one of the "Special Options" (OSDSYS, FASTBOOT, OSDMOD <-- I only tested the last one, but assume it matches to all...) and then use the "run"-command/press start, it goes to BSOD (I would say of course... But it maybe should just permit execution of those.).

This may have been there since the very first version. I'll make it prevent elf booting when one of those is selected.

Btw.:I hope, Num7-Support gets more expanded/userfriendly.

e.g. pressing a button on pad or visual keyboard, to reach another keyboard with Num7-Chars.

That may be a relative easy thing to do, but how many num7 chars are there? I'm not into enconding or anything, tell me which characters you want and I'll see what can I do.

[TnA]

Hm,... JAP&CH.

I´ll go and create the font for every sinlge char, if you want to.

There are so many hidden OSD-Functions.
Thought not only different chars, but also "colors per Item", X/Y per item, etc.


Edit: About source. Could it be included now in FMCBs source?
One Makefile for all. :D

[urbigbro]

The encoding is actually SJIS, not Chinese.

If SJIS is to be properly implemented there are some hurdles that need to be overcome.
1) We need to know the SJIS revision that is supported by the PS2 BIOS, or if it is a custom version, what characters are supported. Through my own testing in making the "Chinese" .cnf it appears that the BIOS doesn't use the latest revision as it won't display all the SJIS Kanji characters I tried to use.
2) A custom font that looks like the PS2 BIOS font and supports all the SJIS characters that the PS2 BIOS will display, needs to be made for uLE. (This has been partially done already)
3) The line spacing the PS2 BIOS uses for single and double byte characters needs to be able to be displayed the FMCB config preview.
4) An understanding of what type of method the PS2 BIOS uses to center items. Perhaps even a switch to use left or right justification.

I would be willing to help with item 1 if it turns out that the SJIS in the PS2 BIOS is indeed a custom version. Be warned as I understand Chinese, and really don't know anything besides the Kanji part of Japanese.

Haro has made a custom Japanese uLE font, but, it only uses Katakana, and I'm unsure if he still comes here. (http://psx-scene.com/forums/349007-post9.html)
If it turns out that in order to find out which SJIS characters the PS2 BIOS display requires trying them all. I'm willing to do so. I would request the help of at least two other forum members that have Japanese knowledge though, as the list huge:wow:


Some optional things that could be done to make the FMCB Config even more useful would be. ( I realize some or all of these ideas may not even be possible with uLE is the origin of your program.)

1) simultaneous preview of all lines that are populated (ascii art would be so much easier):D
2)WYSWYG display including font scaling, offset, etc.


In my exploration of Alt+Num7 codes I have posted the 1000 Alt+Num77o000-999, but only the first 20 or so are small enough to put in a virtual keyboard.

[suloku]

This is starting to feel like it's too much for me, I don't have the skills :doh:


Edit: About source. Could it be included now in FMCBs source?
One Makefile for all. :D

Probably not, as fmcb compiles on a diferent environment and it wouldn't be a good idea to merge both sources.

[jimmikaelkael]

I made the test on my environment, It was failing finding references to libjpg and libfileXio.
I added "-ljpg -lfileXio" to EE_LIBS var in your makefile and it compile just fine.

So the choice is yours ;)

EDIT:
I've just figured out that in fact it's my GsKit that was requiring these dependencies, because mine was compiled with libjpg support, and yours not... Resulting in a configurator ELF that was more than 300Kb (not packed) while yours is only 171Kb.

I've recompiled my GsKit without libjpg support, and now it compiles the configurator just fine without any changes to it, and the size still the same than yours.

And the surprise is that I've recompiled my FMCB installer ELF and the size drop down from 520kb packed to 458kb :)

[dlanor]

This may have been there since the very first version. I'll make it prevent elf booting when one of those is selected.
Mea culpa, I guess, since uLE too had insufficient testing for elf validity in some cases, which sometimes caused attempts by the code to launch invalid strings as if they were paths to valid elf files. This was fixed in uLE v4.22, as described in the following excerpt from the uLE docs.

LaunchELF v4.22 (2008.08.14)
-Fixed various bugs that could crash the RunELF function when called with improper device names or paths to non-ELF files. From now on on real launch attempts are made only after accessing the file and checking its ELF header.
It should be quite simple to add similar tests to the FMCB configurator or any other program using similar elf launching.

That may be a relative easy thing to do, but how many num7 chars are there? I'm not into enconding or anything, tell me which characters you want and I'll see what can I do.
I don't think he's really talking just about the obvious num7 uses, but all kinds of graphic characters which the OSDSYS menu is capable of rendering. As I understand it that is a HUGE number of possible characters, thus definitely too many to be handled by a simple virtual keyboard implementation like the current one. A new implementation would be needed with a table-driven method for paged access to various parts of such a character set.

Best regards: dlanor

[dlanor]

The encoding is actually SJIS, not Chinese.

If SJIS is to be properly implemented there are some hurdles that need to be overcome.
1) We need to know the SJIS revision that is supported by the PS2 BIOS, or if it is a custom version, what characters are supported. Through my own testing in making the "Chinese" .cnf it appears that the BIOS doesn't use the latest revision as it won't display all the SJIS Kanji characters I tried to use.
2) A custom font that looks like the PS2 BIOS font and supports all the SJIS characters that the PS2 BIOS will display, needs to be made for uLE. (This has been partially done already)
3) The line spacing the PS2 BIOS uses for single and double byte characters needs to be able to be displayed the FMCB config preview.
4) An understanding of what type of method the PS2 BIOS uses to center items. Perhaps even a switch to use left or right justification.
Making a program capable not only of rendering all characters and special codes exactly like the OSDSYS, and also capable of text entry and editing with support for all such special usage (both real SJIS and PS2-specific stuff (like the BEL code usage)), all this becomes a HUGE project in its own right, which can not be allowed to hold back the speedy updating of the FMCB configurator for those features we truly need.

Such a super-duper-eye-candy configurator should rather be developed as a separate project, as I honestly expect such a project to take a long time to reach any useful state (if ever). Until then, and for the normal configurator, simple entry of the BEL code itself, and maybe just a few of the characters used for the FMCB default strings, should be added to the (still simple uLE-style) virtual keyboard, but no more. Otherwise we risk having the development 'bogged down' by graphic rendition problems, which have very little to do with the real needs of FMCB configuration.

I would be willing to help with item 1 if it turns out that the SJIS in the PS2 BIOS is indeed a custom version. Be warned as I understand Chinese, and really don't know anything besides the Kanji part of Japanese.

Haro has made a custom Japanese uLE font, but, it only uses Katakana, and I'm unsure if he still comes here. (http://psx-scene.com/forums/349007-post9.html)
Unfortunately the font he made was (inevitably) very limited, like he says in the following quote:
i changed 0xA0~0xDF character to half-width-kana used with one of japanese code "shift_jis".
0xA0~0xDF means a grand total of 64 kana characters, as compared to the several thousands of kanji that real japanese texts may use. So true japanese support is really beyond the meaningful scope of programs like these, IMO. It is possible to achieve, but not with reasonable effort, and the development time would probably be considerable.

If it turns out that in order to find out which SJIS characters the PS2 BIOS display requires trying them all. I'm willing to do so. I would request the help of at least two other forum members that have Japanese knowledge though, as the list huge:wow:
It is a huge undertaking, which is why I'm opposed to making it an immediate goal for the 'regular' FMCB configurator.

In fact I think it would be a horrible waste of effort to undertake such work with just any single program in mind. Far better then to make a generic lib for handling the rendering and the user input and editing of text using these extended character sets, so that other programs too can make use of that lib.

Some optional things that could be done to make the FMCB Config even more useful would be. ( I realize some or all of these ideas may not even be possible with uLE is the origin of your program.)

1) simultaneous preview of all lines that are populated (ascii art would be so much easier):D
2)WYSWYG display including font scaling, offset, etc.
There's nothing wrong with those ambitions, except that they should be applied to some new project (call it an alternate FMCB configurator if you like), since we can not afford to have the main configurator held back for the length of time that such major reprogramming will require.


In my exploration of Alt+Num7 codes I have posted the 1000 Alt+Num77o000-999, but only the first 20 or so are small enough to put in a virtual keyboard.
Like I said above, I think it would be fine to make a limited extension of the existing virtual keyboard. That should be easy to do right away. But the full extent of your propositions above really require a separate project, so as not to interfere with the more immediate needs of FMCB for a continuously updated configurator.

Best regards: dlanor

[JNABK]

Its not the kind of 'eye candy' im into, but a separate app for configuring those OSD displays would be a cool new addition as an independant app.

Maybe named "OSD Configurator" would be an appropriate name. :D

[urbigbro]

I have started a thread to explore the PS2 BIOS SJIS display limitations in another thread. (http://psx-scene.com/forums/freevast/59842-exploring-sjis-display-in-the-osdsys-post441131.html#post441131)
Whatever results I and those who help me achieve will be posted there for whomever decides to make a "alternate FMCB config" program. This will be my last post about said subject in this thread. Thanks goes to all who decide to contribute.

[dlanor]

-Enhanced virtual keyboard to support up to 99 characters. It works, but the display has some bugs I haven't been able to solve yet, I can't succesfully erase the display of the second and third text lines (chars 34 to 66 and 67 to 99 respectively).

I hope I can solve the virtual keyboard problem soon, I've been more than an hour trying to figure it out with no result. I'm releasing this because the problem is related to the display, not to the actual input/output to the cnf file.
I had a look at this code today, and made some fixes that cured the problem.

Here is a memo file I kept while making the fixes:

------------------------------------------------------------------------------
The extension of the keyboard function to 99 chars (3 rows x 33 chars)
is bugged in the following ways.
------------------------------------------------------------------------------
In the display section up to 3 string segments of max 33 chars are copied from
the 'out' array to the 3 arrays 'output1', 'output2', 'output3' for display of
the 3 input text rows. But this copying is only performed for current string
length, and for any characters beyond that those three arrays could retain old
garbage. Those three arrays were also not correctly terminated before use in
printXY function calls, leading to various odd results. Fortunately at least
one of the arrays was ensured correct termination, which prevented the worst
error cases.

I fixed this bug by initializing the first char of each array to NUL, and
then copying the string segments conditionally using strncat function calls,
instead of array operations. And of course I also made room for the string
terminators by extending the length of each array to 34 chars instead of 33.
------------------------------------------------------------------------------
Position coordinates are erroneously generated for the entry cursor shown in
the displayed string. The Y coordinate is calculated based on the total size
of the current string, instead of being based on the current entry position
within that string. This will cause garbage outside the popup whenever backing
up to an earlier position in a long string, as the cursor then is drawn to the
left of the box, when it should have moved up to an earlier entry row.

This bug was simply fixed by replacing "strlen(out)" by "cur" in 5 places.
------------------------------------------------------------------------------
It should also be noted that the new keyboard routine does not enforce any
absolute string length limit (like the old one did at 33 chars), but instead
relies on the function call argument for the max limit to be less than or
equal to the absolue limit of 99 chars. Exceeding that limit must be avoided,
and that is now the responsibility of the calling code.
------------------------------------------------------------------------------
In addition to those fixes I had some problems compiling the code, as I had to add -ljpg and -lfileXio to the lib references in the makefile to make it work. And in the end I got an elf of almost twice the size of the one you got, also packed to twice the size of your packed elf. I think this is because of the same lib difference that jimmi mentioned earlier, which also allowed him to shrink elfs of other projects when he switched to a gsKit without jpg support.

I'll have to make some extensive testing before I make any similar lib switch though, as I can't risk any functionality loss in uLE. And I don't expect the uLE elf to shrink by that in any case, since it does make explicit use of both jpg and fileXio stuff.

I'm attaching the bugfixed "filer.c" for your configurator in a ZIP below.

Edit: And of course I found an editing error in filer.c after posting the attachment... :(
So here is a corrected version :)

Best regards: dlanor

[TnA]

I only tested the virtual keyboard in OSD-Settings now and the difference I first noticed is, that the line in the bottom-left corner (text-field) isn´t there anymore. :)

"Text-Field" looks properly done.

[dlanor]

I only tested the virtual keyboard in OSD-Settings now and the difference I first noticed is, that the line in the bottom-left corner (text-field) isn´t there anymore. :)

"Text-Field" looks properly done.
If you really want to see the differences the fixes make, then you should use the unfixed version to enter text into all three text rows. Then use L1 to back the entry cursor towards the start of row 2 and start deleting characters. Notice how the red cursor passes to the left of the keyboard popup, and how it becomes impossible to control your 'erase position' properly, since the visual feedback is wrong.

Another neat test is to start entering a three-row text and end it with Cancel, and then restart the name entry and look at all the nice garbage remaining in rows 2 and 3 from the last entry attempt. That garbage would not be combined with the real strings, but it would still be very confusing at times.

Those are the really bad symptoms eliminated by the fixes.

Best regards: dlanor

[TnA]

If you really want to see the differences the fixes make, then you should use the unfixed version to enter text into all three text rows. Then use L1 to back the entry cursor to the start of row 2 and start deleting characters. Notice how the red cursor passes to the left of the keyboard popup, and how it becomes impossible to control your 'erase position' properly, since the visual feedback is wrong.


lol I see. The red cursor is under my return-Button. ^^
If I press R1 again, I could see the cursor again in the virtual-keyboard, but the red-cursor also remains under return.



Another neat test is to start entering a three-row text and end it with Cancel, and then restart the name entry and look at all the nice garbage remaining in rows 2 and 3 from the last entry attempt. That garbage would not be combined with the real strings, but it would still be very confusing at times.

Those are the really bad symptoms eliminated by the fixes.

Best regards: dlanor

Ah,... It only clears the first line and second and third remains, like before pressing Cancel (it shows the same symbols here, instead of garbage).


With fixed filer.c, it passes both tests.

[suloku]

Lots of thanks for taking a look at it and even fixing it! I've been trying myself with no results, only odd displays.

Actually I even didn't notice the L1 bug, as I never tried to go off the screen to the left of the box, I thought that going off the screen behaviour was fixed alongside with the right side of the box.

I suppose this kinds of modifications are beyond my reach.

Mea culpa, I guess, since uLE too had insufficient testing for elf validity in some cases, which sometimes caused attempts by the code to launch invalid strings as if they were paths to valid elf files. This was fixed in uLE v4.22, as described in the following excerpt from the uLE docs.

It should be quite simple to add similar tests to the FMCB configurator or any other program using similar elf launching.

It was actually my fault. I added an exception for OSDSYS to the runELFfunction, but I didn't when I added FASTBOOT and OSDMENU.


I'll have to make some extensive testing before I make any similar lib switch though, as I can't risk any functionality loss in uLE. And I don't expect the uLE elf to shrink by that in any case, since it does make explicit use of both jpg and fileXio stuff.


I think we discussed this matter on one of the early versions of fmcb configurator you tested, as you couldn't compile it for the same reasons jimmi explained.

ule doesn't experiment any significant size change when compiling with my environment (not even a kb), so don't bother trying.

Until then, and for the normal configurator, simple entry of the BEL code itself, and maybe just a few of the characters used for the FMCB default strings, should be added to the (still simple uLE-style) virtual keyboard, but no more.

Actually the only other character used on FMCB default strings is the BEL char. The other ones are what they display as.

BTW here's the compiled beta6 + src:

Changelog:

-Fixed virtual keyboard bugs by Dlanor.

So as Dlanor suggested, it would be interesting to add some other useful characters to the virtual keyboard (there's room for 12 more at the BEL char row). If not, this should become the 1.3 unless further issues are found.

[dlanor]

----- snip ----- re: gsKit LIB dependency issues
I think we discussed this matter on one of the early versions of fmcb configurator you tested, as you couldn't compile it for the same reasons jimmi explained.

ule doesn't experiment any significant size change when compiling with my environment (not even a kb), so don't bother trying.
It is not for the sake of uLE itself that I want to fix this, but for the sake of being able to compile both uLE and the FMCB suite with a common lib setup, instead of having to either switch between two different ones, or add makefile patches.

I've decided to handle this not by making any further edits to the gsKit makefiles either, but simply by changing the 'setup.sh' bash script used to adapt libs for uLE. And I've also made a separate small bash script just for recompiling gsKit with the LIBJPG variable (and some others) unset, so that users can compile gsKit without those dependencies, and yet without having to remove those environment variables for real.

These scripts will be included with the next uLE release.

Best regards: dlanor

[jimhackthorn]

i got a idea would it be posable to make a skinable FMCB configurator either now for FMCB 1.8 or for the next FMCB release it is a lot like ule and if it can be skinable then the FMCB configurator should also be skinable also it would be better then looking at a plain white screen. let me know what ya think about this idea.

[g.t.o]

Hi :)

Firstly I wish to apologize for my bad English I am French.


I Come here to presented the freemcboot configurator 1.3beta 6 custom language and skin modified by Hackchip.
French translation by me :D

New:


1) Last day of global functions of uLaunchELF 4.30.
2) Add the "Load_External_Language" which was done in "Polo35", and adding the "loadSkin."
3) Read external file language "FMCB_CFG.LNG"

mass: / APPS / FMCB_CFG.LNG
mc0: / APPS / FMCB_CFG.LNG
mc1: / APPS / FMCB_CFG.LNG

4) Reading external file Skin "FMCB_CFG.JPG"

mass: / APPS / FMCB_CFG.JPG
mc0: / APPS / FMCB_CFG.JPG
mc1: / APPS / FMCB_CFG.JPG



I hope you enjoy this version. :)


Links to download the sources and elf. =>

http://www.4shared.com/file/75834290/ffd0a406/FMCB_Configurator_13beta6_Version_Custom_Language_ _Skin_source.html
ou
http://www.megaupload.com/fr/?d=OKDPTT5J

.

[Bootlegninja]

first up, hackchip didn't create the configurator. suloku did. hackchip has only modified sources to allow skinning and languages.

[g.t.o]

Yes, I know very well that suloku is the creator of the configurator. ;)
As I said my English is not very good.
I meant amended by hackchip.
Often, the language barrier is a source of misunderstanding. :(
I will correct my mistake.

[TnA]

Often, the language barrier is a source of misunderstanding. :(


Yepp, it is.
Bootleg also know it from elsewhere (me :D ).


Btw.: I like a release this way,... People know, it is no official version. He added a real feature and not just put his name on it + changed source comes with it.

This is more kind of contribution, than ripping out a logo or something. ^^
A thank you fly out to metagames-site/hackchip.

[JNABK]

Thanks GTO....hmmm.....i may have misjudged HackChip before, based on the little info ive read here about him taking credit as his own stuff.:oops::chinscrat

I will check this out and make some skins!:D

[victor_p1]

You can change any settings (resolution) in Mcboot to improve the image of the games.
I have mcboot 1.8 and a 82cm Samsung LCD but the picture is very bad to have something to do with the mcboot?
Excuse my English pessimo

[JNABK]

Free McBoot is only a launcher for homebrew apps, but does not do anything for how the games are displayed from the apps that you use to boot those games.

If all your games have an issue, try using a different cable or check the connections real good. Also check your console settings are correct for the cable your using and check the TV input settings are also correct.

[zsebes73]

Free McBoot is only a launcher for homebrew apps, but does not do anything for how the games are displayed from the apps that you use to boot those games.

If all your games have an issue, try using a different cable or check the connections real good. Also check your console settings are correct for the cable your using and check the TV input settings are also correct.

tud valaki magyarul : Hungary:):):)

[JNABK]

tud valaki magyarul : Hungary:):):)

lol, no im not hungarian.......:lol:

[victor_p1]

Problem resolved, buy a "cable of components" and amazing image on the ps2 do Lcd 32" im very happy and recomend all people play ps2 on lcd or plasma.
Mary Christmas for everione

Excuse my English

Free McBoot is only a launcher for homebrew apps, but does not do anything for how the games are displayed from the apps that you use to boot those games.

If all your games have an issue, try using a different cable or check the connections real good. Also check your console settings are correct for the cable your using and check the TV input settings are also correct.

[JNABK]

Im glad it was only a simple cable change and nothing worse....Happy Holidays to you too. :)

[Marvin pl]

Hi i'am new on this forum. First i need say is hello everyone. Second: my english is bad (i better read than write).

And my first question is... Why you using embed usb modules? I'm not sure, but 99% users using configurator after install fmcb, so i think you can simply use modules from mc?/SYS-CONF folder.

Btw:
if i'm wrong or is some other reason to dont do this. Can you add some option to load external usb modules?

I asking because i using some specific mass storages (kingston DT 2gb ,and Nokia N-gage).

Ps. I writing from phone browser, so if my post look wierd (some long space etc.). Sorry

[TnA]

And my first question is... Why you using embed usb modules? I'm not sure, but 99% users using configurator after install fmcb, so i think you can simply use modules from mc?/SYS-CONF folder.


They are already used. No internal/embedded USB-Drivers are in the Configurator.
Look at the changelog in between Versions.


Btw:
if i'm wrong or is some other reason to dont do this. Can you add some option to load external usb modules?


You certainly are, so no need to make the Configurator itself dependent on a CNF-Entry. ;)

[Marvin pl]

Yep. i found changelog ,and i download fmcb1.8 (prev. i use 1.6) and newest configurator. And it's work (after change usbhdfsd to older usb_mass.irx).

Btw. Thanks for reply, i use only phone for internet and i just dont read/downloading every news. So i just don't know about adding ext. modules. One more time Thanks.

[jadonr]

Is it possible to load an app from the Hard Drive using FMCB? In the FMCB Configurator, I noticed that only the following locations are available:
mass:/
mc?:/

Is there a way to change or add the HDD location? My memory card is getting too full and I would prefer not to have a usb driving hanging out the front all the time (small children tend to break them off :rant:).

Sorry if this has already been answered somewhere else.

[M tha MaN]

No, it can't

[JNABK]

Is it possible to load an app from the Hard Drive using FMCB? In the FMCB Configurator, I noticed that only the following locations are available:
mass:/
mc?:/

Is there a way to change or add the HDD location? My memory card is getting too full and I would prefer not to have a usb driving hanging out the front all the time (small children tend to break them off :rant:).

Sorry if this has already been answered somewhere else.

For loading apps from HDD, use uLaunchELF....

[Neto sk8]

hey men i need your help i want to put the mcboot on my ps2 how can i do it canyou give me your hotmail account please

[Bootlegninja]

Wouldn't every one benefit if they actually seen the problem and solution in the forums instead of hiding it in your email?

[JNABK]

hey men i need your help i want to put the mcboot on my ps2 how can i do it canyou give me your hotmail account please

You do realize this is a forum......we dont do emails for conversations. We discuss things right here. So first, try searching around the forum titles , then you will find answers much quicker than waiting for an email.:chinscrat

[fuzzymillipede]

Ok, I am having a REALLY weird problem. I am trying to create a new option to appear on the main menu in the Configure OSD part of FMCB Configurator. I add the option and then hit "Save to CNF" and then "FMCB Restart". But when it restarts, the option I added gets deleted! Why? I can't add anything now... And the really weird part is that I was able to add stuff before.

[dlanor]

Ok, I am having a REALLY weird problem. I am trying to create a new option to appear on the main menu in the Configure OSD part of FMCB Configurator. I add the option and then hit "Save to CNF" and then "FMCB Restart". But when it restarts, the option I added gets deleted! Why? I can't add anything now... And the really weird part is that I was able to add stuff before.
It's very hard to visualize what is happening to you, without seeing the CNF files for ourselves. But one thing that some people fool themselves with is that they configure something for a file they intend to add, and expect that menu entry to be visible even before the real file is added, which is not how it works.

FMCB always checks for the existence of an elf configured for the OSD menu, and if the elf is not found then that entry is not displayed (since there is no elf to be launched for it).

This also means that you can have a problem with USB devices being detected in a different order at a future bootup than they got when you inserted them during a config session. So if you use more than one USB device, you need to have them inserted at boot time before starting to configure their use in FMCB, to be sure of getting the paths right. And as far as I know the configurator only supports one "mass:" drive anyway (it was designed before the release of a multi-drive driver).

I'm not sure if any of the above applies to your problem, but these are some things that could make a newly configured OSD menu entry seem to 'disappear' in the next boot session. The entry should still exist in the CNF menu for those cases, though not working.

Another and much simpler common mistake is for the user to simply forget that the FMCB configurator does NOT auto-save changes when you exit the program. This must be done by using either of the explicit save commands:

"Save CNF to MC0"
or
"Save CNF to MC1"

(Depending on which MC you boot from.)

Best regards: dlanor

[fuzzymillipede]

I think I figured it out. I was saving my CNF to mc0, when for some reason I had an older CNF on my usb stick. I overwrote the old CNF on mass with the new one from mc0 and my addition appeared on the main menu.

[dlanor]

I think I figured it out. I was saving my CNF to mc0, when for some reason I had an older CNF on my usb stick. I overwrote the old CNF on mass with the new one from mc0 and my addition appeared on the main menu.
Yes, that makes sense. For the standard file searches of FMCB, both for CNF and for the predefined links, the mass: path has higher priority than the MC paths.

Personally I never use the USB device to store my normal configs, using only MC for those, which is why I didn't think of that possibility earlier. For myself I see the ability to put an FMCB CNF on a USB stick only as an emergency measure, when needed to override a broken CNF on MC. But I guess that's mainly a matter of personal taste in such things.

Best regards: dlanor

[peter bostwick]

hello all,

Does any one know a way to configure fmcb to boot in vesa or vga mode? 640x480 @60Hz or 800x600 @60Hz thanks

[TnA]

hello all,

Does any one know a way to configure fmcb to boot in vesa or vga mode? 640x480 @60Hz or 800x600 @60Hz thanks

Nope. FMCBs loader itself doesn´t support forcing other resolutions to the OSD, than PAL or NTSC.

You can use GSMode Selector, to force a V-Mode (also to FMCB and the hacked OSD).

[JIM BOX]

hi for anyone who wants a background image, Polo35 made this i just added engish to the readme a skinable fmcb configurator very easy to use