Message-ID: <Pine.NEB.4.44.0206240006050.29770-100000@panix3.panix.com>
From: Alan Sondheim <sondheim@panix.com>
To: Cyb <cybermind@listserv.aol.com>,
"WRYTING-L : Writing and Theory across Disciplines" <WRYTING-L@LISTSERV.UTORONTO.CA>
Subject: Need help, I don't know anything.
Date: Mon, 24 Jun 2002 00:06:24 -0400 (EDT)
Need help, I don't know anything. I don't know why I find the defrag log interesting. Honestly, I don't. Some of the files held on to their partial status, refused to return whole, to their clean and proper place in the magneto-social order. Others balked in general, and still others went along willingly. What was it about the everglades.mov for example that insisted on a policy of strangulation, scattering its remains in 17 brutal pieces across god knows how many platters? And this, in the midst of purity, dissolution so small statistically that it doesn't even register in the larger order of things. (Continued below. I guess I needed space to present the file it- self, so you would understand what I'm talking about.) Volume HPNOTEBOOK (C:) Volume size = 27.89 GB Cluster size = 4 KB Used space = 15.73 GB Free space = 12.16 GB Percent free space = 43 % Volume fragmentation Total fragmentation = 0 % File fragmentation = 0 % Free space fragmentation = 0 % File fragmentation Total files = 69,685 Average file size = 269 KB Total fragmented files = 22 Total excess fragments = 113 Average fragments per file = 1.00 Pagefile fragmentation Pagefile size = 744 MB Total fragments = 1 Folder fragmentation Total folders = 4,402 Fragmented folders = 2 Excess folder fragments = 42 Master File Table (MFT) fragmentation Total MFT size = 83 MB MFT record count = 74,127 Percent MFT in use = 87 % Total MFT fragments = 3 ----------------------------------------------------------------------- Fragments File Size Files that cannot be defragmented 2 16 KB \WINDOWS\ModemLog_ESS SuperLink-M Data Fax Voice Modem.txt 3 10 KB \WINDOWS\system32\wbem\Logs\wmiprov.log 2 16 KB \WINDOWS\system32\CatRoot2\dberr.txt 2 64 KB \WINDOWS\ocgen.log 4 125 KB \WINDOWS\FaxSetup.log 2 6 KB \Documents and Settings\Owner\Application Data\Microsoft\Windows\Themes\Custom.theme 2 492 KB \Documents and Settings\All Users\Application Data\ Microsoft\Media Index\wmplibrary_v_0_12.db 2 96 KB \Program Files\WindowsUpdate 17 142 MB \everglades\everglades.mov 6 90 KB \Program Files\America Online 6.0\Global.stg 2 7 KB \Program Files\America Online 6.0\idb\hints.ind 2 57 KB \Program Files\America Online 6.0\idb\main.ind 42 168 KB \System Volume Information\_restore {FE9C7AD2-91D5-4C9C-9C3A-1D5559EA1B8F}\RP30 2 12 KB \maria\toronto 3 30 KB \WINDOWS\system32\SymRedir.dll 2 14 KB \WINDOWS\system32\drivers\SymReDrv.sys 6 155 KB \WINDOWS\system32\drivers\SymTDI.sys 16 900 KB \WINDOWS\ACD Wallpaper.bmp 2 13 KB \archive\network\index.html 2 31 KB \Documents and Settings\Owner\Desktop\Panix.ht 2 15 KB \Documents and Settings\Owner\Application Data\ Mozilla\Profiles\default\t8ug9ku4.slt\localstore.rdf 22 2 MB \Program Files\America Online 6.0\Global.org 48 5 MB \Program Files\America Online 6.0\idb\main.idx 2 5 KB \Program Files\America Online 6.0\BetaLog.ini I admire people who can read logs clearly, and understand all the file types. Really, there are so many of them, that an amateur can hardly keep track. Some, such as .ht, I recognize as a hypertelnet configuration file, but things like .idx leave me totally confused. And what is it about these particular files that makes them so resistive? I'm fascinated with ocgen.log. I showed these files to M****. He's more of a neophyte than I am, which made me feel better. But still, when I've fragmented before, everything has gone through the mill. And this time, look what happens! - even though I've taken pains to close down all sorts of background processes. Here's part of the ocgen.log: [accessutil - OC_WIZARD_CREATED] - complete [commapps - OC_WIZARD_CREATED] - complete [multim - OC_WIZARD_CREATED] - complete [accessopt - OC_WIZARD_CREATED] - complete [pinball - OC_WIZARD_CREATED] - complete [mswordpad - OC_WIZARD_CREATED] - complete [wbem - OC_QUERY_STATE] - complete Here's my favorite part: [autoupdate - OC_ABOUT_TO_COMMIT_QUEUE] - complete [rootautoupdate - OC_ABOUT_TO_COMMIT_QUEUE] - complete [ieaccess - OC_ABOUT_TO_COMMIT_QUEUE] - complete [games - OC_ABOUT_TO_COMMIT_QUEUE] - complete [accessutil - OC_ABOUT_TO_COMMIT_QUEUE] - complete [commapps - OC_ABOUT_TO_COMMIT_QUEUE] - complete [multim - OC_ABOUT_TO_COMMIT_QUEUE] - complete [accessopt - OC_ABOUT_TO_COMMIT_QUEUE] - complete About to commit what? Perhaps to be committed, set-aside? The terrifying thing here is the fragmentation - what happened, what happened - why am I so curious - what strange beast slouches towards us - what horsemen, fury, apocalypse - metal fragment straight-jacket torn in 17 pieces - something moving in pieces - in the distance - _