BL4K3Y

Here you go: http://www.realmodscene.com/index.php?/topic/439-how-to-set-up-f3-and-link/.

Do you have a way to read/write to the NAND if things go wrong? You can write an image with XeLL - rename the NAND image to updflash.bin (you might need RawFlash if you don't have the latest version of XeLL on the NAND), put it on the root of a FAT32 USB stick and boot XeLL with the USB stick connected to the console.

As long as you haven't written anything to the NAND, it is safe to read again. Do not proceed with writing a new image until you have at least two matching NAND dumps.

The person who sold the console to you is a friend of mine and he will make sure everything is running as it should be.

If you want FSD to swap discs, the DashLaunch Disk Swapper plugin must be disabled. You need to set the scan depth based on how many folders you need to go through before you get to the files for a game - a scan depth of 4 should be fine.

Try using XeLL Launch. Also remember that "xenon.elf" must be present on the root of your USB device or XeLL won't be able to launch it.

I am in the UK and I don't mind taking a look at the console for you.

Enabling the "autofake" option in DashLaunch should also work. It is designed to enable/disable fakelive when it is necessary to do so.

Good stuff! It was probably caused by the "Default" line pointing to a directory/XEX that didn't exist. By the way, I wondered WTF you were talking about when I got your PM on TX and then I realised lol .

You should have a folder with the game name and inside that folder should be a folder for each game disc. To remove duplicate covers from FSD, press "Y" on each duplicate cover, select "Move Game" and then choose "No Section". The extra discs will still remain on the hard drive and in the FSD database, but you will only see one cover for the game (disc swapping will take place automatically).

Yes, if you really wanted to (FSD allows you to set paths to folders).

I am well aware of how FSD works - I have used it since the first release lol. My point was that the OP should be able to relaunch FSD from a game without any issues because of launch.xex holding launch.ini's "Default" parameter.

I don't mean to contradict what you are saying, but I am sure that the "Default" line in launch.ini is passed as a parameter to launch.xex in the NAND. This means FSD should be able to relaunch each time without a problem because the "Default" parameter in launch.xex would still be loaded in memory (this is how I interpret and understand it). I could be way off the mark - somebody please correct me if I am .

What does the "Default" line in launch.ini say? An example would be "Default = Hdd:FSDdefault.xex".

What are you expecting it to do? It should tell you that your login details are correct and say something about the connection to JQE360 being successful.

It sounds like you may have an issue with CPU_RST. Have you got any photos of your install?

Are you using the installer or are you manually copying the FSD files to your HDD? I have FSD in the directory "XBOXFSD" on my external hdd and it runs fine when the HDD is connected to one of the front USB ports. That debug log tells me that F3 is unable to find (or is unable to extract) the skin file (Default.xzp).

Can you be more specific about your issue? Does the console boot sometimes, but not others or does it just refuse to boot at all?

I already put that in the tutorial at the bottom.

Have you got your J-Runner log?

AUD_CLAMP wiring is the best wiring for HDMI consoles (move the ROL wire to the right leg of Q2N1). Don't forget to build your image with an AUD_CLAMP SMC.

Try changing the scan depth.

Your CPU key will be displayed in XeLL (boot the console using eject).

Disable the F3 plugin.

Can you post a screenshot showing what is inside both directories please.