WINDOWS for Galileo is LIVE

http://msdn.microsoft.com/en-us/windows/hardware/dn786369

Thanks Doc, I just replaced the power sup, two harddrives, fans etc, it has a ATI PCI express All-in-wonder card. I have acouple good laptops that I use. this doesnt get used alot anymore but its only 32 and i need 64 for the newest Linux I wanted to install and fig I might as well get a board that will run 2 cores or more. I wasnt sure about my two DVD burners it didnt look like the newer boards had anything for the 40 pin ribbon cables(or if they make adapters) I'll wait for a deal on ebay, I just want to make sure I get a board that will work. You  know I really want to thank you for getting back to me so fast. I've got on a few forums over the years and never got ans to my questions so I gave up until now. So thanks again, Dave

It will be very difficult to find a board with an IDE/PATA/ATAPI 40-pin connector these days.  However, DVD burners are cheap and better to replace them.

There are adapters to convert a device (CD/DVD, or HD) from the 40-pin connector, However, with just a bit added to the cost of the adapter, you can get a nice, new sata DVD drive.

Your All-In-Wonder card has the TV tuner, right?  If so, it probably is NTSC which, of course, is history now.  So, if you need to receive television (in the US), I would look for a new card that had ATSC.

I have been through this many times, with my old gear and that of friends.  Can you make the old stuff work?  Yes.  However, I have found that, while it is fun to tinker, it is just simply not practical.  For me, getting good performance from a currently supported hardware environment is the best path.  And, I have a room of old stuff that I purge now and then.  I hate to discard this stuff, as it all still "works", but is just not worth keeping.

Good luck with your project.

Doc

Hi,

looks like compiling and installing https://downloadcenter.intel.com/Detail_Desc.aspx?lang=eng&changeLang=true&DwnldId=15817 fixed this for me.

Will do some tests and report back asap.

Hi,

It seems like we need to wait a little since the current boards need an update to run Windows (I Bought an Intel Galileo).

Looking forward to receive the IoT kits from MS!

/Thomas

Let me know if anyone gets this working. The current libraries fail on "Wire" libraries

The error:

C:\Users\thoug_000.HAWKING\Desktop\Galileo-arduino-1.5.3\libraries\Adafruit_Motorshield\Adafruit_MotorShield.cpp: In member function 'void Adafruit_MotorShield::begin(uint16_t)':

C:\Users\thoug_000.HAWKING\Desktop\Galileo-arduino-1.5.3\libraries\Adafruit_Motorshield\Adafruit_MotorShield.cpp:46:3: error: 'Wire1' was not declared in this scope

Hi,

I just put a SSD on my laptop and I want to have IRST working but I did something wrong intalling/updating, and now I'm stuck.

Can't remove old program, Tried to install earlier version says aa newer ver. is installed. Newer versions say "This computer does not meet minimum requirements for installing this software".

When i boot Windows a message appears saying "This computer doesn't have IRST enabled".

Would also like to know if it's possible to use IRST file in SSD instead of Express Cache iSSD..

Thanks.

Hi,

Anyone aware of any Bonjour library for Galileo board? For example, this Ethernet Bonjour library (neophob/EthernetBonjour · GitHub) works with Arduino. This Bonjour library uses direct hardware access by using definitions/functions provided the W5100.h and W5200.cpp in the /utility folder in the Ethernet library that write directly into the W5100/W5200 registers.

Is there any effort on doing this for Galileo?

Just recently bought this card, installed it, pushed power and get a black screen saying "Not supported, System Halted".  It looks like I am SOL, but thought I would get a second opinion. Any ideas?

--Using HP dv7-6185us Laptop with Windows 7

can someone please send me a direct link to Intel display audio driver for windows 8.1 64 bit please someone give me a link

i  need to update my graphics driver. i tried to update my graphic driver to the 15.33.22.64.3621 version. i downloaded it but when i tried to install it, it said something like the driver being installed is not compatible. so which graphic driver version do i use?

Operating System: Windows 8.1 64-bit (6.3, Build 9600) (9600.winblue_gdr.140330-1035)

Card name: Intel(R) HD Graphics 4600

is that enough info??

You will get a better response here:  Graphics

I have moved your post there:

Doc

Hey there, you've undoubtedly been getting a lot of these over the last 9 to 10 months, but any info is good info so I'm going to add my system details and what remedies I've tried so far that have all failed. First, my relevant system specs:

- Intel Core 15-3570K CPU

- Gigabyte GA-H77N-WIFI motherboard

- nVidia GeForce GTX 770 GPU

- Intel Centrino N2230 Mini-PCIe card (with stock antenna setup)

- - with most recent driver installed, 15.12.0.6, (checked against auto-updater)

- Running Windows 8.1 with most (if not all) recent updates

- ASUS N900 802.11N Router

- - with most recent firmware updates.

- - using WPA2/AES encryption

I actually own two computers with the exact same Mini-PCIe card in it. My second computer is the Wacom Cintiq Companion 256GB edition. It, too, has the N2230 inside running Windows 8.1, and is suffering the EXACT same issues as my desktop machine and as you've likely read elsewhere by other people. When my connection is working (on either machine) it's slow. Nominally I should be getting close to 30mbps download and 8 to 10 mbps upload. Under Windows 8.1, speeds are around 0.50 to 1.50 mbps down to 0.25 to 1 mbps up. My phone, a Nexus 5, gets my full network speed when tested right next to these computers on the same wifi network. It's worth noting that even when I have connection to the internet, logging into the GUI to my wireless router is painfully slow. So these slow network speeds aren't just the internet -- the very network connection itself is crawling as it struggles to even communicate with my local router. Full disconnections happen anywhere from as little as 3 minutes into computer usage to one to two hours after the system has been running. The "Limited" warning doesn't always appear when the connection is dropped like a mic by my computers in these cases reconnection can only occur by disconnecting/connecting from the network, disabling/enabling the adapter, or restarting the computer. Kind of like getting an old NES to work, blowing in the cartridge, whamming on the reset button...

Other things I've tried, all of which didn't make a difference:

- Setting my router's wifi channels to a set number instead of Auto

- Disabling B/G wireless signal protection

- Using the latest drivers
- Using older drivers

- Reinstalling current drivers
- Disabling power management for the adapter
- Setting specific public DNS server addresses (for both IPv4 and IPv6)

- Running the various command line "fixes" (disabling heuristics, setting log, those other 2 or 3 plastered on lots of blogs)

- Reformatting my system and starting over from scratch (albeit with Windows 8.1 as it's all I have)

If anyone knows of any particular things that I haven't done that you'd know would work, I'm all ears. If not, you can add my story to the pile, Intel. Let me know if you need any additional information.

i have a toshiba Satellite C55-A intel core i5-3230M with the intel hd graphics 4000 windows 8.1 64bit and 6GBs of ram and I keep on getting this same error pop up randomly, i have updated all my graphic drivers and changed my graphic settings to low but it still keeps happening, help would be great and yes i know my computers not the greatest but is there anything i can do to stop the error?

Hello Everyone,

Recently I have faced an issue in OS deployment for Intel DH87MC and DB85FL.

In our company, all computers have Intel Main Board (DG41TY, DG41TX, DH61WW, DH61BE, DH61ZE) and these days according to the market availability we are purchasing DH87MC and DB85FL.

For OS deployment in these systems we are using the SCCM server that works perfectly fine for the old model of Main boards that we had but for the new models (DH87MC and DB85FL) I can not deploy OS. Also I can deploy OS in different Model of Laptops.

The systems boot from NIC and get the IP address but when the system centre page appears, the system will restart automatically without showing any error.

The steps that I have done so far:

- Recreate driver package

- Check Win PE

- Edit the Task Sequence

- Try additional NIC (This solution worked but it does not make sense to use additional NIC for PCs)

I appreciate if you share your experience and knowledge with me to solve this issue.

Thanks,

thanks sylvia,

I'm really sorry to hear this, infact these MBs are still manufactured and sold (I've just purchased one manufactured in june).

the big issue I see in the system with Intel DH87MC and haswell refresh Core i7 4790 is that system can't reboot.

I think it's not so difficult for a giant company like Intel solve this, and I hope that the product manager responsible of MBs will understand that

If you've bought an Intel board with 8-series chipset, at a moment where intel said that 8-series chipset will support haswell refresh just with a bios update,

and then, at the time of haswell refresh launch, hear that Intel won't release this update 'cause this is its last series of boards,

well, you feel betrayed,

infact if you buy a cheap board, by unknown manufacturers, you can expect that support is terrible, but from Intel, you expect a great support fot its own product.

I hope you can understand,

Stefano

Hi,

I pushed to use AMT in my organisation and we have finally got a 3rd Party Cert from Go Daddy so we can perform remote configuration.  All appeared to be working fine and I successfully remotely configured 250 HP 8200 Elite computers without any problems using an encrypted XML.  However, I have just tried to configure our HP Elite 8000 PC's, which use AMT 5.0, and I am getting the below error message.  It can't be a certificate or authentication issue as I am using the exact same XML that worked with the HP Elite 8200.

Any ideas?

2014-07-11 13:30:10: Thread:392(INFO) : ACU Configurator , Category: HandleOutPut Source: Src\ActivatorUtils.cpp : HandleOutput Line: 210: Starting log 2014-07-11 13:30:10

2014-07-11 13:30:10: Thread:392(DETAIL) : ACU Configurator, Category: VerifyFileSignature Source: Src\ActivatorMain.cpp : wmain Line: 122: Verifying the digital signature of ACU.dll, this operation might take up to 3 minutes...

2014-07-11 13:30:11: Thread:392(INFO) : ACU Configurator , Category: VerifyFileSignature Source: Src\ActivatorUtilsWin.cpp : VerifyFileSignature Line: 457: The file "C:\WMFS_AMT_Configurator\ACU.dll" is signed and the signature was verified.

2014-07-11 13:30:12: Thread:392(DETAIL) : ACU.dll, Category: SetCompatibilityMode Source: Src\ActivatorDll.cpp : SetCompatibilityMode Line: 104: Set compatibility mode to 8.0.

2014-07-11 13:30:12: Thread:392(DETAIL) : ACU Configurator , Category: -Start- Source: Src\HECIDiscovery.cpp : CheckAMT Line: 78: ***** Start CheckAMT ******

2014-07-11 13:30:12: Thread:392(DETAIL) : ACU Configurator , Category: -HECI- Source: Src\HECIWin.cpp : HECIWin::Init Line: 185: Connected to the Intel(R) Management Engine Interface driver, version 5.2.0.1008

2014-07-11 13:30:12: Thread:392(INFO) : ACU Configurator , Category: AMT Mode Source: Src\HECIDiscovery.cpp : CheckAMT Line: 382: Intel(R) AMT  in PROVISIONING_MODE_ENTERPRISE

2014-07-11 13:30:12: Thread:392(DETAIL) : ACU Configurator , Category: -END- Source: Src\HECIDiscovery.cpp : CheckAMT Line: 461: ***** END CheckAMT ******

2014-07-11 13:30:14: Thread:392(DETAIL) : ACU Configurator , Category: -Start- Source: Src\HECIDiscovery.cpp : GetAmtFQDN Line: 1256: ***** Start GetAmtFQDN ******

2014-07-11 13:30:14: Thread:392(DETAIL) : ACU Configurator , Category: Status message Source: Src\HECIDiscovery.cpp : GetAmtFQDN Line: 1274: Failed to get data from the firmware. (0xc0000022)

2014-07-11 13:30:14: Thread:392(DETAIL) : ACU Configurator , Category: -END- Source: Src\HECIDiscovery.cpp : GetAmtFQDN Line: 1333: ***** END GetAmtFQDN ******

2014-07-11 13:30:17: Thread:392(INFO) : ACU Configurator , Category: Discovery Source: Src\HostBasedSetup.cpp : HostBasedSetup::Discovery Line: 410: Calling function Discovery...

2014-07-11 13:30:17: Thread:392(INFO) : ACU Configurator , Category: Local System Account Source: Src\HostBasedSetup.cpp : HostBasedSetup::GetLocalSystemAccount Line: 199: Calling function GetLocalSystemAccount over MEI...

2014-07-11 13:30:17: Thread:392(DETAIL) : ACU Configurator , Category: -HECI- Source: Src\HECIWin.cpp : HECIWin::Init Line: 185: Connected to the Intel(R) Management Engine Interface driver, version 5.2.0.1008

2014-07-11 13:30:17: Thread:392(ERROR) : ACU Configurator , Category: Local System Account Source: Src\HostBasedSetup.cpp : HostBasedSetup::GetLocalSystemAccount Line: 226: Error: failed to retrieve Local System Account using MEI; error code - 3221242473

2014-07-11 13:30:17: Thread:392(INFO) : ACU Configurator , Category: Discovery Source: Src\HostBasedSetup.cpp : HostBasedSetup::Discovery Line: 430: Host Based Setup is not supported

2014-07-11 13:30:17: Thread:392(INFO) : ACU Configurator , Category: Discovery Source: Src\HostBasedSetup.cpp : HostBasedSetup::Discovery Line: 432: Function Discovery ended successfully

2014-07-11 13:30:19: Thread:392(DETAIL) : ACU Configurator , Category: -Start- Source: Src\HECIDiscovery.cpp : UuidDiscovery Line: 1339: ***** Start UuidDiscovery ******

2014-07-11 13:30:19: Thread:392(DETAIL) : ACU Configurator , Category: Status message Source: Src\HECIDiscovery.cpp : UuidDiscovery Line: 1346: Error message not found- 0x800084d1. (0x800084d1)

2014-07-11 13:30:19: Thread:392(DETAIL) : ACU Configurator , Category: Returned data Source: Src\ActivatorDll.cpp : GetHostAndMEInfo Line: 4041: GetHostAndMEInfo output data: IsAMT:True, isAmtCapable:False, isEnterpriseMode:True, configurationMode:0, isRemoteConfigEnabled:True, AMTversion:5.2.1, isMobile:False, provisioningTlsMode:2, uuid:EE1E2A78-065C-11DF-BBDA-FECD88FC000F, isClientConfigEnabled:False, hostBasedSupport:False, configurationState:1, FQDN:HPSystem.wmfs.net.

2014-07-11 13:30:19: Thread:392(INFO) : ACU Configurator, Category: -ConfigAMT- Source: Src\ActivatorMain.cpp : wmain Line: 789: HPSystem.wmfs.net:Starting Unified configuration flow...

2014-07-11 13:30:19: Thread:392(DETAIL) : ACU Configurator , Category: -Start- Source: Src\ActivatorDll.cpp : ClientControlConfiguration Line: 2595: ***** Start ClientControlConfiguration ******

2014-07-11 13:30:21: Thread:392(DETAIL) : ACU Configurator , Category: -Start- Source: Src\HECIDiscovery.cpp : TcpIpDiscovery Line: 1358: ***** Start TcpIpDiscovery ******

2014-07-11 13:30:21: Thread:392(DETAIL) : ACU Configurator , Category: Status message Source: Src\HECIDiscovery.cpp : TcpIpDiscovery Line: 1394: AMT Status code - Internal error. (0xc0004269)

2014-07-11 13:30:23: Thread:392(DETAIL) : ACU Configurator , Category: -Start- Source: Src\HECIDiscovery.cpp : GetAmtFQDN Line: 1256: ***** Start GetAmtFQDN ******

2014-07-11 13:30:23: Thread:392(DETAIL) : ACU Configurator , Category: Status message Source: Src\HECIDiscovery.cpp : GetAmtFQDN Line: 1274: Failed to get data from the firmware. (0xc0000022)

2014-07-11 13:30:23: Thread:392(DETAIL) : ACU Configurator , Category: -END- Source: Src\HECIDiscovery.cpp : GetAmtFQDN Line: 1333: ***** END GetAmtFQDN ******

2014-07-11 13:30:24: Thread:392(DETAIL) : , Category: ADInterfaceInternal Source: Src\ADInterfaceInternal.cpp : ADInterfaceNamespace::ADInterfaceInternal::InitBind Line: 952: Step into InitBind

2014-07-11 13:30:25: Thread:392(DETAIL) : , Category: ADInterfaceInternal Source: Src\ADInterfaceInternal.cpp : ADInterfaceNamespace::ADInterfaceInternal::InitBind Line: 1141: Step out InitBind

2014-07-11 13:30:25: Thread:392(DETAIL) : , Category: ADInterfaceInternal Source: Src\ADInterfaceInternal.cpp : ADInterfaceNamespace::ADInterfaceInternal::CheckIfOUExist Line: 810: Step into CheckIfOUExist

2014-07-11 13:30:25: Thread:392(DETAIL) : , Category: ADInterfaceInternal Source: Src\ADInterfaceInternal.cpp : ADInterfaceNamespace::ADInterfaceInternal::CheckIfOUExist Line: 855: Step out CheckIfOUExist

2014-07-11 13:30:25: Thread:392(DETAIL) : ACU.dll, Category: GenerateOTP Source: Src\ActivatorDll.cpp : GenerateOTP Line: 1020: Changing AMT state from IN-provisioning to Pre-Provisioning in order to set AMT OTP

2014-07-11 13:30:25: Thread:392(DETAIL) : ACU Configurator , Category: -Start- Source: Src\ActivatorDll.cpp : StopConfigurationInt Line: 5008: ***** Start StopConfigurationInt ******

2014-07-11 13:30:25: Thread:392(DETAIL) : StopConfiguration, Category: Entering StopConfiguration Source: Src\ActivatorDll.cpp : StopConfigurationInt Line: 5009:

2014-07-11 13:30:25: Thread:392(INFO) : ACU Configurator , Category: Unprovision Source: Src\HostBasedSetup.cpp : HostBasedSetup::StopConfiguration Line: 326: Calling function StopConfiguration over MEI...

2014-07-11 13:30:25: Thread:392(INFO) : ACU Configurator , Category: Local System Account Source: Src\HostBasedSetup.cpp : HostBasedSetup::GetLocalSystemAccount Line: 199: Calling function GetLocalSystemAccount over MEI...

2014-07-11 13:30:25: Thread:392(DETAIL) : ACU Configurator , Category: -HECI- Source: Src\HECIWin.cpp : HECIWin::Init Line: 185: Connected to the Intel(R) Management Engine Interface driver, version 5.2.0.1008

2014-07-11 13:30:25: Thread:392(ERROR) : ACU Configurator , Category: Local System Account Source: Src\HostBasedSetup.cpp : HostBasedSetup::GetLocalSystemAccount Line: 226: Error: failed to retrieve Local System Account using MEI; error code - 3221242473

2014-07-11 13:30:25: Thread:392(ERROR) : ACU Configurator , Category: AMT Setup Source: Src\HostBasedSetup.cpp : HostBasedSetup::StopConfiguration Line: 334: failed to initialize WSMAN client

2014-07-11 13:30:25: Thread:392(DETAIL) : StopConfiguration, Category: StopConfiguration AMT Source: Src\ActivatorDll.cpp : StopConfigurationInt Line: 5022: Waiting for FW to move to Pre-Provision state(0)...

2014-07-11 13:30:32: Thread:392(INFO) : ACU Configurator , Category: Discovery Source: Src\HostBasedSetup.cpp : HostBasedSetup::Discovery Line: 410: Calling function Discovery...

2014-07-11 13:30:32: Thread:392(INFO) : ACU Configurator , Category: Local System Account Source: Src\HostBasedSetup.cpp : HostBasedSetup::GetLocalSystemAccount Line: 199: Calling function GetLocalSystemAccount over MEI...

2014-07-11 13:30:32: Thread:392(DETAIL) : ACU Configurator , Category: -HECI- Source: Src\HECIWin.cpp : HECIWin::Init Line: 185: Connected to the Intel(R) Management Engine Interface driver, version 5.2.0.1008

2014-07-11 13:30:32: Thread:392(ERROR) : ACU Configurator , Category: Local System Account Source: Src\HostBasedSetup.cpp : HostBasedSetup::GetLocalSystemAccount Line: 226: Error: failed to retrieve Local System Account using MEI; error code - 3221242473

2014-07-11 13:30:32: Thread:392(INFO) : ACU Configurator , Category: Discovery Source: Src\HostBasedSetup.cpp : HostBasedSetup::Discovery Line: 430: Host Based Setup is not supported

2014-07-11 13:30:32: Thread:392(INFO) : ACU Configurator , Category: Discovery Source: Src\HostBasedSetup.cpp : HostBasedSetup::Discovery Line: 432: Function Discovery ended successfully

2014-07-11 13:30:32: Thread:392(DETAIL) : StopConfiguration, Category: Exit StopConfiguration  Source: Src\ActivatorDll.cpp : StopConfigurationInt Line: 5040: This system was already unconfigured. The system was successfully put in the "Pre Provisioned" state and the Intel(R) AMT interfaces are now closed.

2014-07-11 13:30:32: Thread:392(DETAIL) : ACU Configurator , Category: -END- Source: Src\ActivatorDll.cpp : StopConfigurationInt Line: 5042: ***** END StopConfigurationInt ******

2014-07-11 13:30:32: Thread:392(DETAIL) : ACU Configurator , Category: -HECI- Source: Src\HECIWin.cpp : HECIWin::Init Line: 185: Connected to the Intel(R) Management Engine Interface driver, version 5.2.0.1008

2014-07-11 13:30:32: Thread:392(DETAIL) : ACU.dll, Category: GenerateOTP Source: Src\ActivatorDll.cpp : GenerateOTP Line: 1046: Moving to Pre-Provisioning state failed. An old OTP exist in local settings store.

2014-07-11 13:30:32: Thread:392(DETAIL) : ACU Configurator , Category: -Start- Source: Src\ActivatorDll.cpp : StartConfigurationInt Line: 4922: ***** Start StartConfigurationInt ******

2014-07-11 13:30:32: Thread:392(DETAIL) : StartConfiguration, Category: Enter StartConfiguration Source: Src\ActivatorDll.cpp : StartConfigurationInt Line: 4929:

2014-07-11 13:30:32: Thread:392(DETAIL) : ACU Configurator , Category: -HECI- Source: Src\HECIWin.cpp : HECIWin::Init Line: 185: Connected to the Intel(R) Management Engine Interface driver, version 5.2.0.1008

2014-07-11 13:30:32: Thread:392(DETAIL) : ACU Configurator , Category: Status message Source: Src\ZTCLocalAgent.cpp : Activate Line: 538: Activate Intel(R) AMT configuration: (0xc0000050) (Success. )

2014-07-11 13:30:32: Thread:392(DETAIL) : StartConfiguration, Category: StartConfiguration AMT Source: Src\ActivatorDll.cpp : StartConfigurationInt Line: 4965: Waiting for FW to move to In-Provision state(0)...

2014-07-11 13:30:39: Thread:392(DETAIL) : StartConfiguration, Category: Exit StartConfiguration  Source: Src\ActivatorDll.cpp : StartConfigurationInt Line: 4993: The Start configuration operation completed successfully.

2014-07-11 13:30:39: Thread:392(DETAIL) : ACU Configurator , Category: -END- Source: Src\ActivatorDll.cpp : StartConfigurationInt Line: 4995: ***** END StartConfigurationInt ******

2014-07-11 13:30:39: Thread:392(DETAIL) : localhost, Category: Configure AMT Source: Src\ActivatorDll.cpp : ConfigureAMT Line: 1096:

2014-07-11 13:30:39: Thread:392(DETAIL) : ACU.dll, Category: GetNetworkSettings Source: Src\ActivatorDllWin.cpp : LoadNetworkSettings Line: 858: RCSaddress=wm-vms-rcs-01.wmfs.net, RCSMIUser=wmfs\intel.rcs, RCSProfileName=WMFS_AMT_Config

2014-07-11 13:30:39: Thread:392(DETAIL) : ACU Configurator , Category: WMI_GetNetworkSettings Source: Src\WMIAccess.cpp : WMI_GetNetworkSettings Line: 2896: Success. (0) ((ExecMethod WMI_GetNetworkSettings) Success. )

2014-07-11 13:30:39: Thread:392(DETAIL) : NetworkSettingClass, Category: LoadSourceForAMTName Source: Src\NetworkSettingsClass.cpp : NetworkSettings::NetworkSettingClass::LoadSourceForAMTName Line: 517: PC19830.wmfs.net

2014-07-11 13:30:39: Thread:392(DETAIL) : ACU.dll, Category: Configure AMT Source: Src\ActivatorDllWin.cpp : MI_ConfigAMT Line: 591: RCSaddress=wm-vms-rcs-01.wmfs.net, RCSMIUser=wmfs\intel.rcs, UUID=EE1E2A78-065C-11DF-BBDA-FECD88FC000F, ConfigMode=2, PID=, RCSProfileName=WMFS_AMT_Config, AMTVersion=5.2.1, OldADOU=, Configure AMT Name= True. Configure AMT IPv4= True. AMT Name= Host Name- HPSystem Domain Name- wmfs.net . Source For AMT Name= Host Name- PC19830 Domain Name- wmfs.net . Default OS Name= Host Name- PC19830 Domain Name- wmfs.net . Host IPv4= IPv4 Address- 10.32.48.41 IPv4 SubNet- 255.255.255.0 IPv4 Gateway- 10.32.48.254 IPv4 Primary DNS- 10.32.64.20 IPv4 Secondary DNS- 10.191.248.41 . Configure AMT IPv4 to DHCP mode= True. AMT IPv4= IPv4 Address- 10.32.48.41 .

2014-07-11 13:30:41: Thread:392(DETAIL) : ACU Configurator , Category: WMI_ConfigAMT Source: Src\WMIAccess.cpp : WMI_ConfigAMT Line: 1090: An SSL error occurred. Verify the username and password, and the PSK or certificate settings, where applicable. (0xc000521f) ((ExecMethod WMI_ConfigAMT) An SSL error occurred. Verify the username and password, and the PSK or certificate settings, where applicable.  (0xc000521f). Failed while calling  WS-Management call  GetAmtVersion (CIM_SoftwareIdentity.Get). Intel(R) AMT connection error  0xc000521c: A TCP error occurred. Make sure that the destination settings are correct and that a network connection exists to the target.  (0xc000521c). Valid certificate for PKI configuration not found.  (0xc00007e5).  (0xc000521f). )

2014-07-11 13:30:41: Thread:392(ERROR) : ACU.dll, Category: Configure Profile Source: Src\ActivatorDll.cpp : ConfigureAMT Line: 1385: Failed to complete remote configuration of this Intel(R) AMT device. . (An SSL error occurred. Verify the username and password, and the PSK or certificate settings, where applicable.  (0xc000521f). Failed while calling  WS-Management call  GetAmtVersion (CIM_SoftwareIdentity.Get). Intel(R) AMT connection error  0xc000521c: A TCP error occurred. Make sure that the destination settings are correct and that a network connection exists to the target.  (0xc000521c). Valid certificate for PKI configuration not found.  (0xc00007e5).  (0xc000521f). ).

2014-07-11 13:30:41: Thread:392(ERROR) : , Category: Configure Profile Source: Src\ActivatorDll.cpp : ConfigureAMT Line: 2201: Configure Profile Failed: An SSL error occurred. Verify the username and password, and the PSK or certificate settings, where applicable.  (0xc000521f). Failed while calling  WS-Management call  GetAmtVersion (CIM_SoftwareIdentity.Get). Intel(R) AMT connection error  0xc000521c: A TCP error occurred. Make sure that the destination settings are correct and that a network connection exists to the target.  (0xc000521c). Valid certificate for PKI configuration not found.  (0xc00007e5).  (0xc000521f).

2014-07-11 13:30:41: Thread:392(DETAIL) : localhost, Category: end function Source: Src\ActivatorDll.cpp : ConfigureAMT Line: 2312:

2014-07-11 13:30:41: Thread:392(ERROR) : ACU.dll, Category: Profile Configuration Source: Src\ActivatorDll.cpp : ClientControlConfiguration Line: 3086: An SSL error occurred. Verify the username and password, and the PSK or certificate settings, where applicable.  (0xc000521f). Failed while calling  WS-Management call  GetAmtVersion (CIM_SoftwareIdentity.Get). Intel(R) AMT connection error  0xc000521c: A TCP error occurred. Make sure that the destination settings are correct and that a network connection exists to the target.  (0xc000521c). Valid certificate for PKI configuration not found.  (0xc00007e5).  (0xc000521f).

2014-07-11 13:30:41: Thread:392(DETAIL) : ACU Configurator , Category: -END- Source: Src\ActivatorDll.cpp : ClientControlConfiguration Line: 3112: ***** END ClientControlConfiguration ******

2014-07-11 13:30:41: Thread:392(ERROR) : ACU Configurator, Category: Exit Source: Src\ActivatorMain.cpp : wmain Line: 1096: ***********Exit with code 33. Details: Failed to configure this Intel(R) AMT device. An SSL error occurred. Verify the username and password, and the PSK or certificate settings, where applicable.  (0xc000521f). Failed while calling  WS-Management call  GetAmtVersion (CIM_SoftwareIdentity.Get). Intel(R) AMT connection error  0xc000521c: A TCP error occurred. Make sure that the destination settings are correct and that a network connection exists to the target.  (0xc000521c). Valid certificate for PKI configuration not found.  (0xc00007e5). The RCS failed to process the request.

All I had to do was install the dev package and that solved the errors I was getting when installing tcpdump.

Hi there,

I had an Ubuntu box with built-in IR receiver.

I installed XBMC and used a generic MCE RC6 compatible remote control and all worked well.

I have now bought a new D54250WYKH and installed W8.1 (not pro) and XBMC.  I installed the latest driver pack from Intel downloadcenter.  

However, it seems that the remote control doesn't do anything.  It cannot power on/off the NUC and it doesn't do anything inside XBMC.

Is there any software that I can use to check the IR receiver output?  Is there anything that will show me that what my remote control is sending is really MCE compatible?

If anybody can help with that or suggest something that I could try I'd be grateful.

Thanks,

webj

Thank you Kevin!