Vanishing hard disk space

  • Thread starter Thread starter JoeSpareBedroom
  • Start date Start date
If I could stop the phones from ringing.....

Stay tuned, maybe until the weekend. And check CNN news every so often for a
story about a man murdering a computer with a handgun.

Yep - something is haywire!

Let's say you really do have 4GB of RAM as msinfo32 says and your PF
is system managed. That would mean that XP will want to create a PF
of ~1.5 times the RAM which would be about 6GB.

This I corroborate on another system that I know has 4GB of RAM and
system managed PF - all is well in msinfo32.

I do not know what XP would do if it wanted to make a PF of that size
and did not have enough HDD to do so but I would like to know (and
can't experiment right now).

Near as I can tell, your Mother Board supports a maximum of 2GB of
memory (2 slots/2 sticks), so what msinfo32 says is most curious and
is differs from My Computer Properties. Never seen that.

Now I think maybe you really do have 512MB in one or two slots (which
you can verify visually), the msinfo32 PF display info would then be
almost correct at about 1+GB and heaven forbid, msinfo32 is confused
about how much RAM you really have installed, but you are still on
SP2...

I have yet to create the situation where XP will want to increase the
size of an inadequate PF to see if anything shows up in the Event Log
but maybe somebody else can help generate that situation and see what
happens and then you can look for such an event in your log file
around the time of your mystery.

Do you recall seeing any such messages pop up from the Taskbar (close
to the system time) around the time of your mystery?

If XP needs to increase the size of the PF and has no RAM, it will
only be able to do it by taking available HDD space and I don't know
if it will "give it back" or not. If you only have 4GB HDD free and
XP decides it needs another GB or two (temporarily) what will happen I
wonder?

If XP takes it, you will loose a bunch of HDD space for some amount of
time, and then when XP is done, it may give it back. With your low
HDD space that could be a big percentage of free space. Available,
gone, available...

I will work on that just because it is making me mad now.
 
If I could stop the phones from ringing.....

Stay tuned, maybe until the weekend. And check CNN news every so often for
a
story about a man murdering a computer with a handgun.

Yep - something is haywire!

Let's say you really do have 4GB of RAM as msinfo32 says and your PF
is system managed. That would mean that XP will want to create a PF
of ~1.5 times the RAM which would be about 6GB.

This I corroborate on another system that I know has 4GB of RAM and
system managed PF - all is well in msinfo32.

I do not know what XP would do if it wanted to make a PF of that size
and did not have enough HDD to do so but I would like to know (and
can't experiment right now).

Near as I can tell, your Mother Board supports a maximum of 2GB of
memory (2 slots/2 sticks), so what msinfo32 says is most curious and
is differs from My Computer Properties. Never seen that.

Now I think maybe you really do have 512MB in one or two slots (which
you can verify visually), the msinfo32 PF display info would then be
almost correct at about 1+GB and heaven forbid, msinfo32 is confused
about how much RAM you really have installed, but you are still on
SP2...

I have yet to create the situation where XP will want to increase the
size of an inadequate PF to see if anything shows up in the Event Log
but maybe somebody else can help generate that situation and see what
happens and then you can look for such an event in your log file
around the time of your mystery.

Do you recall seeing any such messages pop up from the Taskbar (close
to the system time) around the time of your mystery?

If XP needs to increase the size of the PF and has no RAM, it will
only be able to do it by taking available HDD space and I don't know
if it will "give it back" or not. If you only have 4GB HDD free and
XP decides it needs another GB or two (temporarily) what will happen I
wonder?

If XP takes it, you will loose a bunch of HDD space for some amount of
time, and then when XP is done, it may give it back. With your low
HDD space that could be a big percentage of free space. Available,
gone, available...

I will work on that just because it is making me mad now.
================

One problem here was my typing. I should've just said "1/2 GIG of RAM",
which is confirmed by Belarc Advisor (a wonderful utility):

448 Megabytes Installed Memory

Slot 'A0' has 4096 MB
Slot 'A1' is Empty

That's as much info as I can provide at the moment without opening the case.
 
Gerry said:
If you have sudden changes in free disk space then inevitably the file(s)
are fragmented. These show up in a Disk Defragmenter report even when they
otherwise are often not disclosed in other information sources.

Open Disk Defragmenter and click on Analyse. Select View Report and
click on Save As and Save. Now find VolumeC.txt in your My Documents
Folder and post a copy.

Here's the defrag report. HD Tune to follow later, or tomorrow. Defrag was
run in safe mode, by the way.

Volume (C:)
Volume size = 18.61 GB
Cluster size = 4 KB
Used space = 14.90 GB
Free space = 3.72 GB
Percent free space = 19 %

Volume fragmentation
Total fragmentation = 10 %
File fragmentation = 20 %
Free space fragmentation = 1 %

File fragmentation
Total files = 80,841
Average file size = 368 KB
Total fragmented files = 53
Total excess fragments = 7,406
Average fragments per file = 1.09

Pagefile fragmentation
Pagefile size = 671 MB
Total fragments = 100

Folder fragmentation
Total folders = 6,774
Fragmented folders = 1
Excess folder fragments = 0

Master File Table (MFT) fragmentation
Total MFT size = 110 MB
MFT record count = 87,833
Percent MFT in use = 78 %
Total MFT fragments = 6

--------------------------------------------------------------------------------
Fragments File Size Files that cannot be defragmented
79 19 MB \Documents and
Settings\User\OE\Messages\Inbox.dbx
216 19 MB \System Volume
Information\_restore{0585745D-2457-4D9E-A5E8-35AFCD216CCE}\RP1264\snapshot\Repository\FS\OBJECTS.DATA
61 19 MB \Documents and
Settings\User\OE\Messages\Grocery.dbx
28 21 MB \Documents and Settings\User\OE\Messages\Ann
(1).dbx
162 21 MB \System Volume
Information\_restore{0585745D-2457-4D9E-A5E8-35AFCD216CCE}\RP1264\snapshot\_REGISTRY_MACHINE_SOFTWARE
172 21 MB \System Volume
Information\_restore{0585745D-2457-4D9E-A5E8-35AFCD216CCE}\RP1263\snapshot\_REGISTRY_MACHINE_SOFTWARE
53 26 MB \Documents and Settings\All
Users\Application Data\Apple Computer\Installer Cache\iTunes
7.6.1.9\iTunes.msi
90 26 MB \WINDOWS\Installer\8cbc8f.msp
142 27 MB \Documents and Settings\User\My Documents\My
Music\The Allman Brothers Band\At Fillmore East\You Don't Love Me.mp3
37 27 MB \Program Files\Common
Files\Intuit\TurboTax\TY08\PER\MSI\WinPerReleaseEngine.msi
400 28 MB \Program Files\Common Files\Symantec
Shared\Security Center\SymWSC-2005.1.2.20-2007-08-22-22-18-23-515.dmp
85 31 MB \Documents and Settings\User\My Documents\My
Music\What Is Hip.wma
237 31 MB \Documents and Settings\User\Local
Settings\Application Data\Apple
Computer\QuickTime\downloads\14\10\ea2ef625-8e852977-d76800e3-27f572f3.qtch
18 32 MB \Documents and
Settings\User\OE\Messages\Music.dbx
517 32 MB \Program Files\Java\jre1.5.0_09\lib\rt.jar
249 33 MB \WINDOWS\Downloaded
Installations\{59C4F14F-7590-45FC-BE9F-A67AB3590709}\QuickTimeInstaller.exe
81 35 MB \PARA\CODES\ParaCodes.zip
215 37 MB \Documents and Settings\User\Application
Data\Mozilla\Firefox\Profiles\0b92y4wv.default\places.sqlite
38 38 MB \Documents and
Settings\User\OE\Messages\TheKid (1).dbx
88 41 MB \Eval\2003_FSM.zip
652 41 MB \Program Files\Java\jre1.6.0_07\lib\rt.jar
296 41 MB \Documents and Settings\User\My Documents\My
Music\Dave Brubeck-Blue Rondo a la Turk.wma
230 41 MB \Attic\Security\zapSetup_91_008_000_en.exe
52 50 MB \Documents and Settings\User\My Documents\My
Music\Squib Cakes.wma
613 59 MB \Documents and Settings\User\Local
Settings\Application
Data\Mozilla\Firefox\Profiles\0b92y4wv.default\urlclassifier3.sqlite
20 89 MB \Program Files\Adobe\Reader 8.0\Setup
Files\{AC76BA86-7AD7-1033-7B44-A81300000003}\Data1.cab
54 96 MB \Documents and
Settings\User\OE\Messages\Deleted Items.dbx
225 97 MB \Documents and
Settings\User\OE\Messages\SoulOnTap.dbx
1,503 161 MB \Documents and
Settings\User\Desktop\MOA2009USExp.exe
600 671 MB
\RECYCLER\S-1-5-21-1644491937-413027322-839522115-1003\Dc1.sys
 
Select the Info tabs and place the cursor on the drive under Drive
letter and then double click the two page icon ( copy to Clipboard )
and copy into a further message.

From info tab:

HD Tune: WDC WD200BB-75DEA0 Information

Firmware version : 05.03E05
Serial number : WD-WMAD21049096
Capacity : 18.6 GB (~20.0 GB)
Buffer size : 2048 KB
Standard : ATA/ATAPI-5
Supported mode : UDMA Mode 5 (Ultra ATA/100)
Current mode : UDMA Mode 5 (Ultra ATA/100)

S.M.A.R.T : yes
48-bit Address : no
Read Look-Ahead : yes
Write Cache : yes
Host Protected Area : yes
Device Configuration Overlay : yes
Automatic Acoustic Management: yes
Power Management : yes
Advanced Power Management : no
Power-up in Standby : no
Security Mode : no
Firmware Upgradable : yes

Partition : 1
Drive letter : C:\
Label :
Capacity : 19061 MB
Usage : 80.07%
Type : NTFS
Bootable : Yes
 
Select the Health tab and then double click the two page icon ( copy to
Clipboard ) and copy into a further message. Make sure you do a full
surface scan with HD Tune.


From health tab:

HD Tune: WDC WD200BB-75DEA0 Health

ID Current Worst ThresholdData Status
(01) Raw Read Error Rate 200 198 51 0 Ok
(03) Spin Up Time 95 94 21 2625 Ok
(04) Start/Stop Count 98 98 40 2505 Ok
(05) Reallocated Sector Count 200 200 140 0 Ok
(07) Seek Error Rate 100 253 51 0 Ok
(09) Power On Hours Count 73 73 0 20001 Ok
(0A) Spin Retry Count 100 100 51 0 Ok
(0B) Calibration Retry Count 100 100 51 0 Ok
(0C) Power Cycle Count 98 98 0 2173 Ok
(C4) Reallocated Event Count 200 200 0 0 Ok
(C5) Current Pending Sector 200 200 0 0 Ok
(C6) Offline Uncorrectable 200 200 0 0 Ok
(C7) Ultra DMA CRC Error Count 200 253 0 0 Ok
(C8) Write Error Rate 200 200 51 0 Ok

Power On Time : 20001
Health Status : Ok
 
Surface scan results:
HD Tune: WDC WD200BB-75DEA0 Error Scan

Scanned data : 19065 MB
Damaged Blocks : 0.0 %
Elapsed Time : 9:03
======================

Benchmark results:

HD Tune: WDC WD200BB-75DEA0 Benchmark

Transfer Rate Minimum : 4.7 MB/sec
Transfer Rate Maximum : 46.4 MB/sec
Transfer Rate Average : 38.3 MB/sec
Access Time : 18.6 ms
Burst Rate : 82.1 MB/sec
CPU Usage : 3.3%
=====================

If there aren't any clear answers by Saturday, I'm going to use this
utility.

http://i27.photobucket.com/albums/c... Paul Bass/SmileWaitForFlash.jpg?t=1262291037
 
JoeSpareBedroom said:
Yep - something is haywire!

Let's say you really do have 4GB of RAM as msinfo32 says and your PF
is system managed. That would mean that XP will want to create a PF
of ~1.5 times the RAM which would be about 6GB.

This I corroborate on another system that I know has 4GB of RAM and
system managed PF - all is well in msinfo32.

I do not know what XP would do if it wanted to make a PF of that size
and did not have enough HDD to do so but I would like to know (and
can't experiment right now).

Near as I can tell, your Mother Board supports a maximum of 2GB of
memory (2 slots/2 sticks), so what msinfo32 says is most curious and
is differs from My Computer Properties. Never seen that.

Now I think maybe you really do have 512MB in one or two slots (which
you can verify visually), the msinfo32 PF display info would then be
almost correct at about 1+GB and heaven forbid, msinfo32 is confused
about how much RAM you really have installed, but you are still on
SP2...

I have yet to create the situation where XP will want to increase the
size of an inadequate PF to see if anything shows up in the Event Log
but maybe somebody else can help generate that situation and see what
happens and then you can look for such an event in your log file
around the time of your mystery.

Do you recall seeing any such messages pop up from the Taskbar (close
to the system time) around the time of your mystery?

If XP needs to increase the size of the PF and has no RAM, it will
only be able to do it by taking available HDD space and I don't know
if it will "give it back" or not. If you only have 4GB HDD free and
XP decides it needs another GB or two (temporarily) what will happen I
wonder?

If XP takes it, you will loose a bunch of HDD space for some amount of
time, and then when XP is done, it may give it back. With your low
HDD space that could be a big percentage of free space. Available,
gone, available...

I will work on that just because it is making me mad now.
================

One problem here was my typing. I should've just said "1/2 GIG of
RAM", which is confirmed by Belarc Advisor (a wonderful utility):

1/2 GIG of RAM is the same as 500MB (from your first post). That part is
not the problem.
448 Megabytes Installed Memory

Yes, from an earlier post. And I surmised 64MB of your total 512MB of
RAM was dedicated to onboard graphics. Can you confirm?
Slot 'A0' has 4096 MB

Here we go again!

Is this a typo, or are you telling me that Slot A0 has a 4GB stick of
RAM? If so, what is the type of RAM as well as make and model number.
Regarding your mobo, from your report, I see this:
System Manufacturer MICRO-STAR INTERNATIONAL CO., LTD
System Model MS-7142

I will look into what kind of RAM is appropriate for this board.
Slot 'A1' is Empty

That's as much info as I can provide at the moment without opening
the case.

You really need to open the case! We'll wait. :-)

If you don't post back soo, Happy New Year to you!
 
Daave said:
Regarding your mobo, from your report, I see this:


I will look into what kind of RAM is appropriate for this board.

Okay, have a look here:

http://www.memoryx.net/msimskmome6.html

This board has only two slots. And the maximum memory is 2GB. So if you
really do have a 4GB stick in one of the slots, I'm mystified as to how
the board will accept it! My guess is you have a 512MB stick of PC3200
(or lower) DDR non-ECC RAM installed and something wacky is causing your
mobo to *think* that it's a 4GB stick. Check your BIOS settings and
report back!
 
Daave said:
Okay, have a look here:

http://www.memoryx.net/msimskmome6.html

This board has only two slots. And the maximum memory is 2GB. So if you
really do have a 4GB stick in one of the slots, I'm mystified as to how
the board will accept it! My guess is you have a 512MB stick of PC3200 (or
lower) DDR non-ECC RAM installed and something wacky is causing your mobo
to *think* that it's a 4GB stick. Check your BIOS settings and report
back!


Can you imagine if hammers or can openers worked this way? There'd be riots
in the streets.
 
I saw this one quite a while ago. Maybe I'm old fashioned, but I
don't
dig the "squarified" display at all.

Pies are much easier to follow and comprehend, not to
mention the logical display of what's in what in what, etc.

Cute but useless, IMO, like so much of the new stuff.
 
Daave said:
Okay, have a look here:

http://www.memoryx.net/msimskmome6.html

This board has only two slots. And the maximum memory is 2GB. So if you
really do have a 4GB stick in one of the slots, I'm mystified as to how
the board will accept it! My guess is you have a 512MB stick of PC3200
(or lower) DDR non-ECC RAM installed and something wacky is causing your
mobo to *think* that it's a 4GB stick. Check your BIOS settings and
report back!

The BIOS has two ways to determine the size of memory.

The modern way, is to read the SPD chip on the DIMM. That
contains up to 256 bytes of data, which describe the hardware
characteristics of the DIMM. The contents should be protected
by a checksum.

The BIOS though, has a second check it does. It uses a test
it used to use in ancient times, before SPD existed. We used to
"poke" the memory space, and do test accesses, to see how much
memory existed. Write a value, then do a read back, and check
if the same value comes back or not. You can do a binary
search until you find the "top of the DIMM". And that
tells you the true memory size.

Because the BIOS has the second method, it never is placed in the
embarrassing situation of trusting what it reads in the SPD, and
crashing the computer as a result. In this case, the BIOS has
correctly tested the memory for itself, and determined the true
size is 512 MB. It then prepared the address decoding map accordingly.

Now, that doesn't prevent other pieces of software, from reading
the SPD, and concluding some other amount of memory is installed.
But as long as the BIOS has correctly set up the Northbridge and
memory decoder, so it doesn't stray into "non-existent" memory,
the box stays on its feet.

*******

Use the no-install version of CPUZ. Run CPUZ.exe. Click the
"About" tab. Use the "Save Report" function, to a text file.

http://www.cpuid.com/cpuz.php

Look for a section that looks like this. There would be one
256 byte table, for each installed DIMM.

Dump Module #1
0 1 2 3 4 5 6 7 8 9 A B C D E F
00 80 08 08 0E 0A 61 40 00 05 30 45 00 82 08 00 00
10 0C 04 38 01 02 00 03 3D 50 50 60 3C 1E 3C 2D 80
....
F0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

The parameters can be decoded with documents like this one.
Perhaps by doing a bit of analysis, you can see how it
gets 4096MB. Byte 31 and byte 5 might be interesting.
As well as checking to see if the checksum is correct.

http://web.archive.org/web/20030417070529/http://www.jedec.org/download/search/4_01_02_04R11A.PDF

Or just post the block of data in question, and I'll decode it :-)

Paul
 
Had the same problem - uninstalled Zone Alarm and the problem has gone away.
Do a search in Google - it seems it is a common problem with ZA.
Cheers,
Brian.
 
Please let Twayne know of this problem.
Bri said:
Had the same problem - uninstalled Zone Alarm and the problem has gone
away. Do a search in Google - it seems it is a common problem with ZA.
Cheers,
Brian.
 
JoeSpareBedroom said:
WinXP Pro SP2
500 mb of RAM
18 gb hard disk with around 4gb free

Got a warning last night that I was running out of hard disk space.
Checked My Computer & found I was down to around 200 *MEGABYTES*.
My first thought was "That's interesting". Actually, that's not
what I thought, but there might be kids here, so use your
imagination.
I download quite a bit of music, but in order to keep about 4gb
free, I religiously move the files to my external HD every few
days, so I knew that wasn't the issue. The only things running at
the moment were Firefox and Outlook Express, along with Avast
(antivirus) and ZoneAlarm Pro. I shut down FF & OE & restarted the
computer. Again, I found around 200 MB free. Unfortunately, I did
not check page file use in Task Manager at the time. However, I
compared the list of processes to a screen shot I made for this
purpose in the past, and found nothing unusual. I accept no
software updates (except from Avast & ZoneAlarm) without first
consulting a couple of tech sources for problems, and no new apps
have been installed in at least a year.
Walked away to think about it, came back 10 minutes later, and
found I was back up to 4GB again.

"That's interesting", I thought. I ran a full AV scan using Avast,
followed by a Spybot scan. They found nothing. Upon restarting this
morning, the computer is fine.

I'm mystified. Anyone have any ideas?

Shenan said:
I would get rid of Zone Alarm and Avast and replace the with the
Windows Firewall (especially if you are already behind a NAT
router) and Avira Antivirus. ZoneAlarm is often more trouble than
it is worth for the home user and is utilizing resources for many
who have it installed they would likely enjoy more elsewhere
without losing any level of protection. I have nothing against
Avast (free or pay) - but have found that of the free ones, Avira
antivirus seems to work the best for most users. You could go an
purchase eSet NOD32 antivirus (antivirus only) and get really good
results - but I am not about to suggest (only) that you spend $60
U.S. - you'd likely stop reading. *grin*
I would also uninstall Spybot Search and Destroy. I just don't
favor it as much as I used to - there are definitely all-around
better products out there.

You have an 18GB drive - that is small. You have to be *very*
watchful with your space. There are a few things you can do to
ensure you have as much space as possible and then - something you
can do to see where all the space is being used.

Clean up and then see what you have left to do.

Download/install this:
http://support.microsoft.com/kb/290301

After installing, do the following:

Start button --> RUN --> type in:
"%ProgramFiles%\Windows Installer Clean Up\msizap.exe" g!
--> Click OK.

(The quotation marks and percentage signs and spacing should be
exact.)
If you are comfortable with the stability of your system, you can
delete the uninstall files for the patches that Windows XP has
installed... http://www3.telus.net/dandemar/spack.htm
( Particularly of interest here - #4 )
( Alternative:
http://www.dougknox.com/xp/utils/xp_hotfix_backup.htm )
You can run Disk Cleanup - built into Windows XP - to erase all but
your latest restore point and cleanup even more "loose files"..

How to use Disk Cleanup
http://support.microsoft.com/kb/310312

You can turn off hibernation if it is on and you don't use it..

When you hibernate your computer, Windows saves the contents of the
system's memory to the hiberfil.sys file. As a result, the size of
the hiberfil.sys file will always equal the amount of physical
memory in your system. If you don't use the hibernate feature and
want to recapture the space that Windows uses for the hiberfil.sys
file, perform the following steps:
- Start the Control Panel Power Options applet (go to Start,
Settings, Control Panel, and click Power Options).
- Select the Hibernate tab, clear the "Enable hibernation" check
box, then click OK; although you might think otherwise, selecting
Never under the "System hibernates" option on the Power Schemes tab
doesn't delete the hiberfil.sys file.
- Windows will remove the "System hibernates" option from the Power
Schemes tab and delete the hiberfil.sys file.

You can control how much space your System Restore can use...

1. Click Start, right-click My Computer, and then click Properties.
2. Click the System Restore tab.
3. Highlight one of your drives (or C: if you only have one) and
click on the "Settings" button.
4. Change the percentage of disk space you wish to allow.. I
suggest moving the slider until you have just about 1GB (1024MB or
close to that...) 5. Click OK.. Then Click OK again.

You can control how much space your Temporary Internet Files can
utilize...
Empty your Temporary Internet Files and shrink the size it stores
to a size between 64MB and 128MB..

- Open ONE copy of Internet Explorer.
- Select TOOLS -> Internet Options.
- Under the General tab in the "Temporary Internet Files" section,
do the following:
- Click on "Delete Cookies" (click OK)
- Click on "Settings" and change the "Amount of disk space to use:"
to something between 64MB and 128MB. (It may be MUCH larger right
now.)
- Click OK.
- Click on "Delete Files" and select to "Delete all offline
contents" (the checkbox) and click OK. (If you had a LOT, this
could take 2-10 minutes or more.)
- Once it is done, click OK, close Internet Explorer, re-open
Internet Explorer.

You can use an application that scans your system for log files and
temporary files and use that to get rid of those:

Ccleaner (Free!)
http://www.ccleaner.com/

Other ways to free up space..

JDiskReport
http://www.jgoodies.com/freeware/jdiskreport/index.html

SequoiaView
http://www.win.tue.nl/sequoiaview/

Those can help you visually discover where all the space is being
used.
In the end - a standard Windows XP installation with all sorts of
extras will not likely be above about 4.5GB to 9GB in size. If you
have more space than that (likely do on a modern machine) and most
of it seems to be used - likely you need to move *your stuff* off
and/or find a better way to manage it.

Did anything ever come of this?

Been following the entire conversation and most of the stuff I suggested
have been suggested again as more and more details come to light. If the
purpose was to free up space - then the removal of the products I suggested
could be skipped by and the rest followed. However - it seems that later
more details come out and people are suggesting some of the same things I
did for removal to fix other issues.

*shrug*

Just checking.
 
Shenan Stanley said:
Did anything ever come of this?

Been following the entire conversation and most of the stuff I suggested
have been suggested again as more and more details come to light. If the
purpose was to free up space - then the removal of the products I
suggested could be skipped by and the rest followed. However - it seems
that later more details come out and people are suggesting some of the
same things I did for removal to fix other issues.

*shrug*

Just checking.


Stay tuned, Shenan. I have guests today, but will definitely finish this off
by tomorrow. I don't like to leave these conversations hanging.
 
Don't know who Twayne is but as regards 'vanishing disk space' is concerned,
the problem I had was resolved by replacing ZA with another firewall. I
searched Google for 'memory leaks in Zone Alarm' when I discovered that
after disabling ZA from starting up, I no longer had memory slowly vanishing
from the hard drive. (Rebooting the computer would always restore the
original amount of memory) Perhaps I had just had a bad install of ZA.
 
Stay tuned, Shenan. I have guests today, but will definitely finish this off
by tomorrow. I don't like to leave these conversations hanging.

I thought the problem was the hard disk space was thought to be
"around 4gb", then "some warning appeared" and then when the hard disk
space was actually checked it was reported to have free space of
"around 200 *MEGABYTES*", then after about a 10 minute period of
thought, the disk space was actually checked for real and found to be
4GB.

After 50+ messages, we still don't know what the disk space was
originally (it was just a thought) and we don't know what the warning
message was either.
 
<snipped>
<entire conversation archived indefinitely>
http://groups.google.com/group/micr...p.general/browse_frm/thread/1c9e81bd744ca194/
</entire conversation archived indefinitely>


I thought the problem was the hard disk space was thought to be
"around 4gb", then "some warning appeared" and then when the hard
disk space was actually checked it was reported to have free space
of "around 200 *MEGABYTES*", then after about a 10 minute period of
thought, the disk space was actually checked for real and found to
be 4GB.

After 50+ messages, we still don't know what the disk space was
originally (it was just a thought) and we don't know what the
warning message was either.

Not sure what conversation you are reading - but the original post you
quoted by responding told you all of that. ;-)

What I gathered from the original posting:

- 18GB of total drive space; OP is supposedly very careful about free space
given how little total is available.
- OP received a message that the drive was running out of space, checked and
it was down to under 200MB free.
- OP walked away - came back - 4GB now free; supposedly nothing done to make
that happen other than maybe closing Outlook Express and Firefox and
allowing time to pass.
- Full scans by the OP with AVAST and SPYBOT SEARCH & DESTROY found nothing.
- OP uses ZoneAlarm.

At this time - given what was and has been - OP has an 18GB hard disk
drive/partition with 4GB free space. OP is curious as to what happened to
lower the free space to 200MB or less and then give that back with little to
no interaction from them.

My suggestions are still pretty much the same.

- Uninstall ZoneAlarm. It is a placebo for most users - while it is a fact
the Windows XP Firewall does not do anything with outgoing stuff - if you
have something it needs to block outgoing - you are already
infested/infected. Use the Windows XP Firewall, stay behind a NAT router
and use common sense.
- Uninstall Avast! AV. While it is still one of my suggested freebie AVs -
I think Avira is better (for free) and eSet NOD32 AV only (cost) is better
as well.
- Uninstall Spybot Search and Destroy and use MalwareBytes. The choice of
whether to install resident or just use the free scanning capabilities every
so often is one the OP should make (as is all of this - as these are just
suggestions.)
- Cleanup the hard drive space given the instuctions from earlier.

Going through all of the suggestions so far - no one _really_ disagrees with
this. Some loosely defend ZoneAlarm and another even says that could be the
cause of the problem. I didn't see anyone say anything about Avast!/Avira
or SpyBot Search & Destroy really (other than me) and other people mentioned
parts of what my steps would check/clear up - pointing to certain things as
the possible culprit (like System Restore points.)

Essentially JoeSpareBedroom has done parts of the suggestions and said would
get to the rest after holiday guests leave and they have more time.
 
I thought the name of the guy with the problem was 'JoeSpareBedroom'.
Anyway, hopefully he'll see the post and try, first of all, disabling ZA
from the startup in msconfig to see if that works, then if so, replace ZA
with something else. (I'm now using Comodo).
 
Back
Top