51

(67 replies, posted in Vista / 7 DriverPack LAN)

Hi guys,

I have found out that the new Optiplex760 desktops from Dell are not supported with the current Lan driverpacks. (neither x86 nor x64)

The driver missing is from intel and contains those files:

x32:
e1k6032.cat
e1k6032.din
E1k6032.inf
e1k6032.sys
e1qmsg.dll
NicCo26.dll
NicInstQ.dll

x64:
e1k60x64.cat
e1k60x64.din
E1k60x64.inf
e1k60x64.sys
e1qmsg.dll
NicCo26.dll
NicInstQ.dll

Those drivers are included in the latest Intel driverpack:
http://downloadmirror.intel.com/17252/e … s_13_5.zip

Would you mind integrating those please ?

Maybe the zip contains other drivers not yet in the driverpacks ?

Thanks,
Alex

52

(78 replies, posted in Vista / 7 DriverPack Audio)

Hi guys,

in case you would like to integrate the RME HDSP series of cards, here is the x64/x86 driver:
http://www.rme-audio.de/download/hdsp_wdm_3075.zip

Bye,
Alex

53

(41 replies, posted in Vista / 7 DriverPack Graphics B)

Hi muiz,

link isn´t working :-)

Bye,
Alex

54

(15 replies, posted in News)

Hi again,

I also use Windows7 already, altough there are a few driver related problems so it is not that stable for daily work after all. I have integrated the vista driverpacks into Windows7 also, there are a few errors during this process (dism.exe) probably because some of the vista drivers do not work in Windows7 but I guess this will change over time.

It would be nice to have support for control panels in the Vista driverpacks for instance the ATI CCC etc.

@muiz: No problem, no rush, thanks for your work on this ! Very appreciated ! :-)

Bye,
Alex

55

(15 replies, posted in News)

Hi muiz,

will you be updating the rest of the x86 driverpacks soon ? I´d just like to know if I should wait another few days for a fresh install of my system or if I can go for it now :-)

Thanks,
Alex

56

(78 replies, posted in Vista / 7 DriverPack Audio)

Hi muiz,

winrar reports that the archive is corrupt. Downloaded it twice.

Thanks,
Alex

57

(41 replies, posted in Vista / 7 DriverPack Graphics B)

Hi !

New ATI driver is finally out:
https://a248.e.akamai.net/f/674/9206/0/ … _74233.exe
https://a248.e.akamai.net/f/674/9206/0/ … _74234.exe

58

(41 replies, posted in Vista / 7 DriverPack Graphics B)

well, hopefully ATI releases 9.1 driver soon so it will make it into the next driverpack then ! :-)

59

(85 replies, posted in Vista / 7 DriverPack Chipset)

Thanks !

60

(85 replies, posted in Vista / 7 DriverPack Chipset)

Hi Jaak,

I got my driver from Windows Update but I have checked the asus site, the driver can be downloaded here:
http://dlsvr04.asus.com/pub/ASUS/misc/u … PVista.zip

That is the AI Suite but if you unpack this, the driver can be found in the ACPI\WinVista or ACPI64\WinVista folders.

Bye,
Alex

61

(85 replies, posted in Vista / 7 DriverPack Chipset)

Hi !

I have found that on my P5Q-E mainboard the following is never installed with the vista driverpacks, neither in Vista x64 nor in Windows 7 x64:

http://img158.imageshack.us/img158/3161/71002431kw9.jpg
http://img158.imageshack.us/img158/71002431kw9.jpg/1/w413.png

Bye,
Alex

62

(34 replies, posted in News)

Hi !

Yeah, but I have a temporary solution ... I copied the two files peimg.exe and peimg.ini over from a WAIK 1.1 installation. Still works fine on Windows7 with WAIK 2.0 beta. :-)

Bye,
Alex

63

(55 replies, posted in Vista / 7 DriverPack Mass Storage)

Hi !

I am not sure about vmware but on my physical machine (Gigabyte X38-DQ6 board) there is definitely no Silicon Image controller and I still have that icon in the control panel ... :-)

PS: Only controllers are onboard Intel and JMicron JMB36X

Bye,
Alex

64

(55 replies, posted in Vista / 7 DriverPack Mass Storage)

Hi muiz,

thanks. One small problem: the Silicon Image SATA Controllers Control panel item is being installed all the time even if no SI controller is present (for instance in a virtual machine). Also goes for the x64 version by the way.

Bye,
Alex

65

(34 replies, posted in News)

Hi Muiz,

well, the new WAIK also makes it a bit more complicated. It contains dism.exe and can be installed on Vista/XP so dism.exe is available there. However, the new WAIK does not come with peimg.exe anymore to service an offline WinPE image (for instance add drivers). Dism.exe is supposed to replace that according to the documentation.

However this only works for Windows 7 /WinPE 3.0 (that comes with W7) images, not for pre Windows 7 images. Since you cannot have both WAIKs installed, there is now no way to add drivers to a Vista PE image when the new WAIK is installed.

Or am I missing something here ??

Bye,
Alex

66

(34 replies, posted in News)

Hi Muiz,

there is a new WAIK beta available now for Windows7 and Vista. That should make things easier :-)

67

(34 replies, posted in News)

Hi !

Answering my own post ....


1. WAIK did install on Windows 7. Must have done something wrong yesterday :-)
2. Mounting/Unmounting Windows 7 Images with imageX on Vista works fine. For driver injection dism.exe on Vista also works so one has to use both tools on Vista.

Bye,
Alex

68

(34 replies, posted in News)

Hi Muiz,

I was wondering ... since WAIK is currently not able to install on Windows 7 (at least out of the box) and dism.exe does not seem to be able to mount wim images on Vista how do you deal with two situations:

- when running on Windows 7 and you wish to mount Vista wim images for driver injection for instance ... do you use dism.exe ?

- when running on Vista and you wish to mount Windows 7 wim images for driver injection ... do you use imagex.exe to mount the Vista images ?

The following command works fine on Windows 7 but on Vista I get the "The mount-wim" option is unkown, error message even though I have copied the Dism.exe + DISM folder to the System32 directory and registered the dlls as you wrote in your guide ...

dism.exe /Mount-Wim /Wimfile:%WinImagex64% /index:%Index% /MountDir:%Mount%

What do you think ?

Bye,
Alex

69

(39 replies, posted in Vista-Tool)

Hi again,

ok, I have this working now.

First I am setting the variables (which I am not posting here), then I am doing this:


REM CREATE INDEX FILE OF Install.wim
"%WaikTools%\imagex.exe" /info %WinImagex64% > "%AIWTempx64%\indexinstallwim.txt"

REM FIND OUT IMAGECOUNT OF INSTALL.WIM
for /f "tokens=3" %%a in ('find /I "Image Count" "%AIWTempx64%\indexinstallwim.txt"') do set ImageCountMax=%%a

REM START WITH INDEX1 for IMAGECOUNT
set Index=1

REM SET STARTPOINT FOR INDEX LOOP
:startindex64

REM MOUNT WINDOWS IMAGE (install.wim) WITH CERTAIN INDEXOUNT
"%WaikTools%\imagex" /mountrw %WinImagex64% %Index% %Mount%


REM INTEGRATE DRIVERPACKS
%pkgmgr% /o:%Mount%;%Mount%\Windows /n:%driversxmlx64%


REM UNMOUNT WINDOWS IMAGE (install.wim)
"%WaikTools%\imagex" /unmount /commit %Mount%


REM IF INDEX IS LESS THAN MAX.IMAGECOUNT THEN ADD 1 TO INDEX AND GO BACK TO LOOP START
if %Index% LSS %ImageCountMax% set /A Index=%Index%+1 & goto :startindex64

I am doing the same thing later on for the 32bit install.wim (the above was for the 64bit install.wim). That way, I am integrating all driverpacks into all images of an install.wim (takes a VERY long time).

However, two things remain:

1. Can you guys tell me how you get pkgmgr to show the driver integration process for each driver? If I use the Vista Tool, cmd windows pop up showing this process. In my case, this does not happen, I see that the image was mounted, then I don´t see anything for a very long time (while the drivers are integrated) and later on the image is unmounted.

2. The fact that the drivers.xml is static is not very cool. I would like the script to adapt to different driverpaths automatically (for instance if I am copying the whole Installation folder to another drive or PC, the script should still work). So I guess I´d have to adapt the driverpath in the xml programmatically. Not very nice but seems to be the only way. Has someone here done that before ?


Bye,
Alex

70

(39 replies, posted in Vista-Tool)

Hi Shahed,

thanks for this info, however, this guide only describes a semiautomated process. One has to manually create an unattend.xml in WSIM. The Vistatool does not seem to need this or am I mistaken ? Isn´t it possible to tell pkmgr to integrate all drivers below a certain folder without this xml ??

Sorry, maybe those are just dumb questions but I am used to doing this for injecting drivers into boot.wim and it works just fine:

 

for /f "tokens=* delims=" %%i in ('dir %DriversSource%\$WinPEDriver$\Network /s /b /a:d') do ("%WaikTools%\..\PETools\peimg.exe" /inf="%%i\*.inf" %Mount% )

Why the need for this xml when dealing with install.wim ??

Bye,
Alex

71

(39 replies, posted in Vista-Tool)

Hi Muiz,

sorry to be so annoying but would you mind sharing with me which commands the Vista Tool issues to integrate the drivers into the Vista images ? I would like to script the slipstreaming process. Thanks a lot !

Bye,
Alex

72

(39 replies, posted in Vista-Tool)

Hi muiz,

1. Well, it would be good if a new driverpack could be slipstreamed over an old version but of course this would only be a viable solution if the older drivers in the image are getting replaced. I guess thats not the case right now. Maybe in the future ?

2. Updating all images in a wim could be done by scripting the Vista tool, no ? Any plans for adding this ?

3. Well, all you would have to do to support a WDS server boot is slipstream the LAN drivers (only those are necessary) into the boot.wim image like this:

imagex /mountrw boot.wim 2 %mountpoint%
peimg.exe /inf= *.inf %mountpoint%

Are you doing the same for the install.wim I guess or are you using another way to slipstream the drivers into the install.wim image ? (just curious)

Have a happy new year !
Alex

73

(39 replies, posted in Vista-Tool)

Hi muiz,

just 3 quick questions ... :-)

1. will we be able to slipstream future driverpacks into a wim image that already contains older driverpacks similar to the way it is being done with the DP base on WinXP ? Or do we have to start with a fresh image each time a new driverpack is being released ?

2. Why is it not possible to update all images in a wim simulationously ? Instead one has to choose the images one by one which takes a while with your basic Vista DVD because it contains so many vista editions. Is this planned for the future ?

3. When using a WDS server to distribute Vista images the network drivers have to be integrated into the boot.wim image in order for the WDS server to support booting the PE image over the network. Will you be able to do that in a future version of the Vista Tool ?

Thanks,
Alex

Wow, this is wierd.  Looks like the DPFinisher got confused.
Code:

PCI\VEN_1002&DEV_9589&SUBSYS_01BC1043&REV_00\4&2E5EAC9&0&0008: ATI Radeon HD 2600 PRO
<snip>
2008-07-18 19:29:52 : <FLTR>         ! Could not match +infFile"C:\D\G\A1\A_Hotfix.inf" through the HWID "PCI\VEN_1002&DEV_9589&SUBSYS_01BC1043" (original HWID: "PCI\VEN_1002&DEV_9589&SUBSYS_01BC1043&REV_00").
<snip>
2008-07-18 19:29:53 : <FLTR>         ! Could not match +infFile"C:\D\G\A1\CX_59746.inf" through the HWID "PCI\VEN_1002&DEV_9589&SUBSYS_01BC1043" (original HWID: "PCI\VEN_1002&DEV_9589&SUBSYS_01BC1043&REV_00").
<snip>
2008-07-18 19:29:53 : <FLTR>         ! Could not match +infFile"C:\D\G\A1\CX_59749.inf" through the HWID "PCI\VEN_1002&DEV_9589&SUBSYS_01BC1043" (original HWID: "PCI\VEN_1002&DEV_9589&SUBSYS_01BC1043&REV_00").
<snip>
2008-07-18 19:29:54 : <FLTR>         ! Could not match +infFile"C:\D\G\A1\mobility.inf" through the HWID "PCI\VEN_1002&DEV_9589&SUBSYS_01BC1043" (original HWID: "PCI\VEN_1002&DEV_9589&SUBSYS_01BC1043&REV_00").

It looks like the finisher was being ultra-exclusive in it's matches because it didn't ignore the &REV_00.
It even ignored the generic HWID present in the Hotfix .inf as well as the factory standard .inf (not to mention in the mobility.inf)
"ATI Radeon HD 2600 PRO" = ati2mtag_RV630, PCI\VEN_1002&DEV_9589

Overflow, any ideas here?

Hi !

But the driver was installed fine, no ? At least it seems so. Only the CCC did not get installed. Does this make sense ?

Bye,
Alex


Please use Code Tags next time, helps avoiding confusion among readers.
-- Helmi

Hi mr_smartepants,

yeah, sorry for that. Also I am sorry for not being able to give you a log of the failed DPG8.06G installation.
I will mail you the logfile. Yes, .Net was installed before and I remember CCC installs working (haven´t installed XP on one of my systems for months now).

Log will be there soon.
Bye,
Alex