75UR15

Like the plugin, don't much like the theme (sorry) so I kinda retrofited the one from gba emulator over, it can be found here if anyone is interested:
http://www.mediafire...qf1yu5jpu3uj5y3
the title menu works differently, and the title pic (stitle.bmp) was getting in the way, updated here:
http://www.mediafire...nxb3lapy3zgbuvq
preview available here:
http://s216.photobuc...nt=Img_0209.jpg
my iphone is distorting the colors a little, it will match what shows in gba emulator.

the images therein need to go in:
x:\CATSFC\system\gui\

Make sure you have a full backup of your saves, and you will need the update file for the ps3 (equal or higher than what the system has now). Once a new drive is installed (as I understand it) the previous drive is "unusable" without reformatting (haven't put my old drive back in but that is what I was given to understand). Also, if you have a SATA II (3.0 GB/s drive) make sure you set the jumper (if your drive has it) for SATA I (1.5 GB/s) operation....it will stop your drive from having those "unable to find drive" problems. It doesn't happen often, but it is as annoying as hell when it does (can't restart by remote/controller...have to manually power down restart).

Explanation
as it was explained to me the ps3 sata controller inside is limited to 1.5 operation, and if the drive starts up before the ps3, it starts in II mode and won't be recognized by the "old" controller. Normally the system starts before this happens and "imposes" the sata I limitation and everything works fine.

I had this problem on my dsi xl...didn't realize what the "lines" were at first, but after I reset it they appeared better, so I kept hitting the reset button and the lines stood out enough to recognize them. They were the lines from the battle screen of Final Fantasy I. Running ds screen tester now. 10mins or so in and the lines are greatly reduced. I have to look VERY closely (on the tester black screen) to see them at all, 10-20 more I expect them to be gone.

edit 20-30ish now the lines are gone on the tester, but after resetting again I could see them. They now only appear when i hit that power button for a reset, not when I first turn it on or do anything else. Gonna run that tester till the battery dies to see if that helps any.

edit 2
also for a note, i never left my console on on the pause /battle screen

edit 3
1hr in and even when resetting the lines are mostly gone, and the more pronounced ones are hard to see. (2bars left in power meter)

edit 4
90(ish) minutes in, still 2 power bars left (have been resetting each post for checking) and 100% clean, no traces of the burn in, not that I would want to test this to see if it would work again. To the writer of the screen test, kudos to you or your group

quicknote
@JonthanD
As far as lcd not burning in, it usually takes longer, but they are just as capable, I used to play wow hours on end, I had it once where my bars at the bottom and side (which except for occasional changes to the spell never change location or appearance) burned in, and stayed burned in for 4+hrs of white screen (opened image editor, and zoomed in on a blank white image). Corrected after about 6ish on that one. (was a high quality screen from dell the 2005fpw ultra sharp....and after 12+hrs of straight playing....yes I KNOW i need a life).

Easier answer for later (in case anyone wants it), using the original .app file you used to make the .csm with would install the original theme without needing to install anything else. For 4.2 that is 87.app and for 4.3 that is 97.app, it would just need to be "installed" with mymenufy. I realize their wii is already working, but if this thread is looked up later this would be faster and likely they would already have the file they neeeded (it is used to take a .mym and make a .csm).

AFAIK there is no difference in the danger of using the Official update if you do or do not already have it (bootmii as boot2) installed. If you CAN install it as boot2 you will be able to after whether or not you installed it before. The only people (like me, sigh) who can't are those who have wiis with an updated boot1 which prevents boot2 from using bootmii (or other unauthorized code).