Ps3 Emulator V 1.1.7 Bios Fatal Error 2.5.1

0 views
Skip to first unread message

Margaret Sieverding

unread,
Aug 19, 2024, 9:57:12 PM8/19/24
to studledlika

I did see this thread. However, what is puzzling me is that the emulator can run other cartridges, including some that I built using 7800basic or cc7800. Just not the one built straight from assembly.

ps3 emulator v 1.1.7 bios fatal error 2.5.1


Download Zip https://psfmi.com/2A3flm



Actually I realized that, even when the cartridge loads, I do get the "OPTIONAL 7800.u7 NOT FOUND" error (I tried fixing it, to no avail). So I guess the issue is that the cartridge load fails for an "unspecified" reason.

Exactly what Atarius Maximus stated. The ROM you are utilizing does not have a proper header. Your binary file needs to contain a proper header in *.a78 format. See the below link for more information:

I went and tried to move files around so I could be xbmc emustation on drive E as I had it on F. Now when I boot up the xbox I get a fatal error message

"special://masterprofile/guisettings.xml, Line 0 failed to open file"

Now am I completely ruined or can I just somehow boot back to a dashboard and reinstall xbmc emustation?

Rocky5's dashboards etc, like XBMC Emustation, may have some sort of backdoor recovery options. Whether that is correct and applicable in this case I do not know. You'll need advice from somebody who knows XBMC Emustation.

Are you using Rocky5's softmod? That's important because it is automatically set up to launch XBMC Emustation from C:\, E:\ or F:\. If another softmod was used it is likely the thing was being launched from a shortcut.xbe inside the XBMC folder. If that is pointing at F:\XBMC\default.xbe and the XBMC folder is now on E:\ that would explain the problem.

It depends on what files you actually moved but I'm thinking that the error message is not indicating just a problem with the guisettings.xml which could be bypassed by tools built into XBMC and its variants. Its basically telling you the installation is messed up.

It is probably going to be quite simple to fix with FTP/disc based file manager because, sweetdarkdestiny has also just posted, all that likely needs be done is to replace everything you moved from F:\ to E:\. You can then get advice on how to move it to E:\ safely if you're still wanting to do that for some reason.

When I installed XBMC Emustation it put in on F:\ and I want to move it to E:\ because based on another post by Rocky5 he stated it's best to run Emustation from E:\ and have the emulators, media and roms folder on something like F:\ as to not slow down seek times when accessing games.

So now that it has been installed on F:\ what is the easiest/painless way to shift Emustation to E:\ while leaving emulators/media/roms on F:\

Iif you're using a Rocky5 softmod he puts almost everything on C:\, protected by using a Virtual/Shadow C. So how and the path it uses to boot the main dash is very different from, for example, SID/AID. By default that installs (vanilla) XBMC on E:\ ie. in its own folder and boots the default.xbe in the XBMC folder by using a shortcut XBE: E:\evoxdash.xbe.

I'd be looking at the actual folder path and file names in a file explorer too. In particular, especially if you've renamed anything yourself, check for accidental spaces that have been added between or after characters/names.

I ask because I have an uninstalled zip of XBMC Emustation and when unpacked on PC it is set up like this: XBMC-Emustation (folder) and inside that > .emustation (folder), system (folder), default.xbe (file), splash (logo image file). I would assume that is how it installs. If your installation does not match then that could be the problem.

You know what, that is all that it was ha! I went in and removed the spaces and it works fine now. I'm not even sure how those got in there to begin with as I don't remember renaming it at all.

Thanks for all the help!!

So this kind of brings me into a new set of questions. Maybe I could move this part to another thread, but what is the difference between the file/drive layout when I view it through the dashboard file manager and the file manager through XBMC Emustation?

Regular first, then XBMC Emustation

While XBMC-Emustation is running, FTP to the console and download the file Q:\system\xbmc.log. Open it on your PC in a text editor and look for the mapping entry in the log file. I suspect it is mapped to the scripts folder.

Having issues with getting 7800 games to open on MAME through Launchbox and I simply cannot figure out why. I get the following error message every time I try opening a game through Launchbox in the first image.
I'm not sure what it is saying as all my roms are in .a78 format and I've searched online if anybody else has encountered the same error but couldn't find anything else so any explanation of it is appreciated.

I'm pretty sure I have the correct bios folder with everything necessary in it in my MAME roms folder as well (a7800), although I'm thinking its a problem with how I have MAME configured on Launchbox. Second image below is my current configuration.

r/MAME - Trouble emulating Atari 7800 on MAME
I'm thinking by command-line might be incorrect somehow or I just don't have it configured right in general. To be honest I'm not sure, I've been troubleshooting for awhile and I can't figure out why the 7800 specifically isn't working as other consoles like the 5200, Colecovision, and the Vectrex work just fine through my current configuration on Launchbox.

1. Outside of Launchbox, MESS doesn't load the console at all and gives me the error attached. As for MAME, the console will load with the cart empty but when I try to load a rom it gives me the same error message. So I'm not sure if the problem lies in my ROM set or the bios itself.

2. I use MESS because of a video tutorial that used MESS to emulate the 5200 and I've used it ever since. I am aware of the merger but I like keeping my Arcade games on MAME and consoles on MESS and the video showed how to obtain a version of MESS that I'm not entirely if you'd called it "old" or "new". This is the video in question:

So I ended up getting a new ROM set which worked great without issue so the original set I had was likely a bad dump so thank you both for making me realize this, I wouldn't have otherwise. I think its safe to say my problem is fixed, thanks again, I greatly appreciate it!

I've been trying to get the a5200, a7800, and Colecovision to run from GameEx using mame64. I have been able to get the a5200, but the other 2 are not running for reasons I can't explain. I have been trying debug this from the command line, and it complains that it can't find the colecovision BIOS file. When I look at the path in the command line and follow it in the file system to the BIOS zipfile, the file that it is complaining about is there....Does anyone have any ideas on what the problem is or other things to try? I will attach a screenshot of the error at the command line and show the location of the file which it says it can't find as well as the config for the emulator if that helps generate any thoughts. Thanks! -John

Description: If the RShim service is running on an external host over the PCIe interface then, in very rare cases, a soft reset of the BlueField can cause a poisoned completion to be returned to the host. The host may treat this as a fatal error and crash.

The games I was having this problem in were Battlefield 2042 and Dead Space. As you mentioned, I would watch my GPU LED's shut off, the CPU debug light turns on, yet all fans continued to spin until I used the power reset switch on my PSU to reboot.

the fact that crash occurs with 7900xtx doesn't mean it is the cause , you can have forgotten to "load setup default" in bios when you change from one gpu to another , or if you don't do DDU when uninstalling drivers ...

Hey man, got the exact same issue here. And the fact that I have also have the same mainboard (MSI B450 Tomahawk Max) makes me kinda curious right now. Please let me know if you find a solution for this problem.

My CPU is a Ryzen 9 5900X and I have a 1200W PSU. at this point I might suspect the motherboard to be the origin of this problem. Somehow when I first installed the new GPU, everything worked fine and I also had no crashes or anything, but after a while it just started crashing constantly as I tried to play the games. Didn't change anything on the hardware or in the game settings....

I see you say you've tried other psu cables and slots but have you tried a completely different psu? I had crash issues with my 7900XTX as well and it turned out that a brand new 1250w Inwin psu was the issue all along. I even had it stable for a time when I changed monitor so it was really hard to solve the issue.

I'm in the same spot as you, my PSU is brand new, and I'm starting to suspect that it is the culprit. I haven't tested another CPU on mu machine but for the last 2 weeks I've tested this GPU on another machine, and had no issues. Step by step I'm trying to test every hardware configuration to try to isolate the issue.

I have similar issues, but my crash is only while browsing or on desktop and are random....never while gaming....i just change my connection from 1 cable split in two for 2 differents cables on separate rail.I will get back to you if the problem is solved...but i do think my psu is the problem since it start to coil wine just after i upgrade my gpu(was on 6700xt before whitout problem)

2 days since i plugged the gpu on 2 separate rails instead of one splitted in two.....finger crossed its solved the issue...for know...no crash and better benchmark score whitout even overclocking....i really do feel that the problem is fully or partly solved....

b37509886e
Reply all
Reply to author
Forward
0 new messages