Not enough free Disk Space Error
Posted 23 July 2003 - 04:29
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.
Posted 23 July 2003 - 14:42
Posted 25 July 2003 - 09:09
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.
Posted 25 July 2003 - 23:35
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.
Posted 27 July 2003 - 15:35
Thanks for your kindness. TacoBell.
I'm very anxious to hear good news(like 'I found the reason!' ) from you.
Posted 28 July 2003 - 19:28
I get a few calls from customers myself when they C: drive is low on space. Had one today as a matter of fact.
Edited by TacoBell00, 28 July 2003 - 19:29.
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
Posted 29 July 2003 - 07:02
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....
Can this be a appropriate solution?
Thanks in advance.
Posted 17 August 2003 - 02:21
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.