|
|
I am installing Object Desktop v1.5 or Professional v1.5, and I receive an EPFIE187 Error, cannot create object. What should I do? |
 |
1) The installation program cannot find its supported files.
2) If you are running Warp 3.0, pre fixpack 20, you maybe be running into an OS/2 limitation of the Class Table size. |
 |
1) Make sure that you have a .; as the first entry in your CONFIG.SYS in your PATH & LIBPATH lines. And then try reinstall again.
Example: SET PATH=.;C:\OS2;..........C:\OBJDESK; 2) Install FP20 or greater and reinstall Object Desktop. |
|
|
I installed Object Desktop v1.5, and I received an EPFIE178 Error, cannot exit exec routine? What should I do? |
|
You could be installing over/after and older version of Object Desktop and the installation is unable to overwrite the old class. |
|
You need to remove the old Object Desktop classes by running the following Rexx Utility,OBJDRMOV, from an OS/2 command line from within the OBJDESK directory. |
|
|
I tried to install FixKit#1 for ODv1.5 and received a difference error in the file OBJDCOMM.DLL, the file is not the proper version! Now What do I do? |
|
Our first manufacturing run of Object Desktop v1.5 was a slightly different build from our Mass production and this difference was not taken into account when FixKit1 was developed. |
|
You need to download and apply PrepFix1 before applying FixKit1. |
|
|
I tried to install FixKit#2 for ODv1.5 and received a difference error in the file OBJDONAV.DLL, the file is not the proper version? |
|
Object Desktop must be at the the v1.5.1 level before installing. Also, an internal fixkit1 was accidently released to the public which does not have the corrected OBJDONAV.DLL. |
|
If you are at v1.5.0 you must first apply FixKit#1. Otherwise apply PrepFix#2 before applying FixKit#2. |
|
|
The installation program hangs while process either bitmaps or icons? |
|
1) Your OS/2 Boot drive may not have enough disk space. 2) An internal error is trapping causing the installation to lock up.
|
|
1) Free some hard drive space from your OS/2 boot drive. 2) You may need to manually install the bitmaps by unpacking the file BITMAP.___ into the \OS2\BITMAP directory. |
|
|
I am running Warp v4, and just installed Object Desktop, rebooted, and my desktop has hung? What happened? |
|
The Control Center's CPU Meter is conflicting with OS/2's Pulse Meter on the Warp Center. |
|
Boot to a command line prompt and remove WARPCENTER from the AUTOSTART line in your CONFIG.SYS file until you are able to reconfigure your system so that you only have one CPU Meter running. |
|
|
I have the Demo of Object Desktop/Professional, do I need to Unistall the Demo before installing the registered version? |
|
It is recommended that you Uninstall the Demo before Installing the Registered Version. It is possible to install the registered version over top of the Demo but it is possible that the new class registrations may not take place properly which could lead to problems. So becuase of this an Uninstall is recommended. And a reboot before Installing the Registered version is a MUST. |
© 1996-2000 by Stardock Systems, Inc. All rights reserved. Last modified on 02.22.00