Just read the manual: admin guide ;-)

You can use the following switches with DeployAnywhere:
/logPth
that specifies the fully qualified path where the DA log files are written.

F:
CD GHOST
ghdplyAw32.exe /target=c:\Windows /ddb=\DriversDB /eval


(F: is the express share folder)
Notice: this was not running from XP machine or Windows7, (entry point error)
All the same I copy the SMEUTIL.SYS under c:/Windows/system32/drivers

Must boot using WinPE 2.1, for this wokring :-(

Hi, use this script to make log files

F:
CD GHOST
ghdplyAw32.exe /target=c:\Windows /ddb=\DriversDB /debug

I also have the same configuration as you! I found that during a deployment using the DA, both of the drivers are well recognized and sometimes not.
All computers are Dell. I integrated the SATA drivers Intel Matrix Storage (for AHCI mode) and the SATA drivers Intel Rapid Restore Technology (IRRT) from Intel.
On a roll of twenty or a PC, it happens 2 displays a blue screen.
Once a time I need to re-create the Image File !

Sometimes, drivers are not injected the latest versions. This is the case of network drivers from Intel. On an Optiplex 755, it recognized the driver and not installed a 2010 version 15.2 from Intel. It use an old version.

I made a backup of the file "DriversDB". I open my DS and launches deployAnywhere. I analyze the network drivers and mass storage manufacturer whose ID is the same and I delete them (by deleting the corresponding folder of the driver) and keep the latest version.
After deleting some drivers' folders, restart the console DA reindex all drivers.
For example : I delete all Drivers from Intel (ID vender 0x8086) I put the last version.

Since I have not had any problems.

The only problem I met now is a time of loading Windows XP after authentication abnormally long in a domain.
It take sometime more than 30 seconds to 3 minutes after authentification Windows if it was on network or not !...

I use the same scripts as you !

@echo off

REM Inject Hal, Nic and Storage Drivers with DeployAnywhere
echo Injecter librairie HAL, Reseau et Media de masse
echo avec Altiris DeployAnywhere
echo.
del %SystemRoot%\inf\atrsdfw.inf
copy %ALTIRIS_SHARE%\Ghost\SMEUTIL.SYS %SystemRoot%\system32\drivers
%ALTIRIS_SHARE%
cd\Ghost
GhDplyAw32.exe /target=c:\windows /ddb=%ALTIRIS_SHARE%\driversdb
cd\

exit 0
 

Aware: options are case sensitive... No I don't joke, they are: see here: http://service1.symantec.com/SUPPORT/on-technology.nsf/293a5302ae81e39288256ebb0049cfe7/2cf0e515ed142c3987257552005c615d?OpenDocument

"
DeployAnywhere (DA) command line switches:
/target
/ddb
/eval
/managed
/debug
/logPath
/logId
/findactivewindows
/capturesupportinfo

/managed

• Outputs missing driver information to driver_list.txt in DAs CWD
  Cannot be used with both /eval and /debug but can be used with either
  In GSS 2.5 this switch is used to run DA from the Ghost console

  Example output:
  {
  v=0×8086 [vendor]
  d=0×10BD [device]
  s=0×02111028 [subsystem]
  r=02 [revision]
  o=XP [OS]
  m=Y [mandatory – always Y for critical devices]
  i= type = RETARGET_NETWORK_DEVICE PCI ID = PCI\VEN_8086&DEV_10BD&SUBSYS_02111028&REV_02 Desc = @oem36.inf,%e10bdnc.devicedesc%;Intel® 82566DM-2 Gigabit Network Connection [the information in a more presentable format]
  t=N [type N==network, S==storage]
  }

"
Also those options for advanced logs option...
"
/debug

• Produces very verbose logging to GhDplyAw32.txt. By default this file is in the current working directory and it is overwritten each time it is created. each time it is created.
  Note:
  * The file is overwritten
  * Is never deleted by DA

/logPath

• /logPath=<fully qualified path to where the DA log files will be written>
  The path to ghdplyaw32.txt and driver_list.txt are affected by this parameter.
  May be used with /logId

/logId

/logId=<string which will be prepended to the log file names>

The names of ghdplyaw32.txt and driver_list.txt are affected by this parameter.
May be used with /logPath
"
/findactivewindows
This switch is used to locate the drive letter that Windows is installed on
"
sounds nice but how can I use this ???

I see in /debug the error:
The HAL type could not be determined for this system

also

F:\Ghost>ghdplyAw32.exe /target=c:\Windows /ddb=\DriversDB /managed

Using Driver Database = F:\DriversDB
Target OS = XP
Target = C:\windows
Retargeting...

I add the EVAL with debug mode, and also TARGET running in debug mode.

I add the EVAL with debug mode, and also TARGET running in debug mode.

So this week , I'm fed up ! My DS Server crashed due to SQL Server :'(

I reinstall all DS 6.9 SP4 and made some tests with DeployAnywhere.
You right, I have the same issue with "The HAL type could not be determined for this system.".

But no problem for the deployment because I reinject the HAL and computer work fine.

Pascal, I think that you need to open a ticket to Symantec.