Two days ago, I planed to update the firmware from BS0H to BS0K because I thought BS0K shall be better and it only looked a bit better than BS0H. I was not satisfied with the result so I decide to use the Ominipatcher to do some tweaks on the BS0K and hopefully it would improve the PIPO. I read the forum and some guys used this tweak to produce very impressive PIPO result with certain medias.
Although the result I got from the 1633S is good and naturally I want the lowest PIPO it can get. I guess I screwed up my drive after patchedâ€¦ :a Here it was how I done; I loaded Ominipatcher v1.3…15 with BS0K and checked the â€™Increase DVD+R/-R/R9/RW reading speed to 12x.â€™ and â€˜Enable auto-bitsettingâ€™ and also â€˜fix the â€œdead drive blinkâ€ / Enable cross flashingâ€™. I selected Daxon AZ2, MCC03 & CMC MAG E01 and applied their speed at 4x, 6x, 8x &12X.( Iâ€™m now still not sure if I applied them correctly… ) After I save the bin file and loaded with LtnFW and burnt the firmware. One weird thing I found at LtnFW; when chose â€˜updateâ€™ the BS0k and it stared. Immediate it showed 100% on the bar but words still said in programming. I could see the LED of the drive blinked. After a while, the LED stopped blinking but it still said in programming. Does anyone encounter this problem before? I waited 10min and rebooted my PC. It looks fine to me after windows started.
I used the Neroâ€™s â€˜create data discâ€™ to burnt the BenQ DVD+R 8x and read it after burnt. I got a nasty surprise, there is a big spike after about 2.7G toward 3.7G. :a I used Kprobe to scanned also and got the same result. â€˜Oh man, here goes one pc of dead disc!(fish)â€™ I said. Later I decide to use the EEPROM utility to reset the â€˜learnt mediaâ€™. Hopefully it will reset back where it was. Again, I generated a data disc and read its PIPO. The result seems no change and the spike was still there. Immediate I reflashed the BS0H and generated a data disc from Nero again. When read again, it showed a spike too. The funny thing was the spike at almost the same place as the 1st read.(Generate by Ominipatcher).
The next step I did was went back to the original driveâ€™s firmware version; BS0C and generated a data disc to read its PIPO. The result even worse than the other two; 2 big spikes.(please look at the attached pictures)
I spent over a dozen of discs to repeat the testing in binary & windows formats. All the result I got were bad; all got spikes! Iâ€™m not sure where or what did it go wrong. :a I need some fresh ideas, please advise. Thank you. (I guess Iâ€™ll burnt more discs soon. )
The arrangement of the pictures;
- BS0H; without any tweaks and patches
- BS0K; no patch
- BS0K; patched, reset and reburnt
- BS0H; patched, reset and reburnt
- BS0C; patched, reset and reburnt
** For some reason I couldn’t upload the images. It said “not a valid image”. I have tried a few time but not successfully upload! I also tried to reduce the pictures size but no help. Not sure why… :a
OC-Freak, can I send you an attached files and help me post the image?