MassStorage x64 (Page 1 of 3)

Will be in the next version, thx !

DONATE!
HWID's Tool     Read BEFORE you post

Is there any way you could add the Dell PERC 6/IR drivers (and preferably all of the PERC drivers) to the next release? I need them badly - I'd do it myself but I'm not sure how the mass storage pack works - I've got everything else (graphics/LAN/etc) working fine after i added some drivers to your existing driverpacks.

Since Vista dropped text mode setup, is there anything special about the mass storage pack anymore? I know it was strange in XP because of the txtsetup.oem files.

link to drivers:
http://bit.ly/i8j9V

They are for Win2K8 but work fine in Vista.

Thanks!

Last edited by emkinney (2009-03-13 08:03:32)

Updated to 903.1

DONATE!
HWID's Tool     Read BEFORE you post

It doesnt do that at my end , and not on many computers i installed.
So cant help you yet with this.

Updated to 903.2

DONATE!
HWID's Tool     Read BEFORE you post

I dont have that problem at my end, sorry

DONATE!
HWID's Tool     Read BEFORE you post

That was very diplomatic Fragbert...
I certainly hope it is well recieved by muiz.
He should be able to realize you are only trying to be helpful in the nicest possable way.

DP BartPE Tutorial   DP_BASE Tutorial   HWID's Tool     Read BEFORE you post    UserBars!

The DriverPacks, the DP_Base program, and Support Forum are FREE!.

I assumed you would make such a one-lined, dismissive and defensive reply. A pity.

Excuse me, but dont dare accuse me of spamming when I made ONE POST about this error less than a day ago! Somebody ELSE also brought this error up. You see, this is what happens when there is a genuine bug, multiple people will report it. What you should do is instead of getting all defensive saying that we are imagining things, is at least take note and make a genuine effort (time permitting) to reproduce the error - which I suspect you have not done as of yet. If you want to reproduce the error, simply run an x64 install with this x64 pack in a x64 VM. I guarantee you will see it.

People who develop these kinds of projects do so with the understanding that there are bugs and that people who report them are doing a SERVICE - not "whining" as you put it. You may not think so but we are very much helping you to improve the only decent Vista unattended integration tool in exisitence.

I understand completely that you have no time to constantly update a huge project like this - a reply from you saying as much is much better than "sorry, dont see it here, tough luck". A project like this most certainly should be an open group project much like XP driverpacks are now. The more people the better - but since this is Vista that will be hard to do since it is such a pariah in the unattended community.

I am not a programmer so the best I can offer you is reporting bugs and specifics on how they are reproduced - and I have quite a few now on Vista-Tools if you would be willing to listen instead of dismiss.

Hi guys,

I would call the Vista driverpacks section something like Vista-Win7 driverpacks section. Sooner or later, people will come flying to Windows 7 and then it won´t be such a pariah anymore :-) I myself use Win7 build 7056 exclusively now and except for some minor bugs have no complaint whatsoever.

Even Vista was not that bad over the last few months once you set your mind to it and learned a few new ways but it certainly was different from XP and we all know that people won´t learn new things unless they have to or unless they gain some profit from it. Hopefully Win7 will bring enough profit so people will adopt it.

As for the Vista driverpacks:

muiz, I really, really (really !) appreciate your efforts and your quick response to new driver updates etc.
I hope you can see that my reporting of bugs or problems is meant to help make the driverpacks better, it´s not just whining. :-)

I would very much like the Vista/Win7 driverpacks to go the driverpacks Base route with logging/testing etc.
It does work currently (at least I have found no major problem on my pcs except for the one jraid driver update) but it may be different on some other hardware or with different drivers.

If I can help in any way (I am no programmer except for some very light scripting but I can test) please tell me !

Bye,
Alex

PS: I m not using the Vistatool by the way because it does not work unattendedly and won´t integrate the drivers into all images of a wim (you have to do this manually one by one). Instead I have created a script that will integrate all DriverPacks automatically using the waik commandline tools and integrate it automatically into all available images of a wim. So the proble with the SI control panel on vmware is definitely a driverproblem not a vistatool problem.

I can post the scripts if people are interested or would like to adapt them (currently it does not have any logging)

Last edited by midiboy (2009-03-21 19:30:49)

Hi muiz,

I did not say at once but I do slipstream the drivers into all available images of a wim. From my script:

 

REM Create Indexfile of wim
"%WaikTools%\imagex.exe" /info %WinImagex32% > "%AIWTempx32%\indexinstallwim.txt"

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

REM START WITH INDEX1 for IMAGECOUNT
set Index=1

REM SET STARTPOINT FOR INDEX LOOP
:startindex32

REM MOUNT WINDOWS IMAGE (install.wim) WITH CERTAIN INDEXCOUNT
IF %WinOS%==Windows7 %dism% /Mount-Wim /Wimfile:%WinImagex32% /index:%Index% /MountDir:%Mount%
IF NOT %WinOS%==Windows7 "%WaikTools%\imagex" /mountrw %WinImagex32% %Index% %Mount%



ECHO Integrating Driverpacks into install.wim Image %Index% of %ImageCountMax% ... 
ECHO Please be VERY patient ...

REM INTEGRATE DRIVERPACKS
IF %WinOS%==Windows7 %dism% /image:%Mount% /apply-unattend:%DriversSource%\Driversxml\drivers_installwim_x32.xml
IF NOT %WinOS%==Windows7 start "" /wait %pkgmgr% /o:%Mount%;%Mount%\Windows /n:%DriversSource%\Driversxml\drivers_installwim_x32.xml

REM UNMOUNT WINDOWS IMAGE (install.wim)
IF %WinOS%==Windows7 %dism% /Unmount-Wim /MountDir:%Mount% /commit
IF NOT %WinOS%==Windows7 "%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 :startindex32

Thats just part of my script. It also automatically creates those drivers.xml files that Vista needs depending on the location of the drivers folder. The whole thing is a bit different for Win7.

I know it is just a commandline process, nothing advanced like C or vbs or powershell but it works.
So things are indeed possible ....

Bye,
Alex

Hi Again,

I think I may know why the SI Control panel is being installed ...
See this picture:
http://img205.imageshack.us/img205/4738/64544035.png

This is the driver details for my Western Digital Harddrive (connected to the onboard Intel ICH10 controller in AHCI mode). For some reason the harddrive uses the Silicon Image SiRemFil.sys driver although no SI controller is present on the system.

Can you do something about this, muiz ?
Bye,
Alex

The ICH10 controller uses the Intel iastor.sys driver.