Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[andrewwan1980]

I think most of us are lucky to name our kick start ROMs as:

kick13.rom
kick20.rom
kick31.rom

since coincidently that is what PSPUAE expects - opposed to WinUAE where the filename can be of anything with spaces & symbols.

Please could you handle:

 - selecting a kick start ROM version where the file doesn't exist or is corrupted (rather than PSPUAE crashing)
 - same with the Load Preset Configs (A500, A600, A1200, etc)... if the ROM file doesn't exist then PSPUAE crashes.


Side-issue:

I notice latest WinUAE has a ROM detection system. I experiemented with 2 different copies of my 3.1 ROMs and found one is accepted while the other isn't. However both seem to run fine with games. What is this ROM detection system? Does it detect authentic/real ROMs?


Update: I just realised all this information is in the README.txt. And the above was referring to 0.63BE... just updated to 0.70.///.

[FOL]

I think most of us are lucky to name our kick start ROMs as:

kick13.rom
kick20.rom
kick31.rom

since coincidently that is what PSPUAE expects - opposed to WinUAE where the filename can be of anything with spaces & symbols.

Please could you handle:

 - selecting a kick start ROM version where the file doesn't exist or is corrupted (rather than PSPUAE crashing)
 - same with the Load Preset Configs (A500, A600, A1200, etc)... if the ROM file doesn't exist then PSPUAE crashes.


Side-issue:

I notice latest WinUAE has a ROM detection system. I experiemented with 2 different copies of my 3.1 ROMs and found one is accepted while the other isn't. However both seem to run fine with games. What is this ROM detection system? Does it detect authentic/real ROMs?


Update: I just realised all this information is in the README.txt. And the above was referring to 0.63BE... just updated to 0.70.///.

It shouldnt crash, but tell you what the problem is, then revert back to using kick1.3. The other rom your using proberly doesnt work cause its an over sized rom (amiga forever), pspuae doesnt support these kicks.

EDIT:- Just tested with only having Kick1.3 and the error message system works fine. If I try to load kick3.1, 3.0 etc etc. It tells "Error you dont have that Kickstart, using 1.3 instead".

So what PSP FW are you using.

EDIT2:- Just tested with no kicks, using latest beta and 070 and both function perfect. It tells me its missing the kicks then goes back to xmb.
As with above question, which version are you using?

EDIT3:- So we are all good then? *FOL goes back to getting 0.71 ready for release, *

[andrewwan1980]

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).

I just upgraded to PSPUAE 0.70 and tried manually loading Kick Start 2.0 and my PSP crashes and switch off.

I then tried the quickstart A600 & A1200 and they both crash PSP and switch off.

[FOL]

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).

I just upgraded to PSPUAE 0.70 and tried manually loading Kick Start 2.0 and my PSP crashes and switch off.

I then tried the quickstart A600 & A1200 and they both crash PSP and switch off.

Which eboot? 1.50 or 1.00_CFW_Slim?

I dont bother with 1.50, no point with CFW.

This might sound silly, but we have had really odd problems caused by corruption on the MS.

[andrewwan1980]

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).

I just upgraded to PSPUAE 0.70 and tried manually loading Kick Start 2.0 and my PSP crashes and switch off.

I then tried the quickstart A600 & A1200 and they both crash PSP and switch off.

Which eboot? 1.50 or 1.00_CFW_Slim?

I dont bother with 1.50, no point with CFW.

This might sound silly, but we have had really odd problems caused by corruption on the MS.

Am using 1.50 (and always have with Dark Alex CFW) coz I thought that was the norm. Though I want 1.00 boot up so I can run bochs PSP....

[FOL]

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).

I just upgraded to PSPUAE 0.70 and tried manually loading Kick Start 2.0 and my PSP crashes and switch off.

I then tried the quickstart A600 & A1200 and they both crash PSP and switch off.

Which eboot? 1.50 or 1.00_CFW_Slim?

I dont bother with 1.50, no point with CFW.

This might sound silly, but we have had really odd problems caused by corruption on the MS.

Though I want 1.00 boot up so I can run bochs PSP....

Lost me with that, comment. I recomment using the 1.00 eboot with custom firmware, just put the pspuae folder in the GAME371 <---- in your case. If it was say 3.90, then it would go in the GAME390 folder. This way if your kernel is set to 1.50, it will use the 3.71 kernel if its put in the 371 folder.

[andrewwan1980]

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).

I just upgraded to PSPUAE 0.70 and tried manually loading Kick Start 2.0 and my PSP crashes and switch off.

I then tried the quickstart A600 & A1200 and they both crash PSP and switch off.

Which eboot? 1.50 or 1.00_CFW_Slim?

I dont bother with 1.50, no point with CFW.

This might sound silly, but we have had really odd problems caused by corruption on the MS.

Though I want 1.00 boot up so I can run bochs PSP....

Lost me with that, comment. I recomment using the 1.00 eboot with custom firmware, just put the pspuae folder in the GAME371 <---- in your case. If it was say 3.90, then it would go in the GAME390 folder. This way if your kernel is set to 1.50, it will use the 3.71 kernel if its put in the 371 folder.

Yes, currently my PSPUAE is in GAME150. 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)?

If you look on http://www.dark-alex.org/ then you see that Dark Alex only does 1.50 addons to his 3.71 onward CFWs... unless one can replace the 1.50 with 1.00 for the addon...

[FOL]

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).

I just upgraded to PSPUAE 0.70 and tried manually loading Kick Start 2.0 and my PSP crashes and switch off.

I then tried the quickstart A600 & A1200 and they both crash PSP and switch off.

Which eboot? 1.50 or 1.00_CFW_Slim?

I dont bother with 1.50, no point with CFW.

This might sound silly, but we have had really odd problems caused by corruption on the MS.

Though I want 1.00 boot up so I can run bochs PSP....

Lost me with that, comment. I recomment using the 1.00 eboot with custom firmware, just put the pspuae folder in the GAME371 <---- in your case. If it was say 3.90, then it would go in the GAME390 folder. This way if your kernel is set to 1.50, it will use the 3.71 kernel if its put in the 371 folder.

Yes, currently my PSPUAE is in GAME150. 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)?

If you look on http://www.dark-alex.org/ then you see that Dark Alex only does 1.50 addons to his 3.71 onward CFWs... unless one can replace the 1.50 with 1.00 for the addon...

I think your really confused. Yes you can use the 1.00Eboot on any custom firmware, without 1.50 addon. 1.00 eboots will work with everything aslong as they are in usermode. I added alot about where to put PSPUAE in the readme.

You do exactly what I do in regards to default kernel, as I said I never bother with 1.50 anymore. I just place pspuae in the GAME folder and away i go, .

[delta191]

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 

[FOL]

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 

To help clarify things, taken from the readme.

Open the V1.50 folder.
Open the PSP folder, Open the GAME folder.
Drag and Drop %__SCE__PSPUAE & __SCE__PSPUAE to the GAME folder of your
MS (normally ms0:PSP\GAME\), See below (typical dir structure).

MS0:(MemoryStick ROOT DIR)
|
|-PSP\
  | 
  |-GAME\

It may prompt you to Overwrite, click "yes to all".
------------------------------------------------------------------------

V1.00 / Slim and Custom Firmware Install. <------------------------This is what should be done with custom firmware......
Open the V1.00_CFW_SLIM folder.
Open the PSP folder, Open the GAME folder.
Drag and Drop the PSPUAE folder to your MS (normally ms0:PSP\GAME\),
See below (typical dir structure).

MS0:(MemoryStick ROOT DIR)
|
|-PSP\
  | 
  |-GAME\

It may prompt you to Overwrite, click "yes to all".

------------------------------------------------------------------------

With Custom Firmwares, you may also use the old V1.50 KXPLOITED EBOOT, <-----This is what should be done with custom firmware wanting to use the 1.50 Version......
Open the V1.50 folder.
Open the PSP folder, Open the GAME folder.
Drag and Drop %__SCE__PSPUAE and __SCE__PSPUAE to the GAME150 folder of your
MS (normally ms0:PSP\GAME150\), See below.

MS0:(MemoryStick ROOT DIR)
|
|-PSP\
  | 
  |-GAME150\

It may prompt you to Overwrite, click "yes to all".

Although V1.00 EBOOT is a FW V1.00 EBOOT, it is untested on PSP FW V1.00, but
it should work.

[andrewwan1980]

Damn... I only use 3.40OE (and upwards) for the PSP popstation (to play PS1 ISOs).
And a lot of homebrew (SNES, CPS2, DOSBox, N64, SCUMMVM, GBA) all use 1.50... unless am mistaken and they are compatible with 1.00 CFW...

So you're telling me we can multi-boot 1.00, 1.50 & (whatever 3.71) firmwares?

[FOL]

Damn... I only use 3.40OE (and upwards) for the PSP popstation (to play PS1 ISOs).
And a lot of homebrew (SNES, CPS2, DOSBox, N64, SCUMMVM, GBA) all use 1.50... unless am mistaken and they are compatible with 1.00 CFW...

So you're telling me we can multi-boot 1.00, 1.50 & (whatever 3.71) firmwares?

What do you mean multiboot?

So your using popsloader to load you ps1 games?

Yes you are mistaken, nearly all of them have been updated to work on newer firmwares. If an app/emu has a 1.00, slim or cfw eboot, then use that. You tend to reply with confusing answers, .

EDIT:- You just reminded me, talking about plugins, . Added to readme, that some plugins cause PSPUAE to not load.

[andrewwan1980]

Damn... I only use 3.40OE (and upwards) for the PSP popstation (to play PS1 ISOs).
And a lot of homebrew (SNES, CPS2, DOSBox, N64, SCUMMVM, GBA) all use 1.50... unless am mistaken and they are compatible with 1.00 CFW...

So you're telling me we can multi-boot 1.00, 1.50 & (whatever 3.71) firmwares?

What do you mean multiboot?

So your using popsloader to load you ps1 games?

Yes you are mistaken, nearly all of them have been updated to work on newer firmwares. If an app/emu has a 1.00, slim or cfw eboot, then use that. You tend to reply with confusing answers, .

EDIT:- You just reminded me, talking about plugins, . Added to readme, that some plugins cause PSPUAE to not load.

Just to clarify again:

I use 3.71M33-4 with 1.50 addon.
By default I have two folders, GAME & GAME150. I put my PS1 ISOs into GAME folder since it can only load from there (I think). I put all homebrew into GAME150 folder.
The system defaults the GAME folder to use 3.71 (C)FW


I assume you have been telling me you don't bother use 1.50 CFW and you use 1.00 (C)FW?

[FOL]

Damn... I only use 3.40OE (and upwards) for the PSP popstation (to play PS1 ISOs).
And a lot of homebrew (SNES, CPS2, DOSBox, N64, SCUMMVM, GBA) all use 1.50... unless am mistaken and they are compatible with 1.00 CFW...

So you're telling me we can multi-boot 1.00, 1.50 & (whatever 3.71) firmwares?

What do you mean multiboot?

So your using popsloader to load you ps1 games?

Yes you are mistaken, nearly all of them have been updated to work on newer firmwares. If an app/emu has a 1.00, slim or cfw eboot, then use that. You tend to reply with confusing answers, .

EDIT:- You just reminded me, talking about plugins, . Added to readme, that some plugins cause PSPUAE to not load.

Just to clarify again:

I use 3.71M33-4 with 1.50 addon.
By default I have two folders, GAME & GAME150. I put my PS1 ISOs into GAME folder since it can only load from there (I think). I put all homebrew into GAME150 folder.
The system defaults the GAME folder to use 3.71 (C)FW


I assume you have been telling me you don't bother use 1.50 CFW and you use 1.00 (C)FW?

Almost, . Your confusing yourself, I never mentioned I use 1.00 Firmware. I use 3.90-M33-2, and I never use my GAME150 folder, i dont even have the 1.50 addon installed.

When i mention 1.00, im talking about the Eboot (app/emu, in this case PSPUAE). Its been compiled to run on 1.00 (but it will work on any firmware except 1.50 Firmware). Truth be told, I dont even know if the 1.00 Eboot will work with the 1.00 Firmware (I already mention this in the readme).

So, in the case of PSPUAE, you can use the 100_CFW_SLIM 1. Simply throw the pspuae folder in your GAME folder, saves having 2 folders and the error messages will work.

Ill PM you my revised Readme, hopefully my changes will make it clear, hard to explain here through posts.

EDIT:- Think I see what you mean by multiboot, so the answer is YES, you can use 1.00, 2.xx & 3.xx Eboots in the GAME and GAME371 folder and 1.50 Eboots in the GAME150 folder.

[andrewwan1980]

<snip> <snip>

Almost, . Your confusing yourself, I never mentioned I use 1.00 Firmware. I use 3.90-M33-2, and I never use my GAME150 folder, i dont even have the 1.50 addon installed.

When i mention 1.00, im talking about the Eboot (app/emu, in this case PSPUAE). Its been compiled to run on 1.00 (but it will work on any firmware except 1.50 Firmware). Truth be told, I dont even know if the 1.00 Eboot will work with the 1.00 Firmware (I already mention this in the readme).

So, in the case of PSPUAE, you can use the 100_CFW_SLIM 1. Simply throw the pspuae folder in your GAME folder, saves having 2 folders and the error messages will work.

Ill PM you my revised Readme, hopefully my changes will make it clear, hard to explain here through posts.

EDIT:- Think I see what you mean by multiboot, so the answer is YES, you can use 1.00, 2.xx & 3.xx Eboots in the GAME and GAME371 folder and 1.50 Eboots in the GAME150 folder.

Yes, the 1.50 addon was not required for 3.50 (or 3.60) OE/M33 and earlier versions... however with 3.71M33 and later versions, DArk Alex said he couldn't merge the 1.50 or something and it came later as an addon...

Interesting.. you say PSPUAE won't work on 1.50 CFW... when I have been running 0.63EB and 0.70 on my 1.50CFW.