Condition |
Incomplete Installation under NT
Stockroom Inventory Manager 5 (Windows) does not install completely under NT.
Action |
The following info may be helpful installing Stockroom Inventory Manager 5 under NT...
WINDOWS NT INSTALL PROCEDURES
Stockroom Inventory Manager, Version 5.0
Some Windows NT configurations prevent the install program from completing two steps. These two steps can be completed manually.
Step one – ICONS.
Place the mouse cursor on the desktop and right click. Select NEW and then SHORTCUT. Use browse to find the CMSSR50 folder. If you took the defaults, this will be on your C: drive. Locate the program called SR5WIN.EXE. Click the EXE program name twice OR click it once to highlight it and click OPEN. The program now asks you to select a name for the shortcut and fills in the name of the EXE file. You can change this to anything you like. Click FINISH and your desktop icon is installed. If your machine has custom profiles for each user, you must make these shortcuts exist in every profile that will need access to the programs. You can do this in the PROPERTIES settings for the shortcuts. Click "Exists in All Profiles" and unclick "Exists in This Profile Only"
Now follow these same steps to build a shortcut to the BDECFG.EXE file in the C:\IDAPI folder.
Step Two – WIN.INI
Click the START button in the lower left corner of the screen. Click RUN. Type SYSEDIT in the entry field. Click OK. The System Configuration Editor will start. Inside its window will be several smaller windows with names like C:\AUTOEXEC.BAT, C:\CONFIG.SYS, C:\WINNT\WIN.INI, etc. Click on the title bar for the one named WIN.INI. Click on SEARCH and type in IDAPI. Click NEXT. If you get the message "Cannot Find IDAPI", click OK on the message box.
If the IDAPI section was not found, scroll down to the bottom of the file. Type in the following EXACTLY as shown. Upper and lower case ARE important. If there is already an IDAPI section, it should look like the one shown below. If you did not install the IDAPI in the default directory, you will have to modify the drive letters and/or paths to point to your copy of the IDAPI.
[IDAPI]
DLLPATH=C:\IDAPI
CONFIGFILE01=C:\IDAPI\IDAPI.CFG
[Borland Language Drivers]
LDPath=C:\IDAPI\LANGDRV
Click FILE and then SAVE. Click FILE and then EXIT.
If you installed the data in other than the default folder, then you need to refer to the section in the manual on setting the BDE aliases to point to your data files.
You must now reboot your computer for the WIN.INI changes to take effect. You should now be able to start the program by clicking on the desktop shortcut for the Stockroom program.
If you are upgrading from DOS, the Stockroom data files (*.DBF and *.DBT) and the DOS program file (STINV.EXE or SUPPLY.EXE) must be accessible from the machine that will run the Windows version of Stockroom.
Unlike the DOS version, you can install the Windows Stockroom program on one machine and place the Windows Stockroom data on another machine such as a network server that is automatically backed up once a day.
When doing this, the FIRST Windows program install should be done as a NEW INSTALL or DOS UPDATE INSTALL and all subsequent installs should be done as WORKSTATION INSTALLS.
Before installing any Workstation programs, first do the NEW INSTALL or the DOS UPDATE INSTALL. Import the DOS data if you are upgrading from a DOS version. Next do WORKSTATION installs on the other machines. The Workstation install will install the Stockroom program and the IDAPI program and will ask you to tell it where the Windows data files are located.
You will have to modify the BDE Alias settings on each installation machine, as explained in the manual, so that each BDE is pointing at the shared data directory on the server. If each machine sees the server as having the same drive letter and path, then make all the BDE aliases the same. In this case, you could even copy IDAPI.CFG from the first machine to all the other machines. However, if some workstations see the Windows data server using a different drive letter and/or path than other workstations use, then each BDE Alias must be individually configured.
Return to CMS Support Page Return to CONTENTS Page