Jump to content

Recommended Posts

Posted (edited)

Yet another Super Smash Brothers Brawl topic >_<

 

I use 8x DVD+R DL media from Verbatim. Media code is MKM-003-00 (can't seem to get hold of 001's). I burn at 2.4 speed (although this line is in the log: I 18:26:26 Average Write Rate: 3.134 KB/s (2.3x) - Maximum Write Rate: 4.201 KB/s (3.0x)). I used the latest version of ImageBurn and set the layer break to 2084960.

My writer is a rather old (but good) Nec ND-2510A. Firmware is v2.19, which I believe is the very latest.

Everything went fine until I reached about 40% then an error appeared (see below please). Looking at the disc it was written to until about 5mm from the edge, so I'm guessing it choked at the layer break?

 

Can anyone offer further advise on this?:)

 

many thanks,

 

Jeroen

 

 

 

I 17:59:37 ImgBurn Version 2.4.4.0 started!

I 17:59:37 Microsoft Windows XP Professional (5.1, Build 2600 : Service Pack 3)

I 17:59:37 Total Physical Memory: 523.764 KB - Available: 62.276 KB

I 17:59:37 Initialising SPTI...

I 17:59:37 Searching for SCSI / ATAPI devices...

I 17:59:37 Found 1 DVD

Edited by Jeroen1000
Posted

Your burner is old and was good...you can replace it with a modern drive for $20-$30. I'm actually surprised that burner even recognized those discs.....old burner + new media = coasters

Posted

I just dumped its firmware and you are quite right. Only following are supported DL media:

 

0x30 0x30 0x30 0x30 0x30 0x30 0x30 0x30 0x30 0x30 0x30 0x00 0x00 0x00  [00000000000  ] ->  
0x30 0x30 0x30 0x30 0x30 0x30 0x30 0x30 0x30 0x30 0x30 0x00 0x00 0x00  [00000000000  ] ->  
[b]0x4D 0x4B 0x4D 0x00 0x00 0x00 0x00 0x00 0x30 0x30 0x31 0x00 0x01 0x00  [MKM	 001  ] ->  2.4x [/b]
0x30 0x30 0x30 0x30 0x30 0x30 0x30 0x30 0x30 0x30 0x30 0x00 0x01 0x00  [00000000000  ] ->  2.4x 
0x52 0x49 0x43 0x4F 0x48 0x4A 0x50 0x4E 0x52 0x30 0x30 0x01 0x01 0x00  [RICOHJPNR00  ] ->  2.4x 
0x52 0x49 0x43 0x4F 0x48 0x4A 0x50 0x4E 0x44 0x30 0x30 0x01 0x01 0x00  [RICOHJPND00  ] ->  2.4x 
0x30 0x30 0x30 0x30 0x30 0x30 0x30 0x30 0x30 0x30 0x30 0x00 0x01 0x00  [00000000000  ] ->  2.4x 
0x52 0x49 0x54 0x45 0x4B 0x00 0x00 0x00 0x44 0x30 0x31 0x01 0x01 0x00  [RITEK   D01  ] ->  2.4x 
0x30 0x30 0x30 0x30 0x30 0x30 0x30 0x30 0x30 0x30 0x30 0x00 0x01 0x00  [00000000000  ] ->  2.4x 
0x50 0x48 0x49 0x4C 0x49 0x50 0x53 0x00 0x43 0x44 0x32 0x00 0x01 0x00  [PHILIPS CD2  ] ->  2.4x 
0x43 0x4D 0x43 0x20 0x4D 0x41 0x47 0x00 0x44 0x30 0x31 0x00 0x01 0x00  [CMC MAG D01  ] ->  2.4x 
0x30 0x30 0x30 0x30 0x30 0x30 0x30 0x30 0x30 0x30 0x30 0x00 0x01 0x00  [00000000000  ] ->  2.4x 
0x30 0x30 0x30 0x30 0x30 0x30 0x30 0x30 0x30 0x30 0x30 0x00 0x01 0x00  [00000000000  ] ->  2.4x

 

Luckily, I anticipated this and bought myself a Pioneer 215D as it seems to be the very best drive out there for burning DL media. Too bad it is beige :mellow:

Posted

Theres nothing spray paint cant handle =) remember to lacker it after before using it to seal the paint. Also just spay the tray and facing otherwise it will cease. That what i would do hehe =)

Posted

Yeah - the 2.4x speed on those 003's was a dead giveaway. Still, the drive should be buried with honour, if it has lasted so long.

 

Regards

Posted (edited)
Theres nothing spray paint cant handle =) remember to lacker it after before using it to seal the paint. Also just spay the tray and facing otherwise it will cease. That what i would do hehe =)

 

Great tip. On my ND-2510, I managed to get the facia off (after I figured out the tray had to be left open before removing the drive from the computer).

Then I clicked the tray's front off (you know the thing which usually has some writing on it regarding the drive's abilities).

If I can manage this on the Pioneer I'll know what to do on my day off tomorrow :thumbup:

 

Hi Blutach,

 

I'm donating the entire computer with drive to my dad. Since he burns about 2 discs a year it may very well last a lifetime:)

 

Thanks to all for helping me out here!

Edited by Jeroen1000
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.