ImgBurn 2.3.1 released

[blutach]

Here's the changelog:

• Added: 'Reset Settings' feature to the 'Options' tab in 'Build' mode.
• Added: 'Read' support for discs (DVDRAM etc) formatted with the FAT16/32 file system.
• Changed: Optimised the file system parsing code.
• Changed: Set default write buffer size to 40MB for people with 1GB of RAM or more (actually set at 980MB rather than 1GB this time).
• Changed: Set default path for IBG files to [APPDATA]\ImgBurn\IBG Files.
• Changed: Set default path for LOG files to [APPDATA]\ImgBurn\Log Files.
• Changed: The little 'DVDInfoPro' icon to the latest one - as taken from the program's exe.
• Changed: Upgraded to NSIS v2.25.
• Changed: Some internal workings of the 'Check For Program Updates' code.
• Fixed: Access Violation error when doing an 'on the fly' DL burn in Build mode.
• Fixed: DVDRAM discs formatted with FAT32 were always seen as 'empty' and so no 'overwrite' prompt was displayed if you tried to write to them.
• Fixed: Old drives that don't report the track mode correctly in the TOC could then read normal Mode1/2048 discs to a Mode1/2352 image.
• Fixed: Problem using numeric keypad to enter a custom number for 'sectors' in Discovery mode.
• Fixed: The layer break preview application wasn't working correctly under win 9x (Problems in the CreateProcess/ShellExecute wrappers).
• Fixed: The stars in the 'Select/Create Layer Break Position' window's list showed some odd graphics corruption under Win9x.
• Fixed: UDF file system parsing code could get stuck in a loop.

Download it here: http://www.imgburn.com/

Thanks LUK!

Regards

[locoeng]

That was quick...

[Chewy]

an 'on the fly' DL burn in Build mode.

I don't think I would test this part

[soup]

I think I might, thanks for the heads up blutach & thank you LUK.

[locoeng]

I don't think I would test this part

Where is your sense of adventure?

[Zero G]

Thanks LUK!!!

[Chewy]

Where is your sense of adventure?

well from the burns I have seen on dl media I can't imagine true "on the fly"
copying

guess at 2.4x it might work

8x would be what I would want to test

[locoeng]

The only DL's I have are MKM001's or 2.4X...may have to give it a shot. Now to find a flick worthy of wasting..er I mean testing this feature out on.

[LIGHTNING UK!]

If you can build an image at > 8x, there's no reason on-the-fly @ 8x wouldn't work.

Write mode just reads data from a buffer and sends it to the drive. It doesn't matter if the data in that buffer is from an image on the hdd or it's the 'virtual' image that the 'Build' code is creating.

It's not like a DL build would ever be made up of loads of little files (where access times may become an issue) - because movies just aren't like that, the files are mainly great big 1GB things!

[Chewy]

LUK,
we are talking reading from one dual layer dvd disk directly to another?

Right?

[zaveon]

thanks LUK...

[LIGHTNING UK!]

Erm... I wasn't, no.

By 'on the fly' I simply meant going from hdd VIDEO_TS file to a DVD+R DL disc, without an intermediate ISO file.

That is to say, the 'Output' option is set to 'Device' rather than 'Image File'.

[blutach]

I have done may DL burns this way and it is entirely safe using the 2.4X MKM001 media I have.

Regards

[2COOL]

Thanks LUK! I'll check it out when I get home from work.

[Dan]

Excellent! Thanks LUK!