outofwork

Once again I will display my ignorance about the details of this. I can't find dashlaunch to update the settings for launch.ini. Can I assume that the last time I did an update for the console that dashlaunch it's possible that it did not get installed and something else created the launch.ini file telling launch to boot into FSD? I am currently at dash 2.0.16547.0 Is it also safe to assume that if that in fact did happen that I can simply install dashlaunch and go through the process of changing it to boot into Aurora? I feel really stupid about asking all these questions but my rationailzation <BSEG> is that I rarely do anything with the console except either just prior to my grandsons coming over or every few months when I want to install some new games. So, I really don't do much with the console except for maybe a couple of times in a year.

You know that old saying about being snake bit? Seems that this week I may be the poster child for that expression. Earlier today I booted into FSD, executed Aurora, retrieved covers for over 600 games, etc. Everything going along just fine...finally. 30 minutes ago I turn the console back on and it will not boot into FSD. What happens is that either the XBox 360 logo stays on the screen forever or it boots directly into the normal MS dashboard. I know that this is a paranoid question but is it at all possible that Aurora could have reset something that has caused this? If not, it's one helluva coincidence. The only thing that I did at all was put an updated launch.ini in the root directory on the external drive so I could copy it over to HDD after it booted up. Please tell me that I'm not royally screwed here. I have powered the console off and back on three times and twice it booted into the MS dashboard and once it just hung displaying the Xbox logo. I did notice that when it boots into the MS dashboard that my alias is being automatically logged on. It seems that if I disconnect the external drive before I power up the console it will boot into FSD as before. Is it at all possible that the bootup is reading the updated launch.ini, which says to boot aurora.xex off of HDD, which of course I haven't copied it there yet, off of the root of the external drive and not finding aurora.xex where launch.ini says it is that it just reverts back to the standard MS dashboard? It seems that I may be learning a lot about the details of how all this works because of all the problems that I have had this week. I am going to move the modified launch.ini out of the root directory into a directory on the external drive to see if that is what the problem is. This is weird as hell. I'll be damned. That's what it was. I moved the modified launch.ini into a directory on the external drive and now it boots into FSD as it should. In some cases that could be to your advantage if it looks to the external drive first.

Many thanks. I got the answers to some of my questions already by reading through all of the Aurora topics.

As you indicated Aurora is very slick. I am impressed with the amount of work that had to have gone into Aurora. A few questions as always: 1) Is there a text editor that is available so I can edit files without having to go back to the PC to edit files? 2) Do I simply copy Aurora to HDD, put it in a new folder and create a path statement for launch.ini that would look like this: hdd:\Aurora\aurora.xex Can I assume that when I press the Home button that the game will exit and reload Aurora? 3) Here is the launch.ini for FSD: [QuickLaunchButtons] Default = hdd:\FreeStyle\default.xex [settings] nxemini = true pingpatch = true Do I need a similar structure for Aurora? If so, what settings if any are necessary? FYI, I do not plan on running any games on-line via Aurora. 4) Did Dashlaunch create the launch.ini for FSD based on the options chosen? Do I need to run Dashlaunch and have it create a new launch.ini for Aurora? 5) Is XexMenu 1.1 from 2010 the most current version? Apologies for all the questions. I checked the tutorials but might have missed the setup details. Also, a year ago or so I contributed some money to Team FSD via Paypal can I assume that option is still available for the Aurora team? Thanks, outofwork

I didn't realize that Aurora was a complete replacement for FSD. After all the problems since the drive failed I am definitely leaning that way. Time to dig in for the details on Aurora and how to set it up. Is there a tutorial for those of us who are on the periphery so-to-speak? The video is very cool. Can I assume that Dashlaunch needs to be modified so it boots directly into Aurora instead of FSD? I'm not sure how it actually works so I am guessing as you can probably tell.

The saga continues... after I deleted the database entries the rescan for XEX and XBLA got covers for about 600+ games which it should have. However, what happened is that when I try to run a regular game the covers don't match up with the NAME bar as you move through the covers. When I select the game to run based on the NAME that appears in the rectangular silver bar and not the cover picture it takes forever to load. When I load the same game via the FSD File Manager it loads very quickly. I thought that powering the console off and then back on might resolve the problem but it didn't. I don't see any option to resync the covers and the games.

Once again apologies for being a continuing PITA BUT (pun intended) right after I had run Aurora and gone back into FSD's Fie Manager most of the entries under Drive List have disappeared. The only ones that remain are Game, HDD1 and USB0. Am I becoming paranoid, am I seeing things or did Aurora do something that eliminates access to these other "Drives" via FSD's File Manager? Thanks, outofwork

Interestingly enough FSD's File Manager would not allow me to delete those two files. It said that it failed when I tried to delete them. But, Aurora did allow me to delete those files. Two questions about Aurora... 1) I initially thought that it was primarily a file manager and an application that runs under the auspices of FSD. Is that correct? 2) When I execute Aurora it starts backing up files. Where is it backing those files up to? I just need to fiddle with it a bit to find out everything that it can do. The real appeal to me for Aurora is that it appears to give me the ability to back up all the files and folders on HDD1.

I successfully restored all my XBLA and XEX games. However, even though I set the paths and the scan levels it is only seeing a very few games in each and the covers repeat for a few games over and over. I vaguely recall that if I delete the database files and do a manual scan that everything will come back as normal. But, I want to make sure that I only delete the right files. The two that I believe that I should delete are in the following path - hdd1:\freestyle\data\databases\ and those files are content.db and settings.db. Would someone please confirm that? Thanks, outofwork

Status update - I had a 2 TB external that I had been using for Windows 7 backups among other things. I had to use the 2 TB drive because I am using Windows Backup for one type of backup and Ghost for the second backup and Windows 7 can't handle anything above 2 TBs and Windows 7 was never fixed. The drive was almost full but I moved everything to the 3 TB drive, emptied the 2 TB drive, set it up as FAT32 and VOILA the console sees it right away. So, perhaps my earlier speculation about the protocol handshaking/device recognition was on the right track. There must be something in that handshaking that says "I am 3 TBs" and the console says FAT32 can't address 3 TBs even if the first partition is 2 TBs. There must be a definitive answer somewhere but at least I will be back in business after I restore almost 1.7 TBs to the "new" 2 TB drive. Now I need to buy a couple of new 2 TB drives at a Black Friday sale. Thanks for the help and suggestions.

I am probably going to bite the bullet and buy a new 2 TB external drive. Am I correct in assuming that it must be a USB 2.0 interface and not one that is USB 3/USB 2 compatible? For some reason it appears that the 3 TB drive that I have partitioned to 2 TBs as the first partition will simply not work. I wonder if it because this 3 TB drive is USB3/USB2 compatible and console can't follow the handshaking protocol that might be initially different for a USB3/USB2 drive?

Just for the hell of it I tried to get the MS Dashboard function to format the 3 TB drive that I set up the first partition as 2 TB. I think that it would only set up a 32 GB partition but I just wanted to see if it could write to the drive. It can't. I get back an error message that says an error occurred performing the function or something very similar. What a PITA. For the life of me I can't remember exactly how I set this up a couple of years ago when I initially got the RGH console. I had no trouble and it worked perfectly. I need to start writing things down.

I know that I am grasping for straws here but I wonder if the fact that the 3 TB drive is USB 3.0 is the problem? I know that USB 3.0 is supposed to be completely compatible with USB 2.0.

Yes, I did FAT32 and you wouldn't believe how difficult it was to find something that would actually format a 2 TB drive. Windows 7 will definitely only format 32 GBs, not the entire 2 TBs. I used a program called Macrorit. I wish to hell that I could remember how I set the drive up three years ago.

Update - Interestingly enough when I go to the MS Dashboard it recognizes the external drive only when I plug it in or unplug it. By recognize I mean that a message appears indicating that "Detected Storage Device Change Refreshing Mounted Drives" but the drive does not appear as external storage. It appears to me that there is something on the drive itself that is creating the problem. Either the fact that it is a 3 TB drive, the fact that it is partitioned with a 2 TB partition being the first partition (MBR, Primary partition and Active) and the remaining 1 TB exists as unallocated space or something else. I am determined to figure out what is causing this.