[REL] DP_Monitors_wnt5_x86-32_908130 (Page 1 of 3)

There's already a Monitor pack that also covers LC displays.
Did you check with that one so you only included drivers that were missing from it?

Otherwise, I suppose there will be lots of driver overlapping.

Coming up next - useful links:
• If you like this project, please support it with your donation!      • Grab your HW info (HWIDs) here!     
• If you are a newbie, be sure to check out the DriverPacks tutorial!     • Here's how to create your own DP!

Ok, that means we should prune the old pack of any LCD drivers (but only if they are really duplicated, otherwise, migrate them to the new LCD pack) and rename it to CRT or something to indicate it catches all but LCD drivers.

I don't see any reason to have an driver included more than once, especially, when users can easily customize the dp3ps to fit their needs.

Coming up next - useful links:
• If you like this project, please support it with your donation!      • Grab your HW info (HWIDs) here!     
• If you are a newbie, be sure to check out the DriverPacks tutorial!     • Here's how to create your own DP!

Wow... Nice job!

DP BartPE Tutorial   DP_BASE Tutorial   HWID's Tool     Read BEFORE you post    UserBars!

The DriverPacks, the DP_Base program, and Support Forum are FREE!.

Firstly, a few more infos would be nice.
Did you prune any duplicated driver files?
Did you include any further possible updates for CRTs?

Secondly, please for God's sake do use the official hosting provided to you by DP.net!
There is absolutely no need whatsoever to use OCHs when our own server is up and running!
The time I have to wait on RS.com for even starting the DL I could already have well finished it were it hosted on our server (speed is higher than on RS.com, too).

Thirdly, you totally messed up the folder structure which will mean not only will the Finisher fail to delete the remaining files, also will %systemdrive% be cluttered with 26 files and folders...

Please read the tut on how to properly create a 3rd party DriverPack again and try to follow it.
Your effords in honour, but you aren't doing anyone favour if you do not stick to our guidelines.

EDIT:
Oh, and fourthly, WTF is a 12MB .BMP file doing in there???
DP_Monitor_wnt5_x86-32_81021.7z\IIY\
Just spotted by coincedence...

Coming up next - useful links:
• If you like this project, please support it with your donation!      • Grab your HW info (HWIDs) here!     
• If you are a newbie, be sure to check out the DriverPacks tutorial!     • Here's how to create your own DP!

Alright, if this is just a driver archive, then please don't call it DriverPack because that implies it was created according to our standards and can be used as one.
That would save less experienced users a lot of trouble and us unnecessary support issues (re: Finisher).

As for pruning, I was assuming that if two packs that both deal with display drivers are combined, there may be some files overlapping in different dirs.
In order to save space, all duplicate files (i.e. drivers for same HWIDs but different versions as well as byte-identical files (checksum)) need to be found (there's tools helping you) and deleted so only one version remains.

As for the CRTs, samlab ONLY updated LCDs, you combined both the old monitor pack (which contained both CRTs and LCDs) with his new and comprehensive LCD pack.
Therefore, if you did not update CRT drivers, then they were not updated at all.

If you also did not prune duplicate files, then best you did was extracting both packs, merging folders and repacking.

Sorry for the harsh words, but that hardly justifies a version update and does not gain anything really.
I am always very happy to see users contribute but there are certain standards that need to be met.
If you fail to do so, all you achieves was making yourself a lot of work with no usable outcome.
I'm not trying to discourage you, just making you aware of possible futile work. That would really help no one.

As for the .BMP, you are correct, I only spotted it in 7zip.
Maybe it's a glitch, what version are you using and what compression settings?

Coming up next - useful links:
• If you like this project, please support it with your donation!      • Grab your HW info (HWIDs) here!     
• If you are a newbie, be sure to check out the DriverPacks tutorial!     • Here's how to create your own DP!

Ok, I see now.

As for NA and EU versions of the driver, are there any differences?
This is the first time I have heared of regional drivers (well, apart from scanner drivers due to some obscure taxing by the EU) apart from translations of GUI and manual.

As for tools, there are some posts on the forum about it.
Can't remember all links right now, but you should focus on the Software forum and maybe give these two a try:
http://forum.driverpacks.net/viewtopic.php?id=3148
http://forum.driverpacks.net/viewtopic.php?id=3018

Coming up next - useful links:
• If you like this project, please support it with your donation!      • Grab your HW info (HWIDs) here!     
• If you are a newbie, be sure to check out the DriverPacks tutorial!     • Here's how to create your own DP!

Unless your name is Nvidia, if you have different HW, you'd asign them a different HWID, that's the whole point of it.
If the drivers are NOT compatible, yet HWIDs overlap, you will run into problems with the DriverPacks if you include both drivers (we do have such problems with NV, btw).
If you have the wrong HW and the wrong driver gets chosen (which will happen if HWIDs overlap; you cannot change the order in which drivers are being processed once the ISO is created), you may BSOD (for Kernel drivers at least).
Only way to get around this is to create an ISO that has the HWID for the device that you do not have removed.
Then, of course, it will no longer be universal.

Coming up next - useful links:
• If you like this project, please support it with your donation!      • Grab your HW info (HWIDs) here!     
• If you are a newbie, be sure to check out the DriverPacks tutorial!     • Here's how to create your own DP!

Nah, it's not off topic as it would affect the Monitor pack.

If there are two versions of the same driver (old and new) with naturally the same HWIDs, Windows will automatically pick the newer one - no problem there.
However, if there are two drivers that differ from each other not only in version/date, then it will still pick the newer one, however, this could be the wrong one.

It does not help placing the files in a different dir, as setup will search them all.

Sometimes, it may help to specify some super-generic IDs (only vendor and no device given for instance).
Yes, you will lose Driver Signing (assuming, that's what DS means, WHQL is the better term, IMO), but that is a small price to pay, IMO, if it means that this is the only way to actually make the driver install correctly AT ALL!
WHQL means nothing anyway, we've seen beta drivers get it, we've seen drivers that constanly BSOD get it.
Only problem is that WHQL'ed drivers will be prefered to non-WHQL'ed, even if older (IIRC).
That means you will have to disable the Signed Driver Policy as well as the Unsigned Driver Policy - again, not much of a sacrifice, IMO.
I've been doing so for years and have yet to experience one single disadvantage.

Coming up next - useful links:
• If you like this project, please support it with your donation!      • Grab your HW info (HWIDs) here!     
• If you are a newbie, be sure to check out the DriverPacks tutorial!     • Here's how to create your own DP!

Hello guys

Samlab, here it's a link for the latest DRIVERs and ICMs of the ALL Lenovo ThinkPad Notebook's LCD's:
http://www-307.ibm.com/pc/support/site. … MIGR-62923

Thank you!

Last edited by Grunger86 (2008-10-22 08:31:56)

I'm just going to throw this out there, for whatever it's worth..

Where I live you are not even able to purchase a CRT monitor anymore.  Literally.  They are history.  The government, education, and health care sectors even have to pay a huge surcharge per unit if for some reason they did want one and then were able to find someone willing to sell them.  It seems a bit like supporting 5.25" floppies.

Is there really a need to mess around with this excellent DP by adding this sort of stuff to it?

it's an excellent point

let's think in terms of a Legacy "CRT pack"   and  a "Monitor pack" (LCD or better)

DP BartPE Tutorial   DP_BASE Tutorial   HWID's Tool     Read BEFORE you post    UserBars!

The DriverPacks, the DP_Base program, and Support Forum are FREE!.

If it matters, I 'vote' for separate LCD and CRT monitor packs.