DriverPacks.net Forum - [SLVD] PCI Simple Communications Controller Drivers for Windows 7 x64

Re: [SLVD] PCI Simple Communications Controller Drivers for Windows 7 x64

null@example.com (Deathbot70) — Thu, 01 Sep 2011 13:35:40 +0000

TechDud wrote:

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.

Nothing to forgive TechDud, I am sure it was all in fun and nothing personal was ment by it.

And yes mr_smartepants, the issue was resolved and many thanks to you and TechDud for your help.

Deafbutt70

Re: [SLVD] PCI Simple Communications Controller Drivers for Windows 7 x64

null@example.com (OverFlow) — Mon, 29 Aug 2011 02:43:37 +0000

I am going to ban you for 10 minutes deafdud... remember to be nice

Re: [SLVD] PCI Simple Communications Controller Drivers for Windows 7 x64

null@example.com (TechDud) — Mon, 29 Aug 2011 01:24:56 +0000

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.

Re: [SLVD] PCI Simple Communications Controller Drivers for Windows 7 x64

null@example.com (mr_smartepants) — Sat, 27 Aug 2011 16:20:25 +0000

Cool, thanks for the confirmation that the driver works.
What you just described is contained in DP_Chipset_wnt6-x64_1108\x64\C\Intel\MEI\2\
Marking as "solved".

Re: [SLVD] PCI Simple Communications Controller Drivers for Windows 7 x64

null@example.com (Deathbot70) — Sat, 27 Aug 2011 14:19:30 +0000

Okay, I'm not sure what is going on here anymore. The discussion is a tad bit out of my relatively small range as far your driver speak is going. All I know is that I downloaded the Driver Link that Mr_Smartiepants had posted in message 6.( http://downloadcenter.intel.com/Detail_ … pe=Drivers ) I used RAR to extracted it all from the .EXE. Went into the Device Manager and told it to look for the driver in the folder. It found it and updated the driver. It gave me no thank you or anything, just took the driver and went on it's merry way. So far I have recived no conflicts of any kind.

That is as far as I have gone with it. As far as massive holes in my security or what not. Whelp, I have yet to have Morpheous blank out my screen and tell me to follow the white rabbit.

But, as I said, if there is any information you need, just ask and I will answer it the best I can.

DEATHbot
Not Deafbutt
or Deafbot
or Deathbutt

Thanks TechDud

Re: [SLVD] PCI Simple Communications Controller Drivers for Windows 7 x64

null@example.com (OverFlow) — Sat, 27 Aug 2011 02:32:45 +0000

My 486 could hash that in ten minutes

Re: [SLVD] PCI Simple Communications Controller Drivers for Windows 7 x64

null@example.com (TechDud) — Fri, 26 Aug 2011 11:49:57 +0000

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
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.

Re: [SLVD] PCI Simple Communications Controller Drivers for Windows 7 x64

null@example.com (TechDud) — Thu, 25 Aug 2011 17:58:14 +0000

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?

Re: [SLVD] PCI Simple Communications Controller Drivers for Windows 7 x64

null@example.com (mr_smartepants) — Thu, 25 Aug 2011 17:41:58 +0000

Deathbot70 wrote:

Bingo, the Extracting of the drivers manually let me get the one I needed it was the HECIx64.sys, which is I belive what you had stated. Everything is up and running now. Thank you very much for your time and expertise!
Deathbot

Wow, it worked? Hmmm. That doesn't sound good for Intel if little ol' me can write a better .inf than their engineers.
I guess now I'll get requests to fix the rest of them too. Yay, more work for me.

Re: [SLVD] PCI Simple Communications Controller Drivers for Windows 7 x64

null@example.com (TechDud) — Thu, 25 Aug 2011 17:12:56 +0000

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

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

Re: [SLVD] PCI Simple Communications Controller Drivers for Windows 7 x64

null@example.com (Deathbot70) — Thu, 25 Aug 2011 15:26:35 +0000

Bingo, the Extracting of the drivers manually let me get the one I needed it was the HECIx64.sys, which is I belive what you had stated. Everything is up and running now. Thank you very much for your time and expertise!

Deathbot

Re: [SLVD] PCI Simple Communications Controller Drivers for Windows 7 x64

null@example.com (TechDud) — Thu, 25 Aug 2011 12:56:29 +0000

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.

Re: [SLVD] PCI Simple Communications Controller Drivers for Windows 7 x64

null@example.com (OverFlow) — Thu, 25 Aug 2011 03:26:19 +0000

in theory you could add a sequence of garbage and it would again hash correctly... But mr_smarts is correct it would take a very powerful computer a very long time to arrive at the solution. Unless you just got lucky.

I agree with your analysis that this is the reverse of a bruteforce attack. with a BF attack the "Password" kicked out may or may not be the original password... it is simply a sequence of characters that will match the the encryption key when hashed.

Re: [SLVD] PCI Simple Communications Controller Drivers for Windows 7 x64

null@example.com (mr_smartepants) — Wed, 24 Aug 2011 17:27:18 +0000

TechDud wrote:

forgive me, i lack understanding of why a hack would be necessary.

It should not be needed. The .inf already contains a generic [Intel.NTamd64] section which should work with all 64-bit systems.

I think that the Win7 drivers are either included in the OS or downloadable from Windows update.
This is a quick 'hack' test just to see if that section is relevant. I'll bet money that it won't work.

Oh, and WHQL signing will never happen when tinkering with the .inf as I have (unless you have a LOT of time on your hands, which I don't)

Re: [SLVD] PCI Simple Communications Controller Drivers for Windows 7 x64

null@example.com (TechDud) — Wed, 24 Aug 2011 07:35:26 +0000

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?