Package Builder doesn't work

Hi Everyone ,
I'm using IP 3.11.106 (x86), and in this build the package builder doesnn't seem to work. Anytime I'm trying to save a new package I get the message: "IP has detected a problem and has to be closed" . My system: WinXP, Intel Centrino Duo, ATI Mobility Radeon X1600, 1024 MB Ram, 100 GB HD. Maybe somebody has had similar problems or any idea what could be wrong?
Thank you very much!
Tintin

4,679 views 6 replies
Reply #1 Top
Hello Tintin67,

I will send this to our technical support department and they will get back with you as soon as possible.

Thanks,
Jenny
Reply #2 Top
LOL. I *saw* Package Builder but *read* Object Package and thought, "Good God, no one can be using that any more and expect support."

Thanks for the memories:

OD1.5 for OS/2

Possibly the most significant new feature of Object Desktop v1.5 is the Object Package. Object Packages are simply files that contain Workplace Shell objects--sort of like zip files except they can contain objects as well as normal files. They seem to work well and are quite simple to use. With Object Packages users have the potential to easily package folders or the entire desktop and quickly and easily share them with other users!


Reply #3 Top
Hello Jenny,
thank you very much!
Tintin
Reply #4 Top

: I have a few questions:

Do you have any XP service packs installed?

Does renaming iprepair.dll help the issue?

Do you have any security software installed?

Thanks!

-Mike
[Stardock Support]

Reply #5 Top
Hello Mike,

I have XP service pack 2 installed; my security software is:

Antivirus:
AntiVirenKit Pro (a german program working with 2 engines: "Kav" (Kaspersky, I think)- and "BD" (Bit Defender)

and AVG Free Edition

Firewall:
Agnitum Outpost Pro

And last but not least I have ad-aware SE and a-squared free installed.

What do you mean by renaming iprepair.dll? Am I supposed to rename this file??

Thank you very much,
Silke
Reply #6 Top

: Yes, I would suggest renaming this file to something else (ex. iprepair.dll.old). If renaming this file doesn't help, there might be a conflict with the security software you're running.

-Mike
[Stardock Support]