Jump to content
OGXbox.com

HDShadow

Members
  • Posts

    936
  • Joined

  • Last visited

  • Days Won

    17

Everything posted by HDShadow

  1. Soldering in an LPC pin header apparently "......isn't that hard." but I still made a pig ear of my first attempt at that. You not only need good eyesight (and I bet mine is worse than yours - right eye requires +10 dioptres for reading ) but also the right equipment.
  2. Good luck with the RAM upgrade in particular - I wouldn't even dream of attempting that much as I'd like to have a Xbox with the extra memory.
  3. Well......................in this case it has actually proven either to be the new FATXplorer version update or the new driver. I've literately just finished testing the HDD in question in two out of the three 'problem' enclosures and its now working in both with FATXplorer. I'd been in contact with the Eaton Works support team and very quickly they replied that the update would likely fix the matter. Whether it was the FATXplorer update or the new driver wasn't clear but whatever it was worked. Yay! Not important for other Xbox users but the Windows USB/SATA sector reporting mismatch with the same HDD/housing which prevented me from using that HDD to clone another Windows OS HDD via USB still persists. But it makes me wonder if there might be a software or driver fix for that now too. Who do you approach to prompt looking into something that might just be because of niche USB bridge issue? WDC? They'd probably just say to try using a different USB external enclosure...........................which is exactly what I'm doing.
  4. Extraordinary. I have an older version of the same make of USB external enclosure which I bought more recently because it was being sold off cheaply. Just for a lark I thought I'd try the ITB WD in that. Blow me down - it is now being recognised by FATXplorer, the latest update with the new formatting tools. But I didn't use those, no need the content of the already FATX formatted HDD are suddenly now all available. What I do not know is if it was the enclosure swap or the driver update and reboot FATXplorer prompted before I tried to access the contents. The enclosure only claims support for WinXP and Vista yet it works fine with Win7 64bit >.but I've just checked and the other enclosures only claim support for up to Vista too. That would suggest the driver update was the fix but I'll now have to swap the HDD back to one of the other enclosures to test out that theory. Here's the new FATXplorer log for the very same HDD in the alternative enclosure:- FATXplorer Log 2.txt
  5. I should make it clear: the HDD concerned works fine. Using Chimp it cloned the TSOPed Xbox/HDD I was using as a parent hardmod without serious issue except Chimp's refusal to format it to use F only. That was resolved with XBPartioner v1.3. So all is good with the HDD and I could FTP the contents from the PC if I wanted. But I thought I'd like to try using FATXplorer instead. That's when I ran into this weird problem with FATXplorer recognising the HDD as an attached USB mass storage device but not recognising it as FATX formatted. I'm looking for an explanation for and solution to that.
  6. Strangely enough about 8 hours ago I was actually there reading about the new formatting facility and wondering if it would be a solution to this HDD issue too. Windows has no problems even when it is FATX formatted ie. it still sees the HDD in Device Manager and Storage Management as an attached mass storage device with unallocated space. Formatted to NTFS FATXloprer should pick it up and if it has done the formatting to FATX itself it would be a bit odd if it then didn't recognise it as an attached FATX formated device. My money is on it not working and it indeed being a bit odd. But I'm still going to try that because I hope I'm wrong.
  7. That's the theory, yes, and in practice when attached internally, using SATA of course, it reports and behaves as it should do ie. a 512/4096 (512e). However, when using the particular HDD enclosures I have the HDD, as I understand it, appears to report as native 4096. .png I've asked about this on various IT forums and the only explanation offered is that there is, apparently, a problem with some USB enclosures which use a certain JMicron bridge controller chip version. I'm testing that theory by buying another, different make and type of enclosure, but I'll have to wait for that to be delivered.
  8. I knew that but didn't think about trying it in this case. Thanks for the idea. Primarily I was interested as to finding out why Chimp 261812 wouldn't format it to use all free space for F yet, as said, XBPartitioner v1.3 formatted it correcting in just a few clicks. Last night I had another issue with same HDD - I hadn't used FATXplorer for some time so I decided to see how practical it was to install stuff to it on PC, things like apps, homebrew stuff, skin packs etc which I have archived. Had to install ie. update to the latest version of MS.NET Runtime: v5.0 and get the latest FATXplorer Beta version too. All installed, rebooted to be safe and the HDD in an external USB housing that has worked with both IDE and WD SATA 160GB and 320GB respectively. No joy - Windows shows it as an attached mass storage device and FATXplorer detect it too but not as a FATX formatted HDD. FATXplorer Report.txt Tried downloading the new driver, rebooting etc but it still is not being recognised. I opened a ticket on the FATXplorer web site to see if they could offer some insight and/or solution other than the obvious ie. use a different HDD or different USB housing. It is likely something to do with the fact the 1TB WD HDD is "AF" (Advanced Format) and there are reported issues with these newer AF HDD's firmware and some USB enclosures. I was going to use this same HDD to clone an existing internal PC HDD which includes a full Wndows OS but the cloning software refused to proceed because of the mismatched "Sector" sizing. No problem if you connect it by SATA internally but that's a bit of a faff. It was one of the reasons I decided to use it as a Xbox HDD and yet it seems the issue with FATXplorer not recognising the FATX formatting may be related.
  9. Not sure whether this is a Chimp 261812, HDD, BIOS or other matter. I've not used a 1TB HDD with a Xbox before, largest size I've used is 500GB and I've had no problems with Chimp 261812 formatting the extended partition(s). Well today I decided to build a new Xbox HDD using a recently purchased ITB WD AF SATA HDD for use in a chipped Xbox by using a TSOPed Xbox and Chimp 261812 (v1.0). I've done similar things in the past when I couldn't use an installer disc because the Xbox did not have a working DVD drive. All went well and worked perfectly except the formatting of the extended partitions. I elected to have all available space for F but after I'd cloned the existing 80GB IDE 2.5" HDD, BTW just C and E, I was asked again how I wanted to partition the available free space. I checked the Slave ITB HDD's status and the partition table showed the remaining space equally split between F and G about 450GB each. WTF? So I redid it, choosing all F again, but still with the same result. The custom EvoxM8+ BIOS I used for the TSOP is set up for all free space to be used by partition 6 (F) and not to ignore the partition table. So I exited Chimp and used Rocky5's XBPTableWriter to reaffirm all free space goes to F. Went back to Chimp, this time with the 1TB as Master HDD on the TSOPed machine and checked. It was still showing equal split F and G so again I tried reformatting to use all F but still no joy. Long story but I eventually gave up on Chimp and went to XBPartitioner v1.3 and very quickly had the thing formatted to use all the space to F with the correct cluster size (64K) for the 950+GB F partition. So any ideas why Chimp might have been unable to do that?
  10. FYI the v1.6 480p loader patch used for Gun Valkyrie is the same as Panzer Dragoon Orta. Both Sega games. It is actually just the PD1 launcher that PDO includes as an in game unlockable. It was found that in both cases if you launch that PD1 actually runs in 480p, if your set up supports and it is enabled of course. The 'trick' is it maintains that resolution if you then exit back to the primary game. Rocky5 incorporated that discovery into his XBMC v1.6 480p launcher script for those two games but AFAIK it doesn't work for any other Sega game that has the same problem.
  11. Yes, the manually set date from my current or previous session if that hasn't gone. This is relevant to this matter as that relatively quick check I mentioned I did to confirm how long the time/date had been retained boosted the retention another 12 hours. When I turned the Xbox on at about 11.30pm I was surprised to find I dd not need to adjust the time/date, it was still showing the correct time. 11.30pm 16th June 2021. Not sure about the relevance of that comment on game saves not going away. I think you must have misunderstood why I mentioned it. I'd used the last game save I'd made to determine when I'd finished playing the previous session that's all. I usually save and backup save at the end of a session. Using the MS dash game save manager it displays the time and date of the save. Knowing that I could work out accurately how long the time/date had been retained by that Xbox.
  12. That suggested 3 - 5 hours date/time retention for a new clock cap is a significant underestimate. It may vary with the cap type but even my not replaced yet original clock cap in a 2005 chipped v1.6 still retains it for longer. But it does seem to depend on how long your previous session lasted. BTW the Xbox concerned is not connected to the internet at any point either. Last night I was using it for a couple of hours (playing Mercenaries) and I turned off/unplugged the Xbox as I always do afterwards. I've just checked and the last save I made was at 1.32am and it is now 12.45pm here. So I think it is fair to say it is still retaining the settings for at least 12 hours. Originally, with similar session lengths, I've found that and other Xboxes maintain the info in the same circumstances for 24+hrs. The clock cap may also be irrelevant to the time/date retention if you used SID to softmod the Xbox. Because of an oversight it will not retain any time/date after, I think, June 2019. It reverts to an earlier one at any reboot. I think it is the date of the SID installer itself but I might be wrong about that. Although this has apparently been fixed in the most recent version of SID the most common version you find online is still SID v5.11/12 which does have the problem. The final version of AID installs v5.11 SID too. Rocky5's XBSMT doesn't have the same trouble but I'm not sure about HeXEn installed softmods.
  13. I'm guessing it'll be a custom UX Config.xml thing maybe using "PC Games" instead of HomeBrew as a lot of those are PC ports to the Xbox. There's some really good ones amongst a wider selection of games that either do not play that well or remind you how lucky we are as gamers not being back in the 1980s. In the same way that menu option could also be a direct launcher of the ScummVM 'emulator' which supports a limited number of old school point and click PC adventure games which do run reasonably on the Xbox eg. Broken Sword. It'll be interesting to know more. However no way will PC LoK: Soul Reaver run on the Xbox. Even using the Playstation PCSXbox emulator I think you'll be lucky to get anything approaching playable performance.
  14. I have a feeling filevans may indeed be a new account by that old 'friend' of this forum and other Xbox forums he has also disrupted in the last few months. However he is correct about the Xbox supporting PAL 576i/50Hz over Component but, as I said, that does also depend on the TV. Some older TV's only supported prog scan over Component and others may only support 480i. No idea about more recent TVs but my JVC HV-32P37SUE 32" CRT WS supports 480i. 576i, 480p, 576p and 1080i although not 720p via Component. If he was serious he would have addressed my suggestion that he just use a the RGB SCART cable he already has. If he wants to use 50Hz then forget about what the Component cable is or is not doing and use that RGB SCART cable instead. Set the UnleashX or XBMC or MS dash to PAL50 and that's the problem solved. What those other consoles he mentions have anything to with...................................anything, who knows?
  15. It may depend on the TV. 480p is 480p/60Hz. If it was a NTSC or NTSC set Xbox and you'd switched off the progressive scan options it might default to 480i/60Hz when using Component. If using PAL with Component, which is I think what you're doing, and you're seeing a noticeable difference between the boot screen resolution and the main dash/games resolution are you sure the console is actually region set to PAL? The Xbox itself does not support any PAL progressive scan resolution ie. 576p/50Hz. So we're talking about a change in resolution from 576i/50Hz to 480i/60Hz. Are you seeing that with your eyes as a significant difference or is it just your TV telling you the resolution has changed. The primary question really should be: why on earth do you want to to use 50Hz and, if you're desperate to use 50Hz for some niche reason, why don't you just use a RGB SCART cable? That gives the best interlaced resolution picture quality. Component, if it supports interlaced resolutions, is in practice just as good although it will require picture setting adjustments to match a RGB SCART display as that tends to exaggerate colours and contrast. 480p/60Hz picture quality is noticeably better than 576i/50Hz and, of course, 480i/60Hz. You should go to the MS dash and check your video settings there. The UnleashX dash resolution options do not always stick, apparently. I've never had that problem but you do need to save and reboot after changing them. However that also leads on to another important question: are you using a softmod and if so what? It could well be involved if it is a modern one where the resolution settings are protected.
  16. Great solution worth remembering - who would have even thought to try that? But why does it work and what triggers the problem in the first place? That reminds me of a 'trick' you could do with PAL PS2 Gran Turismo 3 or possibly 4. If you stuck at the game you could 'complete' it 100% but if you swapped the language to German you'd find the UK Vauxhaull Motors vehicles all became Opel (the German parent company). If you used those you could complete the game to 101%+ and it would actually show that in the player stats progress.
  17. I've just tried my original Forza Motorsport PAL disc on a PAL region changed to NTSC v1.6 with Xecuter 2.6CE with the unknown Evox M8+ 1.6 BIOS that was pre-installed before purchase. Both banks appear to use the same BIOS but one with logos removed. UnleashX main dash (v572) no problems from disc at all. Plays in 480p no problem either. It does work the disc hard though so it is a game I'd suggest is always played as HDD installed. Currently doing that now with DVD2Xbox so I can test it from the HDD too. Removed the three updater XBEs included first. Thoughts: when you deleted the original Forza saves did you check the TDATA folder (4d53006e both PAL and NTSC) had been removed too? I noticed that is where the Leaderboards are saved and probably other stuff too like any DLC* there might be for it. The game also used X or Y or Z for a lot of stuff as well (300MB+). EDIT Just tried the HDD install and it worked perfectly as installed and after removing the three updater XBEs included too. Also works after installing the DLC 440 block Update and 480p/WS displays as it should and no specfic ACL patching apparently required either. Launches from UnleashX (v572 and v584), EvoX (B3935) and XBMC v3.5.3. I have at least one other v1.6, softmodded, so I'll test it on that later if this matter is not resolved in the meantime. * there is a Forza update but no other official DLC. Plenty of user game save DLC though. The official update is installed in E:\TDATA\4d53006e\Su and it looks like a replacement default.xbe and a downloader.xbe. I've removed the latter then tested again and everything still works as it is supposed to. BTW if you're want a good Preview FMV the game itself includes videos in its Forza Motorsport\media\FrontEnd folder. They're always far better than the ropy gameplay recordings Prevew packs often include. You'll find they are in the, oft used with Xbox video content, .bik format (Bink Video) which are usually easily converted to XMV for any UnleashX skin use which has Previews enabled. Usually the "Attract" videos are the ones to go for but in this case they're just the MS Studios branding FMV. However the "Intro" video there is ideal.
  18. Rocky5's ConfigMagic v1.6.1 mostly GUI update might have prevented this as it is made difficult to exit ConfigMagic with an unlocked HDD and warns you not to do it if you're using a softmod. Use of his v1.6.1 update is recommended for this reason. This case is also another good example of why once you've softmodded your original 8GB - 10GB you should immediately install another, bigger HDD and keep that original one, locked of course, as backup for just such situations. I've never had cause to use it in such circumstances but if ConfigMagic has been used a master password "TEAMASSEMBLY" may have been enabled. Not sure if it can be used to relock a Xbox HDD though; others here may know about that. Also ConfigMagic may have written the eeprom.bin to the root of the E:\ at some point during the process. As the HDD is unlocked you could use a USB housing and FATXplorer to check whether that has happened. If it was softmodded using SID/AID the eeprom might (it should be standard user practice) have been written to E:\Backup or the softmod's own E:\UDATA folder. With the eeprom and XBHDM you should be able to relock the HDD. As I've been more into chipping and TSOPs recently I've not done it for some time but with softmods, as I was strongly advised to do as a Xbox modding noob by people like Heimdall (HeXEn) on the Xbox-Scene forum, I routinely backed up the eeprom (EvoX) as part of the pre-softmod process. But later I also unlocked and relocked all my softmod HDDs with ConfigMagic to enable that master password option, just in case.
  19. ........................................or that. ^
  20. If its like vanilla XBM4Xbox the navigational sounds will be under Settings > Appearance > Skin > Navigational sounds. One of the options is to turn off those sounds so I guess you might have accidentally enabled that somehow. Incidentally the full range of XBMC navigational sounds options is, I think, 24 (including off). Some older sources for these may not work with XBMC4Xbox v3.5.3 and its variants which also use that version. This is because the files in the XBMC "sounds" folder include a "sounds.xml" some of which use a slightly different XML syntax (older) apparently not compatible with the later XBMC versions. Luckily you can sub in one of the basic, newer sound.xml files and with a little editing get them working again.
  21. The pic of the lead looks like it is a fairly typical type of third part Xbox Component cable: just green/blue/red + L/R Audio (white/red) phono plugs. There are obviously no Composite or S-Video options. I have a PS2 Component lead which looks very similar. Can you post a pic of the TV's phono sockets being used with and without the cables in place and precise details of the TV make and model you are using?
  22. Are you 100% sure the green/blue/red phono plugs are plugged into the correct sockets or the sockets concerned aren't dual purpose? The only way you can get B/W with Component is when just the green lead is plugged in, so it suggests either the wrong sockets are being used or the blue and red leads or sockets are not working for some reason. Does the lead you're using have an HD/AV switch because that might explain it too ie. AV = Composite, HD = Component?
  23. Depends on the HeXEn version too. It uses a modified UnleashX dash and pre-v584 that wouldn't recognise v1.6 Xboxes so if it is using using an older version it would do the same. I have older UnleashX dashboard versions which don't recognise even a v1.4 correctly because of their age. I'd imagine the latest versions of HeXEn ie. from HeXEn 20I7 > would use a UX v584 'engine' so should be OK but the only definitive way of identifying a Xbox is. as SS-Dave just said, to open it up and check. AFAIK no Xbox version reporting tool can differentiate between a v1.2 and a v1.3. The semi-mythical v1.5 can't be identified for similar reasons.
  24. Was the 2TB HDD properly partitioned and formatted?

Board Life Status


Board startup date: April 23, 2017 12:45:48
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.