Community
cancel
Showing results for 
Search instead for 
Did you mean: 
idata
Community Manager
1,249 Views

Intel Pro 1000 PT 64 bit win7 problem

On two different machines I always get this error "The software is not designed for this version of Microsoft Windows" and thats the end of the install.

I can install the drivers manually but then I haven't any options too configure the adaptor as the proset software isn't installed.

Anyway round this bug which seems to have effected the 15.x drivers

0 Kudos
17 Replies
idata
Community Manager
106 Views

Mark_H_Intel
Employee
106 Views

Did you download PROWinx64.exe or PROWin32.exe? You need PROWinx64.exe for 64-bit Windows.

Which PRO/1000 PT adapter do you have?

idata
Community Manager
106 Views

Prowinx64.exe Intel Pro 1000 pt server adaptor

Mark_H_Intel
Employee
106 Views

I don't know why you are getting the error. When you look at the computer properties does the "System type" say "64-bit Operating System"? Are you running a beta of a service pack for Windows 7?

Here is something you can try.

Try extracting the files and running the installation from APPS\PROSETDX\Winx64\DxSysChk.exe. (Or bypass the check and run DxSetup.exe.)

The files are in an executable zip file, so you can extract them with WinZIP, WinRAR, or similar programs.

You can also extract them from the command line using:

Prowinx64.exe /f /s /e

 

The http://downloadmirror.intel.com/18713/eng/readme.htm read me has more details on installation.

I hope this helps.

Mark H

idata
Community Manager
106 Views

Windows seven enterprise 64 bit no beta service packs.

Tried your other solutions already and still get the same error message.

idata
Community Manager
106 Views

One log file. It seems to be detecting that the system is 32 bit and not 64. Also not detecting the network card which is interesting.

=== Logging started: 15/10/2010 18:59:42 ===

 

Action start 18:59:42: INSTALL.

 

Action start 18:59:42: AppSearch.

 

Action ended 18:59:42: AppSearch. Return value 1.

 

Action start 18:59:42: CostInitialize.

 

Action ended 18:59:42: CostInitialize. Return value 1.

 

Action start 18:59:42: FindRelatedProducts.

 

Action ended 18:59:42: FindRelatedProducts. Return value 1.

 

Action start 18:59:42: LaunchConditions.

 

Action ended 18:59:42: LaunchConditions. Return value 1.

 

Action start 18:59:42: CA_RESET_BASE_DRIVERS.

 

Action ended 18:59:42: CA_RESET_BASE_DRIVERS. Return value 1.

 

Action start 18:59:42: CA_RESET_LR_DMIX.

 

Action ended 18:59:42: CA_RESET_LR_DMIX. Return value 1.

 

Action start 18:59:42: SetSetupBDCost.

 

Action ended 18:59:42: SetSetupBDCost. Return value 1.

 

Action start 18:59:42: CA_RESET_SNMP.

 

Action ended 18:59:42: CA_RESET_SNMP. Return value 1.

 

Action start 18:59:42: CA_RESET_SMASHV2.

 

Action ended 18:59:42: CA_RESET_SMASHV2. Return value 1.

 

Action start 18:59:42: CA_RESET_DCB.

 

Action ended 18:59:42: CA_RESET_DCB. Return value 1.

 

Action start 18:59:42: CA_RESET_FCOE.

 

Action ended 18:59:42: CA_RESET_FCOE. Return value 1.

 

Action start 18:59:42: CA_RESET_ADVANCED_INSTALL.

 

Action ended 18:59:42: CA_RESET_ADVANCED_INSTALL. Return value 1.

 

Action start 18:59:42: CA_RESET_BASIC_INSTALL.

 

Action ended 18:59:42: CA_RESET_BASIC_INSTALL. Return value 1.

 

Action start 18:59:42: ISSetupFilesExtract.

 

1: Starting to extract setup files

 

1: Getting SUPPORTDIR property :

 

1: Extracting SetupFiles to: C:\Users\jon\AppData\Local\Temp\{2AAA1310-1A77-472d-A7D2-A5E55B00EF8E}

 

1: Getting ISSetupFile table view

 

1: Executing ISSetupFile table view

 

1: Extracting Setup File:

 

1: C:\Users\jon\AppData\Local\Temp\{2AAA1310-1A77-472d-A7D2-A5E55B00EF8E}\Rules.Map

 

1: Extracting Setup File:

 

1: C:\Users\jon\AppData\Local\Temp\{2AAA1310-1A77-472d-A7D2-A5E55B00EF8E}\DMIXSetpCHS.reg

 

1: Extracting Setup File:

 

1: C:\Users\jon\AppData\Local\Temp\{2AAA1310-1A77-472d-A7D2-A5E55B00EF8E}\Rule.dll

 

1: Extracting Setup File:

 

1: C:\Users\jon\AppData\Local\Temp\{2AAA1310-1A77-472d-A7D2-A5E55B00EF8E}\DMIXSetpCHT.reg

 

1: Extracting Setup File:

 

1: C:\Users\jon\AppData\Local\Temp\{2AAA1310-1A77-472d-A7D2-A5E55B00EF8E}\uninstall.reg

 

1: Extracting Setup File:

 

1: C:\Users\jon\AppData\Local\Temp\{2AAA1310-1A77-472d-A7D2-A5E55B00EF8E}\ConfigCheck.vbs

 

1: Extracting Setup File:

 

1: C:\Users\jon\AppData\Local\Temp\{2AAA1310-1A77-472d-A7D2-A5E55B00EF8E}\StrProv.dll

 

1: Extracting Setup File:

 

1: C:\Users\jon\AppData\Local\Temp\{2AAA1310-1A77-472d-A7D2-A5E55B00EF8E}\StrProvR.dll

 

1: Extracting Setup File:

 

1: C:\Users\jon\AppData\Local\Temp\{2AAA1310-1A77-472d-A7D2-A5E55B00EF8E}\SavResDX.vbs

 

1: Extracting Setup File:

 

1: C:\Users\jon\AppData\Local\Temp\{2AAA1310-1A77-472d-A7D2-A5E55B00EF8E}\SavResPROSet.vbs

 

1: Extracting Setup File:

 

1: C:\Users\jon\AppData\Local\Temp\{2AAA1310-1A77-472d-A7D2-A5E55B00EF8E}\DMIXSetpDEU.reg

 

1: Extracting Setup File:

 

1: C:\Users\jon\AppData\Local\Temp\{2AAA1310-1A77-472d-A7D2-A5E55B00EF8E}\Rules.dat

 

1: Extracting Setup File:

 

1: C:\Users\jon\AppData\Local\Temp\{2AAA1310-1A77-472d-A7D2-A5E55B00EF8E}\DMIXSetpESN.reg

 

1: Extracting Setup File:

 

1: C:\Users\jon\AppData\Local\Temp\{2AAA1310-1A77-472d-A7D2-A5E55B00EF8E}\DMIXSetpFRA.reg

 

1: Extracting Setup File:

 

1: C:\Users\jon\AppData\Local\Temp\{2AAA1310-1A77-472d-A7D2-A5E55B00EF8E}\DMIXSetpITA.reg

 

1: Extracting Setup File:

 

1: C:\Users\jon\AppData\Local\Temp\{2AAA1310-1A77-472d-A7D2-A5E55B00EF8E}\DMIXSetpJPN.reg

 

1: Extracting Setup File:

 

1: C:\Users\jon\AppData\Local\Temp\{2AAA1310-1A77-472d-A7D2-A5E55B00EF8E}\DMIXSetpKOR.reg

 

1: Extracting Setup File:

 

1: C:\Users\jon\AppData\Local\Temp\{2AAA1310-1A77-472d-A7D2-A5E55B00EF8E}\DMIXSetpPTB.reg

 

1: Extracting Setup File:

 

1: C:\Users\jon\AppData\Local\Temp\{2AAA1310-1A77-472d-A7D2-A5E55B00EF8E}\WdfCoInstaller.inf

 

1: Extracting Setup File:

 

1: C:\Users\jon\AppData\Local\Temp\{2AAA1310-1A77-472d-A7D2-A5E55B00EF8E}\WdfCx64F.dll

 

1: Extracting Setup File:

 

1: C:\Users\jon\AppData\Local\Temp\{2AAA1310-1A77-472d-A7D2-A5E55B00EF8E}\WdfCx32F.dll

 

1: Extracting Setup File:

 

1: C:\Users\jon\AppData\Local\Temp\{2AAA1310-1A77-472d-A7D2-A5E55B00EF8E}\DMIXSetpENU.reg

 

1: Extracting Setup File:

 

1: C:\Users\jon\AppData\Local\Temp\{2AAA1310-1A77-472d-A7D2-A5E55B00EF8E}\Crash_dll.dll

 

1: Setting SUPPORTDIR property to: C:\Users\jon\AppData\Local\Temp\{2AAA1310-1A77-472d-A7D2-A5E55B00EF8E}

 

1: Setting ISSETUPFILESCOMPLETED property

 

Action ended 18:59:42: ISSetupFilesExtract. Return value 1.

 

Action start 18:59:42: ResolveSource.

 

Action ended 18:59:42: ResolveSource. Return value 1.

 

Action start 18:59:42: ValidateProductID.

 

Action ended 18:59:42: ValidateProductID. Return value 1.

 

Action...
Mark_H_Intel
Employee
106 Views

I am not an expert on reading these logs, but I can see enough to address a couple of your comments.

The log shows "Current system is 32e bit system." I think this means we detected that this is 32-bit extended (64-bit) system.

The log lines that read "Failed to get Hardware ID from PCI device" are trying to detect FCoE capable devices. Those lines do not mean your Ethernet adapter was not detected.

I am still stumped as to why you get the error at the end.

Maybe we will find a clue by looking at some system details.

You can run the http://www.intel.com/support/idyp.htm Intel(R) System Identification Utility to capture information about any of the Intel components on the machine. Go to the Advanced tab after you run the utility and then save the information using the save icon.

Mark H

Mark_H_Intel
Employee
106 Views

One of the software developers looked at the log file. The log file indicates that you have a 64-bit system, but the web pack download you are using does not support the 64-bit system.

Try deleting the download you are using and getting a fresh copy of the download. Make sure the file name you download is PROWinx64.exe. You do not want PROWin64.exe (no x in this name because it is for Itanium(R) Processors) or PROWin32.exe.

Mark H

idata
Community Manager
106 Views

Already done that. Looks like someones got the wrong package on the download link or packaged the wrong one up.

Same thing happen a year ago with the ahci drivers set. It was a long time before the correct version was put up.

Mark_H_Intel
Employee
106 Views

I downloaded the file and installed it without the problem you mentioned. Maybe there is a bad copy cached somewhere. Try downloading prowinx64.exe under one of the other Windows operating systems. The file is the same and covers all x64 Windows no matter which OS is listed in Download Center.

http://downloadcenter.intel.com/confirm.aspx?httpDown=http://downloadmirror.intel.com/18725/eng/PROW... Here is a link to the x64 file for Windows Server 2008 R2. Hopefully this one will work for you.

Mark H

idata
Community Manager
106 Views

Still the same problem. I noticed there was a new version released today. Downloaded this on another pc same result.

idata
Community Manager
106 Views

Any news on this???

I can install the driver manually it's the proset software I want so I can set the paremeters.

idata
Community Manager
106 Views

Any news on this as it still detects the wrong operating system.

idata
Community Manager
106 Views

Still no fix ???? Come on problem not solved. Ignoring it doesn't make it go away.

Mark_H_Intel
Employee
106 Views

I am sorry to hear you are still seeing this issue. We have tried the web pack downloads on multiple systems without replicating your issue.I am stumped as to the cause for your problem. Neverhteless, I have an idea that might help. When we sell the retail adapters, we put a CD in the box. I have posted a http://downloadcenter.intel.com/Detail_Desc.aspx?agr=Y&DwnldID=19754 zip file copy of the version 16.0 CD in Download Center.

Try http://downloadcenter.intel.com/Detail_Desc.aspx?agr=Y&DwnldID=19754 downloading the file, unzip it, and run autorun.

I hope this will work. Let us know either way.

Mark H

idata
Community Manager
106 Views

Sadly same problem. It's not urgent but strange when every other bit of harder correctly detects the operating system.

Interestingly had the same problem at work on another pc. Ii've just re-installed the os on that machine. So I'll try it again tomorrow on that pc and see what happens.

The above indicates a likely problem with the drivers though.

Reply