Home › Forums › Knowledge Base › Legacy Applications › Configuring for Touch Menus Software
- This topic has 0 replies, 1 voice, and was last updated 19 years ago by
Rob.
-
AuthorPosts
-
April 15, 2006 at 2:19 pm #1656
Rob
MemberConfiguring for Touch Menus Software
Last edited: December 15, 2003 08:18 AM
This document provides generic instructions for configuring Touch Menus and non-Touch Menus equipment so that Touch Menus software will run properly. It is supplemented by the Windows Configuration Information Knowledge Base document. Setup should only be attempted by someone who is technically proficient, as some instructions are necessarily vague to account for the varieties of computer configurations found in the market today. The primary instructions assume this is being set up on a Windows95/98 platform. If this is not the case, see the Non-Windows95 Systems section at the end of this document.
Primary Configuration OverviewThis section contains the general steps needed to get Touch Menus back office software packages installed and running. To configure the system to also run Touchnet, see the additional steps included in Configuring for Touchnet.
1.
Follow the instructions in the Creating the Directories section.
2.Follow the instructions in the Loading the Software section.
3.Follow the instructions in the Connecting the HASP section.
4.Follow the instructions in the Printers section of the Windows Configuration Information document.
5.Follow the instructions in the Creating an Icon section of the Windows Configuration Information document.
If this system will only run back office software, you are done. If you need to run Touchnet also, proceed to the next section.
Configuring for Touchnet1.
Follow the instructions in the Setting up the Ramdrive section.
2.Follow the instructions in the Configuring for Mouse/Touch section.
3.Follow the instructions in the Defining the Path section.
4.Follow the instructions in the Disabling Printing section.
5.Follow the instructions in the Creating an Icon section of the Windows Configuration Information document.
Stop. You are done. If something is not working, repeat the steps listed above or call Your Support Technician.
Creating the DirectoriesDirTree.bmp (5018 bytes)Touch Menus software requires a specific directory structure and there is currently no install program in existence to create it. Use Windows Explorer, or whatever method you are most comfortable with to create the directory structure as shown in the illustration at the right. Note that where it says (application), put the unique name assigned to the specific application you are installing. Also note that you may have software that requires additional directories not listed here.
Loading the SoftwareThis document assumes that you have access to Touch Menus software. If you are a dealer, you can download the software you need from the Downloads section of the Developers area. Otherwise you will need to copy the software off of an existing Touch Menus system or make special arrangement with Touch Menus to obtain the software by some other means. Most of our software initially comes in Zip format and needs a utility like PKUNZIP or WinZip to access it. See the FAQ called How Do I Unzip a File for more information. Each directory has it’s own set of files, installed as follows:
*
TOUCHNET – Install TNV6_56 or the current version of Touchnet here.
*(application) – Install the zip of the desired application here.
*CHECKS – Can leave empty for a new install.
*
DATA – Contains store specific information. If setting up an office for multiple stores, the information in this directory will be unique for each store, even though the application itself may be the same for all stores.
*REPORTS – Can leave empty for a new install. Alternately, if this is an office copy of an actual store, or sales information exists for a demo system, it can be loaded here.
*PCX – Install any graphic images here.
*TOOLS – Some applications require various utility programs to run. If you have any, put them here.
*PLUGINS – The Manager program can be supplemented with custom reports, called plugins. If you have any, install them here.
Connecting the HASP
haspback.gif (36950 bytes)Touch Menus software will not run properly unless a HASP is installed on the LPT1 port. HASPs for customer owned equipment are usually set up to run on non-networked or standalone computers, and do not require any additional software to operate. You can test a HASP and verify that it is operating correctly by running a utility called RAP. From the RAP main menu, select Request HASP ID. If it returns a number, the HASP is functioning.
Setting up the RAMDrive
The term RAMDrive is not technically correct for a Windows95 station. However, Touch Menus has retained the term to maintain consistency throughout its product line. What Touchnet actually requires is a valid Z: drive from which it can read and write data. On a Windows 95/98 system set it up as follows:
1.
Create a directory called RAMDRIVE.
2.Edit the Autoexec.Bat and add SUBST Z: C:RAMDRIVE. Note that you may have to modify the command if the directory was placed on other than the C: drive.
Configuring for Mouse/Touch
Touchnet is designed to work with a touch screen. However a mouse can used instead. Most Windows95 mouse drivers will work fine in DOS, but if yours doesn’t, you may have to contact the manufacturer to get a DOS mouse driver.
You will also need to tell Touchnet to turn on the mouse pointer. Do this by editing the Autoexec.Bat and adding the command SET SHOWMOUSE=YES.
Defining the PathYour Windows icon knows what directory to locate Touchnet in, but the application itself may make calls to various utilities and programs not located in the current directory. To assure that the application will run properly, edit the Autoexec.Bat and add the following command:
PATH=C:WINDOWS;C:WINDOWSCOMMAND;C:TOUCHNET;C:TOOLS;C:PLUGINS
Disabling PrintingOne problem most applications have is that they expect to be running on a network with a variety of local and global printers that don’t exist on this system. An easy way to avoid unnecessary printer errors is to go to the application directory and rename the file PRINTERS.DAT to something else like PRINTERS.BAK. Touchnet will then assume there are no printers and ignore any print commands that come from the application.
Non-Windows95 SystemsMost of the steps performed for a Windows95 system are essentially the same for a Windows 3.1 or DOS system with the following changes and additions:
1.
For Windows 3.1 you would set up an icon differently. For DOS, you most likely have a menu system of some kind that would need to be configured to run Touch Menus software.
2.A more efficient way to set up a RAMDrive in DOS is to add these two commands to the Config.Sys:
*
DEVICE=C:DOSRAMDRIVE.SYS 300 /E
*LASTDRIVE=Z
Then change the Subst command in the Autoexec.Bat as follows:
*
SUBST Z:
(if RamDrive.Sys loads to a different driver, modify the command as needed)
3.
A DOS mouse driver must be loaded prior to running Touchnet.
4.You must have approximately 510K to 520K free base memory. See the tech tip Memory Optimization Tricks for more information on configuring memory.
Revisions
7/2/99 rw
1.
Initial Writing.
12/12/00 rw
1.
Document was formerly named Configuring Customer Owned Equipment. Renamed to reflect the fact that the document was being used to configure in house equipment, not just customer owned.
2.Updated hyperlinks to match changes to the Windows Configuration Information document.
-
AuthorPosts
- You must be logged in to reply to this topic.