I am specifying FILE_TIME_LAST_WRITE when adding files to a File Tree ( by calling StarBurn_ISO9660JolietFileTree_Add ). Then burning the tree to the disk. This works just fine.
When I view the newly created disk, the Time Stamp on the disk lags by 11 hours compared to the time stamp of the original file.
For example:
Directory of D:\ (THIS IS THE CD)
03/14/2006
08:17p 393,216 441813f5.bkm
Directory of C:\optical.tmp (THIS IS THE HARD DRIVE)
03/15/2006 07:26a <DIR> .
03/15/2006 07:26a <DIR> ..
03/15/2006
07:17a 393,216 441813f5.bkm
Code Fragment wrote:
l__EXCEPTION_NUMBER = StarBurn_ISO9660JolietFileTree_Add(
l__PVOID__ISO9660JolietFileTree,
( PCHAR )( &l__CHAR__ExceptionText ),
sizeof( l__CHAR__ExceptionText ),
&l__ULONG__Status,
filename.toLatin1().data(), // Pointer to directory or file name name to build the ISO9660 or Joliet image from
NULL, // Pointer to directory or file name to be stored in the ISO9660 or Joliet image as root name, NULL to include default name from the previous parameter
FILE_TIME_LAST_WRITE, // File time that will be included in file system image (See FILE_TIME).
&AddToNode, // &ChildNode, // Pointer to pointer to the file tree node we'll use as parent. This is the result of either tree walking with StarBurn_ISO9660JolietFileTree_GetFirst(Next)Kid().
&NewNode ); // Pointer to pointer to the new created file tree node.
Do you have any ideas what is causing this? It there some Time Zone setting that needs to be made?
Thanks
Login
Register
FAQ
Search
Thanks!