just reread your log.. you too ran without QSC.
1,751 2007-06-19 09:17:47
Re: Error when slipstreaming with Method 1 (9 replies, posted in Feedback and Support - DriverPacks Base)
1,752 2007-06-19 09:10:26
Re: Error when slipstreaming with Method 1 (9 replies, posted in Feedback and Support - DriverPacks Base)
WITHOUT QSC, and capital letter used for \XP
again the error
2007-06-18 23:35:57 : <INIT> DriverPacks BASE 7.05.2 initialized.
2007-06-18 23:35:57 : <INIT> Host environment: WIN_XP Service Pack 2 on X86 CPU.
2007-06-18 23:35:57 : <INIT> Created temporary working directory.
2007-06-18 23:35:57 : <INIT> Imported proxy settings from Internet Explorer.
2007-06-18 23:35:57 : <INIT> Start scanning for DriverPacks for the wnt5_x86-32 platform.
2007-06-18 23:35:57 : <INIT> Detected DriverPack Chipset 7.06!
2007-06-18 23:35:57 : <INIT> Detected DriverPack MassStorage 7.06!
2007-06-18 23:35:57 : <INIT> Detected 3rd party DriverPack(s).
2007-06-18 23:35:57 : <INIT> Finished scanning.
2007-06-18 23:35:57 : <INIT> Detected settings file "C:\BASE\DPs_BASE.ini".
2007-06-18 23:35:57 : <INIT> Windows XP Professional - SP2 detected.
2007-06-18 23:35:57 : <INIT> The platform wnt5_x86-32_disc will be used (which is the 'disc' installation platform for the OS family 'wnt5_x86-32').
2007-06-18 23:35:57 : <INIT> Imported settings from settings file.
2007-06-18 23:35:57 : <GUI> Initialized GUI.
2007-06-18 23:35:57 : <GUI> Created a list of all available language files.
2007-06-18 23:35:57 : <GUI> Set the last used language, English, as the GUI language.
2007-06-18 23:36:00 : <GUI> Saved settings!
2007-06-18 23:36:00 : <GUI> Closed GUI.
2007-06-18 23:36:00 : <SEL> Selected module: mod_slip_wxp_x86-32_disc_m1.
2007-06-18 23:36:02 : <PREP> Removed all attributes from \I386.
2007-06-18 23:36:04 : <PREP> Cleaned up \I386\svcpack.inf.
2007-06-18 23:36:04 : <PREP> Unslipstreamed .
2007-06-18 23:36:04 : <PREP> Restored \I386\winnt.sif.
2007-06-18 23:36:05 : <PREP> Restored \I386\txtsetup.sif.
2007-06-18 23:36:05 : <PREP> Restored \I386\dosnet.inf.
2007-06-18 23:36:10 : <SLIP> Extracted DriverPack Chipset.
2007-06-18 23:36:16 : <SLIP> Extracted DriverPack MassStorage.
2007-06-18 23:36:16 : <SLIP> Started CAB compressing DriverPack Chipset (estimated 0.4 minutes).
2007-06-18 23:37:16 : <SLIP> Finished CAB compressing DriverPack Chipset.
2007-06-18 23:37:17 : <SLIP> Started CAB compressing DriverPack MassStorage (estimated 1.3 minutes).
2007-06-18 23:38:43 : <SLIP> Finished CAB compressing DriverPack MassStorage.
2007-06-18 23:38:43 : <CRIT> Could not copy Intel Chipset drivers' .inf files from \$OEM$\$1\D\C\I\xp\ to \$OEM$\$$\INF.
2007-06-18 23:38:46 : <CLNP> Temporary working directory successfully deleted.
2007-06-18 23:38:46 : Program terminated.
sorry, posted earlier log..
1,753 2007-06-19 08:59:13
Re: Error when slipstreaming with Method 1 (9 replies, posted in Feedback and Support - DriverPacks Base)
hi
I ran a test, and another, and another.
when I changed \xp to XP, and ran it WITH QSC, no $oem$ error
then, used a fresh extract with fresh copies.
when I used xp (the way it is in the release), WITH QSC, I still do NOT have that $oem$ error.
when I deleted the QSC folder (stil with lower case for \xp), and ran WITHOUT create QSC, bingo, I got the error.
2007-06-18 23:20:59 : <INIT> DriverPacks BASE 7.05.2 initialized.
2007-06-18 23:20:59 : <INIT> Host environment: WIN_XP Service Pack 2 on X86 CPU.
2007-06-18 23:20:59 : <INIT> Created temporary working directory.
2007-06-18 23:20:59 : <INIT> Imported proxy settings from Internet Explorer.
2007-06-18 23:20:59 : <INIT> Start scanning for DriverPacks for the wnt5_x86-32 platform.
2007-06-18 23:20:59 : <INIT> Detected DriverPack Chipset 7.06!
2007-06-18 23:20:59 : <INIT> Detected DriverPack CPU 7.04.1!
2007-06-18 23:20:59 : <INIT> Detected DriverPack Graphics A 7.06!
2007-06-18 23:20:59 : <INIT> Detected DriverPack Graphics B 7.05!
2007-06-18 23:20:59 : <INIT> Detected DriverPack Graphics C 7.04!
2007-06-18 23:20:59 : <INIT> Detected DriverPack LAN 7.06.1!
2007-06-18 23:20:59 : <INIT> Detected DriverPack MassStorage 7.06!
2007-06-18 23:20:59 : <INIT> Detected DriverPack MassStorage 7.06.1!
2007-06-18 23:20:59 : <INIT> Detected DriverPack Sound A 7.05.1!
2007-06-18 23:20:59 : <INIT> Detected DriverPack Sound B 7.05!
2007-06-18 23:20:59 : <INIT> Detected DriverPack WLAN 7.04!
2007-06-18 23:20:59 : <INIT> Detected 3rd party DriverPack(s).
2007-06-18 23:20:59 : <INIT> Finished scanning.
2007-06-18 23:20:59 : <INIT> Detected settings file "C:\BASE\DPs_BASE.ini".
2007-06-18 23:20:59 : <INIT> Windows XP Professional - SP2 detected.
2007-06-18 23:20:59 : <INIT> The platform wnt5_x86-32_disc will be used (which is the 'disc' installation platform for the OS family 'wnt5_x86-32').
2007-06-18 23:20:59 : <INIT> Imported settings from settings file.
2007-06-18 23:20:59 : <INIT> QuickStream Cache directory not found!
2007-06-18 23:20:59 : <GUI> Initialized GUI.
2007-06-18 23:20:59 : <GUI> Created a list of all available language files.
2007-06-18 23:20:59 : <GUI> Set the last used language, English, as the GUI language.
2007-06-18 23:21:20 : <GUI> Saved settings!
2007-06-18 23:21:20 : <GUI> Closed GUI.
2007-06-18 23:21:20 : <SEL> Selected module: mod_slip_wxp_x86-32_disc_m1.
2007-06-18 23:21:22 : <PREP> Removed all attributes from \I386.
2007-06-18 23:21:23 : <PREP> Deleted old method 1 related files.
2007-06-18 23:21:25 : <PREP> Cleaned up \I386\svcpack.inf.
2007-06-18 23:21:25 : <PREP> Unslipstreamed .
2007-06-18 23:21:25 : <PREP> Restored \I386\winnt.sif.
2007-06-18 23:21:25 : <PREP> Restored \I386\txtsetup.sif.
2007-06-18 23:21:25 : <PREP> Restored \I386\dosnet.inf.
2007-06-18 23:21:28 : <SLIP> Extracted DriverPack Chipset.
2007-06-18 23:21:33 : <SLIP> Extracted DriverPack MassStorage.
2007-06-18 23:21:33 : <SLIP> Started CAB compressing DriverPack Chipset (estimated 0.4 minutes).
2007-06-18 23:22:03 : <SLIP> Finished CAB compressing DriverPack Chipset.
2007-06-18 23:22:03 : <SLIP> Started CAB compressing DriverPack MassStorage (estimated 1.3 minutes).
2007-06-18 23:23:28 : <SLIP> Finished CAB compressing DriverPack MassStorage.
2007-06-18 23:23:29 : <CRIT> Could not copy Intel Chipset drivers' .inf files from \$OEM$\$1\D\C\I\xp\ to \$OEM$\$$\INF.
2007-06-18 23:23:34 : <CLNP> Temporary working directory successfully deleted.
2007-06-18 23:23:34 : Program terminated.erm, we have a bug.
1,754 2007-06-19 08:37:45
Re: Sysprep mass storage section with DriverPacks Mass Storage (41 replies, posted in DriverPack Mass Storage)
Hi
far as I know, limiting a driver to make it support fewer hwIDs does not break WHQL.
And, faik, changing the name o/t SYS, does not break WHQL either.
I am fairly sure that we can make a pack with three different aahci.sys and three different iastor.sys, with the inf files in accord with those names, and internally edited so the calls and references in those INFs are for the files they use.
if there are syspreppers who want to have a go at a testversion with such a change in it, say so.
I can make the testpack..
1,755 2007-06-18 22:24:35
Re: Error when slipstreaming with Method 1 (9 replies, posted in Feedback and Support - DriverPacks Base)
Hi
I will look wether xp has to be upper case or lower case.
However, I can already tell you you have way too many drivers included for method 1.
(this won't work... only do this IF you want to use the disc as driver disc only, not as installer...)
1,756 2007-06-18 11:40:31
Re: [IMPL]Matrox 2.04.00.179 SE U WHQL (8 replies, posted in DriverPack Graphics)
Hi Muiz
I am working on it.
1,757 2007-06-18 11:26:24
Re: [Question] System Errors pertaining to HDD (15 replies, posted in Hardware)
Hi again
you said you ran that ultimatebootCD in USB mode.
I would use A cheap IDE converter. I really think you get more reliable results than over USB.
such a IDE converter is in my tools-drawer, and one can use it again, and again, and again.
USB interfaces can go bust (has an inteface chip) whereas an IDE converter is just what Helmi said wide-ass to tight-ass
hehehe..
One could call it standard IDE-plug to Slim-IDE-plug adapter or molex-adapter, but the point is that no EXTRA eletronics play part in that connection.
I like Helmi's description better 
an example
http://www.addonics.com/products/io/aaedt18ide25.asp
one can find cheaper, and local shops may have them in stock.
hmmm, first example was a poor example
this is similar to what I use
http://www.newegg.com/Product/Product.a … 6812119020
1,758 2007-06-18 10:52:19
Re: [BUG?] Intel 82Q963/Q965 Dell Optiplex 745: yellow exclamation mark (38 replies, posted in DriverPack Graphics)
hi
at intel, I just read that latest IGP should not be installed if there is a third party card present in the computer.
This is beyond our control.
--------------------------------
The driver they currently have is newer than what I see in current DriverPacks release.
Matter of fact, it has very little overlap compared to the driver we had in Grafics_B 6.12
(that's a trend.. newer drivers often drop support for older hardware)
Since I am already handling another request atm, I will take the opportunity to recover the OLD driver we had in 6.12 and put it back in, and replace the current "bad" one with the newest as an update..
1,759 2007-06-18 07:03:46
Re: [BUG?] Broadcom 57 Nextreme in Optiplexx 745: yellow exclamation mark (21 replies, posted in DriverPack LAN)
@ chud
does the broadcom driver work right now?
Note; the HDA issue probably deserves another topic.
1,760 2007-06-18 06:45:02
Re: ASUS F3H AP027 driver problem (4 replies, posted in DriverPack Chipset)
I just expanded these, and they contain XP too.
They ought to be in our latest release, and I will look .
However, I have the feeling you did not make a driver slipstreamed XP.
(EDIT >> 945GM has your chip covered, and what we have is newer than what asus uses..)
for this single machine you want to do, download the INTEL INF install utility at INTEL, and run it.
INTELchipset
1,761 2007-06-18 06:42:00
Re: ASUS F3H AP027 driver problem (4 replies, posted in DriverPack Chipset)
1,762 2007-06-18 06:10:53
Re: [FIXED in 7.06] Chipset 6.0.8 locks up Dell Optiplex GX520 (84 replies, posted in DriverPack Chipset)
CBITS wrote:
Hello all! This thread has been the missing puzzle piece to a project I've been working on for work. Without it, I would have kept going around and around in a giant oval! By using the 6.05 Chipset driver pack along with the updated driver packs (7.04), I finally have been able to make a universal unattended XP slip w/ drivers & 3rd-party apps for the Dell machines within my department. Since the disc's creation, I've successfully tested the slip on a Dell Optiplex GX520, Latitude E105, and an Inspiron 6400. If the disc continues to be successful with the Dells, then it will become the department's stock installation disc!
@Bashrat, Thanks for the driver packs... I've talked to my supervisor to see what we can do to to support driverpacks project.
Peter
Chemistry & Biochemistry IT Services
University of Texas at Austin
Hi,
I would sure like to know wether our latest release fixed this issue, for this release has more or less been implementing same thing CBITS did.
I downloaded just about all archived chipset drivers from Intel, and the latest.
Then I used those to build our fresh pack with NO OLD files missing, and the newer ones got added/overwrote older.
The SP folder was not present in latest INTEL driver, and latest driver supported all OSes.
I Kept the SP folders, tho, and because I intended to use a single folder for all OSes, I made sure each folder had all files in it that the other had. (They were all the same files, but one \SP folder had an extra file and that got included in the other \SP folders) .
Then I discovered I could not use a single folder (which I had calledl X86 in a private test version.), because when I tested this with Method 1, I got an error like <IN\XP folder missing> during slipstream.
((Using this X86 folder, building a Disc with Method 2 ran without problem.))
So, the release has same folder stucture it had, but all OLD files these machines might use are included, and this should finally solve this issue.
(this Intel update in Chipset and mass storage DriverPack aimed to solve the issues)
I'd like to hear feedback, so that this can maybe get the topic title change we all like to see.
Can we get rid of [NOT FIXABLE] ?
You tell us.
1,763 2007-06-18 04:53:45
Re: [Question] System Errors pertaining to HDD (15 replies, posted in Hardware)
hi
SMART has to be enabled in the BIOS of the machine it is hooked up to.
This is worth looking into, for chances are it is turned off.
1,764 2007-06-17 21:38:12
Re: [BUG] ahcix86.sys corrupt (19 replies, posted in DriverPack Mass Storage)
this file is not used in windows2000, as the setting for "ahcix86" is ms_1_exc_disableIfOS = "w2k"
BUT.... I THINK I JUST FOUND THE REASON.
there was a hidden character before the = in that ms_1_exc_disableIfOS = "w2k"
Thanks, I'll upload the fixed files.
1,765 2007-06-17 21:28:51
Re: [BUG] ahcix86.sys corrupt (19 replies, posted in DriverPack Mass Storage)
Hi
I'll check.
1,766 2007-06-17 20:50:53
Re: Intel SigmaTel HDA (19 replies, posted in DriverPack Sound)
hi
I think I commented on that when I last worked on DP_Sound, but I cannot remember wether the different downloads show different hwIDs in those drivers.
I thought that this is a nice way to make a mess, and decided on the AC97 front panel, because AZALEA control panel is not so user friendly.
This control panel pops up when "Jacksense" senses insertion of a mini-jack.
I know that if the hwIDs are same, we can never have all.
Heck, I cannot even remember which of the two controlpanels I chose, if any.
I bet it is in the comments I made during the testing of that pack.
I know I am not capable of writing code so that the required combination is used.
(I am no programmer, see.)
1,767 2007-06-17 17:33:28
Re: Unattended (network) install - using method 2 (2 replies, posted in Feedback and Support - DriverPacks Base)
hi
method 2 edits dosnet.inf and places the mass storage systemfiles used by TXTmode in i386 folder.
(that's why you do not see them in Winnt.sif)
The OEM folder has the 7zipped copies of the driverpacks you selected (including mass storage) and other files "setup" will use once TXTmode finished (in the BINaries folder).
What happens then is, 7zip/copy the driverpacks and executables to install them to hard disk, and then run the executables.
Your second question was answered by Bâshrat the Sneaky himself in another discussion.
I did not find that back yet, and when I do, I will post the link.
(I want to collect some info, and use it for a FAQ and maybe a tutorial )
1,768 2007-06-17 16:47:12
Re: Looking for a good DriverPacks Tutorial... (74 replies, posted in Other)
I saw the edit that it works now..
hehe, I'm still thinking it was "in use" by another program.
the stuff posted in here was used for a tutorial, and it can be found here.
http://forum.driverpacks.net/viewtopic.php?id=1449
(just a note; the one I have on personal space has some extra content by now. Once the new site is up for public, it will be easier to flesh it out and have better detail on the new features.)
1,769 2007-06-17 15:50:56
Re: Looking for a good DriverPacks Tutorial... (74 replies, posted in Other)
Hi
welcome to DriverPacks.
Was there a winnt.sif in the i386 folder before you launched Base?
If there weren't it should have this in the log.
2007-06-16 04:22:58 : <PREP> Removed all attributes from \I386.
2007-06-16 04:22:58 : <PREP> Generated \I386\winnt.sif file.
(I assume you did not have it open in an editor like notepad while you ran Base)
1,770 2007-06-17 15:35:26
Re: [REQ] Intel Matrix Storage Drivers (3 replies, posted in DriverPack Mass Storage)
Myyz
welcome to DriverPacks
7.06 had an error one could not miss.
(I learned that when one did something to a file, one must re-test before uploading.)
please use the new release?
7.06.1 is newer than what you used.
1,771 2007-06-17 14:35:31
Re: Sysprep mass storage section with DriverPacks Mass Storage (41 replies, posted in DriverPack Mass Storage)
@ torrero and other syspreppers.
In Mass storage version 7.06.1 we made a U-turn in the intel section.
Primo; The foldernames changed. IN\1\O no longer exists.
IN\1 has the oldest driver V. 5.5.1035
TXTmode name is iastor55.sys
IN\2 has V. 6.2.1002
its TXTmode name is iastor62.sys
IN\3 has V. 7.05.1017
Its TXTmode name is iastor75.sys
There is more to it than the change in the INI.
The 5.5.xx, 6.2.xx and 7.05.xx drivers themselves (their INF) were edited
You see, the newest driver dropped support for some old hardware, but there was overlap, and machines crashed.
IN\3 with V. 7.05.1017 was a real problem for machines that used hardware supported either by 6.2.xx or 5.5.xx, which made me make this change.
I have no idea what this will do to sysprep.
-------------------------------------------------
during tests, we tried giving distictive names to the INF and SYS files
(this required edits in INF for filecopy and internal filename references).
This still caused crashes, but then there was still OVERLAP.
Now, there is NO overlap, and this could be done again, I guess.
Now, IF you want me to do this for you so you can try all three intel drivers in SYSPREP, you can ask.
HOWEVER, you could also simply try the newest mass storage driverpack, and see what happens.
Then we would at least find out wether that works or not.
(post updated to reflect the current situation in 7.07.2 somewhat better.)
1,772 2007-06-17 05:11:48
Re: insufficient memory for dmboot.sys error (6 replies, posted in Feedback and Support - DriverPacks Base)
cool..
it gave no memory error on server 2000 as well?
the error with jraid was an error I made just before I finalised mass storage 7.06
(and soon as I read about it I fixed it, so 7.06.1 was the cure.)
the memory errors in windows 2000 were adressed as well, but it should be clear that by making windows 2000 load fewer drivers, that the UN-selected "CAN" be needed, so that the user 'MAY HAVE TO" re-enable them in mass storage.INI (and then repack the driverpack)
1,773 2007-06-16 20:38:42
Re: [REQ] old ATI drivers not yet covered by DriverPack Graphics B (19 replies, posted in DriverPack Graphics)
Hi
when I said, "I don't get this" I meant I don't understand why it is an issue..
A couple hours later, I had to do a system and since I did not have that particular windows version slipstreamed yet, I made a DVD.
RVM slipped Sp2 into it, and then the april hotfixpack. (doing a Dutch Home Edition.)
Then Base with all current releases, and setup was launched..
I got a popup when sigmatel HDaudio driver got loaded, and later on (after restart into GUI) another popup on top of Finisher for hardware that got detected while Finisher was running.
The machine will be picked up soon, and I can not afford to hold it back now.
(Now that I finally decided to sell it..)
1,774 2007-06-16 15:52:00
Re: [REQ]Dell TrueMobile 1300, 1400, etc. WLAN (Broadcom) (5 replies, posted in DriverPack WLAN)
hi
it looks like a driver update against War-drivers.
Muiz?
1,775 2007-06-16 15:49:03
Re: [SOLVED]Incorrect Listings (1 replies, posted in DriverPack WLAN)
Hi
it will take a while before you see result, since work on WLAN's optimizing has just started.