outofwork

One little nagging problem remains. Whenever I am playing a game and depress the Guide button on the wireless controller to quickly exit the game I am presented with what appears to be the standard (non-F3) dashboard which has the following displayed: Xbox Guide Xbox Home Join Xbox LIVE Open tray If I hit the Guide button again it reboots F3. I assume that something in the configuration (INI ?) file is wrong and I probably caused it. How do I fix it and how to I get to the launch.ini file to edit it assuming that's what I need to fix? As always many thanks for the invaluable assistance, outofwork

For others who may have the same or similar problem... problem resolved. For some reason I had to increase the scan level for the XBLA games to 1 higher than what would work under FSD2.2. If you are having a similar problem try increasing the scan level. It worked for me. outofwork

I am trying to resolve the problem/bug(?) that I have with F3 regarding XBLA. It says that I have one game when I have over 100. It shows the graphics for that one game to the left and right when I scroll what should be the covers for the other 100+ games. When I select any of the covers it will start the one and only game that it thinks that I have. I tried deleting the path and rescanning and that didn't fix the problem. I am assuming that the database in question is HDD1FreestyleDataDatabasesContent.db. I have tried to move it to make a backup so that it could be rebuilt and apparently it has a read only attribute associated with the file and I don't know how to change it so I can move it. Has anyone else reported the problem and is there a way to fix it? Thanks, outofwork

Yes, the install process for FSD 3 has an option to remove the previous version of FSD and I would strongly recommending selecting that option as well as literally all the others to include checking for the latest update which it will download. The installation of FSD 3 is so slick and so fast that you think something is wrong.

Take your pick as there are many, many programs that will work just fine. I personally use Nero. The install for FSD 3 is so easy it's unbelievable. I would recommend removing the previous version and checking for the latest update. As I recall I think that I checked all the boxes.

Perhaps I could assist in some small way if your setup is similar to mine. The administrators here held my hand through the process and I greatly appreciated their tolerance and patience. I learned quite a few things not all of which I have committed to memory but I have a pretty good understanding on the overall process. Outofwork

Thanks. I had already proceeded and everything looks fine except that it says that I only have one XBLA game on my external 2 TB drive when I probably have over 100. That and it is showing the same cover for that one game when I move left to right or right to left looking at what you would think be the covers for the other games that exist on the external drive. I deleted the game path for XBLA and recreated it but that doesn't seem to make any difference. I don't think there is anything that I could have done to cause that but given my success rate lately who knows. I again apologize for all of my basic, stupid questions. It's been interesting and a good learning experience. Thanks, outofwork

I'm still fiddling with this and here is what I just did. I booted up into FSD 3 and then went into the normal Xbox Dashboard went into System Settings, Console Settings, System Info and I inserted the USB stick with $SystemUpdate 16197 with renamed the folder to $$ystemUpdate and got the following: ? Update Required To proceed , security and program updates are required. System updates will be added to ensure security and proper functionality. If you decline, you will be returned to the Xbox Dashboard. Do you want to accept the update? I did not proceed because I'm a little bit concerned about the security wording in the message. Is this the normal update message and is it safe to install the update? I still cannot figure out why the USB stick won't boot. Also, the system info displayed shows the following: Current Setting: Dashboard: 2.0.16197.0 Is this because when I ran XeBuild GUI with the system files for 16197 it updated the NAND (?) but the $SystemUpdate will update the binary code for the functionality for the 16197 update? I'll be damned if I know why this is still confusing. Is there a basic tutorial that goes through the functional description of each of these pieces? Thanks, outofwork

Well I seem to be snake bit yet once again no doubt due to my not having a clear understanding of the process. What would logically seem to be the easiest step in this won't work. I formatted a USB stick FAT32 bootable, copied over the $SystemUpdate folder and renamed it to $$ystemUpdate. Then tried to boot it up (normal power on) by inserting it in one of the USB ports on the front of the console. It went into FSD 3 with no option for any update. I then tried booting with the eject button that kept searching for a xexon.elf file. Clearly that's not the right way. I'm missing something here. How does the console know what to do with a folder named $$ystemUpdate? There is no default.xex file in the root directory except all of those separate ones inside of the now renamed $$ystemUpdate folder which is not what I want to do for sure. This process should kick itself off but I don't know how it can without a default.xex file. Sorry for being a PITA, outofwork

Yes, that's clear and I will use the USB stick. However, given that I am innately curious... is the default.xex update specific? Thanks, outofwork

There are rewards and punishment to being too conservative and I have recently experienced both. However, I am now ready to apply $SystemUpdate 16197 from Microsoft to complete the updates. Can I use the default.xex from $SystemUpdate 15574 or are they update specific? I have $SystemUpdate 16197 but I don't have the default.exe for it. Yes, I am being very cautious. Once I finish the 16197 update is there a way to make a complete Ghost-type image of the HDD drive for backup purposes so that I could do a restore in the event of a hard drive failure? Thanks, outofwork

You're absolutely correct. Thanks for clearing that up. So I will give this a shot. Unfortunately the older you get the longer it takes to finally sink in. Actually I never did have a completely clear understanding of how all the different pieces fit together. I'm still not 100% but I am getting there thanks to your assistance. Thanks, outofwork

If the Dashboard limitation is due to the way that the original RGH mod was implemented and it's a hardware restriction then I would think that it's almost impossible except in rare occasions for software/microcode (like the XGD3 LiteOn burner mod) to overcome a hardware constraint. So, the more I think about it the more I think I am misinterpreting the last announcement even though it says ALL JTag/RGH consoles can upgrade to $SystemUpdate 16197. Please set me straight on this and I will go away... at least for a while. Thanks, outofwork

Okay let's see if I have this correct. Yes, this will allow me with my old phatt Falcon (v3.0) to go to the latest $SystemUpdate from Microsoft which is 16197 after 16197 system files from the zip are combined with my existing NAND image and the NAND is reloaded. I can then apply $SystemUpdate 16197 from Microsoft and then install FSD 3.03. $SystemUpdate 16197 from Microsoft is not available yet on the MS web site as I believe it is being rolled out on a limited basis, perhaps overseas initially. How was the restriction of not going past the Dashboard prior to 15572 overcome on a Falcon (v3.0) CB:5771 original RGH console? I'm curious what the restriction was and how it was overcome. The technical folks that do this work for the scene are incredibly gifted and I certainly appreciate their efforts. Thanks, outofwork

Okay, hopefully I am not misinterpreting this announcement. Can this possibly mean that my old phatt console with a Falcon (v3.0) MoBo CB: 5771 which means that I have the original RGH which I thought was prevented from implementing a Dash any higher than the one that preceded 15572 can now use the latest and greatest Dash 16197? I did not see any availability of Dash 16197. Has Christmas come early or is this a sick joke on the poor Noobs like myself?

"** NOTE ** if you install this over your existing FSD it will DELETE YOUR DATABASE. NEW INSTALL ONLY! you have been warned." built on the first scan following the installation? Sorry for such a newbie question but can I "assume" that the databases for installed games and XBLA will be rebuilt on the first scan following the new install? Thanks, outofwork