About GroupWare Support Center

Keystroke: F1

Purpose:

This option will give the Product Version, Product Release Date, Total Free Memory, Free GDI Resources, and Free USER Resorces.


Backup Private BIF

Keystroke: Ctrl+N

Purpose:

This option opens up a dialog box to allow you to specify the filename and location where it will create a backup copy of your Private BIF.

This is a useful feature if you are going to modify or delete entries in the Private BIF.  Press this option to create a backup copy of your Private BIF before you press the BIF Purge option.

See Also:

Purge BIF


Control Panel

Keystroke: F11

Purpose:

This option launches the Windows Control Panel program.  The Control Panel contains all sorts of information on how to configure Windows.

In Windows 3.1 you can access information about the Fonts, Desktop, Printers, 386 Enhanced, and various other programs that were installed to the Control Panel.

In Windows 95, you can access information about the Display, Fonts, Modems, Printers, System configuration, and various other programs that were installed to the Control Panel.


DOS Prompt

Keystroke: F10

Purpose:

This option will launch COMMAND.COM which will open a DOS prompt.

Some customers are more comfortable editing and searching for files at a DOS prompt.  This option gives them that access.

See Also:

System Configuration Editor


Edit Private BIF

Keystroke: Ctrl+E

Purpose:

This option will launch the BIFED20.EXE program and open the Private BIF.

This is a quick and easy way to edit your Private BIF.

See Also:

Edit Public BIF


Edit Public BIF

Keystroke: Ctrl+P

Purpose:

This option will launch the BIFED20.EXE program and open the Public BIF.

This is a quick and easy way to edit your Public BIF.

See Also:

Edit Private BIF


File Manager

Keystroke: F6

Purpose:

This option will launch the Windows File Manager WINFILE.EXE.  This program is usually located in the WINDOWS directory.

This is helpful if you want to copy, move, or delete files related to Novell's GroupWare products.

See Also:

DOS Prompt


GroupWise Information

Keystroke: F5

Purpose:

This option will give you access to information inthe Private BIF concerning GroupWise and Notify.

The GroupWise Private BIF Information dialog willdisplay the various different file locations specified under preferences for GroupWise and Notify.

The Third Party button will show a list of all the Third Party DLLs that will be loaded when GroupWise is executed.  These DLLs can alter the functionality of GroupWise.  This is a helpful troublshooting option when GroupWise is not operating as it should.


InForms Information

Keystroke: Shift+F5

Purpose:

This option will give you access to information in the Private BIF concerning InForms Designer and InForms Filler.

The InForms Private BIF Information dialog will display the various different file locations specified under preferences for InForms Designer and InForms Filler.

The Third Party button will show a list of all the Third Party DLLs that will be loaded when InForms Filler is executed.  These DLLs can alter the functionality of InForms Filler.  This is a helpful troublshooting option when InForms Filler is not operating as it should.

The IDAPI Config button will launch the IDAPICFG.EXE program that is installed by InForms Designer and InForms Filler.  This program is from Borland International and is used to configure Paradox and dBase settings.  This program is launched from the location specified in the WIN.INI under the [IDAPI] section, CONFIGFILE01 item.


Main Screen

Purpose:

The main screen gives information about the location of Novell GroupWare applications as well as what version of Shared Code is currently in memory.

The file locations displayed for GroupWise, InForms Designer, and InForms Filler are read from the Private BIF under the WPMacro Facility Group, and the WPOffice, InFormsDesigner, and InFormsFiller sections.  This is the location that the Novell GroupWare applications will look to, when launching another Novell GroupWare application.

The SoftSolutions information is the location where the ODMA.DLL file is located.  This is normally the SYSTEM directory.  If it is not found, the value <ODMA.DLL not found> message will show there instead of the dll location.

The BIF Information section shows what directory the Shared Code that is in memory was loaded from.  It also shows the release date and version if the version is greater than 2.2.  When Shared Code was initialized, it read the SH_SH_.ENV file to determine where to read the Private and Public BIFs.   NOTE:  Startup options on the command line of the application that first initialized Shared Code may override the values in the SH_SH_.ENV file.

The locations of the Private and Public BIFs are displayed in this section.  It is possible that no Public BIF is used, but you will always have a Private BIF.  There are two buttons at the end of each BIF location.  These buttons will launch the BIFED20.EXE program from the Shared Code directory and open the BIF specified on that line.

The Environment Information section shows the DOS environment.  The majority of these values are put in the environment by the SET command in the AUTOEXEC.BAT or possibly in a login script if you are on a network.  Some  values a set in the DOS environment by Windows when it is initalized.

The display driver shows what dirver file is in use and the realease date.  This option is for Windows 3.1.  Windows 95 will not show the correct value.


Purge BIF

Keystroke: Ctrl+U

Purpose:

This option will purge all related information from the Private BIF.

It is suggested you make a backup of your Private BIF before purging the Private BIF.

See Also:

Backup Private BIF


Registration Database

Keystroke: F8

Purpose:

This option will give important installation information about Novell Shared Code, GroupWise, InForms Designer, and InForms Filler.

The Shared Code Registration Database Keys dialog will show the directories where the various Novell Windows applications installed Shared Code.  It will also show the directory where the last Shared Code application loaded Shared Code from.  NOTE:  If these directories do not point to the same location you may run into problems with your Novell Windows applications.  Use the Resolve Shared Code option on the main screen to automatically reconfigure all these settings.

The Edit REG.DAT button will launch the REGEDIT.EXE program with the startup option /v.  This will give a verbose listing of all the keys in the Registration Database.  In WIndows 3.1, it will open the REG.DAT file.  In Windows 95, it will open the SYSTEM.DAT and USER.DAT files automatically.  This option is helpful when you are troublshooting and need to view the different settings that were created when the program was installed.  Shared Code 2.x applications (WordPerfect 6.x, GroupWise 4.1x, InForms 4.1, etc.) no longer use ini files.  Their installation information is now stored in the Registration Database.  The configuration information is stored in the BIF files.  When troublshooting, if you are having problems starting an application that uses Shared Code 2.x, you may want to look at the settings for that application in the Registration Database.  The BIF file APIs are part of Shared Code so the BIF would not be accessed until after Shared Code is initalized.

The GroupWise, InForms, and SoftSolutions buttons will display dialogs to show you key information about those applications that is stored in the Registration Database.  These dialogs have a button to Purge or remove all entries for that program from the Registration Database.

The GroupWare Purge button will purge all the information related to GroupWise, InForms Designer, InForms Filler, and Softolutions from the Registration Database.  After pressing this button, it will prompt you to verify you want to purge the information.

See Also:

Resolve Shared Code


Resolve Shared Code

Keystroke: F4

Purpose:

This option will attempt to resolve the most common Shared Code problems.  It will search for and evaluate all versions of Shared Code 2.x.  Once it determines the most current version, it will prompt you to consolidate all versions into one directory.  This option will copy only the newest files or files that are in an old Shared Code directory (ie. version 2.1) but are not in the newest Shared Code directory (ie. version 2.3).

Once the most current files are copied, this option will then update various different files that contain pointers to the Shared Code directory.  These files include the REG.DAT and product *.REG files.

This option will then create a new SH_SH_.ENV file, prompting you for the options to place in this file.  It will create a backup of the original file.

Finally, this option will verify that all the Third Party DLLs specified in the BIF files exists.

NOTE:  The Shared Code Resolve option should not be run if a customer has a foreign language version of Shared Code 2.x prior to version 2.3 installed as well as the US English version 2.3, unless they do the following:

The customer must obtain the most current version of the Shared Code file WPSH20xx.DLL for the language(s) for which they have installed (other than US English).  The xx represents the 2 letter Novell international code for the language.  If the customer chooses to continue with the Resolve option, the utility will still attempt to consolidate the multiple Shared Code directories it found.  When the consolidation process is completed, the customer should then copy the newest Shared Code 2.3 WPSH20xx.DLL file(s) they received from Novell into this consolidated directory.  If they do not update this file, the older applications that used the older Shared Code 2.x will not operate properly.

See Also:

Registration Database


Save Information

Keystroke: F3

Purpose:


SoftSolutions Information

Keystroke: Ctrl+F5

Purpose:

This option will allow to easily change the DMSRestrict options for GroupWise, InForms Designer, and InForms Filler.  You can also view SoftSolutions related information that is not stored in the Private BIF.

The DMSRestrict option in the Pribvate BIF willtell Shared Code whether or not to load theSoftSolutions Profile dialog when you want to Openor save within these programs.  The DMSRestrictoption is placed in the program group (i.e.InFormsDesigner), Environment section.  The valuesto restrict the Profile dialog are TRUE and FALSE.

The Directories button will show the directory search order SoftSolutions will use when it tries to locate files.  The first directory is the current working directory you are in when you run SoftSolutions.

NOTE:  This dialog will show what the current working directory.  Since you are running the GSC utility, it will show the current working directory GSC is using.

The DLLs button will show various information about the DLLs that are used by SoftSolutions.

The SoftSolW.INI button will launch NOTEPAD.EXE and open the SOFTSOLW.INI file.  Both of these files are located in you WINDOWS directory.  This will allow you quick access to viewing or editing the ini file.

The RENAME ODMA button will prompt youfor a name to rename the ODMA.DLL file in you SYSTEM directory.  By renaming this dll, you shut off all integration with SoftSolutions.


System Configuration Editor

Keystroke: F9

Purpose:

This option will launch the System Configuration Editor SYSEDIT.EXE.  This file is normally located in your SYSTEM directory.

The System Configuration Editor will allow you to easily make changes to your WIN.INI, SYSTEM.INI, CONFIG.SYS, and AUTOEXEC.BAT files.

See Also:

DOS Prompt