InstallSheild says there isn't enough disk space
Frank Levine
(InstallShield Software Corporation) wrote:
>On Tue, 14 Jul 1998 12:29:49 -0400, Peter Tyson <pty...@speedline.ca>
>wrote:
>>Do you know if this has been addressed by InstallShield yet? If so what build?
>
>It is going to be addressed in the next Maintenance Releases of both
>Express and IS5.1
>
>Stefan
>InstallShield Software Corp.
Please clear up some points so I can determine if I fall into this
category:
1) Are there separate IS calls to get "free disk space" and "total
disk space"?
2) If yes, is the "free disk space" call still returning 2GB if the
free space is >2GB?
3) Is the "total disk space" call returning the 32bit unsigned
overflow value of total disk space (i.e. total disk space of 4.1GB
returns .1 GB to this call).
4) Will an IS installation crap out when it detects that it is about
to exceed what it believes to be "total disk space"? (I can see the
logic to this as in between the time IS calculated free space and some
later point in the install some other running app could have eaten all
the free space).
5) Is this the reason for the erroneous "out of disk space" messages?
Any patches for a work around would be gladly received (either IS or
Windows98 - even on a use-as-is basis)
Stefan Krueger
I'm not an official InstallShield representative, but I'll try to answer
your questions (assuming InstallShield 5.5):
>1) Are there separate IS calls to get "free disk space" and "total
>disk space"?
Yes. GetDiskSpaceEx (for free space) and
GetSystemInfo(DISK_TOTALSPACE_EX,...) for total disk space.
Note that both functions also come in a flavor without "Ex" and limited to
2GB (backward compatibility).
>2) If yes, is the "free disk space" call still returning 2GB if the
>free space is >2GB?
The GetDiskSpaceEx function returns the amount of free disk space on the
specified drive. The value passed in nUnits determines whether the value
returned by GetDiskSpaceEx is a measure of bytes, kilobytes, megabytes, or
gigabytes.
>3) Is the "total disk space" call returning the 32bit unsigned
>overflow value of total disk space (i.e. total disk space of 4.1GB
>returns .1 GB to this call).
DISK_TOTALSPACE_EX returns the total capacity of the disk drive. nvResult
specifies the measurement unit; pass one of the following predefined
constants in this parameter: BYTES, KBYTES, MBYTES or GBYTES.
>4) Will an IS installation crap out when it detects that it is about
>to exceed what it believes to be "total disk space"? (I can see the
>logic to this as in between the time IS calculated free space and some
>later point in the install some other running app could have eaten all
>the free space).
Generally InstallShield reports an error when there is not enough disk
space.
>5) Is this the reason for the erroneous "out of disk space" messages?
I don't know, but I guess it depends on the version you are using.
Stefan Krueger
Independent Setup Consultant
NEU: Deutschsprachiges Forum auf InstallSite
// InstallSite - Resources for setup developers
// http://www.installsite.org (primary site - USA)
// http://installsite.sw.com.sg (mirror site - Singapore)
My reply-to address is invalid to avoid spam.
If you are looking for individual assistance,
like e-mail support, please mail to
in...@installsite.org for support options.
Frank Levine
Thank you, Stefan, for your response.
If I understand your reply, if not using 5.5 or if using 5.5 with with
GetSystemInfo(DISK_TOTALSPACE...) (not the _EX version) one cannot
tell the difference between .1GB, 2.1GB, 4.1GB etc. tot.al disk space.
I am not an IS programmer, but an end user. As an attempt at a fix, I
shrank my free space to well below 2GB (by creating some huge files)
so the problem facing most likely relates to erroneous total disk
space calculations, not free space. The questions still remain:
1) Assuming 5.5, is the use and interpretation of the _EX version the
complete responsibility of the IS programmer, or are there some IS
internal calls that may or may not "use" the _EX version that are out
of the control of the IS programmer and may abort the installation if
the non _EX version is being used?
2) Assuming not 5.5, the IS programmer cannot adequately assess the
true disk space on the drive. Is this also true of IS internal calls?
In this case can these internal calls that may be retrieving the wrong
total disk space be automatically aborting the installation when that
erroneous value is exceeded?
P.S. - Seeing that IS is "working on this" and that "it will be fixed
in the next maintainance release" (of 5.1) I assume that there are
internal calls beyond the control of the IS programmer that are
retrieving erroneous results for total disk space and that this is
causing problems (i.e. erroneous "no space" problems). What
do you think?
Stefan Krueger
>GetSystemInfo(DISK_TOTALSPACE...) (not the _EX version) one cannot
>tell the difference between .1GB, 2.1GB, 4.1GB etc. tot.al disk space.
From documentation these calls should return 2 GB if there is more than 2
GB, that is 2.1 GB should be reported as 2 GB, and 4.1 GB as 2 GB as well.
Note that this is only true for local drives. As soon as some network client
(Novell for instance) is involved, things get more complicated.
There was also a bug in GetDiskSpace if a UNC path was used. This was fixed
in IS 5.5.
Did you get an indication that setup only sees .1 GB? Or only "not enough"?
>1) Assuming 5.5, is the use and interpretation of the _EX version the
>complete responsibility of the IS programmer, or are there some IS
>internal calls that may or may not "use" the _EX version that are out
>of the control of the IS programmer and may abort the installation if
>the non _EX version is being used?
There are some internal disk space calculations, but hopefully they have
also been made >2GB compatible in 5.5 (?)
But instead of guessing: What error message do you get (maybe screenshot)?
This could allow us to tell whether this is a built-in message, or something
created by the programmer of the setup. BTW why don't you ask him or the
company that sold you the software?
>2) Assuming not 5.5, the IS programmer cannot adequately assess the
>true disk space on the drive. Is this also true of IS internal calls?
Yes.
>In this case can these internal calls that may be retrieving the wrong
>total disk space be automatically aborting the installation when that
>erroneous value is exceeded?
I'm not sure. (Who could be without analyzing the source code of
InstallShield?)
>P.S. - Seeing that IS is "working on this" and that "it will be fixed
>in the next maintainance release" (of 5.1) I assume that there are
>internal calls beyond the control of the IS programmer that are
>retrieving erroneous results for total disk space and that this is
>causing problems (i.e. erroneous "no space" problems). What
>do you think?
What is the version number of your setup.exe (right-click in Explorer,
select Properties and go to the Version tab)?
John Smith
Here are responses to your questions:
>>GetSystemInfo(DISK_TOTALSPACE...) (not the _EX version) one cannot
>>tell the difference between .1GB, 2.1GB, 4.1GB etc. tot.al disk space.
>
>
>From documentation these calls should return 2 GB if there is more than 2
>GB, that is 2.1 GB should be reported as 2 GB, and 4.1 GB as 2 GB as well.
>Note that this is only true for local drives. As soon as some network client
>(Novell for instance) is involved, things get more complicated.
>There was also a bug in GetDiskSpace if a UNC path was used. This was fixed
>in IS 5.5.
>Did you get an indication that setup only sees .1 GB? Or only "not enough"?
This is my local C: drive (no network drives). The only indication of
what Installshield sees is freespace during the Omnipage 8.0 install
(it displays 2GB), not total disk space.
>>1) Assuming 5.5, is the use and interpretation of the _EX version the
>>complete responsibility of the IS programmer, or are there some IS
>>internal calls that may or may not "use" the _EX version that are out
>>of the control of the IS programmer and may abort the installation if
>>the non _EX version is being used?
>
>
>There are some internal disk space calculations, but hopefully they have
>also been made >2GB compatible in 5.5 (?)
>But instead of guessing: What error message do you get (maybe screenshot)?
>This could allow us to tell whether this is a built-in message, or something
>created by the programmer of the setup. BTW why don't you ask him or the
>company that sold you the software?
I do have some screen shots of the failure. Caere1 and caere2 are
errors when trying to install from HP 4100C scanner CD (Omnipage 8.0
is bundled on that CD). Caere suggested I download Omnipage 9.0 from
their site (I did). Caere3 is the error encountered during
decompression of Setup.exe for Omnipage 9.0. These 3 screenshops are
included in the attached file. Caere1 error allows me to click OK to
continue and then stops with Caere2 error. Note - caere2 occurs on
precisely the same file (opreseng.dll) regardless of how much
freespace I have. I can shrink freespace by 1.5 GB and caere1 and
caere 2 both occur, and caere2 gets error copying "opreseng.dll".
Yes, I spoke both with HP and Caere - they are clueless. That's why
I'm here. If Omnipage wasn't considered such good OCR software I
wouldn't be exerting this kind of effort.
>>P.S. - Seeing that IS is "working on this" and that "it will be fixed
>>in the next maintainance release" (of 5.1) I assume that there are
>>internal calls beyond the control of the IS programmer that are
>>retrieving erroneous results for total disk space and that this is
>>causing problems (i.e. erroneous "no space" problems). What
>>do you think?
>
>
>What is the version number of your setup.exe (right-click in Explorer,
>select Properties and go to the Version tab)?
I am not currently at the install site, so I can't do that now.
Monday ...
I am basing these questions about disk space overflow on the previous
entries in this thread. Here are some excerpts:
--------excerpt 1--------------------------
>
On Tue, 12 May 1998 11:16:28 +0200, "John Makin"
<john....@NOSPAMoscarfab.demon.co.uk> wrote:
>The disk space calculation overflows at 4.2 GB to 0. Therefore a 5GB HDD
>will be seen as 0.8GB !!
This is being addressed.
Stefan
ellipse data systems
--------------------------------------------
A little farther down:
---------------excerpt 2--------------
On Thu, 21 May 1998 15:51:00 -0500, "Ed Staub"
<est...@xxxworldnet.att.net>
wrote:
>Is this problem present in:
> "InstallShield 5.0 Free Edition (Build 149)" ?
> This is the version in Visual C++ as of Service Pack 3.
InstallShield is addressing the issue. The versions that are affected
(as
far as I can see) are: Express 2.x, InstallShield 5.x (all versions).
InstallShield is definitely rating this as a high-priority issue (I
don't
work for InstallShield, but I do know that they are giving this a high
priority).
Stefan
ellipse data systems
---------------------------------------------
Followed by a response from "Installshield Software Corp"(?)
---------------excerpt 3--------------------
On Tue, 14 Jul 1998 12:29:49 -0400, Peter Tyson <pty...@speedline.ca>
wrote:
>Do you know if this has been addressed by InstallShield yet? If so what build?
It is going to be addressed in the next Maintenance Releases of both
Express and IS5.1
Stefan
InstallShield Software Corp.
-------------------------------------------------------
This is the supposed overflow I'm referring to. Are these thread
entries bogus? If not what "disk space calculation" are they
referring to?
P.S. - three different Stefans on the same thread?
John Smith
I posted some responses and a zip of some screen shots. Somehow it
didn't end up under this thread. Look for my nym or the subject of
this message elsewhere in this newsgroup. Post any responses under
this message. Sorry.
Stefan Krueger
First let me explain the Stefans (because that's the easiest task): Stefan
Paetow (ellipse data systems) who wrote on 21 May 1998 that he isn't working
for InstallShield - is now an InstallShield employee
(ste...@installshield.co.za). The other one is me, Stefan Krueger
(skru...@installsite.org).
Your screen shots show multiple problems:
Caere1 is definitly a message that has been programmed by the creator of the
setup. And it shows a problem that may seriously affect the setup. Does the
mentioned path exist? Did you try to create this folder yourself (in
Explorer)? Maybe you don't have suffient rights? (Is this NT?)
Caere2 looks like it is coming from InstallShield (built-in error message).
Might be that InstallShield tries to copy opreseng.dll to the directory it
failed to create before. The text of the message could be misleading.
Caere3 is generated by ExeBuilder, the self-extractor. Note that the product
name should have been inserted where the "%s" is. (The latter could be a
fault of the programmer). Examine your temp dir: Where does the TEMP
environment variable point to? (Note that ExeBuilder is a 16 bit program).
Does the temp directory exist in the specified location? Delete all files
and folders in it and try again. Do you have sufficient rights to create
subdirectories under temp?
Generally you should be logged on with administrator rights to install
software. I don't think that this is a disk space issue, but an access
provileges problem. Or a virus (CIH for instance).
Caere1 and 2 show another interesting thing: There appears to be a title bar
("OmniPage Pro 8.0 Setup") that does NOT belong to InstallShield.
InstallShield's is hidden beneath it. I don't know why this is or if this
could be the cause of your trouble.
Did you try to install this software on a different system?
BTW I think that FineReader is better than OmniPage (my opinion).
Stefan Krueger
Independent Setup Consultant
NEU: Deutschsprachiges Forum auf InstallSite
// InstallSite - Resources for setup developers
// http://www.installsite.org (primary site - USA)
// http://installsite.sw.com.sg (mirror site - Singapore)
My reply-to address is invalid to avoid spam.
If you are looking for individual assistance,
like e-mail support, please mail to
in...@installsite.org for support options.
John Smith schrieb in Nachricht <36d6d91c...@news.installshield.com>...
>Hi Stefan,
>
>Here are responses to your questions:
>
<snip>
Frank Levine
Hello Stefan,
Sorry about the names.
>John? Frank? Name confusion everywhere...
>First let me explain the Stefans (because that's the easiest task): Stefan
>Paetow (ellipse data systems) who wrote on 21 May 1998 that he isn't working
>for InstallShield - is now an InstallShield employee
>(ste...@installshield.co.za). The other one is me, Stefan Krueger
>(skru...@installsite.org).
>
>Your screen shots show multiple problems:
>
>Caere1 is definitly a message that has been programmed by the creator of the
>setup. And it shows a problem that may seriously affect the setup. Does the
>mentioned path exist? Did you try to create this folder yourself (in
>Explorer)? Maybe you don't have suffient rights? (Is this NT?)
>
This is Windows98. The folder is the Microsoft Office 97 Startup
folder. I didn't create it myself, it was created when MS Office 97
was installed. You should know that I was installing software onto a
Toshiba laptop system right out of the box, so the existence of virii
is extremely unlikely, seeing that the location was never connected to
the internet (answering some questions that occur further down)
Omnipage uses an entry in the Office startup folder to provide better
interface to MS Office products (so they say).
>Caere2 looks like it is coming from InstallShield (built-in error message).
>Might be that InstallShield tries to copy opreseng.dll to the directory it
>failed to create before. The text of the message could be misleading.
>
It is not copying it to the previous directory. I verified that by
performing the install (without hitch) onto my Win95 system. It is
going either into the Windows\System directory or the Omnipage install
directory (forget which, but I'm dead certain it isn't going to the
Office Startup directory - please trust me on this point).
>Caere3 is generated by ExeBuilder, the self-extractor. Note that the product
>name should have been inserted where the "%s" is. (The latter could be a
>fault of the programmer). Examine your temp dir: Where does the TEMP
>environment variable point to? (Note that ExeBuilder is a 16 bit program).
>Does the temp directory exist in the specified location? Delete all files
>and folders in it and try again. Do you have sufficient rights to create
>subdirectories under temp?
TEMP=C:\Windows\Temp
It exists and is empty before each attempted installation. After
failure it has files in it. Again, this is not NT.
>
>Generally you should be logged on with administrator rights to install
>software. I don't think that this is a disk space issue, but an access
>provileges problem. Or a virus (CIH for instance).
Not a virus (see comments above), not NT.
>
>Caere1 and 2 show another interesting thing: There appears to be a title bar
>("OmniPage Pro 8.0 Setup") that does NOT belong to InstallShield.
>InstallShield's is hidden beneath it. I don't know why this is or if this
>could be the cause of your trouble.
>
>Did you try to install this software on a different system?
>
Yes - it installs fine on my Win95 system.
I have written files to all of the directories that have either had
errors or supposedly been full. After Caere3 said that the TEMP
directory was full, I wrote a 500 MB file to it, just for the hell of
it. No problem.
What is the "disk space calculation" problem that is being addressed
by Installshield, as posted by Stefan Paetow and referred to in my
(John's) previous post?
The previous posts in the original thread relate to problems that
match mine, so it would aid me to know what is being addressed by
Installshield in regards to those problems, so I could ascertain if
pertains to me.
Kevin Harrison
Has this problem been resolved.
I've recently created a similar install to that mentioned.
The install destination for non-system files is to the MSOffice startup
directory.
I'm getting exactly the same problem (reporting insufficient disk space) -
although I didn't get it testing under NT.