Hello,

There is a problem that we are aware of (and plan on fixing) that is probably
the source of your trouble. To circumvent the problem, you need to ensure that
the amount of available space on the drive that NT is installed on PLUS the
amount of available space on the drive that the TEMP environment variable
points to is less than 2 GB.

For example, suppose that:

1) The NT operating system is on the D: drive
2) The D: drive has 500 MB of free space
3) The TEMP environment variable is set to F:\TEMP
4) The F: drive has 3 GB of free space

This will cause the problem because the sum of available space is 3.5 GB, which
exceeds 2 GB. In this case, there are a couple of things you can try:

a) Set the TEMP variable to point to D:\TEMP (you'll need to create a TEMP
directory on the D: drive). Since the D: drive has less than 2 GB of free
space, you should be able to do the installation successfully. Once it's
complete, you can set TEMP back to its original setting.

b) Create one or more large files on the F: drive such that the free space on
the drive drops to less than 1.5 GB. Once the installation is complete, you can
remove the large file(s).

Hope this helps,

Andy

Andy Raibeck
IBM Storage Systems Division
ADSM Client Development
e-mail: storman AT us.ibm DOT com



ADSM-L AT VM.MARIST DOT EDU on 07/02/98 10:04:45 PM
Please respond to ADSM-L AT VM.MARIST DOT EDU
To: ADSM-L AT VM.MARIST DOT EDU
cc:
Subject: NT Server install problem


Greetings,

I have a small problem with a Windows NT 4.0 Server with SP3, IIS4, IE4
installed.  When I try to install the Win32 client The install bitmap appears
on the screen, the Install Shield Wizard runs through to 100% and the install
screen comes up for a split second and then disappears leaving me at the NT
desktop.  I have tried reinstalling SP3, tried multiple copies of the client
software, I have even taken out on the RAID drives to see if during the
rebuild the machine will slow down enough for me to be able to read any error
messages with no success.  There is no information in any of the logs, and
running it from a DOS prompt leaves me none the wiser.  I have just
reinstalled the server as my first install was to test the machine.  On the
first install nothing weird or unusual occurred with the ADSM client or the
server and everything worked well.  The first install had no IIS4 or IE4.  Any
help would be greatly appreciated.
Regards,
Mark.

Mark Reschke
Systems Support Analyst
Information Technology Services
University of Melbourne
Parkville 3052, Australia
Ph. +613 9344 5411
Fax. +613 9347 4803

M.Reschke AT its.unimelb.edu DOT au