G
Guest
I have an XP Embedded machine in the field that has a 40 GB drive partitioned
3 ways. C:\ is 10.1 GB. D:\ is 16.2 GB. E:\ is 10.1 GB. The C:\ drive was
down to 55 MB of free space, so I did some poking around with TreeSize.
I found that there were 2 restore points. One that occurred on February 7,
a 6.9 GB restore point; and another on March 4, a 2.3 GB restore point.
There were other restore points of inconsequential size.
Based on the way System Restore points are configured on these kiosks is 12%
max, meaning they should only grow to 1.2 GB.
Is there a known SP1 incident on this? What else can/should I check. The
app logs and sys logs have rolled, but I have other kiosks that have the same
problem
The offending restore points keep dumping the a*.sys file Virtual memory is
fixed at 768 MB.
It's running Windows XP Embedded SP1, on a Pentium III 732 MHz processor,
256 MB RAM.
Has someone seen this before?
--
Slater...
Jeff
"Time is an illusion, rising from time."
3 ways. C:\ is 10.1 GB. D:\ is 16.2 GB. E:\ is 10.1 GB. The C:\ drive was
down to 55 MB of free space, so I did some poking around with TreeSize.
I found that there were 2 restore points. One that occurred on February 7,
a 6.9 GB restore point; and another on March 4, a 2.3 GB restore point.
There were other restore points of inconsequential size.
Based on the way System Restore points are configured on these kiosks is 12%
max, meaning they should only grow to 1.2 GB.
Is there a known SP1 incident on this? What else can/should I check. The
app logs and sys logs have rolled, but I have other kiosks that have the same
problem
The offending restore points keep dumping the a*.sys file Virtual memory is
fixed at 768 MB.
It's running Windows XP Embedded SP1, on a Pentium III 732 MHz processor,
256 MB RAM.
Has someone seen this before?
--
Slater...
Jeff
"Time is an illusion, rising from time."