Neoware e140 - Thin Client User Manual page 382

Troubleshooting
366 Operations on Virtual Volumes
This will also make sure the logical volume is always clean at boot
time.
When CVolwrite/Volatile mode is not acceptable, you may schedule
deletions of the CVol files on an acceptable basis (every night, every
3 days, every weekend etc...). A deletion batch file should:
1 CD to the directory where the CVol files are stored.
2
Shutdown all the clients that may have mounted a virtual drive
off that server.
3
Stop the Neoware Image Manager server module.
4
Delete all the CVol files.
5
Re-start the Neoware Image Manager server module.
If your client OS is Windows XPe (Windows XP Embedded), you
can enable Enhanced Write Cache. Then the clients will not actually
write any data in the CVol data files.
To reduce the number of different sectors that are written during a
user session, you should preferably use NTFS file system for the
client volumes. If this is not possible, use FAT32 file systems and,
as the last choice, use FAT file system.
Using compressed NTFS as the file system for the client volume is
also a way to reduce the number of sectors that are written during a
user session. To be efficient, the whole volume should be com-
pressed. This compression should be done on the reference client
hard disk, before Neoware Image Manager Client Builder is run.
To reduce the number of different sectors that are written during a
user session, you should set the virtual memory of the clients to use
a local hard disk, if any. If no local hard disks are present or avail-
able to store the Windows swap file, you should set the virtual mem-
ory size to a reasonable size. The minimum and maximum size for
virtual memory should be set to the same values. The size of the vir-
tual memory file (also known as a "page file" or "swap file") should
not exceed the maximum number of sectors in a CVol file divided