JimPrice.Com Site Map

NS-Batch Installation Problems

According to more than one user, the installation program for NS-Batch fails under (at least one version of) Windows NT Workstation. The problem descriptions / solutions have been:

The Usual Failure ...First failure reported (with NT 4.0)
Problem with NT 3.51 ...So...it's not limited to 4.0 after all!
With QuarterDeck CleanSweep ...Another flavor of problem.
A Quick Fix ...A poor man's solution.

The Usual Failure

The best description of the failure (so far) has come from Heini Holmberg.

The problem manifests itself during installation under Windows NT 4.0 Workstation (Build 1381), US version (and may be present in other versions as well). Even on a fast Pentium machine with adequate RAM and disk space, installation stops because of "insufficient memory and diskspace". The bug can be overcome, by deleting the three .INI files that the setup creates in the "winnt" directory (_isen31.ini, _isenv31.ini, and _delis43.ini ).

If the setup program stops responding, the system may lock up completely, or just the setup program may freeze. (Even if the system locks up completely, you've got about 30 seconds to delete the files after the setup program fails.) If you delete those three files, you should be able to complete the installation. Once the install completes, NS-Batch appears to operate without problems (and by the way, the "uninstall" program seems to work fine).

In case you're wondering, the installation program is the "express" version of InstallShield that comes with the Borland (now Inprise) C++ compiler. The 32-bit version of NS-Batch (rev 0.5e) was compiled with version 5.01 of the compiler, and the latest available version of InstallShield Express was used to build the release file. I am in the process of getting help from Borland on this problem. In the mean time, if any users have any further information that you'd like to share, please don't hesitate to contact me.

Just FYI, here's what the _isen31.ini file contained:

7068=Insufficient memory available to run Setup. 
Close all other applications to make more memory 
available and try to run Setup again.``Error 111.
7063=Setup is unable to find a hard disk location to 
store temporary files.``Make at least %dKB free disk 
space available and then try running Setup again.``Error 101.
7064=Setup is unable to decompress and copy all of the 
program files needed to proceed with the installation.  
Contact your software vendor.``Error 112.
7110=Setup Initialization Error

The file _isenv31.ini file contained:

Stepping 12, GenuineIntel 

And, finally, the file _delis43.ini contained:


Failure with NT Workstation 3.51

This variant of the problem was reported by Lazlo Toth.

The problem was observed on a Pentium 120, with 48 Megs of RAM, running NT Workstaion 3.51, Build 1381 (upgraded to service pack 5). When an installation was attempted, InstallShield froze, showing the progress indicator at about 40%. (Sound familiar anyone?)

By deleting the .INI files as described above, the installation was completed and NS-Batch seemed to run without problems. However, it was then impossible to delete temporary directory from which the installation program was run. My hunch about this problem is that a thread of the first execution of InstallShield was still running somewhere, and had the directory locked.

Thanks to Lazlo for reporting this new variant and the disturbing news that the problem is not limited to just NT 4.0.

Failure with Quarterdeck CleanSweep

This problem was reported to me by Mark Symons.

The problem has been observed when you install NS-Batch under NT 4.0 (with Service Pack 2) and CleanSweep version 3.0 from QuarterDeck is running. CleanSweep includes a utility called SmartSweep, which can monitor installations. If SmartSweep is not switched off before the installation for the 32-bit version of NS-Batch is run, the installation will freeze (and must be terminated with Task Manager).

Installation appears to complete normally if SmartSweep is (temporarily) disabled.

A Quick Fix

Here's one way to solve the problem. I've created a (32-bit) release that does not use InstallShield. This release contains (to the best of my knowledge) the same executable, and runtime .DLL files that you'll find in the full 32-bit release. The only difference is that it's just a .ZIP file, with no support by InstallShield for creating the application directory, tossing icons on the desktop, and all that other neat stuff.

To install the product, create an empty directory, unzip the file, and then just run nsb-32.exe. If you find that I've left out any of the runtime .DLL files, please let me know, and I'll add them to the archive.


32-bit only Version 1.06 - From a fast server.Fast
32-bit only Version 1.06 - From my server
32-bit only Version 1.05
32-bit only Version 1.04
32-bit only Version 1.03
32-bit only Version 1.02
32-bit only Version 1.01
32-bit only Version 0.6e
32-bit only Version 0.6d - From a fast server.Fast
32-bit only Version 0.6d - From my server
32-bit only Version 0.6c
32-bit only Version 0.6b
32-bit only Version 0.6a

Again, if anyone has any additional information on these problems, please be sure to forward it to me via e-mail.

Many thanks to everyone who has put up with the installation problems enough to try NS-Batch, and very special thanks to all those who have struggled to find work-arounds for the the bugs.

Tip This page and its contents, copyright © 1996-2010, JimPrice.Com. Here's a link to our privacy statement. If you have any questions about this page, please drop me a line (e-mail address should be obvious to all but SPAM-bots).

This site last updated 5/24/2010.