Attached Link: http://www.iseran.com/Win32/FAQ/except.html

Being serious for a moment, (I know, I know... :) weren't we told that if you'd updated anything, that the update/patch wouldn't touch that file? Added to this is that fact that if you've uncompressed the poses (no program data) you have to recompress them, which would imply it's the size and not the date that it's looking at as this would change once you've saved the recompressed poses back to disk. It may or may not retain the creation date though... Now assuming that the crack isn't a perfectly padded copy, one would assume that the internal code of the P5 executable has been "butchered" and the file size has changed, either a lot or a little. So how are they getiing the patch to apply to the crack? Me I figure it was either a shoe horn or "smoke and mirrors" YMMV However, some digging on the error above reveals the following: EXCEPTION_ACCESS_VIOLATION = C0000005 Many exception errors are not processed by applications. The most common exception error is EXCEPTION_ACCESS_VIOLATION (c0000005). It occurs when a pointer is dereferenced and the pointer points to inaccessible memory or a write operation is attempted on read-only memory. If an application does not trap an exception, the Win32 module, UnhandledExceptionFilter, will do one of the following: display a message box, invoke Dr. Watson, or attach your application to a debugger. The following are standard exception errors: EXCEPTION_ACCESS_VIOLATION EXCEPTION_ARRAY_BOUNDS_EXCEEDED EXCEPTION_BREAKPOINT EXCEPTION_DATATYPE_MISALIGNMENT EXCEPTION_FLT_DENORMAL_OPERAND EXCEPTION_FLT_DIVIDE_BY_ZERO EXCEPTION_FLT_INEXACT_RESULT EXCEPTION_FLT_INVALID_OPERATION EXCEPTION_FLT_OVERFLOW EXCEPTION_FLT_STACK_CHECK EXCEPTION_FLT_UNDERFLOW EXCEPTION_ILLEGAL_INSTRUCTION EXCEPTION_IN_PAGE_ERROR EXCEPTION_INT_DIVIDE_BY_ZERO EXCEPTION_INT_OVERFLOW EXCEPTION_INVALID_DISPOSITION EXCEPTION_NONCONTINUABLE_EXCEPTION EXCEPTION_PRIV_INSTRUCTION EXCEPTION_SINGLE_STEP EXCEPTION_STACK_OVERFLOW It's a very common programming error, not irrefutable evidence of wrongdoing on the part of the user, though the text at the top of the link is amusing :) Now the question is, if I a non-programmer can work this out, what can't the programmers at CL? Or is there consipracy in the air! [Dramatic chord!] and here was I thinking there was no life left in the beast... :) later jb