We all know that DVD/CD writer can get more function and improve
the quality of burning by updating it firmware.
NEC ND-3550A is an old model DVD writer. And it also is popular in
the market. NEC ND-4551A is an upgraded model of ND-3550A.
The difference between these two models is newer model support
DVD-RAM burning and LabelFlash. In my point of view, it is not
worthwhile to buy a new model (ND4551A) just for DVD-RAM supported.
There is a way to upgrade your NEC ND-3550A to ND4551A by
updating the firmware in just few steps.
Step 1, First, you need to download modified ND-4551A firmware,
Flash Utility and bootcode Flasher. These are 3 main programs.
Uncompress them to a same folder. They can be downloaded from
Step 2, run CMD (Command Prompt) in Windows XP. Change to the
folder which created in Step 1.
Step 3, Run necbfl, enter your DVD-ROM path (eg. E: is the DVD-ROM
drive, the path should be like this \\.\e:)
Step 4, Choose 2 (upgrade to ND-4550A) or choose 3 (upgrade to ND-4551A);
Then press Y. Upgrade process will be run.
Step 5, Please reboot your computer after the process finished.
Step 6, You will see that the status light of the DVD-ROM is flashing.
Don’t worry, this is normal. Run binflahs; then click on Flash.
Step 7, reboot your PC; Done.
Please notice, the warrantee of your DVD-ROM will be violated
after you flash in the firmware. Take your own risk.
Welcome to AstaHost - Dear Guest , Please Register here to get Your own website. - Ask a Question / Express Opinion / Reply w/o Sign-Up!
Update Your Nec Dvd Burner Fireware To Get Dvd-ram Supported
1 reply to this topic
Posted 22 July 2009 - 02:41 AM
Flashing ProblemUpdate Your Nec Dvd Burner Fireware To Get Dvd-ram SupportedI've run Necbfl.Exe up to line 6: on the instructions. My old NEC 3550 shows up on the bios & Windows as NEC 4551 with the from LED constantly flashing.When I try to run Binflash in DOS the write the new Firmware on the device it tells me SCSI error and does nothing else. I have also tried this process in Windows but binflash shut down automatically no matter what PC I try this on.What am I doing incorrect or what can be done to current the device current state?-question by Daniel
Reply to this topic
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users