Solution to "Loading GUI String Table...FAILED" [Archive]

suram884

03-06-2006, 06:40 PM

There are two problems. First is the CR/LF characters, as dlanor noted. To solve this one simply download the program called UltraEdit32. Use that to edit your config.dat file. When you open up config.dat, it was ask you if you want to convert the file to DOS, select YES. It will only make it display the file properly but will not convert the file. When you click save, the file will be saved in UNIX format, which is how we want it. Add the two hdd lines at the end. But, before you save it you need to do one more thing...

myPS2 interperts the LF character as the end of the line, so you need to add an extra empty line at the end of the file. Position the cursor at the end of the last line and press enter. Just click save and you're all set.

Also, I've noted that some people have empty lines between their config parameters. One such person is darkarmyofone. ;) (I had to point you out since you were complaining about it so badly) myPS2 thinks that it's at the end of the file if it encounters an empty line. So do not leave empty lines between parameters.

Here is a visual:
http://img315.imageshack.us/img315/3255/myps2stringfailed9iz.th.jpg (http://img315.imageshack.us/my.php?image=myps2stringfailed9iz.jpg)

firehawk

03-06-2006, 07:31 PM

I'm currently using Vim to edit the configuration files. It does not ask to convert or anything like that, just add the lines and save. But Vim is not easy to use, you'll have to try it out for a while to get use to it.

darkarmyofone

03-07-2006, 12:06 AM

i wasnt complaining, i was trying to get help. dont make examples out of people unless its needed. and it wasnt in this case. thanks.

darkarmyofone

03-07-2006, 12:54 AM

anyways, i understand what your saying, but i cant seem to get ultra edit 32 to do what your asking. ive tried and tried many different things. i was wondering if you could post a predone config.dat using my partition names... i would appreciate it. if not thats alright. but i still aim to conquer this obstacle ;)

wallacee

03-07-2006, 05:15 AM

try notepad2 over at

http://www.flos-freeware.ch/notepad2.html

it has the correct line formattings in it

Neocronicum

03-07-2006, 06:59 AM

None of your points apply to the config.dat i created for darkarmyofone's system but it still didn't work. So there has to be some other problem in his case.

darkarmyofone

03-07-2006, 12:43 PM

i got ultra edit 32 to do exactly as u posted in the first post. i opened it, it asked me if i want to change it to dos. i did. i went and removed my line spacing. i also placed that blank line at the end just like you told me too. and then clicked save. and i still get the same error at the same spot... should my partition be pfs0 or +MYPS2 i guess in theory according to MYps2 those partitions are the same. it used to show up as pfs0, but when myps2 v1.1 or 1.2 came out they corrected it to display the real name "+MYPS2" so im now confused as to what i need to do now. i no longer have faith that my partition names are arranged correctly in my config.dat

my HD has the one partition on it that everyone else with MYPS2 has, pfs0 AKA whatever you named it, in my case +MYPS2. and DIRECTLY inside of that partitions root directory, like RIGHT when you open it is a folder called MYPS2. and that folder contains all of the Myps2 v1.2 shit, skins, fonts, myps2.elf, you know what i mean.

so it should be like

hdd_boot_part = hdd0:+MYPS2
hdd_boot_path = /MYPS2/

or

hdd_boot_part = hdd0:+pfs0
hdd_boot_path = /MYPS2/

or

hdd_boot_part = hdd0:+PFS0
hdd_boot_path = /MYPS2/

"not sure if its pfs0 or PFS0, im pretty sure its lower case.

any suggestions as to how i should write those two lines... or is the way i had it the way it should be? the first of the three examples is the way i have it and was told to write it.

i also checked to make sure that every single skin and media file for Myps2 was accounted for on my HDD "took FOREVER" but its all there in the proper places. so i know the integrity of the files are ok. the fucking think just wont load them... this is weird, can someone with a WORKING config.dat post it on here, like one that allows you yourself to launch myps2 from the hard drive. i'd like to compare it to my non functioning config.dat that i created by following this tutorial.

thnx guys.

suram884

03-07-2006, 03:26 PM

It is suppose to be like:

hdd_boot_part = hdd0:+MYPS2
hdd_boot_path = /MYPS2/

There might be a problem with having the partition and folder the same name. My myPS2 folder is located in a partition I created named +ELFs, and I also have a +MYPS2 partition which is empty right now, but I will fill it up with some media later.

My config looks like this:

hdd_boot_part = hdd0:+ELFs
hdd_boot_path = /myPS2/

On a side note, pfs0 is not a real partition. It is just a reference that gives easy access to the current mounted partition.

Neocronicum

03-07-2006, 03:38 PM

this is weird, can someone with a WORKING config.dat post it on here, like one that allows you yourself to launch myps2 from the hard drive. i'd like to compare it to my non functioning config.dat that i created by following this tutorial.
The one that attached to my post in the other thread did work for me. I created a partition and folder structure based on your description of your system and it all worked just fine. Perhaps you should try and delete your current partition and recreate it.

darkarmyofone

03-07-2006, 10:42 PM

im going to try changing the name of my myps2 folder to APPS and see if that works. if that doesnt work. im going to delete and recreate the partition. this is rediculous lol. i bet its something wrong thats right under my nose. theres no way ive dont this wrong. its been tried like well over 100 times and im knoledgable to the subject. lol, thats luck for ya.

thanx for the suggestions guys. im trying em out as i type.

darkarmyofone

03-07-2006, 11:44 PM

status report: FAILURE

i tried both of the fuggested methods. neither worked. i cant figure it out lol. im sure future versions of MyPS2 will accomodate such problems. i guess i could wait.. :-\ but someone did say they got my scenario to work... any chance u could re create it and send me the config.dat to compare and troubleshoot mine?

my partitions name is +APPS now

and the folder containing myps2 v1.2 is "MYPS2" located in the root of the +APPS partition. just like b4, but with different names. no luck :(

pettigrew95

03-08-2006, 02:34 AM

Ok so the fix worked i edited the lines with ultraedit and it got past the GUI String Table FAILED. However now its at the Welcome to myPS2 screen and it says Please wait while the program is loading. It just sits at this screen now and does nothing. What can be the problem now?? Im trying to run myps2 1.2 from the HD. here is my current config.dat file, don't mind in the config file:

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 = 0.0.0.0
ftp_enable = 1
ftp_port = 21
ftp_anonymous = 0
ftp_login = myPS2
ftp_password = myPS2
radio_cache_list = 0
lang_file = english.xml
lang_charset = ISO-8859-1
skin_name = default
time_timezone = 60
time_dst = 0
hdd_boot_part = hdd0:+FILES
hdd_boot_path = /MyPS2 2.1/

i do have an extra line under my hdd_boot_path so thats not the problem and also where it says hdd_boot_path = /MyPS2 2.1/ because on my HD i saved it in the folder titled that, i know its 1.2 it was my mistake so dont pay attention to that. Any help is greatly appreciated thanks!

Silvio6

05-18-2006, 05:47 AM

Hello,

here is my perfectly working config file content.

hdd_boot_part = hdd0:+MEDIA
hdd_boot_path = /MYPS2/

and the net configuration is as follows:

net_enable = 1
net_ip = 192.168.1.7
net_netmask = 255.255.255.0
net_gateway = 192.168.1.1
net_dns = (my ISP'dns ip address)

the rest of the file is the same as standard.

I had the same problem as you before, here is what I changed:

1_ Put ALL the files/directories that come with myPS2, i didn't include the content of the "docs" directory before, and maybe that was the problem
2_ I created the folder MYPS2 all caps without a space on my ps2 partition
3_ Used Ultraedit and even Notepad2 to be sure the config.dat is ok
4_ Connected my ps2 to my LAN each time I made a test.

Here is my working samba.xml
<shares>
<share>
<name>Share1</name>
<path>smb://MULTIMEDIA-PC/TEST/</path>
</share>
<share>
<name>Share2</name>
<path>smb://MULTIMEDIA-PC/MUSIC/</path>
</share>
</shares>

To make Samba work perfectly, i had to
1_ Disable netbios over tcpip on my PC (but now i can't see the other computers of my workgroup :mad: )
2_ Create the lhmosts file whith my computer's ip address and put it on the memory card (not on the harddisk)
3_Once i had MyPS2 run on my HD, I went on the configuration menu, and set the workgroup to my lan's workgroup. then restars ps2/myps2.

Hope this will help you, good luck !

Silvio6

urmele

05-21-2006, 02:16 PM

I had the same problems and finally it works out for me.
The only thing which i've done was to delete the content from the +MYPS2/
[because i had a complete backup from the elf file with all the folders in it and
i'm not sure if this may cause problems when i start the prog from MC]
folder on my 120GB Maxtor HDD (i couldn't delete the whole folder with ULaunch).
After that i created a folder called MYPS2/ on my MC (no special signs and all capital letters).

Then i copyed this:

boot/
fonts/
language/
logs/
shoutcast/
skins/
MYPS2.ELF
CONFIG.DAT
samba.xml

into it, and voula,it works (but don't ask me why).

dlanor

05-21-2006, 02:22 PM

I had the same problems and finally it works out for me.
The only thing which i've done was to delete the content from the +MYPS2/
folder on my 120GB Maxtor HDD (i couldn't delete the whole folder with ULaunch).
Of course you couldn't, because hdd0:/+MYPS2/ is not just a folder.
It is a partition, so no commands intended to modify normal folders will affect it.

Best regards: dlanor

urmele

05-21-2006, 02:41 PM

Of course you couldn't, because hdd0:/+MYPS2/ is not just a folder.
It is a partition, so no commands intended to modify normal folders will affect it.

Best regards: dlanor

It would be nice if you could also delete or create partitions on a HDD with
ULaunchELF, do you know a good program which i can use for it?

By the way, i also have a exact copy from MYPS2 in a subfolder from my HDD,
but i don't think this has anything to do with my working copy on the MC.

dlanor

05-21-2006, 03:30 PM

It would be nice if you could also delete or create partitions on a HDD with
ULaunchELF, do you know a good program which i can use for it?
Most people use the 'DMS HDD Format' tool. You can find it on any serious PS2 site (including this one of course). Just make sure to get the 48-bit version if you have a disk larger than 128GB. And avoid the ancient version 1.0 (You need v1.1).

By the way, i also have a exact copy from MYPS2 in a subfolder from my HDD,
but i don't think this has anything to do with my working copy on the MC.If the copy on MC is the one you launch, then it rules, but there are many different ways of using this stuff.

In my own tests I launch MyPS2 from HDD (not the +MYPS2 partition), without having any copy on MC, but that requires slightly different configuration.

Btw: Removing the +MYPS2 partition entirely is not a good idea if you intend to keep using the program, though you may want to remove it in order to replace it with one of different size.

Best regards: dlanor

urmele

05-21-2006, 06:10 PM

Btw: Removing the +MYPS2 partition entirely is not a good idea if you intend to keep using the program, though you may want to remove it in order to replace it with one of different size.

Best regards: dlanor

Thanks for your fast reply.
I have a 120GB Maxtor, so i'll try to use the normal version of HDFormat 1.1.
As for the MYPS2, i wish i could view JPG's with ULE or SMS, so i could delete
it, but as long as it doesn't work with my favourites, i'm stuck to it.

Have a nice day!

shuichinz

05-26-2006, 11:50 PM

this doesnt work ive tried and tried too boot off the harddisk

im using a DMS4 lite.

boot from HDD devo mode it boots to here.

ive tried so many different areas to put the gui in.

ok so heres whats going on.

i have my files in "+boot" the myps2.ef is renamed boot.elf

i made a folder in +boot called "myps2"

copied all files into the root of +boot and to "myps2" from the cd that boots fine with working samba

my config file looks like this.

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_debug = 0
ftp_enable = 1
ftp_port = 21
ftp_anonymous = 0
ftp_login = myPS2
ftp_password = myPS2
radio_cache_list = 0
lang_file = english.xml
lang_charset = ISO-8859-1
skin_name = default
time_timezone = 60
time_dst = 0
hdd_boot_part = hdd0:+boot
hdd_boot_path = /myps2/

dlanor

05-27-2006, 12:03 AM

this doesnt work ive tried and tried too boot off the harddisk

im using a DMS4 lite.

boot from HDD devo mode it boots to here.

ive tried so many different areas to put the gui in.

ok so heres whats going on.

i have my files in "+boot" the myps2.ef is renamed boot.elf

i made a folder in +boot called "myps2"

copied all files into the root of +boot and to "myps2" from the cd that boots fine with working samba
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

flamingo24

05-27-2006, 01:41 AM

dlanor

05-27-2006, 10:03 AM

@shuichinz

I am not sure why it doesn?t boot directly from dev2 since once the elf is executed it will look at the config.dat then locate and execute the xml files accordingly; my guess is it has issues booting from a system partition; It seems to ignore the hdd lines in the config.dat while booting from dev2
Yes, that is what I meant with my comment about:
special methods that may not be used by the mod-chip code (specifically "fakehost.irx")
Having studied the source code I've seen that the test for HDD booting relies entirely on the use of the "fakehost.irx" module by the launcher that starts MyPS2. This is the most common method used by homebrew browsers for launching applications on HDD, but it's not mandatory.

For a Dev2 launcher it's more natural to simply mount the partition as pfs0: and launch the application through its path on pfs0:, without using the fakehost module, and then MyPS2 will fail because it won't identify this boot method as related to HDD.

This is a known problem with myps2 and booting directly from dev2 is impossible at the moment, If you want to boot directly into myps2 use dev1 (mc0) this method works without issue...:)
True, but it's also wasteful of MC space, as MyPS2 isn't very compact compared to other programs of similar kind.

If you really want to boot myps2 from the hard drive I would recommend using uLaunchELF to launch into myps2 from the hdd...:cheers:
That's how I do it myself for testing MyPS2 (obviously ;)).

Best regards: dlanor

NewYerk

06-01-2006, 03:17 AM

After a lot of trying I have finally come so far that
myPS2 goes pass the Loadin GUI string..... trouble and I come to the part where it says it cant find a partion and ask if I want to create one. I do I do I DO want to create but the myPS2 (or the PS2 itself?) freeze and I cant do anything.

I boot uLaunchElf (gosh it was simple and easy to understand that little nifty prog) using Dev.2 and in uLaunchElf I boot myPS2.

This is how my config looks like :
---------------------------
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.1.135
net_netmask = 255.255.255.0
net_gateway = 192.168.1.1
net_dns = 195.50.140.114
net_smb_debug = 0
ftp_enable = 1
ftp_port = 21
ftp_anonymous = 0
ftp_login = myPS2
ftp_password = myPS2
radio_cache_list = 0
lang_file = english.xml
lang_charset = ISO-8859-1
skin_name = default
time_timezone = 60
time_dst = 0
hdd_boot_part = hdd0:__boot
hdd_boot_path = /MYPS2/

---------------------------
And I used Notepad2 to create it.

(the net_dns is not mine btw)

I have all the files in the a _folder_ called /MYPS2/ on __boot, including ELF itself. I would like to keep it this way since I dont have space enough on my MC.

I did try to create a partion called "myps2", but it still freezes (froze? bad english). I did however not change anything in the CONFIG.DAT after I created that partion since I thought that myps2 itself would "see" that I have a myps2 partion and therefor not ask if I want to create one.

I have google'd and search this forum but I cant find anything related to this.

Help!!!

*EDIT:

I changed to "hdd_boot_part = hdd0:+myps2" but doing so I got the Loading GUI error again..

**EDIT:
I renamed the "+myPS2" to "+MYPS2" (lower/uppercase) and kept the both hdd_ -settings as "__boot" and "/MYPS2/" and it did find that partion and I got passed the screen asking for if I want to create a "+MYPS2". But well pass that screen nothing happens. All I see is the backgroundimage and nothing happens when Im pressing any button on keypad.

NewYerk

06-01-2006, 05:56 AM

*UPDATE
I changed the net_dns to 0.0.0.0
and it works to use FlashFXP to ftp so I guess something is working.

Altho a lot of partions doesnt show up in FlashFXP, such as the games etc.
And there seems to be 4-5 partions with the same name for some reason.
And they are not in the /hdd/0/ but in /hdd/1/ with no possibility to mount
any of the partions to /pfs/.

NewYerk

06-03-2006, 05:31 AM

This is the status now.

The config looks like this
---------------------------
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.1.135
net_netmask = 255.255.255.0
net_gateway = 192.168.1.1
net_dns = 0.0.0.0
net_smb_debug = 0
ftp_enable = 1
ftp_port = 21
ftp_anonymous = 0
ftp_login = myPS2
ftp_password = myPS2
radio_cache_list = 0
lang_file = english.xml
lang_charset = ISO-8859-1
skin_name = default
time_timezone = 60
time_dst = 0
hdd_boot_part = hdd0:__boot
hdd_boot_path = /MYPS2/

---------------------------

I renamed the "+myps2" partion to "+MYPS2" (thanks dlanor) and therefor I
dont get the question if I want to create a new partion, where it earlier froze.
Now I dont get that question but it still freeze up. All I can see is the background. I can ftp to the ps2 so I guess something is working.

So the current problem is still the same but I just came a (very) little bit further.

dlanor

06-03-2006, 01:36 PM

scr_mode = 255
That is the only major diff from my own CONFIG.DAT, where I have:
scr_mode = 2

I'm not sure what those codes mean though, so it may just be the common difference between PAL (which I have) and NTSC, but I'd expect you to have PAL as well, unless you have imported an NTSC console.

I renamed the "+myps2" partion to "+MYPS2" (thanks dlanor) and therefor I
dont get the question if I want to create a new partion, where it earlier froze.
Now I dont get that question but it still freeze up. All I can see is the background. I can ftp to the ps2 so I guess something is working.
The FTP server is probably started when the program processes the FTP section of CONFIG.DAT, but apparently something goes wrong a little later.

As I recall, one of the stumbling blocks with this config file is that the program is rather picky about some silly stuff. So line endings must be of type CR+LF (normal for most Windows editors), and must also have an extra empty line at the end. Does your file have that ?

Best regards: dlanor

NewYerk

06-04-2006, 05:58 AM

That is the only major diff from my own CONFIG.DAT, where I have:
scr_mode = 2

I'm not sure what those codes mean though, so it may just be the common difference between PAL (which I have) and NTSC, but I'd expect you to have PAL as well, unless you have imported an NTSC console.

I do have a PAL so I will try this out after I finnished typing.

As I recall, one of the stumbling blocks with this config file is that the program is rather picky about some silly stuff. So line endings must be of type CR+LF (normal for most Windows editors), and must also have an extra empty line at the end. Does your file have that ?

Best regards: dlanor

Im not sure what CR+LF means but I understand that it has something to do with what kind of format the program I use for editing the config saves the file as. I copied the last to lines in the config straight from the readme.html wich may not be the correct format. And also, when opening the config (I use Notepad2 since it was suggested in a thread) the spacing between the commandlines differs from what I have pasted here. I am not sure how to get
the right spaceing between the " hdd_boot* " and the "=". I simply copied the spaceing between the other lines in the config (I hope you understand me here) and pasted it between the " hdd_boot* " lines and the "=" so it matches with the other lines.

Thanks for your reply, I will try it out now and post the result. :)

NewYerk

06-04-2006, 06:09 AM

Changing the "scr_mode" did not help, still freeze at the same place.

I will try to get it to run from the MC now.

dlanor, could you please send me your working config so I can eliminate the
problem depending on CR+LF. Would be highly appriciated ;)

Thanks!

NewYerk

06-04-2006, 06:43 AM

Works like a charm from the MC. Only problem seems to be that the controler dont work in some programs I launch from MYPS2. Doesnt really matter..

I still want to run it from the hdd tho since I dont have much space left on mc (actually had to remove a lot of nice saves :cry: I know I could have transfered them first but I didnt want get into all that).

I read in some forum that I needed to unpack the myps2.elf to be able to run it?
Any thoughts on that?

shuichinz

06-05-2006, 03:59 PM

ok ok i think i figured out the myps2 boot from dev2 on hdd.

mounting the partition your booting from? ie this "__boot" partition:crazy: :p

shuichinz

06-05-2006, 04:08 PM

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

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

flamingo24

06-05-2006, 04:27 PM

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...

shuichinz

06-05-2006, 04:29 PM

@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.

senorlocksmith

06-05-2006, 05:08 PM

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.

evilwise

06-06-2006, 12:06 PM

I also crash at "Loading of XML GUI files failed!" when loading from mc0: Been looking for help on these forums for a week.

senorlocksmith

06-06-2006, 07:48 PM

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.

senorlocksmith

06-06-2006, 07:49 PM

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

senorlocksmith

06-06-2006, 07:50 PM

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

shuichinz

06-06-2006, 07:55 PM

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

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.

dlanor

06-06-2006, 10:42 PM

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.

Thumps

06-27-2006, 02:59 PM

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

I have managed to recompile a new version of myPS2, I wanted to add the ps2link.irx. Although I had to build a seperate version of the ps2sdk to get myPS2 to compile properly it works and I've managed to add ps2link support and fix an error in the sort by name feature.

I'm not sure the problem with booting off hard drive, I've been doing it for awhile. I simply copied all myPS2 files to the hdd0:+MYPS2 partition and use the config settings of

hdd_boot_part = hdd0:+MYPS2
hdd_boot_path = /

that way I can load myPS2 from elflauncer and I don't have to keep anything except elflauncher on my mc.

if you need a special copy of myPS2 compiled let me know, I'll see what I can do.

Mike

dlanor

06-28-2006, 05:48 PM

I have managed to recompile a new version of myPS2, I wanted to add the ps2link.irx. Although I had to build a seperate version of the ps2sdk to get myPS2 to compile properly it works and I've managed to add ps2link support and fix an error in the sort by name feature.
I think you've misunderstood my earlier problems. I too can recompile myPS2, and in most respects it works fine. It's just that the Samba networking is broken in these versions, giving no response whatever.

I'm not sure the problem with booting off hard drive, I've been doing it for awhile.
No. From your descriptions you have been launching it from HDD, after booting another program from MC. This is a Dev1 type of booting (or possibly exploit booting).

The problem I was posting about had to do with Dev2 type booting (modchip starts ELF directly from HDD). This is much trickier, as there are NO specifications for how it is to be done properly, and we can't rely on different chip manufacturers to have implementations that are even similar to each other (and we really need them to be identical). :(

I simply copied all myPS2 files to the hdd0:+MYPS2 partition and use the config settings of

hdd_boot_part = hdd0:+MYPS2
hdd_boot_path = /
That is an incorrect method which leads to other errors. When launched from HDD myPS2 will automatically want to mount two PFS partitions. One is 'its own' partition "+MYPS2", and the other is the partition named in "hdd_boot_part", and the original code does not check for the case where these two are identical.

So if they are identical, this will result in an attempt to mount the same partition twice, using two different mount points, and the second attempt will always fail. This is likely to mess up the mounting list, making correct access to additional partitions fail (at least that's the effects it had in my earlier tests). Naturally it should be possible to add new code to fix those problems, and maybe you've already done so. (?)

that way I can load myPS2 from elflauncer and I don't have to keep anything except elflauncher on my mc.
That's an excellent way of doing it, and similar to my own, but it doesn't address the problem of Dev2 booting at all.

To be honest, I don't see any real need for Dev2 booting, since any chip capable of it is also capable of Dev1 booting, and that has many other advantages too. (Allows simpler 'back to browser' implementation for other apps, such as SMS and PS2MP3.)

if you need a special copy of myPS2 compiled let me know, I'll see what I can do.
Well, if your recompiled myPS2 still has a fully functional Samba interface, then I'm definitely interested, as that's one thing I haven't been able to get here.

Best regards: dlanor

Thumps

06-28-2006, 09:09 PM

I think you've misunderstood my earlier problems. I too can recompile myPS2, and in most respects it works fine. It's just that the Samba networking is broken in these versions, giving no response whatever.

Yes, the version I managed to compile does work with samba, The whole reason I wanted to play with myPS2 in the first place is for samba. I have 2 linux servers that offer several samba mounts. So all my mp3's, photos, personal work is only available to samba or NFS.

No. From your descriptions you have been launching it from HDD, after booting another program from MC. This is a Dev1 type of booting (or possibly exploit booting).

The problem I was posting about had to do with Dev2 type booting (modchip starts ELF directly from HDD). This is much trickier, as there are NO specifications for how it is to be done properly, and we can't rely on different chip manufacturers to have implementations that are even similar to each other (and we really need them to be identical). :(

Ahh ok, I wondered about that. I don't have a modified ps2 myself. I loaded the exploit onto my memory card using the AR network update method. I have the mod chips sitting on my desk but never installed them because all I wanted was the ability to really play with my ps2 from a developers point of view.

That is an incorrect method which leads to other errors. When launched from HDD myPS2 will automatically want to mount two PFS partitions. One is 'its own' partition "+MYPS2", and the other is the partition named in "hdd_boot_part", and the original code does not check for the case where these two are identical.

So if they are identical, this will result in an attempt to mount the same partition twice, using two different mount points, and the second attempt will always fail. This is likely to mess up the mounting list, making correct access to additional partitions fail (at least that's the effects it had in my earlier tests). Naturally it should be possible to add new code to fix those problems, and maybe you've already done so. (?)

Yeah I was wondering about that myself. It wouldn't be the first time I've taken the hard route to get something done :banghead: . Although in my case it seems to work perfectly, I can access the other mount points using the pfs1..pfs2 and the myPS2 partition is mounted on pfs0 without any issues.

Considering I come from the Unix world. I'm used to multiple mount points and partitions and from the way I read the code the hdd_boot_part refers to the partition you're booting from and the hdd_boot_path refers to the path for that partition. Because the hdd0:/+MYPS2 gets mounted as pfs0: the path becomes root. Although the logic might be flawed for the ps2 world it appears to work properly. I have full support for hard drive partitions and no error messages appear.

That's an excellent way of doing it, and similar to my own, but it doesn't address the problem of Dev2 booting at all.

To be honest, I don't see any real need for Dev2 booting, since any chip capable of it is also capable of Dev1 booting, and that has many other advantages too. (Allows simpler 'back to browser' implementation for other apps, such as SMS and PS2MP3.)

Well, if your recompiled myPS2 still has a fully functional Samba interface, then I'm definitely interested, as that's one thing I haven't been able to get here.

Best regards: dlanor

Thank you, I just wanted to have it on my hard drive and not the memory card considering that I didn't use a packer while recompiling myPS2 the binary is over 3 megs and I would like to have game saves on my memory card not just myPS2. I can understand the need for Dev2 booting. It would be much nicer to boot directly then stick a CD in the ps2 or having to boot from the memory card. I have considered doing something similar for my kids ps2, I dont really want to allow them access to the elf launcer.

And yes I have support for Samba on my compiled version of myPS2, but it did require me to recompile the entire ps2sdk and supporting irx's. Although having been working with GCC for over 10 years on the unix side of the world, I'm no stranger to makefiles or build environments.

Take Care,
Mike

Thumps

06-28-2006, 10:39 PM

That is an incorrect method which leads to other errors. When launched from HDD myPS2 will automatically want to mount two PFS partitions. One is 'its own' partition "+MYPS2", and the other is the partition named in "hdd_boot_part", and the original code does not check for the case where these two are identical.

So if they are identical, this will result in an attempt to mount the same partition twice, using two different mount points, and the second attempt will always fail. This is likely to mess up the mounting list, making correct access to additional partitions fail (at least that's the effects it had in my earlier tests). Naturally it should be possible to add new code to fix those problems, and maybe you've already done so. (?)

Actually after a little review. I found the source version available on svn does check if the two mount points are identical. During the start myps2 will check if it's being booted from it's own +MYPS2 partition and avoid mounting it a second time. in that case the elf path is set to pfs0: plus the boot_path.
In my example pfs0:/
That way when the config file is read it's read as the elf path plus "CONFIG.DAT". or pfs0:/CONFIG.DAT

.. ok getting back to booting directly from a mod chip..

From what i understand the issue is when setting the boot mode. Now most of this might be way off topic, if so I apologize. I am new to the ps2 development scene so bear with me.

It seems the boot method depends on the argv[0] or how the mod chip called the myPS2 application. It could be called as host:/ or hdd0:/ or possibly pfs0:/. The hdd0:/ and psf0:/ versions are not checked for by myPS2. so if we check for those boot methods we could set myPS2 to boot correctly. That wouldn't be hard to do at all.

the host:/ is what elf launcher seems to do and ps2link which leads to the check for the fakehost module to find out if myPS2 is getting booted by ps2link or a launcher. If the mod chip is loading myPS2 without the fakehost module we have a problem. Either we have to drop support for booting using ps2link or we have to find another way to figure out how myPS2 is getting booted.

That's just my newbie views on the myPS2 loading issue, but if we can get enough information on how the modchips load myPS2. Support could be added. The only issue is my version of myPS2 does support ps2link, although I'm adding it as a optional module similar to the ftp support. I want it so I can output debug messsages to my computer for any development. it would be available as a configure option of ps2link_enable though so that it could be turned off.

Mike

E P

06-29-2006, 03:37 AM

Thumps

06-29-2006, 12:14 PM

Hum, this all sounds interesting. Especially now since I just finally got SMB to work.:) It works with Slax linux here. Windows XP Pro just couldn't cut it. Now if only I could tear myself away from Slax. Got my printer working with CUPS yesterday and now myPS2's SMB with Samba. Maybe I'll hit the lottery tomorrow.:lol: Linux a solution indeed.:)

lol yeah, I have 4 Linux systems myself. I wouldn't network without them.

Dlanor, I should now be able to help you to some capacity.:) All my tools are still on this XP machine so I'll have to shift Slax over to a different PC so I can continue to use this one for development.

Anyway I never did compile myPS2 but maybe now I should try to see if it's a packer issue as Thumps seems to believe.

Actually thats not correct, I had trouble getting ps2-packer to compile, so I couldn't test it. However today I did manage to test it and a ps2-packed version of myPS2 works with samba. I believe its a loader problem based on how the modchip loads myPS2. The version I have compiled will test for being booted straight from HD and from pfs0:/ hopefully by today I'll be able to post my test version so someone else can either confirm or deny it for me.

Mike

E P

06-29-2006, 03:20 PM

lol yeah, I have 4 Linux systems myself. I wouldn't network without them.
Well it wasn't as hard as I had earlier thought. In my networking computer science class, our team members were too afraid to deal with linux let alone Samba. I have done things with linux to some degree but only command based things like Oracle. Never really got to play around with it until now. I really wanted to get into linux the right way with Fedora but Slax does quite nicely. It's great to be able to take an OS with you with Slax on a stick.

Actually thats not correct, I had trouble getting ps2-packer to compile, so I couldn't test it. However today I did manage to test it and a ps2-packed version of myPS2 works with samba. I believe its a loader problem based on how the modchip loads myPS2. The version I have compiled will test for being booted straight from HD and from pfs0:/ hopefully by today I'll be able to post my test version so someone else can either confirm or deny it for me.
Dlanor and I use the precompiled binaries of ps2packer from here (http://www.nobis-crew.org/ps2-packer/). Although now that I have thought about it maybe our older ps2dev environment may be a factor. I don't know but I guess the only way to find out is to compile it myself. I didn't really care before since SMB didn't work but now that I got it working with Slax everything has changed.:)

flamingo24

06-29-2006, 04:02 PM

there is another issue switching skins while running myps2 from the hdd, when I try and switch a skin running from my ps2 hard drive it drops to a bsod; :chinscrat if you can get myps2 to boot directly from dev2 this issue will need to be remedied.

lol yeah, I have 4 Linux systems myself. I wouldn't network without them.

I took a course in cisco systems and the actual use of samba is really not difficult weather it's through linux or windows (I have managed to use the myps2 samba without the imhost simply by changing the samba.xml from computer name to ip address after making some adjustments to my router settings) my in house systems are networked with windows since I play alot pc games ;)

Hum, this all sounds interesting. Especially now since I just finally got SMB to work. It works with Slax linux here. Windows XP Pro just couldn't cut it. Now if only I could tear myself away from Slax. Got my printer working with CUPS yesterday and now myPS2's SMB with Samba. Maybe I'll hit the lottery tomorrow. Linux a solution indeed.

:) awesome

dlanor

06-29-2006, 06:28 PM

----- snip ----- re: problems with recompiled myPS2 binaries
Yes, the version I managed to compile does work with samba,
Good. Then I'm very interested in seeing your sources.
But perhaps it would be best (before diving into those sources) for me to test one of your recompiled binaries, to ensure that it does work properly in my PC LAN as well as in yours.

The whole reason I wanted to play with myPS2 in the first place is for samba.
It's the same for me, though I do take every PS2 homebrew I find for a spin or two. But the Samba implementation is something I'd like to port into uLaunchELF as well, which is the main reason I've invested quite some time in experiments with myPS2.

I have 2 linux servers that offer several samba mounts. So all my mp3's, photos, personal work is only available to samba or NFS.
I don't run linux myself, but I did get the original myPS2 Samba implementation to talk to my Windows PCs without problems (one WinXPpro and one Win2K).

----- snip ----- re: modchip boot methods for MC (Dev1) and HDD (Dev2)
Ahh ok, I wondered about that. I don't have a modified ps2 myself. I loaded the exploit onto my memory card using the AR network update method. I have the mod chips sitting on my desk but never installed them because all I wanted was the ability to really play with my ps2 from a developers point of view.
As long as you have an HDD and networking, there's little real need for CD-R/DVD-R access, which is the main contribution of a modchip. The only things you'd really need it for are a few emulators that need ROM data files on CD, and a few games that don't work from HDL (so not really dev-related).

----- snip ----- re: problems I had using +MYPS2 partition for booting myPS2
Yeah I was wondering about that myself. It wouldn't be the first time I've taken the hard route to get something done :banghead: . Although in my case it seems to work perfectly, I can access the other mount points using the pfs1..pfs2 and the myPS2 partition is mounted on pfs0 without any issues.
I see, and I also noted your later post where you verified having found code that checks this identity correctly. That's very good, of course, though I must add that it didn't work for me, but that was quite a while ago, so possibly the code has been changed since then. Once I got it working with two separate partitions, I stopped experimenting with just a single one.

----- snip ----- re: booting other launcher on MC to start myPS2 from HDD
I just wanted to have it on my hard drive and not the memory card considering that I didn't use a packer while recompiling myPS2 the binary is over 3 megs and I would like to have game saves on my memory card not just myPS2.
I know, and in the case of myPS2 even packing is no big help, as it requires a whole folder tree besides the binary, and packing that stuff is out of the question as the program needs it unpacked. I never even considered putting this stuff on my own MC (even though it's a 32MB type), so I never used it from any other media than HDD.

I can understand the need for Dev2 booting. It would be much nicer to boot directly then stick a CD in the ps2 or having to boot from the memory card.
Actually a boot from HDD will often be much slower than a boot from MC, even though HDD is the faster medium. This is because an HDD boot requires loading drivers and scanning the partitions, and if you have a lot of games installed (like most people do ;)) the latter will take a lot of time. So for these cases an MC boot will be much faster.

I have considered doing something similar for my kids ps2, I dont really want to allow them access to the elf launcer.
I'm not sure if you've followed recent discussions in the uLaunchELF forum, but some of the latest changes allow you to program all menu buttons of uLE, so that you can remove access to both FileBrowser and configuration menu from the main menu. This leaves the kids only with those launch key buttons that you have chosen for them (using it as mc1 in your own PS2 to set it up of course).

Doing this will require modifying the CNF file in a text editor, but that should be no problem for you.

And yes I have support for Samba on my compiled version of myPS2, but it did require me to recompile the entire ps2sdk and supporting irx's. That is to be expected. We do the same kind of stuff for uLaunchELF too, since we have no way to update the SVN with some needed changes.

Although having been working with GCC for over 10 years on the unix side of the world, I'm no stranger to makefiles or build environments.
I haven't done much work on unix systems myself, but I've been around long enough to have a decent grip on most of this stuff too. So it should be enough for me if you explain any changes you made to the setup as supplied by ntba2.

Also, as I mentioned above, a good starting point for me is to simply test one of your recompiled binaries. Just to ensure that its Samba routines can talk to the PCs on my LAN, since that's what failed to work with those I recompiled.

Best regards: dlanor

dlanor

06-29-2006, 06:56 PM

From what i understand the issue is when setting the boot mode. Now most of this might be way off topic, if so I apologize. I am new to the ps2 development scene so bear with me.
Don't worry. You seem to understand this well enough already.

It seems the boot method depends on the argv[0] or how the mod chip called the myPS2 application. It could be called as host:/ or hdd0:/ or possibly pfs0:/. The hdd0:/ and psf0:/ versions are not checked for by myPS2. so if we check for those boot methods we could set myPS2 to boot correctly. Yes, that's the basic idea.

That wouldn't be hard to do at all.
I'm not so sure. At this point the IOP state is unknown, set up somehow by the modchip, with details unknown to us, and therefore not to be relied on (as chip manufacturers may differ).

I made some experiments with uLE, trying to load CNF from HDD at this stage, but ran into some odd problems. This often happens when trying to load drivers before a necessary IOP reset (specified in the loaded uLE CNF), as the PS2SDK drivers are mostly allergic to being loaded twice by the same EE application... :(

I'm not sure how this would affect myPS2 initialization, but we can't rule out similar problems until it has been tested thoroughly.

the host:/ is what elf launcher seems to do and ps2link which leads to the check for the fakehost module to find out if myPS2 is getting booted by ps2link or a launcher. If the mod chip is loading myPS2 without the fakehost module we have a problem. Either we have to drop support for booting using ps2link or we have to find another way to figure out how myPS2 is getting booted.
I disagree. It should still be possible to recognize all possible boot methods, as long as they all use argv[0] for the launch path. For the case of a DMS4pro chip (which I have), the Dev2 boot method is testable as:
"booted_Dev2 = !strcmp(argv[0], "hdd0:__boot/boot.elf");"

NB: I may have missed a slash separator there, as I can't check the debug info right now.

That's just my newbie views on the myPS2 loading issue, but if we can get enough information on how the modchips load myPS2. Support could be added.
Indeed. It may be tricky (remains to be seen), but it can be done.

The only issue is my version of myPS2 does support ps2link,
But that's really an unrelated issue. I don't see how this affects recognition of boot methods.

although I'm adding it as a optional module similar to the ftp support. I want it so I can output debug messsages to my computer for any development. it would be available as a configure option of ps2link_enable though so that it could be turned off.
Sure. I see no major problems with that.

Best regards: dlanor

dlanor

06-29-2006, 07:03 PM

Dlanor, I should now be able to help you to some capacity.:) All my tools are still on this XP machine so I'll have to shift Slax over to a different PC so I can continue to use this one for development.
Good, but I assume you'll have both those PCs active in your LAN then. This may help untangle some of the problems you had earlier, not being able to see Windows shares via Samba on myPS2.

Anyway I never did compile myPS2 but maybe now I should try to see if it's a packer issue as Thumps seems to believe.
I think you misunderstood that reference. I think he was just talking about the normal storage space problem when using large unpacked binaries on a small 8MB memory card.

Best regards: dlanor

Thumps

06-30-2006, 12:28 AM

I'm not so sure. At this point the IOP state is unknown, set up somehow by the modchip, with details unknown to us, and therefore not to be relied on (as chip manufacturers may differ).

ok, I didn't consider the IOP state at all. Although from what I have causually gathered, most applications stick libraries for io into it. hense the IOP name I'd guess lol. However if this version of myPS2 works for you, we can begin some furture tests.

I made some experiments with uLE, trying to load CNF from HDD at this stage, but ran into some odd problems. This often happens when trying to load drivers before a necessary IOP reset (specified in the loaded uLE CNF), as the PS2SDK drivers are mostly allergic to being loaded twice by the same EE application... :(

It makes sense there would be issues if you loaded the same module twice. If the loading code doesn't check that the module isn't already loaded you could end up with two identical functions at different addresses.

I disagree. It should still be possible to recognize all possible boot methods, as long as they all use argv[0] for the launch path. For the case of a DMS4pro chip (which I have), the Dev2 boot method is testable as:
"booted_Dev2 = !strcmp(argv[0], "hdd0:__boot/boot.elf");"

NB: I may have missed a slash separator there, as I can't check the debug info right now.

I think the point I was attempting to make was missed here. The source for myPS2 didn't test for hdd0: in argv. Therefore it didn't know it was booting off hard drive.

When myPS2 called the SetBootMode function to figure out how it was being booted it only checked for host, mc, usb and cd. If your modchip calls it as hdd0:__boot/boot.elf, myPS2 wouldn't know it's booting from hard drive.

I've added a test for this to the current code. Hopefully it might help in the dev2 booting. At the very least we can gather some more information, because I've added the argv[0] to the information myPS2 displays at start up. if we can gather this information from when it doesn't work we might be able to figure out why it's not working.

Just look for the following messages right when myPS2 boots.

Load Path:
SetElfPath:

Those two variables set the stage for how myPS2 attempts to boot.

But that's really an unrelated issue. I don't see how this affects recognition of boot methods.

Actually it was meant as more of a warning :) although it's available as a configure option and off by default. I've included the modified language fils and default theme file for the network settings to turn it back on if you want.

E P

06-30-2006, 02:33 AM

Good, but I assume you'll have both those PCs active in your LAN then. This may help untangle some of the problems you had earlier, not being able to see Windows shares via Samba on myPS2.
Yeah that's what I plan to also do especially since I managed to get both machines running slax to test smb. I had a one-way connection going so the shares do work properly with samba. XP and Slax networking should be far easier than dealing with Slax and 98. Network changes to Windows 98 SE can become very tedious with all the rebooting usually involved.

Anyway I used Slax to burn a Slax CD to run it on another machine and it worked. Now with my XP machine I have access to all the ps2dev tools and a more comfortable environment to work from.

I think you misunderstood that reference. I think he was just talking about the normal storage space problem when using large unpacked binaries on a small 8MB memory card.
Oh, yeah that was it.

Thumps

06-30-2006, 07:11 PM

there is another issue switching skins while running myps2 from the hdd, when I try and switch a skin running from my ps2 hard drive it drops to a bsod; :chinscrat if you can get myps2 to boot directly from dev2 this issue will need to be remedied.

ok, if I get any positive feedback about the myPS2 I posted, I'll take a closer look at the skin switching. Cause we have to keep those skins. BTW those skins in your sig are amazing. Thank You. I have found that trying to switch skins while playing an mp3 is a no no. Although I haven't had any problem switching skins from hard drive as all my myPS2 stuff is stored on the hard drive.

I took a course in cisco systems and the actual use of samba is really not difficult weather it's through linux or windows (I have managed to use the myps2 samba without the imhost simply by changing the samba.xml from computer name to ip address after making some adjustments to my router settings) my in house systems are networked with windows since I play alot pc games ;)

Yeah that's exactly what I did two. I just use ip addresses in my samba.xml file even though I do have a wins server on my network. I just found that myPS2 had issues with my dns and figured why bother trying to poke around I know the ip addresses off by heart.

Mike

Thumps

06-30-2006, 07:36 PM

Well it wasn't as hard as I had earlier thought. In my networking computer science class, our team members were too afraid to deal with linux let alone Samba. I have done things with linux to some degree but only command based things like Oracle. Never really got to play around with it until now. I really wanted to get into linux the right way with Fedora but Slax does quite nicely. It's great to be able to take an OS with you with Slax on a stick.

it's amazing how flexible Linux is sometimes. When I first used Linux the only none open source appliacation available was a early version of Netscape. There wasn't any samba support so I had to use ftp or appleshare to transfer files. Now my Linux system offers full samba support including domain logins.

Dlanor and I use the precompiled binaries of ps2packer from here (http://www.nobis-crew.org/ps2-packer/). Although now that I have thought about it maybe our older ps2dev environment may be a factor. I don't know but I guess the only way to find out is to compile it myself. I didn't really care before since SMB didn't work but now that I got it working with Slax everything has changed.:)

Darn, I wish I read that earlier, I ended up having a heck of a fight to get ps2-packer to compile. There was some issues with my native cygwin trying to compile it. Seems my version of cygwin didn't really like being compiled with ee code. Although thankfully in the end I won the fight and managed to get the whole ps2-packer installed and running. I know my ps2dev environment is taken directly off SVN. It's been updated a few times but still requires the patches included with myPS2.

Mike

dlanor

07-01-2006, 09:01 AM

ok, I didn't consider the IOP state at all. Although from what I have causually gathered, most applications stick libraries for io into it. hense the IOP name I'd guess lol.
That is the main purpose of it, but IOP memory is managed independently from EE memory, and there is no real standard for what the IOP contains when an application starts. Normally it does contain some basic drivers, including the one through which the application ELF was loaded, but not even that is certain, as the launcher may have made an IOP reset before passing control to the ELF code.

However if this version of myPS2 works for you, we can begin some furture tests.
It does work, including Samba access. But here's something really weird: After making that test I decided to make another, whose results left me flabbergasted.

:crazy:
The test version I recompiled back in March also works now.
With full Samba support!
:crazy:

I've tested that ELF, and variants of it, dozens of times before, without any Samba success at all. But now, all of a sudden, it works perfectly. I just don't get it...

----- snip ----- re: Problem with reinitialization of drivers after IOP reset
It makes sense there would be issues if you loaded the same module twice. If the loading code doesn't check that the module isn't already loaded you could end up with two identical functions at different addresses.
That's not the problem. An IOP reset cleans out the old IOP functions, so at that point you have to reload some IOP modules to be able to do anything. This includes the drivers to all IO devices you want to use.

The problem is that the PS2SDK libs for the EE processor will malfunction for the new incarnation of the IOP modules, since those EE libs only allow initializing a module once, and they have no idea that IOP reset can ever be performed. So most attempts to repeat initilization leads to no response at all (device won't work at all), or to suicidal insanity (device malfunctions badly, possibly crashing the application).

We've had to solve this problem for some devices, as we must be able to read CNF files before deciding whether or not to perform IOP reset in uLaunchELF. Those changes are included in our source releases. But for some other devices our changes don't work, such as the gamepad. If we use any of the pad access functions before performing an IOP reset, then the new pad initialization thereafter will malfunction. (And we still don't know exactly why...)

I've added a test for this to the current code. Hopefully it might help in the dev2 booting. At the very least we can gather some more information, because I've added the argv[0] to the information myPS2 displays at start up. if we can gather this information from when it doesn't work we might be able to figure out why it's not working.

Just look for the following messages right when myPS2 boots.

Load Path:
SetElfPath:

Those two variables set the stage for how myPS2 attempts to boot.
Unfortunately that's not much help with some DMS4 launch methods.

I just tried launching your ELF from the ToxicOS browser (works fine to launch uLE), but it just resulted in a garbled screen (with no sign of normal myPS2 output). This happens for any myPS2 ELF, so it's not just yours...

Trying it with the Dev2 launcher works better, but the result is still wrong.
"Load Path: hdd0:__boot/boot.elf"
"SetElfPath: hdd0:__boot/"
"Failed loading CONFIG.DAT"
"CONFIG.DAT must be"... and so on

Naturally, CONFIG.DAT was present beside the ELF, together with the usual myPS2 folder tree, so that was never the real problem. The problem is that you apparently attempt to use "hdd0:__boot/" as a valid path for accessing files, which it isn't. It can only be used for mounting. All file access must be made through PFS.

Best regards: dlanor

flamingo24

07-01-2006, 11:21 AM

Thumps

07-01-2006, 02:16 PM

Unfortunately that's not much help with some DMS4 launch methods.

I just tried launching your ELF from the ToxicOS browser (works fine to launch uLE), but it just resulted in a garbled screen (with no sign of normal myPS2 output). This happens for any myPS2 ELF, so it's not just yours...

Trying it with the Dev2 launcher works better, but the result is still wrong.
"Load Path: hdd0:__boot/boot.elf"
"SetElfPath: hdd0:__boot/"
"Failed loading CONFIG.DAT"
"CONFIG.DAT must be"... and so on

Naturally, CONFIG.DAT was present beside the ELF, together with the usual myPS2 folder tree, so that was never the real problem. The problem is that you apparently attempt to use "hdd0:__boot/" as a valid path for accessing files, which it isn't. It can only be used for mounting. All file access must be made through PFS.

I think you hit it right on the nail there.. it seems to be a chicken or egg problem. myPS2 needs to load it's config file to start up, let me see if I can't work up something newer to test.

ok here is a newer version that should check for being booted as hdd0: and set the elf path to pfs0:/ I'm not sure how well that'll work cause I can't test it. but it's worth a try.

Mike

Thumps

07-01-2006, 05:38 PM

@Thumps

I finally got a chance to test your myps2 beta; now it seems I can switch skins running from the hdd with this version (although it was not a priority in this release) :) the only trouble I ran into was after boot and making one skin change the second attempt will freeze at the activate skin dialog. this is an improvement from before since I am able to at least switch skins running from the hdd :D however, I did notice if I save the myps2 settings after switching to another skin it does not freeze! :dance:

samba works, still it doesnt seem to want to boot directly from dev2; since this version allows me to switch skins (hdd) I'm sticking with your beta...thanks...:cheers:

You're welcome, I'm glad it at least works better for you. I've been working with a few of the skins myself. It appears some act strange when loading. Although I haven't had any crashes while loading them from hard drive. I have found that some don't like to be loaded the BeOS one specifically can not be loaded from the default skin. All it does is add a blank character to the themes list and returns to the current skin. Although I don't think it's a hard drive problem per say. I have all my myPS2 files in the myPS2 partition and simply boot into that using the options

hdd_boot_part = hdd0:+MYPS2
hdd_boot_path = /

that way with the exception of the BeOS skin, I can switch skins all I want and haven't had a single crash.

hope that helps
Mike

Thumps

07-01-2006, 05:45 PM

dlanor

07-01-2006, 06:34 PM

I think you hit it right on the nail there.. it seems to be a chicken or egg problem. myPS2 needs to load it's config file to start up, let me see if I can't work up something newer to test.

ok here is a newer version that should check for being booted as hdd0: and set the elf path to pfs0:/ I'm not sure how well that'll work cause I can't test it. but it's worth a try.
I've tried it with Dev2 booting now and it doesn't work. It just crashes with garbage on screen.

This garbage takes the form of 10 evenly spaced and perfectly stable vertical bars, starting with a white one at the left edge, followed by alternate black and white ones, ending with a black one at the right edge of the screen.

None of those bars are purely white or black though, as they are also mixed with random dot garbage forming rectangular patterns, with each such rectangle having a width equal to that of the bars (and aligned to them), and a height of appx 1/16 of the screen height. But the brightness of this random dot garbage is very low, probably never exceeding 15% of the white bar level.

In all of this there is nothing that resembles normal character graphics, even garbled, so it is very doubtful if any text had been displayed at the point of crashing.

It all looks rather peculiar, but trying to draw any program related conclusions from these symptoms is probably hopeless... :(

What I think we see here is random initialization data of the dynamic RAM cells. Many DRAMs I've seen through the years have been designed with alternating cell sequences tending to pull low and high respectively, and I think it is this that causes the black/white bars.

The above was for a clean start from an enduring standby mode.

If I make a 'warm' reset after running other programs then the above will also be mixed with graphic remnants from the preceding programs. Thus I have seen at one and the same time graphic remnants from the uLE skin and the ToxicOS skin, mixed with the black-and-white bars. Since at least one of those skin remnants is two resets 'old' by that time, I think we can assume that the crash occurred before myPS2 initialized screen.

I almost forgot to add that the program works fine when launched from uLE in a normal manner, using the same ELF in the same place and with the same config files.

Best regards: dlanor

dlanor

07-01-2006, 06:58 PM

ok I just thought of something really dumb.. if hdd0:__boot/ gets mounted as pfs0:/ then trying to access pfs0:/__boot/ is going to fail.. I'm not sure what you mean here. Since "__boot" is a partition, not a folder, it is never legal to access it as "pfs0:/__boot/". Such a usage would refer to a folder named "__boot", which is certainly not what I'm using.

Of course, it is permitted to have folder names identical to the partition names too, but I advise strongly against doing that, as it only gets confusing, and serves no functional purpose.

normally that's not a problem I could just replace the path with pfs0:/ but there is a problem if someone tries to stick myps2 inside a folder in a partition say hdd0:__boot/myps2/ Then I'll need to switch it to pfs0:/myps2/. The generic method used by uLaunchELF is to split any full HDD path into two parts.

For the example given here, the full path to split is: "hdd0:/+ELFS/myPS2/v1.2/MYPS2_2006.02.27_ntba2.ELF" (a real example from my own HDD)

The first part split off contains the drive and partition names, like "hdd0:+ELFS", and is used for mounting the partition on a PFS mountpoint, like "pfs0:".

The second part contains all the stuff that followed after the first part, which here is "/myPS2/v1.2/MYPS2_2006.02.27_ntba2.ELF", so that is what must be appended to the PFS path, resulting in "pfs0:/myPS2/v1.2/MYPS2_2006.02.27_ntba2.ELF".

One slight complication is that there may or may not be a '/' separator between the drive spec and the partition name. uLE normally uses one, but DMS4 Dev2 does not. But for program launching uLE uses fakehost anyway, so myPS2 will never see the paths used internally by uLE.

Also, for Dev2 booting you never have to consider the case of "boot.elf" being inside any folders, since that's not implemented. It's always in the root directory of the "__boot" partition, for current implementations anyway.

I'll have to take a closer look at it after dinner.. my kids are buggin me to make supper for them.
Yeah. Real life comes first, of course.

Best regards: dlanor

flamingo24

07-01-2006, 07:09 PM

It appears some act strange when loading. Although I haven't had any crashes while loading them from hard drive. I have found that some don't like to be loaded the BeOS one specifically can not be loaded from the default skin. All it does is add a blank character to the themes list and returns to the current skin. Although I don't think it's a hard drive problem per say. I have all my myPS2 files in the myPS2 partition and simply boot into that using the options

I tried your method of using the myps2 partition; once again it started up with the same behavior as before bsod upon activating a skin (using ntba2 v1.2); however, both your beta versions allow me to switch skins from the hdd :)...the blank character you refer to has happened before when I was loading from my usb flash drive it must have been a sector corruption since after deleting the skins folder and re-transferring back it would read and activate skins fine (this was not specific to a single skin)...

myPS2 needs to load it's config file to start up, let me see if I can't work up something newer to test.

ok here is a newer version that should check for being booted as hdd0: and set the elf path to pfs0:/ I'm not sure how well that'll work cause I can't test it. but it's worth a try.

I got the same thing as dlanor booting direct from dev2 (screen garbage); half the matrix logo the other half thick garbled lines. unrelated to this on both beta versions of v1.2 it will not allow me to launch elf files (freezes). this is a non-issue since I use uLaunchELF for this function, though the one problem with this is that when I want to exit myps2 I can't launch uLaunchELF :(

dlanor

07-02-2006, 12:19 AM

I got the same thing as dlanor booting direct from dev2 (screen garbage); half the matrix logo the other half thick garbled lines. It's interesting to note that results for a DMS4pro and a Matrix Infinity (which I assume you have, from your comment) both give identical results.

If you haven't already done so, could you please try the earlier beta again (it doesn't crash here, but only fails to load CNF), and report the exact strings displayed for "Load Path:" and "SetElfPath:" with Matrix Infinity. We need to know if both modchips use the same argv[0] string for Dev2 launches.

unrelated to this on both beta versions of v1.2 it will not allow me to launch elf files (freezes). this is a non-issue since I use uLaunchELF for this function, though the one problem with this is that when I want to exit myps2 I can't launch uLaunchELF :(
I don't get that problem here. I have no problem starting uLaunchELF from any version of myPS2, including Mike's two betas.

Since the skin implementation of myPS2 can affect both functionality and appearance, this could in fact be a skin issue. Have you tried with just the original default skin installed ? That's what I use, and it might make a difference for your setup too.

Best regards: dlanor

Thumps

07-02-2006, 04:44 AM

I don't get that problem here. I have no problem starting uLaunchELF from any version of myPS2, including Mike's two betas.

Since the skin implementation of myPS2 can affect both functionality and appearance, this could in fact be a skin issue. Have you tried with just the original default skin installed ? That's what I use, and it might make a difference for your setup too.

Actually, I have tried it with the default skin, and 3 different versions of myPS2. In any case I can only run some of the elfs that I have. ps2link, execftps, 3stars all seem to run. However hdl 8b, uLaunchElf 3.61, and myPS21.2 don't run. So I do see it as a bug, it's just looking at the SVN logs I see there has been some changes to the elf loading part. Which might not be completed yet.

as for dev2 booting, I spent most of tonight looking over SVN logs for elf loader but I did manage to think about it and came up with some interesting
questions..

first off hdd0:__boot/myPS2/myPS2.ELF for example.
hdd0 has to be mapped to a pfs entry in which it becomes
pfs[x]:/myPS2/myPS2.ELF but only if it's mounted. So how do we know if the mod chip has already mounted it or not. what happens if the mod chip mounted that as pfs0. From what I've read everything coming from a hard drive must be handled through the pfs file system. However what's to say the mod chip didn't simply open the elf, read it to memory and unmount the filesystem, then execute the file. I couldn't find any function to figure out what partitions are mounted. So I'll have to keep on looking.

But I have to say thank you for the support, my crash course in ps2 development is turning out to be very enjoyable lol.

Mike

flamingo24

07-02-2006, 09:53 AM

If you haven't already done so, could you please try the earlier beta again (it doesn't crash here, but only fails to load CNF), and report the exact strings displayed for "Load Path:" and "SetElfPath:" with Matrix Infinity. We need to know if both modchips use the same argv[0] string for Dev2 launches.

I tried the earlier beta and it said there was no config.dat present, I did'nt remember the exact string so I relaunched from dev2 :)

Matrix Infinity (yellow dot, v1.88 firmware;v7)

Load Path:hdd0:__boot/boot.elf
SetElfPath:hdd0:/__boot/

the dms team were the first to release a modchip with dev support (dms3) all other modchips I think model after them for there dev implementation.

Since the skin implementation of myPS2 can affect both functionality and appearance, this could in fact be a skin issue. Have you tried with just the original default skin installed ? That's what I use, and it might make a difference for your setup too.

this was my bad; at first I tried this and modified the config.dat placed another fresh myps2 installation (ntba2 v1.2-as is) in a different area on my hdd, replaced the myps2.elf with the beta myps2 elf and relaunched...I had the same issue launching ule (v3.79) :( it was at this point I realized I have only attempted to test this with the ule.elf. :banghead: I then went to the original installation relaunched under the macos skin and applied the partition where I store all my elf files used with ule, went over to myprograms and launched super mario war and it worked :) I jumped the gun alittle, still the only elf I really want to launch from myps2 freezes :(

edit: I do not think this is at all a ule problem; myps2 has flakey elf launching capabilities; also I don't think this has anything to do with the beta's. now that I think about it I recall back when I used myps2 to launch elf files it did take issue with some elfs and others it did not, it's probably something simular to what sms had issues with launching certain elf files on exit...

Thumps

07-08-2006, 03:40 AM

ok, sorry I couldn't work on this for the last 6 days. I had to fight my kids to get my ps2 back.. seems they love the custom modded uLaunchElf and HDL that I created for them.

Anyway I'm releasing a new beta for dev2 booting. I can't test it but all it does is turn hdd0:/x to pfs0:/ when booting off hard drive.
When booted you should see.

Load Path:hdd0:__boot/boot.elf
SetElfPath:pfs0:/

That means myPS2 will search for it's configure file where ever you booted myPS2 from. So if you boot from hdd0:__boot/myPS2.ELF you should also have the hdd0:/__boot/CONFIG.DAT which becomes pfs0:/CONFIG.DAT.

I've also removed all references to loading ps2link. So this will work with a original myPS2 1.2 setup. So if you tried my other beta's and added the language and skins files you will need to revert them for this to load. I wanted to remain as original as possible incase this does work for people.

Hopefully this actually works, because I can't test it. I didn't even know mod chips could boot code directly when I bought my mod chips, so now I'm thinking of going out and getting a couple DMS4 chip instead of the cheap chips I did buy (duo2 GT) which don't support dev2 booting. it's just that it will be several weeks before I can even consider that, I'm in the middle of negotiating a new job for myself.

Also thank you everyone for the great support. I hope this works so I can at least help out the ps2 development scene. Not to mention, I'd love to keep helping out with coding where ever I'm needed :)

Mike

flamingo24

07-08-2006, 12:29 PM

Thumps

07-08-2006, 12:46 PM

I'm glad to see your still working on a solution :) I tried booting from dev2 with the latest beta the results are simular to the 2nd beta, newest version shows the bottom half the matrix logo the top half alternates (solid pattern) between thick black and thick white lines.

Thanks, I'm trying.. it's just I don't have much time between this interview process and the kids wanting to play with the only ps2 that has a hard drive.

It sounds like for some reason the gs isn't getting setup properly (just my guess that the gs is already initialized and myPS2 isn't resetting it, simply because it seems like the matrix logo is a texture left over in video memory that should have been erased). Thanks also to the great description given by dlanor.

I'll have to take a closer look at it when I get back. Although I don't really know much about the gs yet. Hopefully it's not something I need a mod chip to be able to get working. I just don't have the time to look into it this weekend as i'm in the middle of planing a trip for an interview on Monday.

Mike

ROTORGAMES

10-11-2006, 09:01 PM

hello:

frist sorry for my bad english.

I have a problem:

I would like to make run MyPS2 1.2 because I need to transfer save games fron USB stick to MC.

I don´t have HDD, y only have a MC & USB stick.

I burn MyPS2 1.2 on dvd with 300MBx3 data blank files, and I boot it using SWAP MAGIC DVD 2.0 (i don´t have cd version).

I edit the CONFIG.DAT with ultraedit32 as a result of:

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_debug = 0
ftp_enable = 1
ftp_port = 21
ftp_anonymous = 0
ftp_login = myPS2
ftp_password = myPS2
radio_cache_list = 0
lang_file = english.xml
lang_charset = ISO-8859-1
skin_name = default
time_timezone = 60
time_dst = 0
hdd_boot_part = hdd0:+boot
hdd_boot_path = /MYPS2/
<- line 27 white.

and when y use it i have this error:

h-t-tp://img204.imageshack.us/my.php?image=snapshot6ad3.jpg

(I can´t put the image this is my first post)

Anyone can help me??

thanks

dlanor

10-11-2006, 09:21 PM

@ROTORGAMES:
Since you are having problems with myPS2, perhaps you should consider some other alternative instead. Another file manager with USB capabilities, called uLaunchELF, is also hosted on this site. You can find it in another subforum near this one ("PS2 Homebrew/Dev & Emu Scene > Official UlaunchELF Forums").

Best regards: dlanor

ROTORGAMES

10-12-2006, 05:38 AM

anyone have a beeter solution to my problem????

jrbilodeau

10-26-2006, 05:57 PM

I've tried to find a solution for a problem that im having but cant seem to find one. im using a matrix infinity firmware 1.91 with dms hdd explorer in dev 2 mod as my app loader. im not sure if this applies the same way as trying to load myPS2 in dev2 because dsm hdd explorer installs to hdd0:/__boot and then my myPS2 folder gets installed inside that partition making it hdd0:/__boot/MYPS2/MYPS2.ELF

i'm able to load myPS2 my loading uLaunchelf, but i cant do it from dms hdd explorer. what i've noticed is that if i run it off uLaunchelf SetElfPath = host: but if i load it from dms hdd explorer SetElfPath = hdd0: and doesn't see my config file.

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.120
net_netmask = 255.255.255.0
net_gateway = 192.168.0.1
net_dns = 192.168.0.1
net_smb_workgroup = MSHOME
net_smb_debug = 0
ftp_enable = 1
ftp_port = 21
ftp_anonymous = 1
ftp_login = myPS2
ftp_password = myPS2
radio_cache_list = 1
part_mount_list = hdd0:+SNES
lang_file = english.xml
lang_charset = ISO-8859-1
skin_name = default
time_timezone = 60
time_dst = 0
hdd_boot_part = hdd0:__boot
hdd_boot_path = /MYPS2/

zabolyx

10-26-2006, 10:46 PM

anyone have a beeter solution to my problem????

that is a better solution. The only thing I want myPS2 for is to listen to shoutcasts. I'm sure if someone could get a hold of the source for myPS2 then a shoutcast player could be made as a stand alone.

snipersnake

11-09-2006, 04:20 AM

wow...so rocket science for me..

ImpactBlue

12-08-2006, 06:18 AM

I have taken the time to read through this thread as thoroughally as possible. I am having CONSIDERABLE difficulty getting MyPS2 1.2 to boot up. I've written my Config file exactly as outlined, using MYPS2 (all caps) for the folder name and +MYPS2 for the Partition name.

Before trying this, I tried installing it to the Boot partition, only to receive a Loading GUI String Table Failure. After making a new partition for the program, I came to receive the exact same error.

My Config file is as follows, and has the 27th line blank as it should be

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_debug = 0
ftp_enable = 1
ftp_port = 21
ftp_anonymous = 0
ftp_login = myPS2
ftp_password = myPS2
radio_cache_list = 0
lang_file = english.xml
lang_charset = ISO-8859-1
skin_name = default
time_timezone = 60
time_dst = 0
hdd_boot_part = hdd0:+MYPS2
hdd_boot_path =/MYPS2/

The partition and the folder names both line up, but it is STILL giving me a GUI failure. Can someone PLEASE help me out with this and double-check this for me? I want to get this working, so I can repeat the process as a christmas present

juancaretta

12-18-2006, 01:34 PM

Hi, i've trying getting this to work, but i couldn't. Here is my config.dat:
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_debug = 0
ftp_enable = 1
ftp_port = 21
ftp_anonymous = 0
ftp_login = myPS2
ftp_password = myPS2
radio_cache_list = 0
lang_file = english.xml
lang_charset = ISO-8859-1
skin_name = default
time_timezone = 60
time_dst = 0

Is it ok? It has a blank line in the end, i didn't put the hdd lines because i don't have one. It's a slim ps2, model SCPH-77001 with a Matrix Infinity v1.88 modchip. I'm trying to launch it from a USB drive using uLaunchElf. Thanks in advance.

dreamzboy

12-27-2006, 09:36 PM

Hi,

I'm lost within this thread, but here's my situation. I used Dung's Boot CD to install myPS2 into the memory card. However, when I boot up the disc, my ps2 doesn't launch into the "Launch" interface, the blue interface that has "Select - Configuration" "Left - Launch" "Right - Launch" it will just boot directly into myPS2 and everything works with no errors. I want to be able to boot up to that blue screen. What's weird is that I made 2 "exact" cd, one will boot up the launch blue screen, but it has the Loading GUI error. While the other, boot straight into the myps2. what the :rant: ? Any idea on this anyone?

dreamzboy.

jroc74

12-30-2006, 12:20 AM

My first post here, my lil .02 cents:

I just bought HDLoader 3.8b last week. It has myPS2 on it. (along with hdldump. HDL 3.8b is a good buy IMO) I kept getting the Loading GUI error just trying to run it from the mc!! It turns out I was missing:

/boot/
/fonts/
/language/
/shoutcast/
/skins/
/logs/

folders/files from the mc. (whoever made the disc musta been high that day.)

All I did to fix it was download myPS2, transfered the missing folders/files to the mc, (luckily I could ftp into it using myPS2) and I was up n running. Now that I got it to run off the mc I can finally work on getting it to run off the hd. Those still having the GUI error make sure u have the folders/files listed above. Maybe they need to be in the right directory or something. If u dont have the folders/files download myPS2 to have have fresh default settings and go from there if u made changes here n there.

BTW, I tried transfering the files using CuteFTP.....nada. FlashFXP just seems to be configured right for some reason.