sorry ... but bump
1 2010-01-25 08:42:38
Re: simple process plan (see if i get it right) (2 replies, posted in Universal Imaging)
2 2010-01-20 16:19:03
Topic: simple process plan (see if i get it right) (2 replies, posted in Universal Imaging)
Hi gang,
I posted once here long long time ago whilst trying to universal image -- i didnt succeed, got bummed but now im back giving it another shot.
What ive done so far is create a virutalised XP sp3 client on my xen server, downloaded the latest driver packs to another computer, extracted the packs.
What i do next is where i get lost somwhat. I know i need to:
1) Go to my current differing models of client computers and find out what drivers they have/need (including mass storage)
2) See if the drivepacks have these drives
3) Copy these drivers to the virutal XP image and Inject these drivers into the sysprep/finalization process of my virtual image
Im run into problems with stage one. I go to my client computers, a mix of HP models, and i run the findHWID.exe app which *i believe* should run against my extracted driverpack repository and, when appropriate ticks are checked, populate my sysprep.inf which the drivers locations required for that model of computer. Am i right in my understanding here?
In my resulting hwids.csv it shows some data i dont understand so much. I can acertain that there are "few" devices there, but i dont see things like LAN card (intel gigabit 82566DM-2) or video card (Intel q33 express chipset). There are a few chipset (class=system) and masssorage (class=hdc, these are duplicated aswell). Across differing models i get some slight variations but no drivers ever originate from anything other then "D\C" and "D\M"
Should I be seeing anything other than these entries? Am i doing things in the right procedure with the right utility?
Thanks for any direction.
3 2009-08-06 11:44:57
Re: "Uni" Image wont boot (cycles) but not a HAL issue. (8 replies, posted in Universal Imaging)
Hi guys -- thanks for the responses. Unfortunatley i hae had to rebuild my potential universal image machine so i cant provide my mass storage section anymore.
So guys you suggested to remove drivers before sysprepping? Is this for all drivers or just the video? This is definatley a step i do not do.
Also why is working on vmware more efficeient?
I will restart my universal image quest and return with uninstalled video card results.
4 2009-07-30 14:45:26
Re: "Uni" Image wont boot (cycles) but not a HAL issue. (8 replies, posted in Universal Imaging)
Can i get any help with this please?
5 2009-07-22 10:23:07
Topic: "Uni" Image wont boot (cycles) but not a HAL issue. (8 replies, posted in Universal Imaging)
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
6 2009-07-06 11:55:57
Re: simpleton's guide to universal imaging (8 replies, posted in Universal Imaging)
that is why i am looking for some conceptual advice here. I know that you are not a sysprep/imaging fan in general and would rather create a slipstreamed install disc. I have not seen anything describing the popups and KTD correlation - i did however read just before i posted that you describe KTD as a purely tech-lab based function and this should not be enabled for end-user destination computers.
I am sorry if this is covered somewhere else. Ill be quite now.
7 2009-07-06 11:43:27
Topic: simpleton's guide to universal imaging (8 replies, posted in Universal Imaging)
Hi everyone.
1 this site is pretty amazing - i apologise for not being able to help myself with these simple conceptual problems.
What i am doing at the moment is attempting to create universal image for a range of HP computer models.
I do this by:
1 - installing the base XP on a physical machine (including partition as required)
2 - install all updates (sp3+)
3 - install all software & configure supplimentals (default user etc)
4 - running with the guide by skinLayers (http://forum.driverpacks.net/viewtopic.php?id=1682)
5 - create ghost image and deploy
I know that this is a good method, it has saved me alot of images. I thank you all for this, but i know there is a better way aswell.
1 - installing on vm seems to be a "better" method. Why i am not sure but it seems to be the way to go. I simply dont know how this would be done? I understand and have some experience with vm's (xen) but i get lost regarding drivers, pseudo drivers, fileSystem etc.
2 - driverpacks has helped me alot but after my sysprep of a destination computer i still get "unsigned driver" messages (over 100 in some cases) - i have ensure the the "ignore driver warning" is enabled in the finisher ini but it remains -- is this just a mistake on my half?
3 - i have read on the sysprep driver finder program -- if i understand correctly i could downbload and expand all the driverpacks in c:\D\ - run the driver finder then sysprep/image my master image. Would this work or am i missing a component here?
I know my questions arent so clear so i apologize. Thanks for any help.