The above video goes away if you are a member and logged in, so log in now!
|
| |
Would you like to get all the new info from PSX-Scene in your email each day?
| |
|
-
#1
heres my problem hopefully someone can help
heres my problem hopefully someone can help –
05-22-2003,12:37 PM
ok when i first installed a modchip on my v5 ps2 it was back in the day with a neo 2.2 backups booted fine with the old swap method (gameshark2) then i got a magic 3.1 and installed that and it would direct boot psx originals and backups and ps2 originals. wouldnt direct boot any ps2 backups. i took that out and installed my messiah 2 now with my m2 installed my reset button fails to work, the way i load games is by opening and closing the tray and it wont boot any ps2 backups or psx (mainly because i need the reset button) so what should i do here to fix this crap? im thinking about droppin 150 on a used ps2 at EB and starting from scratch again cuz i dont think my ps2 now can be saved lol i cant get that thing to direct boot ps2 backups for the life of me. any help would be appreciated
sublime90
-
05-22-2003,07:57 PM
Have a look at the RESET wire between Magic and PS2 and ensure it is on the right point.
Double check your ribbon cable connexion- in fact that's the most likely problem - the cable might be nicked.
-
05-22-2003,10:26 PM
i will take your broke v5 and maybe make a deal on a premoded v? i have a few different versions....maybe we can work something out on a trade or something.... PM me if you want to try to work something out.....
john
(modking420)
-
05-24-2003,01:12 AM
hey charlie do you think i might need to check the soldering of the reset wire, cuz when i was first playing it,after i first installed it, i was playing a game for like a minute then it made a noise and went straight into standby mode, then it couldnt reset anymore and i just have been booting games by opening and closing the disc tray
sublime90
-
05-24-2003,06:18 AM
Then it won't be the chip's RESET wire.
It could be anything but it might well be that the Reset/Eject cable has been damaged or caught in a screw. It is also possible that under compression, BIOS wires are touching at the bare end. Something like that.
Pro attention would be best.
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|