krick wrote:

I told you exactly what I did...

1) boot windows 2000
2) insert XP CD with integrated driverpacks

I know it basically has already been said, but I need to stress this once again:
Both nLite as well as the DriverPacks, besides being created for the UNattended installation (yes, we all are that lazy tongue), are intended ONLY to be booted from the disc you created with (reason why nLite allows you to directly brun a bootable disc, btw).
Because of entries in the Windows setup information files, WHEN booting fro mthe disc, an upgrade installation is no longer possible!
This is done so deliberately and is an option provided by MS themselves (tells you that you probabaly shouldn't mess with it).
If you still do an in-place upgrade as you did, you do not have to be surprised it did not work as intended.
Firstly, as has been said, you need to boot from the disc you want to install, and secondly, I know NOONE around here or any other unattended install forum, that would actually even just CONSIDER doing an in-place upgrade.
It simply has just NEVER been done so we wouldn't even know what could happen.

This brings me to the next point: Backup.
Because you are venturing into the great dark unknown with that in-place stuff, you desperately NEED to backup (or you do not value the data, in which case you could have just formatted and properly and unattended installed...).
Well, and if you run a backup anyway, what's then still keeping you from installing from scratch, thereby avoiding any conflicts, incompatibilities or useless legacy files taking away space from the drives...?

Point is, I couldn't think of a case were an in-place upgrade would be justified or even practical.

I simply want to "clean up the mess" at this point.  A simple list of files to delete from the root of my hard drive would have sufficed instead of a verbal assault.

In this case, if you really want to clean up, reformat.
Who know what else has been messed under the hood and has just not shown itself.
You may encounter further issues down the road, then you will have to reinstall anyway, just my advise is to do that now so you get a clean start.
Also, as to files you can delete from %systemdrive%, let's go the other way round, list those that you MUST keep:

bootfont.bin
NTDETECT.COM
AUTOEXEC.BAT
IO.SYS
MSDOS.SYS
config.sys
ntldr
boot.ini
hiberfil.sys
pagefile.sys

Those files should be hidden by default (and marked as system files!) anyway so if you delete everything that's visible, you are save to go.

What I did, while not officially supported, does seem like something people might want to do.

As I said, I know of noone who would ever want to do an in-place upgrade, so I doubt that...
Even then, if they want to do it, we aren't stopping them, we just don't support it.

If I had encountered that, I would have known what to do.  As an end user, I never expected it to dump all the files into the root of my hard drive and it caught me off guard.  As it was, I had no way of knowing what went wrong or how to solve it.

The DriverPacks are mainly for experienced and/or power users that want to increase their possibilities with an unattended install.
That means, they already know what an unattended install is, have read the guides and msfn.net and have a basic knowledge about system setup.
MSFN.net guide tells you how to manually add selected drivers to your install (quite close to M1 in our case), DP adds support for virtually any device, so it's a step to the next level (or over-next rather).

Folks that do this usually KNOW what files are needed in %systemdrive% and what can be deleted, so it's a non-issue.
Also, it is rather known around here what the Finisher does (cleanup, among other), so, it should be kind of logical that a manual execution of the Finisher, during an attended install no less, could possibly bring the desired results...

327

(10 replies, posted in DriverPack Graphics)

scarface wrote:

here is an update http://rapidshare.com/files/142426863/D … 04.7z.html
Intel Graphics 82945/82965 G/GM/Express updated to 6.14.10.4977
removed hlp files
previous file is 52.3MB new file is 51.9mb
not tested

Thanks for directly providing (what looks like) a complete DP, but usually, we prefer getting the original driver from the manufacturer's website.
If you host on RS or any other OCH, we can never be sure it's the original, unaltered, final (non-beta) driver - it's not that we wouldn't trust you, but you have to be cautious.

Also, I think we agreed on keeping the helpfiles in, even in multi-language fashion if available.
The reason for this is firstly, as you can see, they do not take away much space and secondly, the DriverPacks are intended to be international, so if there's other languages than English included, that's great (not everyone posting here is also using an English OS).

Oh, and thirdly, if you were to test the files you provide, that would really be awesome because it saves us a lot of work and also means that we do not have to search for HW to is supported by the driver to be able to test it.
We do not have all the HW we included drivers in the DriverPacks available for testing, you know wink
That would certainly fill a whole hangar for storage big_smile

328

(8 replies, posted in DriverPack Mass Storage)

You did use the TextMode option in BASE, didn't you (here's where DPs_BASE.log would have come in handy...)?

ATi drivers for both GFX cards as well as the SB can be found here:
http://game.amd.com/us-en/drivers_catal … egrated-xp

AFAIK, they already got included in the latest nightlies, you may want to try these if you need support right now and don't want to wait for the final version (but use caution, it could still be bugged):
http://driverpacks.sytes.net/driverpacks/Nightlies/

Also, next time, please but a [REQ] in your thread title if what you want to do is REQuesting new drivers to be added to the DriverPacks wink

Jaak wrote:

hehe; when M1 gets dropped

Oh noes, the legacy!!!


@ sandrion:
You need to "resolve" (change status to) any translation "issue" you report no notify the system that your translation is ready to be included in the next version of BASE.
I'll do that for you this time smile

mcgiwer wrote:

My OS wasn't detected becouse on my HD (in the system32 dir).

Of course it will not be detected, because you point it to the INSTALLATION path as opposed to the needed SOURCE path (files as found on CD).
If what you tried worked, you'd create an installation disc out of the installed files and that cannot work well.
You will need fresh, unaltered files (you can use nLite on them, though) as from CD if you want to slipstream the drivers.

As you only want to install the drivers on an already existing installation, you must take a different approach!

I can't copy it from the CD becouse I have a small HD (only 4.2 GB - I have an old PC and bigger drivers are difficoult supported).

As Jeff has already pointed out, and I have mentioned in my previous posts, you WILL need more HDD space either way (slipstream or driver installation)!
What you are currently running is less than what fits on a DVD-R, the nowadays industry standard for space so to speak.
The way I see it you have these options:

* Ditch that old machine (must be from the early to mid 90's I figure, given that little HDD space) and get a decent one, ANY would be better I guess.
* Find out what the max size for a HDD is to be supported by your mobo/BIOS (maybe install a BIOS update to increase the limit), then buy a 20 GB (probabaly smallest you can find if at all) HDD for little money and work from there on
* If you system has USB, get an external HDD case and put a HDD inside.
That way you will circumvent any size limits given by the BIOS - any OS supported by the DriverPacks will not have a problem with modern-sized HDDs
* Download an install only those drivers that your system really needs, thereby avoiding the "large" size of the DriverPacks. You could use Driver Genius to help you find the required drivers.
* If you system is that old, the OS should already provide most if not all essential drivers anyway (legacy support).
You should also be able to get the rest through WindowsUpdate - have you given that a try already?


I'd like to suggest somthing for the newer version of the base. My suggestion is: when in the soft is selected the disk option then the OS should be gained from the system entries (for ex. registry) and not from the i386 (on 32 bit systems), becouse many Windows-es XP don't have this dir.

As I already wrote, it is a very bad idea to take the files from your install dir and work on those.
Instead, you will need the CD that contains the untouched and trouble-free files.
Also, it does not matter whether the i386 dir is present in your install dir because it certainly is present on your install disc!
So claiming that many XPs would not have it is a moot point.

In case you really only have a restore disc and not a proper install disc, you should complain to your OEM for not providing a proper one and get this software: http://www.heise.de/ct/ftp/06/03/202/
It will allow you to transform your recovery CD or partition into a real installation one.
You can use Google to trabslate the site if you do not understand German.

krick wrote:

When doing an upgrade to XP from an existing Windows 2000 install using the same DVD, the XP upgrade is successful, but the driverpacks process fails somehow and I end up with a "D" folder in the root of my hard drive, along with a bunch of loose files.

You need to reboot at least once and if that doesn't do the trick, you must run the DriverPacks Finisher manually to clean those files (or delete them by hand, whichever you prefer...)

Is there something specific you are looking for?

You mean, like log files?
Yeah, we love those!

krick wrote:

I'm guessing the bug has something to do with the fact that Windows 2000 is installed to a directory named "WINNT" and XP installs to a directory named "WINDOWS".

As the DriverPacks officially support Win2k, obviously, we are aware of that.
In order to prevent such naming issues (and because the users can also freely name the windows dir to whatever they like), the variable %systemroot% is being used.
Go ahead and type that into Explorer, you'll see it works. wink

mcgiwer wrote:
Helmi wrote:

Well, then clean up!

I have an old PC with only 2 disks with only 4.2 GB space each sad

Well, well.
I am a bit puzzled as to how you want to do the reinstall anyway, but you will need additional space that way or the other.
You should consider a HW upgrade sometime soon - even the smallest HDD size you can find would be a great step forward and ease such space problems.

Helmi wrote:

See, because you need it doesn't mean our team will drop all current tasks and work on a solution for your problem (which does not exist, as all features work already...).

I haven't told that You or any else team member should drop his work to solve my problem... that's Your words...

No, but you said it was urgent because you needed your problem getting fixed by us.
How should this be interpreted otherwise?

Helmi wrote:

As that is not the case, asking nicely and showing patience are the only matters that may get things done for you!

I have asked nicely that such problem exists and nead to be solved and You are jumping off to me with some resentments...

No, you haven't asked nicely, at least not in my book.
You said that "DriverPacks Base neads a installer.".
You haven't said either please or thanks.
Great job on editing your post and removing "urgent" from the subject line, btw...

Anyway, I'm done with that - I told you how to behave and ask around this place.
Hopefully, you'll follow this advise next time.
We're all trying to be friendly to each other here and get along fine.

I'm not holding a grudge or anything, but there's always two ways how you can say something.

Currently, we do not support Vista with the BASE and the DriverPacks.

You should also include the OS in the subject line so that is directly clear what kind of drivers you are looking for.

Also, we do not provide drivers on a per system basis.
You cannot request us to search a driver for your system!
(but maybe a user will be so kind and help you regardless...)

You can only request a driver that you have already found and know a link to on the manufacturer's HP to be added to the DriverPacks (that is, if you used the BASE to slipstream the DriverPacks into your source, installed and had that driver missing or only an outdated version installed).


Besides, please you CODE tags for the next time you post such a long list, that makes it easier to read, thanks.

Probably a server error, as the server reports which version are current to the BASE.

Just ignore it this time around.
The check is merely based on the filenames so it does not tell you whether the packs you DL'ed are good or bad.

mcgiwer wrote:
Helmi wrote:

So, copy the contents of your Win CD to your HDD and integrate

It's dificult if You don't have much space left tongue

Well, then clean up!
You'll have to move stuff to your backup anyway if you are going to reinstall, so why not just start now, then use the free space (you'll only need about 1-2 GB and honestly, HDDs are super cheap ATM!) to copy the %SOURCE% to your HDD (you can also let nLite do the task for you so you don't miss hidden and system files!) and integrate the DriverPacks.


Helmi wrote:

Besides, REQesting something that's already there is one thing

I have downloaded the Base form Driverpaks.net .After unpack the installer for the Base wasn't there.

If you create a DP'ed install source, the DP_install_tool.CMD will be there.
You can use that for exactly this task.
Of course, if you do not create such a source, you will have to manually extract all the files and fiddle around 'till it works - your choice.

Helmi wrote:

telling is to hurry it up by adding "Urgent" to the topic line scores as very impolite in my book

I've set it to urgent becouse I nead this as urgent as possible to get my PC working properly

See, because you need it doesn't mean our team will drop all current tasks and work on a solution for your problem (which does not exist, as all features work already...).
The DriverPacks are free and we don't even want to get paid for them, but we do like getting a "please" and "thanks" in a while and a donation now and then.

I don't see you providing either.

This projects lives for its users by its users!
Only if everyone tries to contribute what they can, we can achieve the greater good.

If we were on your salary list, you could demand things off us with a deadline you set.
As that is not the case, asking nicely and showing patience are the only matters that may get things done for you!

OverFlow wrote:

because it has two connectors on the card - (yes?)

a two head unit (might as well hook up a second monitor now)

Yes, indeed.

As you can set different options for each monitor, each output connector needs to be listed seperately.

Oh, and hooking up a second monitor is indeed great fun (got me a nice 22" CRT 30kg - 66 lbs for you Brits wink -monster sitting here now, perfect addition to the 15" LCD big_smile))

If you show a little patience, the next BASE version will feature this very option that only takes you three clicks to complete.
If you know how to handle BASE in general, you won't need any guide then.

All you need to do is remove those sub-folders that you do not need (in this case \A), then repack.
To avoid conflicts, also remove any INI lines that point to the removed paths.

Besides, my DriverPack Graphics A files does contain entries for [N1] (this also being the brackets you are referring to?).
But I'm currently using a test nighly version.
Which is yours?

To check whether a file has been downloaded completely and is not corrupted, please use 7-Zip's (great packer btw, recommend to install) archve testing feature and/or check the MD5 sum given on the DL page.

Wut?
You will need to intergrate the DriverPacks onto the HDD rather than the install CD anyway, because BASE cannot write to an optical medium.
So, copy the contents of your Win CD to your HDD and integrate.
Also, read the tutorial in my sig.

Besides, REQesting something that's already there is one thing but telling is to hurry it up by adding "Urgent" to the topic line scores as very impolite in my book.
It's done when it's done based on feasability and ease of implementation.
How much you'd want it is not the driving factor (unless you come over with an extremely generous donation, maybe wink).


Should you possible refer to a driver installer that updates the drivers on the current system (that is NOT an integration!!!), that, also, has already been impelented...

342

(9 replies, posted in DriverPack WLAN)

You can get the HWID tools in both our sigs.
DL the file and execute it, then post the results from the created .TXT file.

You can check this guide for driver integration if you only want a single one or a couple ones:

http://unattended.msfn.org/unattended.xp/view/web/34/

Hey, could it be that even the English file is missing some entries?

I stumbled across these when updating the German file only not to find any relating one in the English one...
http://img172.imageshack.us/img172/2833/missingentriesen2.png


Other than that, the German file is finished (for the time being...) but I'll wait with uploading it the bugtracker until you have updated the English reference file wink

OverFlow wrote:

I did not even know it was down...

admins could still access the site wink

Oh snap.

I was about to email you about it (guessin that Bâshrat the Sneaky was too busy to act in time) but I thought you might notice it all by yourself, as it affected both the forum as well as the main page.

Next time I will not be so hesitant, then wink

Welcome aboard again! smile

Just a side-note:
The AGP hotfix driver do not seem to have been released in the 8.8 fashion, yet.

BASE 8.08 will introduce new options for the NVdia Control Panel to be installed in new fashion, old or both (akin to ATI CCC/CP).
This requires three new entries to be translated.
As the (now) alpha version of BASE is not publically released yet, I will trow you a bone in form of the new English.LNG file so you can already start translating if you wish, so everything will be ready once it goes final (not immediately I guess...).

[Details]
author		= "Wim Leers and Jeff Herre"
authorContact	= "admin@driverpacks.net & Jeff@AdaptivePC.com"
lastUpdatedFor	= "8.05"


[GUI]
description		= "description"
slipstream		= "&Slipstream!"
exit			= "&Exit"
; %s="<name of settings file to overwrite>"
iniSave_01		= "Could not delete %s!"
iniSave_02		= "DriverPacks BASE settings files"
disc			= "disc"
multibootDisc		= "multibootDisc"
instPlatform		= "installation platform"
none			= "none"
all			= "all"
select			= "select"
paths			= "paths"
patterns		= "patterns"
yes			= "yes"
no			= "no"
true			= "enabled"
false			= "disabled"


[any_any_any__GUI]
start_tree				= "Start"
	start_title			= "Start"
	start_01			= "Welcome to DriverPacks BASE, the tool to slipstream the DriverPacks into your installation files.|||Supported destination OS platforms:|• wnt5_x86-32 (Windows 2000, XP, Server 2003)||Supported installation platforms:|• disc|• multibootDisc (any of the above platforms)"
	start_02			= "Select your preferred language:"
	start_03			= "&Apply"
	start_04			= "Load settings file..."
	start_05			= "&Browse"
	start_06			= "Make a donation to support this project."
	start_07			= "Load other language?"
	; %s="<name of the other language>"
	start_08			= "The settings file you've opened has a different preferred language than English: %s. Would you like to set %s as the preferred language?"
	start_desc			= "DISABLED"

settings_tree				= "Settings"
	settings_title			= "Settings"
	settings_01			= "These are the required settings. Please review them, if you don't, the default settings will be used."
	settings_desc			= "DISABLED"

settings_location_tree			= "Location"
	settings_location_title		= "Select location of platform"
	settings_location_01		= "Location"
	settings_location_02		= "&Browse"
	settings_location_03		= "Select a valid location."
	settings_location_04		= "N/A"
	settings_location_05		= "Please browse to a directory that is valid for the installation platform you selected."
	settings_location_06		= "Changing the installation platform"
	; %s="<name of the newly selected installation platform>"
	settings_location_07		= "Are you sure you want to change the installation platform to "%s"? Your current settings will be lost, unless you have exported them!"
	settings_location_desc		= "What kind of directory to choose? That depends on the installation platform you're using.|• disc: the directory that contains the I386 directory.|• BartPE: the \plugin directory to which DriverPacks will be exported.|• multibootDisc: the multibootDisc's root directory."

updateChecker_tree			= "UpdateChecker"
	updateChecker_title		= "UpdateChecker"
	updateChecker_01		= "Loading..."
	updateChecker_02		= "&Refresh"
	updateChecker_03		= "Could not connect to the internet! This has 2 possible causes:||1. Your firewall is preventing this application to access the internet. If this is the case, please give it the permission to connect to the internet through port 80 and then click the 'Refresh' button.||2. You don't have an (available) internet connection."
	; %s="http://www.driverpacks.net/"
	updateChecker_04		= "%s seems to be offline. Please try again later."
	updateChecker_05		= "New version available"
	updateChecker_06		= "Up-to-date!"
	updateChecker_07		= "Where did you get that?"
	updateChecker_08		= "Installing updates"
	; %s ="DriverPacks BASE"
	updateChecker_09		= "Current %s"
	; %s ="DriverPacks BASE"
	updateChecker_10		= "New %s"
	; %s="DriverPacks BASE"
	updateChecker_11		= "Would you like to download and (automatically) install the new %s?"
	updateChecker_12		= "Initializing download ..."
	updateChecker_13		= "&Cancel"
	updateChecker_14		= "Download progress"
	updateChecker_15		= "Cancel download"
	updateChecker_16		= "Do you want to cancel the download?"
	updateChecker_17		= "Starting installation."
	updateChecker_desc		= "DISABLED"

about_tree				= "About"
	about_title			= "About the DriverPacks BASE"
	about_01			= "Credits"
	about_02			= "developer"
	about_03			= "method 2 methodology"
	about_04			= "original DriverPack MassStorage and hotfixes"
	about_05			= "enhanced dummy setup"
	about_06			= "enhanced method 2"
	about_07			= "Thanks to the main testers"
	about_08			= "And the rest of the testing team"
	about_09			= "and many others"
	about_10			= "Please make a donation to support the DriverPacks development.| Especially when using the DriverPacks professionaly."
	about_11			= "Windows version detection"
	about_12			= "Translations"
	about_desc			= "DISABLED"


[any_any_multibootDisc__GUI]
settings_settFiles_tree			= "Settings Files"
	settings_settFiles_title	= "Select the settings files"
	settings_settFiles_01		= "settings file"
	settings_settFiles_02		= "&Add"
	settings_settFiles_03		= "&Delete"
	settings_settFiles_04		= "Add settings file..."
	settings_settFiles_desc		= "DISABLED"

settings_details_tree			= "Details"
	settings_details_title		= "Details for selected settings file"
	settings_details_01		= "No settings file selected."
	; %s=<number>
	settings_details_02		= "Viewing details for settings file #%s."
	settings_details_desc		= "DISABLED"


[wnt5_x86-32_disc__GUI]
settings_dps_tree			= "DriverPacksâ„¢"
	settings_dps_title		= "Select the DriverPacks to slipstream"
	settings_dps_01			= "DriverPack MassStorage text mode drivers are necessary if you wish to|boot from a mass storage controller that's not supported by default."
	settings_dps_02			= "Select &all"
	settings_dps_03			= "Select &none"
	settings_dps_desc		= "DISABLED"

settings_dpsMthd_tree			= "DriverPacks method"
	settings_dpsMthd_title		= "Choose the slipstream method"
	settings_dpsMthd_01		= "method &1"
	settings_dpsMthd_02		= "method &2"
	settings_dpsMthd_desc		= "• Method 1: copy drivers to $OEM$\$1\, then list the directories in winnt.sif's OemPnpDriversPath entry. The drivers will be CAB compressed.|• Method 2: install a dummy setup that will be executed before the real setup. This dummy setup will extract the DriverPacks from the CD/DVD to the HDD and then update the DevicePath key in the registry."

settings_fnshrMthd_tree			= "Finisher method"
	settings_fnshrMthd_title	= "Choose the method to start the Finisher"
	settings_fnshrMthd_01		= "&GUIRunOnce"
	settings_fnshrMthd_02		= "&RunOnceEx"
	settings_fnshrMthd_03		= "&Custom"
	settings_fnshrMthd_04		= "RunOnceEx settings"
	; %s="937"
	settings_fnshrMthd_05		= "&Default start ID (%s)"
	settings_fnshrMthd_06		= "C&ustom start ID"
	settings_fnshrMthd_07		= "Enter your custom start ID."
	settings_fnshrMthd_08		= "Custom execution of DriverPacks Finisher: instructions"
	; %s=""%SystemDrive%\DPs_BASE.exe""
	settings_fnshrMthd_09		= "You decided to set up the execution of the DriverPacks Finisher your self, so here are the instructions:||-execute %s|(The path is copied to the clipboard, so please paste it if you don't want to|make a mistake.)"
	settings_fnshrMthd_desc		= "• GUIRunOnce: executes during first login, no GUI output.|• RunOnceEx: executes during first login, progress window. You must specify a start ID: default (937) or custom (to prevent interference with your other RunOnceEx items).|• Custom: if you want to start the Finisher yourself (e.g. through XPlode)."

optSettings_tree			= "Optional settings"
	optSettings_title		= "Optional settings"
	optSettings_01			= "These are the optional settings. Please review them, if you don't, all optional settings will be disabled."
	optSettings_desc		= "DISABLED"

optSettings_ktd_tree			= "KTDâ„¢"
	optSettings_ktd_title		= "KTD"
	optSettings_ktd_01		= "&DISABLE KTD"
	optSettings_ktd_02		= "Enable KTD for &ALL slipstreamed DriverPacks"
	optSettings_ktd_03		= "Enable KTD for the DriverPacks I will &SELECT"
	optSettings_ktd_04		= "Enable KTD for the drivers in the &PATHS I enter"
	optSettings_ktd_05		= "Enable KTD for the drivers that match the PA&TTERNS I enter"
	optSettings_ktd_06		= "KTD cache location"
	; %s="%SystemRoot%\DriverPacks"
	optSettings_ktd_07		= "&default (%s)"
	optSettings_ktd_08		= "&custom"
	optSettings_ktd_09		= "Enter your custom KTD cache location."
	optSettings_ktd_desc		= "KTD is an option that allows you to Keep The Drivers after setup finishes. This means the drivers will remain available for installation: you can add hardware that is not supported by default and thanks to KTD, their drivers can be installed without having to download the correct drivers or searching for a support CD."

optSettings_ktdSett_tree		= "KTD settings"
	optSettings_ktdSett_title	= "KTD settings"
	optSettings_ktdSett_01		= "KTD is disabled: no further settings needed!"
	optSettings_ktdSett_02		= "KTD is enabled for all (available) DriverPacks: no further settings needed!"
	optSettings_ktdSett_03		= "Select &all"
	optSettings_ktdSett_04		= "Select &none"
	optSettings_ktdSett_05		= "Here you can enter the paths of the drivers you wish to apply KTD on. You should separate paths using a semi-colon (;).||A correct example:|D\G\N\1;D\W||An incorrect example:|D\G\N\1\nv4_disp.inf;D\W\||Note: KTD will be applied on the directories you specify AND ALL THEIR SUBDIRECTORIES!||Now delete this informative text and enter the paths you need!"
	optSettings_ktdSett_06		= "&Clear"
	optSettings_ktdSett_07		= "Here you can enter the patterns any of the HWIDs of a .inf file of a driver should match before KTD would be applied onto that driver. You should separate the patterns using a semi-colon (;).||A correct example:|VEN_10DE;USB||An incorrect example:" & @CRLF & "VEN 10DE;USB||Note that KTD will be applied on ALL FILES AND ALL SUBDIRECTORIES of the directory in which ANY .inf with a match was in! This may seem problematic at first sight, but - in general - if there are multiple drivers in one directory (or drivers in one of the subdirectory), then that's because they are necessary or complementary for each other. This means the results would still be as expected!|Also note that you can use the device names (as specified in the .inf files' [HwidsDatabase] section) as a pattern!|Now delete this informative text and enter the paths you need!"
	optSettings_ktdSett_desc	= "DISABLED"

optSettings_qsc_tree			= "QuickStream Cacheâ„¢"
	optSettings_qsc_title		= "QuickStream Cache"
	optSettings_qsc_01		= "&Enable QSC (Recommended)"
	optSettings_qsc_02		= "&Disable QSC"
	optSettings_qsc_desc		= "QuickStream Cache is an option that creates a sliptream cache: you won't have to compress the DriverPacks again for each time that you slipstream them!||Important remark: FOR NOW you have to delete unused QuickStream Caches (QSC directory) yourself every once in a while!"

optSettings_other_tree			= "Other"
	optSettings_other_title		= "Other optional settings"
	optSettings_other_01		= "DriverPack Graphics A"
	optSettings_other_02		= "ATI Catalyst Control &Center (ATI CCC) (Requires .NET FW!)"
	optSettings_other_03		= "ATI Catalyst Control &Panel"
	optSettings_other_04		= "DISABLED"
	optSettings_other_05		= "Nvidia Control Panel"
	optSettings_other_06		= "Nvidia Control Panel (old style)"
	optSettings_other_07		= "Nvidia Control Panel both"
	optSettings_other_desc		= "DISABLED"

overview_tree				= "Overview"
	overview_title			= "Overview of settings"
	overview_01			= "Platform"
	overview_02			= "default"
	overview_03			= "custom"
	overview_04			= "No DriverPacks selected."
	overview_05			= "Not yet specified."
	overview_06			= "&Export settings"
	overview_desc			= "DISABLED"

[wnt5_x86-32_bartpe__GUI]
settings_dps_tree			= "DriverPacksâ„¢"
	settings_dps_title		= "Select the DriverPacks to slipstream"
	settings_dps_01			= "DriverPack MassStorage text mode drivers are necessary if you wish to|boot from a mass storage controller that's not supported by default."
	settings_dps_02			= "Select &all"
	settings_dps_03			= "Select &none"
	settings_dps_desc		= "DISABLED"

overview_tree				= "Overview"
	overview_title			= "Overview of settings"
	overview_01			= "Platform"
	overview_02			= "default"
	overview_03			= "custom"
	overview_04			= "No DriverPacks selected."
	overview_05			= "Not yet specified."
	overview_06			= "&Export settings"
	overview_desc			= "DISABLED"

The new entries are the last three, just FYI (new BASE will pop an error about it, but without you wouldn't know)...

As it is possible to use either the new style, the old style (yes, it's still in the new drivers!) or even both by simply adding a registry entry (with three different values for each option), a selection could be added to BASE just as it is with ATI CCC or CP (which, albeit, does not feature the "both" option due to technical limitation).



This feature will be made available in the upcoming BASE 8.08.

Kees030 wrote:
Helmi wrote:

look up INFs for matching HWIDs (don't we have such a tool already, BTW?)

I think this is what WsnoW's Drivers Pack Unpacker & Installer does (http://forum.driverpacks.net/viewtopic.php?id=2403).

Nope, that may be able to do that but I was talking about a Team-only programme (so you may not know it, was more a hindsight to Jeff wink).

Still, if this tool can help with the idea, why not!

OverFlow wrote:

perhaps someone will also find this appealing and write a "Pack Pruner" application wink
this could easily be a stand alone app that lists folders with checkboxes and a description...
this app could be run prior to DriverPacks BASE for customizing the packs for a specific set of machines (or one).

Ah yes, it could work as follows:

First, you run HWID on all machines that you want drivers from included in the pruned packs.
Then, this stand-aslone app would use these different HWID files as a reference for which files to be kept from the packs.
It would then upack all of them (that will take some space, around 2GB I figure), look up INFs for matching HWIDs (don't we have such a tool already, BTW?), move the folders and sub-folders containing those INFs to a new DIR, repack that as a 3rd party DriverPack and provide it for BASE for slipstreaming.

IDK how to preserve Finisher compatibility this way, but maybe you could do without (3rd party DriverPack ususally do not provide support for the Finisher anyway so you wouldn't have it if you made it yourself, either, unless you were up for some extra work).



Problem's just, I wouldn't know how to code that idea into a binary tongue