cannot install printer driver in XP Embedded

Question

 Hi guys.
I'm running out of ideas here.  i have XPE deployed image, using Sean Liming's XP Pro component with everything enabled and all possible printer support added but I cannot get certain printer drivers to install.  These include PDFCreator, which uses Ghostscript printer driver, and PDF995.  Not sure what the proper term for these drivers is but they let any app print its data into a pdf document.

Is there any way to log the install process so that I can pinpoint what's missing in my image?  This same isntaller installs no problem on my XP Pro.

When installing PDFCreator (www.pdfforge.org), I get the error 126 and the following error log:

Printerstatus before installing:
Spooler service: is running
Printermonitors [3]:
 Standard TCP/IP Port
 LPR Port
 Local Port

Printerports [9]:
 FILE:
 COM4:
 LPT3:
 LPT2:
 LPT1:
 COM3:
 COM2:
 COM1:
 IR

Printerdrivers (Windows 4.0) [0]:

Printerdrivers (Windows NT x86) [0]:

Printerdrivers (Windows x64) [0]:

Printerdrivers (Windows IA64) [0]:

Printerdrivers (Windows NT Alpha_AXP) [0]:

Printers [0]:

Printerdriver-Directory (Environment: Windows 4.0):
 Result: Success = C:\WINDOWS\System32\spool\DRIVERS\WIN40

Printerdriver-Directory (Environment: Windows NT x86):
 Result: Success = C:\WINDOWS\System32\spool\DRIVERS\W32X86

InstallMonitor:
 Monitorname : PDFCreator
 Environment : Windows NT x86
 Result: Success

Install printerport:
 Portname : PDFCreator:
 Result: Success

Install printerdriver for Win2kXP2k3 (32bit):
 Drivername : PDFCreator
 Environment : Windows NT x86
 Result: Error 126 = The specified module could not be found

InstallPrinter:
 Printername: PDFCreator
 Drivername : PDFCreator
 Portname   : PDFCreator:
 Result: Error 1797 = The printer driver is unknown

Printerstatus after installing:
Spooler service: is running
Printermonitors [4]:
 PDFCreator
 Standard TCP/IP Port
 LPR Port
 Local Port

Printerports [10]:
 PDFCreator:
 FILE:
 COM4:
 LPT3:
 LPT2:
 LPT1:
 COM3:
 COM2:
 COM1:
 IR

Printerdrivers (Windows 4.0) [0]:

Printerdrivers (Windows NT x86) [0]:

Printerdrivers (Windows x64) [0]:

Printerdrivers (Windows IA64) [0]:

Printerdrivers (Windows NT Alpha_AXP) [0]:

Printers [0]:

--------------------------------------

Windowsversion: 5.01.2600
WinDir: C:\WINDOWS
Win64: false
ProcessorArchitecture: X86
SystemDir: C:\WINDOWS\system32
TempDir: C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\
CurrentDir: C:\WINDOWS\system32
Computername: ULTRASON-4UFSKC
Username: Administrator
UILanguage: 1033
Internet Explorer version: 7.0.5730.11
Path: C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem
C:\WINDOWS\system32\Wbem\framedyn.dll: found
framedyn.dll: found in path
Environment:
ALLUSERSPROFILE=C:\Documents and Settings\All Users
APPDATA=C:\Documents and Settings\Administrator\Application Data
CommonProgramFiles=C:\Program Files\Common Files
COMPUTERNAME=ULTRASON-4UFSKC
ComSpec=C:\WINDOWS\system32\cmd.exe
DEVICEMODEL={00000000-0000-0000-0000-000000000000}
DEVICEROLE=0
HOMEDRIVE=C:
HOMEPATH=\Documents and Settings\Administrator
LOGONSERVER=\\ULTRASON-4UFSKC
NUMBER_OF_PROCESSORS=2
OS=Windows_NT
Path=C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem
PATHEXT=.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH
PROCESSOR_ARCHITECTURE=x86
PROCESSOR_IDENTIFIER=x86 Family 15 Model 107 Stepping 2, AuthenticAMD
PROCESSOR_LEVEL=15
PROCESSOR_REVISION=6b02
ProgramFiles=C:\Program Files
PROMPT=$p$g
RUNTIMEGUID={2A6C5522-0BF0-40C8-A2D6-F73240DE66A5}
RUNTIMEPID=J9KHQ-38HJ3-9CKJG-GFRB6-XMXDY
RUNTIMESKUCODE=XPeCli
SESSIONNAME=Console
SystemDrive=C:
SystemRoot=C:\WINDOWS
TEMP=C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp
TMP=C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp
USERDOMAIN=ULTRASON-4UFSKC
USERNAME=Administrator
USERPROFILE=C:\Documents and Settings\Administrator
WEBUILDDATE=1/30/2009 10:44:22 PM
windir=C:\WINDOWS

Answer 1

PDF generators are probably devices.  Setupapi.log tracks what gets installed so you might want to check this file. Are you using WES or XPe? If you are using WES, the full XPe pro- might not work since there are some component differences.

-Sean

---

www.sjjmicro.com / www.seanliming.com, Book Author - XP Embedded Advanced, XPe Supplemental Toolkit

Answer 2

I'm using XPe.
I checked setupapi.log but no mention about pdf stuff :(

any other suggestions?

Answer 3

I cannot even believe it but I fixed it.  It took me almost a week tracking down the problem on and off.  After doing exhaustive searches I noticed that there are many people having the same problem, mostly on XP Pro.  Common solution is an error in environment path to /system32\wbem folder and the virtual driver installer cannot locat framedyn.dll which is necessary for the driver to install. 

I just found out that framedyn.dll is not the only file necessary for this install.  srclient.dll must also reside in system32 for any virtual printer driver to install.  This file is included in "System Restore Core" component which was not part of my XPE image.


SOLUTION: srclient.dll to system32, framedyn.dll to system32\wbem, make sure system paths are pointing to these to locations