Jump to content
RealModScene

noob99

Members
  • Content Count

    6
  • Joined

  • Last visited

  • Days Won

    1

noob99 last won the day on July 25 2018

noob99 had the most liked content!

Community Reputation

1 Neutral

About noob99

  • Rank
    RMS Freshman
  1. But the Xbox was running just fine. I did not do anything to the NAND or DashLaunch for at least half a year. So why the sudden trouble? And for the settings of DashLaunch, I used the default settings and only changed the "default path" to Aurora. Also I did a clean install of the NAND without DashLaunch and installed DashLaunch via the Xbox. But I will try to install DashLaunch via J-runner. I let you know if it resolves my problem and update on other things I tried.
  2. Sorry, my bad. Just critical thinking and the urge to understand. Thank you for helping, I am a little wiser now
  3. Okay, did not know that. Though I am still not convinced (maybe i should try it, but I can not at the moment..) Since DashLaunch knows launch.ini file is saved at the hdd. The second why it sould prefer an empty launch.ini file over a configured one, unless this is done on purpose, as a fail-safe. In that case its make sense
  4. Thanks for the suggestions. Party Buffalo Xbox 360 Drive Explorer was a big help. I did not try the empty lanuch.ini file, but it also would not help as I will explain. The Xbox 360 was now working again with the hard drive, but as soon as I installed DashLaunch I got the Fatal Crash Intercepted (FCI) message. So I dumped my NAND and made a new one in J-runner and wrote it back to the Xbox. And as soon as I installed DashLaunch... the FCI message appeared again. For now it is working, I boot to XeXMenu and then select my game... no problem at all. The Xbox 360 was configured with DashLaunch to start Aurora automatically. Now is the question has anybody got an idea why I got the FCI message after installing DashLaunch?
  5. Hello, Here is an interesting problem, anyone got a solution or a cause of the problem? After the weekend, when booting my Xbox 360 I got a Fatal Crash Interception. I tried to boot multiple times, but with the same result. Other forums suggest to boot and press the eject button to unload my plug-ins. Here is were I got the idea that something is wrong with Dash Launch or with the launch.ini file. But trying this resulted also in the message: "Fatal Crash Intercepted". After I opened my Xbox 360 and removed the internal 3.5 inch hard drive, the Xbox boots straight into NXE. So something is definitely up with the hard drive. Now I want to delete the launch.ini file, but it is on the hard drive, which I cannot reach/read. When booting the Xbox without HDD and then connecting the HDD results in a reboot and a fatal crash. Stuck again. Now I was trying to update the NAND... maybe it helps, but the NAND was already updated to kernel 17349. When I was trying to dump the NAND, I was searching for programs. And I tried three programs: Flash360, NAND flasher for Xbox 360 and Simple 360 NAND Flasher. This resulted into, wtf, three different NAND dumps . Is this normal? Currently I am out of ideas... Except for swapping the hard drive, but it has too many games on it. Anyone got an idea?
  6. I have also problems for requesting the API key on Aurora. Filled in the API key manually, but it fails when I try to download the cover art. Really sucks, was working really nice on FS3 (with JQE) Username: BA360 If someone can check why it is not working, would be great!
×
×
  • Create New...