Swizzy

That's the part that guide is for, in order to update F3 you need to change settings so that it looks for beta updates, then you can update to the latest version... Or you can download the latest version and manually replace the files on the console =)

since you've got dashboard < 14699 and a falcon it'd work just as well with RGH 1.1

there is no such thing as "exFAT32" there is however "exFAT"

As it's a USB driven drive, have you checked that it is indeed getting enough power? (does it make any strange sounds?)

That's a quite common thing to get... bad blocks... however, that status code isn't one of the standard ones... this one means: ECC Error Detected & Interrupt (not sure exactly what that interrupt means... but... it's probably safe to treat it like a badblock, which you don't have to do on your own (xebuild auto remap bad blocks for you...) Next you want to update your consoles dashboard, follow one of the links i gave you earlier, etheir to the network guide, which is quite easy to follow, or use my manual guide [should also be quite easy to follow, but have more steps in it)

Installing F3 have nothing to do with the format of your internal harddrive... formatting the internal harddrive is done in the original dashboard... About formatting your old hdd to NTFS; you'll need to go to the "Diskmanager" in windows and rebuild the partition table THEN you can format it like any other...

Try replacing the font as is stated in the readme...

Put this on a USB Memory stick: http://www.homebrew-connection.org/files/xbox/nand_flasher/dl_Simple_360_NAND_Flasher_v1.3_BETA.rar and run it on your xbox (unrar it first) you'll probably need to go to the filemanager to launch it (just select "default.xex" and press A and it should start) once you've done that, follow the on-screen instructions, if all goes well you'll have both your nand dump and cpukey on your usb memory... If that doesn't work, let me know and i'll make a package for you to run a newer version of XeLL that should work...

The internal hdd is supposed to be XTAF (byte reversed XTAF) and... that's done from the dashboard itself... it doesn't really matter what you format it as before doing so tho...

Are you talking about an external or internal harddrive? there's a difference... external = USB, those need to be FAT32 and that have a different limitation compared to XTAF (which the internal drive uses) External have a limitation of 268,173,300 files which is an insane ammount... you'll not reach that any time soon even if you have hundreds of games on that disk

Depends alot on the games, if you're going to use the internal harddrive for your games i would recommend you use the GOD format instead of the XEX format... that renders less files most of the time

Well, it's quite difficult to say, do you have XEX versions of games on your internal harddrive? this can be the cause of the issue (to many files) some games have a truckload of files...

Personally i use XM360 or F3 for FTP server and Filezilla on my PC I think you're having an issue with the harddrive tho, it might have to many files, to many bad sectors or something... the filesystem doesn't support an infinite ammount of files, however... it should support a insanely large ammount of files... you may also have other problems such as path name, file name etc... check this for more info: http://www.free60.org/FATX#Limitations

http://lmgtfy.com/?q=crc32+windows or if you're using macintosh: http://lmgtfy.com/?q=crc32+osx or if you're using linux: http://lmgtfy.com/?q=crc32+linux one of the above 3 links should help, CRC32 is VERY common, infact, you can even use any SFV tool... it also generate CRC32... any of 'em should be a-ok ** edit: ** I did have a tool made entirely in C specifically for this while i was adding the crc32 stuff... it was nothing special, just a random crc32 implementation, after a little tinkering i was told where the fault was (i had taken this code as-is and just put it in the 360 code... problem with that is that the crc32 implementation is different from "big-endian" which the 360 has, compared to the "little-endian" which most computers use (windows always use little endian i think) The difference between big and little endian is nothing you'll need to worry about unless you are going to start developing stuff on your own or create patches or so for consoles... but, if you do want to read about it, here's a link: http://en.wikipedia.org/wiki/Endianness

It's the game logic, live with it or hack the game

Do you have enough free space on the drive?

Quite normal, the cars are generally region based, you have a "set" of vehicles for different regions in the game, it's then randomly generated which colors they have and which exact one is going to be there...

If you use the automatic mode (the cmd file) you need to generate a CRC32 hash of the updflash.bin and put this in a text file named "updflash.crc32" however, if you use the manual mode ( press A or B ) you don't need this file (it's purely for safety, if you transfer your nand over network it may end up beeing mangled... having a CRC32 requirement in order for the automode to work adds a small layer of protection against potential bricks) And yes, i do make alot of tools/fixes, i didn't make XeLL-Reloaded v0.993 myself, but i had a big part in it

Corona don't power on when you press eject after a power cycle, however... once you've started with power once it'll accept eject as a valid startup reason (dunno why) other then that any xell version older then XeLL-Reloaded v0.992 don't have Corona video support, there is however one that was unofficial that had HDMI support for coronas

You most likely have an old version of XeLL in your nand, and the reason for not updating F3 is because the newer versions are all "Beta", so you have to enable that option in order to update that part... Judging by you having rev 0.58 i'd say you've probably got and old dashboard aswell, so i would recommend updating the entire console, you can read a tutorial i've written here: http://xebuildtut.xeupd.com or the one jpizzle wrote for xebuild 1.08 (easier): http://www.realmodscene.com/index.php?/topic/2205-xebuild-108-update-tutorial/ I do however recommend that you before doing anything else dump your console using Simple 360 NAND Flasher, then store the dump made from that in a safe place...

What was the last thing you did? did it work before? have you tried starting with eject? how long have you waited for it to start? did you do the installation yourself or did someone else do it for you? does the chip have a green led blinking every 5 seconds~ or is it always lit green, or just red? There are many things that can cause this problem, we need more information about your situation then "it doesn't work, it's a genuine TX product..."

It's not at all better, in reality what you're doing when you set your fans at a low speed is steer your box down the road to RROD... if you don't want to hear the box... put it in a different room and set the fans to max (100%) Setting static fan settings is a BAD thing (unless of course you set it to the maximum) the recommended method of changing how the temps are in the box is to lower the treshold values... of course, this does come at a price... higher noise... Low noise + low temperature don't come hand in hand, never has, never will... not without swapping the entire cooling system to a water cooling system anyways, that's the one possible method of having low temps and low noise levels...

It's possible yes, it's just not something someone would want to do... because it takes up computing power for nothing and it'd probably cause issues with the controller input...

I highly recommend changing the temp settings rather then changing the fan setting... if you change the fan settings it should be no lower then 100% to make sure it doesn't cause other problems (overheating all together if your environment gets warmer)

You would have to build it using the official github repo with my branch (mine is experimental, when it's deemed a-ok it gets moved to the official one then i start doing more experiments the reports i've had so far suggests everything is working fine... but i haven't had time to work on it lately... maybe i'll make a quick release within a few days...