Postscript files being printed as text

[Anonymous]

Anonymous wrote:
> I have a similar issue with printing after a clean install of FC-3.   The diff is that printing works great from any application on the cups server, but when attempting from a WinXP machine via samba, the postscript is printed rather then the rendering of the postscript.
>
> A side issue that the cups drivers for windows brings up an error window when attempting to go to [Printing Preferences...] that looks like the dll crashed.  It has the error:
>
> Function address 0x6a90450e caused a protection fault. (exception code 0xc0000005) Some or all property page(s) may not be displayed.

No solutions, I'm afraid, but I find myself in the exact same situation with an HP psc 2400 series printer and a slightly different function address (e.g. 0x6064a0db).  Here are my particulars s/w rev's as well as a "getdriver" dump which matches quite well with a working WinXP Printer Test Page:

# rpm -qa|grep -E "cups|samba"
libgnomecups-0.1.12-5
system-config-samba-1.2.22-0.fc3.1
samba-3.0.10-1.fc3
cups-libs-1.1.22-0.rc1.8.2
cups-1.1.22-0.rc1.8.2
hal-cups-utils-0.5.2-8
samba-common-3.0.10-1.fc3
cups-devel-1.1.22-0.rc1.8.2
samba-client-3.0.10-1.fc3

#
# rpcclient -Umyuser%mypasswd -c 'getdriver hp 3' localhost
Connecting to 127.0.0.1 at port 445
Doing spnego session setup (blob length=58)
got OID=1 3 6 1 4 1 311 2 2 10
got principal=NONE
Got challenge flags:
Got NTLMSSP neg_flags=0x608b0215
NTLMSSP: Set final flags:
Got NTLMSSP neg_flags=0x60080215
NTLMSSP Sign/Seal - Initialising with flags:
Got NTLMSSP neg_flags=0x60080215
lsa_io_sec_qos: length c does not match size 8

[Windows NT x86]
Printer Driver Info 3:
        Version: [3]
        Driver Name: [hp psc 2400 series]
        Architecture: [Windows NT x86]
        Driver Path: [\\LOCALHOST\print$\W32X86\3\hpz2ku09.dll]
        Datafile: [\\LOCALHOST\print$\W32X86\3\hpop2409.dat]
        Configfile: [\\LOCALHOST\print$\W32X86\3\hpzpm309.dll]
        Helpfile: [\\LOCALHOST\print$\W32X86\3\hpfmom09.hlp]

        Dependentfiles: [\\LOCALHOST\print$\W32X86\3\hpzvip09.dll]
        Dependentfiles: [\\LOCALHOST\print$\W32X86\3\hpztbx09.exe]
        Dependentfiles: [\\LOCALHOST\print$\W32X86\3\hpztbu09.exe]
        Dependentfiles: [\\LOCALHOST\print$\W32X86\3\hpztbi09.dll]
        Dependentfiles: [\\LOCALHOST\print$\W32X86\3\hpzstw09.exe]
        Dependentfiles: [\\LOCALHOST\print$\W32X86\3\hpzstc09.exe]
        Dependentfiles: [\\LOCALHOST\print$\W32X86\3\hpzsnt09.dll]
        Dependentfiles: [\\LOCALHOST\print$\W32X86\3\hpzslk09.dll]
        Dependentfiles: [\\LOCALHOST\print$\W32X86\3\hpzrm309.dll]
        Dependentfiles: [\\LOCALHOST\print$\W32X86\3\hpzres09.dll]
        Dependentfiles: [\\LOCALHOST\print$\W32X86\3\hpzrer09.dll]
        Dependentfiles: [\\LOCALHOST\print$\W32X86\3\hpzr3209.dll]
        Dependentfiles: [\\LOCALHOST\print$\W32X86\3\hpzpre09.exe]
        Dependentfiles: [\\LOCALHOST\print$\W32X86\3\hpzlnt09.dll]
        Dependentfiles: [\\LOCALHOST\print$\W32X86\3\hpzjui09.dll]
        Dependentfiles: [\\LOCALHOST\print$\W32X86\3\hpzime09.dll]
        Dependentfiles: [\\LOCALHOST\print$\W32X86\3\hpzimc09.dll]
        Dependentfiles: [\\LOCALHOST\print$\W32X86\3\hpzflt09.dll]
        Dependentfiles: [\\LOCALHOST\print$\W32X86\3\hpzeng09.exe]
        Dependentfiles: [\\LOCALHOST\print$\W32X86\3\hpzcon09.dll]
        Dependentfiles: [\\LOCALHOST\print$\W32X86\3\hpzcoi09.dll]
        Dependentfiles: [\\LOCALHOST\print$\W32X86\3\hpzcfg09.exe]
        Dependentfiles: [\\LOCALHOST\print$\W32X86\3\hpofax08.dll]
        Dependentfiles: [\\LOCALHOST\print$\W32X86\3\hpof2409.dat]

        Monitorname: [hpzlnt09]
        Defaultdatatype: [RAW]

Perhaps this additional info might help someone wiser than I to determine what the problem is that both of us our experiencing?

Thanks in advance,

       == ken ==