You are not logged in. Please login or register.
DriverPacks.net Forum » Posts by Helmi
Problems were reported with the 3.96 driver if I recall well, which is why 3.95 was chosen instead.
Yes, that is correct.
As soon as the next, bug-free version is released, the newer one will be included.
Some other news (related to DP MS) : new version Intel Matrix Storage Manager 6.2.1.1002 (in case you didn't know yet). Ingore if not important :-).
Please post such driver requests in the appropriate forum (after having checked no one else has already done the same).
This makes it much easier to keep track of them and won't get overlooked 
Also, please include direct links to the driver file (ZIPped or similar preferred, however, if only available, EXEs work, too) as well as a possible changelog.
but i think the [PROB] can be removed from this topic....
Rgr that, topic edited accordingly.
At your service, as always
7.01.2 RC1 is in the Testing Team forum, which has this new feature and in which this problem doesn't exist at all. It should only take a couple of days before this new version is available.
Jup, already spotted, will be testing tonight, hopefully (maybe tomorrow, since the new Sereby's UpdatePack should come out then).
I believe Helmi reported that if you did that with QSC filled with the files from your previous (610 or 612), that the process did what it had to do. ( Well, he had not noticed the error because the folder with content was in placeas he had replaced an earlier base...)
Quite right!
I was very much surprised reading about so many folks having problems with the 701(.1) releases because i noticed nothing wrong when I created my DVD last week.
Either it's due to QSC or the fact that I am already using MSDP 611 (which has not been released yet, however, an even newer version will come very soon).
What problems were you getting ????
As I wrote before, once you touch the XPCD folder with nLite, it will not allow you to do consequtive changes to that folder (even something as creating an ISO out of it) as the path will no loner be rockognized a valid source.
This is not a bug, though, but by design (you get a warning message).
While I have no problem with a warning per se (you know, to keep the newbs from wondering what they broke) it's pretty bad there's no override.
Or at least there was not when I tested it last.
If you volunteer to try it out, you're most welcome 
Very strange, I did not experience this with 7.01 and I just reinstalled my system (which would not have worked w/o the MSDP).
I not not clear out the QuickStream Cache before, though, maybe it's linked to that?
Heh, it was merely a small translation so I guess that's why most of us where so fast (plus the fact that you initially told us it was very little work so one one was scared ).
Still, great to see most folks are still around regularly so they can respond on even such minor issues ASAP!
Have you tried 1.3RC
Currently using that however I did not dare closing it in fear of having to go through all of it again (nLite takes a lot of more time than the DriverPacks do, all that re-cabbing etc...)
I didn't know there was a problem when just using Nlite to create the ISO
Found the ISO creation part handy as it handles the boot sector etc.
There's no problem, it will work just fine if you remember my tips
In fact, the auto inclusion of the boot image is one of the reasons I'm using it myself.
I was using CDImage before but that was very crash-prone 
I could do it manuallay with Nero or CDRgold but I', too lazy for that ;p
You need to create a new Windows CD and reinstall.
I believe this is what you haven't gathered yet, right?
It will not help you getting your current system's drivers updated.
NLite needs to be executed before applying thr DriverPacks and must not be touched afterwards!
That's right, slipstreaming the DriverPacks should be the very last step before creating the ISO.
What I'm doing is, finishing all the tasks with nLite except from creating the ISO.
Since version 1.2 or so you can no longer open a once-nlited directory again so I leave nLite open on the ISO creation side, minimize the window, slipstream the DriverPacks, then go back to nLite solely to create the ISO.
Before 1.2 I would simply restart nLite, select my XPCD dir and perform ISO creation as the only task.
No idea why that got changed, though...
German translation updated and submitted, too!
kenotz wrote:so it's not yet official
No. and quite frankly... It probably never will be, because a printer is an optional piece of equipment.
Yeah, unless someone came up with the splendid idea of on-board printers , I doubt they will make it official.
After all, if we start to include some external devices, we'll have to go for all of them, and where will that end? 
Or will it be missing any vital drivers?
Probably.
The DriverPacks were made with the already supplied with XP drivers in mind, eg, there's no need to include a driver if it is already in the Driver.CAB and has not been updated since.
As there's a lot of legacy and vintage HW supported by Windows, it is unlikely there a newer drivers out for most of them.
We only add drivers to the DriverPacks if a device could not have been installed successfully already, which means the driver.CAB had no driver included.
If it works fine out-of-the-box, there's no need for a DP.
In fact, if MS supplied the latest drivers for all devices via Windows Update, this project would have never come to exists I guess
So, if you really want to, you could extract all the *.INF files from driver.CAB and compare them to those included in the DriverPacks.
If you cannot find duplicates or newer files, then you need to keep them in order to maintain support for the specific device.
If not, you can toss them out and save a little space.
However, the Printer DriverPacks are pretty large, mainly because of these stupid GUI printer drivers (yay for no Linux and network support!) and their horrendously blwon-up *.EXEs...
So I doubt you'll save a lot of space, and this will take a lot of time.
Unless you're very critically at your space limit, it's not worth the efford, IMO.
I always leave the driver.CAB untouched and it has always worked out fine
Using the Printers DriverPacks you couldn't fit it onto a CD anyway and if you move to DVD you should have more than enough space.
beta of virtual pc 2007
Just in case anyone cares, the RC1 is now out!
Links can be found if you log into your beta subscription account and select the VPC entry.
Direct link for all you lazy asses!
I guess I should look up how to disable SFC.
I'm using nLite for this task.
(The option is on the first page and a bit hidden under advanced options)
Actually, no. As per posted log file:
2006-12-22 13:21:37 : <KTD> KTD cache location set: "C:\D".
2006-12-22 13:21:37 : <KTD> KTD is enabled, in PATHS mode.
2006-12-22 13:21:37 : <KTD> Move drivers inside "C:\D" to "C:\D\D".The C:\D folder does noe exist. Neither are the DriverPacks located in %SystemDir%DriverPacks.
The C:\D\ is merely the temporary directory for the first extraction.
If you have KTD enabled, they will be moved out of this dir to their final destination.
If it's disabled it will get deleted.
Please check your KTD settings again, the default is disabled.
If you enable it, also check the path.
Default is %SystemDir%\DriverPacks, and it has always worked for me.
Bâshrat the Sneaky wrote:Just download the DriverPack Sound B, download all DriverPacks, extract the DriverPack Sound B, put the DriverPacks in the 'DriverPacks' directory, start the BASE, configure it to suit your needs and click the Slipstream!-button. That's it.
Please forgive my ignorance to ask you a simple question .
What do i have to do to put the DriverPacks in the 'DriverPacks' directory ( quote from you sir )
Thanks you
The Driver Packs! (d'oh!)
(The ones you DL'ed, basically, everything except for the BASE).
Bâshrat the Sneaky wrote:That depends on the method you will be using. Method 1 will require about 600 MB, method 2 290.
Sorry for my ignorance , but what is method 1 or method 2 , where can i read them in detail . Thanks so much
M1: Add drivers to XP's CAB archive.
Takes up a lot of space on the source and will result in an error when too many drivers are included.
M2: Include drivers as 7zip archives.
Much smaller, more compatible, however, may take a bit longer to install.
I'd be surprised, 7-zip manages higher compression than a lot of other formats (including RAR).
Indeed.
Should you actually manage to achieve better compression, feel free to put some examples online so we can verify the results.
I'd be very surprised, though.
Very annoying to me. Unacceptable to my neighbors.
You must have thin walls, then!
Anyway, nice program/script.
I guess.
I always disable the SFC, so I don't get any pop-ups anyhow.
Though, once, I forgot to do so (no nLite prior to DP because I was testing some stuff) and I got this beeping galore. Must be very frustrating if you install a lot of PCs O_O
ps. anyway to obtain the "beta" or nightly build of these packs ?
Become a member of the Testing Team.
i want to post in this one too. I want to include the ati drivers on my cd but if I do so and end up installing on an nvidia based computer does it still install the ati components? or does it only choose to do either of those ONLY when an ati card is detected?
Only when an approrpiate ATi card is detected - that is precisely what the Finisher is for, to only install non-INF components (such as control panels) on systems that actually have the specific hardware.
This is why it's called "exceptions"
Using latest DriverPacks (6.12) with a RIS image.
1. Trying to install a HP NC8430. The client installs ok, but several devices are incorrectly detected or installed (exclamation mark in Device Manager):
* Audio Device on High Definition Audio Bus (integrated ADI SoundMax HD audio card. Found in sp32593.exe from support.hp.com)
* HP Integrated Module (Bluetooth, found in sp32315 from support.hp.com)
* Mass Storage Controller (Texas Instruments SD reader, found in sp33416.exe from support.hp.com)
* PCI Simple Communications Controller (Agere modem, found in sp32644.exe from support.hp.com)
* 3 Unknown devices (no idea what these are, but dev-ids are ACPI\HPQ0004\3&B1BFB68&0, ACPI\HPQ0006\2&DABA3FF&0 and ACPI\IFX0102\4&28738126&0)
Please check whether these devices are actually supported by the DriverPacks.
If not, I suggest you post a [REQUEST] thread about each of them in the approriate subforum with a link to the driver file so that it can be included in the next version.
2. After first login, a notepad pops up with a text file named "desktop", containing [.ShellClassInfo] LocalizedResourceName=@%SystemRoot%\system32\shell32.dll,-21787.
I got that once myself but never found out the cause.
It is still a mystery for us.
Hasn't happened again on me for some time, though.
Also, an error message saying "CLI.EXE - application error - the application failed to initialize properly (0xc0000135)." This seems to have something to do with the graphics card?
Quite correct that is ATi's CCC trying to launch.
Do you have .NET FW slipstreamed?
If not, it is a requirement for CCC to run.
Either rely on the CP or slipstream it into your CD/DVD.
5. KTD is not enabled, even though properly set in settings (see log file, C:\D does not exist).
The default path for KTD is %Systemdir%/DriverPacks, which is ususally C:/Windows/DriverPacks on a default path.
Have a look for them there, I'm sure you will find them
DriverPacks.net Forum » Posts by Helmi
Powered by PunBB, supported by Informer Technologies, Inc.
Currently installed 3 official extensions. Copyright © 2003–2009 PunBB.
[ Generated in 0.061 seconds, 12 queries executed ]