You are not logged in. Please login or register.
Active topics Unanswered topics
Search options
jtdoom wrote:It's amazing that a single comma or carriage return can break this.. But that is what can happen.
Any small typo can break this. 
Like an underscore that goes missing (it is a a mystery how that happened).
Some people take the time to figure out what went wrong when it goes critically wrong, and detailed reports do help. We do need some extra testers, and people who already make their own modifictions can tell us how to make better modifications.
We need Dr Watsons too.. Yesterday proved this, don't you think?
I know what you mean WRT typos, the number of times I have shouted at my AutoIt scripts saying they are right before clearing my eyes, seeing the missing bracket or quote and then quietly fixing it goes into high double digits.
I have just rebuilt my disc and it works perfectly, thank you. Regarding testing I only have 3 machines, all Nvidia gfx, one with RAID array, one laptop (always have probs with the DP Nvidia gfx so use the OEMs), when the DriverPacks are released a rebuild is done and tested on all 3 and if there are any problems I try to sort of post on the forums.
I do sometimes have the time to spend (on a 4 on 4 off shift pattern), but will take some time to understand the ini, unless there is a readme somewhere. If there is anything I can do that fits my setup, let me know and I will try, this is the type of project that needs to stay alive and if more people help it lessens the burden of others.
jtdoom wrote:if the old are supported, the AR-1 can safely go.
EDIT; matter of fact, the BSOD is probably caused by loading two different SYS files for same chip.
I am looking at a Silicon-Image update at the moment, and can do this while I am at it.
Sweet, thanks
jtdoom wrote:the line
ms_1_tag = "arecsasr" is because both drivers use arcm_x86.sys
when Base creates the cabs for txtmode, it gives the second one another name, and in this case that is arecsasr.sys.
since second one has SAS.. areca SAS RAID , this seemed good enough to describe it.
once plug and play loads, the newer one should get picked.
your idea of removing the INF for the controller from that older driverset is good, if you also remove its HWID in AR-1
btw, thanks for reporting in that other topic.
The typo I made this morning (had worked all night) made people look for the cause, and then they revealed older errors as well.
No probs, I did remove the HWID for my model the old way that I did it but, with the latest DP version I don't have to, the only problem is the BSOD when the ms_1_tag = "arecsasr".
I use Siginets integrator to slipstream the drivers and that uses the DP api, could this cause the BSOD problem?. If I understand right when the txtsetup.sif file is updated with the massstorage drivers the ones from [AR-1] will not be included as I have ms_1_tag = "arcm_x86" for both AR-1 and AR-2 and the arcm_x86 value in the sif file will be overwritten with the device name from [AR-2], if that makes sense :-)
I cannot think of a reason for the BSOD but if I cannot get it to work with the different tag lines would it be a possibility just to have the newer drivers in the DP instead of both?. I know new cards are supported with the new drivers but the old cards are also supported.
Thanks.
jtdoom wrote:Hi
I advise you first look at AR\1.. and AR\2 and the mass storage ini.
If I missed something you normally include, report asap.
EDIT, since it used a different sys-size and had support for newer models, I did not update, but add the driver.
The way you have done it is similar to the way I used. I created the 2nd folder and added the same files - the oem and pdb, I also deleted the arc1220.inf from the [AR-1] and edited the [AR-2] ms_1_hwids to just have the PCI\VEN info for my model (arc1220).
Upon my first try after changing the ini WRT the hpcissm2 problem I got a BSOD upon start of the GUI portion, no file name listed just the mem address. I tried a few variations and rebuilds and found that if the ms_1_tag line under [AR-2] is changed then no BSOD.
change
to
Is there a reason why you named it arecsasr, I am new to editing the driverpacks and don't fully understand the "ms_" lines.
Thanks again for this.
jtdoom wrote:huh? is there a carriage return there?
that's difficult to spot.
Yep there is\was a carriage return, the "PCI\VEN_" info was on a separate line.
Would you like me to post a bug report, there seem to be a lot of people starting new threads about the prob in the feedback forum without searching.
you will need to edit the DriverPack_MassStorage_wnt5_x86-32.ini file and repack the drivers until its fixed officially.
change
[C-2]
ms_count = 1
ms_1_deviceName = "Compaq server HP ProLiant E200/E200i/P400/P400i/P600"
ms_1_tag = "hpcissm2"
ms_1_sysFile = "hpcissm2.sys"
ms_1_hwids =
"PCI\VEN_103C&DEV_3220&SUBSYS_3225103C,PCI\VEN_103C&DEV_3230&SUBSYS_3234103C,PCI\VEN_103C&DEV_3230&SUBSYS_3235103C,PCI\VEN_103C&DEV_3238&SUBSYS_3212103C,PCI\VEN_103C&DEV_3238&SUBSYS_3211103C"
ms_1_isBusExtender = false
ms_1_exc_skipIfOS = "w2k"
to
[C-2]
ms_count = 1
ms_1_deviceName = "Compaq server HP ProLiant E200/E200i/P400/P400i/P600"
ms_1_tag = "hpcissm2"
ms_1_sysFile = "hpcissm2.sys"
ms_1_hwids = "PCI\VEN_103C&DEV_3220&SUBSYS_3225103C,PCI\VEN_103C&DEV_3230&SUBSYS_3234103C,PCI\VEN_103C&DEV_3230&SUBSYS_3235103C,PCI\VEN_103C&DEV_3238&SUBSYS_3212103C,PCI\VEN_103C&DEV_3238&SUBSYS_3211103C"
ms_1_isBusExtender = false
ms_1_exc_skipIfOS = "w2k"
jtdoom wrote:Hi benners,
done, and released.
Hi jtdoom
thanks for this, I'll rebuild the disc later and post back.
For sometime I have been editing the massstorage DP to add these updated drivers. I have had no problems since using them and they also detect the areca raid virtual device. The drivers in the massstorage DP do not contain the inf file for this so a dialog pops up during GUIRunOnce asking for the drivers.
I sometimes forget to edit the DP after downloading the latest version and then I'm fooked, any chance of including them?.
thanks
Link for x86 WinXP
release txt
******************************************************************************************
**
** ARECA "SATA PCI RAID" Driver Release
**
******************************************************************************************
** History:
** REV# DATE DESCRIPTION
** 1.00.00.00 03/31/2004 First release
** 1.01.00.00 11/29/2004 Bug fix with Bus reset if PHY error(Device error)
** 1.02.00.00 06/29/2005 Bug fix with abort command,add ARC1x70 serial adapters support
** 1.20.00.13 11/29/2005 add ioctl code 'ARCMSR_IOCTL_FLUSH_ADAPTER_CACHE',
** customer can send this command for sync its raid volume data,
** Bug fix with abort command,
** scheduling pending ccb with first in first out
** add scsi device "iop processor" id 16
** 7/29/2006 add SAS RAID adapters support
** 6.20.00.14 03/22/2007 Bug on shutdown notify
I am having a problem using Siginets Integrator to slipstream my driverpacks with the new DPs_BASE v6.12. I can slipstream the packs using DPs_BASE.exe with no problem but when using the "Run a program after Integration" option in Siginets program I get the error message below. Is this a problem with the api?, previous versions have always worked. I have also posted this on Siginets forum Here. If its a bug I will post it on the bug tracker but just wanted to make sure first.
Bâshrat the Sneaky wrote:I already thought I had not seen such reports...
All I need at the moment are your hwids. And indeed, please post it in the correct forum: DriverPack Graphics.
Thanks, bit of a typo at the end, should have been a full stop not a question mark DOH!.
Bâshrat the Sneaky wrote:benners wrote:Well, tested and it works fine, drivers got copied and when I plugged my scanner in the drivers were loaded, thanks again Bashrat.
The 3 directory makes it better for me as I don't want all of the drivers in my packs copied over, I have an exe in my 3rd party pack that is copied to C:\D\A\1 and deletes all the ATI files and folders leaving only the exes, I had to do this because I always got BSOD due to the ATI2mtag.sys in the Graphics Pack A drivers. I tried adding the Radeon 8500 drivers to my pack but the the ones in Graphics Pack A always got selected, even Microsofts updated driver blue screened. I also had probs with the NVIDIA drivers for my Go5700 so this was a less hassle free way.
I can put any drivers for scanners and printers in the 3 dir and leave the rest in D. :-), saving space.
We can solve these issues. Did you report them in the past?
Nope, I thought it would be easier for me to do as is than mither folks about something I can sort, but it would be easier to just use the packs, what info besides the hwids would be needed? then I'll post in the correct forum?
Well, tested and it works fine, drivers got copied and when I plugged my scanner in the drivers were loaded, thanks again Bashrat.
The 3 directory makes it better for me as I don't want all of the drivers in my packs copied over, I have an exe in my 3rd party pack that is copied to C:\D\A\1 and deletes all the ATI files and folders leaving only the exes, I had to do this because I always got BSOD due to the ATI2mtag.sys in the Graphics Pack A drivers. I tried adding the Radeon 8500 drivers to my pack but the the ones in Graphics Pack A always got selected, even Microsofts updated driver blue screened. I also had probs with the NVIDIA drivers for my Go5700 so this was a less hassle free way.
I can put any drivers for scanners and printers in the 3 dir and leave the rest in D. :-), saving space.
Thanks Bashrat, changing dir structure now.
No problems here with the driverpacks.
@Asrod
The BartPE platform is a work in progress http://forum.driverpacks.net/viewtopic.php?id=351
Nope similar error here, error says Copy drivers inside "C:\D\3" to "C:\WINDOWS\DriverPacks\D\3" I only saved third party driver packs and none contain a directory called 3 and none of the drivers were copied. looks like were getting there though :-)
2006-08-25 09:19:10 : <INIT> DriverPacks Finisher 6.08.6 initialized.
2006-08-25 09:19:10 : <INIT> Detected platform wnt5_x86-32.
2006-08-25 09:19:10 : <INIT> Start logging of the HWIDs for relevant devices present in this system.
2006-08-25 09:19:10 : <INIT> 1. ACPI devices
ACPI\ACPI0003\2&DABA3FF&0 : Microsoft AC Adapter
ACPI\FIXEDBUTTON\2&DABA3FF&0 : ACPI Fixed Feature Button
ACPI\GENUINEINTEL_-_X86_FAMILY_15_MODEL_2\_0 : Intel(R) Pentium(R) 4 CPU 3.40GHz
ACPI\GENUINEINTEL_-_X86_FAMILY_15_MODEL_2\_1 : Intel(R) Pentium(R) 4 CPU 3.40GHz
ACPI\PNP0000\4&369939D9&0 : Programmable interrupt controller
ACPI\PNP0100\4&369939D9&0 : System timer
ACPI\PNP0200\4&369939D9&0 : Direct memory access controller
ACPI\PNP0303\4&369939D9&0 : Standard 101/102-Key or Microsoft Natural PS/2 Keyboard
ACPI\PNP0401\3 : ECP Printer Port (LPT1)
ACPI\PNP0501\0 : Communications Port (COM1)
ACPI\PNP0700\0 : Standard floppy disk controller
ACPI\PNP0800\4&369939D9&0 : System speaker
ACPI\PNP0A03\2&DABA3FF&0 : PCI bus
ACPI\PNP0A05\4&369939D9&0 : Generic Bus
ACPI\PNP0B00\4&369939D9&0 : System CMOS/real time clock
ACPI\PNP0C02\1F : Motherboard resources
ACPI\PNP0C04\4&369939D9&0 : Numeric data processor
ACPI\PNP0C09\4&369939D9&0 : Microsoft ACPI-Compliant Embedded Controller
ACPI\PNP0C0A\1 : Microsoft ACPI-Compliant Control Method Battery
ACPI\PNP0C0C\3&61AAA01&0 : ACPI Power Button
ACPI\PNP0C0D\2&DABA3FF&0 : ACPI Lid
ACPI\PNP0C0E\2&DABA3FF&0 : ACPI Sleep Button
ACPI\PNP0F13\4&369939D9&0 : Synaptics PS/2 Port Pointing Device
ACPI\THERMALZONE\THRM : ACPI Thermal Zone
ACPI_HAL\PNP0C08\0 : Microsoft ACPI-Compliant System
ROOT\ACPI_HAL\0000 : ACPI Multiprocessor PC
26 matching device(s) found.
2006-08-25 09:19:11 : <INIT> 2. PCI devices
PCI\VEN_104C&DEV_8023&SUBSYS_00451025&REV_00\4&3A321F38&0&10F0: Texas Instruments OHCI Compliant IEEE 1394 Host Controller
PCI\VEN_10DE&DEV_0348&SUBSYS_00451025&REV_A1\4&56EB5F&0&0008: NVIDIA GeForce FX Go5700
PCI\VEN_14E4&DEV_169C&SUBSYS_00451025&REV_03\4&3A321F38&0&00F0: Broadcom NetLink (TM) Gigabit Ethernet
PCI\VEN_14E4&DEV_4320&SUBSYS_1220185F&REV_03\4&3A321F38&0&18F0: WLAN 802.11g mini-PCI Module
PCI\VEN_1524&DEV_1410&SUBSYS_00451025&REV_01\4&3A321F38&0&08F0: ENE CB1410 Cardbus Controller
PCI\VEN_8086&DEV_244E&SUBSYS_00000000&REV_C2\3&61AAA01&0&F0 : Intel(R) 82801 PCI Bridge - 244E
PCI\VEN_8086&DEV_24D0&SUBSYS_00000000&REV_02\3&61AAA01&0&F8 : Intel(R) 82801EB LPC Interface Controller - 24D0
PCI\VEN_8086&DEV_24D2&SUBSYS_00451025&REV_02\3&61AAA01&0&E8 : Intel(R) 82801EB USB Universal Host Controller - 24D2
PCI\VEN_8086&DEV_24D4&SUBSYS_00451025&REV_02\3&61AAA01&0&E9 : Intel(R) 82801EB USB Universal Host Controller - 24D4
PCI\VEN_8086&DEV_24D5&SUBSYS_00451025&REV_02\3&61AAA01&0&FD : Realtek AC'97 Audio
PCI\VEN_8086&DEV_24D6&SUBSYS_00451025&REV_02\3&61AAA01&0&FE : Agere Systems AC'97 Modem
PCI\VEN_8086&DEV_24D7&SUBSYS_00451025&REV_02\3&61AAA01&0&EA : Intel(R) 82801EB USB Universal Host Controller - 24D7
PCI\VEN_8086&DEV_24DB&SUBSYS_00451025&REV_02\3&61AAA01&0&F9 : Intel(R) 82801EB Ultra ATA Storage Controllers
PCI\VEN_8086&DEV_24DD&SUBSYS_00451025&REV_02\3&61AAA01&0&EF : Intel(R) 82801EB USB2 Enhanced Host Controller - 24DD
PCI\VEN_8086&DEV_2570&SUBSYS_00000000&REV_02\3&61AAA01&0&00 : Intel(R) 82865G/PE/P/GV/82848P Processor to I/O Controller - 2570
PCI\VEN_8086&DEV_2571&SUBSYS_00000000&REV_02\3&61AAA01&0&08 : Intel(R) 82865G/PE/P/GV/82848P Processor to AGP Controller - 2571
16 matching device(s) found.
2006-08-25 09:19:11 : <INIT> 3. HDAUDIO devices
No matching devices found.
2006-08-25 09:19:11 : <INIT> 4. USB devices
USB\ROOT_HUB\4&2044FEE0&0 : USB Root Hub
USB\ROOT_HUB\4&76C8FEE&0 : USB Root Hub
USB\ROOT_HUB\4&ED9212F&0 : USB Root Hub
USB\ROOT_HUB20\4&1362C802&0 : USB Root Hub
USB\VID_1025&PID_0045\018866798844 : USB Mass Storage Device
USB\VID_1241&PID_1111\5&B49E57D&0&1 : USB Human Interface Device
USBSTOR\DISK&VEN_USB2.0&PROD_CARDREADER_CF_RW&REV_0814\018866798844&0: USB2.0 CardReader CF RW USB Device
USBSTOR\DISK&VEN_USB2.0&PROD_CARDREADER_COMBO&REV_0814\018866798844&1: USB2.0 CardReader Combo USB Device
8 matching device(s) found.
2006-08-25 09:19:11 : <INIT> Logging of HWIDs complete.
2006-08-25 09:19:11 : <INIT> Processed settings.
2006-08-25 09:19:11 : <FLTR> Collected the HWIDs for this system.
2006-08-25 09:19:11 : <FLTR> Verifying requirements for exception [wnt5_x86-32__0001__D-G-A-1] (1 of 22 exceptions).
2006-08-25 09:19:11 : <FLTR> 1. tagFiles (ALL tagFiles must be found)
2006-08-25 09:19:11 : <FLTR> Found tagfile "C:\ATICCC.ins" (1/2).
2006-08-25 09:19:11 : <FLTR> Found tagfile "C:\D\G\A\1\ATICCC.exe" (2/2).
2006-08-25 09:19:11 : <FLTR> 4. +infFiles (ANY +infFiles must be matched)
2006-08-25 09:19:11 : <FLTR> Wildcard specified for +infFiles requirement: scan for .inf files (1 of 1 +infFiles).
2006-08-25 09:19:11 : <FLTR> Checking .inf file 'C:\D\G\A\1\C2_34826.inf'.
2006-08-25 09:19:13 : <FLTR> Checking .inf file 'C:\D\G\A\1\CX_34826.inf'.
2006-08-25 09:19:14 : <FLTR> Checking .inf file 'C:\D\G\A\1\E2_34826.inf'.
2006-08-25 09:19:14 : <FLTR> Checking .inf file 'C:\D\G\A\1\EX_34826.inf'.
2006-08-25 09:19:14 : <FLTR> Checking .inf file 'C:\D\G\A\1\MX_34826.inf'.
2006-08-25 09:19:15 : <FLTR> ! Could not match any of the +infFiles.
2006-08-25 09:19:15 : <FLTR> => This exception will not be applied.
2006-08-25 09:19:15 : <FLTR> Verifying requirements for exception [wnt5_x86-32__0002__D-G-A-1] (2 of 22 exceptions).
2006-08-25 09:19:15 : <FLTR> 1. tagFiles (ALL tagFiles must be found)
2006-08-25 09:19:15 : <FLTR> ! Could not find tagfile 'C:\ATICCP.ins' (1 of 2 tagfiles).
2006-08-25 09:19:15 : <FLTR> => This exception will not be applied.
2006-08-25 09:19:15 : <FLTR> Verifying requirements for exception [wnt5_x86-32__0021__D-G-A-2] (3 of 22 exceptions).
2006-08-25 09:19:15 : <FLTR> 1. tagFiles (ALL tagFiles must be found)
2006-08-25 09:19:15 : <FLTR> Found tagfile "C:\ATICCC.ins" (1/2).
2006-08-25 09:19:15 : <FLTR> Found tagfile "C:\D\G\A\1\ATICCC.exe" (2/2).
2006-08-25 09:19:15 : <FLTR> 4. +infFiles (ANY +infFiles must be matched)
2006-08-25 09:19:15 : <FLTR> ! Could not match any of the +infFiles.
2006-08-25 09:19:15 : <FLTR> => This exception will not be applied.
2006-08-25 09:19:15 : <FLTR> Verifying requirements for exception [wnt5_x86-32__0022__D-G-A-2] (4 of 22 exceptions).
2006-08-25 09:19:15 : <FLTR> 1. tagFiles (ALL tagFiles must be found)
2006-08-25 09:19:15 : <FLTR> ! Could not find tagfile 'C:\ATICCP.ins' (1 of 2 tagfiles).
2006-08-25 09:19:15 : <FLTR> => This exception will not be applied.
2006-08-25 09:19:15 : <FLTR> Verifying requirements for exception [wnt5_x86-32__0003__D-G-A-3] (5 of 22 exceptions).
2006-08-25 09:19:15 : <FLTR> 1. tagFiles (ALL tagFiles must be found)
2006-08-25 09:19:15 : <FLTR> Found tagfile "C:\D\G\A\3\CPanel.exe" (1/1).
2006-08-25 09:19:15 : <FLTR> 4. +infFiles (ANY +infFiles must be matched)
2006-08-25 09:19:15 : <FLTR> ! Could not match any of the +infFiles.
2006-08-25 09:19:15 : <FLTR> => This exception will not be applied.
2006-08-25 09:19:15 : <FLTR> Verifying requirements for exception [wnt5_x86-32__0004__D-G-3-1] (6 of 22 exceptions).
2006-08-25 09:19:15 : <FLTR> 1. tagFiles (ALL tagFiles must be found)
2006-08-25 09:19:15 : <FLTR> ! Could not find tagfile 'C:\WINDOWS\system32\3dfxV2ps.dll' (1 of 1 tagfiles).
2006-08-25 09:19:15 : <FLTR> => This exception will not be applied.
2006-08-25 09:19:15 : <FLTR> Verifying requirements for exception [wnt5_x86-32__0005__D-G-S-1] (7 of 22 exceptions).
2006-08-25 09:19:15 : <FLTR> 1. tagFiles (ALL tagFiles must be found)
2006-08-25 09:19:15 : <FLTR> ! Could not find tagfile 'C:\WINDOWS\system32\drivers\sigrp.sys' (1 of 1 tagfiles).
2006-08-25 09:19:15 : <FLTR> => This exception will not be applied.
2006-08-25 09:19:15 : <FLTR> Verifying requirements for exception [wnt5_x86-32__0006__D-L-NV-123] (8 of 22 exceptions).
2006-08-25 09:19:15 : <FLTR> 2. +hwids (ANY +hwids must be matched)
2006-08-25 09:19:15 : <FLTR> ! Could not match any of the +hwids.
2006-08-25 09:19:15 : <FLTR> => This exception will not be applied.
2006-08-25 09:19:15 : <FLTR> Verifying requirements for exception [wnt5_x86-32__0007__D-S-CR-1] (9 of 22 exceptions).
2006-08-25 09:19:15 : <FLTR> 1. tagFiles (ALL tagFiles must be found)
2006-08-25 09:19:15 : <FLTR> ! Could not find tagfile 'C:\WINDOWS\system32\drivers\ha20x2k.sys' (1 of 2 tagfiles).
2006-08-25 09:19:15 : <FLTR> => This exception will not be applied.
2006-08-25 09:19:15 : <FLTR> Verifying requirements for exception [wnt5_x86-32__0008__D-S-CR-2] (10 of 22 exceptions).
2006-08-25 09:19:15 : <FLTR> 1. tagFiles (ALL tagFiles must be found)
2006-08-25 09:19:15 : <FLTR> ! Could not find tagfile 'C:\WINDOWS\system32\drivers\ha10x2k.sys' (1 of 3 tagfiles).
2006-08-25 09:19:15 : <FLTR> => This exception will not be applied.
2006-08-25 09:19:15 : <FLTR> Verifying requirements for exception [wnt5_x86-32__0009__D-S-CR-3] (11 of 22 exceptions).
2006-08-25 09:19:15 : <FLTR> 1. tagFiles (ALL tagFiles must be found)
2006-08-25 09:19:15 : <FLTR> ! Could not find tagfile 'C:\WINDOWS\system32\drivers\P17.sys' (1 of 2 tagfiles).
2006-08-25 09:19:15 : <FLTR> => This exception will not be applied.
2006-08-25 09:19:15 : <FLTR> Verifying requirements for exception [wnt5_x86-32__0010__D-S-H-2] (12 of 22 exceptions).
2006-08-25 09:19:15 : <FLTR> 4. +infFiles (ANY +infFiles must be matched)
2006-08-25 09:19:15 : <FLTR> ! Could not match any of the +infFiles.
2006-08-25 09:19:15 : <FLTR> => This exception will not be applied.
2006-08-25 09:19:15 : <FLTR> Verifying requirements for exception [wnt5_x86-32__0011__D-S-N] (13 of 22 exceptions).
2006-08-25 09:19:15 : <FLTR> 1. tagFiles (ALL tagFiles must be found)
2006-08-25 09:19:15 : <FLTR> ! Could not find tagfile 'C:\WINDOWS\system32\drivers\nvapu.sys' (1 of 1 tagfiles).
2006-08-25 09:19:15 : <FLTR> => This exception will not be applied.
2006-08-25 09:19:15 : <FLTR> Verifying requirements for exception [wnt5_x86-32__0012__D-S-S-U] (14 of 22 exceptions).
2006-08-25 09:19:15 : <FLTR> 1. tagFiles (ALL tagFiles must be found)
2006-08-25 09:19:15 : <FLTR> ! Could not find tagfile 'C:\WINDOWS\system32\drivers\sthda.sys' (1 of 1 tagfiles).
2006-08-25 09:19:15 : <FLTR> => This exception will not be applied.
2006-08-25 09:19:15 : <FLTR> Verifying requirements for exception [wnt5_x86-32__0013__D-S-SI-1] (15 of 22 exceptions).
2006-08-25 09:19:15 : <FLTR> 1. tagFiles (ALL tagFiles must be found)
2006-08-25 09:19:15 : <FLTR> ! Could not find tagfile 'C:\WINDOWS\system32\drivers\sis7012.sys' (1 of 1 tagfiles).
2006-08-25 09:19:15 : <FLTR> => This exception will not be applied.
2006-08-25 09:19:15 : <FLTR> Verifying requirements for exception [wnt5_x86-32__0014__D-S-SI-2] (16 of 22 exceptions).
2006-08-25 09:19:15 : <FLTR> 1. tagFiles (ALL tagFiles must be found)
2006-08-25 09:19:15 : <FLTR> ! Could not find tagfile 'C:\WINDOWS\system32\drivers\sis7018.sys' (1 of 1 tagfiles).
2006-08-25 09:19:15 : <FLTR> => This exception will not be applied.
2006-08-25 09:19:15 : <FLTR> Verifying requirements for exception [wnt5_x86-32__0015__D-S-T-2] (17 of 22 exceptions).
2006-08-25 09:19:15 : <FLTR> 1. tagFiles (ALL tagFiles must be found)
2006-08-25 09:19:15 : <FLTR> ! Could not find tagfile 'C:\WINDOWS\system32\drivers\FM801.sys' (1 of 1 tagfiles).
2006-08-25 09:19:15 : <FLTR> => This exception will not be applied.
2006-08-25 09:19:15 : <FLTR> Verifying requirements for exception [wnt5_x86-32__0016__D-S-T-3] (18 of 22 exceptions).
2006-08-25 09:19:15 : <FLTR> 1. tagFiles (ALL tagFiles must be found)
2006-08-25 09:19:15 : <FLTR> ! Could not find tagfile 'C:\WINDOWS\system32\drivers\cmaudio.sys' (1 of 1 tagfiles).
2006-08-25 09:19:15 : <FLTR> => This exception will not be applied.
2006-08-25 09:19:15 : <FLTR> Verifying requirements for exception [wnt5_x86-32__0017__D-S-T-4] (19 of 22 exceptions).
2006-08-25 09:19:15 : <FLTR> 1. tagFiles (ALL tagFiles must be found)
2006-08-25 09:19:15 : <FLTR> ! Could not find tagfile 'C:\WINDOWS\system32\drivers\TT1724ht.sys' (1 of 1 tagfiles).
2006-08-25 09:19:15 : <FLTR> => This exception will not be applied.
2006-08-25 09:19:15 : <FLTR> Verifying requirements for exception [wnt5_x86-32__0018__D-S-T-5] (20 of 22 exceptions).
2006-08-25 09:19:15 : <FLTR> 1. tagFiles (ALL tagFiles must be found)
2006-08-25 09:19:15 : <FLTR> ! Could not find tagfile 'C:\WINDOWS\system32\drivers\dmxsens.sys' (1 of 1 tagfiles).
2006-08-25 09:19:15 : <FLTR> => This exception will not be applied.
2006-08-25 09:19:15 : <FLTR> Verifying requirements for exception [wnt5_x86-32__0019__D-S-V-1] (21 of 22 exceptions).
2006-08-25 09:19:15 : <FLTR> 1. tagFiles (ALL tagFiles must be found)
2006-08-25 09:19:15 : <FLTR> ! Could not find tagfile 'C:\WINDOWS\system32\drivers\envysens.sys' (1 of 1 tagfiles).
2006-08-25 09:19:15 : <FLTR> => This exception will not be applied.
2006-08-25 09:19:15 : <FLTR> Verifying requirements for exception [wnt5_x86-32__0020__D-S-V-2] (22 of 22 exceptions).
2006-08-25 09:19:15 : <FLTR> 1. tagFiles (ALL tagFiles must be found)
2006-08-25 09:19:15 : <FLTR> ! Could not find tagfile 'C:\WINDOWS\system32\drivers\vinyl97.sys' (1 of 2 tagfiles).
2006-08-25 09:19:15 : <FLTR> => This exception will not be applied.
2006-08-25 09:19:15 : <FLTR> Finished filtering exceptions.
2006-08-25 09:19:15 : <EXEC> No exceptions left to execute: none have met all requirements!
2006-08-25 09:19:15 : <KTD> KTD cache location set: "C:\WINDOWS\DriverPacks".
2006-08-25 09:19:15 : <KTD> KTD is enabled, in PATHS mode.
2006-08-25 09:19:15 : <KTD> Copy drivers inside "C:\D\3" to "C:\WINDOWS\DriverPacks\D\3".
2006-08-25 09:19:15 : <ERR> Could not apply KTD on "C:\D\3", since it does not exist!
2006-08-25 09:19:20 : <KTD> Successfully created the "%KTD%" environment variable, it has been set to "C:\WINDOWS\DriverPacks". It will be available after the next reboot.
2006-08-25 09:19:20 : <KTD> Successfully updated the DevicePath registry value!
2006-08-25 09:19:20 : <KTD> Successfully created the .pnf files. KTD has been applied! It will be available after the next reboot.
2006-08-25 09:19:32 : <CLNP> Deleted the DriverPacks, which were located in 'C:\D'.
2006-08-25 09:19:32 : <CLNP> Deleted 'C:\hwids.dat'!
2006-08-25 09:19:32 : <CLNP> Deleted 'C:\DPsFnshr.ini'!
2006-08-25 09:19:32 : <CLNP> Deleted 'C:\devcon.exe'!
2006-08-25 09:19:32 : <CLNP> Deleted 'C:\makePNF.exe'!
2006-08-25 09:19:32 : <CLNP> Deleted 'C:\addUsepmtimer.exe'!
2006-08-25 09:19:32 : <CLNP> Deleted 'C:\ATICCC.ins'!
2006-08-25 09:19:32 : <CLNP> Added new value to the RunOnce key in the registry: the DriverPacks Finisher itself will get deleted after the next reboot.
2006-08-25 09:19:32 : Program terminated.
Submitted as bug#228 http://bugtracker.driverpacks.net/view.php?id=228 rebuilding image and trying to reproduce.
Tested again, this time adding WLan to the kept drivers, WLan copied ok but same error with the 3rd party packs
I use Siginets RVMIntegrator to slipstream the driver packs and with the latest version get the message below. I have tried twice after creating a new ini file and can reproduce the error on both occasions.
I haven't had time to test the new version but the GUI is all screwed up, the location page seems to stay visible when all the others are displayed causing some of the buttons to lose functionality like the export settings one. It only seems to happen when I am creating a new ini, once the file is created I cannot reproduce the problem.
Bâshrat the Sneaky wrote:@benners: If you have only one I386 directory, then you should use regular disc mode. But I'm afraid your winnt.sif files won't get updated both. Where are they located? And are there other files that are moved from their regular location?
I thought that, it was how I was doing it anyway. Regarding the winnt.sif files, I check periodically the line added to the [GuiRunOnce] section after slipstreaming the driverpacks, and, if it changes I update the sif files that are copied over during the making of a fresh DVD, I use XPlode and some AutoIt programs to do certain tasks like checking for program updates, compiling inno scripts and the copying of the i386 directory.
I have drive E: where the DVD root folder is created and modified files are copied from a location on D:, using XPlode, the disc is built from scratch each time and previous builds are deleted. Other files that are moved are txtsetup.sif and setupldr.bin, the original ones are then deleted from the i386 folder.
Thanks
I also use a form of mutliboot, not different OS, but for different users. I have 1 i386 folder, used to be 2 with UBCD but decided to create a seperate disc, and x number of folders for different users which contain the boot files.
I use BootFolder.exe by Nazgul to copy the boot files to the specific folders, and copy seperate winnt.sif and setupldr.bin files, would this setup be any use to test the multiboot options?. I know when I select my root folder I don't get any settings apart from being asked for a settings file.
Hi Wim,
I have also made a couple of donations (Tony Bennett) could you add me to the group.
Cheers
Posts found [ 20 ]
Powered by PunBB, supported by Informer Technologies, Inc.
Currently installed 3 official extensions. Copyright © 2003–2009 PunBB.
[ Generated in 0.019 seconds, 6 queries executed ]