You would have to burn them and then run it through kprobe to see what sort of results you get back, just because you have an mkm 003 version doesn't neccassaraly mean they see good discs some people on the forums have been using bverbs mkm 003 and still had shocking results albeit they were made in Taiwan, report back once you've took the needed stepsI have Videx DVD+R DL discs that show
"MKM003" on info, so that means that
I can use this instead of Verbs ?
My lite-on 124 says the same, its B model but the flash is nex, diden't have any probs with flashing it using my Icy box external bay, unfortwnly i don't have any Verbs here to burn yet, but i would like to hear from Uber if there might turn out to be a problem when the flash ain't MCIX, my model is iHAS 124-19I can't write the flash either. I am suspecting it has to do with it saying the following under flash type: NEX(NX25P16) - (1-0)
Note that the drive IS labelled with the B both on the label on the actual drive itself but also in device manager. Does this mean it's still the wrong drive even though correct letter?
I switched from using my external bay with drive connected via usb to laptop to using the usbpro and my desktop and now it worked. Still don't know what was wrong with the first approach as I did everything exactly the same. Nice to have it working though
Did you read the first page of this thread??, It shows the 6 compatible drives, They have to be model# iHASxx-xx B to use maxburner f/w Manufactured 2011, There are some drives that can be crossflashed to ihasx24 but older liteons aren't one of them, http://www.team-xecuter.com/forums/showthread.php?t=73461&highlight=crossflashI have an old Lite On drive from 2006 or 2007. Could I flash that with the 124 firmware and then the max burner?
I'll pass that on to see if its something genuine that needs addressing
More quotes:a feature of dvd+r spec is write strategy is loaded from the blank media from the adip, which seemed to work better for mkm003 as well as enable 2.4x
Remember this is a non standard burn. out of the box, crazy sh*t not supposed to happen or even possible......C4E: testing produced better results ie no failures with mkm003 using media info from adip (as opposed to media info in fw) as well as enabling 2.4x burn speed
C4E: media info is loaded from adip when there is none in fw. our focus was better burn results for the extra data area ie no write/verify failures.