Advertisement
SonsOfLiberty

XGD3 Sub-Standard Media Burning Guide

Dec 28th, 2011
2,014
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 12.60 KB | None | 0 0
  1. I'll post 3 guides/tutorials in this edit, first guide I wrote myself, second one was pulled form various sources, the ImgBurn was pulled from http://team-xecuter forum.
  2.  
  3. 1 - My Burner Max Table Edit
  4. 2 - Someones else burn method using settings and mumbo jumbo
  5. 3 - ImgBurn verifying guide and why sometimes it fails on verify which usually isn't the bad burn you think it is, you say what? Just read the 3rd part :D
  6. 4 - Are the KProbe numbers you should get with MAX and what the standard should be, I would assume they need to be this for a "good/logical" burn...reports say some peoples
  7. numbers are ALL OVER the place but they can still install and play their games fine and have for hours, even on dreaded Forza 4, unconfirmed by me.
  8. -----------------------------------------------------------------------------------
  9.  
  10.  
  11.  
  12. NEW INFO HAS CAME IN... If you really really aren't going to be using verbs, whatever ID you disc is, replace it with the VERBATIM 001 2.4x write stragey and get superb burns.
  13. Note if you change this and plan on using 001 verbs you will have to flash back to original FW, mkay?
  14.  
  15. Guide 1:
  16.  
  17. Want to get other media to burn besides Verbatim and work on burner max?
  18.  
  19. First we need this: Media Code Speed Edit 12010
  20.  
  21. Download: http://www.datafilehost.com/download-ffaa39ca.html
  22.  
  23. Now, firstly I TAKE no responsibility for YOUR failure to follow directions.
  24.  
  25. Find c4eva's firmware that he supplied for your drive...
  26.  
  27. For example mine is: iHAS-124B-AL0S-MKM001MKM003-final.bin (Obvious this will vary depending on your drive)
  28.  
  29. Make a copy of the Burner Max Firmware, and place in a another folder and name it what you like, mine was TDK TEST FW.
  30.  
  31. Now open Media Code Speed Edit, next in the upper right you should see LOAD, click it and load your copy
  32. of c4eva's burner max fw. Now you should see a lot lot of disc ID's, be care full NOT all are for DVD+R DL.
  33.  
  34. How do I find my Disc ID?
  35.  
  36. Load ImgBurn, and hit Discovery and scroll down on the right till you see DISC ID: xxxxxxxx
  37.  
  38.  
  39. Now once we have our ID, find in the list in Media Code Speed Edit.
  40.  
  41. Find your ID, now you see the speeds and it will say like 4x , 6x, 8x, we don't want that on cheap media.
  42.  
  43. So now here's the next part, you want to find a disc ID that has the speed of 2.4x, but YOU do not want to select ANY of the MKM tables,
  44. leave those alone, those are the VERBATIM ones.
  45.  
  46. So what I used was this Disc ID: ISSM
  47.  
  48. Now the easy part, your disc ID, whatever it may be, double click it: you should be presented with a window that will say media code to replace with:
  49. and now we USE ISSM which has 2.4x write, just click on it and hit OK, it will give a warning box, click YES...you can use any you wish, but if you
  50. have those other ID's they will no longer work (remember DO NOT USE MKM), this is why I choose to use some off brand I've never heard of, that does only 2.4x,
  51. obviously you can select one that has a 2.4x-4x write if you wish, just don't use MKM.
  52.  
  53. Now go to the upper right hand corner (near the X aka close button) and "select Save", just click on the copy of the firmware we originally loaded and click YES for over write.
  54.  
  55. Now you firmware is now saved :D
  56.  
  57. If you want to be safe, re-load that same firmware in Media Code Speed Edit and make sure the DISC ID: your using only says 2.4x.
  58.  
  59. Onto flashing it's the same principle except will just use: Flash_Utility (it's in the fw pack)
  60.  
  61. Load Flash_Utility, pick correct drive, click "READ", I backed mine up for just the sake of it, it's up to you
  62. and I saved it in the same folder as edited FW. After done "reading", click write, click yes, load your edited fw, and yes once again, should say completed
  63. successfully or something close to that, that's it!
  64.  
  65. Now power down your PC, let it sit for a few seconds, and power back on.
  66.  
  67.  
  68. NOTE: On my burn/s I did NOT use OPC in ImgBurn, you can play and test yourself, for me, this works and
  69. is just fine.
  70.  
  71. Also I did not mess with these: Smartburn = enabled Force Hyper Tuning = disabled Online Hyper Tuning = disabled
  72.  
  73. I only left Smartburn enabled, if this way doesn't work for you, you an try enabling them or enabling OPC, just play around with settings and burns.
  74.  
  75. Now, when you start your first burn in ImgBurn, no matter what you do, ImgBurn now will never go above 2.4x
  76. with the current Media ID disc your using.
  77.  
  78. I've burned 4 TDK's so far, all verify successfully....
  79.  
  80. Use at your own risk and enjoy, and thanks go to c4eva, and for Giglife for giving me the idea and successfully testing some other media on it.... :D
  81.  
  82. SOL
  83. -----------------------------------------------------------------------------------
  84.  
  85. -----------------------------------------------------------------------------------
  86. Guide 2 (not mine pulled from various sources):
  87.  
  88. Firstly, remember the EEPROM Utility you used? OPEN that sucker up again!
  89.  
  90. Go to the OPTIONS tab. Enable ALL options EXCEPT FOR OVERSPEED!
  91.  
  92. After each one, you will get a GREEN text saying Successful blahblah.
  93.  
  94. Exit. No need for reboot. These settings will stick even after PC off.
  95.  
  96. Ok. Now the nitty gritty. In my experience, Verbatim MKM-001 are less reliable than
  97. my TDK (RITEK-S04-66). (SOL's input says he's full of shit :D)
  98.  
  99. These TDKs ONLY burn at 4x/6x/8x. Attempting to use 2.4x will show in IMGBURN
  100. log: Write speed miscompare, wanted 2.4x, got 4x (not actual quote). So 4x will be forced.
  101.  
  102. OPC can be left ON or OFF for these TDK. OPC OFF should be used on the lighter purple-backed
  103. discs. Get a verb mkm003 and a TDK s04-66 and look at the back. Now look at a memorex.
  104. In the case of the Memorex, we WANT to use OPC OFF. But keep in mind that heave Caching/HDD
  105. activity WILL destroy this disc and still burn to the end. Memorex are BAD for this. I am
  106. just using as an example of disc quality by color. I would say to first to a TDK at 4x
  107. with OPC OFF and NOTHING ELSE RUNNING! IRC of course is lightweight, but have the BROWSER
  108. open before the burn. so that the openning and caching of it will not interrupt the disc.
  109.  
  110. After this disc burns and VERIFIES in IMGBURN (should not have to click or READ ANYTHING
  111. after you click burn. NO ERRORS and NO DIALOGUES). If you do get a dialogue its bad. It
  112. should write and verify all with no dialogue. After you get a good burn with OPC OFF
  113. it is ok to turn ON OPC, and you can use your PC a little bit more... Just be sure to
  114. limit your activity. Set your IMGBURN buffer to 100MB (Settings>I/O>Page 2).
  115.  
  116. MKM001 at 2.4x only worked for me with OPC OFF
  117.  
  118. MKM003 at 4x OPC ON failed
  119.  
  120. MKM003 at 4x OPC OFF failed
  121.  
  122. MKM003 at 2.4x OPC ON SUCCESS
  123.  
  124. MKM003 at 2.4x OPC OFF SUCCESS
  125.  
  126. TDK(RITEK-S04-66) at 4x OPC ON SUCCESS
  127.  
  128. TDK(RITEK-S04-66) at 4x OPC OFF SUCCESS
  129.  
  130. TDK(RITEK-S04-66)(WITHOUT extra options in EEPROM ON) at 4x OPC ON FAIL
  131.  
  132. TDK(RITEK-S04-66)(WITHOUT extra options in EEPROM ON) at 4x OPC OFF FAIL
  133.  
  134. Part 2 of this guide here:
  135.  
  136. TO FULLY BURN XGD3 ON A 15-CENT-PRICED DISC (mostly RICOHJPN-D01-67 media, any brand is possible; RITEK-S04-66 had (very) low success rate according to
  137. tests (not my tests though) CMC MAG-D03-64 had almost 100% success rate but also a higher price)
  138.  
  139. Run ImgBurn 2.5.6.0 (future higher version will also do).
  140.  
  141. 0.Turn on or off Tools -> Settings -> Write -> Perform OPC Before Write, different disc will have different success rate with this option on or off.
  142.  
  143. 1.Select "Write image file to disc" as usual.
  144.  
  145. 2.Click "Advanced Settings" button in bottom right corner. (Marked red in screenshot)
  146.  
  147. 3.Open Lite-On panel in Advanced Settings. It is required to click the individual "Change" button if you changed any setting item and a "Success" message
  148. will pop up to confirm the change.
  149.  
  150. - Turn on Online HyperTuning
  151. - Turn on SmartBurn
  152. - Turn off OverSpeed
  153. - Turn on or off Force HyperTuning (same reason as OPC mentioned in step 0)
  154.  
  155. -----------------------------------------------------------------------------------
  156. ^ that above I have no even attempted testing since my method works
  157. -----------------------------------------------------------------------------------
  158. Not my info but figured I would share :D
  159.  
  160. Written 10/23/2011
  161.  
  162. For those who can't get IMGBurn to verify immediately after burning stop trying. HOWEVER, if you still want to try because "it makes you feel better"
  163. try these steps. Instead, let the burn complete then go back into IMGBurn and do "Verify Disc".
  164.  
  165. http://i53.tinypic.com/2hhglu9.png
  166.  
  167. This method may verify for you just fine, in which case you can stop reading this and continue to KProbe for additional tests.
  168.  
  169. For others, you may be receiving some I/O Errors. Well, simply saying "I've got I/O Errors" will not help us to diagnose the problem.
  170.  
  171. I'll briefly go over 1 of the MANY types of I/O Errors. If your I/O error says "The semaphore timeout period has expired", that is a hardware error.
  172. In other words, you're running IMGBurn from your main hard disk, while verifying an image on another hard disk, while using an external optical disc drive.
  173. Basically, IMGBurn is saying "WTF, information is not cached and i'm tired of resetting the device for it to catch up so i'll throw this error". If you
  174. require further explanation, I an give it to you.
  175.  
  176. Assuming that you're using media that Uber, C4, TX, etc. have approved as working (MKM003 or MKM001) chances are, nothing is wrong with your burn and you
  177. can continue to KProbe for further verification.
  178.  
  179. To solve this issue, try to make all things equal. In other words, don't use an external optical drive enclosure because you're creating a bottleneck and
  180. just for verification sake, copy your backup image onto your main hard drive. I know what you're saying, "You just built that massive Core i7 machine and
  181. it's capable of curing cancer!" Well it's not.
  182.  
  183. Just reduce your variables and try again. If you're using a external enclosure for your optical drive you're limited by not only the USB connection but the
  184. controller of the external enclosure, and to be frank, most of them suck so you'll receive errors. Like I said, make it easy on yourself.
  185.  
  186. Chances are, if your backups look like this in KProbe, (this is a XGD3 backup) you're just fine. Also, look at Uber's scans. Like I said before, even if
  187. IMGBurn verification fails, you may well have a good disc. The true test lies within KProbe.
  188.  
  189. -----------------------------------------------------------------------------------
  190.  
  191. From TX Forum:
  192.  
  193. Make sure KProbe2 is set to 4x CLV Scanning
  194.  
  195. PI MAX should be 100 or less & PI Average should be 5 or less
  196. PIF MAX should be 4 or less & PIF Average should be 0.20 or less
  197. Nero Score should be no less than 90
  198.  
  199. The fact that the burn verifies at 100% is irrelevant when you are testing the quality through KProbe2 so you may want to not waste your time doing that
  200. extra step. It doesn't hurt of course - but if you are running a full Kprobe scan its going to give you your correct verify results anyway regardless of
  201. what imgburn tells you.
  202.  
  203. There are many factors that affect a quality burn and/or test. Too many processes open in the background in Windows, poor quality SATA chipset, SATA set to
  204. AHCI instead of IDE can affect results, a dirty disc (fingerprints etc), burning from a fragmented drive (make sure images are on a nicely defraged drive
  205. with plenty of free space).
  206.  
  207. Also there are various settings with the EEPROM / IMGBURN that you can play with such as.....
  208.  
  209. Smartburn = enabled
  210. Force Hyper Tuning = enabled
  211. Online Hyper Tuning = enabled
  212.  
  213. Remember Verbatim MKM-001 = 2.4x with OPC in IMGBURN disabled and Verbatim MKM-003 = 4x with OPC in IMGBURN Enabled.
  214.  
  215. Nothing is set in stone but this is a good guide to put you on the right path. Remember the discs are now being pushed to their limit so the margin of error has been greatly reduced.
  216.  
  217. -----------------------------------------------------------------------------------
  218.  
  219.  
  220. Last notes, this is almost every way possible to solve your burning issues, while using Verbatim (which you should, they usually always burn the best and
  221. have the "BEST" change of success). But this doesn't mean you can follow guide 1 and 2 and can't achieve great burns on sub-standard media. Tell how
  222. bad some of these TDK's I have are here, I burned about 5 so far, during this burning testing, I had 2 TDK's when inserted and starting to burn, ImgBurn
  223. gave me the dreaded would you like to "Overburn or Turncate" the disc, yes very LOL, cause there was not enough room on the TDK even with Burner Max
  224. Firmware, this shows how the quality of sub par media goes from disc to disc, and spindle to spindle.
  225.  
  226. Well that's it, hope you get some great burns on whatever you choose :)
  227.  
  228. -SOL
  229.  
  230.  
  231.  
  232.  
  233.  
  234. More INFO?
  235.  
  236. Try #fw or #c4e or start an account here: http://team-xecuter.com
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement