Why are my YUDEN000 T02's Burning Horribly w/my 851@832 (CG4E) burner?

vbimport
#1

Hmmmm, I wish my first post could’ve been a happier one, but…

I have been burning DVD-R’s only (MXL RG02, RITEKG04, and ummm…LEADDATA01) for the past couple months using VS0E with acceptable results, then decided to flash to CG4E b/c of all the hype (and b/c Code King rocks!!) and also b/c I wanted less PI/PIFs.

So I got my hands on a batch of Taiyo Yuden 8x +R discs, and needless to say, they were terrible. I thought DVD+R’s were friendlier to the Lite-On 832 too?? MY RITEKG04’s (4x, -R) fared much better than my YUDEN000 T02’s (8x, +R). I even cleared the EEPROM with the Code Guys’ utility before burning them. Here are the results…

The first scan is of a RITEKG04 (burn @ 4x), 2nd burnt disc after EEPROM was reset.

Several discs later, I tried burning a YUDEN000 T02 @ 8x. My other YUDEN000 T02 burns look almost exactly the same (so I didn’t bother putting them up), whether they’re burnt @ 8x, 6x, or 4x. Yes, ugly scan, but somehow it manages to play in my standalone DVD player flawlessly.

I don’t understand and also envy those of you who get burns w/averages around 5-10PI/1-2 PIFs. WTF am I doing wrong?!?!? It’s driving me crazy!!! :a

Any help would be appreciated! :iagree:

#2

What brand are the TY discs?

There are quite some fake media on the market with TY media code…

#3

here’s the media code for mine
i have the same burner with the same firmware, like yours. I’m averaging about 10PI

Media Information
Disc Regions are 1,2,3,4,5,6,7,8
Media code/Manufacturer ID YUDEN000T02
Media Product Revision Number 00h
Format Type UDF 1.02
Volume Name WITHOUTAPADDLE
Application id
Implementation id DVD Shrink
Recording Date/Time (mm/dd/yyyy) 1/24/2005 12:27:28
Format Capacity 4.36GB(4.68GB)
Book Type DVD-ROM
Media Type DVD+R
Manufacturer Rated Speed 8.0x 11080KBps
Data area starting sector 30000h
Data area end sector 22E12Fh
Linear Density 0.267um/bit
Track Density 0.74um/track
Number of Layers 1

                       Complete Media Code

00000000 08 02 00 00 01 0F 01 00 00 03 00 00 00 25 E1 2F …%./
00000010 00 00 00 00 00 00 03 59 55 44 45 4E 30 30 30 54 …YUDEN000T
00000020 30 32 00 38 23 54 37 10 02 4E 72 02 8C 63 16 16 02.8#T7…Nr…c…
00000030 0B 0B 0A 0A 01 19 1B 0C 0C 0C 0D 01 00 00 00 00 …

compare the media code with your disc

#4

@K-Dizzle
Welcome to cdfreaks :slight_smile:

Good first post. Thanks for your comments.

Unfortunately some 851S’ do not read properly when flashed to 832S firmware. You may be unlucky enough to have one of these drives. Try flashing back to GS0F (you can get it from my site) and then rescan the above discs or burn a new disc and see how it comes out. If this is better you can then work your way up to other firmware. You may find that 812S firmware works ok in your drive and then the only thing you won’t have is Dual Layer burning. If you do try 812S firmware, make sure you try US0N before US0Q.

#5

OC-Freak,

I knew I forgot something in my post…the TY’s are the infamous Fuji-branded ones I picked up from the local Fry’s over the weekend.
:confused:

#6

Code King,

Thanks for the welcome. This is the first time I’ve heard of crossflashing a 851 to an 812. Was it only mentioned for my compatability reasons?

If my 851 is having those scanning problems you mentioned and if my scans come back ok/excellent when using GS0F, then can it be assumed that my “bad” burns using 832 firmware (GS0E or CG4E) are actually ok and that I can continue to burn using 832 firmware even if my scans continue to come out bad?

#7

Yes. At one time, when the 832S firmware was new, we actually recommended people use the 812S firmware, as the only real gain with 832S frimware was DL burning. Just use OmniPatcher to enable crossflashing on the unscrambled version.

If my 851 is having those scanning problems you mentioned and if my scans come back ok/excellent when using GS0F, then can it be assumed that my “bad” burns using 832 firmware (GS0E or CG4E) are actually ok and that I can continue to burn using 832 firmware even if my scans continue to come out bad?

You can but you may also have problems reading data DVDs and Video DVDs. It’s unlikely to just be the PI/PIF reporting that’s at fault.

#8

@CodeKing

I reverted back to GS0F from CG4E, and here are my scan results. They’re about the same as when I scanned with CG4E. These discs were burned w/CG4E, BTW. Both CD-Speed and K-Probe scans looks the same. :Z

In my CD-Speed scan, what’s wrong with the Disc Info ID? It appears fine in K-Probe. Also, why does my Lite-On only read at 2.4x (also read @2.4x in K-Probe) instead of 4x? Weird…

It’s getting late - I’ll try to flash to 812 tomorrow and see what happens… :frowning:


YUDEN000T02 (Read with GS0F).PNG572x672 6.75 KB

#9

The good news is you can rule out the reading problem. So you should be able to use 832S firmware. :slight_smile:

Ahh 2.4x, sounds like your DMA is disabled. Check your DMA setting in device manager…

#10

I’d also suggest once you get the DMA issues squared away and burn a disc, if the PI Errors and such are still sky-rocketing high to just try to play back a disc in a stand-alone and see if it plays. It could just be your drive isn’t reading as well for PI/PO testing and that is where part of high scans could be coming from. Just a suggestion though. :slight_smile:

#11

@Codeking
@Braxas

It wasn’t a DMA problem - I have the drive enabled at Ultra DMA Mode 2.

Well, here’s a scan of a data disc I burnt with VGS0F - still no luck. The scan is still terrible. Ignore the two spikes in the beginning of the scan - I was messing around w/the Device Manager there during the burn. :wink:

Is there any reason to try out the 812S firmware on my drive or can I just go back to 832 using CG4E? I’m still stumped…