Jump to content


This is a ready-only archive of the InstallSite Forum. You cannot post any new content here. / Dies ist ein Archiv des InstallSite Forums. Hier können keine neuen Beiträge veröffentlicht werden.
Photo

Not enough free Disk Space Error


9 replies to this topic

loorie

loorie
  • Members
  • 10 posts

Posted 23 July 2003 - 04:29



Hi,

Some of my clients are reporting me :

Though they have enough disk space on their computers,
My Install Kit is making Error that there is not enough Disk space.
This Error occurs at all kinds of OS.

I tried to find out here and there, but couldn't find clear solutions.

If someone has met silmilar problem, please share the solution with me.



Taco Bell

Taco Bell

    IS6 Expert

  • Moderators
  • 1,281 posts

Posted 23 July 2003 - 14:42

Exactly what code are you using to calculate the free and required disk space?
user posted image

loorie

loorie
  • Members
  • 10 posts

Posted 25 July 2003 - 09:09

I didn't add any code to calculate free disk space or space required...

I think it's included in the default install process.

To avoid this problem i tried,
1. Check if TEMP, TMP forder is set as a hidden folder.
2. Delete Everything in the TEMP folder.
3. Enlarge Virtual Memory.

But it failed. Some of my clients told that it worked by reboot...;;

I have to fix this problem, because there are quite many reports of this problem..T.T

Am i the only one who's suffering with this kind of problem?....hu...

TacoBell, Thanx for Reply.




Taco Bell

Taco Bell

    IS6 Expert

  • Moderators
  • 1,281 posts

Posted 25 July 2003 - 23:35

Yeah I figured as such. In which case, you must be using the default code in the OnFirstUIBeforeN event then. I'm not exactly sure what this code does though, so I'll check it out and let you know.

By the way, increasing the virtual memory will not help this. That's just extra memory and will actually make you have less free space, not more.
user posted image

loorie

loorie
  • Members
  • 10 posts

Posted 27 July 2003 - 15:35




Thanks for your kindness. TacoBell.

I'm very anxious to hear good news(like 'I found the reason!' biggrin.gif ) from you.





Taco Bell

Taco Bell

    IS6 Expert

  • Moderators
  • 1,281 posts

Posted 28 July 2003 - 19:28

I still have to check the default code, but make sure there's enough space on C: since this is not only used to apply Common Files and system files, but also as the temporary location for the setup.

I get a few calls from customers myself when they C: drive is low on space. Had one today as a matter of fact. wink.gif

Edited by TacoBell00, 28 July 2003 - 19:29.

user posted image

loorie

loorie
  • Members
  • 10 posts

Posted 29 July 2003 - 03:56



Yes, I'm sure there is enough space on C:.

I found some comments about this in InstallShield Community.

There was an answer that DiskSpaceError occurs if <TARGETDIR> is not _valid_.
But I'm confused by the word 'valid'.

What does 'valid' mean? The directory should already exist? As far as i know,
if <TARGETDIR> is not in System, InstallShield automatically creates the specified directory.

Do you have any thoughts about this?

Time is running, but still in the fog... huh.. ...T.T





Stefan Krueger

Stefan Krueger

    InstallSite.org

  • Administrators
  • 13,269 posts

Posted 29 July 2003 - 07:02

InstallShield will check for available space in TARGETDIR. If TARGETDIR is not set, or points to a location with not enough space, or a location that's not writabvle (e.g. the CD drive) you'll get this error. I'm not sure whether TARGETDIR must exist at thiat point, but you can easily try that...

loorie

loorie
  • Members
  • 10 posts

Posted 29 July 2003 - 10:03



Thanks for your advice, Krueger.

Then, can this be solved by script coding?
Or should i leave the code and give privately help to those who meet this problem?

What kind of advices can be helpful to them?

PS. I'm very qurious about the client who solved this by rebooting System.... rolleyes.gif
Can this be a appropriate solution?

Thanks in advance.





Taco Bell

Taco Bell

    IS6 Expert

  • Moderators
  • 1,281 posts

Posted 17 August 2003 - 02:21

Sorry for the late reply, but I finally got around to checking the default code for the OnFirstUIBefore event.

For a non-custom setup (e.g. typical, compact) it calls ComponentCompareSizeRequired to test the default value for TARGETDIR of PROGRAMFILES ^ @COMPANY_NAME ^ @PRODUCT_NAME. The user isn't asked for a destination until AFTER this check has been made.

For a custom setup, it uses the dialog's built-in space checking against the same default value for TARGETDIR.

Therefore it's possible to get different results depending on the setup type.

I personally would modify the default code to do Dlg_SdAskDestPath _BEFORE_ Dlg_SetupType. That way it's requiring the user to have sufficient space where he/she will actually being the software and not just on the default Program Files partition.
user posted image