Javascript Disabled Detected

You currently have javascript disabled. Several functions may not work. Please re-enable javascript to access full functionality.

1 votes

VistaPE open source driver integrator

Started by markus8 , Apr 06 2008 04:45 AM

Please log in to reply

11 replies to this topic

#1 markus8

Members
5 posts

Australia

Posted 06 April 2008 - 04:45 AM

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. :thumbsup:

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.alphadim...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.

#2 jezza333

Member

Members
47 posts

Australia

Posted 06 April 2008 - 09:28 AM

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? :thumbsup:

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

#3 markus8

Members
5 posts

Australia

Posted 06 April 2008 - 10:17 AM

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?

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

Hi Jezza,

The output should be like:

&#91;&#39;D&#58;\\build\\WinBuilder\\Projects\\VistaPE-Core\\Drivers\\Drivers\\AddDrivers.exe &#39;, &#39;D&#58;\\build\\WinBuilder\\Target\\VistaPE-Core\\Windows&#39;, &#39;D&#58;\\build\\WinBuilder\\Projects\\VistaPE-Core\\Drivers\\Drivers\\Drivers&#39;&#93;

Doing 1/65, cmd &#34;peimg /inf=&#34;D&#58;\build\WinBuilder\Projects\VistaPE-Core\Drivers\Drivers\Drivers\intel_chipset_Vista\5000XZVP.inf&#34; &#34;D&#58;\build\WinBuilder\Target\VistaPE-Core\Windows&#34;&#34;

Preinstallation Environment Image Setup Tool for Windows Copyright &#40;C&#41; Microsoft Corporation. All rights reserved.  Installing INF package&#58; D&#58;\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 &#34;peimg /inf=&#34;D&#58;\build\WinBuilder\Projects\VistaPE-Core\Drivers\Drivers\Drivers\intel_chipset_Vista\945.inf&#34; &#34;D&#58;\build\WinBuilder\Target\VistaPE-Core\Windows&#34;&#34;

Preinstallation Environment Image Setup Tool for Windows Copyright &#40;C&#41; Microsoft Corporation. All rights reserved.  Installing INF package&#58; D&#58;\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!

#4 TheHive

Platinum Member

.script developer
4199 posts

Posted 19 April 2008 - 03:35 AM

Any Plans to add a Gui to it?

#5 patsch

Silver Member

Advanced user
785 posts

Germany

Posted 04 September 2008 - 07: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:

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

#6 MichaelZ

Frequent Member

Team Reboot
333 posts

Location:Braunschweig, Germany
Germany

Posted 21 November 2008 - 11:23 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

#7 MichaelZ

Frequent Member

Team Reboot
333 posts

Location:Braunschweig, Germany
Germany

Posted 21 November 2008 - 06:59 PM

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:
[codebox]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. [/codebox] But the corresponding sys files are not in the target's drivers directory. Whereas the storage driver for an Adaptec interface card was copied: [codebox]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
[/codebox]

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

#8 Zhang Heng

Member

Members
51 posts

China

Posted 05 December 2008 - 01:59 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.

#9 InfinityoO

Newbie

Members
19 posts

United States

Posted 09 December 2008 - 11:09 PM

[codebox]['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 [/codebox] 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

#10 InfinityoO

Newbie

Members
19 posts

United States

Posted 09 December 2008 - 11:23 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

havning the same problem

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

#11 was_jaclaz

Finder

Advanced user
7101 posts

Location:Gone in the mist
Italy

Posted 10 December 2008 - 09:28 AM

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

1) You have NOT peimg in the build, or it cannot be found
2) Try using a more recent Winbuilder, FOLLOW instructions in ctmag's signature:
http://www.boot-land...?showtopic=6056

jaclaz

#12 InfinityoO

Newbie

Members
19 posts

United States

Posted 10 December 2008 - 10:11 AM

1) You have NOT peimg in the build, or it cannot be found
2) Try using a more recent Winbuilder, FOLLOW instructions in ctmag's signature:
http://www.boot-land...?showtopic=6056

jaclaz

sorry i already fixed that problem..

what i meant was that i am getting this error now

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 WindowsCopyright © Microsoft Corporation. All rights reserved.PEIMG failed to use the servicing stack shim library (ssshim.dll) to locate aservicing stack that matches the target image (0x80070003).PEIMG failed to complete the operation with status code 0x80070003.return code = 0

Back to VistaPE

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users

VistaPE open source driver integrator

#1 markus8

#2 jezza333

#3 markus8

#4 TheHive

#5 patsch

#6 MichaelZ

#7 MichaelZ

#8 Zhang Heng

#9 InfinityoO

#10 InfinityoO

#11 was_jaclaz

#12 InfinityoO

0 user(s) are reading this topic

Sign In