Jump to content
OGXbox.com

HDShadow

Members
 View Profile  See their activity

  • Posts

    935

  • Joined

  • Last visited

  • Days Won

    17

 Content Type 

Everything posted by HDShadow

  1. HDShadow
    ^ Interesting info; could be helpful to others here too.
  2. HDShadow
    Not sure TBH. I've checked my own NTSC 5960, not NTSC-J, MS dash and it appears only to support English, various EU languages, Japanese, Korean and, I think, Chinese (Simple). What is odd is that when I checked the Xbox wiki says the Xbox has, apparently, 'always' supported Chinese (Traditional). You'd think that maybe a regional option variation which, most obviously, would be provided with NTSC-J consoles. But from what you're saying it appears not [b]unless[/b] the wiki is wrong and the option was added with the 5960 version MS dash update. What I'm certain of is that you can't add any language options to the MS dash yourself. You'd have to mod it (softmod or chip/TSOP) to be able to add anything and even then I'm doubtful if adding a Chinese (Traditional) language.xml to the mod dash, if there is one, would affect the game's language support.
  3. HDShadow
    The Xbox restarting when just plugged in is a well known indication of trace rot, usually at the front of the board and often caused by the clock cap or other cap(s) leaking. But it can apparently occur as a result of original manufacturing contamination too ie. lack of cleanliness when handling the MB during assembly. On the error 7 issue: are you sure the chip is being enabled at boot? Error 7 can also be caused anything on the IDE cable so check all the connections. You have another Xbox so try replacing the DVD drive with a known working one from that. It will at least ruled out that being the problem.
  4. HDShadow
    I'd also add that I found a download for the redump version too in under five minutes of searching that is still working. No malware or other issues detected. Not burned it to disc or installed it yet but I can confirm the content matches the original files I have. Only thing to do is also find the English in game text translation patch which is not comprehensive but helps a bit in navigating the all Japanese menus. I've seen links to downloads for that too, one of which I think is the source I originally used. BTW if you don't know about how to deal with redumps: the redump version is about 6GB and will, with the throttled download speed, typically take about 15mins. You will then have to extract the redump ISO from the zipped folder and use a tool like XDVD Mulleter Beta 10.2 or Extract XISO on the ISO to extract the actual game files. I'd suggest the former as you don't have too install it. That game can then either be burned to DVD-R/Imgburn or installed direct to the HDD by FTP. I'd suggest excluding the dashupdater and updater XBEs as they're unnecessary and potentially trouble, particularly for softmods.
  5. HDShadow
    I'd argue that it would be easier to get hold off if you get the remake version for PS4/Windows/Xbox One which can be downloaded, legally, for around $25/£22.
  6. HDShadow
    If you have an eeprom settings tool available maybe, I really don't know. The fact is the Enigmah application is a tool that is quick and simple. Apart from not having a built in exit to dash option there is nothing to criticise. It does the job and takes. literally, seconds to do.
  7. HDShadow
    I think it more likely it is a XBMC4Gamers dashboard setting than a MS dashboard setting. I can't think of any system idle shut down menu option on the original dashboard. XBMC4Xbox has power saving settings and I'd guess that would be the place to look for the culprit. I've just checked and in Settings > System > Hardware there is a Shutdown Idle Timeout option and that has likely been set to a particular time rather than Off. The only time I've seen this sort of thing is with a SCART cable connection where some TVs go to standby if there is no input from the attached device after a specified length of time. I doubt that is relevant here.
  8. HDShadow
    Have you tried launching the games from the UnleashX File Manager? RE: the EvoX eeprom backup issue mentioned - it shouldn't make any difference where the EvoX dash is installed if installed as an app ie. E:\ or F:\ or G:\Apps\Evox\default.xbe. Unless its evox.ini has been messed around with it should give you the option of where the eeprom is saved. Usually this is the default location (which is its own "backup" folder) or E:\ or F:\ or G:\backup. The G:\ location may not be included. The eeprom is not needed for hardmodded consoles but it is always a good idea to have a backup just in case there is a chip issue. But if you can't launch ConfigMagic as an app (which will do the same thing) I'm guessing you won't be able to use EvoX as an app either so this is all rather moot.
  9. HDShadow
    You guys do understand that my post (now redacted) was a 1st April joke but like most of the best jokes of that type had a worrying degree of credibility. I should have thought more about some of the audience not recognizing such intended comic irony but I'd bet, being Canadian, MondayBad did.
  10. HDShadow
    Cold booting is putting the install disc in the Xbox tray and closing it, then turning the console off and restarting it with the disc in place. With the chip working properly and everything else working OK then the install disc should priority boot before most error messages appear. How did you burn HeXEn? It must be on DVD-R which is universally Xbox version DVD drive compatible, ideally burned with ImgBurn at default settings. It doesn't have to be the latter but it is standard practice because it is known to produce Xbox friendly discs reliably. How are you turning on the Xbox? With The Aladdin chip types you need to press and hold the power button for about a second to actually activate the chip. Otherwise it will try to boot the MS dash and that can result in a range of errors if the HDD is unformatted/empty. BTW are you seeing the MS and BIOS logos and 'flubber' sequence on boot or does it go straight to error 07? If I was a betting person I'd still put my money on the adapter being the problem if the disc still won't boot.
  11. HDShadow
    HDD type is irrelevant. The usual problem if something "...didn't work" is the SATA adapter. They are notoriously variable in quality. Before buying another HDD to add more to your expense it would be a good idea to provide details here about exactly what "....didn't work". What error are you getting? What modchip are you using? What install disc are you using? Did you try cold booting that disc? If you tried to install a dashboard by other means: more details on that please.
  12. HDShadow
    Thanks, good work, useful archive. Just had a look at the XBMC ones and I noticed the HD-TV skin appears to be the same link as the previous skin: Containment, same download size too. It looks as though you've accidentally duplicated the Containment download link. Just a suggestion: if the archive expands it is going to be pain downloading each skin separately so some method of packaging up the whole archive or at least each dashboard archive would likely be appreciated.
  13. HDShadow
    It should not be possible but is there any chance you're accidentally inserting the fan plugs (in both cases) the wrong way around so that the GRND and the TACH Signal connections are transposed? Seems highly unlikely but when the Xbox is on if 12v is going to the middle pin and the GRND connection is good then any attached fan should be working. I'd test it with a another 3 pin PC fan to to eliminate any possibility of both the fans tried being faulty.
  14. HDShadow
    Ah, I see we're talking about a custom case - now it makes more sense.
  15. HDShadow
    Whatever you're talking about the one thing I can tell you for sure is that can't do a TSOP flash on a v1.6 Xbox as it doesn't have a TSOP. A WD SATA (HDD?) not fitting the Xbox case? You're going to have to explain (photos?) exactly what you're trying to do because none of this makes any sense to me.
  16. HDShadow
    That is definitely the SID/AID installed UnleashX dash boot splash.jpg found in that E\UDATA\9e115330\0064122817A8\.......... Are you sure disabling or deleting that particular icon in that location actually stops it appearing at boot? The E\UDATA\21585554\0064122817A8\000000000000 location is a weird one because that's the installer dashboard and post-install that particular splash.jpg is not there afterwards in either of the two SID/AID softmods I've checked. Maybe I deleted them to stop them annoying me replacing my preferred alternatives in the UnleashX dash UDATA configuration folder. The 9e115330 location definitely works for boot-time splash screens. They can be added/replaced by anything without any consequence. I'm pretty sure any skin LoadingScreen will take precedence ie. it will run instead of the splash.jpg. The problem I've found is that if you've swapped the skin back to one without a loading screen you can find that the splash.jpg has actually been replaced by the UnleashX default splash.jpg. I don't understand that TBH but it seems in some circumstances that it regenerates an UnleashX dash version splash.jpg rather than the SID/AID installer one. At least that is what sometimes happens on my SID/AID softmods. The default UnleashX logo splash.jpg is a horrible low resolution thing so I replaced it with this on all my softmods and hardmods too:- I also add a splash.png version to that folder so that when the .JPG is replaced, under whatever ever circumstances that happens, I can simply delete the low resolution default splash.jpg, copy that .PNG and replace the extension with .JPG. It is easier than searching through my copious icon file archive for my original .JPG one. The splash screen usually only gets seen when controller resetting or backing out of an app to the main dash.
  17. HDShadow
    You can edit the UnleashX skin.xml to add a loading screen or FMV in .XMV format. In fact it is more correctly called an intro-movie or intro screen. A loading screen will run at both boot and when launching any app which can be a bit annoying. This is a simple example adding both intro-movie and loading screen to the skin.xml:- <Skin name="XXX"> <Information> <Author>XXX</Author> <Copyright>Copyright XXXX</Copyright> <Version></Version> </Information> <IntroMovie ShowInfo="True">XXX.xmv</IntroMovie> <LoadingScreen ShowInfo="True"> <Background>XXX.jpg</Background> </LoadingScreen> If you do not use the <IntroMovie> option ie. you just leave it empty as is the default for most skins <IntroMovie/> the LoadingScreen JPG/PNG will be used at boot instead. If you don't want the ShowInfo text content then, obviously, change "True" to "False". When editing a skin.xml always use a backup copy and a mirror of your main dash installed as an app to test it works OK first.
  18. HDShadow
    Always meant to question that signature . It can could be interpreted as also meaning it might be a better or indeed only option for some people too. Never had a problem caused by a softmod of any consequence and I've been using them since around 2005. Also used chipped and TSOPed ones too. My primary Xbox a chipped one's Xecuter 2.6CE ceased to function about a year ago and whilst I have a replacement chip I've not bothered yet to try to fit it. I've been using one of my other Xboxes, softmodded at least a decade ago with SID/AID, which which I'd set up to mirror the chipped one in just such circumstances. Again without any problems.
  19. HDShadow
    Late to the HDD make discussion but I use Seagate SATA HDDs in Xboxes by preference as I've had issues and annoyances from the WD ones I've used (both PATA and SATA). The SMART values when using the HDD in the Xbox I'd assume are coming from the UnleashX dash info - that's always been suspect. I use Seagate ITB Barracuda SATA HDDs exclusively in my PCs and for backup. Some of the backup ones are originally from primary/secondary PC internal use which means they've been used regularly for at least five years before retiring to less demanding purposes. However if I went by the SMART (CrystalDisInfo) reporting I could still be using them as they're all still free of significant errors. The only time I've had to replace Seagate HDDs is when they've arrived faulty or been sold as new but actually had hundreds of hours PVR use under their belt. Don't like anything bigger than 1TB though, they're the ones I avoid, any brand, because many, including standard consumer Seagates in particular, only support CMR up to 1TB. All the rest are SMR and they're definitely slower for PC use but whether that affects their Xbox use is still up for debate.
  20. HDShadow
    It may be an adapter/TV/screen issue but I suspect this is probably just a failure to switch the console to NTSC properly with Enigmah. The large font issue though is weird because you don't expect that with XBMC4Gamers. It is usually only an issue using the UnleashX dash with 720p/1080i when the skin being used is missing scaling parameters
  21. HDShadow
    ^ That table is the one most commonly cited and, as said, the one by own testing contradicted in some cases but particularly the universal compatibility of the Philips 6035/21. This is my own table based on the eight disc drive types I had at the time. The Tesco DVD-R ones (UK supermarket own brand) are no longer available and I've not found any other UME02 discs anywhere since. The test speed used (usually determined by the media) rarely proved a compatibility factor so the 'burn at low speed' recommendation is questionable. Likewise the burning program only made a difference in the case of the Samsung 605B and Maxell DVD+R. But this was all done with limited testing, typically two discs per test, but that still meant 100+ burns. As you might imagine I was thoroughly bored and significantly poorer by the end of the exercise but I've not had any reason to question the result except, ironically, the Philips 6035/21 ones. That is simply because, at the time, I only had one, ageing example which came in a used Xbox I'd bought which was obviously well used, probably abused and stank of nicotine.
  22. HDShadow
    The tables you can find in various places showing disc media compatibility do not entirely match my experience and my testing. I did that testing over seven years ago and it was certainly not scientifically thorough. I simply didn't have all the various disc drive versions (missing one Philips and the earliest Samsung) and I couldn't afford to test all the different manufacturers for it to be 100% reliable. However what I did find is that the 6035/21 Philips was the least compatible. It did not like CD-R and was inconsistent with CD-RW. Like every other drive it was 100% OK with DVD-R but unlike most of the others it didn't work consistently with DVD+R. I put that down to the age (it has since died) but later when I just happened to buy another Xbox which had the same Philips 6035/21 that too was inconsistent. Neither Philips worked with any of the DVD-RW or RVD+RW disc I tested. So not a thorough testing but that Philips 6035/21 drive was undoubtedly the winner for the least good compatibility.
  23. HDShadow
    I'll keep that idea as a last resort. The thought of reflowing all the solder connections of the Focus chip does not thrill me.
  24. HDShadow
    Settings are different for two of the XBMC app installations I've checked but still the same problem. I will try a stock XBMC version without any user settings. My feeling, as indicated, is that this problem is electrical ie. some component has failed or partially failed which is only affecting the display when using a more demanding dashboard like XBMC. Swapping to NTSC was one of the first things I tried as well as changing the PAL setting from PAL60 480i/60Hz to PAL50 576i/50Hz. When using RGB SCART and 480i/60Hz there is little point in swapping to NTSC which is why this is the only Xbox I have which is permanently used in PAL mode. Made no difference to the problem whatever I used, that's the bottom line. All audio functions on the dashboard like navigational sounds, music playing from CD or installed on the HDD work perfectly no crackling or distortion so the sound is not affected. It is just the dashboard video display. What I haven't done yet is to test it when running a game which is surely more demanding on the components connected with rendering the display. I'll post again when I've done some more testing.
  25. HDShadow
    Hope it is OK to post this link here but it pretty much covers the problem my, currently most used, Xbox has developed out of the blue in the last week too. https://old.reddit.com/r/originalxbox/comments/u35int/problem_with_xbmc_flickering_not_affecting_any/ Any suggestions here as there has not been many new ideas posted to that thread about this problem since it was first reported? As indicated this only seems to affect XBMC whether running as main dash or app, all v3 versions and right back before that to the older XBMC v9.04 circa 2008. Not tried it yet with the suggested v2.0 version. UnleashX and EvoX as apps work without issue. Swapping skins (from Xbox-Classic v3.0 compatibility update) makes no difference either. Not tried it with other cables (currently using proven good RGB SCART) or other TV types.

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.

  I accept