1,326

(20 replies, posted in DriverPack WLAN)

newer RT2870 drivers (v3.2.3.0 Win-All) available from RaLink here --> Edit:link broken

PS:  have you updated any drivers for the older hardware (such as RT2400, RT2500 - USB or notUSB) from this topic, mr_smartepants?

On my next set of scans, i will see if i can somehow turn of heuristics; to see if it still nags me.  This should be known as a 'PUP' (key word being Potentially).  BitDefender offers 'no support whatsoever' with their liveCD, i won't try to contact them.  I will venture to contact AntiVirus companies whose products i actually use regularly.

I wonder if it would be possible to add the option for FindHWID's to output 'relative paths' instead? hmm

Sure, mr_smartepants, those will help, although i'll only use files from the packs to fill holes in the pack if an OEM isn't forthcoming (or defunct), & i have not previously downloaded.  Most files have been re-downloaded from the OEMs (about 64 OEM support sites, so far), my other major source is, of course, Windows Update Catalog.

Will WHQL-only packs make sense for nt5, nt6-x86, & nt6-x64?   ie:  DP_Display_ntX-xYY  = WHQL;   DP_Monitor_ntX-xYY = non-WHQL.

That will make it much easier when testing in 'beta' to spot ( & correct) WHQL Signing errors, etc., if any.  big_smile

1,329

(14 replies, posted in BartPE - UBCD4Win - WinPE)

You could try the updated driver from HP here --> http://h20000.www2.hp.com/bizsupport/Te … amp;mode=5
  or directly here --> ftp://ftp.hp.com/pub/softpaq/sp53501-54000/sp53631.exe  it seems to have your HWID.

1,330

(14 replies, posted in BartPE - UBCD4Win - WinPE)

Wouldn't that ID be included in Intel PROset 16.5 -- http://downloadcenter.intel.com/SearchR … amilyId=38 like OverFlow mentioned?

Thank you.  I found lots of downloads for these, yet just trying to maintain source-security. big_smile

I almost neglected to credit Us2002.  Rectified.

I think if i split the pack along the lines of WHQL (D/3/D/*) and non-WHQL (D/3/Mo/*) that should remove most of the CRT drivers from the WHQL pack, and resolve the age-old question of how to best segregate the LCD display drivers from the CRT equivalents.  The Vista-7 drivers could be mostly WHQL (\x86\3\Di\) & WHQL-only (\x64\3\Di\).

Does anybody have access to an old copy of the monitor packs DP_Monitor_wnt5_x86-32_908130.7z or older that they could share with me?
There are a great many LG drivers, etc. missing that i am no longer able to download from an OEM.
SamLab.ws or mindwarper should have a copy kicking around somewhere; please help.

The BitDefender 'Rescue CD' claims that both 'FindHWIDS.v3.2p.exe' & the unpacked 'FindHWIDS.v3.2p_unpacked.exe' have the virus "Gen.Trojan.Heur.AutoIT.1".
I don't know if the main program gives the same false-positive.

1,334

(6 replies, posted in DriverPack Chipset)

In a Security Catalog (*.cat) file this would correspond to the OSAttr variable contained along with a sha1 hash value.  For example: OSAttr      2:5.00,2:5.1,2:5.2,2:6.0,2:6.1
for the first digit:   1=Win9x, 2=WinNT
the remainder (colon excluded):   Win98=4.10, 98me=4.90, Win2K=5.00, WinXP=5.1, Win2K3=5.2, Vista=6.0, Win7=6.1, Win8=6.2(preliminary)

Architecture variability can be expressed within the Catalog Information, contained in a noncritical extension.  From the same .cat file as the OSAttr example:

30 68 1e 04 00 4f 00 53   0h...O.S
02 04 10 01 00 01 04 5a   .......Z
32 00 30 00 30 00 30 00   2.0.0.0.
2c 00 58 00 50 00 58 00   ,.X.P.X.
38 00 36 00 2c 00 58 00   8.6.,.X.
50 00 58 00 36 00 34 00   P.X.6.4.
2c 00 56 00 69 00 73 00   ,.V.i.s.
74 00 61 00 58 00 38 00   t.a.X.8.
36 00 2c 00 56 00 69 00   6.,.V.i.
73 00 74 00 61 00 58 00   s.t.a.X.
36 00 34 00 2c 00 37 00   6.4.,.7.
58 00 38 00 36 00 2c 00   X.8.6.,.
37 00 58 00 36 00 34 00   7.X.6.4.
00 00                     ..

A Vista Security Catalog may be accepted as valid on a 7 system within the same architecture, even if '2:6.1' is not explicit within the OSAttr variable, as long as it contains '2:6.0'.
This could help explain why many Vista drivers can be 'seen' as WHQL on Win7 systems of similar architecture.

I see that a previously mentioned Intel ME Management engine had no such noncritical extension embedded, and apparently was verified as WHQL.  Can anyone tell me how the noncritical extension can influence this behavior or point to some relevant info,  as i still don't fully understand all of the circumstances when & why a Vista .cat file can work with Win7.

I am truly sorry for the lack of respect, Deathbot70.

Such undeserving commentary may not violate the rules of this forum, 'per se', yet after re-reading them, i realize that it doesn't live up to the 'spirit' of the rules.  In fact it appears to be rather ignorant, and as such adds nothing to an air of 'positive discussion', nor does it demonstrate 'mutual respect'.  I was embarrassed by what i read.  I would much rather remember that i will learn nothing by whatever it is that i post, only through what i read from other registered member's posts.  I will return to a 'less is sometimes more' philosophy.

Thank you for retaining a good sense of humour.  I don't want to be called  DeafDud, or TechButt either, although i have earned such titles.

Forgive me for posting this in a [SLVD] topic, i came within a 'whisker's breadth' of doing something terribly egregious and i needed to recompense of my own volition.

Any chance new cat signatures may be used in NT6.2?  NIST advises hashing algorithms  based on SHA-256 or higher.  I do so hope the crypto-strength gets improved as i see 'Clouds-on-the-cheap' nearer than the horizon, so to speak.

TechDud wrote:

If only you could simply add some commented-out characters to the .Inf file to enable the file to generate the same sha1 CRC value of 'f8c713d374e9620476d5392729c4d79b412199c2' so that it does pass WHQL.  Of course, if that method worked, that would be disquieting, to say the least.

I found an interesting article pertaining to "Collision resistance" here --> http://unixwiz.net/techtips/iguide-crypto-hashes.html big_smile
Amazing how MD4 can be cracked by hand, MD5 has fallen as well, as referenced in the article.    I suppose the odds would be that there could be large numbers of collisions possible now with sha-1.
With a fixed length of bytes, it corresponds to 2^160 or 1461501637330902918203684832716300000000000000000(±99999999999999999) different combinations.

Just in case you are still having trouble:
Do you have the latest BIOS?  Are there any firmware updates for your drive?  Remember the previous two suggestions can 'brick' your hardware if you don't know what you're doing.
Does your memory pass a MemTest86?
You could re-zero the drive with the HDD manufacturer's tools.  Then run the 'Advanced' Test to verify the HDD surface.
  I know this can take a couple hours for budget drives, yet this ensures trouble-free operation & can weed-out drives that have suffered high-g's or other damage.

One might refer to these two MS support sites: http://support.microsoft.com/kb/324103 & http://support.microsoft.com/kb/316401

Deafbot70 wrote:

The computer has no Modem that I am aware of

Unless you count that TCP/IP stack built into the BIOS.  ie:  reminiscently like 'Intel Management Engine - SOL' = Serial Over LAN = PCI Communications device = Big Gaping Security Hole that survives an OS re-install?

TechDud wrote:

You probably need to extract the installshield file from intel, as posted by mr_smartepants with 7-zip.  Try to manually update

Deathbutt70 wrote:

Bingo, the Extracting of the drivers manually let me get the one I needed it was the HECIx64.sys

mr_smartepants wrote:

Wow, it worked?  Hmmm.

Forgive me, yet i'm not convinced that he used your hacked .Inf, unfortunately for all of us.

TechDud wrote:

He got what he wanted, whether it was a wise move, or not, and has thus far contributed nothing to the discussion.
For instance:  did mr_smartepants hack work?  Did the Vista WHQL signature validate properly in Win 7 with the manual install of the extracted files?

Can anyone speak to the potential security risk this type of 'Management Engine' could represent.  Better yet, can anyone comment on how to plug such a hole, without killing off other resources, such as changing the default password?

Older KVM's can cause I2C communication to be disrupted too, like a cable with no support for EDID.
If you have a cable with pins 9, 12, & 15, you should be able to read the EDID over I2C with the power cord removed from the display.

EDID communication (or programming) errors can cause other affects, like the infamous Playstation3 HDMI 'black screen' issue.  The solution for displays exhibiting that behavior was to enter 'Service Mode' with a 'Service Remote' (if necessary) which 'Write-Enabled' the EEPROM, and then re-program the EDID chip over I2C.  This reprogramming method also works for monitors, less the service remote (Google 'Service Mode').

Anyone brave enough to try AOC's iMenu? http://forum.driverpacks.net/viewtopic. … 112#p45112 hmm

PS:  it might be best to disable this as it may pose a security risk.  There may be negative consequences to disabling this.  http://communities.intel.com/community/ … -windows-7

"The managability engine is used to reduce the cost of maintainance of corporate computer systems.  It is part of the network hardware and allows remote maintenance activities when the OS is damaged or the system is off\sleeping.

Is that not magical?
on levovo systems, ctrl-P allows access to configuration options, before BIOS post screen?

He got what he wanted, whether it was a wise move, or not, and has thus far contributed nothing to the discussion.
For instance:  did mr_smartepants hack work?  Did the Vista WHQL signature validate properly in Win 7 with the manual install of the extracted files?

Help us out in return for helping you out, Deafbutt sad

PS:  I had searched Windows Update Catalog to no avail, & i see that same reference to 'EventLogMessageDllPath_winxpe' in 'MEI_allOS_7.1.14.1107_PV.exe'

;*******************************************************************************
;*                                                                            **
;*                     I N T E L   P R O P R I E T A R Y                      **
;*                                                                            **
;*   COPYRIGHT (c) 2003-2010 BY INTEL CORPORATION. ALL RIGHTS RESERVED.  NO   **
;*   PART  OF  THIS  PROGRAM OR PUBLICATION MAY BE REPRODUCED, TRANSMITTED,   **
;*   TRANSCRIBED, STORED IN A RETRIEVAL  SYSTEM,  OR  TRANSLATED  INTO  ANY   **
;*   LANGUAGE OR COMPUTER LANGUAGE IN ANY FORM OR BY ANY MEANS, ELECTRONIC,   **
;*   MECHANICAL, MAGNETIC, OPTICAL, CHEMICAL, MANUAL, OR OTHERWISE, WITHOUT   **
;*   THE PRIOR WRITTEN PERMISSION OF :                                        **
;*                                                                            **
;*                             INTEL CORPORATION                              **
;*                                                                            **
;*                          2200 MISSION COLLEGE BLVD                         **
;*                                                                            **
;*                     SANTA CLARA, CALIFORNIA 95052-8119                     **
;*                                                                            **
;*******************************************************************************
;
;
; File Name: HECI.inf
; Install information file for HECI Driver
;
; Generated by C DriverWizard 3.1.0 (Build 1722)
; Requires DDK Only
; File created on 6/20/2005
;

;--------- Version Section ---------------------------------------------------

[Version]
Signature="$WINDOWS NT$"
Class=System
ClassGUID={4d36e97d-e325-11ce-bfc1-08002be10318}
Provider=%Provider%
DriverVer=10/19/2010,7.0.0.1144
CatalogFile=HECI.cat

[ControlFlags]
; Pnp drivers should not be installable via non-PnP hardware dialogs
ExcludeFromSelect = *

;--------- DestinationDirs Section -------------------------------------------

[DestinationDirs]
DefaultDestDir = 10
HECI_Files_Driver = 12
HECIx64_Files_Driver = 12

;--------- SourceDiskNames and SourceDiskFiles Section -----------------------
; These sections identify source disks and files for installation.

[SourceDisksNames]
1 = %Location%,,,""

[SourceDisksFiles]
HECI.sys  = 1,,
HECIx64.sys  = 1,,


;--------- Manufacturer and Models Sections ----------------------------------

[Manufacturer]
%MfgName% = Intel, NTx86.6.0, NTx86.5.2, NTx86.5.1, NTamd64

[Intel.NTx86.6.0]
; DisplayName               Section           DeviceId
%HECI_DeviceDesc%=HECI_DDI, PCI\VEN_8086&DEV_1C3A

[Intel.NTx86.5.2]
; DisplayName               Section           DeviceId
%HECI_DeviceDesc%=HECI_DDI, PCI\VEN_8086&DEV_1C3A

[Intel.NTx86.5.1]
; DisplayName               Section           DeviceId
%HECI_DeviceDesc%=HECI_DDI, PCI\VEN_8086&DEV_1C3A

[Intel.NTamd64]
; DisplayName               Section           DeviceId
%HECI_DeviceDesc%=HECI_DDI_x64, PCI\VEN_8086&DEV_1C3A


[Intel]
; Empty section, so this INF does not support Windows 2000.

;---------- DDInstall Sections -----------------------------------------------
; --------- Windows NT -----------------

[HECI_DDI]
CopyFiles=HECI_Files_Driver
AddReg=HECI_NT_AddReg

[HECI_DDI.Services]
AddService = MEI, %FLG_ADDREG_NOCLOBBER%, HECI_Service, winxp.EventLog

;---------- DDInstall Section Windows x64 ----------

[HECI_DDI_x64]
CopyFiles=HECIx64_Files_Driver
AddReg=HECI_NT_AddReg

[HECI_DDI_x64.Services]
AddService = MEIx64, %FLG_ADDREG_NOCLOBBER%, HECIx64_Service, winxpe.EventLog


; --------- Registry ----------------------

[HECI_NT_AddReg]
;reg-root,[subkey],[value-entry-name],[flags],[value]
HKR,,WdTimerTic,%REG_DWORD%,120

[HECI_NT_AddReg.Security]
"D:P(A;CI;GA;;;BA)(A;CI;GA;;;SY)"

[HECI_DDI.HW]
AddReg=HECI__NT_HW_AddReg

[HECI_DDI_x64.HW]
AddReg=HECI__NT_HW_AddReg

[HECI__NT_HW_AddReg]
HKR,,DeviceCharacteristics,0x10001,0x100
HKR,,Security,,"D:P(A;;GA;;;BA)(A;;GA;;;SY)"

[HECI__NT_HW_AddReg.Security]
"D:P(A;CI;GA;;;BA)(A;CI;GA;;;SY)"

; --------- Service ----------------------

[HECI_Service]
DisplayName    = %HECI_SvcDesc%
ServiceType    = %SERVICE_KERNEL_DRIVER%
StartType      = %SERVICE_DEMAND_START%
ErrorControl   = %SERVICE_ERROR_NORMAL%
ServiceBinary  = %12%\HECI.sys
LoadOrderGroup = Extended Base

[HECIx64_Service]
DisplayName    = %HECI_SvcDesc%
ServiceType    = %SERVICE_KERNEL_DRIVER%
StartType      = %SERVICE_DEMAND_START%
ErrorControl   = %SERVICE_ERROR_NORMAL%
ServiceBinary  = %12%\HECIx64.sys
LoadOrderGroup = Extended Base

;-----------------------------------------------------------------------------
; Common base for all drivers for Eventlog and TextModeFlags
;
[winxp.EventLog]
AddReg = winxp.AddEventLog.reg

[winxp.AddEventLog.reg]
HKR, , EventMessageFile, 0x00020000, %EventLogMessageDllPath_winxp%
HKR, , TypesSupported,   0x00010001, 7

[winxpe.EventLog]
AddReg = winxpe.AddEventLog.reg

[winxpe.AddEventLog.reg]
HKR, , EventMessageFile, 0x00020000, %EventLogMessageDllPath_winxpe%
HKR, , TypesSupported,   0x00010001, 7

; --------- Files ----------------------

[HECI_Files_Driver]
HECI.sys,,,2

[HECIx64_Files_Driver]
HECIx64.sys,,,2
;--------- Strings Section ---------------------------------------------------

[Strings]
;---------------------------------------------------------------------------------------------------
EventLogMessageDllPath_winxp   = "%SystemRoot%\System32\netevent.dll;%SystemRoot%\System32\drivers\HECI.sys"
EventLogMessageDllPath_winxpe  = "%SystemRoot%\System32\netevent.dll;%SystemRoot%\System32\drivers\HECIx64.sys"

Provider = "Intel"
MfgName = "Intel"
HECI_DeviceDesc = "Intel(R) Management Engine Interface"
HECI_SvcDesc = "Intel(R) Management Engine Interface"
Location = "Intel(R) Management Engine Interface"

REG_SZ                      = 0x00000000
REG_MULTI_SZ                = 0x00010000
REG_EXPAND_SZ               = 0x00020000
REG_BINARY                  = 0x00000001
REG_DWORD                   = 0x00010001
REG_NONE                    = 0x00020001

SERVICE_KERNEL_DRIVER       = 0x00000001
SERVICE_FILE_SYSTEM_DRIVER  = 0x00000002
SERVICE_ADAPTER             = 0x00000004
SERVICE_RECOGNIZER_DRIVER   = 0x00000008

SERVICE_BOOT_START          = 0x0
SERVICE_SYSTEM_START        = 0x1
SERVICE_AUTO_START          = 0x2
SERVICE_DEMAND_START        = 0x3
SERVICE_DISABLED            = 0x4

SERVICE_ERROR_IGNORE        = 0x00000000
SERVICE_ERROR_NORMAL        = 0x00000001
SERVICE_ERROR_SEVERE        = 0x00000002
SERVICE_ERROR_CRITICAL      = 0x00000003

FLG_ADDREG_NOCLOBBER        = 0x00000002
FLG_ADDREG_DELVAL           = 0x00000004
FLG_ADDREG_APPEND           = 0x00000008
FLG_ADDREG_KEYONLY          = 0x00000010
FLG_ADDREG_OVERWRITEONLY    = 0x00000020
FLG_ADDREG_64BITKEY         = 0x00001000
FLG_ADDREG_KEYONLY_COMMON   = 0x00002000
FLG_ADDREG_32BITKEY         = 0x00004000

SPSVCINST_STOPSERVICE			= 0x00000200
SPSVCINST_DELETEEVENTLOGENTRY	= 0x00000004

This looks like a job for a specialized algorithm based on sha-1.  Accelerating the process with a zippy GPU would reduce the compute time tremendously.
I haven't tried to do this kind of programming since i created a lossless compression algorithm in 1984.

Alternatively, one could include the certificate from intel.  http://www.osronline.com/showthread.cfm?link=186756

Edit: scratch the certificate brain-fart, we discussed something similar, earlier.

I see from LCD panel datasheets that the average frequency used on a backlight inverter is 65kHz.

Here's another tidbit:  lower your brightness, extend component life (incl battery on a portable)

The main function of this pack will be to facilitate the proper resolution modes & refresh rates when using a VGA cable that is missing the DDC (EDID) communication lines. (pin 9 - +5/3.3V, pins 12 & 15 - I2C bus)  The included color profiles are only useful for pictures (using GDI+ i think).

Avoid using CNET or Download.com; they are now a distributor of toolbars & malware.  See full details here --> http://www.neowin.net/news/downloadcom- … -bloatware

NO MORE VICTIMS, VICTOR! mad

Creative Labs is continuing to leave posts on their forum which clearly plagiarize daniel_k's work.  Such a shameless insult to the literal blood, sweat & tears suffered by Daniel Kawakami.  To you, pal, I am truly sorry it took this long for me to delete the offensive files (5 days after reading his post), yet i have complied without waiting for a request.  Thankfully i never shared as i was suspicious from day one.  I should have recognized the offending 'Trusted Contributor', as this is not the first time that he has plagiarized daniel_k's work.  http://forums.creative.com/t5/Sound-Bla … m-p/556929  Stealing somebody's work, and passing it off as your own is simply wrong on so many levels.  For another user to suggest that it is for the 'community good' is totally misguided.  Of course no one is shocked that unCreative doesn't mind.  Look to avoid ZiiLabs products, too (and probably their drivers if applicable).  Link here, to see daniel_k's reaction scroll down the page http://forums.creative.com/t5/Sound-Bla … d-p/579939

Look for all the Vista, 7 'lack of driver' BS to repeat itself once 'Windows 8' is released. sad

Creative Labs:  EPIC FAIL!


PS: Happy 10th 'Birth'RTMday, Windows XP! http://www.neowin.net/news/today-marks- … ows-xp-rtm big_smile

PPS:  Happy 20th 'Birth'day, Linux! http://video.linux.com/video/2127 cool

Windows 8 will offer native USB 3.0 support.  Referenced here --> http://www.neowin.net/news/microsoft-co … -windows-8

A good guess may be that a native stack will be included, as it was with USB 2.0 & windows XP.

Driverpacks.net has USB 3.0 drivers already included for Win 2k, XP, 2k3, Vista, 2k8, 2k8R2 & 7, BTW.

Incandescent or LED lighting should eliminate that effect (or is it an affect?).

Is anyone out there brave enough to try AOC's iMenu on their DDC/CI compliant LCD monitor to verify function with another brand?  USE AT YOUR OWN RISK http://www.aocmonitorap.com/drivers/i-M … up.exe.zip

It's so nice to be able to adjust my contrast & brightness on-the-fly with my mouse! big_smile

forgive me, i lack understanding of why a hack would be necessary.  The .cat file included with the official intel driver contains signatures for Windows 2k, xp, 2k3, & vista including 64-bit.  I am told that the vista whql signatures are upwardly compatible.  Is this incorrect, or is there another issue that makes that aforementioned driver incompatible with Windows 7?

So, it's the lack of the [Intel.NTamd64.6.1] identifier that's causing this BS?
Maybe it would be worthwhile to add [Intel.NTamd64.6.2] for future Win 8 support.

If only you could simply add some commented-out characters to the .Inf file to enable the file to generate the same sha1 CRC value of 'f8c713d374e9620476d5392729c4d79b412199c2' so that it does pass WHQL.  Of course, if that method worked, that would be disquieting, to say the least.

PS:  it might be best to disable this as it may pose a security risk.  There may be negative consequences to disabling this.  http://communities.intel.com/community/ … -windows-7

"The managability engine is used to reduce the cost of maintainance of corporate computer systems.  It is part of the network hardware and allows remote maintenance activities when the OS is damaged or the system is off\sleeping.

Is that not magical?
on levovo systems, ctrl-P allows access to configuration options, before BIOS post screen?

I'm sorry, i'm not trying to 'toy' with you, i've 'seen' it as a 'Intel(R) Management Engine Interface', now i see the file name starts with HECI.

I see that it does exist in 'DP_Chipset_wnt5_x86-32_1108.7z\D\C\I1\' & the 'hecix64.sys' is missing.  That driver does have WHQL for xp & Vista.  Perhaps it was removed from the Vista-7 pack.  I wish i had some way of searching archives & contents for strings - like WinRar USED to be able to do reliably (maybe it's bad syntax on my part, there's nothing in the help file, though)

You probably need to extract the installshield file from intel, as posted by mr_smartepants with 7-zip.  Try to manually update, & if it works, request this driver be added to the Vista-7 pack (after searching the forum for reasons this driver may have been removed).  Please indicate whether 7 says that is WHQL'ed, if successful.  Thanx.

Ah, good to get confirmation, i can safely delete the 59Hz drivers from LG.
... standard VGA would be necessary, since communication over DDC via I2C is likely unavailable.  I will test I2C communication just to make certain of my 'facts', to minimize risk to the end-users. (not much i can do for 'stupid', though! lol I'm my own worst victim sometimes - 'kit gloves' with other peoples goods)

I see that many modern LCD's with low response-times support refresh rates up to around 75Hz.  I like the higher refresh rates, since bandwidth increases (if i remember right).  Aren't LED monitors less susceptible?
Do you see 'heterodyning' over DVI/HDMI, or just VGA?  Are you talking about interference on an LCD over VGA, especially with a moire-pattern?

Dr. Bill Wattenburg (https://secure.wikimedia.org/wikipedia/ … Wattenburg) says that many MegaWatts per year could be saved, if the hydro utilities simply delivered electricity at 115Vac, instead of the 121Vac normally used.  (He also says that if the federal governments mandated all new 'federal' vehicles for government tender to be dual-fuel natural gas, our economies would improve faster, as North America has more proven natural gas reserves than Saudi Arabia has oil)  His radio show is a must-listen event for me, personally.

Eizo Test has been helpful to me http://www.eizo.de/pool/files/de/Eizo_Monitortest.zip, as has 'LCD adj' http://www.eizo.com/data/downloads/soft … DJ110C.zip, and 'ScreenAdj' http://www.eizo.com/data/downloads/soft … /SA100.zip.  AOC's iMenu http://www.aocmonitorap.com/drivers/i-M … up.exe.zip has allowed DDC/CI access to my Samsung LCD for simple on-the-fly adjustments.  I will see if it will support another manufacturer's 'Auto-Rotate' feature, soon.  I here through the grape vine that there is a later version of iMenu somewhere, possibly version 3.9.0.0, yet it so far eludes me.  Use any of these 'utes' at your own risk, i have not been able to extensively test them.

It would seem that my previous estimate of 'half-way' may have been overly optimistic.  I think i would prefer to release (as a RC) a well-researched, well-rounded, set of packs for xp & vista-7, rather than an endless line of 'updates'.  Hopefully this would minimize the risks to 'the adventurous'.  Here's the current changelog --> http://forum.driverpacks.net/profile.php?id=14671 big_smile

The reason i ask is because i've seen a lot of LG drivers with 59Hz set as an overriding main refresh rate.  This has me concerned since this isn't an obvious multiple of 25/50Hz as used for PAL/hydro.
If it can be confirmed that 59Hz refresh is an error, i'd seriously like to delete them since i have newer inf's.

i've downloaded lcd drivers from europe, yet i haven't seen any with 50Hz as the specific refresh rate.  A quick search reveals no drivers with 50Hz as a refresh rate for common resolutions.  I've been wondering, lately, how the OEM's solved compatibility between the various world standards.

I need to ensure that obvious refresh rate errors can be minimized, i have never tried 'tweaking' the refresh on an lcd, i'm assuming a black screen would result (unsupported).  My hope is that it wouldn't cause permanent damage.  It would be good for this pack to be a community-service rather than 'electronic-roulette'!

Monitor drivers don't load in 'Safe Mode', do they?

I appreciate all comments. cool