NeMesiS

HDD Conversion: For the "Dual Fan Upgrade Kit" to work we have to remove the DVD-rom and relocate the HDD to that side. The "HDD Converstion" is split into two pieces, the "HDD Caddy" and "DVD Bezel Bracket" A gap between the two pieces has been created to help improve airflow around the HDD. The "HDD Caddy" snaps into the DVD-rom moutning bracket. I tried leaving plenty of tolerances to allow for a variety of different Drive and Adaptor installs.

Case Fan Housing: The "Dual Fan Upgrade Kit" consists of 3 main parts: "Case Fan Housing", "HDD Conversion" and the "Dual Fan Caddy". All of which will be sold separately at some point. The "Case Fan Housing" was the first thing I designed when I got a 3D printer. At the time I was seeing people trying to install replacement case fans. The mounting tabs were a point of weakness, so I decided to print them separately and included spares. I know that the "Case Fan Housing" isn't necessary but I'm going to try and works things out in a way that the "Case Fan Housing" is either included for free or at a highly discounted rate.

Filament: I know I'm being super picky about the filament but I really liked 3dfillies product. I contacted them to see when they were expecting filaments to be restocked. They assured me that they're next shipment was expected to arrive on the 8th, plus a few days to unpack and inventory the shipment. They also brought it to my attention that: "Formulation has changed slightly to make it stronger so the appearance it a little more shiny". This shouldn't be an issue, looking forward to ordering from them as soon as stock is available. And to start printing the "Dual Fan Kits" for official release.

Recapitulate: Due to my usuall supplier "3dfillies.com" not having sufficient stocks of filament. I have not been able to start printing these off for sale in larger quantities. Did some test prints with other filament brands but I wasn't happy with the results. Until a solution can be found, I decided to go ahead and print using what available filament I had remaining. Some of which are still available at a discount for those that are interested...

Introduction: Designing the "Dual 80mm Fan Caddy" was a nightmare... It's been something I've been working on for a few years now. Tolerances were extremely tight, much of it had to be spot-on to fit correctly. The design has been split into separate pieces to better suit 3D printing. This reduces the chance of failures and helps produce quality prints. I was able to send a half dozen samples to volunteers for testing sometime ago. The results were far better than I had expected, I've still not had the chance to see for myself but I trust the feedback that was given to me.

Now that I've had a little bit of time to think... I miss how the way things were before MakeMhz showed up. There were many smaller makers and sellers around. Sure, we were competing with each other in the public eye. But behind the scenes we helped each other out. We even created a Facebook page where we all advertised our products alongside each other without any conflict. The polar opposite of what's been happening today. I would really like to see some of the older sellers return!

Well said... It really sums up the situation and that I am far from being the only victim in all this... You just don't get the point, do you? You don't need to take down your links because it should be acceptable for anyone to use or upload XeniumOS. As far as I'm concerned it belongs to the community! This is not the only thing I got you with... You accused me of not contacting or crediting the original author! I gave credit to the original author when I first mentioned my plans for the programmer. And I had attempted to contact the original author over 4 months before your accusations! Why won't you respond to this? You still have not once addressed how MM bought teamxodus domain! Are you going to keep glossing over and ignoring this fact? Your only creating resentment for yourself and MakeMhz... Anything good you've done in the past is being undone by your current actions. Now that you and the others have escalated the situation as far as you have. Did you ever stop to think if your accusations about my works on the HDMI mod could be wrong and the repercussions that will follow due to your actions? "If you say that someone is digging their own grave, you are warning them that they are doing something foolish or dangerous that will cause their own failure."

Again, trying to spin the story to favor MakeMhz... What you think we like receiving that sort of behavior from MakeMHz members? Accusations, threats, harassment, intimidation and DMCA's... I'm sick of your shit, FUCK OFF! Listen to your own advice!

So... I'm thinking we could edit the sourcecode for "Xenium-fw-update" Remove XOS Data while retaining bootloader patches... Without having a good look, I wonder if we could just move bootloader.cpp over to "Xenium-fw-update v2.3.2". As I don't think "XOS Data" had been implemented yet And for shits and giggles replace the background image for the app... Update version number and recompile? Another option would be to embed our own skin by editing xeniumos_data.cpp I did look into this a little while ago on this thread... After using your "Xenium-Repacker" and performing a hexdump I was able to compare XeniumOS_Additional_Data.bin from both XeniumOS v2.3.1 and XeniumOS v2.3.5 Here were my results... EDIT: But I'm sure you would like to have the tools available to possibly create fixes/patches for XeniumOS, as for example?

Correct... On the surface it appears to be OpenSource, well at least the app which was based on "XeniumTools" But the tools and processes involved in creating the patch's themselves were never made public... This becomes a common theme for MakeMhz, where they hinder the community at every opportunity. Not to mention constantly changing their story when their BS has been called out... They start an all-out attack just to be debunked... Then you get a response like this: Trying to shrug it off making it out that they never really cared about it in the first place... BS! You guys should be called "MakeBS"... EDIT: Sorry Dustin it's been taken "www.makebs.com"... Guess you won't be getting your hands on this one...

Ooooooh, we will... We all know how much this butt hurts MakeMhz! Nice try... Let's discuss that shall we and what we can do about it?

Agree there are beneficial fixes... I would occasionally get a modchip that would self-destruct, fortunately I put them aside for another day. Upon using the update those modchips would light up red, reboot and return to normal. (I'm going by memory here as this hasn't happened to me in a long time) Another great fix was v1.6 using component video... Yea but it just seems like he used that as an excuse, especially when you consider recent comments. And the fact that MM happened to introduce he's skin on the same update... It might have been a fix but I don't think the intent behind it was positive. EDIT: It's pretty obvious it's not what everyone wanted. So, I showed the community a way how to opt out of that fix if they wanted to. Of course, with the use of the "Xenium-Repacker"...

You can have a look at the releases along with their changelogs here: Releases · MakeMHz/xenium-fw-update (github.com) Be warned BS is included... for example: "Disables 'skin' support to prevent black screen on boot if drives fail to initialize" This is a load of crap, he just doesn't want anyone replacing he's MM skin... So, take what he says with a grain of salt...

Great little script mate, nice work! EDIT: If I forget to credit people properly, this is a much better approach...

Not sure if anyone noticed but I was able to expose MakeMHz for hosting the very same thing that Dustin and Ryzee attacked me for, XeniumOS v2.3.1 in the form of a recovery.bin! Also during my search for a source of XeniumOS, I came across this thread: Need Full XEnium Flash Memory Dump - Page 2 - Modchips - OGXbox.com Ironically "Mr I never hosted XeniumOS" has done the very same thing he accused me of. Not just any XeniumOS mind you but XeniumOS GOLD, by he's own admission it was never released to the public by TeamXodus. Essentially uploading IP that wasn't he's! You will notice this pattern a lot throughout their arguments, that they are already guilty of the things they are trying to accuse me of... Whatever professional courtesy I was extending to MakeMHz no longer exists!

Step 4: Installing pineapple free XeniumOS v2.3.5b... Transfer the newly created "XeniumOS_v2.3.5b.bin" to "XeniumTools" folder on your console. Launch "XeniumTools", select "Write a RAW 2MB Flash Dump" and install "XeniumOS_v2.3.5b.bin" Upon completion, reboot your console. Finally delete any bioses you had previously installed as they will no longer work. An easy way of doing this would be to "Reset to Factory Default" under "settings". We are all done... Share, upload and enjoy!

Step 3: Repacking XeniumOS with the Original Skin... Finally, we will need to download "Xenium-Repacker" by TeamUIX xenium-repacker.py: https://github.com/OfficialTeamUIX/Xenium-Repacker This is a python script that will allow us to unpack and repack XeniumOS. I put both the dumps into a folder and named them accordingly, along with "xenium-repacker.py". For this python script I'll be using Linux sub-system on my Windows 11 machine. Open up the terminal into the directory where the dumps are located. Use the following command to unpack XeniumOS v2.3.1: "python3 *.py -d *2.3.1.bin" A folder called "extracted_banks" will be created, rename it to something else temporarily. Now run the command again but for XeniumOS v2.3.5: "python3 *.py -d *2.3.5.bin" This time leave the folder called "extracted_banks" and replace "XeniumOS_Additional_Data.bin" with the "XeniumOS_Additional_Data.bin" from the XeniumOS v2.3.1 dump. This file (aka XOS data) will return the Original Skin and re-enable custom skins. Repack XeniumOS v2.3.5b using the following command: "python3 *.py -p XeniumOS_v2.3.5b.bin" You will now have pineapple free "XeniumOS v2.3.5b"

Step 2: Update XeniumOS v2.3.1 to v2.3.5... Launch "XeniumUpdate" and hold "X" to continue. This will update the bootloader with improvements while at the same time embedding a modified skin and removing the ability to use custom skins by updating "XOS Data". Essentially forcing MM branding upon everyone whether they liked it or not. After "XeniumUpdate" has completed "reboot" your console and launch "XeniumTools". Once again select "Dump Xenium Flash Memory" to create a dump of XeniumOS v2.3.5 We should now have a dump of both "XeniumOS v2.3.1" and "XeniumOS v2.3.5" Exit "XeniumTools" and transfer that dump to your PC as well...

Step 1: Fresh install of XeniumOS v2.3.1... We will need to download both "XeniumTools v1.1" by Ryzee and "Xenium-FW-Update v2.3.5" by MakeMHz default.xbe: https://github.com/Ryzee119/Xenium-Tools/releases/tag/V1.1 xenium-fw-update.zip: https://github.com/MakeMHz/xenium-fw-update/releases/tag/v2.3.5 Create two folders "XeniumTools" and "XeniumUpdate". Extract "xenium-fw-update.zip" and move "xenium-fw-update.xbe" to the "XeniumUpdate" folder and rename it to "default.xbe" Next move "recovery.bin" from "xenium-fw-update.zip" to the "XeniumTools" folder along with XeniumTools "default.xbe" Turn on your console with your Xenium modchip installed and boot into a dashboard. Using FTP transfer both the "XeniumTools" and "XeniumUpdate" folders to "E:\Apps\" Also transfer another copy of "recovery.bin" to "E:\recovery.bin" as a safety measure. Now launch "XeniumTools" and select "Write XeniumOS 2.3.1 Update File" then "recovery.bin" This will install a fresh copy of XeniumOS v2.3.1 using the recovery.bin Then select "Dump Xenuim Flash Memory" to create a dump of XeniumOS v2.3.1 Reboot your console, transfer the dump to your PC for later use...

How to compile pineapple free XeniumOS v2.3.5b Introduction: In this guide I will be showing everyone how to update XeniumOS to v2.3.5 whilst retaining the Original Skin! And explaining things along the way using nothing but GitHub repositories... Notes: I actually haven't done this before, the file I previously supplied was given to me. I'm not sure who compiled it as by the time I got it, it had passed through many hands. Caution: Use at your own risk! Only recommended those who know how to recovery their modchip if anything goes wrong.

They're completely ignoring my responses and questions which make it absolutely impossible to have a meaningful conversation with them. I suggest we do the same, ignore them and give them nothing. They're only purpose here is to insight hate and conflict within the community... It's a shame to see a small handful of people ruining it for everyone else, I'm sure there are good people within the MakeMHz community and I hold no offence to them. But I have never seen such behavior in the 20 years I've been working with OGXbox's... I will not give into intimidation and harassment; it only adds fuel to the fire and drives me further. I will continue working on projects as I did but I will not post anymore updates on the HDMI mod until development has been completed and ready for release... This will be the last time I will address any hostile MakeMHz members on this thread! I can only suggest that others should do the same, ignore them and give them nothing. I have nothing more to say on the matter... NeMesiS

Prove me wrong, answer my questions!

"The problem with making assumptions is that we believe they are the truth! We invent a whole story that's only truth for us, but we believe it. One assumption leads to another assumption; we jump to conclusions, and we take our story very personally" Since starting this thread I have made no announcements as to what I'm doing for firmware. Your basing everything assumption... If this not a smear campaign, then why don't you reply to my concerns? Instead of trying to attack me from every angle possible even if it's irrelevant. It doesn't matter what I say, you ignore and continue with further accusations! Then why go to all this effort? Because it's obvious to everyone here that it indeed this is a smear campaign!

Oh, I forgot to mention that I tried contacting the original author back in May, however I had been warned he was inactive. Sure enough it's been over 4 months and I have not heard back from him. But I'm sure you already knew this since you did your research? I can't show my changes if I didn't make any! I didn't make any changes to the original code with the exception of updating the GPIO to suit my design. I wrote a completely new python script in order to get the hardware to work with the software. I thought I had been extremely clear on this in previous posts... Do you not read my posts, or do you just come here to insight conflict? I haven't stolen he's credits, it's all there... Don't stress, I'm not pulling a MakeMHz! Besides myself no one else has tried it, don't you think it's better to have people test it first? Sure, I had some help with this project and I would love to credit the person who did but I'm afraid that I'll just be painting a target on their back for you and Dustin to attack. Now that I think about it, you guys never address my responses or answer my questions. You come here to discuss matters with me, yet I'm largely ignored... This is nothing more than a smear campaign!

Seeing that you're a moderator for MakeMHz are you speaking on Dustin's behalf? There's a good chance that people bought into MakeMHz's HDMI with the expectations of it being OpenSourced. I can see why there has been so much backlash, as far as people knew they were supporting an OpenSourced project. Instead, Dustin chose to take advantage of he's own customers with false and misleading claims. Essentially defrauding people! (again...) Dustin has had years to OpenSource the project but if I don't do something within 1-week you guys attack me? And (when) he does OpenSource the project what was the point of any of this... credit? Show me where MakeMhz credits teamxodus! Are you fucking serious, isn't that exactly what MakeMhz did with teamxodus? What right did Dustin have to purchase teamxodus domain and redirect it to his site? This is all because MakeMHz was removed from XeniumOS... All I did was return it back to it's original state giving the original authors the credit they disserved! And what the fuck does that matter when Dustin stole that too? So, it's perfectly acceptable for MakeMHz to steal people's work and take credit for it? They obviously can't even live up to their own expectations!