Share via

Storage Hardware Considerations for a Thin Client (Windows Embedded CE 6.0)

  • Article

1/5/2010

This topic discusses considerations for storage on a Windows Embedded CE powered thin client.

Internal Flash Memory Storage

You can opt to support internal flash memory storage. Internal flash memory storage can store the run-time image, data files for the device, or both.

If the internal flash memory is the storage medium for the run-time image, the boot loader must be able to download another copy of the run-time image by using another storage medium, such as a network or a USB storage drive, or a hard disk. This ensures recovery of the boot loader and the run-time image from possible storage corruption. Use this same storage medium to update the run-time image.

The following list shows examples of internal flash memory storage:

  • Disk on module (DOM)
  • Disk on chip (DOC)
  • NAND flash array
  • NOR flash array

Mass Storage

Although the Windows Thin Client OS design allows for using mass-storage devices, such as Advanced Technology Attachment (ATA) PC Cards, we do not recommend mass-storage devices that have physically rotating media because of reliability concerns.

For information about how software uses RAM, ROM, and mass storage, see RAM, ROM, and Mass Storage Comparison.

For information about how to develop device drivers for a specific type of device, see Windows Embedded CE Drivers.

See Also

Concepts

Performance Considerations for the Hardware Components of a Thin Client
Hardware Architecture Diagram for a Thin Client
Memory Hardware Considerations for a Thin Client