Xplorer xfang6/18/2023 You can even recover one version with the other (SST 29EE020 SST 29LE020).īooting from a Winbond W29C040P-90 FX to recover a SST one won't work, didn't try the opposite yet as i only own one Winbond version for now. So far tested with these FX versions: 2x SST 29EE020 and 2x SST 29LE020 Then i swap to the bricked one and flash the same rom as the working one to recover, works like a charm. If you're booting off a cart, it's far less reliable on a bricked XPlorer, compared to using the CDR the plugging it in and enabling comms afterwards.īy just booting the PSX with the working Xplorer FX plugged to it and PC, launching X-Killer > Tools > ROM Manager > Detect. ![]() Sicklebrick wrote:But uhm, how are you booting XKiller to do the hotswap? Not a lot to go on here, they can be fiddly, but maybe some of the info's useful! ![]() Oh yeah, last thing, don't put anything over 384kb onto the XPlorer, even if it's a 512 model - the upper 128k can't be read by the PSX! Probs not relevant, but just incase! You could also maybe try with the official XLink software? I've no idea if that will work, but could be worth a crack? Sometimes, I've also noticed a difference between flashing with the cart off/on (go with off), and if you hit reset or power down afterwards. Also I can't remember the exact details, but I've had a similar issue whereby certain ROMs would completely fail to ever boot unless the last ROM had booted successfully at least one time (meaning every attempt would have to be repeated). I've also noticed some carts will be detected but not flashed properly unless you properly ram the cart into the back of the PSX (loose pin?). If you're booting off a cart, it's far less reliable on a bricked XPlorer, compared to using the CDR the plugging it in and enabling comms afterwards. Heyhey, you'll find the ROMs and a nice conversion table showing which cart can accept which ROM here (in theory):īut uhm, how are you booting XKiller to do the hotswap? Then i contacted Tim about this and he kindly answered me but unfortunatly, he doesn't have the X-Flash source code anymore so currently anyone willing to dowgrade those versions will meet the same issue. I guessed X-Flash could bypass this but it would need to properly recognize my FX first. (In this situation, trying to hotswap starting from the Winbond version just won't work !) Luckily i have two FX models with those 2x SST eeproms so i can unbrick with booting on the working one, hotswap to the bricked one and then reflsash with X-Killer. If flashing the FX with a 1.xx, 2.xx, 3.xx rom installed to a 4.xx, it will brick it. If flashing the FX with a 4.xx rom installed to a 1.xx, 2.xx, 3.xx, 4.xx, it will work just fine. This can be partially solved with X-Killer, which detects those as a 384 KB flashrom, but: X-Flash won't properly detect my FX that uses the 2x SST 29EE020 eeproms so i can't use it to properly flash this model. ![]() X-Killer then worked just fine, so thanks to all of those involved. I installed Windows 7 SP1 圆4 with Tim's X-Killer Inpout32 version i grabbed from Simias' page and the Inpout32 driver mentionned on Orion's page I installed Windows Xp pro SP3+ x86 and Sicklebrick's patched X-Killer with the GiveIO driver from here.īoth X-Killer and XLink95 worked just fine, so thanks Sicklebrick !Ī Lenovo T410 with an ExpressCard using a PLX OXFORD OXPCIe952 chipset. I could get my hands on a few machines to play with :Īn old IBM T43 with a native parralel port They both came with the Xplorer 4.52 PRO (UK) 05-11-1999 rom installed and i wanted to upgrade them with the Xplorer 4.52 PRO (UK) 22-11-1999, but i can't since X-Flash is complaining about the rom file being too big for the detected EEPROM.Īny help would be appreciated since i don't really want to brick those. ![]() Is that because they use 2 SST 29EE020 EEPROM and X-Flash doesn't handle that proprely ? My other two FX, the SST29EE020-120-4C-NH 256K x2 ones, are detected as SST 29EE020 (Xplorer) 256 KB only. My Xplorer FX Pro is detected as Winbond 29C040 (New Xplorer FX) 512 KB My Xplorer is detected as SST 29EE020 (Xplorer) 256 KB Right now i don't have the needed hardware to connect them to a PC and use XKiller. Xplorer FX / FX Professional ( 2 x SST 29LE020-200-4C-NH 256K) X-Terminator PRO DX ( 1 x Winbond W29C040P-90 512K) Xplorer FX Professional ( 1 x Winbond W29C040P-90 512K) I recently acquired a few Xplorer carts :
0 Comments
Leave a Reply. |