HP Neoware e140 Neoware Image Manager 4.6 User Manual - Page 121
Potential Incompatibilities, mised as Windows will only invoke the device driver if the hardware
View all HP Neoware e140 manuals
Add to My Manuals
Save this manual to your list of manuals |
Page 121 highlights
Building a Virtual Hard Disk to Boot any PC or TC • Start with a freshly formatted hard disk containing a clean installation of Windows. Note that Pre-installed Windows setups often embed proprietary components that may not be compatible with all the hardware configurations your Windows installation may need to run on. Pre-installed Windows setup should not be used as the base for a Neoware UbiBoot-enabled configuration. • Avoid installing hardware-specific applications if the corresponding hardware is not present in every computer that will run with this installation of Windows. For example, the software modules THOTKEY or TfcnKy that are used to associate programs to some Toshiba Laptops extra keyboard keys may use up to 98% of CPU time when running on a non-Toshiba computer. Note that because of the Plug'N'Play capabilities of Windows 2000/ XP/2003, a hardware driver specific to a device on one PC can be installed on the Neoware UbiBoot enabled hard disk even if another PC or TC which does not have that device will be using the hard disk image. The operating system of the PC or TC will not be compromised as Windows will only invoke the device driver if the hardware is actually detected. For information on HAL and ACPI, refer to the sections "HAL Considerations" on page 113, and "Mixing ACPI & Non-ACPI Computers" on page 115. Potential Incompatibilities It may not always be possible to create a single image that can boot all your hardware. Some drivers can be incompatible with each other, or with a piece of hardware. In this case it is recommended that several different images are created, one for each set of clients that can share a common disk image. Potential Incompatibilities 105