Natetronn

https://en.wikipedia.org/wiki/Dd_(Unix)

Yeah, I know. It just doesn't recognize the modchip, as that particular chip isn't in the list of modchips that XBlast OS stores in this switch code: https://bitbucket.org/psyko_chewbacca/lpcmod_os/src/b2b9fbb4dd43216acc936bee250029dee2492376/xblast/HardwareIdentifier.c?at=master#lines-185:210 My suggestion is to ignore it and flash anyway. "This modchip isn't recognized."

That really should have said, "This modchip isn't recognized."

Sure, people can rename them or people can download them from Xbins instead, like you said. And I get you're the one who's taking the time to do it, so not trying to give you a hard time here or anything (thanks by the way.) Oh and I get why that tree makes sense for the various installers. From a programmatic and convenience standpoint, it makes sense. Plus, since you're the one doing two installers, I assume it makes it convenient to share it here the same way you do for both of those. That said, I do wish the files were named descriptively, particularly for those times where the files end up sitting in C:\Bios\ on the console (vs only ever living on an installer disc or in their original zip / named folders.) Coming across a console with C:\Bios\bios.bin and saying, "hmm, I wonder what this bios.bin is?" and having to go, "oh well, guess we'll never know" and then deleting it, because it's basically unknown garbage at that point seems, well, less than ideal. Just thinking about the future people (or future us) who come across all this stuff and wonder what the heck bios.bin was, that's all. Of course, it's not a big deal, but I'd argue that's a two way street and keeping the files named accordingly seems the better of the two streets, if you will. Anyway, I digress.

Is there any reason to rename the bios to bios.bin? It's nice knowing what bios was used; the version number etc. If not for the current user, the next one.

I contacted admins to fix a typo in my initial post, should be 272 NVCLK (not 172), so: 152 FSB = 150Mhz272 NVCLK = 825Mhz ~824HMz is what it reads in XMBC4Gamers when all said and done on the 1.6 I tested on, but ymmv.

Maybe. Just depends. I had some success testing between dashboards and a couple apps, but I didn't test much more than that; mostly just to see if it actually worked or not. I'm not sure IGR will work. You'd need to overclock the traditional way if you wanted more "stick".

I put it in E:\Applications\Xbox Overclock\default.xbe This is probably (?) a good start: 152 FSB = 150Mhz 272 NVCLK = 825Mhz

Just got my ArdPromSD. It arrived packaged very well in a black bubble bag, small box with a thank you sticker on it and thank you tissue paper inside and sliced cardboard padding on the bottom and the chip was inside an anti-static bag and although I haven't tested it yet, I'm confident it will work, as it has a QC Passed sticker on it lol. Looks like fine craftsmanship too. Thanks Dtomcat18!

Thanks for all the work on this!

Ah I see, thanks for the assist.

Is this what you're looking for? Settings (black button) > Skin Settings > Scripts > Run - 480p Game Loaders Script?

I hear there is still bios testing going on in 2022.

All good, no need to say sorry, just double checking I'm on the list