Topic: "Uni" Image wont boot (cycles) but not a HAL issue.
Hello again,
Ive now made a image on a physical computer that is driver-wise "universal" (via skin layers guide without running the makePNF.exe step) and HAL set to Advanced Configuration and Power Interface (ACPI). Thus this image "should" be universal right? IE ive covered 2 of the 3 bases of making universal images - the other being mass storage drivers right?
Now my logic puzzle is this. I usually make my images on a physical machine (HP d330s) which is IDE hdd and i have a universal image from that that works. (except i stuffed the KTD stage and it asks for a driver prompts alot). This time ive made my universal image on a computer that has SATA controller. I didnt think this would be a problem (being an idiot) and when i created a .WIM and imageX'd it to a new computer it only cycles.
Now ...
Reading alot of posts here i found a nice description somewhere that says that "if its a HAL issue, you'll cycle. If its a storage controller issue, you'll blue screen" -- is this correct? If it is then my HAL setting must be wrong? But ive gone back and set my HAL to ACPI MultiProcessor PC AND even standard PC and it still cycles. (at safe mode it dies at mup.sys)
Two questions:
1) What are the reasons why my image would my image be cycling? OR it is positivley HAL related?
2) How can i get my image off this computer so i can deply to other computers? (If indeed it is a storage controller issue?) What steps are required.
Before i get acosted - i did read all the threads and forums. Alot more things made more sense after being forced to re-read things so i wont complain about that but i have tried and am looking for some help.
Thanks