I also have installed SP2 but don't receive a "buffer overrun detected". I made a picture of the DOS screen as I get it.

I have been able to burn a Platinum 8X (RICOH JPN R02) at 12X, it took 7min 21sec, I guess I could use some more DDRAM cause my buffer gets a bit unstable when he starts 12X.
I have a kprobe scan and it seems the crappy platinum dvd+r isn't made for more then 8X.

Nope. I run SP1 and get the same error. So it's not SP2 related.

You can get it here http://club.cdfreaks.com/showthread.php?t=105698

I used it this morning and didn't have any problems. I'm on an Athlon 64 3000+, 2510A, XP Pro SP2 slipstreamed. I put on the hacked HP firmware that someone in this forum posted(and they ROCK for doing so might I add!) and had absolutely no problem. I did a scan right before I flashed it. Worked VERY well and I'm most pleased with it.

Doh! I hate those kinds of bugs. I'm a C++ developer myself so I can relate to that kind of nastiness. Good work in finding it so quickly. And thanks for a kick ass tool!!

What hacked HP version are you referring to? Herrie's 107v2b5 for the 25x0 series or ??

It was easy to find since I had someone with the same error and could add some debugging code to the scan routine. (Actually some output for -v at all)

The scanning error should be gone now. I updated all three versions on the server now. Furthermore there's some additional output when using the -v switch to scan for devices.

I can't find the link in this forum at the moment, but, here's the info from the readme:

NEC ND-2510A DVD+/-/R/RW/DL

File name: 2510A221.bin 24.06.2004 /23:50
FIRMWARE (FW)version 2.21 by DVD_Boost

This is not an original NEC FW !
This is a firmware, based on HP520n v.2.21 (2500R221 @ http://tdb.rpc1.org)
This FW can be used to upgrade a ND-2510A v.2.15 to v.2.21.The device keeps it's original functionality (also DL).

Advantages of this FW:

- The drive shows itself as correct ND-2510A device at any application
- Rip lock
- RPC1
- Bitsetting are allowed, using DVDInfoPro, to set a DVD+ media as DVD-RAM

The application, used to upload this FW to the device is NEC2x00A.exe (TDB http://tdb.rpc1.org/)
Please, use DOS with this application!

The file 2510A221.bin can be found at:
http://home.no/dvdboost/NEC_2510A

The author does not have any responsibility if a device damage occures during flashing procedure.
Using this FW may avoid waranty of the device on eventual RMA.

This firmware truly rocks, IMO. My drive shows up as a 2510a except in the bios(who cares) and allows me to bit set SL discs. And it can still do DL discs as far as I know(haven't tried). It does not have the write strategy for the Ritek DL disc, though, so, for that we still need Herrie's hacked 2.16 FW.

That's always good. I like developers that think about how to debug when things go wrong...before they go wrong. Nice work!

thanks liggy, the scanning error is gone now.

@SamuriHL
Thanks!

I even have a debug build with an option '-d' that dumps a little bit more data, but which output is not compatible with common binfiles. This way I'm able to read some additional information.
I'm currently looking at a way to modify the +R(W)-only drives to make them dual format
Should not be impossible to modify one byte

VERY nice! That's awesome!! Good luck on that one!

Wonderful program Liggy! Being that this is a beta, could I make a suggestion?

Make the syntax comparable to other *nix utilities.

Currently:

Usage:
necflash {-dump} [-s] {filename} {device}
necflash {-flash} [-v] [-s] {filename} {device}
necflash {-scan} [-v]

-dump - Dump firmware and write to file
-flash - Flash firmware and write to file
-scan - Scan for supported devices

-v - Verbose mode
-s - Skip disclaimer

Suggested:

Usage:
necflash {-d[s]} {device} {dest filename}
necflash {-f[v][s]} {device} {source filename}
necflash {-df[v][s]} {device} {source filename} {dest filename}
necflash {-x[v]}

-d, --dump - Dump firmware and write to file
-f, --flash - Flash firmware and write to file
-x, --scan - Scan for supported devices

-v, --verbose - Verbose mode
-s, --skip - Skip disclaimer

My reason for this suggestion is to make it much easier to write scripts to use the utility as well as make it intuitive to those already familiar with Unix/Linux.

Ive got a NEC 2500A and I dumped my firmware, the file was .97 megabytes... that doesn't seem to be what it should right?

Size: 1,024,004
Size on Disc: 1,028,096

Can anyone steer me towards a firmware to flash too

So... whens the GUI?

j/k this is cool enough as is

On the other hand I might just try my hand at a GUI in VB (there was a guide in Maximum PC this month)

1,024,004 is the perfect filesize, when dumping a firmware :-)

Sorry, I can't use -d since this one is already used for debug mode. Don't try testing it with your versions, I have to generate a special debug build for this. I had to rewrite my commandline interface with the risk of introducing new errors. It shouldn't be too difficult to integrate it with scripts the way it currently works

Everyone is free to build a working GUI for this program and give me the sourcecode so I can build a GUI version. But I need a C(++) sourcefile for integration - no VB and it will probably only work with Windows - not Linux and Mac.

TDB has also made a windows flasher for 2.17.

The one on there site is for TDK1616N 2.77 firmware, and doesn't see the ND-3500A

TDB made a (beta) windows flasher for the TDK 2.77. I can't find a NEC-3500A 2.17 flasher on their site.