Funny Files and Folders with a strange date...11/19/2019

Hi,

Probably and maybe nothing, but I come across 114 files and folders with
date modified of 11/19/2019....??

I have a Win98SE machine.....Last clean install was sept of 2004...

I have attached a copy of the search..... All Files.fnd

Thanks, John
--
John Reinders
Hubley, NS

Please remember to remove -removetoreply- when emailing me.

John Reinders wrote:
Hi,

Probably and maybe nothing, but I come across 114 files and folders with
date modified of 11/19/2019....??

I have a Win98SE machine.....Last clean install was sept of 2004...


Looking at your ..fnd listing John, at first glance with the grouping of
files/folders that sport that 2019 date clearly suggests at that moment you
installed your OS back then, the bios was set to that 2019 date is all, and
shortly after that you must of re-set your date aright; and so since at
that first install moment the date was set 2019 and so naturally all your
pertinent files/folders reflect that moment. It's harmless, but if it
bothered you, you could use a program like Touch Pro to change the
file/folder dates of that whole lot, back to whatever date you wanted.

Rick



I have attached a copy of the search..... All Files.fnd

Thanks, John
--
John Reinders
Hubley, NS

Please remember to remove -removetoreply- when emailing me.

Rick Chauvin wrote:
John Reinders wrote:
Hi,

Probably and maybe nothing, but I come across 114 files and folders with
date modified of 11/19/2019....??

I have a Win98SE machine.....Last clean install was sept of 2004...


Looking at your ..fnd listing John, at first glance with the grouping of
files/folders that sport that 2019 date clearly suggests at that moment you
installed your OS back then, the bios was set to that 2019 date is all, and
shortly after that you must of re-set your date aright; and so since at
that first install moment the date was set 2019 and so naturally all your
pertinent files/folders reflect that moment. It's harmless, but if it
bothered you, you could use a program like Touch Pro to change the
file/folder dates of that whole lot, back to whatever date you wanted.

Rick



I have attached a copy of the search..... All Files.fnd

Thanks, John
--
John Reinders
Hubley, NS

Please remember to remove -removetoreply- when emailing me.




Thanks Rick,

I guess it really doesn't bother me that much, I just thought it was
odd. There is still one strange part to this....I did the clean install
of 98SE at the end of September? The dates all say November 19th?

Oh Well!

--
John Reinders
Hubley, NS

Please remember to remove -removetoreply- when emailing me.

John Reinders wrote:

[....]

Thanks Rick,

I guess it really doesn't bother me that much, I just thought it was
odd. There is still one strange part to this....I did the clean install
of 98SE at the end of September? The dates all say November 19th?

You see John no matter when you did the install, even if it was yesterday,
but the point was that whatever the bios date is actually set at the moment
you install the OS is the date that will reflect on all those install files
you are showing in your ..fnd list; iow, for whatever reason when you did
the install, the bios date was set incorrectly and was set at what was
shown.

Rick



Oh Well!

--
John Reinders
Hubley, NS

Please remember to remove -removetoreply- when emailing me.

On Fri, 29 Sep 2006 19:42:36 -0300, John Reinders

Probably and maybe nothing, but I come across 114 files and folders with
date modified of 11/19/2019....??

2019 rings a bell as one of the spurious years that pop up when a
system is not properly Y2k-compliant.

Gee, it's been a while since I thought about that...



------------ ----- --- -- - - - -
Drugs are usually safe. Inject? (Y/n)
------------ ----- --- -- - - - -

cquirke (MVP Windows shell/user) wrote:
On Fri, 29 Sep 2006 19:42:36 -0300, John Reinders

Probably and maybe nothing, but I come across 114 files and folders with
date modified of 11/19/2019....??

2019 rings a bell as one of the spurious years that pop up when a
system is not properly Y2k-compliant.

Gee, it's been a while since I thought about that...



------------ ----- --- -- - - - -
Drugs are usually safe. Inject? (Y/n)
------------ ----- --- -- - - - -

Me too....my system was Y2K compliant (whatever that meant) but I ended
up having to get a new hard drive, so I ended doing a clean install of
98SE...I just ran AIDA32 and the installation date was in fact
11/19/2003 - so much for my memory.

I do not remember seeing dates like this on my system prior to
2003....when I was running win98.....

I've had my current PC since 99...

--
John Reinders
Hubley, NS

Please remember to remove -removetoreply- when emailing me.

On Sat, 30 Sep 2006 13:00:37 -0300, John Reinders
cquirke (MVP Windows shell/user) wrote:
On Fri, 29 Sep 2006 19:42:36 -0300, John Reinders

Probably and maybe nothing, but I come across 114 files and folders with
date modified of 11/19/2019....??

2019 rings a bell as one of the spurious years that pop up when a
system is not properly Y2k-compliant.

Gee, it's been a while since I thought about that...

Me too....my system was Y2K compliant (whatever that meant) but I ended
up having to get a new hard drive, so I ended doing a clean install of
98SE...I just ran AIDA32 and the installation date was in fact
11/19/2003 - so much for my memory.

Somewhere I have the toolset I used to drag into the field, which was
mainly orientated around BIOS Y2k and included fixin' TSRs...
- 2000.exe, which tests rollover, leap years, etc.
- a BIOS-patching .SYS driver for one type of problem
- a BIOS-patching .SYS driver for another type of problem

By ".SYS" I mean DOS Config.sys-level drivers, not 32-bit NT drivers.

One of the TSRs was geared to the "2019" pattern, which was the
"other" Y2k problem pattern at BIOS level. I've forgotten the
details, but failure patterns included...
- BIOS date won't go 2000
- BIOS date can be set 2000, but changes after power off
- BIOS date can be set OK, but won't roll over 1999/2000 properly
- BIOS uses incorrect leap year assumptions

AFAIK it was the "BIOS date set OK, but comes up wrong after power off
and restart" pattern that came up as 2019, and needed that TSR.



------------ ----- --- -- - - - -
Drugs are usually safe. Inject? (Y/n)
------------ ----- --- -- - - - -

"cquirke (MVP Windows shell/user)" wrote in message
...
On Sat, 30 Sep 2006 13:00:37 -0300, John Reinders
cquirke (MVP Windows shell/user) wrote:
On Fri, 29 Sep 2006 19:42:36 -0300, John Reinders

Probably and maybe nothing, but I come across 114 files and folders with
date modified of 11/19/2019....??

2019 rings a bell as one of the spurious years that pop up when a
system is not properly Y2k-compliant.

Gee, it's been a while since I thought about that...

Me too....my system was Y2K compliant (whatever that meant) but I ended
up having to get a new hard drive, so I ended doing a clean install of
98SE...I just ran AIDA32 and the installation date was in fact
11/19/2003 - so much for my memory.

Somewhere I have the toolset I used to drag into the field, which was
mainly orientated around BIOS Y2k and included fixin' TSRs...
- 2000.exe, which tests rollover, leap years, etc.
- a BIOS-patching .SYS driver for one type of problem
- a BIOS-patching .SYS driver for another type of problem

By ".SYS" I mean DOS Config.sys-level drivers, not 32-bit NT drivers.

One of the TSRs was geared to the "2019" pattern, which was the
"other" Y2k problem pattern at BIOS level. I've forgotten the
details, but failure patterns included...
- BIOS date won't go 2000
- BIOS date can be set 2000, but changes after power off
- BIOS date can be set OK, but won't roll over 1999/2000 properly
- BIOS uses incorrect leap year assumptions

AFAIK it was the "BIOS date set OK, but comes up wrong after power off
and restart" pattern that came up as 2019, and needed that TSR.



------------ ----- --- -- - - - -
Drugs are usually safe. Inject? (Y/n)
------------ ----- --- -- - - - -

If the bios keeps changing after power off you might want to check that liitle old battery mounted
on your motherboard.

Galen