/me embarrassed such obvious errors 
(comma returned to place)
1 2008-06-11 07:27:32
Re: [IMPL] ICPlus IP1000A Gigabit Ethernet NIC driver update (4 replies, posted in DriverPack LAN)
2 2008-06-10 05:18:51
Topic: [IMPL] ICPlus IP1000A Gigabit Ethernet NIC driver update (4 replies, posted in DriverPack LAN)
In DP\L\IC2, ver. 2.18.50113.
On http://www.icplus.com.tw/driver-pp-IP1000A.html ver. 2.22.51104
Both are 2005 year, old , but...
Also, W2k drivers are missing...
(edited LINK)
3 2007-07-14 05:05:16
Re: Sysprep mass storage section with DriverPacks Mass Storage (41 replies, posted in DriverPack Mass Storage)
I am similar inexact have explained what to rename in iastor??.inf
this line from [Strings] section
*PNP0600.DeviceDesc = "Intel AHCI Controller"
must be
*PNP0600.DeviceDesc = "Intel AHCI Controller ??"
because it used in service's Display name.
lines look kind of this
AddService = iaStor, %SPSVCINST_ASSOCSERVICE%, iaStor_Service_Inst, iaStor_EventLog_Inst
from section [*.Services]
must be
AddService = iaStor??, %SPSVCINST_ASSOCSERVICE%, iaStor_Service_Inst, iaStor_EventLog_Inst
IMHO, sysprep needs some kind of tricky mass storage drivers set, with non-overlapped drivers' and services' names.
Sysprep 'installs' these drives, so at boot, all they are loaded. But, pnp-setup will search drivers at all. And, searched drivers haven't to be same, what used in sysprep....
May we have driverpack with three parts inside?
1. drivers, not overlapped with other,
2.drivers, overlapped with other, in original form,
and 3. drivers, overlapped with other, modified to be non-overlapped.
Sysprep needs parts 1 and 3, pnp - parts 1 and 2.
Er?
4 2007-07-14 04:41:03
Re: [HOWTO] Using DriverPacks w/ Sysprep (Updated for BASE 7.04) (204 replies, posted in Universal Imaging)
BushLin wrote:
I wish someone had posted this information before, it's taken me way too much time by trial and error to work out which drivers can be added to SysprepMassStorage but I can now post something for others to use. This list is valid for MassStorage 7.07.1
MassStorage drivers tested and working in SysprepMassStorage without error:
A, AD (Not including 4), AM, AR, AT, AU, C, D, I, IN, IT, J, M, SI, VMMassStorage drivers not included in this list but may work ok:
3 (creates a service), AD\4 (driver signing comes up a few times even though disabled), E (w2k3 only error), H (File replace prompt), L (driver signing and file replace), P (driver signing), Q (testing)MassStorage drivers not included in this list due to total failure:
N (fails sysprep, registry error), S (way too many prompts, registry error), V (sysprep hang)Of those not included the biggest losses (for me) are Via and Nvidia as these are far more common than any of the raid controllers, if these can be fixed then the images made with the packs could be much closer to being truly universal. For now I'm just happy to get this many working.
Anyway, here's the list... remember to disable driver signing if you want it to finish without a single prompt.
Keep N/590SLI, it can handle most of NForce...
I have to exclude these drivers:
AD\4
E
IN\1\O
L\2, L\3
P\1, P\2, P\5
Q\
S\4
And my XP boot ok. P\? drivers cause some ntfs.sys error. Other can stop sysprep with registry error.
5 2007-07-12 07:40:26
Re: Sysprep mass storage section with DriverPacks Mass Storage (41 replies, posted in DriverPack Mass Storage)
I've tested 'syspreptestfiles' with renamed Intel drivers.
Bad news:
1. during system reseal, sysprep ask about every HWID entry (pointed to renamed driver) three times, and in log file there are smth about 'improper signed' driver. So, renamed drivers' signing goes off.
2. it's not works at all. All drivers are installed in 'iastor' driver entry in Services, and iastor's imagepath points to the last installed driver. In my case, it was iastor75.sys
3. I've changed *.inf fiels, so drivers' entries are names isator55, iastor62, iastor75. In such case, when sysprep seals system, iaStor75 doesn't install at all. So, I change display names of all three drivers. And drivers are installed and, when system boots, loaded and work. (but! I haven't real Intel devices to test...)
So, think, think.... drivers can be loaded in sysprep process, but driver signing is big trouble, I think... Can anybody (with MS driver toolkit) sign driver with self issued certificate and test to install?
6 2007-07-08 19:19:49
Re: Sysprep mass storage section with DriverPacks Mass Storage (41 replies, posted in DriverPack Mass Storage)
Sorry, I haven't test 'syspreptestfiles' yet...
About unsigned drivers:
1. disable driver signing policy with this bat file (I hope, sysprep's 'DriverSigningPolicy = Ignore' may help too)
@echo off
call :%1 2>nul
if errorlevel 1 goto usage
goto :EOF
:usage
echo Usage: %0 {disable/enable}
goto :EOF
:disable
set INF=%TEMP%\disable.inf
echo [Unicode]>"%INF%"
echo Unicode=no>>"%INF%"
echo [Registry Values]>>"%INF%"
echo MACHINE\Software\Microsoft\Driver Signing\Policy=3,^0>>"%INF%"
echo [Version]>>"%INF%"
echo signature="$CHICAGO$">>"%INF%"
echo Revision=^1>>"%INF%"
call :import "%INF%"
del "%INF%"
goto :EOF
:enable
set INF=%TEMP%\enable.inf
echo [Unicode]>"%INF%"
echo Unicode=no>>"%INF%"
echo [Registry Values]>>"%INF%"
echo MACHINE\Software\Microsoft\Driver Signing\Policy=3,^1>>"%INF%"
echo [Version]>>"%INF%"
echo signature="$CHICAGO$">>"%INF%"
echo Revision=^1>>"%INF%"
call :import "%INF%"
del "%INF%"
goto :EOF
:import
secedit /configure /cfg %1 /db "%TEMP%\secsetup.sdb" /log "%TEMP%\sec.log"
del "%TEMP%\secsetup.sdb"
del "%TEMP%\sec.log"
goto :EOF2. Windows ask about drivers' replacement when new driver replaces one Windows have inside, for example, D\M\AD\4\DPTI2O.SYS. I can't disable this. Anyone can help?
7 2007-06-26 07:56:32
Re: Sysprep mass storage section with DriverPacks Mass Storage (41 replies, posted in DriverPack Mass Storage)
Ok. I'll try it in two days...
8 2007-06-19 05:16:04
Re: Sysprep mass storage section with DriverPacks Mass Storage (41 replies, posted in DriverPack Mass Storage)
AFAIK sysprep, all mass storage drivers, pointed in sysprep.inf, are loaded during next boot time. And then, during boot, each driver will seek for supported hardware and still working or die.
In case of three different drivers for Intel storage controllers, ... hmm survive the last! Last, who be really last in sysprep.inf. In case of UNsigned drivers, of course.
Signed drives ... I don't know exactly, it's seems to be what Windows keep latest version.
//off topic - how do you edit Intel *.inf files and keep Microsoft HW compatibility sign?
So, it's a sad. While some Intel HW supported by MS drivers, MS drivers can save us. And, of course, only one Intel driver can be used in sysprep. IMO, even we rename drivers and try to load all three at once, they are can interfere each other and crash. So, sysprep-er need to choose Proper Driver for his hardware. And pray.
Universal sysprep image for Intel storage controllers is impossible. Just use latest driver. Or (and) build different images.
I'm sad.
9 2007-06-17 08:00:31
Re: Sysprep mass storage section with DriverPacks Mass Storage (41 replies, posted in DriverPack Mass Storage)
In my tests, these drivers' IDs' needs to be excluded from sysprep.inf:
AD\4
IN\1\O
L\2, L\3
P\1, P\2, P\5
Q\
S\4
all other 'older' versions, like IN\1\O - out
With such set, SYSPREPed image boots ok.
But, I'v built sysprep.inf from DriverPack_MassStorage_wnt5_x86-32.ini, not from *.inf files.
10 2007-06-17 07:23:04
Topic: [SOLVED] RSS update tracker broken! (2 replies, posted in Site & Forum Issues And Feedback)
Please, fix it.
Update tracker here http://driverpacks.net/DriverPacks/UpdateTracker.php works fine, but here
http://driverpacks.net/DriverPacks.xml was not updated since "Last-Modified: Tue, 03 Apr 2007 22:27:26 GMT"