Unsolved

This post is more than 5 years old

10 Posts

39183

October 4th, 2011 06:00

E6320 Driver Package XP

The driver package XP A01 for sccm doesn't works. THere is a driver problem that hang the pc on the first boot after deployed the operating system when it initialized the hardaware. Help please, the same procedure with Win7 is OK

4 Posts

October 5th, 2011 05:00

Whats the problem madilall? Do you mean the machine hangs during OSD at reboot after WinPE stage? What (if any) error messages are you getting?

1.1K Posts

October 5th, 2011 13:00

If it's a black-screen hang after mini-setup, that usually indicates a HAL issue with XP.

4 Posts

October 5th, 2011 14:00

As Warren says it could be a HAL issue...though if you're deploying XP how have you configured your BIOS? Are you deploying with the BIOS Storage option set to ATA without using the Mass Storage drivers?

10 Posts

October 6th, 2011 01:00

Black screen after mini setup. I tried with all sata/ATA setting witn the same result

4 Posts

October 6th, 2011 03:00

rather than being a driver issue it may be an issue with the task sequence itself...just a thought. Is it completing the mini-setup and applying your sysprep .ini etc and if so are you getting any on-screen message when the computer hangs? We had a similar issue when deploying XP to E-Series machines and it turned out that it wasn't driver related in the end...

If you're getting any on-screen error can you post it here.

October 6th, 2011 11:00

Mine is a similar case in E6320 Driver package for XP. Let me summarize:

1. I have my SATA Config as RAID on (Industry default) and I did the following changes in my TS after importing respective sata drivers to SCCM Console

Latitude Exx20 R291722 10.1.0.1008 RAID On Intel® ESB2 SATA RAID Controller Intel(R) Mobile Express Chipset SATA RAID Controller

But i still it have blue screen reboots.

As a cross check:

a. I have a HAL change script already on place, which does its jobs for all models - 15 including Dell lati E5400 and E5410.
b. All drivers packages are correctly distributed to DPs

2. If I change the SATA mode ATA

Here I am getting mini-setup screen with "Please Wait" freezing screen forever.

Abobve both situation happens where the

The TS logs tell, it was running "The task sequence engine performed a system reboot initiated by the action (Setup Windows And Configmgr) in the group winPE"

Thanks

October 6th, 2011 13:00

Is my problem due to AFHDD as per the below link

http://en.community.dell.com/dell-blogs/enterprise/b/tech-center/archive/2011/07/27/5-steps-to-prepare-your-deployment-process-for-advanced-format-af-hard-disk-drives.aspx

October 6th, 2011 13:00

How to check in my hardware whether it has AFHDD?

4 Posts

October 7th, 2011 01:00

Rakesh,

Have you injected the mass storage drivers in your XP wim also? I found that I was hitting problems before I included the E2B2 SATA controller in my OS image wim...I then apply the drivers in the TS between "Apply Network Settings" and "Setup windows and ConfigMgr".

Up until this point we were seeing HAL errors and the machines were hanging at various stages of setup...once we'd injected the drivers into the wim we've had successful deployments.

Zym

October 19th, 2011 04:00

Seems to be able to resolve the issue,

In sysprep.inf, if you have ExtendOemPartition =1 make to it 0.

Till do not know what can be the potential impact of this but it resolves all my issues with E6X20 based hardware I have.

Hope this solution help.

Thanks,

October 20th, 2011 07:00

Might be unrelated but I experienced an issue with Sysprep and the Accelerometer driver with the 6220. Using the 6420 Accelerometer driver fixed the issue... Looked like Windows wasn't able to start the driver service.

Cheers
No Events found!

Top