Solution to "Loading GUI String Table...FAILED"

Printable View

Show 50 post(s) from this thread on one page

06-05-2006, 04:08 PM
shuichinz

Quote:

Originally Posted by dlanor

I'm confused by your repeated reference to "+boot" as being the Dev2 partition. I have a DMS4pro myself, and it uses the Dev2 partition "__boot", and that is also the case for Dev2 as implemented for Matrix Infinity. I have never before heard of anyone trying to use "+boot", and I don't think that this can work with any available Dev2 firmware.

Secondly, I wouldn't rely on the ability of the Dev2 launcher of any mod-chip to launch MyPS2 correctly, as I know that it requires some special methods that may not be used by the mod-chip code (specifically "fakehost.irx").

You'll probably be better off starting some other launcher with Dev1/Dev2, and then use that to start MyPS2 from HDD. That has worked well for many others, including myself.

Best regards: dlanor

this is the fault of an afterdawn thread i read. *looks back* GRRRR making me sound uterly stupid

Quote:

Example:

hdd_boot_part = hdd0:__boot
hdd_boot_path = /myPS2/

Should be:

hdd_boot_part = hdd0:+boot
hdd_boot_path = /MYPS2/

anyways thanks for your comments. i will working hard to get myps2 to boot from dev2
06-05-2006, 04:27 PM
flamingo24

Quote:

Originally Posted by shuichinz

anyways thanks for your comments. i will working hard to get myps2 to boot from dev2

As I previously posted it is impossible to boot myps2 v1.2 directly from dev2...
06-05-2006, 04:29 PM
shuichinz

@dlanor

while booting directly off dev2 mode...

renamed the myps2.elf to boot.elf < wonder if thats the cause.

on booting my ps2 says "setting elf path to __boot/"

so it knows that its getting the files from there. but it completly ignores the config.dat file. hence why im having trouble. i hope this is resolved in the next myps2. version.

if myps2 looked for a config on the mc it would bloody fantanstic because i could then mount a rouge partition and tell it to get the gui files from there.
06-05-2006, 05:08 PM
senorlocksmith

Ok well i have followed all the instructions, i have given up on the hdd for now and just tried it on the mc. now i get it to pass the gui string table error. i had it make a partition on the hdd and then it goes in to parsing the gui or something of that sort and then black screen. can anyone tell me whats going on with that. Thanks in advance.
06-06-2006, 12:06 PM
evilwise

I also crash at "Loading of XML GUI files failed!" when loading from mc0: Been looking for help on these forums for a week.
06-06-2006, 07:48 PM
senorlocksmith

ok got it working. just had to check all my files were there in the correct spots on the mc. made sure my config.dat was correct no incorrect line spaces and all that jazz. and of course i heard that copying the fonts from the fonts folder to the one labeled fonts inside the skins/default dir will make a differance. now i said COPY not move so try that out. I didnt move mine but i just wanted it to work before i screw with it even more.
06-06-2006, 07:49 PM
senorlocksmith

Quote:

Originally Posted by senorlocksmith

ok got it working. just had to check all my files were there in the correct spots on the mc. made sure my config.dat was correct no incorrect line spaces and all that jazz. and of course i heard (btw this is written by someone else on another post so i am not claiming that i figured this out by myself, if i remembered his name i would give credit) that copying the fonts from the fonts folder to the one labeled fonts inside the skins/default dir will make a differance. now i said COPY not move so try that out. I didnt move mine but i just wanted it to work before i screw with it even more.

d
06-06-2006, 07:50 PM
senorlocksmith

crap i did it wrong. i ment to say that me figureing this out was becasue of someone elses post so i would give credit but i cant remember the name
06-06-2006, 07:55 PM
shuichinz

heres my working config file with a mount list if anybody wanted to know

thats booting into launchelf then into myps2 fully off the hdd in the __boot partition

Code:

scr_adjust_x = 0 scr_adjust_y = 0 scr_mode = 255 scr_screenshot = 1 scr_path = host:/ tbn_caching = 1 tbn_cache_path = pfs0:/THUMBCACHE/ net_enable = 1 net_ip = 192.168.0.10 net_netmask = 255.255.255.0 net_gateway = 192.168.0.1 net_dns = 195.50.140.114 net_smb_workgroup = WORKGROUP net_smb_debug = 0 ftp_enable = 1 ftp_port = 21 ftp_anonymous = 0 ftp_login = myPS2 ftp_password = myPS2 radio_cache_list = 0 part_mount_list = hdd0:__boot,hdd0:+MP3,hdd0:PGEN 1.1 lang_file = english.xml lang_charset = ISO-8859-1 skin_name = default hdd_boot_part = hdd0:__boot hdd_boot_path = /MYPS2/ time_timezone = 60 time_dst = 0

its not imposible to boot dev2 someone just needs to do me a HUGE favour and compile a version that gets it config file from the memory card. once that happens it will quite happily mount my __boot partition and load up the GUI

so if anyone out there can code i REAAAALLY would love a version that gets the config from mem card.
06-06-2006, 10:42 PM
dlanor

Quote:

Originally Posted by shuichinz

its not imposible to boot dev2 someone just needs to do me a HUGE favour and compile a version that gets it config file from the memory card. once that happens it will quite happily mount my __boot partition and load up the GUI

That is not the proper solution.

The real problem here is that there are 2 ways for a program to be launched from HDD, while myPS2 only supports one of them.

The one commonly used by homebrew uses the 'fakehost' IRX module, and this passes an argument to the launched program holding the launch path that for this case begins with "host:". When myPS2 sees this it will test for existence of the fakehost IRX in the system, and when that is found it will classify this launch as being on HDD. And ONLY then will the HDD-related variables in the CONFIG.DAT file be used.

The second method, used by Dev2, simply mounts the partition on pfs 0, and passes an argument holding the launch path that for this case begins with "pfs0:". This is not supported at all by myPS2, so it will ignore the HDD-related variables.

The proper solution would be to add a new test for the string "pfs0:", and when this is found to set the same flag as used for the other HDD boot method, so that the HDD-related variables will be used the same way too.

Unfortunately I think that all attempts to do this are doomed, however, because so far all my attempts to recompile myPS2 have broken part of its network support. (bye-bye Samba :()

If someone can solve that problem, then the Dev2 fix is a piece of cake.

Best regards: dlanor

Edit:
My earlier statements about argv for HDD launching were incomplete.
Apparently the Dev2 boot method of DMS4 sets argv[0] to be the full path of the ELF file, using raw hdd addressing => "hdd0:__boot\boot.elf". Such a path will not work as-is with any device driver, but will need to be split up and one part used to mount the partition as a PFS mountpoint, so that the other part (in this special case simply "/") can be used for accessing the launch folder through that PFS mountpoint.

Show 50 post(s) from this thread on one page