HDShadow

Thanks for that. It was with Win7 64bit that, I thought, I was having trouble. But as said Eaton-Works pointed me at the correct download I should have used and the latest FATXplorer Beta version is now working as it should.

Can you run me through how you did that? It is annoying that at some point any existing working version can be suddenly disabled and for no good reason I can think. At some point Win7 support will probably removed so I'd like to understand how you can continue to use a particular working FATXplorer/.NET combo on a Win7 PC, which is pretty much dedicated to all my Xbox stuff, despite the expiry date.

Re FATXplorer Beta 3: there's been a new update recently and you must have MS Windows .NET 6 Desktop Runtime 6.0.1 64bit or 32bit installed or it won't launch. I had not used FATXplorer recently and I had trouble getting the update to work on a Win7 64bit PC despite having .NET 5 Desktop Runtime installed which is supposedly supported until May 2022. I could not launch either that or my existing FATXplorer (the beta had expired) version to update it so I downloaded what I thought was the correct .NET 6 version and it still did not work. Eventually I messaged Eaton-Works (kudos for their very quick response) and I found I had been installing the wrong Runtime download. Doh! It must be that exact one above - the download link provided goes to a MS page with multiple downloads. It is the Windows .NET 6 [b]Desktop{/b] Runtime 6.0.1 that is needed:- 24.01.22: 58.4MB File version 6.0.1.30718 MD5: b3b8e251456c6e712940ae507252facb SHA1:1dc44c31438725846f59071c868736112398329b.

There should have been no trouble with a 160GB. Typically the F:\ drive with a HDD of that size will be around 140GiB so the default 16K partitioning should be correct. I'd still do what KE recommended and check what XBPartitioner v1.3 reports about the extended partitions. I've had a few problems with Chimp's extended partitioning on some HDDs in the past and always make it part of my HDD upgrade routine to check them with XBPartitioner v1.3 afterwards just to be sure. Are the Xboxes in question hard or softmodded? If hard modded (TSOP/chip) then I'd guess at a BIOS issue so the obvious question is what BIOS are you using in all cases?

It could be that the game is one of the region locked NTSC ones. There are more well known PAL ones, like Timesplitters 2, but I would think that if it is this problem just switching your consoles region to NTSC using the Enigmah app will fix the problem. But the description of the problem sounds more like a disc error of some sort - usually with an out of region game you'd get a warning that was the case or dirty disc error or the sound would play but the screen would be blank. The only time I've seen anything like that error is where somebody has used DVD2Xbox to rip the original disc as an ISO or when this is from the Xbox dump archive and tries to use the dump ISO instead of extracting the contents with DVDXMulleter or Extract-XISO. So...........................I have to ask: is the game an authentic original MS NTSC retail disc or a burned copy?

Sounds as if it could just be that a cold boot of the installer disc is necessary. Any properly working chip with any BIOS, old or not, must be able to do that. Either disc mentioned should boot and offer you formatting and then dash install options. If they're booting with the old HDD in place; that means there is nothing wrong with the DVD drive, disc or burn. If cold booting does not work then check the jumper on the new HDD: if it is on Cable Select swap it to Master or visa versa. In the far, far distant past that was an oft made suggestion for otherwise inexplicable boot issues whether involving discs or the HDD itself. Other possible causes would be the IDE cable but I assume you're using the same one with both old and new HDD so that's an unlikely culprit which leaves the 'new' 500GB HDD itself as the primary suspect. You do have the option of using Chimp 261812 as well; it is a less usual thing to do with a chip fitted Xbox but try cloning the old HDD to the new one (just C and E) and see if that works. If it doesn't then the new HDD becomes even more suspect. BTW make sure that if you get it working you format the extended partitions (F and G if used) correctly afterwards using XBPartitioner v1.3.

Does that docking station shown in your previous post come with its own cloning tools? If not what do you use?

I've about 60 Xbox PAL games installed on my primary Xbox and apart from Timesplitters 2 they all support NTSC/480p etc. I subbed in an 'acquired' NTSC "default.xbe" for use with PAL TS2 and that works fine in 480p. I am still peeved that PAL Xbox users have to resort to modding and patching simply because MS effectively decided to or at least tried to prevent us accessing the ED/HD options most PAL games do actually include and the console was perfectly capable of displaying.

You usually need to cold boot the burned installer disc, particularly if there is an error present like 16. Just put the disc in the tray, close it, shut down the Xbox and then restart. The disc should boot before the error 16 message kicks in.

Sounds like it is/was what KaosEngineer suggested. X, Y and Z are regularly 'temporarily' written too by a lot of games, sometimes pretty big lumps of data which will persist until written over by another game. If that doesn't happen or there's corruption or a conflict ie. two games using the same file name it can cause trouble. I might be imagining this, later consoles did have such a facility, but I believe that even in stock retail state this could happen with the original Xbox and there was a controller key sequence you could use to clear the cache and those temporary files to resolve such problems.

Whatever way suits you. I've backed up my primary Xbox to PC for years, once a year, just using FTP. I exclude the installed Xbox games (currently 62) as that is close to 200GB which would double the time to back it up this way. That is already many, many hours. Maybe FATXplorer would be quicker but unless the Xbox HDD is easily accessible the thought of the hassle of connecting it to a PC by other means when it can already be quickly connected for FTP doesn't inspire me to try.

With problems like this and a 320GB HDD I'm reminded of a mistake I made when going from a 160GB to a 320GB HHD. I was so pleased to have more space I simply forgot I needed to reformat F:\, as it was over 256GiB, to use 32KB clusters rather than the default 16KB the 160GB was using. Any chance this is the the issue here? Use XBPartitioner v1.3 to check if there is a ER (Error) indicator against Extended Drive 6 (F). If there is then that is probably the trouble and unfortunately all that work backing up 70+ games to the new HDD will have to be redone. Hope its not this but it is an obvious thing you should check.

I agree no need to use run as admin to get Xplorer360 to work. The 'trick' I've found with Xplorer360 is that using menu copying/move is, or can be, problematic. By far the most reliable way of getting files from PC to flash drive when using that program is the good old fashioned drag and drop method. The renaming folders problem also mentioned I'm not sure I fully understand the OP's method ie. exactly what he was doing but what I've found with Xplorer360 is that whilst you can create a "New Folder" using it on the flash drive it will not let you rename it. You have to do that on PC then drag and drop it into Xplorer360. Much of this hassle can now be avoided, as others have said, by using the far better FATXplorer instead.

It sounds like another one of those problems with a hardmod, the particular BIOS flashed as SS_Dave said, but there is also a softmod installation still present. That might explain the difference in behaviour ie. HeXEn's Admin Tools: doesn't that mean the UnleashX dash was launched using the File Manager? If that dash was on E:\ and it was a previously softmodded machine then that is very likely the explanation.

I think a screenshot of the file content you're trying to FTP would help confirm whether its more likely a FTP or other related matter rather than what it is you're trying to FTP. FTPing to the Xbox can be erratic, at least its always been like that for me. You can get multiple FileZilla "Failed to Transfer" errors to begin with and disconnects, particularly with an UnleashX main dash. Then suddenly it'll all go sweetly and you can transfer GBs of stuff in just a few minutes. With the failed to transfers files when using FileZilla just re-queue them afterwards and you'll often find they'll all transfer first or second time unless there is some problem, like lack of space as KaosEngineer suggested.

It is not necessarily that, it depends on the download. If it is from a 'Redump Archive' then yes but many Xbox games if not already "HDD Ready" ie. FTP ready game files, come as ISO or, most often, XISO downloads. Once unpacked from the Zip or RAR folder the latter can be burned directly to disk (DVD-R/ImgBurn) or have the files extract using the C Xbox Tool or Qwix so they can be FTPed. XISOs themselves installed to the HDD can be played on the Xbox too if your softmod has the tool available which supports this.

You are definitely using a HDD ready copy of the game, yes? If so, very perplexing why you have the problem.

Please do because I'm out of ideas too. All I can confirm is that the HDD Ready versions (both) that you can find at the same archive work fine if you FTP it to the Xbox rather than use a disc based installation via DVD2Xbox. There's so much odd behaviour I've had with this game from disc - I've now managed to install the XISO disc created from the Redump files via DVD2Xbox using the same DVD-RW XISO disc that didn't work last Friday. As said the DVD-R disc I made from the same XISO refused to boot on any of the three Xboxes I tested. Likewise those made from the HDD Ready files. Even the Black test burn I did refuses to boot properly now on any of those three Xboxes. I'm thinking the confusing results are due to a bad Maxell DVD-R disc batch issue. I was hoping they were different manufacturers but no they're the same as other Maxwell discs I've burned that work without any problems: CMC MAG AM3. Both burners would have to have been malfunctioning for it to be anything to do with that, highly unlikely as both have only had light use anyway. In short I have no idea what the problem(s) have been with this game and in such circumstances all you can advise is to use the install method that you know does work: FTP.

There's something weird with the Def Jam FFNY files - as said both the HDD Ready ones work from DVD-RW discs on my primary Xbox (chipped) but DVD2Xbox just won't install them from the same discs. FTPing in a HDD Ready version and it works fine. But I've just been testing DVD-R discs (XISOs created from those same HDD Ready files) with two softmods and the same chipped machine. None of them worked! I was suspicious of the DVD-R batch I was using (Maxell); the first disc gave a verification error with ImgBurn. Only time I've had that is with a bad batch. But I tested two other disc from the batch with a XISO of Xbox game: Black (small size so ideal for a quick burn) and they booted fine on all three Xboxes I'm testing. The bad disc must have been a rogue. I've also proved to my own satisfaction its not the burners (two different lightly used ones tested) or ImgBurn. Wasted five or six discs doing this but all the Def Jam FFNY DVD-Rs using the same XISO that works using DVD-RW on my chipped Xbox's Hitachi disc drive do much the same thing on all three machines (the two softmods use Samsung B and Philips). They take an unusually long time to be recognised and that sometimes fails. But when they are and can be launched (both XBMC and UX dashes tested) they immediately stick at the Def Jam FFNY loading screen and eventually give a dirty disc error. I've never had any DVD-R burn fail to boot except when there was a disc media fault. I just can't explain why DVD-RW burns work from disc on my Hitachi disc drive but you can't install them using DVD2Xbox. It just doesn't make any sense. With that and the other testing evidence I'd say don't try to install or play this game from burned disc. FTP it in only. I'd also suggest that if Shxlx006 use DVD2Xbox at any point he uses a file manager and finds the DVD2Xbox UDATA/TDATA save entries there and deletes them. Delete E:\CACHE too and any temporary game content on X, Y and Z. I'd also remove any Def Jam FFNY game install that has been made and start again cleanly by FTPing in a HDD Ready version. DVD2Xbox UDATA/TDATA ID is 0facfac0 but check that just to be sure they are the correct folders. The TDATA one should contain metai.d2x and a settings.d2x files. If you're not using the default skin doing this will revert it to default but otherwise there's no problem. Both DVD2Xbox's default UDATA and TDATA folders will regenerate on next boot.

Shots of your C:\ and E:\ drive content would help on that but if it is chipped (very unlikely a TSOP) then the only 100% way to be certain is to open up the Xbox and check inside. You'll need a torx head screwdriver for that. But check this first: if when you look underneath the screws have obviously been removed (labels torn, replaced, covered by another sticker or peeled away) then somebody has definitely been there before you. But if the labels are original and still virgin then you can be pretty sure it is a softmod so no real need to go any further. If the C:\ and E:\ drive content match a recognised softmod set up it is probably safe to assume it is a softmod.

Only use XDVDMulleter or XISO if it is the redump version. The HDD Ready ones are, as they sound, HDD ready - all you do with them is unZip or unRAR and FTP the game Def Jam folder to your Games folder on the Xbox. If there is something messing with the boot of your Xbox as well it might be the same sort of DVD2Xbox problem I described. Did you use DVD2Xbox at any point in the past to try and install the game from disc, particularly if it was the redump version from the archive? Can you confirm, as it is still not clear, whether you're using a chipped Xbox or a softmod? I ask because my primary softmodded Xbox is also a v1.1 with the same retail BIOS as shown in your earlier screenshots. It has a Samsung 605B disc drive which doesn't like the DVD-RW I used earlier with my chipped Xbox. I'll have to use a DVD-R or two to test the redump and one of the HDD Ready versions. If yours is a chipped Xbox there's not much point as, as KaosE said, the BIOS or chip itself might be involved with the problem.

Shxlx006 The ACL patching, as far as I tested, only applies to the redump version extracted files which, of course, are not ACL patched. The HDD Ready version I FTPed in worked fine without patching, as you'd expect it was already ACL patched. I did not try installing the the game from disc with DVD2Xbox using the XISO I'd prepared from the HDD Ready version files. I was more concerned about getting my Xbox DVD drive working properly again and wasn't going to feed it another disc as none were working at that point. I should have mentioned the BIOS I'm using with the Xecutor 2.6CE chip fitted in that v1.6 is a Evox M8+ customised v1.6 version. The fact is the unpatched redump version game installed via FTP on launch crashed back to the main dash, just as Shxlx006 describes, it was reasonable to assume his problem was the same thing and that ACL patching or using the pre-patched HDD Ready version would fix the problem. I see we're now back to that "default.xbe" issue - Shxix006 really needs to confirm it is the original default.xbe that was extracted from the redump ISO. If it is not and comes from somewhere else then that IS likely the problem. The redump ISO and both the HDD Ready versions I found at the Xbox archive have their "default.xbe" as you would expect. All you need to do is FTP the unZipped/unRAREd HDD Ready game folder to your XBMC Games folder. When done in Programs > Games (it may depend on the XBMC skin exactly where that is found) you should see the game displaying as "DJFFNY" only if it is the redump version. If it is shown as "Def Jam Fight for NY" it definitely is either of the HDD Ready ones. It should boot without issue if it is the latter. Is there any chance a anti-virus or anti-malware program is interfering in this? I've not had problems with XBE files myself but there are several Xbox PC tools that provoke my AV and would delete/quarantine them if I hadn't years ago added them to the exclusion list. It would also help to confirm, since we are pretty sure the redump version is what we're talking about, what tool was used to extract the game files from that downloaded redump ISO: XDVDMulleter or XISO just be certain?

I'm at this moment testing the HDD Ready version installed by FTP and its working fine. I've rebooted several times, played it a bit and there's been no problems. After clearing the HDD Ready install, CACHE and game save(s) (UDATA/TDATA) I'm just about to try the redump extracted files version FTPed in.............................................aha! On launch it's just booted back to my main dash. I'm going to ACL patch it with DVD2Xbox and hope it doesn't **** up my Xbox again.................................it didn't. Yay! So that looks like the problem although I can not explain why DVD2Xbox balked at copying in the files from the redump version disc when that played perfectly from the disc to start with. What you need to to is ACL (Action Control List) patch your existing DJFFNY installation:- 1). Install DVD2Xbox with the full ACL list. The DJFFNY game save ID is 45410049 and I've just checked my copy of the ACL list and there is no specific ACL for that game for it appears just to require the default ACL patch which any version of DVD2Xbox will include. 2). Launch DVD2Xbox and select the File Manger option from the menu (not the Game Save Manager). 3). Use that to find your DJFFNY folder in Games or wherever you installed it. 4). Just highlight the folder, don't open it, and press the controller WHITE button to get a context menu. 5). Choose the Process ACL option and click to run it. 6). As it is the generic ACL patch it will do that very fast, other games ACL patching can take much longer. You can check it has worked by using the file manager to view the DJFFNY contents afterwards. You should now see a "default.xbe" which is the new patched one plus a "default.xbe_orig", a backup of the original default.xbe. 7). Exit DVD2Xbox back to your main dash. 8). I suggest shutting down then rebooting before trying to boot DJFFNY again. Hopefully that will fix it for you too. I'd still suggest you find the HDD Ready version - that should have been ACL patched already and the fact the copies I found booted OK and the redump version didn't after install to the HDD is a good indication it was just a ACL patch issue all along. It doesn't explain the problem I encountered installing it with DVD2Xbox from disc. Anyone else here have an explanation for that? FYI this was all done on a Xecuter chipped v1.6 at 480p and tested being launched from UnleashX v572, v584 and XBMC v3.5.3. If it still doesn't work I'll try it on a softmod too. What version Xbox are you using?

There are several HDD ready archive collections there and I downloaded the two I found to test them along with the redump version. All unpacked perfectly. BTW if you use 7Zip (any context menu Extract option) you get an error '.....payload....' message when both the HDD ready .7z files are being unpacked. You can ignore that; it is known problem with 7Zip . Assuming you have 7Zip installed: to avoid the message rather than use the context menu (you can use the "Open archive" options but that just launches the main 7Zip GUI) you might as well double right click and launch the 7Zip GUI directly. Using its 'Extract' option, magically, the error message will not appear. As to the tests: I used XDVDMulleter to extract the game files from the redump ISO and then converted all three game downloads to XISO with the C Xbox tool. Burned them one at a time to three discs (DVD-RW which my v1.6's Hitachi DVD drive likes) - no problems. On the Xbox itself all three played from disc without any trouble - I created a profile and avatar in the game in each case went through the first 'training' level fight. This is where it gets interesting in regard to the problems described: I then took the redump version XISO disc, which abbreviates the XBE name to "DJFFNY" so must be the one you're using and went to install it using DVD2Xbox. I've never had a problem with any game disc which plays from the disc when I've tried just to install it, not play it, on the same Xbox using DVD2Xbox. But this time there was a big problem. When I clicked to begin the install I immediately had an error message that said 5 files had failed to transfer. I ejected the disc and closed the drawer again, the game was recognised and this time it started to install but after 10 seconds it stopped and reported 63 files had failed to copy error message. I ejected the redump version disc and replaced it with one the other discs. This time DVD2Xbox refused to recognise a disc was present, same thing with the other disc. Remember that only a few minutes earlier I'd been playing the game from each of those discs. Worse was to come I tried my standby test DVD-R disc (Timesplitters FP) that was not recognised and neither was any original disc. I closed DVD2Xbox and tried just booting the DJFFNY disc, then the other two and other games' discs as well - same thing. The DVD drive whirred a bit but refused to recognise any disc at all. Disaster, those Def Jam discs had worked the DVD drive hard and I thought they might have finally broken my previously bullet proof Hitachi drive. TBH I'm not sure which of the things I did fixed the problem but I suspect it was a DVD2Xbox issue. I've had it affect general Xbox function in the past when I simply swapped skins. The last thing I did before getting the DVD drive working again was to delete the DVD2Xbox game save, checking that both the TDATA and UDATA files were not there any more. That's what fixed the skin issue and I'm confident-ish it worked this time too. The question is: is it just the redump version that causes this problem when installing to the HDD? Answer: I do not know because TBH I didn't and don't want to risk messing up my DVD drive again. Later today I will try to FTP to the same Xbox both the redump version and at least one of the HDD ready ones. I'm suspicious of that redump version but have no explanation as to why it should work perfectly from a burned disc but refuse to be installed from that same disc. So again I'd suggest getting the HDD ready version but I would not be that surprised if that turned out to have issues too.

That's the Redump version. Have you tried the HDD ready version? I've just checked and Its archived at the same place as well, in fact there are apparently at least two different archives there which have it. Just Google "Xbox HDD ready" and you'll find the game easily. Screenshots of your game's install location etc might still be useful. XBMC has a built in Screenshot option - just click down on the Left stick (L3) and it will be saved as a BMP in your designated Screenshot folder. The latter may have to be created yourself if you don't have one already - F:\Screenshots seems like and obvious location suggestion. If you're posting it here converting the big BMP file, about 1MB for a file manager grab, is probably best converted to a smaller JPG or PNG using your graphics program of choice first. Paint.net recommended.