WinBatch Tech Support Home

Database Search

If you can't find the information using the categories below, post a question over in our WinBatch Tech Support Forum.

TechHome

WinBatch
Installation Licensing Setup
plus
Install Apps with WB Example

Can't find the information you are looking for here? Then leave a message over on our WinBatch Tech Support Forum.

Winbatch Server Version Installation and Shortcuts 

Keywords:    server version shortcut icons

Question:

How do I install this onto the server and then how do individuals get the necessary shortcuts?

Answer:

The server installation instructions should pretty much explain how to install Winbatch on a server.

Basically, once installed on the server, you need to rename the UNINSTAL.EXE in the \Winbatch\System\ directory to be called MAKEICON.EXE. Then your users can run the MAKEICON.EXE program while attached to the WinBatch network directory to install the shortcut icons on their local workstations.

One thing to keep in mind that's not mentioned in the server installation instructions:

NB: The \winbatch\system\license.ini and/or the c:\windows\license.ini file(s) have to be marked writeable and shareable for the server licensing procedure to work. If license.ini is marked shareable/read-only you will get the error message "incorrect licensing data" when you try to run Winbatch from the local workstation.

Here are further server installation details:

Once you have the Server version of Winbatch installed on your network server:

To install shortcut icons to your WinBatch directory on your SERVER, from your client workstations, (implemented starting in WinBatch version 97A), do the following:

  1. After you have completed the WinBatch installation, go into your \WINBATCH\SYSTEM\ subdirectory, and rename the file, "UNINSTAL.EXE" to "MAKEICON.EXE".

  2. When users from their individual workstations launch MAKEICON.EXE while attached to the WinBatch network directory, shortcuts to the README, *.HLP and *.EXE files on the server will be created in their Start Menu directory. They have the option of changing where they want the Shortcuts to point to, but the shortcuts will always be created in their local Start Menu directory.
If your users want to install a private FileMenu and PopMenu on their workstations, they can do the following:
  1. Copy FILEMENU.INI and POPMENU.INI from your Server's \WINBATCH\SYSTEM\ directory to their local C:\WINDOWS directory. Then follow the steps below:
TO INSTALL AND CONFIGURE FILEMENU:

FileMenu is a shell extension for the Windows 95 Explorer. It allows you to create custom menu items to be added to the context menus (which appear when you right-click on a file). Two types of menus are supported: a global menu, which is added to the context menu of every file, and a file-specific "local" menu, whose entries depend on the type of file that is clicked on.

  1. Make sure the server's FILEMENU.DLL is in your path.

  2. Copy the server's FILEMENU.INI file to your Windows directory, if you haven't done so already.

  3. Make sure that the server's WBD??34I.DLL file is on your path.

  4. The menu file names used by FileMenu are defined in FILEMENU.INI. Edit FILEMENU.INI so that the INI file points to the global menu file, FILEMENU.MNW, on your server, or to a local copy of a customized global menu file. This can be changed by editing the "CommonMenu=" line in the [FileMenu] section.

    The default "local" menu file is named DEFAULT.MNW, and this can be changed by editing the "DefaultMenu=" line in the [FileMenu] section of FILEMENU.INI to point to this menu file located on your server, or to a local customized *.MNW file.

The following settings can be added to the [FileMenu] section of FILEMENU.INI: 
	MenuDir=c:\path
where "c:\path" is the initial directory where you want FileMenu to look for its menus. Specify the server's directory where FileMenu is, unless you want to specify a local folder. 
        CommonMenu=menufile.mnw
where "menufile.mnw" is the name of the global menu file you wish to use. The default is "FILEMENU.MNW". Point to the server's directory where this is located, or use your own. 
	DefaultMenu=menufile.mnw
where "menufile.mnw" is the name of the default local menu file you wish to use. The default is "DEFAULT.MNW". Point to the server's directory where this is located, or use your own. 
        SkipCommonMenu=1
Causes FileMenu not to load the global menu file. By default, the global menu file will be loaded. 
        SkipDefaultMenu=1
Causes FileMenu not to load the default file-specific local menu file (ie, it will load local menu files only for file types listed in the [Menus] section).

After you've set up your menu files, then right-click on a file in Explorer. You should see your menu items added to the context menu. Several sample menu files are included with the program, which you can customize or use as-is. TO INSTALL AND CONFIGURE POPMENU: PopMenu is a pop-up menu which, when run, affixes itself to the right-hand side of the Windows 95 task bar (the bar which runs along the bottom of the screen). Clicking on the icon pops up the menu, which can contain many user-defined items to do all kinds of things.

  1. Copy the server's POPMENU.INI file to your Windows directory, if you haven't done so already.

  2. Make sure your server's WBD??34I.DLL file is on your path.

  3. Set up your menu files and place them your Windows directory. A sample menu file is included with the program, which you can customize or use as-is. PopMenu allows you to specify two menu files: (a) a global menu file, and (b) a window-specific local menu file. The default global menu file is named POPMENU.MNW. You can change this by editing the INI file, as outlined below.
The following settings can be added to the [PopMenu] section of POPMENU.INI: 
        MenuDir=c:\path
where "c:\path" is the directory where you want PopMenu to place menu files that it creates. This will also be the first place PopMenu looks for menus. 
        Editor=editor
where "editor" is the editor you wish to use to edit your menu files. The default is "Notepad.exe". 
        GlobalMenu=menufile.mnw
where "menufile.mnw" is the name of the global menu file you wish to use. The default is "POPMENU.MNW". 
        SkipGlobalMenu=1
Causes PopMenu not to load the global menu file. By default, the global menu file will be loaded. 
        SkipLocalMenu=1
Causes PopMenu not to load the window-specific local menu file. By default, the local menu file will be loaded. 
        SkipGlobalEdit=1
Causes PopMenu not to add a "Create/Edit menu" item at the top of the global menu. By default, the menu item will be added. 
        SkipLocalEdit=1
Causes PopMenu not to add a "Create/Edit menu" item at the top of the local menu. By default, the menu item will be added.

  • Now that that's all done, run POPMENU.EXE. You should see the PopMenu icon appear in the task bar. 
    Article ID:   W13407

    Filename:   Server Version Setup and Shortcuts.txt
    File Created: 2001:03:01:14:38:12
    Last Updated: 2001:03:01:14:38:12