1 Reply by mmx

(6 replies, posted in Universal Imaging)

Downloaded DriverPack Base and the driver packs I wanted.
Extracted Base to C:\DriverPacks
Copied C:\DriverPacks\DPsFnshr.ini to C:\
Extracted C:\DriverPacks\bin\DPsFnshr.7z to C:\
Copied C:\DriverPacks\bin\wnt5_x86-32\ROE.exe to C:\sysprep
Extracted C:\DriverPacks\bin\wnt5_x86-32\M2.7z to ..\M2
Copied C:\DriverPacks\bin\wnt5_x86-32\M2\DevPath.exe to C:\
Extracted packs to C:\
Ran from C:\, 'DevPath.exe C:\D'
Ran from C:\sysprep, 'ROE.exe 937'
Checked key HKLM\SOFTWARE\Microsoft\Windows\Current Version\RunOnceEx\937\1

No worries, though.  I'll either figure it out or write a script to handle it.  I very much agree that there is something different that I am doing.  Was thinking if someone had the source in front of them they could say, 'Oh, that path comes from this code right here.  It determines the path by ...'.  Thanks for reading!

Go to forum: Universal Imaging

2 Reply by mmx

(6 replies, posted in Universal Imaging)

From what I was reading I was under the impression that it's sole purpose was to create:
HKLM\SOFTWARE\Microsoft\Windows\Current Version\RunOnceEx\937\1
with a value of:  C:\DPsFnshr.exe
(937 to be replaced with whatever value you pass it upon running)

I was more confused as to how it got a different drive letter, X:\DPsFnshr.exe.

Go to forum: Universal Imaging

3 Topic by mmx

(6 replies, posted in Universal Imaging)

Hello,

Been messing around with DriverPacks and the many DriverPacks/sysprep guides out there.  Many thanks to the DriverPacks team, an amazing idea implemented well (so for so good at least!).

I have everything set up and running as desired, except for one thing.  When I run ROE.exe to create the registry entry it creates the appropriate key; however, the value points at a network drive I have.  Instead of being 'C:\DPsFnshr.exe' it creates the key with the value 'X:\DPsFnshr.exe'.  Needless to say, this drive does not exist on the machines we're deploying.  How can I change the value ROE creates?

I know I could (fairly easily) create a script/registry key to create/change the appropriate key.  However, I'm kind of just the setup guy, I won't be the one using these tools to re-image machines.  And, I would like to stick as close to on-line documentation as possible (they won't bother to read the documentation I'll give them; but, they'll google it) if a problem/change arises.

Thanks.

Go to forum: Universal Imaging