Hi Will,

PK> 11-28-1999  16:00:57  SYS3175  PID 6a3a  TID 0001  Slot 0054
PK> C:\MAX\SQAFIXP.EXE c0000005 000000c0 P1=00000001  P2=000000c0 
PK> P3=XXXXXXXX  P4=XXXXXXXX   EAX=00000003  EBX=0000d75c  ECX=00000000 
PK> EDX=00000000 ESI=00000004  EDI=0000868e   DS=0037  DSACC=00f3 
PK> DSLIM=0000ce5f   ES=002f  ESACC=00f3  ESLIM=000010d6   FS=150b 
PK> FSACC=00f3  FSLIM=00000030 GS=0000  GSACC=****  GSLIM=********
PK> CS:EIP=005b:000000c0  CSACC=d0df  CSLIM=1fffffff
PK> SS:ESP=0037:0000cd10  SSACC=00f3  SSLIM=0000ce5f EBP=0000ce3a 
PK> FLG=00012246 

 WH> Peter, that error is sys3175 - illegal memory access (AKA GPF ). 
 WH> Since the programs in question are all DOS vdm's I'd suggest looking at
 WH> the DOS settings on both machines, especially the memory settings. 

Ummm, I am not sure how you figured that one, but SQAFIXP is not a DOS App,
its an OS/2 Text mode executable. Here is the beginning of the file -

======================================================================
 00000000  MZZ.-...................@.......................................
 00000040  ........!..L.!This program cannot be run in DOS mode...$........
 00000080  NE.................>t|............@.p.p.{...(...................
 000000C0  ..I...J...B...B...............P...........0......sqafixp........
 00000100  .....msgapi.DOSCALLS.KBDCALLS.VIOCALLS...sqafixp.exe............
 00000140  ................................................................
 00000180  ................................................................
======================================================================

 WH> Obvious question: these appear to be rather old programs so did they
 WH> ever work on the machine that's crashing??

Yes, at least one of them ran ok on Warp 3 with no Fixpak, I have not tried
the other App until now so I cannot check that one. The only FP I have ever
applied to that machine was FP39. One executable is dated 1998, the other
1996. Is 1998 now considered "old"?.........;-)

For what its worth I run them in an OS/2 Window on all machines. I was hoping
this may be a known "problem" with FP39, but maybe not...

Cheers............pk.


--- Maximus/2 3.01