Topic: [REQ] Monitors - Like, how 'bout an update, eh?

Mr_Smartepants wrote:

The Monitors Third Party DriverPack needs a refresh and it's folder structure is appalling.
As an example;
DP_Monitor_wnt5_x86-32_1005.7z\D\3\MON\ACR\AF715\
should be;
DP_Monitor_wnt5_x86-32_1005.7z\D\3\D\A\A1\
...a reduction of 8 characters.  Compound that by a minimum of at least 50 other folder infractions like that and you could potentially save over 400 characters from the 4096 limit.
Third Party DriverPack webcam is another that I just finished that could have it's folders aggressively renamed to shave precious characters.  I just don't have the time.

ok, I'll do what i'm able & report back ASAP.  I have some family commitments to take care of over the next few days, forgive the lag time.
I'll make notes of any folder path changes, so as to avoid my own confusion, and to assist in creation of a changelog for a release candidate.

It is good have you give me direction; i wouldn't have more than a clue of where to properly begin.

Mr_Smartepants wrote:

A good place to start would be reading:
http://forum.driverpacks.net/viewtopic.php?id=5
http://forum.driverpacks.net/viewtopic.php?id=279 (which links back to first)
Have fun with it.  Once it becomes like work, it's no longer fun.

Thank you for the direction.  I will have fun, i repair monitors.  Wish i could use EDID code names.
Plan A:  - fix structure as per instruction
Plan B:  - testing phase
Plan C:  - add support for more LCD's/Plasmas, possible seperate CRT pack, perhaps?

Mr_Smartepants wrote:

The thing to remember is that the folder structure does NOT have to indicate what the manufacturer is.  You can include .txt files to explain the folder contents (like I do in DriverPack Graphics C\A).
For the next round of main NT5 releases, I think I'll really aggressively hit the folder structure.  It'll look ugly, but it must be done.

I understand, the next DP_Monitor pack is meant to be 11.08, not 11.09.

DP_Monitor_wnt5_x86-32_100711.7z is the latest, i gather?

These drivers supply resolution & horizontal-frequency limits (should the VGA cable not include pins 12 & 15 for the I2C bus - the best cables include pin-9 (+3.3 or +5V) enabling Windows EDID comm with AC disconnected from the Display).  The driver sometimes includes a color-matching profile.

  I wonder about the interoperability with Vista-7 that you have encountered previously.  Is it a case that the drivers that DO work in Vista-7 are already there, & those that work for both are included in the NT5 pack?

Mr_Smartepants wrote:

I guess, I don't know, I never use it.

OK, 'be aggressive' in folder size, that will save trouble later.

Sorry about this 'stilted' conversation.  I edit my posts in an attempt to keep my # of post down.  I find that it helps me to keep a 'running-tally' on whatever topic that i'm trying to research, & relay info.

Would 'D\3\M\' be an acceptable folder path name, if not how about 'D\3\Mo\' (Molybdenum)

mr_smartepants wrote:

The thing to remember is that the folder structure does NOT have to indicate what the manufacturer is.  You can include .txt files to explain the folder contents (like I do in DriverPack Graphics C\A).
For the next round of main NT5 releases, I think I'll really aggressively hit the folder structure.  It'll look ugly, but it must be done.

The 'Manufacturer' in the driver may rarely be the manufacturer of the panel, itself, anyway.  I would like to conform to ChangeLog/Contents convention established, previously.  How do i ensure credit is given to those that have written, previously?  I see 'by SamLab.ws - mindwarper' in the Info.txt, there are likely more, including you, Mr_Smartepants.
Would 'D\3\M\' be an acceptable folder path name, if not how about 'D\3\Mo\' (Molybdenum)

mr_smartepants wrote:

No, refer to the tutorials I linked above on Third Party DriverPacks building.
This Should be the new layout:
+D
---+3
------+B = Broadband Pack
------+BT = Bluetooth Pack
------+H = Human Input Device Pack (aka HID)
------+M = Modem Pack
------+Mo = Monitor Pack
------+P = Printer & Phone Packs
------+S = Scanner Pack
------+T = TV Pack
------+TS = Touch Screen
------+U = USB Pack
------+V = Virtual Pack (aka VMware)
------+W = WebCam Pack
------+X = Misc Pack

Although instead of using D\3\Mo (Monitor), I suppose we could use D\3\D (Display).  That might help a bit.
Oh, and including contributor names in parenthesis is acceptable (Mr_Smartepants). wink

'\D\3\D\' it is. cool  I see that i'm crediting SamLab.ws, mindwarper, compstuff & (Mr_Smartepants), is this list accurate & complete?  I don't want to ruffle anybody's corn-flakes! big_smile

I'll likely need to use a 2-character notation for the Manufacturer folder name, already have 27 folders, even with adding 0-9 numbers into the equation, that would make 36 main folders, max.

If i include lower-case letters, i guess that would make 62 combos in a 1-char mfg. folder name.

How does this look?

Ac - Acer
A  - AOC
As - ASUS
Be - Belinea
B  - BENQ
C  - CTX
D  - DELL
E  - Eizo
G  - Gateway
GB - GBM
H  - Hansol
HP - HP/Compaq
I  - IBM,Lenovo
Ii - Iiyama
IQ - ImageQuest
L  - Lenovo ThinkPad
LG - LG
MA - MAG
Me - Medion
M  - Mitsubishi
N  - NEC
NE - NEUOVO
No - Nokia
P  - Philips
Pr - Proview
S  - Samsung
So - Sony
V  - ViewSonic,OptiQuest

Last edited by TechDud (2011-08-29 17:24:41)

Re: [REQ] Monitors - Like, how 'bout an update, eh?

GTW folder found to contain Gateway drivers - not noted.
Nokia & proview folders only have *.icm files, not INF's & no *.cat's!  -- HELP sad
not listed in 10.05 'Drivers' tab on old download page.

who would have known that proview does LED street lighting? http://www.proview.com/en/support_download.asp

Last edited by TechDud (2011-08-07 00:31:52)

Re: [REQ] Monitors - Like, how 'bout an update, eh?

I'm going to poke around some old backups for the 9xx versions.
Is there any way the last 14 posts (& this one too) could be added to the "[REL] DP_Monitor_wnt5_x86-32_100711.7z by compstuff " thread, or given it's own topic?

Re: [REQ] Monitors - Like, how 'bout an update, eh?

Would anyone have a clue as to what the \D\3\MON\Medion\Medion MD30717VE_Dsub_Monitor_Vista x86.cpk file is & what is there doing?  It can go?
Excerpt from SubmissionInfo.xml:

<?xml version="1.0" encoding="utf-8"?>
<Submission Name="30717-MOR-X86VI">
  <FailureFilterExtensionRootNode SubmissionName="30717-MOR-X86VI" SubmissionId="26" />
  <VerificationFile Msg="Verification.wtl File Does Not Exist" />
  <DTMResults>
    <Errors />
    <TestDate>1/17/2007 2:56 PM</TestDate>
    <DTMVersion>1.0.6000.002</DTMVersion>
    <ClientVersion>1.0.6000.0</ClientVersion>
    <StudioVersion>1.0.6000.0</StudioVersion>
    <ContentVersion>1.0.6000.0</ContentVersion>
    <Qfe>QFE002</Qfe>
    <Qfe>QFE004</Qfe>
    <Qfe>QFE005</Qfe>
    <WTTVersion>2.2.2098.0</WTTVersion>
    <ProductTested>
      <SubmissionType>Driver</SubmissionType>
      <Category>Device Logo</Category>
      <OS>Windows Vista Client</OS>
      <SubCategory>Display > Monitors > LCD</SubCategory>
      <Qualification>Basic</Qualification>
      <DriverInformation>
        <DriverFileName Hash="532EA210938843F912C431D3496061CE6ABC71">MD30717VE.inf</DriverFileName>
        <DriverFileName Hash="65CC634E842C88D42B93CE3698B016D9EB2CD1">md30717ve.icm</DriverFileName>
        <DriverFileName Hash="65CC634E842C88D42B93CE3698B016D9EB2CD1">md30717ve.icm</DriverFileName>
        <DriverFileName Hash="532EA210938843F912C431D3496061CE6ABC71">MD30717VE.inf</DriverFileName>
        <HardwareId>Monitor\MED87F5</HardwareId>
        <DriverFileVersion>01/15/2007, 1.00</DriverFileVersion>
        <DeviceId Resource="35">DISPLAY\MED87F5\5&1623011C&0&UID268435456</DeviceId>
      </DriverInformation>
      <SubmissionDeviceData>
        <DeviceData Name="LogoProgramId">DisplayMonLCD</DeviceData>
        <DeviceData Name="LogoDimensionName">DisplayMonitorLCD</DeviceData>
        <DeviceData Name="LogoProgramDescription">Display > Monitors > LCD</DeviceData>
        <DeviceData Name="Category">Display\Monitors\LCD</DeviceData>
        <DeviceData Name="LogoProcessorArchitecture">X86</DeviceData>
        <DeviceData Name="LogoOperatingSystem">Windows Vista</DeviceData>
        <DeviceData Name="WhqlOs">Windows Vista Client</DeviceData>
        <DeviceData Name="WhqlQualification">Basic</DeviceData>
      </SubmissionDeviceData>
      <TestResults>
        <ResultDetails>
          <Pass Id="502" Name="EDID 1.3 and DDC" Guid="3d089993-3e87-4c52-8f57-8bf9db6b818b" ResultGuid="8f37018d-5896-4268-ac86-e31e6fd05c84" PassCount="32" FailCount="0" NotRunCount="0" />
          <Pass Id="503" Name="Flat Panel Refresh Rate (Manual)" Guid="82e968cd-f6ad-42b7-be1c-f8d430a56976" ResultGuid="c8ef3f5a-1285-4886-b067-84912e0ee8d5" PassCount="1" FailCount="0" NotRunCount="0" />
          <Pass Id="504" Name="Run INFTest against a single INF" Guid="09b7ac28-4835-4b8a-a666-bf0edf723d3c" ResultGuid="2bb6751b-60b8-4fd8-a643-f5bbb866dec1" PassCount="1" FailCount="0" NotRunCount="0" />
        </ResultDetails>
      </TestResults>
    </ProductTested>
  </DTMResults>
</Submission>

MD30717VE.cat is missing, too.

Re: [REQ] Monitors - Like, how 'bout an update, eh?

Like I said, it's a big mess! wink
Good luck! {runs away to minimum safe distance...}

Read BEFORE you post.  HWID tool   DriverPacks Tutorial   DONATE!
http://driverpacks.net/userbar/admin-1.png
Not all heroes wear capes, some wear Kevlar!

Re: [REQ] Monitors - Like, how 'bout an update, eh?

good luck with that work...
I can imagine it can be a tedious job...
Will be eager to help test it later on smile

http://d1syubgj0w3cyv.cloudfront.net/cdn/farfuture/Av2BDsDf_iiqO8a4dpI49DKicUs_0zEQtEPcTGyCqV4/perpetual:forever/userbar/tester-1.png

Re: [REQ] Monitors - Like, how 'bout an update, eh?

current changelog:

DP_Displays_wnt5_x86-32
----------------------------------------------------------------------------------------------------------------------------------------
v1109081
- updated folder structure - see contents.txt (all updated files are OEM-sourced unless otherwise noted)
- updated lenovo thinkpad to "DriverVer=03/04/2011,4.36.0.0" to support newer laptop displays
- renamed the IBM/LEN L197 Wide driver files as per request http://forum.driverpacks.net/viewtopic. … 143#p43143 by techie1
- updated Proview drivers to "DriverVer=03/29/2005,2.00.0.1" rev2.04 to fix missing inf
- restored missing NOK020326.inf for Nokia Monitor support (ViewSonic)
- restored missing OQ030926.inf for OptiQuest Monitor support (ViewSonic)
- updated ViewSonic drivers & removed excess installshield, etc. files
- added Sharp LCD drivers from Windows Update Catalogue
- added newest Acer, Gateway/Packard Bell, & eMachines drivers
- restored missing Mistubishi drivers (v91lcd.inf, v71lcd.inf, v51lcd.inf, v50lcd.inf)
- restored missing NEC drivers (neca700.icm, neca900.icm, lcd2080uxi.icm, 'nlxxxxxx.inf') & updated
- updated iiyama drivers & included iiyama.MonTest_2_1.exe, Entech's SoftOSM (incl. in OEM driver pack) & 2 test-images
- added Eizo screen-adjustment utilities
- Updated Sharp drivers
- switched crc-hashing algorithm to sha1 - same as MS Security Catalog file signatures
- added 'ICC Profile Inspector' & 'wxProfileDump' from the International Color Consortium
     http://www.color.org/ICCProfileInspector2_4.zip      http://www.color.org/wxProfileDump.zip
- restored missing Sony .Inf's & added drivers from Windows Update Catalog & OEM
- checked for invalid or ICC v4 profiles in all folders (all profiles need verification of ICC compliance)
- added shortcuts for driver download pages in 'z' folder - To be 7-zipped, 'z' folder eventually removed
- restored missing AOC .Inf's & updated from Windows Update Catalogue; added AOC e-Saver & iMenu to apps for DDC/CI
- removed Vista(min.) .cat's from AOC, Acer, LG folders
- resolved .Inf file names not matching .cat files for Belinea; 103052_art no 121721.inf HWID corrected
- Belinea all-in-one (non-WHQL) .Inf updated to Belinea_362.inf
- renamed pack DP_Displays_wnt5_x86-32, changed 7-zip archive word-size to 256 to comply with Bâshrat's DriverPack Directives
- sorted out LG drivers, included link for forteManager(seperate folder for supporting models), updated from OEM & WindowsUpdateCatalog
- fixed missing files from Hansol & added adjustment app with files from personal backup (originally downloaded from OEM)
- added Acer, Daytek, LG & Proview CRT drivers from personal backup & added Entech softMCCS, Gateway EzTune link, to apps
- added Daewoo drivers & merged with DayTek
- added missing LG .inf's, updated Proview LCD driver from DP_Monitor_wnt5_x86-32_81227.7z
- updated Medion drivers from OEM & Windows Update Catalog
- added Medion.auto.exe & Medion.Pivot-dbshell-R2003-01-21-1548-22.exe to apps (included in OEM driver pack)
- added TriGem drivers from Windows Update Catalog
- added Seanix drivers from a personal backup (originally downloaded from OEM)
- removed &/or copied Vista-7 drivers from Medion & Iiyama & updated from Windows Update Catalog, & again from OEM
- restored missing NEC S527NCI.inf, VR15NCI.inf, VR17NCI.inf, & VR19NCI.inf from DP_Monitor_wnt5_x86-32_81227.7z
- found additional NEC drivers & updated from Windows Update Catalog & added apps

  16.9MB of utils., so far - to be reduced later to links, License Agreement dependant
    (13019 files, 261 folders, 159MB total, ~39.2MB compressed)

Known Issues:
1)  VG1932wm driver missing (viewsonic has VX1932wm by mistake?)
2)  Acer a) B1996-99.icm missing for ac707.inf, ac713.inf, ac915.inf
         b) B1786MNST/L.icm missing for ac707.inf & ac713.inf; probably an illegal name, too
3)  Missing Acer h244hl & al1602w driver
4)  Acer 'b243ph.ICM'  is filled with nulls & is invalid
5)  Acer X233HZ is ICC v4 & may not be compatible with xp, yet the Security Catalog returns OSAttr=2:5.1,2:5.2,2:6.0
6) *resolved
7)  Acer 'AL1501.ICM', \p205h\lc5\'p205h.icm' may be invalid
8)  Sony_d50.icm, Sony_d65.icm, & Sony_d93.icm have been updated to the latest version available.  This will break driver signing
       for many Sony drivers.  Older versions exist in the 'old' folder.
9)  CTXLCD01.ICM is missing
10) Dell 1400fp.icm, IBM l152.icm, NEC & Mitsubishi RDS173X.icm, & Medion MD1786LH.icm may be invalid, there is a problem in the desc. index.
11)*resolved
12) Gateway FHD2302.icm is invalid; actually, it IS the .Inf, over & over again!
13)*resolved
14)*resolved
15) NEC & Mitsubishi WG_50CRT.icc, WG_65CRT.icc, WG_95CRT.icc appear to be CRT_A22 orphans
16)*resolved
17) Medion\AN\S13.icm & S14.icm are invalid; C07.icm & c12.icm not good, either.
18)*resolved
19) Phillips 200BW8, 220BW8, & 220WS8 are ICC v4 & may be backward-compatible with xp, the security catalogs return
       OSAttr=2:5.1,2:5.2,2:6.0
20) ViewSonic va1916w.icm is ICC v4 & may be compatible with xp, the security catalog says OSRAttr=2:5.1,2:5.2,2:6.0
21)*resolved
22) AOC AOC4264 driver is missing; ICM is orphaned
23) aoc V17.icm may be invalid
24) Belinea 1112202.cat may not match '22W artistline_art no 112202.inf'
25) Belinea 103052_art no 121721.inf signing is broken, as the HWID's within were incorrect
26) Belinea ICC color profiles may need to be added to Belinea_362.inf (it's non-WHQL anyway)
27)*resolved
28)*resolved
29) Medion md41977fes01.cat & AN\medion17.cat are not digitally signed
30) Medion MD1998LJ.cat is actually 1998of.cat; therefore MD1998LJ driver files are unsigned
31) TriGem drivers exist in the LG folder
32) Iiyama ple430.inf is missing; ple430.icm does not match hash in ple430.cat
33) Iiyama ple430a.cat is missing it's files; ple430b.cat is missing (as found from OEM)
34) Iiyama AS4821.inf (v1.02) from non-WHQL files has less restrictive timings & may work better, despite being non-WHQL'ed
35)*resolved
..

v100711
Updated: \LEN DriverVer=12/14/2009, 4.34.0.0
..

v100523
Changes since 9.11.01 - COMPSTUFF 05/23/10
-ADDED Dell P2210 Monitor Driver DriverVer=01/20/2009,1.0
..

v91101
Changes since 9.08.130
11/16/09 - Compstuff - Replaced 0 byte nl171v.inf with correct NEC inf 07/03/2006,1.06.0703.1334
11/16/09 - Compstuff - Updated SyncMaster 720N driver from 07/26/2006 ver. 2.0HC tot 03/28/2007 ver. 3.0HC
----------------------------------------------------------------------------------------------------------------------------------------
Credits:

compstuff, mindwarper, (mr_smartepants), muiz, (OverFlow), SamLab.ws, TechDud, Us2002, Wo Wo your hands
..

---------------------------------------------------------------------------------------------------------------------------------

DP_Displays_wnt5_x86-32 Contents:
----------------------------------------------------------------------------------------------------------------------------------------------------------
\D\3\D\               - includes 'semi-universal' utilities, USE ONLY AT YOUR OWN RISK.
A  - AOC (TPV)        - Admiral Overseas Corporation, a brand of Top Victory (TPV) Technology Ltd, as is Envision Peripherals (EPi)
Ac - Acer
AG - AG Neovo
As - ASUS             - aka Republic Of Gamer
B  - BenQ             - spun-off from Acer(2001), includes AUO LCD panel division, BenQ is now a division of Qisda Corp.
Be - Belinea          - formerly a brand of Maxdata, bought by Brunen IT (2008), now owned by Bluechip Computer AG
C  - CTX (BVI)        - aka Chuntex Electronic Co. Ltd
D  - Dell
Da - Daytek/Daewoo    - a Canadian subsidiary of Daewoo International in Korea; now known as Daewoo International
E  - Eizo/Nanao
eM - eMachines        - now a division of Gateway (2004)
G  - Gateway          - aka Gateway2000, now a division of Acer (2007)
GB - GBM Periphery    - all .icm's are labelled 'Gateway2000'; defunct AFIK
H  - Hansol           - spin-off from Samsung Group (1993)
HP - HP/Compaq
HS - HannStar         - aka HANNspree
I  - IBM/Lenovo       - lenovo acquired IBM’s Personal Computing division (2005); co-announced NEC Lenovo Japan Group, a joint venture (2011)
Ii - Iiyama
IQ - ImageQuest       - aka Hyundai ImageQuest Co., aka Hyundai IT
L  - Lenovo ThinkPad
LG - LG Electronics   - Lucky/GoldStar until 1995 @ Zenith acquisition; not to be confused with LG.Phillips LCD nor LG.Phillips Displays(now LG Displays)
M  - Mitsubishi       - formerly NEC/Mitsubishi, now Mitsubishi Electric
MA - MAG Technology   - aka MAG InnoVision; a brand of ProView Tech. Int.; seized by Chinese banks
Me - Medion           - aka Cicero aka Tevion aka Cybercom aka Cybermaxx aka Life aka Lifetec aka Micromaxx aka Traveler; acquired by Lenovo (pending 2011)
N  - NEC Display      - formerly NEC/Mitsubishi (pre-March2005); aka NDS; co-announced NEC Lenovo Japan Group, a joint venture (2011)
                          may include drivers for Mitsubishi & Packard Bell Displays; also includes Display Port support
No - Nokia            - acquired by ViewSonic (2000)
O  - Optiquest        - brand of budget displays by ViewSonic
P  - Philips          - Philips Electronics Co; now Koninklijke Philips Electronics N.V.; not to be confused with LG.Phillips LCD nor LG.Phillips Displays
PB - Packard Bell     - subsidiary of Acer (2008), formerly owned by NEC
Pr - ProView (PTI)    - (PTS) in Asia; includes brand names: Proview, MAG, EMC, KDS, Xerox(Under license)
                           sued Apple over trademark infringement on iPad; sued by Apple; seized by Chinese banks
S  - Samsung          - Samsung Electronics (est. 1969) is a subsidiary of the Samsung Group (also a Korean word meaning "three stars" that shine brightly)
Se - Seanix
Sh - Sharp
So - Sony             - current slogan:  "Just Imagine"
TG - TriGem
V  - ViewSonic

z  - 'support'        - OEM support driver download shortcuts, ICC profile & info shortcuts - to be zipped for RC
----------------------------------------------------------------------------------------------------------------------------------------------------------
cool cool

from 1300-or-so to 1800+ files - that viewsonic folder was a lesson.  Time to find some more updates, any brand preference?  I wonder if there is an INF-checking util, out there; maybe something that could find unreferenced files, from the corresponding inf files.

Last edited by TechDud (2013-04-05 13:02:06)

Re: [REQ] Monitors - Like, how 'bout an update, eh?

No, refer to the tutorials I linked above on Third Party DriverPacks building.
This Should be the new layout:
+D
---+3
------+B = Broadband Pack
------+BT = Bluetooth Pack
------+H = Human Input Device Pack (aka HID)
------+M = Modem Pack
------+Mo = Monitor Pack
------+P = Printer & Phone Packs
------+S = Scanner Pack
------+T = TV Pack
------+TS = Touch Screen
------+U = USB Pack
------+V = Virtual Pack (aka VMware)
------+W = WebCam Pack
------+X = Misc Pack

Although instead of using D\3\Mo (Monitor), I suppose we could use D\3\D (Display).  That might help a bit.
Oh, and including contributor names in parenthesis is acceptable (Mr_Smartepants).

We can reduce all  3rd Party path by changing a structure in a next way:
+D
------+3B = Broadband Pack
------+3BT = Bluetooth Pack
------+3H = Human Input Device Pack (aka HID)
------+3M = Modem Pack
------+3Mo = Monitor Pack
------+3P = Printer & Phone Packs
------+3S = Scanner Pack
------+3T = TV Pack
------+3TS = Touch Screen
------+3U = USB Pack
------+3V = Virtual Pack (aka VMware)
------+3W = WebCam Pack
------+3X = Misc Pack

Re: [REQ] Monitors - Like, how 'bout an update, eh?

magon wrote:

We can reduce all  3rd Party path by changing a structure in a next way:
+D
------+3B = Broadband Pack
------+3BT = Bluetooth Pack
------+3H = Human Input Device Pack (aka HID)
------+3M = Modem Pack
------+3Mo = Monitor Pack
------+3P = Printer & Phone Packs
------+3S = Scanner Pack
------+3T = TV Pack
------+3TS = Touch Screen
------+3U = USB Pack
------+3V = Virtual Pack (aka VMware)
------+3W = WebCam Pack
------+3X = Misc Pack

No, unfortunately the way DriverPacks BASE and DriverPacks Finisher are coded the D\3\ folder structure is hard-coded into both apps for KTD compatibility.  A rewrite of both would be required.

Wim Leers wrote:

Note: in the past you didn't have to use the "3" subdirectory. This is now a requirement, to make the KTD functionality compatible with the Third Party DriverPacks

Read BEFORE you post.  HWID tool   DriverPacks Tutorial   DONATE!
http://driverpacks.net/userbar/admin-1.png
Not all heroes wear capes, some wear Kevlar!

Re: [REQ] Monitors - Like, how 'bout an update, eh?

TechDud wrote:

I wonder if there is an INF-checking util, out there; maybe something that could find unreferenced files, from the corresponding inf files.

Well, sort of. 
I use "FindHWIDs" all the time when building packs.  It cuts my research time by about 99% and it's an awesome tool.
http://forum.driverpacks.net/viewtopic.php?id=3018
I use it for detecting duplicate HWIDs and drivers but it's capable of so much more.  Contact the author (KickArse) with your idea and maybe he can code it.

Read BEFORE you post.  HWID tool   DriverPacks Tutorial   DONATE!
http://driverpacks.net/userbar/admin-1.png
Not all heroes wear capes, some wear Kevlar!

Re: [REQ] Monitors - Like, how 'bout an update, eh?

mr_smartepants wrote:

No, unfortunately the way DriverPacks BASE and DriverPacks Finisher are coded the D\3\ folder structure is hard-coded into both apps for KTD compatibility.  A rewrite of both would be required.

Wim Leers wrote:

Note: in the past you didn't have to use the "3" subdirectory. This is now a requirement, to make the KTD functionality compatible with the Third Party DriverPacks

Yes I know
And use KTD  for my own pack. All another 3DParty Packs I install after Windows with Drivers Installer Assistant by Romeo91 
If such a little  modification of DPs_BASE is not comprehensible I will be disappointed

Re: [REQ] Monitors - Like, how 'bout an update, eh?

Fitting, then that monitors could be '3\D' big_smile

Can anyone help me, to explain what the heck a '.cpk' file is (7-zip 'sees' it as an archive), and how it relates to driver signing?  For example:  ftp://ftp.gateway.com/pub/hardware_supp … y/FHX2300/
Maestro222W.cat is missing.  Similarly, i don't know what to to with the various .XML files that i'm finding.  I'm somewhat stuck, until i get some direction on this.

I would like to build this pack with an eye towards possibly updating Vista-7.

I found a good page that shows a VGA cable with no EDID support, forcing the use of a driver.  Unfortunately, you cannot tell from just looking at it, you have to find continuity on pins 12 & 15.
http://support.gateway.com/s/monitor/sh … ins1.shtml
Many older KVM's don't properly pass these signals, either.  In one case, this behaviour is desirable; for instance an Acer AT3201W can be used to down-convert a 1080p VGA stream, to a resolution that it can display.  (This actually looks better & is more responsive than having my old Radeon9100 lappy try to convert the image on-the-fly).  I'm not able to do this with a cable that does properly pass the EDID info.

If your monitor connects over VGA, and you cannot get windows to autodetect it, either a non-compliant cable is being used, your using an older KVM, or the EDID serial-ROM (24C02, etc.) in the monitor is corrupted/damaged.  DVI & HDMI use similar communication methods to allow Windows to autodetect the display's proper parameters.  However; sometimes they can exhibit similar symptoms, leading one to believe the Serial ROM is damaged or corrupted, requiring reprogramming or replacement.

Last edited by TechDud (2011-08-08 15:44:16)

Re: [REQ] Monitors - Like, how 'bout an update, eh?

Take a look in the .inf file.  Generally, if a questionable file isn't listed anywhere in the .inf, then it isn't needed.  Some files are only needed by the installer (setup.exe) and not by the drivers.
You can find 99% of the files in "sourcedisksfiles" & "*copyfiles*" sections of the .inf.  Sometimes, .dll files are referenced in the hexedit code of .sys files, but that's rare.

Read BEFORE you post.  HWID tool   DriverPacks Tutorial   DONATE!
http://driverpacks.net/userbar/admin-1.png
Not all heroes wear capes, some wear Kevlar!

Re: [REQ] Monitors - Like, how 'bout an update, eh?

What's the difference between Windows Color System & Image Color Management, when dealing with ICC/ICM profiles, not counting 64-bit?

Whoops, found the answer here: http://www.colorwiki.com/wiki/Vista%27s … stem_-_WCS

Windows 2000 and XP include Microsoft's CMS called Image Color Management (ICM). The Color Management Module (CMM - I hope this is the last of these acronyms) was originally written by Heidelberg and has not seen much of upgrades or bug fixes over the years. As a result of this low priority on Microsoft's list, ICM has had enough bugs and short comings few people rarely use it for color conversions. Though you can select ICM for conversions in Photoshop and other applications, few users do. Many print drivers and RIPs on Windows use CMMs licensed from Kodak and other companies. It's fair to say that those of us in the professional realm had given ICM up for dead.

Recall that ICC device profiles perform half the required color conversion.

Features

    •    WCS profiles are NOT compatible with ICC profiles. They are XML-based text files that are much simpler and do not contain gamut mapping calculations at all. Think of them as slightly processed measurement files.

    •    There are three different kinds of WCS profiles: Device model, gamut mapping method, and appearance model.
        The device model profiles contain the color measurement information from the actual graphics device.
        The gamut mapping method profile selects which gamut mapping technique the user desires. WCS is based on CIECAM02 appearance modelling.
        The appearance model profile contains the parameters for CIECAM02 transforms. This is where you might specify the color temperature of the lighting used to view your print or the color and intensity of its surround.

    •    WCS and ICM work hand-in-hand in Vista. If all the profiles supplied in a color transformation are ICC-format, then ICM is call upon to do the processing. If one or more of the profiles is WCS-format, then WCS takes over and performs the conversions.

    •    If WCS is performing the conversions, any ICC profiles in the workflow are converted to WCS format prior to processing the image color data. Any gamut mapping in the ICC profile is ignored and WCS treats it as a virtual device, reconstructing the device measurements from the A2Bn tags in the ICC profile.

    •    Microsoft has upgraded ICM to version 3, fixed its bugs and updated it to use ICC version 4 profiles, bringing it up to date and hopefully removing any processing problems we've seen in the past. This is great news as it shows that Vista will be able to play with all the ICC profiles in the world and fit into existing color workflows. ICM is still based on the original Heidelberg code.

    •    Because WCS calculates the color transformation on the fly, gamut mapping should be more efficient and accurate. WCS has the information for each device's gamut and can presumably make better judgements and choices when dealing with out of gamut colors. This also means that black point compensation is automatically handled at this stage. (more on BPC below)

    •    WCS can also perform calculations using floating point math and allows device models to describe where to map diffuse whites and specular highlights. This and other enhancements allow for a number of new things to occur such as avoiding possible round-off errors on 16 bit devices, support for high dynamic-range devices (like the new digital projectors in movie theaters) and also extended gamuts.

    •    WCS can also be set to preserve the black channel through a workflow. Something for which ICC users require device link profiles at this time.

    •    By separating the device information from the gamut mapping and viewing data, users may be able to address specific color problems in the most appropriate area. Gamut mapping issues could be addressed separately from device measurements and viewing issues. In ICC profiles today, all the functions are combined during profile construction into one table.

    •    WCS can convert WCS profiles to ICC profiles. After conversion, the original WCS device profile is embedded into the ICC profile as the 'MS00' tag. In this manner WCS profiles can be embedded into image files as ICC profiles.

    •    WCS is only available with Windows Vista and Microsoft has stated it will not be made available to Windows XP.

    •    WCS was developed in conjunction with Canon.

    Microsoft has documented the daylights out of WCS so very little of it is based on 'magic sauce'. Also, many of the algorithm components are extensible or replaceable so developers can write their own plug-ins and alter device models (how the system expects devices to behave, inks to mix, paper to absorb), gamut mapping and so forth.

    Microsoft has created a useful demo image that contains an ICC profile that has a WCS profile embedded within it. The image and profiles are constructed in such a way that a Ducati motorcycle appears to be blue, green or red if the profile is entirely ignored, the ICC component is used, or the WCS component is used, respectively. It's worth a look:

<http://blogs.msdn.com/color_blog/archiv … ofile.aspx>
Shortcomings

So, with all these new features and capabilities are there any shortcomings? Well, yes. This is a version 1.0 product after all.

    •    The WCS CMM essentially has black point compensation ON at all times. In most cases this is good, but if you don't want the blacks intelligently improved - such as when you are proofing - then it means you won't be able to simulate a printing system that has lighter blacks than your inkjet or monitor.

    •    WCS can handle CMYK devices but at this time there is NO control over CMYK parameters such as total ink limit, black start, GCR level, etc. Laser printers are very different than inkjets which are very different than offset presses. WCS can support different device model plug ins but that is more like presets and I believe there is only one CMYK model shipping with WCS at this time.

    •    WCS does not support more than 4 print channels. So no Hexachrome or other n-color printing systems.

    •    WCS, like Windows XP, still does not load calibration curves from monitor profiles. This one deserves a little background...

& from the WCS white-paper from MS here: http://download.microsoft.com/download/ … e6/WCS.doc

•    Provides forward and backward compatibility with ICC-based device profiles and sRGB

•    Uses limited user access and XML profiles to improve security.

WCS - ICM test file http://blogs.msdn.com/cfs-filesystemfil … rofile.zip from http://blogs.msdn.com/b/color_blog/arch … ofile.aspx funny, the bike still looks green without the profile mad
I still don't understand what the .cpk files are.

Last edited by TechDud (2011-08-08 20:19:44)

Re: [REQ] Monitors - Like, how 'bout an update, eh?

TechDud wrote:

I still don't understand what the .cpk files are.

http://www.fileinfo.com/extension/CPK

Log file generated by Driver Test Manager (DTM), a component of Microsoft's Windows Logo Kit (WLK) device certification software; contains a testing report, which logs information about a hardware device; used for submitting test results to Microsoft so that a device may be certified for Windows; also used for debugging failed tests.

CPK files can be viewed with the DTM Log Viewer. The viewer shows information such as the test date, the test operating system, and passed and failed tests.

The WLK software is made available by the Windows Hardware Quality Labs (WHQL), a Microsoft group that certifies Windows hardware devices.

I don't think they're needed.

Read BEFORE you post.  HWID tool   DriverPacks Tutorial   DONATE!
http://driverpacks.net/userbar/admin-1.png
Not all heroes wear capes, some wear Kevlar!

Re: [REQ] Monitors - Like, how 'bout an update, eh?

WooHoo!!!   big_smile

.XML files would be needed for Vista-7 support only?

Last edited by TechDud (2011-08-08 20:21:26)

Re: [REQ] Monitors - Like, how 'bout an update, eh?

For .cat files, should i avoid all files that have OSAttr:6.0 or 6.1 as a minimum? (*.cat + *.icm + *.inf)
Or would it be best to simply leave out the *.cat file.

Re: [REQ] Monitors - Like, how 'bout an update, eh?

be cautious... removing certain files, and we don't always know which ones, will break signing.

Be sure to test signing after you delete files. if i remember correctly this can be done with "sigverif"

It's always better to maintain signing if possable.

DP BartPE Tutorial   DP_BASE Tutorial   HWID's Tool     Read BEFORE you post    UserBars!
http://driverpacks.net/userbar/admin-1.png
The DriverPacks, the DP_Base program, and Support Forum are FREE!.

Re: [REQ] Monitors - Like, how 'bout an update, eh?

For xp, the .xml & .cpk files are not used by 'Image Color Management', naturally they may be needed for NT6.x.  I've been simply double-clicking the .cat file & manually viewing the validity of the security catalog (verifying date), then checking the Catalog Entries for proper file-naming, the OSAttr value, as well as compare sha1 signatures (& the number of them) with generated crc values.

If i understand this right, NT5_x86 signatures can be validated in NT6_x86, I'm not sure if NT5_x64 signatures can be validated in NT6_x64. hmm
It is the NT6-only signatures that will not validate in NT5.

   Kinda wish it could all be automated, though. lol

Re: [REQ] Monitors - Like, how 'bout an update, eh?

very few of the .xml files have WCS profile from what i've seen so far.  According to MS, there is a way to export these profiles to a .ICC or .ICM profile.

Um, the sigverif tool has a log output similar to the Win98 version of SFC.exe insofar as the date values get truncated.  No dice; it is rejecting infs with sha1 values exactly as indicated in the cat files.  Much like the SFC tool, this may need some work which would be well above my abilities now.

Do you have any other options, i'm forced to do all the verification manually for 12000+ files.

I must be somewhere near the halfway point on this pack; maybe a 11.09 release is more likely.  http://forum.driverpacks.net/viewtopic. … 838#p44838 yikes

OK, it would seem that sigverif only verifies certification IF the 'Security Catalog' (.cat) is presently installed, except for individual files that carry their own certification within. (ie: .sys, .exe, .dll, .cat, .etc, ...)  Vista or 7 minimum .cat files are verified by this tool, as well, without noting OSAttr=2:6.0,2:6.1.  It really gets confusing with .cat's with OSAttr=2:5.0,2:6.0 as the results are the same as the previous case.

I forgot to mention that i am working in xp, if it helps.  Is it not true that a driver with a .cat file with OSAttr=2:5.0 should verify as WHQL in 5.1?

Last edited by TechDud (2011-08-14 12:48:53)

Re: [REQ] Monitors - Like, how 'bout an update, eh?

I don't know.

DP BartPE Tutorial   DP_BASE Tutorial   HWID's Tool     Read BEFORE you post    UserBars!
http://driverpacks.net/userbar/admin-1.png
The DriverPacks, the DP_Base program, and Support Forum are FREE!.

Re: [REQ] Monitors - Like, how 'bout an update, eh?

OK, maybe a better question would be, does the OSAttr variable have to exactly match the OS installed for WHQL signatures to be validated, and if so would that be OS-dependent (so long as architecture remains same)?

Theoretically, what could happen would i to take the cat files i want to test, & copy them to my %windir%\SYSTEM32\CATROOT\{F750E6C3-38EE-11D1-85E5-00C04FC295EE} folder?  Could it be a quick way to find invalid cat's?  I'm scared to try after 'dint palm driver incident.

Last edited by TechDud (2011-08-15 16:43:50)

Re: [REQ] Monitors - Like, how 'bout an update, eh?

having a little trouble understanding a line under [MonitorModel.AddReg]

I need to understand the syntax of HKR,,ICMProfile,0,"profile.icm".
What does "HKR,,ICMProfile,1,2" or "HKR,,ICMProfile,1,9" do?

I've been searching the net for a couple of hours now with few results, have i stumbled upon some state secrets here? hmm

Re: [REQ] Monitors - Like, how 'bout an update, eh?

May I give the  Vista-7 Monitors 3rd-Party packs a refresh, if you like the new pack? I am confidant that i'll make a significant contribution.  Included would be Vista (minimum) WHQL Catalog's, as well as ICC v4 color profiles (i'd like to say compliant, yet that depends on what the OEM included).  The xp color profiles (perhaps even the .Infs) are forward-compatible; if you're stuck with one of those cables, & a display's giving you issues, & the .Inf isn't in the Vista-7 pack...

It may seem useless since it does nothing for color in video (NTSC<->sRGB <-> PAL - ICC says their v5 profile will be done by latter 2012, maybe when win 8 releases, perhaps), yet works well for GDI+ enabled apps, in concert with image acquisition, & printing.

What these packs do (for XP, so far), is allow you to have a non-DDC compliant VGA cable hooked up & have the proper resolutions & refresh rates available (this can't be auto-detected, integration not practical), & a proper color profile (depending on OEM).  Many people complain that a VGA signal shows noise on the screen, yet there are small utilities included (from OEM) that set up a picture, on the max (or native) resolution, of an alternating black & white pixel; thereby generating usually a horribly noisy image (no idea what this will do on CRT, yet to try some).  Then you hit the AUTO button on the display & the image ends up clean.  That sets up 1080p, on a modern display.  With or without DDC, the INF may take precedence. big_smile

Last edited by TechDud (2011-08-19 05:03:08)

Re: [REQ] Monitors - Like, how 'bout an update, eh?

Go for it!  Nobody else is going to.

Read BEFORE you post.  HWID tool   DriverPacks Tutorial   DONATE!
http://driverpacks.net/userbar/admin-1.png
Not all heroes wear capes, some wear Kevlar!