A. When a RIS client computer boots so it can install an OS from the RIS server, the client displays a list of OS images that are applicable to it. A problem occurs when the image's hardware abstraction layer (HAL) differs from the HAL that the local machine should use (e.g., single-processor HAL versus multiprocessor HAL). I experienced this problem recently when I used the Remote Installation Preparation (RIPrep) utility to create an image from a client workstation. When I booted another computer so it could install an OS from the RIS server, the computer didn't display the image. The problem was that the computer I used to create the image had hyperthreading enabled, which means the HAL is a multiprocessor version (although the machine actually has only one CPU), whereas the destination machine didn't have hyperthreading and required a single-CPU HAL. If the HAL is the same on both the imaged and local systems, compare the NTFS permissions on the RIS server's image folder with the permissions on an image that you know works. If the permissions aren't the same, adjust them on the image folder so they match the permissions on the folder of the working image.