Windows Embedded is a family of operating systems that offer familiar tools and software engineering technologies for developers to quickly bring the next generation of smart, connected, service-oriented devices to market. Windows Embedded features enable interoperability with industry standards and Microsoft technologies, enabling connectivity to PCs, services, servers, and other devices.
Windows Embedded is based on the hardware and software requirements of your embedded system design.
The Difference Between Windows Embedded & Windows XP
- Componentization
- Embedded Features
Componentization has the following benefits:
- Great Performance
Reducing disk and memory use can significantly improve performance of both the platform and your software. - Reliability
Generally, reliability increases with fewer executable files running and interacting with one another, devices, and the user. - Customization
Componentization, enables fine-grained customization that is not possible by using traditional setup programs. - Licensing
By using more customization, you can license very specific areas of functionality and more easily guarantee compliance. - Security
Devices that contain only the components that are required for their functionality are more secure, because they have a smaller surface attack area. Security can also be increased with components that add functionality such as encryption or antivirus protection.
Some of Features
- Protect Disk Volume, EWF (Enhance Write Filter)
Embedded device disk volumes often require protection against improper disk write operations Reducing disk and memory use can significantly improve performance of both the platform and your software. - HORM (Hibernate Once Resume Many)
A valuable feature for quickly booting a Windows XP. - File Base Write Filter (FBWF)
FBWF redirects all writes targeted for protected volumes to a RAM cache called an overlay. - Minlogon
In a Windows XP Embedded runtime allows you to reduce boot time, shutdown time, and footprint. - Create Single-User Environment
A single-user environment can be the best option for some embedded device scenarios. - Footprint
The size of a run-time image is called the footprint. A small footprint will allow a run-time image to be deployed onto hardware with memory or hard disk size restrictions.
For more information, please call our technical engineer or email us.
If you have enquiry about our products, please call our technical engineer to get some advice!
Call Us : 08161892943, 08561054249
Or send us email
