I just wrote this to the support of Curious Labs: I have a problem with Poser 5: Since i've installed the SR1 patch (which i've downloaded about 1 hour ago) i can't start Poser 5. It crashes my system with a bluescreen error "0E:018F:BFF6C172" - whatever this might be. I can't even leave Poser 5 or make a software reset. I have to reboot the hardware using the reset-key. I tried several times but always with the same effect. My PC is a "Dell Dimension 4100" running with Windows ME. (DELL Dimension 4100 with a 1000 MHz Intel PIII Processor and 384 MB RAM, 32 MB NVIDIA GeForce 2 GTS, 80 Gig Harddrive) It ran in a very stable way up to this moment - i hardly ever had a bluesreen before. How can this be fixed - and until there is a fix for this problem: How can i get rid of the patch and use the unpatched version which worked fine on my PC?

If you haven't switched it off, you should have a System Restore point that will allow you to go back to the time prior to the patch install. So this way you can unpatch your Poser 5 :o)

THX for the hint - i have a "point of return" from yesterday (3rd of October) and i've tried that recovery already but no effect. I think it recovers only the system itself but not installed software? Anyway - it didn't work and i'm still looking for a solution.

Same problem here. Just downloaded and applied patch. Too late. I'll have to uninstall entirely.

In between i've tried to completely deinstall Poser 5 and reinstall it from the CD. The de- and re-installation process worked without problems - but the software doesn't work anyway. I still get the same exception error as before. So i think the patch has changed something in my system directory?

I emailed CL and asked (begged) them to send out a mass-email when the product is fixed, really fixed. Gotta make a living now... reality strikes hard.

Same here. It looks like a lot of people with Windows ME are having the same problem. I did a restore from yesterday morning and things went back to the way they were.

Any of your on Win2k? I'm almost scare to try this patch now.

Hiya,

same here: got P5 today, installed it, started it: fine, no errors - just run nicely.

Downloaded the patches, installed them, started P5 and got this screen (see attached image).

I have WindowsXP Professional, AMD 2000XP, 1.6GHZ, 80 MB Harddrive, 512MB RAM.

Just clicked ok two times to get rid of this error message and had not to reboot my PC.

Uninstalled P5 and reinstalled everything from CD, started P5: fine.

Installed the Poser5SR1App.exe (the small patch with ~ 11MB) first. Rebooted my PC, started P5, got the error message again.

Ohhhh, nice patch LOL.

Ehhhhh... this should read 80 GB Harddrive ....

(0E): Page Fault The Page Fault interrupt allows the operating system to recover small code segments from temporary storage on your hard disk that were put there when electronic memory (RAM) resources started to get low. An interrupt 14 (0E) is usually issued whenever an application goes looking for a piece of itself in RAM and cannot find it. The operating system usually retrieves the missing page of code from your hard drive, then re-issues the instruction that caused the fault. If successful, the error goes away and you never see it (it all happens very quickly). A page fault you do see occurs when the retrieve attempt fails, or data retrieved is invalid, or the code that issued the fault tried to access a portion of memory in use by another process. In these cases the operating system takes over for the appropriate action (the Blue Screen of Death, normally). A common cause is faulty drivers or corrupt Windows DLLs files. There is a large amount of information on the Microsoft Web Site about potential blue screen problems.

Norbert, THX for this information. I think it's interesting that the unpatched software could handle that (and by the way any other software i have installed on this PC can handle it too) while the patched software can't. I don't think that it's a problem of my machine or anybody else's machine. It simply occurs due to a lack of proper programming and testing.

.

This weekend I'm going to scorch the hard-drive and install XP Professional. Then I'm going to install P4 and Pro Pak. Then I'll install P5 and have a dedicated machine. If it fails on the SR-1 install there will be nobody to blame but the OS and P5. No, I'm not going to install the XP patch... not yet. Drastic measures by a Poser addict. Once you've tasted P5 the habit can't be broken.

You know I've been thinking that all day, ever since I saw an earlier post this morning... I'll bet it's Interlok (the antipiracy software) which contains within it's code the power to arbitrarily reboot your machine if it thinks your trying to to circumvent it. (throw "tpkd.sys" or "tpkd.vxd" into google and see for yourself) Some bloke using some music software had many of the same problems. Now that would be ironic... Perhaps the program as written by CL funtions perfectly, but the anti-piracy stuff is what's killing everyone's machine :P CL people: Just out of interest, what happens if I should install, say Adobe's Ebook reader software, (which also comes with Interlok) will that hose the protection, os it Interlok smart enough to realise the drivers are newer? (assuming they are newer of course) later jb

From Larry Weinberg; "It seems there are two or three people with your same problem. We'd like to try and determine what it is. Attached is the older Interlok system driver for Windows 98 and Me that may fix your problem. Please let us know if it does. Make a backup copy of the newer driver that has been installed in your windowssystem folder. (Tpkd.vxd) Unzip this file and place the Tpkd.vxd file in your windowssystem folder. YOU MUST THEN REBOOT your system. Then try Poser again. If this works, please let us know immediately! Sorry about the problems." ------------------------------------------------------------------- Tried the above and it didn't work.. same blue screen. ------------------------------------------------------------------- Larry Weinberg wrote; "The other person who had your problem was helped by using the old driver. That person was on Windows ME. Is it possible that you may need to update your Windows 98 operating system to the latest service updates ? We have not had these problems on Windows 2000 or Windows XP or on our Windows 98 machines. It is possible that a special virus checker could be conflicting with the Interlok driver. Also, there have been some cases that an HP printer driver can be the cause of conflict. Thanks for the positive thoughts. Hopefully we can find the cause of this quickly." ------------------------------------------------------------------- I uninstalled P5 again and made sure that the older driver was installed... Don't know the date on the driver that I started out with before installing the patch. Should check Microsoft for any 98SE updates (can't imagine that there are any but..) Now P5 runs again... no patch installed.

Puntomaus: You didn't install the crack did you? The error you are getting has only been seen when installing the patch over the cracked version of P5.

krazik, I got my copy of P5 today directly from Egisys and I haven't registered it so far. I downloaded the patches, installed my P5, installed the patches, uninstalled P5, reinstalled and so on. It works perfect with just the figure fix but not with the other fix. And I just called Egisys and told them about this error message and send them the screenshot.

Maybe in the future you will think about what you are writing or what you are accusing other people of BEFORE you write it down.

But maybe you just wanted to tell us about your experiences with your cracked programm, huh?

Can you try registering your P5 from the CD then installing the patch. My experiences with the crack? I work for Curious Labs.

No one is accusing anyone here. We need to put this information out so honest people don't run into problems. If the known crack is ever installed -- even just to check out the application -- it will cause problems that may permanently disable the ability for Interlok to run correctly on that system until the disk is reformatted completely. We have experienced this when trying to use our patch on the known crack. I'm sure you purchased your copy of Poser if you say you did. The screen shown here is exactly what we saw on a machine that once had the crack installed.

Puntomaus, maybe the problem is because you didn't register? I don't see why that should make a difference, but maybe...?

The problem is fixed for me so far. Curious Labs support mailed me an older version of Tpkd.vxd, copied it to my system directory, rebootet - bingo: The "bluescreen of death" is gone. Thank you Curious Labs! By the way - i have a virus scanner and a hp-printer-driver running. It works anyway now. THX Larry...

By the way: What is an Interlok driver or what does it do?

No, I have not registered it yet. I thought I register when I have everything installed and everything works fine. But if you think that this could be the problem I will try the other way. Just sent out an email to CL with my Serial Number and challenge code and will try to install the patch again when I recieve the response code.

Sorry, krazik, but I did not know that you work for CL. I was just rather angry that someone could think I use cracked software :-(.

Just so you know, we are investigating with Pace now to find out why the old Interlok copy protection drivers may work better than the new drivers for some Win 98 and Me. It again may be incompatibility with some Hp printer drivers. Registering first before installing the current SR1 may help. I had you install the old tkpd file, but forgot the ilinet.dll to go with it. So that may explain this blue screen if it wanted to register. We'll verify here and post the old drivers in a complete form.

Yay, everything runs fine now. Registered P5, installed the patches and no error message anymore :-)))).

Puntomaus
doing happy dance now

OK, so... Reading between the lines. If you haven't registered yet, then Interlok hasn't written out it's control block. (It doesn't use the OS, it writes direct to the disk itself) But if you install the crack, then that may hinder Interlok from ever functioning properly until you reformat. Which would imply that the crack has found a way to either disable Interlok's ability to write to disk, (presumably by masking the interrupt or something) or it's actively faking the control block, (and the patch is tripping over that) or it's write protecting the portion of the disk that Interlok is trying to use, perhaps by filling it with fake data. Interesting :) Though before anyone starts pointing the finger, I have an Egi.Sys paper reciept, and a valid challenge response to prove that I actually paid for my version of P5 :) Just out of interest, (he says dubiously :) what happens if you authorise, Interlok writes out it's block, then you use the crack, can you get the patch to run then? I'd volunteer, but I'd have to find the crack first :P later jb

Congrats, Puntomaus. I'm glad that did the trick.:)

On your OE crash, out of curiosity, do you have either Norton or some version of Easy CD creator (be it adaptec or roxio). If you have the latter, try uninstalling it and rerunning your patch. If that helps, then never ever go back to the cd program (try nero instead).

That's right folks, all you need is brand new PC,(preferably a Pentium 3/4, as we all know how dodgy those AMD chips are) with all the latest drivers, and a dedicated network connection, (how else are you going to access "content paradise") on which you only install the OS (plus every concievable patch), P5 and the patch(es) to minimise application conflicts. Yeah, that'll work! later jb

Fascinating. So you guys have gone from "it must be user inexperience, that's why it's glitching", to "you must be using the cracked version, that's why it's glitching.. "? Interesting approach for company PR. Best of luck with it. Maybe if it works out it'll catch on industrywide.

So since they have only seen those errors on cracked versions, and put that information out there and SPECIFICALLY didn't accuse anyone of anything.... You're still going to get bent out of shape because they told the truth about a technical issue while trying to help. shrugs clearly CL can't win here.

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