Get message of missing PCDLIB.DLL each time new user tries running our date-limited demo/trial on Win 2000 Professional. It is based on OI3.7.5 deployed single-user runtime, which has run fine many times before (but I don't think previously on Win 2000 Prof).

The system then seems to run OK but a DOS file in out startup routine doesn't seem to be being written (maybe unconnected).

First they got missing CTL3D.DLL - but this was cured by OI Client Install.

I see that PCDLIB.DLL resides in the OINSIGHT.EXE directory in the development system and nowhere else on the PC. It is not deployed to the OINSIGHT.EXE directory of any of our various deployments and we have never before had this message.

I have looked in the repository and cannot find it. I conclude it should not normally be required in a runtime system.

Can the gurus please tell me asap :-

1) What does PCDLIB.DLL do?

2) Why does Win 2000 Prof suddenly seem to need it when this and all our other deployments work fine without it on other Win versions?

3) Should I add a publishable repository entry so that it is deployed in future for any Win 2000 Prof users?

TIA

Tech Support…

Any ideas on this?

Your silence is deafening!

Richard

How are you deploying? PCDLib.Dll is used for displaying images according to the exported functions. We'd suggest adding it to whatever deployment schema you use.

The Sprezzatura Group

[i]Celebrate CeBIT with Sprezz Local![/i]

Richard-

PCDLIB, as Sprezz has written, is used by OI with regards to imaging.

It is also supplied with many other software packages, almost always imaging related- Kodak, Corel, etc. It may be that on this particular machine that a different version of the DLL is being loaded before OI's version gets loaded.

Have you tried looking on the machine to see if there is another version of the dll? Have you tried renaming it?

Changing your deployment definition shouldn't affect this.

Mike

Thanks, Mike & Sprezz

Originally deployed as single-user runtime via RDK and then copied via WinZip on CD-ROM (with our own encrypted date limit routine).

Funny thing is that it's been done quite a few times and this has never before happened.

Looking at this PC, there's a PCDLIB32.DLL in WINDOWS\SYSTEM and PCDLIB.DLL in the development copy of Open Insight. As before, no PCDLIB.DLL in the deployed runtimes.

Three questions :-

1) Is this necessary in a deployed runtime? If so why isn't it in the repository as publishable?

2) Why has this problem never before occurred when exactly the same procedure has been done lots of times before?

3) Has anyone else met this? I've searched this discussion forum and there seem to be no previous references to PCDLIB.DLL, let alone this sort of problem.

Any ideas?

Mike

I've looked at your reply again - and there are still questions unanswered.

PCDLIB.DLL is not anywhere else on my PC except in the oinsight.exe directory in the development copy.

The single user runtime deployment doesn't contain PCDLIB.DLL and we have deployed quite a few copies thus. It has always worked fine without it and I therefore assume that the deployed runtime doesn't normally need it. If that's wrong, then why don't you include it in the deployment spec and why haven't we met this problem before? Also why hasn't anyone else met it and reported it?

Is this soemthing to do with the way OI16 runs on Win 2000 Prof?

If I find anything from this end I'll report

Thanks

Enlightenment please …?

Three situations :-

1) As reported, missing PCDLIB.DLL with runtime system running locally on Win 2000 Prof (so user told me)

2) Network system - user just given new PC with Win2000 Prof. No error message reported.

3) Network system - one PC has NT and gives missing PCDLIB.DLL message but no other PCs (using Win 98) give message.

After OKing message the system runs fine with no PCDLIB.DLL anywhere in sight!

What's going on? Should we deploy PCDLIB.DLL just to stop risk of this harmless message appearing and worrying end users?

I think I would. Niggling error messages tend to confuse / upset users. I had a situation where a few Gateway boxes shipped with a stripped down version of Microsoft Office included with ME. It turned out that Microsoft was attempting to prevent users from installing Corel / Wordperfect products, so CTL3D was modified in Windows\System. Well OI 3.71 didn't like that at all. So .. in the create event of the app, we unload CTL3D and load the one that we ship (just-in-case strategy .. like yours). At exit, we re-load the one that was there. The problem of course is that it took quite a while to figger out what the problem was in the first place. Thank you Microsoft. I don't think I'll start my rant now .. although it is tempting .

Don

Don

Interesting re CTL3DV2, which is the one component which seems every now and then to be missing from Windows installations. At least OI Client Install sorts it - but Client Install doesn't fix the PCDLIB.DLL problem.

You also refer to Windows ME. One of our users found that every time the boss logged in to our OI app, everyone else's PCs logged into it froze at random.

One of our gurus in the UK asked if anyone was using ME (saying that he refused to talk to anyone using it, let alone visit them. On enquiring, it turned out the boss's PC was the only one using ME. It was swapped with his secretary's (running 98) and the problem disappeared.

Maybe a bit like the PCDLIB.DLL which seems to happen sometimes (but not always) with NT and Win2000 Prof.

Richard

View this thread on the forum...