rr Berlin, Germany, 02.09.2007, 18:46 |
File date bug in MS Network Client 3.0 (Miscellaneous) |
While moving data from old ThinkPad 770 to my new Evo N620c laptop I noticed a strange thing: Whenever copying (COPY, XCOPY, VC) a file with date "xxxx-01-01" (YYYY-MM-DD) from a network share its date becomes "adjusted" to "xxxx-13-01" (Do we have a 13th month, that I didn't know off? ). I wrote a small test tool in Turbo Pascal, which uses GetFTime to demonstrate this behaviour. --- |
|
Steve US, 02.09.2007, 19:55 @ rr |
File date bug in MS Network Client 3.0 |
> While moving data from old ThinkPad 770 to my new Evo N620c laptop I |
|
rr Berlin, Germany, 02.09.2007, 21:40 @ Steve |
File date bug in MS Network Client 3.0 |
> Maybe this will explain it: --- |
|
Rugxulo Usono, 02.09.2007, 21:51 @ rr |
File date bug in MS Network Client 3.0 |
> While moving data from old ThinkPad 770 to my new Evo N620c laptop I --- |
|
Steve US, 02.09.2007, 22:08 @ rr |
File date bug in MS Network Client 3.0 |
> > Maybe this will explain it: |
|
rr Berlin, Germany, 02.09.2007, 22:08 @ Rugxulo |
File date bug in MS Network Client 3.0 |
> I dunno, try removing any COUNTRY.SYS lines in CONFIG.SYS, reboot, and try --- |
|
rr Berlin, Germany, 02.09.2007, 22:09 @ Steve |
File date bug in MS Network Client 3.0 |
> Kidding, no. Only exploring. Did you buy your new machine from a --- |
|
Rugxulo Usono, 02.09.2007, 23:13 @ rr |
File date bug in MS Network Client 3.0 |
> I only tried MS-DOS 6.22, but different "servers" (Windows NT 4.0, 2000, --- |
|
rr Berlin, Germany, 26.10.2007, 14:58 @ rr |
File date bug in MS Network Client 3.0 |
> Explanations are welcome! It's a little hard to debug this monster. --- |