#1 Burning Software

Hi,

I have tested the UDF import feature (in StarBurn V11) and I have observed (not as soon as I would have liked) that the imported files have the correct size but the content is wrong. Most of the files have nothing in them, some from the upper directory levels have the correct content, and some have contain

which seems to be a part of the file system structure.

I have tested this on several computers using different burners.
I have used UDF2BuildBurn and UDF2ImportBurn samples to be sure that the problem is not in my code.
If you need additional info I will be glad to provide it.

Stuff works fine here. Please update to the most recent build initially. If the problem will be still there please provide more info.

I have just downloaded and used version 20090101.
The same problem can be reproduced. I have observed that the import works fine for DVD-RW discs but fails for DVD+RW and BR-RE discs.
The testing sequence is quite simple.
1. Burn a folder containing a few files using UDF2 onto a DVD+RW disc
2. Import the session from 1. and burn a few more files.
The files added at step 2. are ok but most of the files from session 1. are empty (the size is correct).

I will send you an email with the debug output and the sample folder I have used for testing.

Got it and your e-mail with the attachments. Please give us some time to take a closer look. Thank you!

OK, the problem was rather non in the content itself but in small file sizes... It appeared we don't handle very small volume sizes well (overlapping). I've fixed this so Andrew will run few more tests on Monday and will issue you with a new build. Sorry for this and thank you very much for cooperation!

Hello,

Updated binaries you can download by this link:
link was removed

I have tested the new build and it seems to works fine.
Thank you for your prompt replies and the quick fix.

Good

...and sorry for being such a pain in the <censored> We'll try to provide better service in the future.

I am using V11 from 20090202.

It seems that there is a problem with the StarBurn_UDF2_FileDirectoryDateTimeSet function when the STARBURN_UDF2_FILE_DATE_TIME parameter has the Offset member set to a value different than 0.
All the files/folders added to the UDF2 image have an invalid date/time. No modified date is displayed in Windows Explorer and GetFileTime returns -1.

In your example this happens only when the Daylight saving time is active because the conversion is not correct.
I think that the correct conversion from TIME_ZONE_INFORMATION Bias to STARBURN_UDF2_FILE_DATE_TIME offset is

STARBURN_UDF2_FILE_DATE_TIME.Offset = TIME_ZONE_INFORMATION.Bias;
if TIME_ZONE_ID_STANDARD
STARBURN_UDF2_FILE_DATE_TIME.Offset := STARBURN_UDF2_FILE_DATE_TIME.Offset + TIME_ZONE_INFORMATION.StandardBias;
else if TIME_ZONE_ID_DAYLIGHT
STARBURN_UDF2_FILE_DATE_TIME.Offset := STARBURN_UDF2_FILE_DATE_TIME.Offset + TIME_ZONE_INFORMATION.DaylightBias;



The outputdebugstring for the StarBurn_UDF2_FileDirectoryDateTimeSet call

NapalmBurn:NapalmBurn_UdfFileUnicodeCreate(): EXITing with success Process Backup4all.exe (1792)
NapalmBurn:NapalmBurn_UdfFileDirectoryDateTimeSet(): ENTERed for 0x06790408, 0x065FF9FE Process Backup4all.exe (1792)
CNapalm_UdfFile::DateTimeSet(): ENTERed 0x065FF9FE Process Backup4all.exe (1792)
CNapalm_UdfFile::DateTimeSet(): EXITing with success Process Backup4all.exe (1792)
NapalmBurn:NapalmBurn_UdfFileDirectoryDateTimeSet(): EXITing with success Process Backup4all.exe (1792)


Also this version of Starburn.DLL needs msvcr90.dll which is not available on all systems.

A message box is displayed saying that the DLL is not found. This happens only the Starburn.DLL is loaded.

My guess (i'm not ussualy programming in C++) is that you are using the /MTD (dependencies linked dynamically) directive instead of /MT.

We don't use MS VC to build the DLL.