1

(109 replies, posted in Universal Imaging)

Thanks Somebody. I reread overflows post and I must have joined a few sentences and misinterpreted his instructions.
Disregard my previous post. Ill start from scratch.
tongue

Pig

2

(109 replies, posted in Universal Imaging)

Ok, let me try to explain what is happening.

When Driverpacks.net is created here is what is under it.

---Driverpacks.net
   -DP_Install_tool.cmd
   -DPCP1005.7z
   -DPINST.exe
   -DPInst.xml
   -DPM1009.7z
-Bin
  -7-Zip.dll
  -devpath.exe
  -DPsFnshr.7z
  -DPsFnshr.ini
  -un7zip.exe
   

So your step states:

Move the contents of this folder (this will consist of a 'D' subfolder and a couple of stray files - don't worry, they will be auto-removed on the target computer) to the root of the system drive of the guest Windows. Delete the DriverPacks.net folder.

So this puts the bin folder labeled above on C:\
Looking back at your picture reference under 14. I do not see a bin folder. So am I supposed to remove the files from BIN and then put them under C:? Only DPsFnshr is under BIN. Yet under your picture you have files such as pmtimer.exe, makePNF, etc.

Do you see the confusion now? I am following your instructions verbatim. However, your results are not matching up to mine, and I am using the latest files from Driverpacks.net. If I am doing something wrong, then so be it, I will have to fix the methods I am using. However I am following your instructions step by step. So If my results are wrong, perhaps we need to look back at the instructions provided and see where the disconnect is. Currently I just added the files needed so that my folders are almost exactly like yours. I shall see if that helps... if not... then I will start completely over and go step by step again. If I recieve the same results. I will let you know.

Pig

3

(109 replies, posted in Universal Imaging)

OverFlow wrote:

Pig apparently did not copy the files from the DriverPacks.net folder correctly...

Actually, going back over my steps. I did do that correctly. I had to extract the files from DPsFnshr.7z in order to get the files needed under C:

Pig

4

(109 replies, posted in Universal Imaging)

Ok, Thank you both for pointing that out to me. I am not sure how I missed that.
Ill give it a shot and see how it turns out!

Thanks again
Pig

5

(109 replies, posted in Universal Imaging)

Ok, first issue has arisen.

Upon reboot after sysprep the machine went through the setup steps, however when it hit the setup phases and came to the desktop, the first error showed up.

It was looking for DPSFNSHR. Now I did not see it in your walkthrough.

Is this something that I missed? Was it forgotten, or is it underlying knowlege that I just havent committed to memory?

I replaced the image just prior to sysprep so I can add the files needed.... if needed.

Anyone have any ideas?

Pig

6

(109 replies, posted in Universal Imaging)

Thanks for the welcome.

I used Somebody's methodology here, the only changes I have are:

1: Using a physical box to develop the image.
2: Added both the CPU and Mass storage to the Stand Alone (Step. 12 above)

I am now just updating all my driver packs today, and plan on transfering them over and running the Sysprep for some testing.
Fingers crossed!

Somebody, thanks again for laying it all out in a simplified manner!

Pig

7

(109 replies, posted in Universal Imaging)

Thank you for this very well developed step by step.
However I do have a question.

Why wouldnt you integrate the mass storage drivers along with the CPU drivers? To make it more likely to be Hardware Independent?
Or is that included in the Non-plug and play hardware detection?


I would like to use this method (with a few differences) to create an image that can be put across many platforms.

Pig