K
KMyers1
Am using Offline Files in Windows XP SP3 with all critical updates.
Was attempting to append data to some very large files that happened
to be on a mapped network drive using Offline Files. While the append
was in progress, I could see the file size in Explorer slowly increase
to the final size of over 3GB. Within a few seconds after the append
operation was complete, the file size would suddenly be changed to 0
(zero). Opening the file confirmed that it had been truncated to zero
bytes. I tried this several times using different techniques for
appending to the file (include a utility that I wrote myself). In
every case, the file size was truncated to zero immediately after the
append operation completed. The problem appears to occur any time
that appending to a file would result in a file size exceeding 2GB.
When I tried the same thing on a local drive, not using Offline Files,
this file truncation did not occur.
Does anyone know:
1. Is this problem specific to offline files, or does it affect all
files on mapped drives?
2. If this problem is specific to offline files, does it only occur
when working offline, or does it also occur when connected to the
offline files server?
3. Is there any way to correct or avoid this problem other than not
using offline files or mapped drives?
Thanks,
Kevin M.
Was attempting to append data to some very large files that happened
to be on a mapped network drive using Offline Files. While the append
was in progress, I could see the file size in Explorer slowly increase
to the final size of over 3GB. Within a few seconds after the append
operation was complete, the file size would suddenly be changed to 0
(zero). Opening the file confirmed that it had been truncated to zero
bytes. I tried this several times using different techniques for
appending to the file (include a utility that I wrote myself). In
every case, the file size was truncated to zero immediately after the
append operation completed. The problem appears to occur any time
that appending to a file would result in a file size exceeding 2GB.
When I tried the same thing on a local drive, not using Offline Files,
this file truncation did not occur.
Does anyone know:
1. Is this problem specific to offline files, or does it affect all
files on mapped drives?
2. If this problem is specific to offline files, does it only occur
when working offline, or does it also occur when connected to the
offline files server?
3. Is there any way to correct or avoid this problem other than not
using offline files or mapped drives?
Thanks,
Kevin M.