Print

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

[andrewwan1980]

1. Does PSPUAE support AGA chipset?

2. I remember my joystick having two fire buttons. Does PSPUAE support Joystick 0, fire button 1? I only could find Joy 0 Fire 0 & Joy 1 Fire 0.

3.
PSPUAE Chipset settings doesn't include AGA so I assume AGA is not supported. But the last ECS option is confusing. In PSP it's listed as ocs, ecs_agnus, ecs_denise, ecs. Which is the most powerful/best ECS version?
-OCS = A500, A1000, A1500, A2000, A2500, CDTV
-ECS AGNUS = A500+, A600, A3000, A3000T, A3000UX
-ECS DENISE = A500+, A600, A3000, A3000T, A3000UX
-ECS FULL = A500+, A600, A3000, A3000T, A3000UX

4.
I tried all CPU types successfully.
-68000 = A500, A500+, A600, A1000, A1500, A2000, CDTV
-68010 = A500+, A600
-68020 = A1200, CD32
-68030/68881 = A2500, A3000, A3000T, A3000UX, A4000
-68040 = A4000, A4000T

But got problems with RAM:
-FastMem = Expanded Memory (Max 8192kb)
-Chipmem = Graphics Memory (Max 2048kb) (Mem can be different, but must = 10.5 Megs Total)
-Bogomem = Slow Memory (Max 1536kb)

I can set Chipmem & Bogomem to the max. But FastMem at max crashes PSPUAE. I run with 4MB FastMem fine though. Is this a bug?

5.
-Load Config A500 (OCS)
-Load Config A600 (ECS Denise)
-Load Config A1000 (OCS)
-Load Config A1200 (ECS)
-Load Default Config (Will load PSPUAE's bootup config)

The Load Configs don't work and crash my PSPUAE (I think I tried the A1200 config). If OCS is A500, ECS_denise is A600 & A1200 is ECS. What is ECS_agnus used by?

6. Is it on-going development to improve the UAE speed of games? eg. Cannon Fodder & most games are not smooth and sound is very fuzzy.

[FOL]

1. Does PSPUAE support AGA chipset?

2. I remember my joystick having two fire buttons. Does PSPUAE support Joystick 0, fire button 1? I only could find Joy 0 Fire 0 & Joy 1 Fire 0.

3.
PSPUAE Chipset settings doesn't include AGA so I assume AGA is not supported. But the last ECS option is confusing. In PSP it's listed as ocs, ecs_agnus, ecs_denise, ecs. Which is the most powerful/best ECS version?
-OCS = A500, A1000, A1500, A2000, A2500, CDTV
-ECS AGNUS = A500+, A600, A3000, A3000T, A3000UX
-ECS DENISE = A500+, A600, A3000, A3000T, A3000UX
-ECS FULL = A500+, A600, A3000, A3000T, A3000UX

4.
I tried all CPU types successfully.
-68000 = A500, A500+, A600, A1000, A1500, A2000, CDTV
-68010 = A500+, A600
-68020 = A1200, CD32
-68030/68881 = A2500, A3000, A3000T, A3000UX, A4000
-68040 = A4000, A4000T

But got problems with RAM:
-FastMem = Expanded Memory (Max 8192kb)
-Chipmem = Graphics Memory (Max 2048kb) (Mem can be different, but must = 10.5 Megs Total)
-Bogomem = Slow Memory (Max 1536kb)

I can set Chipmem & Bogomem to the max. But FastMem at max crashes PSPUAE. I run with 4MB FastMem fine though. Is this a bug?

5.
-Load Config A500 (OCS)
-Load Config A600 (ECS Denise)
-Load Config A1000 (OCS)
-Load Config A1200 (ECS)
-Load Default Config (Will load PSPUAE's bootup config)

The Load Configs don't work and crash my PSPUAE (I think I tried the A1200 config). If OCS is A500, ECS_denise is A600 & A1200 is ECS. What is ECS_agnus used by?

6. Is it on-going development to improve the UAE speed of games? eg. Cannon Fodder & most games are not smooth and sound is very fuzzy.

Nearly all these are already answered. As for crashing, with mem, read what it says in the brackets. With the config crashes, I need more info.

OCS = Original Chipset <---- 1st
ECS Agnus = Enhanced Chipset, Where the Agnus chip was beafed up <---- 2nd
ECS Denise = Enhanced Chipset, Where the Agnus chip was beafed up <----3rd
Full ECS = Enhanced Chipset, Where the both Agnus and Denise chips was beafed up <---- 4th
AGA = Advanced Graphics Arcutecture <---- 5th

For joypad, use CD32 buttons, as CD32 had a 7 Button Joypad, it works fine.

[andrewwan1980]

Nearly all these are already answered. As for crashing, with mem, read what it says in the brackets. With the config crashes, I need more info.

OCS = Original Chipset <---- 1st
ECS Agnus = Enhanced Chipset, Where the Agnus chip was beafed up <---- 2nd
ECS Denise = Enhanced Chipset, Where the Agnus chip was beafed up <----3rd
Full ECS = Enhanced Chipset, Where the both Agnus and Denise chips was beafed up <---- 4th
AGA = Advanced Graphics Arcutecture <---- 5th

For joypad, use CD32 buttons, as CD32 had a 7 Button Joypad, it works fine.

So in the chipset setup/config menu, the last ecs entry is ecs-full? It's the last "ecs" entry written with no agnus or denise appended words.

[FOL]

Nearly all these are already answered. As for crashing, with mem, read what it says in the brackets. With the config crashes, I need more info.

OCS = Original Chipset <---- 1st
ECS Agnus = Enhanced Chipset, Where the Agnus chip was beafed up <---- 2nd
ECS Denise = Enhanced Chipset, Where the Agnus chip was beafed up <----3rd
Full ECS = Enhanced Chipset, Where the both Agnus and Denise chips was beafed up <---- 4th
AGA = Advanced Graphics Arcutecture <---- 5th

For joypad, use CD32 buttons, as CD32 had a 7 Button Joypad, it works fine.

So in the chipset setup/config menu, the last ecs entry is ecs-full? It's the last "ecs" entry written with no agnus or denise appended words.

Not sure i understand the question,

ECS Agnus = only agnus improved
ECS Denise = only denise improved
ECS FULL = Both agnus and denise improved

[andrewwan1980]

Not sure i understand the question,

ECS Agnus = only agnus improved
ECS Denise = only denise improved
ECS FULL = Both agnus and denise improved

Load up PSPUAE and in the config for chipset. It lists like this, in this order and exact wording:

OCS
ECS_AGNUS
ECS_DENISE
ECS



So I was a bit confused. To a layman, the ECS option would appear to be a predeccessor to ECS_AGNUS & ECS_DENISE... because it's just called ECS....

[Hungry Horace]

its eCS full i guess.

does it even matter though?

[FOL]

Not sure i understand the question,

ECS Agnus = only agnus improved
ECS Denise = only denise improved
ECS FULL = Both agnus and denise improved

Load up PSPUAE and in the config for chipset. It lists like this, in this order and exact wording:

OCS
ECS_AGNUS
ECS_DENISE
ECS



So I was a bit confused. To a layman, the ECS option would appear to be a predeccessor to ECS_AGNUS & ECS_DENISE... because it's just called ECS....

Ordered exactly as they were released, it doesnt really make a difference as horace said, only AGA would obviously be completely noticable.

[Chilly Willy]

ECS_AGNUS allows for larger blits, and more chipmem. ECS_DENISE allows for more control over the video - those oddball display resolutions, along with SuperHires. UAE allows you to select one or the other in case you run into a program that expects one, but not the other. I doubt you'll ever do that, though.

[andrewwan1980]

Is there a significance between 1.3, 2.0. 3.1 ROMs and the config settings? Or can we mix-n-match happily?

Currently I only have used these 2 settings:

(my idea of A500) ECS Agnus, 6800, 1MB RAM, ROM 1.3
(my idea of A1200) ECS (Full), 68020, 1MB RAM, ROM 3.1

Am not a complete newbie... but I gather with ALL these custom settings of CPU, RAM, ROM, GFX, etc. one could spend years mix-n-match. I guess that's why PSPUAE has the build-in default configs of A500, A600, A1200. My A500 quickstart loads, but A600, A1000, A1200 crashes. I know A1200 won't work... even though I got a compatible 3.1 ROM (that is recognised by WinUAE detection). I got a 2.04 ROM but there's no A500+ quickstart.. maybe it's not worth it though.

[FOL]

Is there a significance between 1.3, 2.0. 3.1 ROMs and the config settings? Or can we mix-n-match happily?

Currently I only have used these 2 settings:

(my idea of A500) ECS Agnus, 6800, 1MB RAM, ROM 1.3
(my idea of A1200) ECS (Full), 68020, 1MB RAM, ROM 3.1

Am not a complete newbie... but I gather with ALL these custom settings of CPU, RAM, ROM, GFX, etc. one could spend years mix-n-match. I guess that's why PSPUAE has the build-in default configs of A500, A600, A1200. My A500 quickstart loads, but A600, A1000, A1200 crashes. I know A1200 won't work... even though I got a compatible 3.1 ROM (that is recognised by WinUAE detection). I got a 2.04 ROM but there's no A500+ quickstart.. maybe it's not worth it though.

Now your confusing issues, are you getting guru's or is pspuae crashing, i need something definate. Cause your other thread conflicts what this 1 says.

EDIT:- I know Zoom mode can cause crashes with certain configs, this is just how it is. I added turn autozoom off on reset, simply to stop this from happening. Simply load the game/app then turn autozoom on again.

Also, you can mix and match to your hearts content, . Just avoid setting mem to larger than 11 Megs, with current toolchain we can only get 11 Megs. The new toolchain solves this, but we cant use it as it adds alot of problems.

[Hungry Horace]

quickstart A1200 ECS probably doesn t work becuase you dont have kick30.rom - which *most* (not all) A1200's came with.

We also use kick3.0 for the RISS, becuase there are far less problems with different "versions" of kickstart 3.0.... unlike 3.1 which comes in A1200, A4000 and CD32 flavours.

[andrewwan1980]

quickstart A1200 ECS probably doesn t work becuase you dont have kick30.rom - which *most* (not all) A1200's came with.

We also use kick3.0 for the RISS, becuase there are far less problems with different "versions" of kickstart 3.0.... unlike 3.1 which comes in A1200, A4000 and CD32 flavours.

Ah, now you tell me. Thanks man. (where was it said that the quickstart A1200 required kick30.rom?)

Is there a significance between 1.3, 2.0. 3.1 ROMs and the config settings? Or can we mix-n-match happily?

Currently I only have used these 2 settings:

(my idea of A500) ECS Agnus, 6800, 1MB RAM, ROM 1.3
(my idea of A1200) ECS (Full), 68020, 1MB RAM, ROM 3.1

Am not a complete newbie... but I gather with ALL these custom settings of CPU, RAM, ROM, GFX, etc. one could spend years mix-n-match. I guess that's why PSPUAE has the build-in default configs of A500, A600, A1200. My A500 quickstart loads, but A600, A1000, A1200 crashes. I know A1200 won't work... even though I got a compatible 3.1 ROM (that is recognised by WinUAE detection). I got a 2.04 ROM but there's no A500+ quickstart.. maybe it's not worth it though.

Now your confusing issues, are you getting guru's or is pspuae crashing, i need something definate. Cause your other thread conflicts what this 1 says.

EDIT:- I know Zoom mode can cause crashes with certain configs, this is just how it is. I added turn autozoom off on reset, simply to stop this from happening. Simply load the game/app then turn autozoom on again.

Also, you can mix and match to your hearts content, . Just avoid setting mem to larger than 11 Megs, with current toolchain we can only get 11 Megs. The new toolchain solves this, but we cant use it as it adds alot of problems.

In this thread it's PSP crashing (freeze, then switch off) when I select a quickstart A600 or A1200. I always though A600 used kick20.rom and A1200 used kick31.rom. But now I find out A600 uses kick205.rom and A1200 (in PSPUAE case) only uses kick30.rom. This happens in BOTH version 0.63BE and 0.70!!! Interesting also is that when I manually select kick 3.0 (in the Kickstart menu) and I don't have a kick30.rom file, my PSP also crashes and switch off (which is contrary to what FOL said in my other other thread    )

In my other thread was about Another World showing the black-screen-of-death and a red text box Guru Medication.

[FOL]

Switching to the new tool chain, would proberly fix the not showing error message. Only problem is, the new toolchain causes to many issues, we loose alot of speed, cant use G8 optimisations, cant use O3 optimisations, gives errors in the code.

I can get it working, but then we end up with a nasty bug where savestates refuse to work. Im just not able to deal with this as im not able to see problem as it all compiles fine.

I might also point out, that I never implemented the error system, so im unsure on how it works 100%.