GUI Will Not Package Properly

• Article Type: General
• Product: Aleph
• Product Version: 18.01

Description:
The GUI repackaging NEVER picks up our local settings in C:\AL500.
I unpack the install the GUI500 from the server. I install to C:\AL500.
I adjust the alephcom.ini, library.ini and all the other ini files in situ.
I then repack from the same directory I ran the setup from. All the ini files end up with the old versions - i.e. the library.ini with only USMxx, and IP address/Host:Port
I am using makeinst.bat. I have tried on 2 PCs - both Windows XP.

Resolution:
1. Use makeinst.bat for Win95/WinNT and makeins2.bat for Win2000/WinXP.

2. The GUI500.exe synchronizes changes, while GUI500-U.exe installs the GUI "as is". That means that the GUI500.exe checks during the installation if "#" lines exist in the configuration files (e.g., window.dat), and if not, it leaves the line intact (saves installed changes), while GUI500-U.exe does not check for installed changes and installs the window.dat from the new package.

See the attached document for detailed instructions on repackaging the GUI.

Errata:

=====

Paragraph 5 has a small error at the end:

5. Copying the Modified Files to the xxx Directories
Any of the above files you modify (in the TAB or ENG directories) must be copied down to the lower level so that these changes are incorporated into the Master (redistributed) client. The lower level for the AL500/<module>/TAB/ directory is the AL500/<module>/TAB/XXX_TAB, and the lower level for AL500/<module>/TAB/ENG is AL500/<module>/TAB/ENG/XXX.

It should say:

5. Copying the Modified Files to the xxx Directories
Any of the above files you modify (in the TAB or ENG directories) must be copied down to the lower level so that these changes are incorporated into the Master (redistributed) client. The lower level for the AL500/<module>/TAB/ directory is the AL500/<module>/TAB/XXX_TAB, and the lower level for AL500/<module>/TAB/ENG is AL500/<module>/TAB/XXX.

=====

Paragraph 7 needs to be updated for Windows XP. makeins2.bat is used for Windows XP, too.

7. Re-packaging Your New Client
When you are satisfied with your customizations of the GUI client, you can re-package it using the appropriate makeinst.bat script (in the \tempaleph directory). If you are repackaging this GUI client on a Windows 2000 operating system, use the MAKEINS2.BAT file. If you are using Windows 95, 98 or NT operating system, be sure to use the MAKEINS.BAT script.

=====