Pop up hard disk too full

  • Thread starter Thread starter Claude
  • Start date Start date
C

Claude

Hi After a crash, I reinstall XP Professionnel and now each time I print it
tell me in ea pop up that my Hard disk is full and I muss make place
HD 149 Go
Used may be 8Go
What can I do?
regards
claude
 
Right click on My Computer, select Manage.... on the following screen, click
on Disk Management
 
Claude said:
Hi After a crash, I reinstall XP Professionnel and now each time I print it
tell me in ea pop up that my Hard disk is full and I muss make place
HD 149 Go
Used may be 8Go
What can I do?

That "feature" is supposed to be useful, but pretty much everyone just finds it incredibly annoying. You can turn it off by getting
a copy of TweakUI for XP. Install that and run it from the Control Panel. In the left pane click the "Taskbar and Start menu"
branch and uncheck the "Warn when low on disk space" box then click the Apply button. Now it won't harass you about disk space.

The problem is that Windows determines whether or not it should display that warning by checking the percentage of free space to
total space. So, even though you have 8GB of free space (which is more than plenty), it still shows the warning because the
percentage is too low.

If you would prefer, there is a way to change the threshold instead of disabling it altogether.


HTH
 
used maybe 8gb, not free space

Alec S. said:
That "feature" is supposed to be useful, but pretty much everyone just
finds it incredibly annoying. You can turn it off by getting
a copy of TweakUI for XP. Install that and run it from the Control Panel.
In the left pane click the "Taskbar and Start menu"
branch and uncheck the "Warn when low on disk space" box then click the
Apply button. Now it won't harass you about disk space.
The problem is that Windows determines whether or not it should display
that warning by checking the percentage of free space to
total space. So, even though you have 8GB of free space (which is more
than plenty), it still shows the warning because the
 
DL said:
used maybe 8gb, not free space

Um… 8GB used, 141GB free? Then either the threshold is screwed up (it's complaining when there's less than 95% free!), or there's
something else going on.
 
How much space is free? I ask because space may be lost between
"used" and "free" (ADS, file system corruption)

What caused the original crash, and why was it necessary to "just"
re-install? Problems often persist when folks paper over them...
That "feature" is supposed to be useful, but pretty much everyone
just finds it incredibly annoying.

That's because it's so badly implimented.
You can turn it off by getting a copy of TweakUI for XP.
The problem is that Windows determines whether or not it should display
that warning by checking the percentage of free space to total space.

Same dumb logic used to determine IE cache allocations, as well as
pagefile size (e.g. "128M RAM? Well, you'd never have to swap more
than 192M to disk, would you?")

More to the point, there's zero awareness that different HD volumes
might be used differently.

I can see it making sense to reserve (say) the size of the pagefile
(on the basis that a similar size of temp files may be needed) for C:,
and the size of a CD or DVD wherever "CD Burning" is located.

But only the user can know how much space is needed elsewhere, and
without the automatic disk-hogging effects of Temp etc. there may be
no reason to alert at all, or just alert if SR hits the wall there.

OTOH, I may want an earlier warning. Say I devote a 2G volume to
holding the last 5 automatic backups of whatever; I'd need enough free
space to create a new one before deleting the oldest - say 22% of
volume size, as opposed to an absolute size.
If you would prefer, there is a way to change the threshold instead of disabling it altogether.

Can you selectively enable this (or change the threshold) for
different volumes?


------------ ----- --- -- - - - -
Drugs are usually safe. Inject? (Y/n)
 
cquirke (MVP Windows shell/user) said:
How much space is free? I ask because space may be lost between
"used" and "free" (ADS, file system corruption)

149 - 8 = 141GB :p

ADS is not likely to eat up 140GB. I suppose the free space indicator in the boot sector could be wrong, but that's usually updated
often so, it shouldn't matter. Plus, I don't believe that Windows uses that at all.


What caused the original crash, and why was it necessary to "just"
re-install? Problems often persist when folks paper over them...

"Just"? When did he say that he "just installed"?

How is reinstalling considered "papering over a problem"? It gives you a fresh start. A crash does not necessarilly mean there's a
problem. Windows crashes all the time, for various reason. Reinstallation lets you start fresh. Perhaps Claude had installed some
bad combination of programs at some point in the past, or a program that was written badly, or got infected with something, or just
succumbed to WinRot. Reinstalling gave him a fresh copy to work with and he is now experiencing a problem. Whatever cause the
crash is not necessarilly going to return, especially for most users who don't restore their systems to the way it was, particularly
if they had just transiently installed the bad app etc. His problem is not whatever caused the original crash, that's long gone,
his problem is the running-out-of-space warning (which may not even be anymore, since he has not responded.)

It really peaves me when people try to help others with problems that no longer apply instead of addressing the issue at hand.


That's because it's so badly implimented.

Is there a good way to implement it? Actually:

Can you selectively enable this (or change the threshold) for
different volumes?

Nope, to both threshold and enabled status. :(

If it were configurable it would be much more handy. I would like warnings on some drives at some thresholds (percentage or
absolute), but for others I do not. Unfortunately it is currently a one-size-fits-ALL mechanism.
 
Hi The crash was simply the HD Failed after 6 months. So I have a new HD.
I have a disk with 149go
I already put in the register a ligne to stop those type of warning in
"HKEY_CURRENT_USER\Software\Microsoft\Windows\Currentversion\Policies\Explorer"
I put a New DWORD with the command NoLowDiskSpaceChecks.
When I run Tweak, the "Warn when low on disk space " is uncheked.
This happend only when I start printing.
Regards
claude
 
Claude said:
Hi The crash was simply the HD Failed after 6 months. So I have a new HD.
I have a disk with 149go
I already put in the register a ligne to stop those type of warning in
"HKEY_CURRENT_USER\Software\Microsoft\Windows\Currentversion\Policies\Explorer"
I put a New DWORD with the command NoLowDiskSpaceChecks.
When I run Tweak, the "Warn when low on disk space " is uncheked.
This happend only when I start printing.
Regards


Ah, see, it's not Claude's fault that he needed to reinstall Windows, nor was it a problem that he should waste time worrying about
since it is passed (unless it was an _unexplained_ premature failure in which case he should investigate the hardware; nothing
software related here).

And yes, TweakUI will have that box unchecked because that is the registry entry which it manipulates; if you've already set it,
then it's done.
 
Claude said:
What is done?

When you use TweakUI to change that setting, it alters that registry entry. When it starts, TweakUI reads that registry entry and
either checks, or unchecks the box depending on the value. If you've changed it manually, then TweakUI will reflect that.

The windows still appeares

You mean you're still getting "low on space" warnings? Try using TweakUI instead of doing it manually. Run TweakUI, toggle the
check, click OK. Run it again and toggle it again. Run it a third time if it is now checked. TweakUI may be doing more than just
altering the entry, it may also be issuing an API call to let the system know that the setting has changed, which is not done when
you do it manually. Have you rebooted since you made the change?
 
Hi The crash was simply the HD Failed after 6 months. So I have a new HD.
I have a disk with 149go

Ahhh. What SP level of XP did you install?
- XP Gold (SP0) is unsafe for > 137G
- XP SP1 is safe to install > 137G, but can corrupt HD later
- SP SP2 is fine for > 137G

Specifically, if you have a system crash in XP SP1, the code that
writes the crash dump is not OK for > 137G and may corrupt the hard
drive. Same may or may not apply to hibernate (can't remember)

Only when printing, eh?

Printing can create large temp files, but if you have 8G free, it's
not likely to be an issue such that the printing process would alert.

If you can create a large file or few (try copying some stuff around)
and no alerts, then maybe the printer sware's getting it wrong -
especially if it's really ancient printer sware that may "wrap
araound" at 64M or something. It's highly unlikely such drivers would
run on XP at all, though, or that XP would let them install.

Sure sounds wierd...


------------ ----- --- -- - - - -
Drugs are usually safe. Inject? (Y/n)
 
cquirke (MVP Windows shell/user) said:
Ahhh. What SP level of XP did you install?
- XP Gold (SP0) is unsafe for > 137G
- XP SP1 is safe to install > 137G, but can corrupt HD later
- SP SP2 is fine for > 137G

I remember hearing a lot of concerns about drive size several years ago when the bigger ones started coming out, but heard few
actual problems; it's been more theoretical than practical. For the most part it's been about the hardware rather than the
software, if the hardware supports it, the software doesn't usually have problems. I've never had problems with anything no matter
how big the drive. My motherboards have both supported large drives and I've managed to successfully work with them in XP, 2000,
ME, 98, and even DOS. I suspect that it's not so much the drive size as the partition size that would be the problem. I partition
the crap out of my drives but a lot of people just use a single giant one. In that case, if the OS doesn't use 48+ bit pointers,
then it could cause trouble, but if it's partitioned, it shouldn't be a problem. On the other hand, I use DiskDoctor in DOS and it
can access the entire contents of the drive even though it's well over 137GB.
 
So!
I did what you said Alec, doen't make any change.
may be I have to do with it! another Window bug
regards
claude
 
Back
Top