Good luck.Īccording to this, this and this, it is indeed the Management Engine device, so you should be able to install that HECI driver for it once you hack its. It'll complain about it not being signed or verified for the device, but it'll install. Windows should be able to find the driver. Then start up Device Manager, right click on the appropriate driverless entry, click Update Driver, tell it you want to specify where to find the driver, tell it you'll choose the driver to install, hit the Browse button and navigate to the directory containing heci.inf. Edit heci\heci.inf, remove the Intel.NTx86.5.2 section (the one that says NT 5.2 aka Windows Server 2003 isn't supported in the comment), and rename the Intel.NTx86.5.1 section to Intel.NTx86.5.2. It's a regular InstallShield installer that archives the files using the same MSZIP scheme as Microsoft CAB archives. "8086:24c6" will hopefully bring up posts by Linux users indicating their struggles to get the device working, and hopefully those posts will tell you what the device is.Īs far as the Management Engine driver is concerned, you may have better luck if you use something like Universal Extractor to extract files out of the installer. The PCI vendor and device ID will pinpoint what device it is, and a quick Google in the form of e.g. Start up Device Manager, right click on the PCI Simple Communications Controller, hit the Details tab, and in the drop-down, pick Hardware IDs. Intel Active Monitor is currently the only utility I'm aware of that can monitor the motherboard sensors.Īs far as the Simple Communications controller is concerned, I was going to say it might be an Intel HD Audio (Azalia) based modem, but it looks like the device isn't really there.Īlso try this. SpeedFan is able to detect the chip but does not yet have the ability to read sensor data off it. Intel has made it so that this sensor information is available through SMBus only (their BIOS disables access via the ISA bus by setting registers on the chip). I don't have that motherboard but a similar DG33FB motherboard.įrom reading on the Web it appears that at least the Intel desktop boards built around the 965 and Bearlake generation chipsets use the National Semiconductor PC8374L IC to provide LPC legacy devices such as the RS232C serial port header and perhaps PS/2 devices, as well as motherboard sensor monitoring for items such as a CPU external thermal diode, north and south bridge temperatures and fan monitoring. Hmmm, any other ideas? My overriding goal is be able to monitor temps and fans. Has anyone successfully installed these components under Windows 2003? Does anyone know conclusively what the Simple Communications Controller is? Are there any solutions for fan/temp monitoring under Windows 2003 for this board? I've read that it is a modem (can't find any modem drivers on Intel's site), that it is related to "Intel Quick Resume Technology" which can be disabled in BIOS, and that installing the Management Engine Interface drivers will fix it (no 2003 drivers available).Īdditionally, I think I need the Management Engine driver for things like temperature and fan speed monitoring. However, I cannot get following XP software to install:Ĭonsequently, I have an entry in Device Manager for a "PCI Simple Communications Controller" which has no drivers. So far I've been able to use the XP drivers for: Intel doesn't officially support W2K3 for this motherboard (I didn't even think to check before purchase) so there are no drivers available. I have an Intel DG33TL motherboard in a box running Windows 2003.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |