Matrix Infinity & v10 - from bad to worse
After waiting for over a week for the chip, I installed it using the main dvd controller points and did the romeo mod. Booted up THUG2 perfectly. I then upgraded to v1.35 w/o a hitch. After that, I tried HDLoader, and no dice - it would just sit there formatting. The HDD, which was preformated with Winhiip before trying HDLoader, is on the list of drives that work. I'll admit that the drive has occationally shown problems spinning up, but while it was in the ps2 it spun up every time. It might be because it was from a cd-r, because the stupid memcard manager *will not* let me load it onto the mem card. Regardless, it didn't matter if I started with a NTFS, FAT32, PS2, or no partition on the drive. DMS tools v1.10 told me the disk had an error, and HDL just sat there. I'll try it with a different drive...if I ever can (reason below).
After all this crap, it starts giving me occational red screens, so I decided to re-route some wires so that they are all evenly spaced. Problems persist with cd-r's and dvd-r's. When it does load, it would freeze while loading. I thought maybe installing the new firmware released yesterday that includes the new mem manager on the same disc might solve the problems. The firmware didn't help at all, but installed fine. After that, I tried the new mem manager. It sat there for 10 mins 'installing' it, so I switched the machine off & restarted. Now it acts crazy. No video output, pushing eject gives me a blinking blue light followed by an opening tray 10 seconds afterwards or sometimes the cog clicking like mad. Holding the reset button to 'recover from a bad flash' did nothing.
Update (before posting >_>): turned it on (standby), held eject, and the tray opened like normal. Splash screen boots up like a virgin ps2. I push the tray in with the v1.36 disc and I'm greeted by: first a black PS1 logo, then a PS2 logo (like that on the case), then a language select screen...and then it froze up. Now its back to its previous dead state. Could this be a result of a dead clock battery? When I would try to set the time, it would reset to the default date any time I hit a button to change it, but then run on after I OK'd it. I'm also going to try all the alternate points, and then check to see if the PS2 works fine w/o the chip attached.
FYI its a GH-026 v10 board, all control wires are solid ATA-66 cable wires, 3.3v & ground wires are 20awg, and the capacitor on the diagram's 3.3v line had the metal end pop off, but was replaced with the same type, but I highly doubt it's a problem, although logic says that the extra 'noise' w/o a cap might produce these sorta results. We'll see, assuming I can find another v10... This is the s*** I get for sending my v7 to Iraq... :banghead: