i thought i would help a certain few people out with this little tutorial of mine
for all those people who get Port:170, Master/Slave: a0 or a message like that when using mtkflash and cant get extreme bootmaker to autodetect your ports
anyways moving on
first of all
run your extreme bootmaker 3.2/3.4 load in the correct extreme flash
then choose custom mtkflash choose the serial ata controller you use then open msinfo32.exe from the run menu
locate your serial ata controller by clicking on components then onto storage
it will be in ethier scsi or ide shown example below
anyways you need the two sets of numbers from your device id and i/o ports
these are highlighted in red for you's
Name VIA VT6421 RAID Controller
Manufacturer VIA Techn
ologies, Inc.
Status OK
PNP Device ID PCI\VEN_1106&DEV_3249&SUBSYS_32491106&REV_50\4&CF81C54&0&10F0
so i have 11063249 they are my first set of eight put them in the first box DEVICE ID
then comes the next numbers we need for the i/o port box these are always the 1st and 3rd line of i/o's and in the exact postion as mine
I/O Port 0x00009080-0x0000908F
I/O Port 0x00009000-0x0000900F
I/O Port 0x00008C00-0x00008C0F
I/O Port 0x00008880-0x0000888F
I/O Port 0x00008800-0x0000881F
I/O Port 0x00008400-0x000084FF
so my numbers are 90808C00 these go into the second box I/O PORTS
then locate a place to store the your custom mtkflash from target drive
now click prepare drive
then goto where it has created the files and copy out mtkflash.exe and as this is what we are intresed in and delete the rest paste and replace the mtkflash onto your usb/foppy
now you will have a working boot disk that will id your ports as xtreme 1 and 2
also for those that get the choice of ports and then sticks on Port 170, Master/Slave: b0 after choosing ports
boot with xbox 360 on and when at the select xtreme port option turn off the xbox 360 hit the port number its on and then count to 12 then repower the 360 this will take a couple of trys but will work i have had loads come to me with this probleml and my method has resolved there problem
this problem is also known on ms25 drives with a sticker over the ms 22 firmware id
any feedback welcome
Social Networking Bookmarks