Any way to TOTALLY disable Windows 98 Disk Cleanup tool?

I have about 20 gb free on my 700 gb D: drive, and I'm running up
against the 3% free-space limit where Windows-98 apparently seems to
generate a "disk-full" message and wants to invoke the Disk Cleanup
tool.

I've already looked at these:

http://support.microsoft.com/?kbid=193683
http://www.annoyances.org/exec/show/article03-102
http://support.microsoft.com/default...;EN-US;q188074

and they don't solve the problem at all.

On the Settings tab of the Disk Cleanup utility I have the "if this
drive runs low on disk space, automatically run Disk Cleanup" check-box
cleared.

In the registry, the "DisableLowDiskSpaceBroadcast" was already set to
12 (which means that the warning for both drive C and D should be
disabled).

I've seen lots of non-microsoft references to this "3%" rule, but
nothing from microsoft itself.

I also don't see anywhere to change this from 3% to something else.

But in any case, it seems that the system is not obeying any of these
settings to ignore the 3% rule.

Anyone know if there's a way I can really turn this nuisance off?

98 Guy wrote in :

I have about 20 gb free on my 700 gb D: drive, and I'm running up
against the 3% free-space limit where Windows-98 apparently seems to
generate a "disk-full" message and wants to invoke the Disk Cleanup
tool.

I've already looked at these:

http://support.microsoft.com/?kbid=193683
http://www.annoyances.org/exec/show/article03-102
http://support.microsoft.com/default...8074&ID=KB;EN-
US;q188074

and they don't solve the problem at all.

On the Settings tab of the Disk Cleanup utility I have the "if this
drive runs low on disk space, automatically run Disk Cleanup" check-box
cleared.

In the registry, the "DisableLowDiskSpaceBroadcast" was already set to
12 (which means that the warning for both drive C and D should be
disabled).

I've seen lots of non-microsoft references to this "3%" rule, but
nothing from microsoft itself.

I also don't see anywhere to change this from 3% to something else.

But in any case, it seems that the system is not obeying any of these
settings to ignore the 3% rule.

Anyone know if there's a way I can really turn this nuisance off?


I have no immediate answer but I'll try to come up with something. That being
because I know I don't have that trouble,I remember it from distant past, but
now, I can get a disk to the last byte, some process report's disk full, and
it just stops. A tad annoying when encoding a movie overnight, but that's
about it. I guess that response is what you want from the system too. I
can't remember exactly what happens to do it. For now, perhaps disable all
the recycle bins as best possible, that isn't really the answer, but it's a
vaguely similar approach, and may even be related.

Maybe look at TweakUI, that might have some control over it.

98 Guy wrote in :

Anyone know if there's a way I can really turn this nuisance off?


Another thought: 98-Lite, which likely made the cleanup tool modular. I need
to eat and sleep but tomorrow (if you have no answer earlier), I'll do an
install watch on that module and find out what has to be removed to stop it
doing stuff.

98 Guy wrote:

I have about 20 gb free on my 700 gb D: drive, and I'm running up
against the 3% free-space limit where Windows-98 apparently seems to
generate a "disk-full" message and wants to invoke the Disk Cleanup
tool.

I've already looked at these:

http://support.microsoft.com/?kbid=193683
http://www.annoyances.org/exec/show/article03-102
http://support.microsoft.com/default...8074&ID=KB;EN-
US;q188074

and they don't solve the problem at all.

On the Settings tab of the Disk Cleanup utility I have the "if this
drive runs low on disk space, automatically run Disk Cleanup" check-box
cleared.

In the registry, the "DisableLowDiskSpaceBroadcast" was already set to
12 (which means that the warning for both drive C and D should be
disabled).

I've seen lots of non-microsoft references to this "3%" rule, but
nothing from microsoft itself.

I also don't see anywhere to change this from 3% to something else.

But in any case, it seems that the system is not obeying any of these
settings to ignore the 3% rule.

Anyone know if there's a way I can really turn this nuisance off?

what I would do:
- back up the .exe file
- copy some other harmless app over it (I have programs that specifically do
nothing, for just this sort of situation; I can post one if you'd like)

Problem solved.

--
What a miserable looking mud ball.

Auric__ wrote:

what I would do:
- back up the .exe file
- copy some other harmless app over it (I have programs that
specifically do nothing, for just this sort of situation;
I can post one if you'd like)

Problem solved.

It's not that simple.

I was expanding a .rar file that I had just downloaded, and winrar stops
the expansion and gives an error saying the disk is full.

So whether or not the disk cleanup tool runs is sort of not the issue.

The issue is telling windows to stop monitoring free disk space looking
for this 3% situation.

98 Guy wrote in :

So whether or not the disk cleanup tool runs is sort of not the issue.

The issue is telling windows to stop monitoring free disk space looking
for this 3% situation.



There's some registry entries for it, with CLSID's for shell tasks. Also two DLL's as well as the exe.
Assuming that the cleanup module includes the monitoring process and is all you need to remove, try this:

Remove:
[C:\WINDOWS]
CLEANMGR.EXE
[C:\WINDOWS\SYSTEM]
DATACLEN.DLL
OCCACHE.DLL

Merge to registry:
REGEDIT4

[-HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\Curr entVersion\Setup\OptionalComponents\CleanMgr]
[-HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\Curr entVersion\explorer\MyComputer\CleanupPath]

[-HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\Curr entVersion\explorer\VolumeCaches\Recycle Bin]
[-HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\Curr entVersion\explorer\VolumeCaches\Downloaded Program Files]
[-HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\Curr entVersion\explorer\VolumeCaches\Old files in root of drive]
[-HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\Curr entVersion\explorer\VolumeCaches\Temporary files]
[-HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\Curr entVersion\explorer\VolumeCaches\Setup files]
[-HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\Curr entVersion\explorer\VolumeCaches\Delete Windows 98 uninstall information]
;There may also be Internet Explorer related entries there, but if worthless, consider deleting the whole branch:
;[-HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\Curr entVersion\explorer\VolumeCaches]

[-HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\Curr entVersion\Internet Settings\ActiveX Cache]
[-HKEY_LOCAL_MACHINE\Software\CLASSES\CLSID\{5ef4af3 a-f726-11d0-b8a2-00c04fc309a4}]
[-HKEY_LOCAL_MACHINE\Software\CLASSES\CLSID\{88C6C38 1-2E85-11D0-94DE-444553540000}]
[-HKEY_LOCAL_MACHINE\Software\CLASSES\CLSID\{8369AB2 0-56C9-11D0-94E8-00AA0059CE02}]
[-HKEY_LOCAL_MACHINE\Software\CLASSES\CLSID\{C0E13E6 1-0CC6-11d1-BBB6-0060978B2AE6}]

98 Guy wrote in :

I was expanding a .rar file that I had just downloaded, and winrar stops
the expansion and gives an error saying the disk is full.


I put the WinRar cache on drive G: (don't ask, long story...). The upshot is
that when I have less than 32768 bytes, WinRar borks and the system reports
disk full as a likely reason. (I think WinRar deals in 32768-byte chunks,
because my G: drive cluster size is only 8192 bytes). The answer for
immediate need is WinRar's 'Extract To' command, which bypasses its cache.

Lostgallifreyan wrote:

I was expanding a .rar file that I had just downloaded, and
winrar stops the expansion and gives an error saying the
disk is full.

The answer for immediate need is WinRar's 'Extract To' command,
which bypasses its cache.

How exactly could that be relavent in my situation?

I have a 32 gb C drive (1 gb free) and a 700 gb D drive (22 gb free).

Oddly enough, each of them are 97% full.

Any attempt to copy even a small file (a few hundred kb) from the C to
the D drive results in this message:

==================
Error Copying File
==================
Cannot create or replace (file-name). There is not enough free
disk space.

Delete one or more files to free disk space, and then try again.

To free space on this drive by deleteing old or unnecessary
files, click "Disk Cleanup".
==================

There are 2 buttons displayed in that message - Disk Cleanup and OK. I
note that the Disk Cleanup tool is not automatically being invoked in
this situation, so that setting seems to be working.

Opening up a dos window and typing the command "chkdsk d:" gives this:

=========================================
732,395,680 kilobytes total disk space
23,095,744 kilobytes free

32,768 bytes in each allocation unit
22,887,365 total allocation units on disk
721,742 available alloation units on disk
==========================================

98 Guy wrote in :

The answer for immediate need is WinRar's 'Extract To' command,
which bypasses its cache.

How exactly could that be relavent in my situation?



I already gave you a full answer to your problem. That extra detail was
specific only to WinRar, as I said.

98 Guy wrote in :

I have a 32 gb C drive (1 gb free) and a 700 gb D drive (22 gb free).

Oddly enough, each of them are 97% full.

Any attempt to copy even a small file (a few hundred kb) from the C to
the D drive results in this message:

==================
Error Copying File
==================
Cannot create or replace (file-name). There is not enough free
disk space.

Delete one or more files to free disk space, and then try again.

To free space on this drive by deleteing old or unnecessary
files, click "Disk Cleanup".
==================


Note that the cleanup tool is associated with volume caches for temp files
and recycle bins. The main tool just does the cleanup guided by the registry
entries for filt types and locations. What you need to do is use that reg
file data I posted earlier, to disable the shell processes that watch for
that space. You'll also need to make sure your temp files have space or
you'll still end upo with disk-full warmings. The difference is that they'll
be real warnings instead of assumptions that you want that 3% for cache
space.