New Pioneer 107D - burned at 8x!

[JohnnyCNote]

I just got my Pioneer 107D today from Newegg.com, installed it and had it up and running in about 15 minutes. Nero 6.whatever (the latest update) worked with it just fine.

I first tried a CompUSA (Ricoh) +R and burned at 2.4x. Then I flashed it with the hacked firmware from the The Firmware Page and tried an Imation -R. It burned at 8x with completely successful results!

So you could say I'm very pleased with my new drive....

[jeex]

i'm cool with 4x burning on my 106d until dual layer is reasonable.. i'm kinda glad the new flock of 8x burners is in full force, hopefully it will drive down the price of 4x media.. although i'm sure it wont concern you, since you're using a hacked firmware..

dual layer is at though.. perfect 1:1 copies..

[tompika]

Congrats

[JohnnyCNote]

I'd have waited 'til the dual layers came out, but I have a buyer for my Sony DRU-500, so I went ahead and got the Pioneer. Also, I need to make a correction to my original post: I got the 8x results from a TDK 2x disk! I just did another. I'm happy with that.

Tompika - köszönöm!

[jeex]

are you using a TY 2x TDK disc? i've heard some of the TDK's areCrapMcCrap

[JohnnyCNote]

Here's what DVDINFOPro says:

Media code/Manufacturer ID TDKG02000000

00000000 00 42 00 00 01 40 C1 FD 9E D8 50 00 02 98 0C 13 .B...@....P.....
00000010 76 78 80 00 03 54 44 4B 47 30 32 00 04 30 30 30 vx...TDKG02..000
00000020 30 30 30 00 05 88 80 00 00 00 01 00 00 00 00 00 000.............

[neoplex]

Wow!

media code TDKG02 is code-jacked Princo 2x... or CMC 2x... or whoever the hell made those TDK discs.

I own a NEC ND-2500A... the TDKG02's are for crap in my drive.

Running 8x on MCC and TY's (of course) and 6X on Ricoh +R's...

--neoplex

[tompika]

Wow!

media code TDKG02 is code-jacked Princo 2x... or CMC 2x... or whoever the hell made those TDK discs.

these "TDK" TDK's got good responses

https://www.videohelp.com/dvdmedia.php?selectmedia=7#comments

[JohnnyCNote]

Are you saying I should add my results to the Media database?

[tompika]

Are you saying I should add my results to the Media database?

As an active member of this forum you ought to .... after some more testing

[JohnnyCNote]

Consider it done - after some more testing.

I should add that it's much easier to flash than the Sony, which required turning off DMA, etc. Also, the Pioneer is nearly silent, which is amazing considering it's a lot faster. So far I'm very favorably impressed....

[FMercury]

Hi

I have 1 DRU500A too, and make a great bussiness sell it and buy a 107 and now i burn this PRIMEDISK at 8x

00000000 00 42 00 00 01 40 C1 FD 9E D8 50 00 02 77 0E 0B .B...@....P..w..
00000010 FE FF 80 00 03 52 49 54 45 4B 47 00 04 30 33 00 .....RITEKG..03.
00000020 00 00 00 00 05 88 80 00 00 00 01 00 00 00 00 00 ................

Is a great burner...

[JohnnyCNote]

I upgraded to ver. 1.10 firmware and now I can burn the Imations, but lost the 8x. I'm going to leave it that way for now until I use up the Imations, then I'll see if there's any newer firmware. At least I know it has the potential of 8X....

[fsh42na]

Can someone provide a Step by Step idiot's guide to flashing my 107? I've downloaded various official and hacked firmware for it, but I'm really abit nervous about destroying my drive.

[JohnnyCNote]

Try this:

Using DVRFlash on Windows platforms


[General Notes]

Pioneer DVR drives usually require 2 firmware files for flashing. One is
called the kernel and the other the normal part (or general part).
If you are not converting an OEM drive to a true Pioneer, or if you are
simply applying a patched firmware, you don't necessarily need to provide
a kernel, so don't panic if you have only one firmware file.
In the following command samples, we will assume that both files are used.
Also, if you do have a kernel file, you should know that its revision does
not need to match the normal part revision. For instance, you can use a
1.05 kernel with a 1.07 normal part.

And once and for all, don't play it more stupid than you are!
If you are worried, you probably shouldn't because people who publish the
firmwares do everything they can to provide you with exactly what you need.

In short, flashing a firmware is not the end of the world, and it is not a
license for bothering busy people with questions on how to use the flashing
tools, the files you need, or how to actually use your Operating System...

Besides, DVRFlash is pretty much bulletproof and what's more, Pioneer did
such a good job with their DVR drives that you are very unlikely to kill
one, even if you have no clue what you are doing.

If you are still unsure or worried, why don't you:
1/ Do a SEARCH at http://forum.rpc1.org
You will find that your question has probably already been ANSWERED.
2/ Give DVRFlash a try. DVRFlash will always try to help you about what
you might be doing wrong.
3/ If all of the above fails, then, AND ONLY THEN, you can try to post in
the forum with RELEVANT INFORMATION about what you are trying to do and
how you are trying to do it.

But I have to repeat; the information is already out there.
The only difference is that smart people always know how to find it...

In the following samples, the kernel firmware is 'R5100004.133' and the
normal firmware is 'R5100104.133'. You will need to change those names
according to the firmwares you downloaded.
You can input these firmwares in any order you like as DVRFlash will
recognize them automatically.


[NT/2k/XP/2k3]

You don't have to install anything special. Just open a DOS Window and run
a command like:

DVRFlash -vf I: R5100004.133 R5100104.133

In this case 'I:' is the DVR drive letter.
The command above will force flash a 105 compatible drive (in I with the
Pioneer DVR-105 v1.33 firmware
The command above also works with USB/Firewire drives


[Win9x/WinMe]

First, you need to have Adaptec ASPI32 v4.60 installed.
Then you need to figure out the SCSI ID of your drive. To do that, just try
something like the following until you find your drive:

DVRFlash -v 1.0.0
DVRFlash -v 1.1.0
...
DVRFlash -v 2.0.0
etc.

Alternatively, you can download the win32 version of cdrecord and run:
cdrecord -scanbus
This will list all your devices SCSI ID (the x.y.z thing).
Once you have the SCSI ID, enter the command:

DVRFlash -vf x.y.z R5100004.133 R5100104.133

Where x.y.z is the SCSI ID you found above

Note that you can also use the SCSI ID on an NT/2k/XP/2k3 platform if you have
ASPI32 installed.

[fsh42na]

johnny,

thanks a bunch for the info and for not making me feel like too much of an idiot for not having found it myself.

[JohnnyCNote]

No prob! This site can be a bit overwhelming to the newcomer, just as burning DVD's can be, too....