QUOTE(millio007 @ Oct 28 2007, 01:50 AM)

GR8 advice I got the same error was about to shit my pants lol Anyway if you get WRITE errors when doing this on dos 16 You can be sure that you will get error 65 DISCONNECT all IDE AND SATA ports except for the 360 gave it the compatibilty that it needed I guess anyway after this happens erase current reflash and reflash again no neeed to restart PC C4 ownz
Yea, hence the posts repeatedly about disabling onboard IDE/SATA controllers. In some situations you can still have issues regarldess of physically disconnecting cables. BIOS disabling is preferred.
QUOTE(out4it @ Oct 28 2007, 02:07 AM)

OK figured it out. Somewhere down the line a Symantec(shit products) was installed on my pc. Went through the registry and deleted all refs of it. Still no help. Went to my wifes comp to make the fw,and 1,2,3. Then transferred back to my usb stick. Did the erase command, and reflashed. Worked like a charm. But one thing I did notice was after the erase,I just had to power the drive off the on and it flashed. Not 2x like the readme said. THIS WAS JUST AFTER THE ERASE. NOT for the first flash. Worked like a charm. Thanks to everyone especially Castor for trying to help. Although the intial error for when I tried to make the fw is a mystery worth looking into. I still get the error on my PC. Thanks to everyone who worked on this FW!!
ICH 7 chipset
Via 6421L
disabled all drives in device manager.
The reason you were able to flash on first boot after erasing is because the benq firmware has a locked flash. The whole point of the new dosflash is that it polls the drive for mtk unlocking. This is not needed if the firmware on the drive is not present, because without the firmware there is no locking process. That is how the 'recovery' mode works when you cut the traces. And yes, symantec is a POS.
QUOTE(m3kal @ Oct 28 2007, 02:29 AM)

Ive read the original fw fine, made the ixtreme, i can erase the drive ok, but when trying to write, it says cant read binary file

im using via6421 card, after erasing do i turnoff 360? any ideas. Thanks

Sounds like the file does not exist, or perhaps the properties of the file are not set to read. Use a usb thumb drive and your issues should be resolved. Format it with xbm or iprep to make it bootable. then copy firmtool.exe and the ixtreme bin. Just so you guys know, you dont HAVE to boot back into windows to run the batch process to generate the ixtreme benq version. Just run firmtool as its supposed to be ran. e.g. read fw (orig.bin) then type firmtool.exe orig.bin benq-ixA.bin and it will copy the key/serial from orig.bin to the ixtreme version for proper use.
QUOTE(PaddyPat @ Oct 28 2007, 02:48 AM)

So it worked on your ICH7 board with a VIA 6421L SATA card installed? I thought it wouldn't detect the drive on this chipset.
nm....I guess this was
updated yesterday to include ICH chipsets
....you obviously have not read ANY posts regarding dosflash 1.3. It has nothing to do with the manufactorers chipset, but what chipset you are TRYING to use. If you have a PCI addon VIA card, you are using a VIA card, regardless of the onboard sata controller.
QUOTE(straps @ Oct 28 2007, 03:15 AM)

Flash Confirmed working
First i created a bootable usb stick with dosflash 16 on it, then turned off my sata and ide controllers in bios
I used via6421 card with dosflash16 in automatic mode.
When making the i-xtreme firmware the bat file wouldnt work. It came up with "the system cannot execute the specific program"
To get around this I used firmware toolbox 4.5 to copy the key from my orig firmware to the i-xtreme one.
I reflashed the drive with i-xtreme with dosflash 16 in automatic mode
Drive boots up backups successfully
I read on casters post that firmware toolbox should not be used. Should i reflash with a firmware made using firmtool?
By the way if anyone else has problem "the system cannot execute the specific program" when making firmware using the .bat you can run cmd and use firmtool manually. Just copy the i-xtreme firmware benq-ixA.bin and put it in the same folder as firmtool and orig.bin. Now open a command window in the same directory and type "firmtool orig.bin benq-ixA.bin" and it will do it manually
Yes, you should run the command manually at a command prompt. It sounds like perhaps you dont have .NET 2.0 framework installed and are having issues executing a batch file. No idea why this would happen, might not even bee a .net framework issue. However in the past i've resolved such issues by installing .net 2.0 framework.
fw toolbox is not as fully supported as it needs to be, nor does it copy all the strings neccessary for *full* spoofing. We would recommend you do not use it to spoof/transfer keys until it is updated with full support.