Ernegien

Ask around, I think you'll find I help all sorts of people out in the scene, both publicly and privately; it might surprise you. I'm not interested in this stuff unless you're paying me $250+/hr though

Nemesis hasn't created any software of his own; that's the difference. Still waiting on answers to my questions regarding "his" HDMI design's QSB technical details.

You don't need my permission to release your hardware schematics which are useless without software you've yet to create I'm still waiting on my HDMI board questions to be answered in some sort of technical nature regarding the QSB.

I thought I did? but it's become a whole lot of me answering your questions in my honest opinion and none of you answering any of mine. I could care less what people do in the community as long as its their own original work. Copying others and profiting off of it is a bit of a dick move. You're going to release schematics regardless of what I say here so I personally could care less; they're easy to recreate anyways. And I'd love to see devs in the community actually create something of their own without ripping off other people's stuff.

I'd love to see the community actually create something of their own for a change.

Yes, the S.E.M is your own design (it's like an hour of work in kicad) that requires someone else's software before it can actually do anything, congratulations on your achievement. Perhaps you can answer my questions regarding "your" HDMI board design?

I can't speak for him, but show me your software you intend to run on it.

Enlighten me

Thanks, but the only questions I'm really interested in having answered for now (which you've conveniently skipped) are these (and this is just one specific example out of many I know to exist as differences between "your" design and Ryzee's). Please tell us a bit more about your design from a technical perspective; anyone else I know would be ecstatic to discuss their creation and the trials/tribulations encountered along the way.

What your “evidence” looks like to anyone else that knows what they’re talking about

I’m telling you (which anyone can independently confirm) the site just allows the user to upload their copy of the retail 5838 bios directly to the Stellar chip over USB, nothing more. The combining of Dustin’s original code (StellarOS firmware) and the 5838 bios image supplied by the user happens within the Stellar chip on each boot cycle. You appear to be implying Microsoft stuff travels between the end user and Dustin, but that’s simply not the case; he doesn’t host any of that.

This is you selling modchips with XeniumOS preinstalled which bypasses Xbox DRM by not booting into the retail kernel, right? https://www.ebay.com/itm/196118797013 I don't think it's necessarily wrong for you to do so (it is technically Xodus software and Ryzee's CPLD code), but it's a similar situation with Stellar, except I'd imagine Stellar is slightly more protected in that it's non-functional and has no chance of bypassing anything out of the box until the user adds their stuff to it. Again, not a lawyer, I just think you guys are grasping for straws here when literally everyone else in the scene is doing equal or worse. Why you're ganging up on Dustin for attempting to do things by the book is beyond me.

Yes, the website where he sells his original hardware and software (doesn't infringe on anyone else's copyright because it's all his own creation) is located in the US.

When using the Stellar setup website you're referring to, anyone can easily verify via packet captures (network and USB) or by looking at the app's source code (plug it in to an online beautifier to make it easier to read) that everything happens locally on your computer and the bios the user uploads goes directly to the stellar chip via fancy browser USB integration and not out your WAN connection. TLDR: The retail 5838 bios the user provides is sent directly via USB to Stellar and not over the network.

The problem with your questions (and many others' as well) is they're usually all over the board and hard to track whereas I'm always talking about the same specific thing, but I'll try my best. I don't understand all the fake outcry for the Xodus domain registration. It's been abandoned and turned into a landing page by someone else for well over a decade; anyone would have had equal opportunity to complain about it then or purchase it since The reasoning behind its acquisition is also not so devious, so sorry to disappoint. Believe it or not, it's just a really cool piece of Xbox history (probably top 5 in my book) and the RTOS used at the time is super interesting from a technical perspective which not many know or even care about. How are you (or anyone else for that matter) somehow more worthy of being custodial to something you really know nothing about from a software perspective? https://web.archive.org/web/20090122031718/http://teamxodus.com/ https://web.archive.org/web/20120415150857/http://www.teamxodus.com/ The modville one is somewhat petty if true, but I'm not Dustin (not sure why I have to even say this, but these opinions are all my own), so I don't know what you expect from me in terms of any kind of explanation, why don't you ask him My presence here is purely reactionary, and it's quite simple, don't monetize other people's work and then cry foul and claim victim when you're called out on it. Your original designs are great, why don't you stick to those? This is literally the only issue I've ever had with you, and my stance here has been consistent. It sure does unfortunately. It's easy to predict where you're going based on what you've locked yourself into by planning around someone else's design. It's also kind of difficult for people to offer the assistance you've asked for if you aren't even willing to discuss specifically which part(s) you're stuck on, which Xbox versions are affected, what things you've tried etc. It doesn't appear to contain any Microsoft code, but does bypass their "secure" bootloader which is the first part in their chain of DRM. It's about as legal (I'm not a lawyer) as you can get considering some alternatives, but Cromwell can't play games, and I don't see a lot of people flocking to linux on Xbox. Interoperability is an important one, and is used quite frequently as reasoning by reverse engineers for good reason. As the admin already touched on, the Xbox is over 20 years old and out of production/service (MakeMHz products are still available for purchase and/or in active-development however), and components are failing resulting in unusable boxes. To ensure continued operation, some DRM components may need to be modded. DVD drives (sig checks) and even DVDs themselves are dying at an alarming rate, hard drives (password-protected) will eventually fail, I've seen EEPROM (contains security keys) corruption/failures, the flash chips (bootloader and kernel which also have security keys) are only rated for 20 year data retention in the datasheets, so modchips are sometimes required to bring a box back to life to ensure interoperability.

Since you asked, I'm going to take the time to answer your questions, and then I'd appreciate it if you'd stop deflecting/distracting and let Nem answer mine, deal? There's nothing odd about Ryzee and LoveMHz doing similar things around the same time frame. We're all friends, some xboxdev discussion (like "this would be cool if...") we've had could have sparked their minds independently, and once they learn of each other's projects, they bounce ideas and suggestions off of each other as they continue to work independently. Both Ryzee and Dustin each have confirmed this on multiple occasions; there's no conspiracy here, so you can take off the tinfoil hat. Regardless of how similar you think their solutions appear, there are some key differences in how they function which I wouldn't expect non-technical people to understand (which you're clearly using to your advantage when attempting to confuse others into agreeing with your viewpoints), and that's okay. They're also both equally capable of going into great detail about their designs and why they did what they did for various parts of it, which I don't believe Nem can for his judging by his repeated silence when asked simple questions regarding such. This would by far be the easiest way for him to prove his design isn't a clone; if he could actually explain the design which he supposedly created. Normally PMs are private, which I take very seriously, but the cat's long out of the bag and figure it won't hurt sharing this bit which occurs before your linked tweets. Clearly he's been working on this even longer (probing setup and prototype images followed), and I know some others knew well before me. What's funny about the Halo screenshot you mentioned, is I believe it's actually mine . I recognize the poor XY offset of the image which I hadn't bothered fixing at the time on my capture card setup. It's also my Halo 1 720p patch being shown in the image for demonstration. Myself and Ryzee have also stated several times in multiple places that neither of us benefit (monetarily, etc.) from anything Dustin does, hell, I've purchased my own HD+ and Stellar when they came out. It's also getting old that people keep suggesting otherwise, because many in the scene who know me personally would wholly back me up on this, and Ryzee is even more selfless than I. We simply "complain" because we're creators and don't like seeing other creator's taken advantage of. The repeated drama stemming from all this is quite absurd.

As a crappy hobbyist EE, I'd be interested in hearing more about some of your main design decisions. For instance, why did you elect to go with a supplementary QSB when Ryzee didn't? What does this circuitry do exactly? Do you think the same QSB would also work with Ryzee's board as-is? If this is truly your design (because it clearly differs from Ryzee's on account of it not existing in his design), you should have no issues going into further detail as to how it works on a technical level, right? Otherwise, why would you include it? There are plenty of other actual differences between yours and Ryzee's, but not so much between yours and MakeMHz's, which I just find odd I guess

Will the STM firmware be open source? Or are you expected to steal the MakeMhHz version instead?

You're comparing a slice of cheese to a sandwich

The fan speed SMBus/PIC command controls the fan PWM duty cycle so any kernel, app, or i2c hardware peripheral would be capable of regularly querying (ideally listening for) temp and adjusting the fan speed accordingly to target a certain temp etc.

This honestly slipped my mind as I don't really deal with anything other than extract-xiso, but repackinator source would be a way better reference than mulleter decompilation. I'd still refer back to antangelo's project for more context however as repackinator seems overly complex for some of what it's doing and doesn't have any comments so it may be harder for you to follow the logic. https://github.com/Team-Resurgent/Repackinator/blob/main/Resurgent.UtilityBelt.Library/Utilities/XisoUtility.cs

This is probably even less-readable than C to you, but it's well-structured/commented and the author is still around - https://github.com/antangelo/xdvdfs/blob/main/xdvdfs-core/src/layout.rs Alternatively, you can also probably use the decompiled output (via dotPeek etc.) of XboxDVD.dll bundled in the XDVDMulleterBeta app which is written in .NET, but possibly cleaner than extract-xiso source.

There won't be any issues from me. I've been calm this entire time and said what needed to be said, all of which only started with me expressing my disappointment alongside Ryzee and everyone (mostly you, but it's alright, I've forgiven you and still do) piling on afterwards. I'll likely follow up elsewhere with an objective in-depth technical analysis and comparison (since I already own both MakeMHz and Ryzee HDMI boards) once I get my hands on Nem's final hardware/software solution, but won't bother mucking up this thread any further unless I'm either addressed directly or most importantly owe him a sincere apology, and will happily eat my words for claiming he intended on Dustin's closed source code to be used on the hardware he sells, because the differences should be quite apparent if it's his own work or a derivative of Ryzee's open source version as he originally describes versus just using Dustin's stuff.

The gaslighting, strawmanning, and personal attacks taking place in this thread is unreal. My stance here has consistently been "don't use Dustin's XOS patches or HD+ firmware on your hardware when you can write your own or do something else", that's it. Anyone looking back in this thread can clearly see this. Your repeated insistence that somehow I've changed tune just isn't true. Whether you understand this or not, as it relates to XOS, there's the base image created by Team Xodus ~15 years ago (owned by them and always will be) and the patches to it written solely by Dustin. Everyone seems to have already accepted that selling/distributing chips with the base XOS is fine; it's still wrong (you, Dustin, whomever, it doesn't matter) in my opinion (and I've already said this multiple times throughout this thread, not just now), but by varying degrees of such that really don't concern me as I don't sell them. Dustin has since modified the base XOS image with his own patches, and the patches alone are the only thing I've ever referred to here as what's his, it's not complicated

Again, I don't think anyone here really cares (not that there isn't still some consideration to be made, because it is Xodus') about the original XOS binaries being used, we were just discussing it in the context of you using the MakeMHz-patched version on your hardware, but enjoy your "pineapple free" version