thanks Michael, I read the other threads about date/time. I’m also using C interface, if time would change only once and would change to UTC that would be no problem, the problem is that for each session all files that already exists on CD will get new date / time, on every new session, so if I begin writing file 1 and this one has timestamp 03/31/2005 3:58 AM, after writing file on session one, windows reads corectly timestamp for file written to CD, while nero reads it wrong, 3/28/2005 7:58 PM. If I’m writing a new file, file 2, on a new session, session 2, after burning this new file timestamp for file 1 is changed again to 3/25/2005 … and so on. This only happens if I’m seting my time zone to -5, I’m in timezone +2, and don’t have this problem while using +2 timezone.
I’m not sure that I can use solution from that thread you’re saying I could use as a workarround; is this a valid solution?: read file date / time using windows api, than read last session using nero and than do some matching between files read by nero / windows and set proper time using C++ interface? Could I use this to solve my problem? Can I mix C / C++ nero calls?
I’ve tested NeroCmd, I’ve burn file using this, and problem is there too.
This is what I’ve used on first session:
–write --drivename F --real --iso VolumName C: ext.txt --close_session
and this on second one:
–write --drivename F --real --iso VolumName C: ext1.txt --close_session --import_iso_only