I guess they don't mention when updates come out to the cab files. the E6410 went from A00 to A02 pretty fast.. Looks like some fixes are out..

Here is the errors I get when I import all of the E6410 drivers into sccm. \\test\E6410-win7-A02-R269407\E6410\win7\x86\application\R257449\Filter Driver\stdfltn.inf - The selected file is not a valid Windows device driver.
\\test\E6410-win7-A02-R269407\E6410\win7\x86\controlpoint\R257550\Security Device Driver Pack\Dell PBA Device Driver\pbadrv.inf - The selected file is not a valid Windows device driver.

hey guys,

got this on a e6510 with A03 driver cab!
Error: Failed to import the following drivers:
\\sccm01\Drivers\DOWNLOAD\E6510-win7-A03-R277832\E6510\win7\x64\application\R257449\Filter Driver\stdfltn.inf - The selected file is not a valid Windows device driver.
\\sccm01\Drivers\DOWNLOAD\E6510-win7-A03-R277832\E6510\win7\x64\application\R257449\Sensor Driver\accelern.inf - The selected driver has already been imported at this site.

If i install a e6510 with my task sequence i've 1 unknown device in it..
is there any hint / fix available for this?


thanks,
ben

The stdfltn.inf file does not have support for Windows XP or later so ConfigMgr is skipping it. The second file isn't being imported because it sees one a duplicate in the driver store already. We try to ensure that all drivers get imported by adding a unique file to each driver so you don't have to track it down and add it to the package since duplicates will cause the import to fail.

You can either add a unique file to the folder that contains accelern.inf and attempt to re-import or you can find the copy of accelern.inf that exists in your driver store and add it to your driver package so it gets included.

hey guys,

not sure if this is the right place to post this, but I've also a problem with the drivers for the ST Microelectronics Freefall Sensor on our Latitude E6410 laptops (Windows XP SP3). I've added the files from the E6410 A03 driver cab to our sccm driver package (SCCM 2007). The drivers are applied during the staging task sequence, but i get the following device status when I've a look at the ST Micro Accelerometer device in the device manager after the installation:

"This device cannot find enough free resources that it can use. (Code 12)
If you want to use this device, you will need to disable one of the other devices on this system.
Click Troubleshoot to start the troubleshooter for this device."

Has anyone an idea how to fix this?

Thanks
Andreas

A number of the issues with the E6410 and XP are resolved if you are using a correct Uniprocessor or Multiprocessor HAL. Using an older HAL (usually introduced if you build your image on Virtual PC) will cause these problems.

Can you confirm that you are on a current HAL?

For the freefall sensor i added a software package with setup /s.
This works fine on a E4310 / E5510 and E6510

Warren,

I had to change the HAL to multiprocessor. Now the driver is working.

Thank you!!!

"Warren,

I had to change the HAL to multiprocessor. Now the driver is working.

Thank you!!!"

How did you change the hal to multiprocessor?

I'm also having problems with "Fiilter driver"

on a test machine i did the following:

I copied the three files (halmacpi.dll, ntkrnlmp.exe, and ntkrpamp.exe) from C:\WINDOWS\Driver Cache\i386\sp3.cab to c:\windows\system32, renaming them to hal.dll, ntoskrnl.exe, and ntkrnlpa.exe... respectively.

After a reboot I could install the filter driver without problems.

For the SCCM task sequences we a made script that sets the HAL to multiprocessor ACPI. But I had no time to test the script yet.