Sias- thanks for your reply; but I found a work around...I discovered that
there was a "hung" msi process / windows installer process.  If I went in
and stopped the manual service, the install would then work.

pretty quirky, huh?


"ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU> wrote on 03/10/2003
02:51:20 PM:

> Lisa,

> I had the same issue with the 4.1 client.

> I can not remember which solution solved my issue.

> 1. In the readme file it mentions about some value to change in
> the setup.ini file.

>
> 2. Run the file called "instmsiw.exe" that's within the
> directory of the TSM install files.  It's going to update some
> files on the system and ask to reboot the system.  Answer "Yes"
> to reboot the system.  After it rebooted run this file again.
> It will once again update some files.  After you ran this file
> a second time you can then run setup.exe again.

> Sias

>
> ________________________________________________
> Get your own "800" number
> Voicemail, fax, email, and a lot more
> http://www.ureach.com/reg/tag

>
> ---- On    , Lisa Cabanas (CABANL AT MODOT DOT NET) wrote:

> > Any ideas?  NT4 SP5, had 4.2.1.20 client on it and I get this:
> >
> > Error 1711. An error occurred while writing installation
> information to
> > disk.  Check to make sure enough disk space is available, and
> click Retry,
> > or Cancel to end the installation.
> >
> > trying to install the 5.1.5.9 client.  This isn't the same
> error as the out
> > of disk error that used to happen
> >
> >  error 1603 General Windows Installer engine error. Increase
> DiskSpace
> >  requirement in Setup.ini and try again
> >
> >
> >
> > The only hit I come up with is on msdn- but on a win2k box
> using the Group
> > policy method of deploying installments.  (the domain
> controller's sysvol
> > partition is too full). We are not using AD, so this doesn't
> apply, AFAIK.
> >
> > There almost 3 G of space available on the system drive, so I
> am stumped.
> >
> > thanks
> > lisa
> >
> >