So Solid Jedi

Any Ideas Guys?

What should i do to get a good burn?

Hi, i have had 2 successive bad verify's with a PC image i was burning, i tried a different image and getting the same results, what could be the problem? I have attached my log imgburn log.txt

hmm, i know what you mean, but some sort of program is causing it to fail to verify when i have programs open like torrents and things and because im not sure the cause of the failed verifys, at the moment its just easier for me to not have anything else running when doing my burns, now of course i never had this problem with my Pioneer IDE drive but there you go.

Ok, so now ive had 2 successful burns on the trot, sticking to the idea of not running any programs in the background or internet browser whilst burning, seems to have worked....for now.....

Ok, i have still yet to flash back to stock, but today i thought id give another burn ago, so i tried to burn the same img file as yesterdays failed verify and made sure i wasnt using any programs in the background nor internet browser and quess what, it was a successful write and successful Verify with imgburn.....so i dont know? maybe having things running in background is affecting the burns with this temperamental c4e firmware? i know i never had this problem before with my IDE Pioneer drive but im gonna try and stick to this and see how my next few burns go? i have attached the image of opti drive disc read for the latest successful burn for comparison. I heard that MAX PIE should not be higher than 100 and MAX PIF should not be higher than 4, so those numbers seem good by comparison, i just dont like the higher graphs at the beginning and end of the burn though? and jitter seems to take a dip during the middle of the burn?

Yeah, i know exactly what you mean about the abusing the HDD during a burn, have had the pausing happen to me, the buffer was going crazy lol until i shutdown the program that was causing the conflict then it all went back to normal, now im not too sure if it was long enough to really affect the PIE and PIF? kinda took for granted that obviously it could have a negative PIE and PIF effect until today, before today i had never even heard of those 2 things lol.

Ok, i havnt flashed to stock yet, but i had a look at the settings with EEPROM Utility and the only box ticked is Smart Burn, the Force Hyper Tuning, Force Over Speed Writing & Online Hyper Tuning are not ticked using c4e firmware? Oh and something i forgot to mention is that the pioneer drive i referred to as my previous drive i was using for successful burns was in fact a Pioneer DVR-A18L ATA Drive, so maybe the Liteon iHAS624B doesnt like my sata controller or something? its the first Sata RW drive i have used in this setup. (Striker Extreme Mobo)

I explained all that in my second reply - post #7 Be my guest It's always nice to have extra results to compare against. since the OPC pic i uploaded was of NBA JAM, once i have flashed to stock, i will try the same NBA JAM img when burning, should i make any changes to the settings with stock iHAS before burning or leave it the same?

ok, how do i know hypertuning is turned on for the drive? or is it a default of c4e firmware? and i can try and flash back to stock firmware (stock EEPROM & Stock FLASH) and try and get a successful XGD2 burn then post OPC results if it helps? ive attached the log for all my burns to date ** On a side note, changing the "Volume ID:" ie "Label" in IMGBURN is not a good idea coz although you get successful burns, those same images dont verify again in abgx360. So not a good idea guys. ImgBurn.log

No, it was actually with c4e firmware but with normal sized img (XGD2) 7.29 GB (7,838,695,424 bytes) not (XGD3) 8.13 GB (8,738,846,720 bytes) so no overburn comes into play.

I was thinking the same thing, it was made a big thing of the fact that Liteon iHAS with custom firmware can give no errors for XGD3 (Overburnt MKM003) but was the custom firmware fully tested with XGD2 (normally burnt MKM003) which is where im having issues at the moment? It's kinda crappy, the idea of having to have 2 (My old Pioneer for XGD2 burns & Liteon iHAS for XGD3 burns) seperate RW drives in my setup until all releases are XGD3 (Overburnt MKM003) only. I currently have a TSSTcorp DVD-ROM SH-D163B SB01 in the other slot in my PC Anyway, ive attached an image of a successful burnt disc using imgburn OPC on, x4 speed, mkm003 singapore verb, same Liteon iHAS624 B drive.

Ok, just for the record, i know its not a scan of an overburnt disc...... it was a failed XGD2 (No overburn needed) burnt disc (failed to verify at 88%, got L-EC Uncontrollable Errors so i just pushed the stop button) then ran it through ODC and this is what i got? and #2 they are MKM-003 Verbs from Singapore i use and the only ones i use/used and havnt had any problems till installing this new Liteon iHAS624B drive combined with using c4e custom firmware. and #3 i was aware of ODC v1.51 is out.... (but couldnt find a cracked version, lol) I know, in theory all u should have to do is burn at 4x and turn OPC on. (which is what my settings are) but the failed Verify's tell a differnet story for the Liteon iHAS624B? hmmm yeah im sceptical bout the OPC thing as well, thats the only difference to the settings i made when going from my old pioneer (which had no failed verify's) to this new Liteon iHAS. I'll run a successfully burnt disc thru OPC and post a pic of results for comparison.

Ive attached a pic of Disc Quality with Opti Drive Control, but discs arent issue? or are? i dont know what to make of all this jargon? can you shed some light? all i know is the red graph seems to me to be a bad sign? lol