sys.resource in XP HOME

[Guest]

Hi.
I am using WINXP home
P4
40G HDD, 20G free
256Mb RAM
Dell

I am trying to load a small software prog. (40Mb) stand alone no internet
access needed
I receive an error messege: There is not enough disk space
clear disk space or modify prog.

I have run all utilities (AV,defrag,cleared temp folders, cleared restore
points,adaware, ect)
checked AV settings, firewall settings ect.

Is there something in XP home that would cause it to report a false sys./
HDD resource ?

Is there something that I have overlooked?

Thanks for all help.

 

[_Vanguard_]

Hi.
I am using WINXP home
P4
40G HDD, 20G free
256Mb RAM
Dell

I am trying to load a small software prog. (40Mb) stand alone no
internet
access needed
I receive an error messege: There is not enough disk space
clear disk space or modify prog.

I have run all utilities (AV,defrag,cleared temp folders, cleared
restore
points,adaware, ect)
checked AV settings, firewall settings ect.

Is there something in XP home that would cause it to report a false
sys./
HDD resource ?

Is there something that I have overlooked?

Thanks for all help.

Gee, 40MB is now considered small.

You never bothered to actually mention WHAT program it is that you are
trying to install. Maybe it is some ancient and perhaps DOS-mode
program that hasn't a clue on how to handle large drives over 2 or 4GB
in size. Some old games are like that. They use too small a variable
(in bit length) to compute the remaining or free space on a disk, end up
overflowing (wrapping), and the value gets truncated to look much
smaller than it really is. In effect, they are doing modulo arithmetic
in determining the free disk space.

The cure is to create enough free space so the modulo-effected
computation returns a value that the program will accept. Sometimes
this means deleting files, like from your %temp% folder, the browser's
cache, or other fluff. Sometimes this requires that you create a dummy
directory and copy in a bunch of folders to move the floor (of used disk
space) past the 2GB or 4GB boundary so the modulo arithmetic ends up
seeing the next span of 2GB or 4GB as being free. You are trying to
lower the floor so it is farther away from the boundary whether that be
farther below the boundary or just past it.

If you had actually mentioned the program then someone else familiar
with it might have an answer for you. If it is your program then you
need to fix the code for the algorithm used to compute the free disk
space, or get a better library that you happen to be calling from your
program to do the computation. If it is vertical market or custom
software for which you don't have the source code and you suspect no one
else uses then you need to contact the developer to ask why their
product reports bogus errors regarding free disk space.