Leaderboard

From what I've read, I can't help but believe that supporting other BIOSes on a microSD card is nothing more than a gimmick at the moment. There hasn't been much effort in supporting anything else previously with MakeMHz... And if it does go ahead, I can't imagine it'll be a priority at all or that any competitive/preferable modern BIOSes or patches will even be supported anyway. I've been interested in the native ATA TRIM support for SSDs as well, but it's not something that I've really seen discussed since its announcement... Sure, it's not actually all that big of a deal, but I'm keen to see it play out if it's actually a thing. All of the kernel-level patching on-the-fly is the most attractive thing about it all to me at the moment, and also the integrated modern controller support that I haven't seen or heard anything about yet either... There's a lot of promises and undelivered features, but also a lot of drama and refusals to support desired features that are provided elsewhere. I think I'll be on the fence about Project Stellar for a while, patiently seeing how it all plays out and what it has to offer in the long-run... I think that a bit of competition for an internal HDMI output mod (not analogue-digital external converters) could be a good thing for the project overall - I recently saw some mention of PixelFX developing one? In the meantime, an OpenXenium with freedom for my own choice of BIOSes/patches will be good enough for me, at least until something "Stellar" finally happens with this...

That's............................odd. I have no explanation for why connecting a network cable would resolve this problem. I've read about an internet connection causing boot problems but not the reverse. I'd be interested to know if anybody here has an explanation for that. I'd suggest you post some pics of your current C:\ and E drive content before doing anything. If the thing is booting properly then we need to work out and understand why it needs the network connection to boot. Everything could be set up correctly already and the problem is something else. I see SS_Dave has just replied; his suggestion that the particular HeXEn M8+ BIOS used might be connected to the problem sounds very plausible. But I'm not clear as to why connecting a network cable would 'fix' that. As I suggested earlier checking the Evox M8+ BIOS you installed using the EVTool on PC just to make sure what path(s) it is set up to use and anything else relevant that could confirm it is a BIOS issue. I'd be reluctant to advise this but it might be that the best course of action is to reflash the TSOP with a known good Evox M8+. That carries risks of course.

noDVD BIOS does not mean the Xbox will not still load a DVD if the drive is connected. It just means a DVD drive does not have to be connected to the IDE bus. It skips the requirement that a DVD drive must be connected. Go ahead.