Search the Community

Had a weird experience with my latest mod, an xbox 1.6 chipped with an Aladdin XT. First, the dvd drive has a terrible sticking problem I have been unable to fix so far. So, I swapped out dvd drive with another one from a parts xbox, oddly the new dvd drive will play official discs but seems not to read burned discs despite the modchip??? So, unable to boot Hexen I had to swap back to the original (sticky) drive in order to set up the new hdd. When I attempted to run my tried and true copy of Hexen 2017 the disc still refused to recognize at all for some reason (btw just wtf here, this disc has always worked on every other xbox I've modded - but now no), but a copy of Hexen 2018 did in fact boot right up. I went ahead with Hexen 2018 (although I prefer to use 2017 due to having some issue previously with 2018, I can't remember now just what..) and everything seemed to go okay... until I tried to set up hd video modes. I get this error, 'msdash.xbe does not exist' or something similar. Seems that does not get installed when you use Hexen 2018??? According to some thread this file IS included on Hexen 2017 which makes sense because I never had this issue before. Anyways, after all this I just got impatient and ftp'd a copy of msdash.xbe over from another previously modded xbox 1.6 running the same modchip and... now the machine errors out with hardware error 21 every time I try to run the ms dashboard. I feel like I'm starting to lose my mind, I actually already had a couple of other issues earlier on in this mod but got past them. I saw another suggestion to just download msdash.xbe from the internet but when I googled to download it there were like four different versions or something and I really just don't want to mess around anymore. Can anyone help? Thanks in advance if so...

Hi there, I'm having some strange issues formatting SATA HDDs on a 1,6 Xbox with and Aladding xt +2 modchip. I have upgraded to a 1TB SATA drive with the SATA/IDE adaptor and the 80 wire cable. I just did this on a Xbox 1.0 and it worked just fine, but when I try on the 1.6 Xbox even though I try to write the partition at 927.7 GB it never shows up correctly after the reboot, the F drive is only 120GB and after many tries still cannot access the full amount of memory.. Tried a bunch of times, wondered if something was wrong with the drive (it was used but was working perfectly before I upgraded my computer to an SSD) so I went out and bought a brand new 2TB Seagate drive and I'm still having a ton of weirdness. When I try to make both partitions 927.7GB it still shows very strangely after a reboot. It shows (again) that the F drive is only 120GB but is showing the G drive at like over 1700 GBs. To my knowledge the largest size these partitions (with 64KB clusters) can be is 1024GB and anything over that will not work correctly. I kept messing with it and I can't get the two equal sized partitions no matter what. I have tried loading some games on and it seems to work (games load), and the memory seems to display correctly (minus the size of the game copied) after I copy a game. Should I bother worrying about this? The GBs do after all add up to pretty much 2TB... It just seems so strange because I was really pretty sure you can't have partitions over 1TB.. Also since I had no issues before on the 1.0 version I was thinking it could just be the Xbox somehow...? That seems wrong too though... Any clarification or suggestions would be super appreciated, thanks a bunch.