|
|
I have FixPack 17 installed and my system keeps crashing when using Seamless Windows sessions and switching between virtual desktops. |
 |
FixPack 16 through FixPack 18 induced a bug with Multiple Window Positions. |
 |
To work around this problem either install the most recent FixPack or add the following line in your config.sys: |
|
|
When I restart the WPS with Process Commander, or the WPS crashes and restarts, the Control Center and Tab LaunchPad do not automatically start up. |
|
When the WorkPlace Shell restarts it does not run Auto-Start-Able (Such as the Startup Folder) folders that are embedded within other forders. |
|
Place a shadow of Object Desktops Master Setup (V1.5 or higher) on the desktop. |
|
|
The Control Center will not activate when I move the mouse to its Hot Spot. |
|
When the Hot Spot's are set to be either the Upper Right Hand corner or the Upper Left Hand corner, and a windows Title Bar (Or maximized) is covering the top of the screen, this problem occurs. This was broken with v1.5. |
|
We have not fixed this problem yet, but you can get around the problem by changing your hot spot to the TOP, or by moving a window so its title bar does not touch the top of the screen. |
|
|
I get sys0039, CD-ROM Drive not ready error during bootup, how do I get this error to go away? |
|
The Control Center needs to look at the system's resource to find out which Drives are available, in order to display the information for the Available Drives on the system. Upon doing this Object Desktop uses a standard API call to "wake up" the Drives Folder. At this point, for some reason, if there is not a CD in the CD-Rom Drive, or if the CD is a Music CD, this error will occur. |
|
We have not been able to solve this problem at this time but you can either make sure that you have a program
CD in the drive when you boot up, or you can suppress the error message by placing the following line in your
config.sys:
AUTOFAIL=YES |
|
|
The Cascading Menus will sometimes have the word "Name" in place of the objects title? |
|
The problem is an incompatability with NPS WPS's Extension Sort option. |
|
You may be able to get the two to work together by trying to alter the order in which they load.
We are not sure at this time which needs to load first so it may take some experimenting on your part.
Or you could load the Control Center manually after the system has booted and that should
be able to work that way.
Or you could simply disable the Extension Sort feature of NPS WPS. |
|
|
The Control Center will not autostart even though I have it checked in the Master Setup, whats wrong? |
|
There could be one of two problems.
1) The Control Center's Object ID has changed, which is needed to be a specific value in order for the AutoStart routine to work. 2) It is possible that your Master Setup is no longer the active Master Setup on your system, instead it is possible that a Master Setup Object that resides in your Archives (\OS2\ARCHIVES\...) may have become the active Master Setup. |
|
1) Follow these Instructions to correct the Object ID for the Control Center:
a) Using Object Package, tear off a template from the Object Package Template. b) Drop the Control Center object onto the new Object Package file c) Double Click on the Object Package file to open it. d) With in the Object Package window click on the Control Center object e) In the Object ID field check to see if the object id is f) If is not, edit the Object ID to be OBJD_CONTROLCENTER (Include <> Brackets around OBJD_CONTROLCENTER)
g) Go into the file menu and save the changes
h) Close the Object Package file
i) Right click on the Object Package file and chose restore contents
j) You will be prompted with a dialog that says this Object Exist what do you
want to do. First, turn of the check box 'Continue Prompting', then click on the button to UPDATE.
This process will update your Control Center to have the correct Object ID and should now AutoStart.
2)
This one is a little more Tricky. It may take a bit of experimenting to get the correct solution. On your Boot Drive, in your
\OS2\ARCHIVES directory you will find several directories:
\OS2\ARCHIVES\CURRENT
\OS2\ARCHIVES\0X
\OS2\ARCHIVES\01
\OS2\ARCHIVES\02 (etc etc etc)
These directories contain backups of your Desktop. You will need to navigate into these directories(Desktops) and locate
the Object Desktop Folder within and locate the Object Desktop Master Setup. Open the settings for this Master Setup and
turn on the AutoStart option for the Control Center. Now reboot your system and see if the Control Center starts. Now you
will want to repeat this process for each Master Setup until you have found the Master Setup object in question. Once
you have found the Active Master Setup my best solution is to remove this Master Setup from your system by deleting the Object Desktop Folder that contains this Active
Master Setup. After deleting the folder, reboot and test your system. The Master Setup on your Real Desktop should now be the Active object and should work
as desired. Since you have deleted your Object Desktop folder from the Archives, you may no longer have the ability to recover the Object Desktop
folder in case of a problem. So it is recommended that you use Object Package to store a copy of your Object Destop Folder and/or your desktop and
save that package file in a safe location.
|
© 1996-2000 by Stardock Systems, Inc. All rights reserved. Last modified on 02.22.00