Related topics

Explanation on how Windows stores files
The free space in the ODS-2 portion is about 6% of the total, so that's not too bad. Then, the MKISOCD.COM procedure was invoked to lay the ISO-9660 image into MOUNTed it to the VAXstation, and ran an ANALYZE/DISK/NOREPAIR on it. It displays the same anomalies as the CDs that come from DECpaq. I was pleased!

Unable to write database file c:\?
Then almost a week later tried moving 100MB of programs files onto another partition and then returning them to original Directory in NT drive C. And presto, the lost 500MB free disk space reappeared and currently totaling 624MB. What happened? Since I could not run SiSandra HDD test, due to free space constrains,

DOS file size - real vs allocated, how do I differentiate ?
CHKDSK discovered free space marked as allocated in the volume bitmap. Windows found problems with the file system. Run CHKDSK with the /F (fix) option to correct these. 19535008 KB total disk space. 8973768 KB in 74887 files. 26268 KB in 3322 indexes. 0 KB in bad sectors. 138372 KB in use by the system.

Windows reporting incorrect free space
The developers wanted me to try and recover the databases so I ran buildmaster, disk reinit and disk refit. Boy you can have some fun after doing a disk refit with databases that have been altered but thats another story. Everything is OK except when I do a sp_helpdb <database> the 'Free Space' is shown as NULL on

HEADERFULL error, even when it isn't!
Other than MSKB articles about the SFC registry settings, I can find no detailed info regarding how W2K SFC works and how anomalies can be corrected. The partition that W2K is on has over 2 GB of free space, so hard disk space is not an issue. 2. Running SFC /PURGECACHE to clear out DLLCACHE, running it to

Memory report anomalies
Shaun Hollingworth sh...@NSsecurstar.com alt security scramdisk Hello, Further to my recent reply - Before creating a hidden disk, it is advisable to overwrite the free space if the mounted DriveCrypt disk to be sure the unused sectors (as seen from a disk monitor looking at the logical outer disk after it has been

MAC User Group Re: PRAM Troubles
Perhaps the code gets confused when the free space becomes negative (see repeat-by example below). But that is pure speculation. I have been using FreeBSD for 10+ years and routinely use dd of /dev/zero to wipe the free space as root. I did not notice this accounting anomaly when I was still using FreeBSD 4.

kern/82682: "Accounting resumed" while disk fills up
[snip] Can Partition Magic do this without losing data on either drive, assuming there's enough free space? If so, where can I get it, and how much does it cost I used it on my hard disk to split it into two partitions and it worked perfectly. Search 'all-categories' at www.shareware.com for 'presz' and it will

What System 7 Does For You: A summary.
When we attempted to rebuild the desktop on this now-empty disk, the desktop rebuild released no additional free space, until we placed at least one file That a Mac's network copy should be faster than one to a local hard drive remains an anomaly we cannot explain. "Long filenames were maintained when the Mac

File marked for delete
I did run across an anomaly though. I had set my VM to a specific value, same for min and max. This get rid of a free space error reported by Disk Doctor. It also reduces the fragmentation on the HD making Speed Disk clean up what is fragmentated faster. When I ran Optimization Wizzard (basically to clean up the

Anti-Gravity Claim
Before the "discover disks" phase, I had to go to the F2 console and manually "modprobe mesh" to get it to recognize the Zip disk. Because the mesh driver module was loaded Possibly as a consequence of the locale anomaly mentioned in note 2, the setup for that task gave me the default option of "a4" paper.

Mount Analogue - Daumas digicopy
You cannot run a disk optimizer on a stacker drive, but version 2.0 includes an optimizer. I have found one minor anomaly. DIR (and other programs) report a Stacker drive's "projected" free space based on the current average compression ratio. When I have a stacker drive mounted remotely (via Brooklyn Bridge),

kern/82682: "Accounting resumed" while disk fills up
Michael Beck, describing the PC-speaker sound device ---------------------------(end of broadcast)--------------------------- TIP 2: Don't 'kill -9' the postmaster ---------------------------(end of broadcast)--------------------------- TIP 5: don't forget to increase your free space map settings --

Perfect Disk and Win Defrag don't agree
Daz d...@goulburn.net.au aus computers ibm-pc In case anyone else experiences free space anomalies like these, I ended up solving the problem by removing Norton If I boot from a system disk and run chkdsk I get the correct information, but if I run chkdsk from a Win95 MS-Dos prompt I get different information

nt 4 sp4 is out!
Do any of your apps that report free disk space agree with this? Just wondering. This free space was reported both by Norton Utilities and DOS. The anomaly is somehow related to Norton Utilities protecting deleted files on the C drive. Once, I "emptied" the Norton Protected C drive Recycle bin, the amount of free

Dangerously Close
The real file size is useless cos the sum of the sizes of all files on the disk plus the free space does not equal the size of the disk ? (but printed stuff would do as well), cos I have a (sinking) feeling this is going to be just the first in a long line of such anomalies that I'm going to have to deal with ?

[FanFic] The Manifestation of Destinies
Frank&Karen Williams FrankWilli...@erols.com microsoft public win98 disks general Scan Disk says I have 27 MB free on my 1.6 GB C Drive. Drive space says 457 MB. Keep getting 'you're running out of free space' messages. Which indicator is correct? Frank.

(OT)Where can I download a program for writing MP3's direct to CD?
Wietse Venema wie...@porcupine.org fa freebsd bugs Number: 82682 Category: kern Synopsis: "Accounting resumed" while disk fills up Confidential: no I have been using FreeBSD for 10+ years and routinely use dd of /dev/zero to wipe the free space as root. I did not notice this accounting anomaly when I was still

Dangerously Close
Although Windows seems to know how large the hard drive is, it can't seem to determine how much free/used space I have. However, all my utility programs that run under Windows (Norton) also show that there is no used space at all. To throw a further anomaly into the mix, sometimes when I boot up everything is

WinOs2 and big drives
I tend to agree, with new installations I usually turn on a lot of logging for Exchange, in case some tricky anomaly shows up. We are under 300 MB and 700 MB of free space on both. The E:\ drive is a much easier fix, as half of it is filled with old data that could easily be written to CD and put in storage,