Any way to TOTALLY disable Windows 98 Disk Cleanup tool?

"none" wrote in :

[HKEY_CURRENT_USER\Software\Microsoft\Windows\Curre ntVersion\Policies\Explorer]
"NoLowDiskSpaceChecks"=dword:00000001

[HKEY_USERS\.DEFAULT\Software\Microsoft\Windows\Cur rentVersion\Policies\Explorer]
"NoLowDiskSpaceChecks"=dword:00000001

[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Contro l\FileSystem]
"DisableLowDiskSpaceBroadcast"=dword:00000210


Those could work. They're absent on my system and there seem
to be no CLSID's linking them to the cleanuup manager or
anything else, so it's likely down to a core shell file.

No need to deal with the forst of those three branches, it's
just a session-based duplicate of HKEY_USERS\.DEFAULT, or of
a specific user's registry if there had been one.

Where does that setting 00000210 come from? That's not
something anyone can deduce from thin air.

"Lostgallifreyan" wrote in message
. ..
"none" wrote in :

[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Contro l\FileSystem]
"DisableLowDiskSpaceBroadcast"=dword:00000210


Those could work. They're absent on my system and there seem
to be no CLSID's linking them to the cleanuup manager or
anything else, so it's likely down to a core shell file.

No need to deal with the forst of those three branches, it's
just a session-based duplicate of HKEY_USERS\.DEFAULT, or of
a specific user's registry if there had been one.

Where does that setting 00000210 come from? That's not
something anyone can deduce from thin air.

No Idea where the number came from. I pulled it out of a registry on a
laptop with W98. On another system (desktop) it has a value of 3c00 hex,
15360 decimal. What I thought would be the ticket for '98 Guy' is the two
POLICY entries ... but he has it figured out!

It's been sooo long since setting up the systems I forgot how I figured to
put them there. Went through W98 Policy Editor and saw nothing addressing
Low Disk Space. Seems it will remain a mystery! Good news is, I too PACK
partitions to the full sometimes and have no low disk space warnings on any
partition on system (W98, W2K, XP W7). For example, one partition
(encyclopedia DB files is 656MB, 15.4MB free, no errors, defrag even works;
just transferred a 10MB file to it so 5.32MB free, no complaints, no
errors).

In message op.wg46j1ov1r0rdn@dell3100, Harry Vaderchi
writes:
On Sun, 08 Jul 2012 20:12:55 +0100, Bill Blanton
wrote:

On 7/8/2012 14:06, Lostgallifreyan wrote:
"J. P. Gilliver wrote in
:

It's not wrong without context. See you in APIHNA ... (-:


If I let myself take that excuse, the ravening hoardes will be fast led
across the Earth by the four horsemen of the Apocalypse, and all
will be SO
not right with the world that I dare not.... What is APIHNA? API
Hell than
kNows no Abounds? If so, been there, and burned the t-shirt.

A Place In Hell with No Airconditioning?

All 'postrophe's are happy nearly anywhere.

The newsgroup alt.possessive...
--
J. P. Gilliver. UMRA: 1960/1985 MB++G.5AL-IS-P--Ch++(p)Ar@T0H+Sh0!:`)DNAf

"Look, if it'll help you to do what I tell you, baby, imagine that I've got a
blaster ray in my hand." "Uh - you _have_ got a blaster ray in your hand." "So
you shouldn't have to tax your imagination too hard." (Link episode)

none wrote:

"NoLowDiskSpaceChecks"=dword:00000001
"DisableLowDiskSpaceBroadcast"=dword:00000210

Yea, I had already tried those. And a few others.

But it didn't matter, as the drive really had run out of space.

Where does that setting 00000210 come from? That's not
something anyone can deduce from thin air.

No Idea where the number came from.

It comes from he

http://support.microsoft.com/kb/188074

==============
Low Disk Space Notification Received When Drive Is Full

This article was previously published under Q188074

If you do not want to receive this error message, and do not want to use
the Disk Cleanup tool to free disk space, create a DWORD value named
DisableLowDiskSpaceBroadcast in the following registry key:

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Contro l\FileSystem

Set the data value of the DisableLowDiskSpaceBroadcast value to the
appropriate value from the following table:

(table not reproduced in this post)
=================

The bit-positions of that value represent individual logical drives.

I can't say what the value "210" means - unless I know if that's a
decimal value or hex value.

98 Guy wrote in :

none wrote:

"NoLowDiskSpaceChecks"=dword:00000001
"DisableLowDiskSpaceBroadcast"=dword:00000210

Yea, I had already tried those. And a few others.

But it didn't matter, as the drive really had run out of space.

Where does that setting 00000210 come from? That's not
something anyone can deduce from thin air.

No Idea where the number came from.

It comes from he

http://support.microsoft.com/kb/188074

==============
Low Disk Space Notification Received When Drive Is Full

This article was previously published under Q188074

If you do not want to receive this error message, and do not want to use
the Disk Cleanup tool to free disk space, create a DWORD value named
DisableLowDiskSpaceBroadcast in the following registry key:

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Contro l\FileSystem

Set the data value of the DisableLowDiskSpaceBroadcast value to the
appropriate value from the following table:

(table not reproduced in this post)
=================

The bit-positions of that value represent individual logical drives.

I can't say what the value "210" means - unless I know if that's a
decimal value or hex value.


Almost definitely hex, it was preceded by zeros, 8 digits in all. It looks
like a combination of flags, but may well not be.

Nice to know that a single entry can disable the cleanup manager AND the
warnings. Sort of implies that both things are part of one subsystem, likely
the cleanup manager itself, which may be why I don't get warnings even though
I have no registry entry to say otherwise. (I have no cleanup manager at
all...)

"none" wrote in :

No Idea where the number came from. I pulled it out of a registry on a
laptop with W98. On another system (desktop) it has a value of 3c00 hex,

Mystifying. Never mind, I guess I won't need to know any further. I might
do a quick test. Couldn't earlier because I was using the machine for days at
a time encoding stuff, but tomorrow I'll try it while I have easy chances of
shutdown and reboot.