Ahead releases changelog for Nero Burning ROM 6.3.0.2

31 Dec 03 12:36 by Liggy in category Uncategorized

Print this page

R!Co used our news submit to tell us that Ahead has released a changelog for their latest Nero Burning ROM 6.3.0.2.

alt="Nero Burning ROM" hspace=18
src="http://www.cdfreaks.com/contentimages/newsimages/1251946488" align=right border=0
>Bugfixes:

Nero Burning ROM / Nero Express

Prevent Nero Burning ROM / NeroExpress from closing when it is currently burning has been fixed
The pause settings of Video CD and Super Video CD compilation was not taken into account in some circumstances has been fixed

Nero Burning ROM

Fixed incorrect handling of DVD-Video burn process

Nero Express

Burning a second image on a CDRW fails with NeroExpress has been fixed
Layout reorganization problems when using the Japanese language has been fixed
Painting problem in the page that appears at the end of the burn process has been fixed

Nero StartSmart

When inserting a DVD-Video under Windows XP, auto play brings up an option for Nero StartSmart when it should not. This has been fixed
German text is now completed for Nero StartSmart
Corrected DVD-Video autoplay handler in case no application is available to handle playback

Nero ImageDrive

Improved driver stability under Windows 2000 and XP

Only a few minor changes this time but probably reason enough for upgrading your Nero installation.

Feel free to discuss this update
in our Nero & InCD Forum.

Source: Ahead.de

5 Comments on Ahead releases changelog for Nero Burning ROM 6.3.0.2

Rhelic: Posts: 302; Posted on: 31 Dec 03 15:45

A changelog released within 24hrs? That's a record for Ahead, perhaps they'll take the next step and just release a whatsnew.txt with their software!

SamuriHL: Posts: 2900; Posted on: 31 Dec 03 19:33

Minor changes?! I consider the fact that 6.3.0.0 included an Image Drive version that completely blew up windows to be more than a minor change.

I guess that's just my opinion. In any case, I've yet to try the new Image Drive, but, according to several people it's been fixed. Good job to Ahead on getting this out in a fairly timely fashion.