From: "Alex Taylor"    
      
   On Fri, 19 Nov 2010 22:53:39 UTC, piesse  wrote:   
      
   Try the slimmed-down PPD file I sent you first.  If you still get this   
   trap, we can proceed to the next step to try and analyze it.  (See    
   below.)   
      
   OR, you can just take James's suggestion and use the existing OS/2   
   2300PS driver.   
      
      
   BTW, you shouldn't need to use CUPS in either case.  According to the   
   printer specs, it's a native PostScript printer, so you can just use   
   the OS/2 PSCRIPT driver (once you get the PPD imported; or even not, if   
   you use the 2300 driver as above).   
      
   If you do use CUPS, support should already be included in the HPLIP   
   package.  I thought Paul S. provided a prebuilt ECUPS driver which    
   included all the HPLIP PPDs... I suggest you post on the eCUPS list   
   and ask him about it.   
      
      
   > 11-19-2010  23:10:48  SYS3175  PID 0169  TID 0001  Slot 0106   
   > H:\OFFICE51\SOFFICE.EXE   
   > c0000005   
   > 1493735f   
   > P1=00000001  P2=00000007  P3=XXXXXXXX  P4=XXXXXXXX   
   > EAX=00000000  EBX=0007c3b4  ECX=010bd9c8  EDX=00000007   
   > ESI=197fc7e0  EDI=010bd9e3   
   > DS=0053  DSACC=d0f3  DSLIM=5fffffff   
   > ES=0053  ESACC=d0f3  ESLIM=5fffffff   
   > FS=150b  FSACC=00f3  FSLIM=00000030   
   > GS=0000  GSACC=****  GSLIM=********   
   > CS:EIP=005b:1493735f  CSACC=d0df  CSLIM=5fffffff   
   > SS:ESP=0053:0007bfd8  SSACC=d0f3  SSLIM=5fffffff   
   > EBP=0007c248  FLG=00010202   
   >    
   > PSCRIPT.DRV 0001:0001735f   
      
      
   I'm not much good at interpreting trap screens, but if you take a   
   process dump I might be able to help you with some simple analysis.   
      
   Run:   
   procdump on /l:c:\tmp  <-- or some other directory with lots of space   
      
   before trying to print.  When the trap occurs, you should get a file   
   PDUMP.000 in the specified directory.  (Then run 'procdump off' to   
   disable dumping again.)   
      
   Assuming the PM Dump Facility is properly configured on your system   
   (can be a big if, I grant you), then do the following:   
    * Copy \os2\dll\pscript\pscript.sym to the \os2\pdpsi\pmdf\warp45   
      directory (asssuming you're running a W4 kernel).   
    * Open the PM Dump Facility from the Troubleshooting folder (may be   
      located in any of various locations on your desktop).   
    * Choose File --> Open Dump File and select PDUMP.000    
    * Choose Analyze --> Synopses --> Trap Screen Info   
    * Choose Analyze --> Thread --> Ring 3/Stack Trace   
    * Choose File --> Save Output and then post the contents of the   
      resulting file here.   
      
   If you have trouble with that, see    
     http://home.earthlink.net/~steve53/os2diags/ProcDumpRef.txt   
   for more tips on setting up PMDF.   
      
   --    
   Alex Taylor   
   Fukushima, Japan   
   http://www.socis.ca/~ataylo00   
      
   Please take off hat when replying.   
      
   --- Internet Rex 2.31   
    * Origin: Newscene Usenet News Service, http://www.newscene.co (1:261/20.999)