Legacy firmware io driver

Hi

I have an ES1-311. I wish to use it in legacy firmware mode. I've installed the edition of windows 8.1 which came with machine, windows 8.1 with bing, sucessfully and it activated using the oem key in firmware.

The problem I have is the touchpad. To use touchpad advanced features you need i2c drivers but the i2c driver package available from acer support IO Drivers_Intel_603.9600.1948.29470_W81x64_A.zip throws an error when trying to install if booted in legacy bios mode.

I've even tried installing everything in UEFI mode with GPT partitions etc (drivers then install ok and touchpad works), and then converting the whole thing to MBR and fixing the boot process in legacy bios mode. But after all that the touchpad didn't work in advanced mode.

Does anyone know a way around this or where I might be able to get I2C drivers that work with legacy bios. I've asked acer support and its been passed to "concern team". Its been nearly a week now with no reply so I'm starting to think they are not going to be willing to assist. I'm sure ultimately this is possible because booting ubuntu 14.04 linux in legacy bios mode manages to work with touchpad in advanced mode without issue, so I assume its a case of whether anyone has bothered to create windows drivers and whether I can find them.....

Thanks

Smiley Happy

The following is log out put when the driver fails to install in legacy bios mode:

23:48:56:338: >>> Log start
23:48:56:354: Core version: 2.0.5
23:48:56:354: Setup version: 2.0.2.1
23:48:56:354: Command line: "C:\Users\martin\Downloads\IO Drivers_Intel_603.9600.1948.29470_W81x64_A(1)\IO Drivers_Intel_603.9600.1948.29470_W81x64\Setup.exe"
23:48:56:354: OS data&colon; 6-2-1-0 64-bit
23:48:56:354: System up time: 465 sec
23:48:56:369: Current UI language: 0409
23:48:56:369: Language folder: C:\Users\martin\AppData\Local\Temp\IIF1962.tmp
23:48:56:400: Found C:\Users\martin\AppData\Local\Temp\IIF1962.tmp\en-US\IntelCommon.dll. Lang 0409. Rank 3
23:48:56:416: Relaunching setup as elevated
23:48:58:654: Dumping MSI properties (0 total)
23:48:58:669: Exit code: 0
23:48:58:669: >>> Log End
23:48:58:700: Found C:\Users\martin\AppData\Local\Temp\IIF227A.tmp\en-US\IntelCommon.dll. Lang 0409. Rank 3
23:48:58:716: Package version: 2.0.2.2
23:48:58:732: Installed version: <Not installed>
23:48:58:732: This is a clean install
23:48:58:732: Setup mode: Installation
23:48:58:747: Looking for OS: 6.0
23:48:58:747: OS check passed
23:48:58:747: .NET not required, skipping requirement check
23:48:58:763: Driver source is C:\Users\martin\Downloads\IO Drivers_Intel_603.9600.1948.29470_W81x64_A(1)\IO Drivers_Intel_603.9600.1948.29470_W81x64\Drivers
23:48:58:763: Using folder 'C:\Users\martin\Downloads\IO Drivers_Intel_603.9600.1948.29470_W81x64_A(1)\IO Drivers_Intel_603.9600.1948.29470_W81x64\Drivers' as the driver source
23:48:58:779: Scanning all active devices
23:48:58:794: Scanning GPIO\iaiogpioe.inf (Name: GPIO\iaiogpioe.inf, Version: 603.9600.1948.30590)
23:48:58:810: Section with the best match: Intel.NTamd64
23:48:58:810: Device: ACPI\INT33FC (GPIO Controller)
23:48:58:825: MUP OS bits: 0x36D54
23:48:58:825: Adding GPIO\iaiogpioe.inf to the map...
23:48:58:841: Scanning I2C\iaioi2ce.inf (Name: I2C\iaioi2ce.inf, Version: 603.9600.1948.29470)
23:48:58:841: Section with the best match: Intel.NTamd64
23:48:58:841: Device: ACPI\VEN_8086&DEV_0F41&REV_0002 (I2C ES2 Controller)
23:48:58:857: Device: ACPI\VEN_8086&DEV_0F41&REV_0003 (I2C Controller)
23:48:58:857: Device: ACPI\VEN_8086&DEV_0F41&REV_0004 (I2C Controller)
23:48:58:872: Device: ACPI\VEN_8086&DEV_0F41 (I2C Controller)
23:48:58:872: MUP OS bits: 0x36D54
23:48:58:888: Adding I2C\iaioi2ce.inf to the map...
23:48:58:888: Reading config file : C:\Users\martin\Downloads\IO Drivers_Intel_603.9600.1948.29470_W81x64_A(1)\IO Drivers_Intel_603.9600.1948.29470_W81x64\Config.xml
23:48:58:904: Read SocPackageInfo Version : 0x20C
23:48:58:904: Reading string value
23:48:58:919: Read XML SocPackageInfo Root : HKEY_LOCAL_MACHINE, Key : SOFTWARE\Intel\SOCPackageInfo, Value : VersionNumber, Version string name : Version, version string : 20C
23:48:58:935: Registry key SOFTWARE\Intel\SOCPackageInfo does not exist or can not be read. Error : Unable to read registry value : VersionNumber - Error Code : 2. Assuming the installed version is oldest. Proceeding with installation.
23:48:58:935: E Win32 exception occurred!!
23:48:58:951: Error code: 0x4E24 (20004)
23:48:58:951: Error text: ''
23:48:58:966: Extended error text: 'Error in device matching'
23:48:58:966: Debug info: 'Setup.cpp (1267)'
23:48:58:982: Reading config file : C:\Users\martin\Downloads\IO Drivers_Intel_603.9600.1948.29470_W81x64_A(1)\IO Drivers_Intel_603.9600.1948.29470_W81x64\Config.xml
23:48:58:982: /Configuration/TitleOverride section in the configuration file is either missing or contains no data. Skipping version title override.
23:48:59:013: Showing dialog: FINISH

Accepted answers

All comments

philetus

I don't understand why you think something that's not working in Legacy 8.1 must be possible because it works in ubuntu 14.04 linux in legacy bios mode.

leechpool

Hi Philetus,

I'd be the first to admit I know little of the internal details of the different boot modes and what they actual mean so I could well be wrong. I was simply trying to look at it from a high level in terms of what seems logical and likely.

My thoughts were that I could understand that booting with UEFI firmware or legacy firmware could result in different resources being available. Such a difference could mean that while touch advance was available in UEFI mode, it was not available in legacy bios mode. I assumed that because ubuntu linux could access the necessary resources to use the touch pad in advanced mode if the unit is booted via legacy bios then the resources must be available in legacy bios mode and therefore it becomes a purely driver/software etc. issue divorced from hardware resources....I concluded that there was therefore no technical reason that Windows 8.1 could not operate the touchpad in advance mode assuming the necessary drivers/software etc. was available and configured correctly.

Thanks

Smiley Happy

philetus

I imagine in Linux, someone wanted to do something that needed this and wrote their own driver for it that works in Linux and was accepted into the Linux architecture.

Regardless of converting EUFI to MBR and whatver else youre doing, the 8.1 touchpad driver is buggy and if it works correctly for you in EUFI, count yourself lucky.

On another note, I read where someone converted their EUFI to MBR and rendered their laptop totally unbootable, with no access to anything so, be careful.

uNdEmBle

I have similar inquiry. I degraded ES1-311 from preinstaled W8.1 to version W7 and some of drivers did not install, saying that platform is not correct. W7 installed mainly, because I did not use W8 that much, secondly I thought, touchpad functioning will improve.

On Acer support site, supported driver for download are just for platform W8.1. Any knowledge on compatibility of those drivers with W7? Will some functions be impaired, if w8.1 drivers installed on W7 platform?

Quick Links

Top Members

Weekly

Puraw 220

StevenGen 100

poooooooooop69 60

GR08 57

Dimm 45

Swift Series Intel^® Evo™

Game Pass

Acer Corner

Gaming on Chromebook

Swift Series Intel® Evo™

Game Pass

Acer Corner

Gaming on Chromebook

Swift Series Intel^® Evo™