Open the PSP folder, Open the GAME folder.ĭrag and Drop %_SCE_PSPUAE & _SCE_PSPUAE to the GAME folder of your To help clarify things, taken from the readme. I know where he's coming from - after 2 years of placing 1.5 kernel emulators in PSP/GAME150 it takes your mind to be re-trained to placing emulators in GAME folder I just place pspuae in the GAME folder and away i go. You do exactly what I do in regards to default kernel, as I said I never bother with 1.50 anymore. I added alot about where to put PSPUAE in the readme. 1.00 eboots will work with everything aslong as they are in usermode. Yes you can use the 1.00Eboot on any custom firmware, without 1.50 addon. unless one can replace the 1.50 with 1.00 for the addon. If you look on then you see that Dark Alex only does 1.50 addons to his 3.71 onward CFWs. I though PSPUAE can only run in 1.00 or 1.50? So you're telling me I can run PSPUAE in GAME371 or GAME folder (which is defaulted to 3.71)? This way if your kernel is set to 1.50, it will use the 3.71 kernel if its put in the 371 folder. If it was say 3.90, then it would go in the GAME390 folder. I recomment using the 1.00 eboot with custom firmware, just put the pspuae folder in the GAME371 <- in your case. Though I want 1.00 boot up so I can run bochs PSP. This might sound silly, but we have had really odd problems caused by corruption on the MS. I dont bother with 1.50, no point with CFW.
I then tried the quickstart A600 & A1200 and they both crash PSP and switch off.
I just upgraded to PSPUAE 0.70 and tried manually loading Kick Start 2.0 and my PSP crashes and switch off. Hmm, I am using 3.71 M33-4 with only kick13.rom kick20.rom (I thought was A600) and kick31.rom (I thought was A1200). It tells me its missing the kicks then goes back to xmb.Īs with above question, which version are you using?ĮDIT3:- So we are all good then? *FOL goes back to getting 0.71 ready for release, * It tells "Error you dont have that Kickstart, using 1.3 instead".ĮDIT2:- Just tested with no kicks, using latest beta and 070 and both function perfect. The other rom your using proberly doesnt work cause its an over sized rom (amiga forever), pspuae doesnt support these kicks.ĮDIT:- Just tested with only having Kick1.3 and the error message system works fine. It shouldnt crash, but tell you what the problem is, then revert back to using kick1.3. Update: I just realised all this information is in the README.txt. What is this ROM detection system? Does it detect authentic/real ROMs? However both seem to run fine with games. I experiemented with 2 different copies of my 3.1 ROMs and found one is accepted while the other isn't. I notice latest WinUAE has a ROM detection system. if the ROM file doesn't exist then PSPUAE crashes.
same with the Load Preset Configs (A500, A600, A1200, etc). selecting a kick start ROM version where the file doesn't exist or is corrupted (rather than PSPUAE crashing) Since coincidently that is what PSPUAE expects - opposed to WinUAE where the filename can be of anything with spaces & symbols. I think most of us are lucky to name our kick start ROMs as:
0 kommentar(er)
