NewTimeZoneMethod bug

Bug reports will be moved here when the described bug has been fixed

Moderators: white, Hacker, petermad, Stefan2

Post Reply
User avatar
Gral
Power Member
Power Member
Posts: 1460
Joined: 2005-01-26, 15:12 UTC

NewTimeZoneMethod bug

Post by *Gral »

There is a bug with "NewTimeZoneMethod" on CDFS with bad "up" directory entry
TC hangs during enter to directory, without it's own error message.
In order to cause an error, the following three conditions must be met:

1. NewTimeZoneMethod=1
2. Active native full view mode - datetime of "up" directory entry must be visible.
3. (most specific) Bad CD image - datetime of "up" directory entry must be senseless value, eg.:
(YYYY.MM.DD hh.mm)
 0635.00.00 60.10

ISO installed with PassMark OSF Mount V1.5 - https://www.osforensics.com/tools/mount-disk-images.html from command line:
OSFMOUNT.COM -a -t file -m #: -f 6600GT.iso
Sample file ftp://videodarom.no-ip.org/pub/soft/DRIVERS/Video/nvidia/6600GT.iso (204 MB)
Bug occurs on physical discs too, it's probably common on nVidia driver CD, created by Nero.

EDIT
New, small, sample file
http://gral.y0.pl/tc/GameDeviceDriver.7z
(47kB 7z containing 40MB iso)
User avatar
ghisler(Author)
Site Admin
Site Admin
Posts: 48005
Joined: 2003-02-04, 09:46 UTC
Location: Switzerland
Contact:

Post by *ghisler(Author) »

Not confirmed. However, I mounted the ISO with the Windows 10 built in ISO support, not with PassMark, so it may be a bug in PassMark.
Author of Total Commander
https://www.ghisler.com
User avatar
Gral
Power Member
Power Member
Posts: 1460
Joined: 2005-01-26, 15:12 UTC

Post by *Gral »

I forgot to mention - bug occurs only on Windows XP.
Does not occurs on any newer Windows version, even Windows Server 2003.

OSFMount has nothing to do with it, because it also happens with physical CDs, eg. "Nero Burning ROM 5.5" (at least Samsung CD Recorder bundled version) and many older nVidia driver CDs (about 2003), all created with Nero.
User avatar
ghisler(Author)
Site Admin
Site Admin
Posts: 48005
Joined: 2003-02-04, 09:46 UTC
Location: Switzerland
Contact:

Post by *ghisler(Author) »

Thanks, I could reproduce the bug on XP. It's a bug in Windows itself: SystemTimeToTzSpecificLocalTime crashes when the year is >=2559. I will therefore not call this function when the year is that high.
Author of Total Commander
https://www.ghisler.com
User avatar
ghisler(Author)
Site Admin
Site Admin
Posts: 48005
Joined: 2003-02-04, 09:46 UTC
Location: Switzerland
Contact:

Post by *ghisler(Author) »

This should be fixed in Total Commander 9.10 RC1, please test!
Author of Total Commander
https://www.ghisler.com
User avatar
Gral
Power Member
Power Member
Posts: 1460
Joined: 2005-01-26, 15:12 UTC

Post by *Gral »

Fixed!
Post Reply