Hello dear guest!

Boot Land is a community driven site established since 2006 and focused on data recovery/backup boot disks, research of Windows 2000/XP/2003/Vista/7 install/deployment/antivirus tools, customizing Windows PE systems and even learning how to recover from disaster situations.

How about joining our boot disk community? So do it. Life's short!

  - You get free access to our newsletter with all the interesting buzz about boot disks
  - We share publicity revenue with everyone who wishes to participate at the forums
  - Publicity is never, never, never displayed to members (along with many other cool things)
http://boot-land.net/register

2 Pages V   1 2 >  
Reply to this topic
 VistaPE open source driver integrator
Rating 5 V
post Apr 6 2008, 04:45 AM
Post #1
markus8
  
Group: Members

  Joined: 4-April 08
Posts: 5
Thank(s): 1


Australia


Hi All,

Here's my attempt at a driver integrator for VistaPE.

Q. Why did I write this?
A. The existing integrator by ctv99 didn't do what I wanted.
I wanted:
1. Logging of peimg output.
2. Visibility of commands being executed.
3. A text mode interface. The old GUI really didn't appeal to me. I think this app is better as a console app. smile.gif
4. Something that created a "Users" directory that peimg requires, even if it's empty. (I'd rather the script did it than the pebuilder plugin.)
5. Something written in an understandable popular open source language so that others can improve it. Python rocks!

The main information is:
- I used (and tweaked slightly) the original plugin script from ctv99 ?.
- download http://mark.alphadimensions.net/vistape/Dr...Integrator01.7z
- Extract the contents of the archive to WinBuilder\Projects\VistaPE-Core\Drivers
- Configure the plugin in winbuilder with the correct directories.
- Run it!
- Log is created as adddrivers.log. This is appended to on each run, so you my want to clean it out occasionally.

I've also included a how.to.build.txt which gives the details of what to do to generate a new executable. All of the trickery for that is in add2exe.py

Please reply to this topic to confirm how it goes.

Cheers,
Markus.


1 user(s) said "Thank you!" to markus8 for this fantastic post:
Nuno Brito
+Quote Post
post Apr 6 2008, 09:28 AM
Post #2
jezza333
Member   **
Group: Members

  Joined: 2-May 07
Posts: 48
Thank(s): 2


Australia


Gday mate, I tested it out an I can't say there's any script files lying around to prove that it has worked. Maybe I'm doing something wrong? laugh.gif

"'C:\\Program Files\\WinBuilder\\Target\\VistaPE-Core\\Windows'" - Shouldn't that be "C:\Windows" ? huh.gif
+Quote Post
post Apr 6 2008, 10:17 AM
Post #3
markus8
  
Group: Members

  Joined: 4-April 08
Posts: 5
Thank(s): 1


Australia


QUOTE (jezza333 @ Apr 6 2008, 07:28 PM) *
Gday mate, I tested it out an I can't say there's any script files lying around to prove that it has worked. Maybe I'm doing something wrong? laugh.gif

"'C:\\Program Files\\WinBuilder\\Target\\VistaPE-Core\\Windows'" - Shouldn't that be "C:\Windows" ? huh.gif


Hi Jezza,

The output should be like:
CODE
['D:\\build\\WinBuilder\\Projects\\VistaPE-Core\\Drivers\\Drivers\\AddDrivers.exe ', 'D:\\build\\WinBuilder\\Target\\VistaPE-Core\\Windows', 'D:\\build\\WinBuilder\\Projects\\VistaPE-Core\\Drivers\\Drivers\\Drivers']
Doing 1/65, cmd "peimg /inf="D:\build\WinBuilder\Projects\VistaPE-Core\Drivers\Drivers\Drivers\intel_chipset_Vista\5000XZVP.inf" "D:\build\WinBuilder\Target\VistaPE-Core\Windows""
Preinstallation Environment Image Setup Tool for Windows Copyright (C) Microsoft Corporation. All rights reserved.  Installing INF package: D:\build\WinBuilder\Projects\VistaPE-Core\Drivers\Drivers\Drivers\intel_chipset_Vista\5000XZVP.inf  PEIMG completed the operation successfully. return code =  0
Doing 2/65, cmd "peimg /inf="D:\build\WinBuilder\Projects\VistaPE-Core\Drivers\Drivers\Drivers\intel_chipset_Vista\945.inf" "D:\build\WinBuilder\Target\VistaPE-Core\Windows""
Preinstallation Environment Image Setup Tool for Windows Copyright (C) Microsoft Corporation. All rights reserved.  Installing INF package: D:\build\WinBuilder\Projects\VistaPE-Core\Drivers\Drivers\Drivers\intel_chipset_Vista\945.inf  PEIMG completed the operation successfully. return code =  0

snip....

The log is in D:\build\WinBuilder\Projects\VistaPE-Core\Drivers\Drivers\adddrivers.log on my machine.

The first line is the parameters that the program gets the from script
0: The executable path
1: The path of the windows image to insert the drivers in to.
2: The path that is being searched for drivers to insert.

If nothing was found in the drivers folder, you will just get the first line, so I reckon that's what has happened. Check the directory structure above and check that yours matches.

One thing I forgot to mention previously... make sure that peimg is in the system path!
+Quote Post
post Apr 19 2008, 03:35 AM
Post #4
TheHive
Platinum Member   ******
Group: .script developer

  Joined: 14-July 06
Posts: 3,104
Thank(s): 82


Any Plans to add a Gui to it?


--------------------
+Quote Post
post Sep 4 2008, 07:03 AM
Post #5
patsch
Frequent Member   ***
Group: Members

  Joined: 15-April 08
Posts: 291
Thank(s): 24


Germany


I have some problems using this script ... I can't integrate drivers
the log-file shows for every driver I want to integrate:
QUOTE
Doing 65/104, cmd "peimg /inf="C:\temp\WinBuilder075_Beta4\Projects\VistaPE-Core\Drivers\Drivers\Drivers\intel\ich9usb.inf" "C:\temp\WinBuilder075_Beta4\Target\VistaPE-Core\Windows""
Preinstallation Environment Image Setup Tool for Windows
Copyright © Microsoft Corporation. All rights reserved.

PEIMG failed to use the servicing stack shim library (ssshim.dll) to locate a
servicing stack that matches the target image (0x80070003).

PEIMG failed to complete the operation with status code 0x80070003.
return code = 0

any plan what I'm doing wrong?

btw I use WinBuilder [075 beta 4] VistaPE Core v.12 (Beta 2) and a VistaDVD incl SP1 as source
+Quote Post
post Nov 21 2008, 11:23 AM
Post #6
MichaelZ
Frequent Member   ***
Group: Advanced user

  Joined: 8-March 07 From: Braunschweig, Germany

Posts: 193
Thank(s): 7


Germany


QUOTE (markus8 @ Apr 6 2008, 11:17 AM) *
One thing I forgot to mention previously... make sure that peimg is in the system path!


Hi markus8,

would it make sense to give the path of peimg as an additional parameter to adddrivers.exe? The path can be automatically obtained through the predefined variable %WAIKDir% after a ReadEnv.

I tried the script with VistaPE 12 RC1, Vista SP1 DVD German as source and WAIK 1.1 German. It was no surprise that the build took a little longer (22 minutes to integrate drivers with peimg in comparison to one second simply copying them with the regular script). Disadvantage was that there is a bsod when booting the system in VMware:
STOP 0x000000D1 in rdacdisk.sys
I removed IBM\2 from the storage directory. WinBuilder is building presently (will take 22 minutes longer than usually...). Will see what happens next.

Many Greetings
MichaelZ
+Quote Post
post Nov 21 2008, 06:59 PM
Post #7
MichaelZ
Frequent Member   ***
Group: Advanced user

  Joined: 8-March 07 From: Braunschweig, Germany

Posts: 193
Thank(s): 7


Germany


After removing IBM\2 with rdacdisk.sys from the storage directory VistaPE booted fine. So I guess that peimg enters the storage drivers in the DeviceCriticalDatabase registry path and that it is loaded at startup. rdacdisk.sys seems not to be compatible with Vista/WinPE 2. VistaPE 12 RC1 driver integration probably doesn't preload the storage drivers.

But there is an other funny problem with the script. peimg seems not to load all drivers. I noticed that the target system doesn't include the LAN drivers for ADMtek or Intel 1000/Pro. The Logfile states success:
CODE
Doing 42/151, cmd "peimg /inf="D:\Work\WinBuilder\Build\Projects\VistaPE-Core\Zusatz_MZ\Drivers\Drivers\LAN\ADMtek\NETAN983.INF" "D:\Work\WinBuilder\Build\Target\VistaPE-Core\Windows""
Vorinstallationsumgebungs-Abbildsetuptool fr Windows
Copyright © Microsoft Corporation. Alle Rechte vorbehalten.
INF-Paket wird installiert: D:\Work\WinBuilder\Build\Projects\VistaPE-Core\Zusatz_MZ\Drivers\Drivers\LAN\ADMtek\NETAN983.INF
PEIMG hat den Vorgang erfolgreich abgeschlossen.
return code = 0
[...]
Doing 51/151, cmd "peimg /inf="D:\Work\WinBuilder\Build\Projects\VistaPE-Core\Zusatz_MZ\Drivers\Drivers\LAN\Intel\e1y6032.INF" "D:\Work\WinBuilder\Build\Target\VistaPE-Core\Windows""
Vorinstallationsumgebungs-Abbildsetuptool fr Windows
Copyright © Microsoft Corporation. Alle Rechte vorbehalten.
INF-Paket wird installiert: D:\Work\WinBuilder\Build\Projects\VistaPE-Core\Zusatz_MZ\Drivers\Drivers\LAN\Intel\e1y6032.INF
PEIMG hat den Vorgang erfolgreich abgeschlossen.

But the corresponding sys files are not in the target's drivers directory.

Whereas the storage driver for an Adaptec interface card was copied:
CODE
Doing 55/151, cmd "peimg /inf="D:\Work\WinBuilder\Build\Projects\VistaPE-Core\Zusatz_MZ\Drivers\Drivers\Storage\Adaptec\10\ARCSAS.INF" "D:\Work\WinBuilder\Build\Target\VistaPE-Core\Windows""
Vorinstallationsumgebungs-Abbildsetuptool fr Windows
Copyright © Microsoft Corporation. Alle Rechte vorbehalten.
INF-Paket wird installiert: D:\Work\WinBuilder\Build\Projects\VistaPE-Core\Zusatz_MZ\Drivers\Drivers\Storage\Adaptec\10\ARCSAS.INF
PEIMG hat den Vorgang erfolgreich abgeschlossen.
return code = 0


The LAN driver e1y6032.inf works when it is copied using the 'simple' regular driver script or when it is loaded using drvload later on.

Many Greetings
MichaelZ

+Quote Post
post Dec 5 2008, 01:59 PM
Post #8
Zhang Heng
Member   **
Group: Members

  Joined: 22-March 07
Posts: 54
Thank(s): 16


China


QUOTE (patsch @ Sep 4 2008, 03:03 PM) *
I have some problems using this script ... I can't integrate drivers
the log-file shows for every driver I want to integrate:

any plan what I'm doing wrong?

btw I use WinBuilder [075 beta 4] VistaPE Core v.12 (Beta 2) and a VistaDVD incl SP1 as source


The same to me.

It seems it cannot work on a Vista hosted environment.

The solution is:

1. Apply wimpe.wim (from Windows AIK) to a directory (named temp).

2. put all files from %TargetDir%\Windows\System32\config\*, (SYSTEM, SOFTWARE, DEFAULT, etc) to temp\Windows\System32\config and overwrite all files.

3. Install INFs using peimg.exe on temp\windows.

4. copy the file which copied in step 2 from temp\Windows\Systm32\config to %TargetDir%\Windows\Systm32\config

en, drivers installed successfully.

1 user(s) said "Thank you!" to Zhang Heng for this fantastic post:
allanf
+Quote Post
post Dec 9 2008, 11:09 PM
Post #9
InfinityoO
Newbie   *
Group: Members

  Joined: 27-September 07
Posts: 19
Thank(s): 0


United States


CODE
['D:\\winbuilder\\Projects\\VistaPE-Core\\Drivers\\Drivers\\adddrivers.exe', 'D:\\winbuilder\\Target\\VistaPE-Core\\Windows', 'D:\\winbuilder\\Projects\\VistaPE-Core\\Drivers\\Drivers\\Drivers']
Doing 1/151, cmd "peimg /inf="D:\winbuilder\Projects\VistaPE-Core\Drivers\Drivers\Drivers\Chipset\intel_inf\2008s4el.inf" "D:\winbuilder\Target\VistaPE-Core\Windows""
'peimg' is not recognized as an internal or external command,
operable program or batch file.
return code = 0
Doing 2/151, cmd "peimg /inf="D:\winbuilder\Projects\VistaPE-Core\Drivers\Drivers\Drivers\Chipset\intel_inf\5000XZVP.inf" "D:\winbuilder\Target\VistaPE-Core\Windows""
'peimg' is not recognized as an internal or external command,
operable program or batch file.
return code = 0
Doing 3/151, cmd "peimg /inf="D:\winbuilder\Projects\VistaPE-Core\Drivers\Drivers\Drivers\Chipset\intel_inf\5400.inf" "D:\winbuilder\Target\VistaPE-Core\Windows""
'peimg' is not recognized as an internal or external command,
operable program or batch file.
return code = 0


i am getting that in the log.. what am i doing wrong

using vistape 12 rc winbuilder 0.75 beta with vista sp1 as source and with waik 1.1 installed
+Quote Post
post Dec 9 2008, 11:23 PM
Post #10
InfinityoO
Newbie   *
Group: Members

  Joined: 27-September 07
Posts: 19
Thank(s): 0


United States


QUOTE (patsch @ Sep 4 2008, 08:03 AM) *
I have some problems using this script ... I can't integrate drivers
the log-file shows for every driver I want to integrate:

any plan what I'm doing wrong?

btw I use WinBuilder [075 beta 4] VistaPE Core v.12 (Beta 2) and a VistaDVD incl SP1 as source



havning the same problem

btw I use WinBuilder [075 beta 4] VistaPE Core v.12 (RC) and a VistaDVD incl SP1 as source
+Quote Post

2 Pages V   1 2 >
Reply to this topic
1 User(s) are reading this topic ()


  

Collapse

  Topic Replies Topic Starter Views Last Action
No new Pinned: Topic has attachmentsVistaPE Leopard Beta II
Agust 31,2009
126 Max_Real Qnx 19,880 7th February 2010 - 04:13 PM
Last post by: Max_Real Qnx
No New Posts VistaPE - Safely remove USB device?
5 blued 225 7th February 2010 - 12:24 PM
Last post by: Wonko the Sane
No New Posts VistaPE with Java Runtime Environment
4 Nesim Nerse 205 5th February 2010 - 09:22 PM
Last post by: WetHat
No New Posts Pinned: Topic has attachmentsVistaPE Script on Win7PE Project Post here ONLY reports of working setups!
This topic was created to identify VistaPE Script running on Win7PE
5 ludovici 7,718 29th January 2010 - 09:47 PM
Last post by: PaPeuser
No new Pinned: Topic has attachmentsVistaPE updated package RC1a
100 JonF 15,426 29th January 2010 - 06:31 AM
Last post by: dera