From:	jshopREMOVE AT voicenet DOT com (John)
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: Bug in RHIDE:Invalid times on files
Message-ID:	<35d07b9b.2605361@netnews.voicenet.com>
References:	<m0z6EIc-000S4VC AT inti DOT gov DOT ar>
Lines:	21
Date:	Tue, 11 Aug 1998 17:13:38 GMT
NNTP-Posting-Host:	207.103.116.107
NNTP-Posting-Date:	Tue, 11 Aug 1998 13:13:38 EDT
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp

>> The accessed date will be between the years 2005 and 2115.
(using windows95, looking at properties of a file)

This is the (small) problem.
If I run Norton Disk Doctor it reports the invalid dates.
>
>Strange. I know some version of RHIDE let this field unchanged producing 
>things like that. But I tried it with a copy of 1.4 and all works OK.
Could having LFN=y cause this?
That's the only change I can think of when I reinstalled/upgraded.
> 
>> It seems that it sets the modified time by the modified time in RHIDE,
>> rather than the time it was modified *on the disk*.
>
>Yes, and what's the problem?
I'm sorry, this isn't a problem.
>I only saw modified times in the future but looks like Windows some times 
>generates it.
My main concern is that I may have replaced the RHIDE I was using
with an older version, or a modified version.
Where is the "official" site for the latest version?

- Raw text -