SMS 1.7(rev.4) BUGS!!!

Well today I updated my SMS to rev.4 and I've found 2 problems...

SMS boots all the way but the skin that I had in the previous version did not load using rev.4 and when I go to Player Settings and scrolldown. Once I reach the Scroll Bar Color option... SMS Freezes. Now it only freezes when I'm in the Player Settings and I reach Scroll Bar Color. Everything else seems to be in working order.

My Specs are...

I have a PS2 v5/6 unmodded
200GB Maxtor connected via Network Adapter


I load SMS from a partition on my HDD called +MYPS2 with the help of uLaunch 3.72. I've also tried booting it from my MC and I produced the same results.

Well I hope EEUG reads this and fixes these bugs ;) I did notice that when loading a movie... SMS is loading the movie extremely fast compared to the previous version... which is a good thing :D

Best Regards,

neiljames

If you read EEUGs comments in the Work in progress thread (in the same post rev.4 was released), you'll see that the skin format has changed, and your report is not a bug. Also, there is a bug report sticky thread (which helps keep the forum organised), although I'm sure EEUG reads everything.

Thanx alot rathunter. Yeah man... I didn't even get rev.4 from that thread I d/l it from the SMS website :) Yeah I haven't read that thread. I am now tho' Thanx.

Best Regards,

neiljames

Also .lng file was updated, otherwise menu freezes ;)

I just found that I need to delete the configuration file (MC0:/SMS/SMS.cfg) to avoid a freeze. EEUG always advises this, but with some upgrades you can get away with not doing it.

EDIT:
There is a some sort of bug with the cfg file. If I save the setting to use a Background Image in 1.7 Rev.4, I get a black screen next startup. If I go back to 1.7 Rev.3 and save the config with this setting unchecked, then Rev.4 can use my old settings.

...that's funny :), because here I couldn't reproduce anything what you've written, namely:
- using "old" SMS.lng file caused no problems with menu;
- using "old" SMS.cfg caused also no problems (no need to delete it);
- "...If I save the setting to use a Background Image in 1.7 Rev.4..."...it boots up OK next time here (both with ps2link and uLaunchElf) (at least with that "lee99"'s 800x600 image (didn't try other ones, but I think they should work OK);

In my tests I've used an .elf from my "website" and official Sony's equipment (HDD, MC etc.) :)

Uh-oh, I hate these funny bugs...
Ok I tried deleting my custom language and palette files, and then I was able to save the setting for a custom background (no freeze at launch). Then I restored my custom palette file, and that was okey. Then I restored my custom language file, and there was a freeze again. Note that these files work fine when a background image is not used. There appears to be some sort of interplay between my language file and the new skin. It is late here, so I will narrow it down tomorrow.

@rathunter: ...I've tested again with Spanish language file (I even made palette file) - no probs here. Btw., is you language file in Windows format (<cr><lf> as linebreaks) or Unix one (only <lf>)? Second one is not tested, though it should also work, but who knows. Try to share your .lng, .pal etc file, so I can also try them...

From now on, I'll try to post the changelog from EEUG also on the site. Maybe it's more clear that way;) (That I never thought of that before:|)

@EEUG: Sorry for the slow response, I had some trouble narrowing this down. I do use CRLF. My problem appears to be some sort of buffer over-run with my language file. If my file size exceeds 3454 bytes (>80 bytes more than the default ENG), then I get a crash if a skin is enabled. If I shorten some lines (I tried lines in various locations) so the total size is under 3455 bytes, then everything works. The location (line) of the extra data does seem to matter a bit, because I can exceed 3454 bytes in the early lines. I guess it would be a good start to look at the memory addresses in front of the skin? I've attached my custom language file, which I hope will recreate the crash for you.