1,376 Reply by TechDud

(353 replies, posted in Software)

UniExtract Kicks Ass!  http://legroom.net/software/uniextract  One handy feature is the 'Append missing file extensions' checkbox.  I love freeware! cool

I made sure it wasn't a heuristic-based detection, & I had the Threat Category 'Unusual run-time compression' deselected.   I've been hearing that most AntiVirus programs are notorious for not removing known false-detections.  I knew Mr_Smartepants wasn't trying a 'social-engineering' trick on me; he knows i do well enough at killing my own hardware! big_smile  http://forum.driverpacks.net/viewtopic.php?id=5291  As it turned out, i did have a blown capacitorin my power supply, just to add to the digital mayhem! (so much for the theory that computers cannot start with blown capacitors)

The latest Excel Viewer doesn't seem to like CSV files anymore; LibreOffice seems to work though.  If only FindHWIDS could build a CSV list of files/path referenced in the 'CatalogFile=' & '[  .CopyFiles]' sections.  The CreativeLabs Live to XiFi drivers should be an interesting test for such a feature; they are Mr_Smartepants' favorite! lol

Go to forum: Software

1,377 Reply by TechDud

(353 replies, posted in Software)

Avira is freaking out on me (spazz).  It claims to have found the 'SPR/AutoIt.Gen' special detection.  details here http://www.avira.com/en/support-threats … 5/tlang/en sad
FindHWIDS v3.2p has been detected as 'Programs that violate the private domain' "This is a program that may be capable of compromising the security of your system, triggering malware activities or invading your privacy".

I've resolved this by unpacking the file.  No detection now.

Perhaps a change could be made to the program to prevent this signature-based detection?  I wonder if this is the only AntiVirus that falsely detects this as a virus.

Go to forum: Software

1,378 Reply by TechDud

(60 replies, posted in 3rd Party DriverPacks)

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

Go to forum: 3rd Party DriverPacks

1,379 Reply by TechDud

(60 replies, posted in 3rd Party DriverPacks)

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.

Go to forum: 3rd Party DriverPacks

1,380 Reply by TechDud

(60 replies, posted in 3rd Party DriverPacks)

WooHoo!!!   big_smile

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

Go to forum: 3rd Party DriverPacks

1,381 Reply by TechDud

(60 replies, posted in 3rd Party DriverPacks)

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.

Go to forum: 3rd Party DriverPacks

1,382 Reply by TechDud

(60 replies, posted in 3rd Party DriverPacks)

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.

Go to forum: 3rd Party DriverPacks

1,383 Reply by TechDud

(60 replies, posted in 3rd Party DriverPacks)

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.

Go to forum: 3rd Party DriverPacks

1,384 Reply by TechDud

(60 replies, posted in 3rd Party DriverPacks)

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.

Go to forum: 3rd Party DriverPacks

1,385 Reply by TechDud

(60 replies, posted in 3rd Party DriverPacks)

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?

Go to forum: 3rd Party DriverPacks

1,386 Reply by TechDud

(60 replies, posted in 3rd Party DriverPacks)

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

Go to forum: 3rd Party DriverPacks

1,387 Topic by TechDud

(60 replies, posted in 3rd Party DriverPacks)

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

Go to forum: 3rd Party DriverPacks

1,388 Reply by TechDud

(8 replies, posted in 3rd Party DriverPacks)

techie1 wrote:

D\3\MON\IBM\l197wide.inf references "L197 Wide.cat" and "L197 Wide.ICM" but the actual files included with the pack are called "l197wide.cat" and "l197wide.icm"

Seems like this should be corrected by either renaming the files or by changing the names in the .inf file.

I believe an appropriate fix would be to simply change the name of the files, although it is unclear as to what to do with the l197wide.cat file. hmm http://support.lenovo.com/en_US/downloa … MIGR-69709

Perhaps you could tell me which method preserves WHQL-signing, techie1  I wish there was a good utility for this. roll

Go to forum: 3rd Party DriverPacks

1,389 Reply by TechDud

(11 replies, posted in Vista / 7 DriverPack Chipset)

Uncorked for 32bit here --> link removed .. updated below cool cool
& for 64bit here --> link removed .. updated below

Go to forum: Vista / 7 DriverPack Chipset

1,390 Reply by TechDud

(17 replies, posted in DriverPack Graphics)

Graphics processing is about to be included in the 'CPU', now known as an APU.  nV is having trouble with some of the latest cards & performance issues at higher resolutions.  I have no word on whether that issue has been resolved or not.  I'm not a nV-hater, dammit, i wish they'd start giving AMD a real run for their money.  A lack of competition helps no one (well, intel rules the roost in proliferation terms).  coke, pepsi, dodge, ford, potato, what's the difference, spud?

It's only an 'incredible' value if it will still work in 3 years, I'd want a 5-year warranty minimum.  It sucks bullocks that North America doesn't force manufacturers to stand behind their products like in the EU (as i'm told).

Go to forum: DriverPack Graphics

1,391 Reply by TechDud

(5 replies, posted in Vista / 7 DriverPack Chipset)

no hokey Dll-programmed support to screw up your 64bit packs, i hope.
http://www.prolific.com.tw/eng/images/sdd_01.gifhttp://www.prolific.com.tw/eng/images/sdd_02.gifTM

Best known for 'Easy-Transfer' cables http://www.prolific.com.tw/eng/Products.asp?ID=72 ; drivers for which, may be missing.  http://www.prolific.com.tw/eng/downloads.asp?ID=93
http://www.prolific.com.tw/support/file … c_3103.zip  no driver included, just a v6.0.6000.16386 of winusb.dll, linklibwu.dll - PL25A1 Functions Dynamic Link Library (Unicode), linklibwa.dll & the prog, itself (x86/x64).
Easy-Transfer for WinXP: http://www.microsoft.com/downloads/deta … layLang=en

Go to forum: Vista / 7 DriverPack Chipset

1,392 Reply by TechDud

(85 replies, posted in Vista / 7 DriverPack Chipset)

That exemplifies the level of professionalism built into the main packs.  This is the level of 'source-security' employed to ensure malware doesn't creep into the packs.  A prudent step, i would assume, considering the level of threat kernel-mode drivers can represent.  WHQL signing assures (someone want to check on THIS one, please) that no 3rd-party could just 'hack' the .sys file; for example.

Go to forum: Vista / 7 DriverPack Chipset

1,393 Reply by TechDud

(8 replies, posted in 3rd Party DriverPacks)

Ra wrote:

ThinkPad Monitor file Updated to 4.36 for new models

\LEN

http://support.lenovo.com/en_US/downloa … MIGR-62923

soon.

Go to forum: 3rd Party DriverPacks

1,394 Reply by TechDud

(85 replies, posted in Vista / 7 DriverPack Chipset)

The FTDI drivers include both, I believe.  One set for Vcom Ports, the other for programmed dll access.  The two download pages link the same 2.08.14 version.
Latest readme.rtf:  http://www.ftdichip.com/Drivers/CDM/CDM … 20Info.rtf
Here's a D2XX programming guide if it helps. http://www.ftdichip.com/Support/Documen … 00071).pdf

the d2xx dll's are included in the ftdibus.inf driver.

[FtdiBus.NTamd64.Copy]
ftdibus.sys

[FtdiBus.NTamd64.Copy2]
ftbusui.dll
ftd2xx.dll,ftd2xx64.dll
FTLang.dll

[FtdiBus.NTamd64.Copy3]
ftd2xx.dll

[Strings]
Ftdi="FTDI"
DESC="CDM Driver Package - Bus/D2XX Driver"

& from the Logo Verification Report:

Submission ID: 1448749
Submission Date: 4/12/2011
Logo Completion Date: 4/12/2011
Company: Future Technology Devices International Ltd
Product Name: FTDIChip CDM Driver Package
Category: Device
Subcategory: Unclassified
Qualification Level: Signature Only - Microsoft Windows 2000 family - Unclassified
Signature Only - Microsoft Windows XP family, x86 - Unclassified
Signature Only - Microsoft Windows Server 2003 family, x86 - Unclassified
Signature Only - Microsoft Windows Server 2003 family, x64 - Unclassified
Signature Only - Microsoft Windows XP family, x64 - Unclassified
Signature Only - Microsoft Windows Vista family, x86 - Unclassified
Signature Only - Microsoft Windows Vista family, x64 - Unclassified
Signature Only - Windows Server 2008 family, x86
Signature Only - Windows Server 2008 family, x64
Signature Only – Device - Compatible with Windows 7
Signature Only - Device - Compatible with Windows 7 x64
Signature Only - Windows Server 2008 Release 2 family, x64
Marketing Names: N/A
Additional Information:
Firmware version: 2.08.14

If this programmable-access driver represents a security risk, perhaps ftdibus.inf & referenced files should be removed.  I like FTDI chipsets, so far; straight-outta-Glasgow. big_smile

Here you may find some utilities including COMport assignment, a custom-INF maker (never tried it).  There's a Vista-Gadget for it, too.  http://www.ftdichip.com/Support/Utilities.htm
The 'Longhorn' version of USBview is on that page, too.

Go to forum: Vista / 7 DriverPack Chipset

1,395 Reply by TechDud

(18 replies, posted in 3rd Party DriverPacks)

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?

Go to forum: 3rd Party DriverPacks

1,396 Reply by TechDud

(18 replies, posted in 3rd Party DriverPacks)

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.

Monitor Third Party DriverPack conversation continued in this thread: http://forum.driverpacks.net/viewtopic.php?id=5436

Go to forum: 3rd Party DriverPacks

1,397 Topic by TechDud

(0 replies, posted in 3rd Party Vista / 7 DriverPacks)

update DriverVer=08/22/2007,5.12.20.0167 win-all_x86_x64 here --> http://catalog.update.microsoft.com/v7/ … 64e6408a91 cool cool

Go to forum: 3rd Party Vista / 7 DriverPacks

1,398 Topic by TechDud

(0 replies, posted in 3rd Party Vista / 7 DriverPacks)

check out these drivers for real win7 drivers, updates, missing drivers --> http://forum.driverpacks.net/viewtopic. … 730#p44730 cool

Go to forum: 3rd Party Vista / 7 DriverPacks

1,399 Reply by TechDud

(11 replies, posted in 3rd Party DriverPacks)

that's xp_DriverVer=01/03/2011,1.2.1.7011 for your HWID.  This also contains good updates & missing drivers for the Vista-7_CardReader pack, & should be requested for such.

Go to forum: 3rd Party DriverPacks

1,400 Reply by TechDud

(18 replies, posted in 3rd Party DriverPacks)

Would a DP_CardReaders_nt5 be a good candidate for a first project?  I'd like to mimic the 3rd-party titles with the Vista-7 packs.
I would be new to making a driver pack, and am eager to work towards learning how.  Don't expect overnight results, naturally.  I would have big shoes to attempt to fill, of course; it may take a while to grow into them.

I suppose you'll focus primarily on Vista-7 & perhaps 8, depending on what ARM you use. lol

I'm waiting for Windows 9-SP1 (8 with the bugs removed). Windows 1.01 got it going, Win3.1 was a hit, Win_NT5 is ten plus years later still vaguely relevant, Win7 is saving MS's assesses; yup, i'm waiting for Win9.

Concerning any xp driver packs that i may attempt to build (publicly available, for free - other than ISP charges, no one shall charge for the driverpack, ever), would it be best that Win2k, 2k3, & XP_64 drivers be included where possible? hmm

Go to forum: 3rd Party DriverPacks