http://driverpacks.sytes.net/driverpack … 32_810B.7z

10.64.10.3 you mean.

link pulled by jaak
Nightlies/DP_Chipset_wnt5_x86-32_810B.7z

Done days ago! big_smile

The issued should be fixed in 8.10A

http://driverpacks.sytes.net/driverpack … 32_810A.7z

This was fixed a while ago in the chipset nightlie, it's not official yet but it will be soon.

I'm on it.

http://driverpacks.sytes.net/driverpack … 32_810A.7z

Mr.Smartepants is already aware and is working on an update.

New nightlie:

http://driverpacks.sytes.net/driverpack … 32_809D.7z

PCI\VEN_1002&DEV_4390
PCI\VEN_1002&DEV_439C

are not part of ATI 8.9 South Bridge driver....

SamLab can you please post the link of your working driver ?

I normally face the machine in the direction of the server, and point with my finger... wink

That was a good one! big_smile

By copying all drivers from PE, do you mean that I could pick out specific drivers from PE that the image would install when the mini setup starts?

Well OfflineSysprep is not perfect yet. I know Galapo and TheCharlic are working on version 2 which should add big improvements like unattended usage. For now, OfflineSysprep 1.9.02 has an option called "extra driver pack" which is what your looking for. Unfortunately I did not have any success with it so far. However, I'm still running test and when I'll find the solution I will tell everyone I promise. If we have more people testing this and reporting valuable informations I'm sure Galapo will help us as usual. Good luck and plz report back!

It's normal because your host pc or vmware image use a different network driver. So how your suppose to read the drivers network share if you have no network driver installed in 1st place ? Plus sysprep resets the network settings at the 1st boot.

The best way to get around this would be to boot in windows PE and use offlinesysprep to deploy your image. with offline sysprep you can inject the single mass storage driver that is detected in your PE, so you don't need those drivers in your cd or image. Plus you can copy on your image all your drivers from the PE.

I noticed similar issue too. I'm still searching on what the exact cause is. That's strange because it works fine in PE. So I injected the amss driver from the PE and when I boot in windows I get the 007B error. I'll post more details as soon as I can.

213

(6 replies, posted in DriverPack Mass Storage)

Same for D4 folder....damn adaptec.

Like you mention there is a newer version of the driver which is 1.17.41.1 but it's beta. When it will be WHQL I will update it. For now, you can test it on your own.

ftp://driver.jmicron.com.tw/jmb36x/Win2 … .41.01.zip

I'll take care of it when I have some time on my hands.

strange 0x0000007E usually means you have the Intel PPM service started on a AMD PC.

So basically you want us to update the JMicron driver ?

Jaak the driver was simply missing from the pack ? Where are you going with this ?

Done, http://driverpacks.sytes.net/driverpack … 32_809B.7z

Done, http://driverpacks.sytes.net/driverpack … 32_809B.7z

221

(7 replies, posted in DriverPack LAN)

Try this abdou http://driverpacks.sytes.net/driverpack … 32_809B.7z

222

(7 replies, posted in DriverPack LAN)

abdou, I've looked on Microsoft Update Catalog website and the via rhine II driver is more recent than via own web site. Good JOB VIA. So hopefully your problem will be fixed in the next test pack which I will release soon.

If the sysprep process never ends, it means that either a path or a inf file name is wrong. When you update the DP Mass storage pack you must redo your whole PNP list. Good Luck!

Already done my friend days ago. So you really thought you could be faster ? big_smile

older link pulled by Jaak
sytes.net/driverpacks/Nightlies/DP_Chipset_wnt5_x86-32_808C.7z

It means IMPLEMENTED. So your driver should be available in the last wlan pack.