If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Display Modes |
#1
|
|||
|
|||
Win7's dirty, dirty little bits
Exit Win7 - all indications - normally;- Ditto for Win XP.
Periodically, more than I'd like, upon a boot menu/arbitrator to load XP (after a Win7 session), Win7 -apparently- resets all it's "Dirt Bag" bits across all partitions, best I can figure. Dirt Bag: That is what MS does to a hard drive's partition in order to trigger a ChkDsk /F conditon upon the next boot. The make an honest-to-god dirty bit. For real. Worse, people have been damned for the past decade trying to figure it out (when it gets so filthy, I guess, you could just stuff a bar of Ivory soap up it and throw it permanently into hold). Me, I think it's Microsoft's way of being chummy with the NSA. Collecting all the filthy file information on everybody's computer during "dirty bit" operations and pass it along ... Yo - BigBro. No matter if the partition was never acessed, flag it for "dirt" anyway. I tried not giving drives under Win7 drive-assignment letters, although I've as much faith in that circumventing MS dirtbits as a snowball's chance in Hell. What's called for in a new and modern OS, such as Microsoft's, is a complex boot arbitrator with conditional brances for a menu item, as to what drives will be flagged hidden. Might work...a Big Maybe for compromises. That way you buy all the new HDDs, you want, fill them with programs, even. Just make sure you don't show them to MS. Least, not all at once (you'll, in fact, be waiting until tomorrow for ChkDsk to finish). |
#2
|
|||
|
|||
Win7's dirty, dirty little bits
On Sat, 27 Sep 2014 18:11:25 -0400, Flasherly
wrote: Exit Win7 - all indications - normally;- Ditto for Win XP. Periodically, more than I'd like, upon a boot menu/arbitrator to load XP (after a Win7 session), Win7 -apparently- resets all it's "Dirt Bag" bits across all partitions, best I can figure. Dirt Bag: That is what MS does to a hard drive's partition in order to trigger a ChkDsk /F conditon upon the next boot. The make an honest-to-god dirty bit. For real. Worse, people have been damned for the past decade trying to figure it out (when it gets so filthy, I guess, you could just stuff a bar of Ivory soap up it and throw it permanently into hold). Me, I think it's Microsoft's way of being chummy with the NSA. Collecting all the filthy file information on everybody's computer during "dirty bit" operations and pass it along ... Yo - BigBro. No matter if the partition was never acessed, flag it for "dirt" anyway. What's the problem? Remember, Windows accesses volumes in the background. It appears that when Windows accesses a volume it marks it dirty, when it releases a volume the last thing it does is mark it clean. Chkdsk runs if the drive is marked dirty. Better to run it when it's not needed than have a directory problem that breeds because you used a corrupted volume. |
#3
|
|||
|
|||
Win7's dirty, dirty little bits
On Sat, 27 Sep 2014 16:26:18 -0700, Loren Pechtel
wrote: What's the problem? I'm periodically/randomly experiencing a boot condition, (the CHKDSK dirty-bit flag is present), going into Windows XP, upon and after exiting Windows 7 64 Pro. I'm using a boot arbitrator on SSD1 as my BIOS "first boot" assignment, whereupon is contained the boot arbitrator and Windows XP. The boot arbitrator then will boot Windows 7, as provided by the boot arbitrator selection menu, by going to and bring up Windows 7 from SSD2 - a physically different SSD, entirely, whereupon Windows 7 is installed and runs from. They both, Win7 and XP, shut down without apparent incident, cleanly to reboot. However, as I said, I'm apt to get a ChkDsk condition, for Windows XP, by all indications generated -by Win7- upon exiting. Windows XP then will check all and every one of my drives, because all and every one is marked with a "dirty bit." On one drive, alone, I have 250,000 files. I seldom use that drive, but to see Windows XP churning away to chkdsk it, just because Windows 7's prior shut-down sequence, by all indications a smooth shutdown, says to do so - Man, that's starting to burn my butt on weirdness factoring alone. (I really shouldn't ignore what may be some irregularities between SSDs and various permutations they can be run - IOW, plattered and conventional HDDs may not exhibit, altogether, those same aberrations if I installed both XP and Win7 on two conventional drives.) Remember, Windows accesses volumes in the background. It appears that when Windows accesses a volume it marks it dirty, when it releases a volume the last thing it does is mark it clean. Chkdsk runs if the drive is marked dirty. Win marks them initially dirty: a partition - logical/primary. All mine, my "drives," are FAT32 (one NTFS). Win then releases drives for a clean condition - presumably at shut down or restart. Just restating how I read you. Better to run it when it's not needed than have a directory problem that breeds because you used a corrupted volume. Oh, yes. I'm not quite ready to turn it off indiscriminately, rather deny chkdsk to disk partitions that were actively engaged in prior MS operations. I can however turn off ChkDsk (through the registry) - never to run on drives I know damn well it never accessed and should not have flagged for dirty. I just don't want to - be cleaner, as its largely been up to now, if Win7 just stayed clean and also played that way. I'm going to be carefully watching how I shut down Win7 from now on. I still may crash XP on occasional image backups, the first time booting up after an image is placed/written onto the SSD boot partition. It almost invariably takes on the second image write, though, should the first immediately crash. Never had that problem, on the Samsung SSD, until I moved XP to a newer Crucial SSD (and Win7 to the Samsung). Like I said, the weirdness factor -(is Crucial really all it's cracked to be by comparison to Samsung?)- in my hardware setup may be incidental to generating OS instability. |
#4
|
|||
|
|||
Win7's dirty, dirty little bits
On Sat, 27 Sep 2014 20:55:54 -0400, Flasherly
wrote: Dirty Bits -- Found something else. Sticking in SSDs into XP and an old(er) MB (non-AHCI BIOS), my SSDs' partitions aren't correctly aligned. Fun. I'll have to figure out so'mo' *NIX to fixerupper with GPartEd. Something about GPartEd resizing individual partitions, through two stages, adding or subtracting a meg of space, give here then take there, to bring the partitions back into correct alignment for correcting one big heap of a mess of mistakes when using all but the latest&greatest soft- and hardware. A SSD's "offset" of course should be divisible by the whole number 4096 at a returned sum and whole number (sic) without fractional or decimal placement. As anyone not numbered among idiots --those whom carry tablets, subscribe to clouded identities-- naturally should know. (I'm checking and will report back if XP users still qualify for special mental-imbecile status.) |
#5
|
|||
|
|||
Win7's dirty, dirty little bits
On Sunday, September 28, 2014 6:11:25 AM UTC+8, Flasherly wrote:
Exit Win7 - all indications - normally;- Ditto for Win XP. Periodically, more than I'd like, upon a boot menu/arbitrator to load XP (after a Win7 session), Win7 -apparently- resets all it's "Dirt Bag" bits across all partitions, best I can figure. Dirt Bag: That is what MS does to a hard drive's partition in order to trigger a ChkDsk /F conditon upon the next boot. The make an honest-to-god dirty bit. For real. Worse, people have been damned for the past decade trying to figure it out (when it gets so filthy, I guess, you could just stuff a bar of Ivory soap up it and throw it permanently into hold). Ubuntu does an fsck after 30 boots. A pain when you have a stack of 2 TB drives in it. |
#6
|
|||
|
|||
Win7's dirty, dirty little bits
|
Thread Tools | |
Display Modes | |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
dirty keyboard | [email protected] | General | 17 | February 21st 08 01:42 PM |
setting of dirty bit in the pte | bharath | Intel | 0 | September 8th 06 07:10 PM |
ink in Canon i550 becomes "dirty" | stefan | Printers | 16 | September 30th 05 08:35 PM |
Windows XP says I have a "Dirty" disk! | John W. Wells | Dell Computers | 4 | August 14th 04 01:37 AM |
tnt2 fan was dirty | Skybuck Flying | Nvidia Videocards | 6 | May 12th 04 04:23 PM |