Couple of bugs ;)

Started by Art, July 18, 2007, 12:29:31 PM

Previous topic - Next topic

0 Members and 4 Guests are viewing this topic.

Art

Hi Guys,
First of all, thanx to Ric, FOL, and whomever else is currently working on PSPUAE,
or helping toward it's continued development.

I posted on DSemu, but just in case... many of my games that loaded in older PSPUAE
versions (however unplayable) did not work with the Birthday Edition until I zipped them.
I would not have known to try this, but was lucky to be persistent enough.
The second little issue is that I get no error message when a Kick file is not present,
or named incorrectly, it just bugs out to XMB without explianaton.

But hey, all in all, I'm having a ball with it as an ex-owner of many A500 machines,
and several CD32s at different times in my life.

I don't think I will bother with aquiring any real Amigas again, but PSPUAE is great :)
Cheers, Art.

skateblind

#1
Hi!

The kickstarts crash you speak about is not a bug, it makes sure you have at least one available and have it named correctly. Its all in the readme that came with the release.
*EDIT* Just read your post again  ::), and I see the problem you had was that there was no message explaining this, I'm pretty sure one of the coders could add a small error function to display messages explaining the crash, but this would take a while to get right(if possible). It would also be a bit silly to add a new functions to check for individual errors, so a universal error catcher and message displayer would be needed, but would take up a lot of time to code and get right, I guess. Im not a PSPUAE coder/developer, so this is all speculation based on previous discussions, so I would wait for a response from one of the coders, most likely FOL since he handles public relations on behalf of the coders ;) *EDIT*

What type of files are you playing your games from, ADF(.disk) or States(.asf)?

It might have to do with the config files(.options) in the CONFIGS folder being from older versions. Parts of those configs are probably trying to set the memory to illegal amounts or to options that are not available anymore in the  new release.Because you zipped them they will no longer use their old configs because the files names are different, although Im not sure if ZIP files use the config files at all anyway, eg. AnotherWorld.adf would have a config called anotherworld.options. so when you load that ADF the config will load automatically, but if the config was for an older version, it might not work.

Possible Solution:
If you copied over your old PSPUAE install, then I would suggest removing the entire installation from your memory stick, which would be the PSPUAE folder. Then copy the new release into the correct place, as well as your games(ADFs or save-states(ASF)) and then try again. Do not copy your OLD configs across, use/make new ones.

Thats the only solution I can give with the little amount of information you have given.
I hope that helps.
What are you looking at?

EmuChicken

aye - start from scratch! :)  - a clean directory!

I've mentioned about the error messages...  but if you are using a dark alex firmware, extract the single directory pspuae archive to the GAME340 (for 3.40OE-A) and then run it to get the messages...

FOL

Quote from: EmuChicken on July 18, 2007, 02:14:11 PM
aye - start from scratch! :)  - a clean directory!

I've mentioned about the error messages...  but if you are using a dark alex firmware, extract the single directory pspuae archive to the GAME340 (for 3.40OE-A) and then run it to get the messages...

Emu and Skate are correct. The Kxploit eboot, just doesnt seem compatable with Custom Firmwares in regards to using the psp's own message display's. I have another idea to try to sort this, but after discovering something and discussing it with GnoStiC, im abit more involved with that at the moment. Rather not say what it is until its 100% confirmed.

Also, i have not had any problems with .adf's or .zip's, if you can try what the others said about starting fresh. see if that helps as in most cases it does.
QuoteResolute and Industrious
Grand ruler of the yellow people and the Ultimate Amiga Empire

Hungry Horace

i have a suspicion that blitter cycle exact and immediate blitters are the wrong way round

i base this on "plutos" where you ship blows up by itself, without cycle eaxct on winuae....   on pspuae immidate blits fixes it.


this might also explain the problem some people have been having with SWOS savestate career mode.
Quote from: KillerGorillabecause winuae is made of code and your amiga is made of stuff


Hungry Horace

scrap that.... memory serves me wrong

seems immidate blits DOES fix it on winuae.

strange that i never got the amiga online version working then.... coulda sworn only cycle exact made winuae-kaillera break  ???
Quote from: KillerGorillabecause winuae is made of code and your amiga is made of stuff


Art

It's ok, there's no longer a problem for me once I posted here.
Everything seems to work if it's zipped first which is probably better for me on the PSP.

I am using a new install, and copied the kick13.rom and adf files over.
Also I'm using the single eboot file, not kxploited folders.

I didn't know Sony's message screens were used, no wonder they don't work.

Haven't used savestaes yet, but the concept sounds interesting.
Cheers, Art.





skateblind

Glad to hear you have managed to sort it out.
States have been specially set-up for quick loading and to be run at the best speed PSPUAE can run them at, although some might be able to go quicker with different settings, but doubtful.

@FOL, Are zips just the same as ADF's or will not be as compatible/stable and does it affect the overall speed of it compared to ADF's?
What are you looking at?

FOL

Quote from: skateblind on July 20, 2007, 02:54:08 PM
Glad to hear you have managed to sort it out.
States have been specially set-up for quick loading and to be run at the best speed PSPUAE can run them at, although some might be able to go quicker with different settings, but doubtful.

@FOL, Are zips just the same as ADF's or will not be as compatible/stable and does it affect the overall speed of it compared to ADF's?

They are used same way, zip's have little effect on speed. Im still conserned that he can only use zips to play.
QuoteResolute and Industrious
Grand ruler of the yellow people and the Ultimate Amiga Empire

EmuChicken

mhmn, could you zip your pspuae directly and send it to some guys email address / fols / whoevers...

Art

Sorry for the lateness. I am checking in though.
Yes I certainly would send the files if anyone cares to pm an email address.

Some specific examples are:
Workbench 1.3 disk works if zipped or ADF,
Pinball Dreams both disks need to be zipped,
Interference demo by Sanity needs to be zipped.
(Interference is a file system disk like Workbench).

@ FOL, with reguards to ADF files, it is traditional format for Amiga emus,
but I don't particularly care if support for them was discarded,
but it seems ADFs are working for everyone else.

I stayed at 3.03 OE if that makes any difference. Most ppl would have
upgraded for compatibility with later UMD games.


FOL

#11
Quote from: Art on July 23, 2007, 01:01:25 AM
Sorry for the lateness. I am checking in though.
Yes I certainly would send the files if anyone cares to pm an email address.

Some specific examples are:
Workbench 1.3 disk works if zipped or ADF,
Pinball Dreams both disks need to be zipped,
Interference demo by Sanity needs to be zipped.
(Interference is a file system disk like Workbench).

@ FOL, with reguards to ADF files, it is traditional format for Amiga emus,
but I don't particularly care if support for them was discarded,
but it seems ADFs are working for everyone else.

I stayed at 3.03 OE if that makes any difference. Most ppl would have
upgraded for compatibility with later UMD games.



Whoops, misread this 1, til skate pointed it out.

.ADF is the standard and IS SUPPORTED. Why you think its been dumped, beats me.
As I asked over at DCEmu, please supply me with .adf's so i can test yours on my PSPUAE install. As I  think you have a problem with your install, hence your adf problem.

Also, are you using the correct, eboot? I know everyone (well nearly everyone) has their game folder set to kernel 1.50. I will say this only once, DONT use the v1.50 eboot, if you must keep game folder set as kernel 1.50, just use the 1.00 (also marked custom firmware) folder version of PSPUAE in the game350 (or in your case game303) folder.

As you might be aware of the problem Emu found and i think it has something to do with a conflict between 3.xx kernel and 1.50 kernel in custom firmware.

EDIT:-
I have been doing extensive testing with these .adf files;

Jaguar XJ220 (NON AmiDOS) Working fine
Lotus 2 (NON AmiDOS) Working fine
Turrican (NON AmiDOS) Working fine
Turrican 2 (NON AmiDOS) Working fine
Xenon 2 (NON AmiDOS) Working fine
AnotherWorld (AmiDOS) Working fine

As you can see, All these games run absolutely perfect from .adf file's. I would really like to know where your .adf's came from, cause we have had our release's, downloaded from else where and they repackage it with files and .adf's, which has caused us problems in the past.
QuoteResolute and Industrious
Grand ruler of the yellow people and the Ultimate Amiga Empire

Hungry Horace

getting some problems with having set up a manual zoom / view settings....

set up for eotb, saved, worked fine on reload, but wont set up properly when loading the state after re-booting pspuae.

hmmm.

investigation required.
Quote from: KillerGorillabecause winuae is made of code and your amiga is made of stuff


EmuChicken

So you're saying that the manual zoom settings arent being saved correctly?

Hungry Horace

Quote from: EmuChicken on July 25, 2007, 12:06:34 AM
So you're saying that the manual zoom settings arent being saved correctly?

no, i am not 100% sure yet, (tried to reproduce it, and it worked ok... doh!) but i think it may be to do with trying to switch off auto-zoom, when manual zoom is still on?  as a result, it switches it off again and then screws up the manual screen settings (changing zoom values etc)

it would explain why it happened when just starting pspuae, and not later on.
Quote from: KillerGorillabecause winuae is made of code and your amiga is made of stuff