QUOTE(xbrains @ Nov 1 2007, 09:41 AM)

I think I have discovered a mistake in the file "BENREMOQ". The directory where it gets the bios file is currently "copy quiet\fw\benq-ixa.bin". I believe it should be "copy quiet\fw\benq-ixB.bin" Correct me if I am wrong.
Cheers. An updated benbatch.rar is now online (same name as the previous one), also on Xbins. New .rar file is 6412 bytes, and gives you credit for bugspotting in the readme!
QUOTE(BoNg420 @ Nov 1 2007, 11:23 AM)

its quite sad people need batch files or any type of auto-flasher. its only a few simple commands. It was the same way for samsung. There was autolasher tools, but who really needs them.
It saves making mistakes. A batch file NEVER makes a typo. I don't even trust myself when it comes to repetitive stuff (which is why I always leave the eject button on top of the unshielded 360 lid - if I don't, I forget to refit it) which is where the batch files come in handy. They're geared towards "professional modders" who do a lot of boxes, need to keep track of which firmware came from where, and who want the end users' boxes to be in safe hands.
QUOTE(rabbitstroker @ Nov 1 2007, 11:51 PM)

@eXOBeX
Thanks for for your hard work and time, look forward to future releases from you (IMG:
style_emoticons/default/smile.gif)
You're welcome! I might even release my hacked GaryOPA files (which save in the same structure as BENREAD/SAMREAD) but I haven't bothered getting FLASH24S.BAT and FLASHIX.BAT to co-exist in the same directory yet.
QUOTE(BoNg420 @ Nov 1 2007, 05:40 PM)

I know, but I just cant see trusting an autotool, especially if its someone elses box. I'd rather make sure I do everything myself. I don't even trust samtool, as it has put the key in the wrong place before for me.
I don't use SAMTOOL, basically because I don't need to. I know X360SAM inside-out though, I know it's thick-as-shit when it comes to drive keys, just copying the whole block without trying to figure it out, and it's never let me down. The next version (when I can remember where the source code is) will add BenQ spoofing, that's probably just about it.
I use FIRMTOOL though, because I don't have any reason to doubt Caster420's work. He writes using a decent language (Turbo Pascal isn't it, Caster?) and I think that, like me, Caster would be on a major guilt trip if he managed to fuck his code up and create a brick-fest, so things get tested, and tested thoroughly. The only thing I'd change about FIRMTOOL is that I'd go for the 3-files approach (orig, xtreme, hacked) rather than the 2-files approach (orig, copy-of-xtreme-that's-going-to-become-hacked) but that's just personal preference.
X360SAM does what it set out to do: directly replace the need to hexedit a big block of code in Windows.