From: nospam@needed.invalid   
      
   On Sun, 2/22/2026 2:15 PM, Frank Slootweg wrote:   
   > Paul  wrote:   
   >> On Sun, 2/22/2026 12:08 PM, Chris wrote:   
   >>> Mr. Man-wai Chang  wrote:   
   >>>> On 2/20/2026 12:34 AM, micky wrote:   
   >>>>>   
   >>>>> I should have thought of those, but...   
   >>>>>   
   >>>>>> A virus scan?   
   >>>>>   
   >>>>> Been happeing now for 3.5 hours, and maybe last night too.  No scan   
   >>>>> takes that long.   
   >>>>>   
   >>>>>> Automatic defrag?   
   >>>>>   
   >>>>> Just wrote the files yesterday to a blank flashdrive, 3GB into a 16GB   
   >>>>> drive.  No fragmenting to defrag. ---  But in general, do I have   
   >>>>> automatic defragging?  How would I know?   
   >>>>   
   >>>> Just my wild guesses. I am also curious about the constantly flashing HD   
   >>>> LED as well, not just the USB ports!!   
   >>>>   
   >>>> Back in the MS-DOS single-user, no-networking days, everything was more   
   >>>> certain. The floppy diskette drive never ever made a sound suddenly. :)   
   >>>   
   >>> Oh yes, it did. Especially in MS Word. It would often randomly seek to all   
   >>> physical drives when doing other actions. It was some deep-seated   
   >>> assumption that everything would be stored on a removable disk and it   
   >>> needed to check that it was still there before doing anything.   
   >>   
   >> If you watch with Process Monitor, you will see some pretty   
   >> unbelievable scanning sequences in there. They are logically   
   >> unrelated to anything! But what would be the point of me   
   >> telling people this. And no, it's not malware.   
   >   
   >   No criticism, just a observation:   
   >   
   >   You often mention Process Monitor, but as far as I know, Process   
   > Monitor is add-on software, while for tasks like this - i.e. checking   
   > which processes are doing what on a certain drive - the bundled Resource   
   > Monitor is perfectly OK/sufficient.   
   >   
   >   Resource Monitor's 'Disk' tab has both a 'Disk Activity' pane - giving   
   > program name, PID and File - and a 'Processes with Disk Activity' pane   
   > - giving program name, PID and Read/Write/Total B/sec.   
   >   
   >   In my experience the 'Disk Activity' pane is often enough for cases   
   > like the ones in this thread, especially when combined with the 'Queue   
   > Length' graphs per drive in the righthand pane.   
   >   
   >   For those unaware of Resource Monitor: You can of course find it by   
   > typing the name into Search or by Task Manager -> 'Performance' tab ->   
   > three-horizontal-dots icon in the upper right -> Resource Monitor.   
   >   
   > [...]   
   >   
      
   Many of the utilities, are just clever re-applications of ETW.   
      
   Yes, I'm aware of Resource Monitor, and the fine grained observations   
   it offers. One difference would be, more sources are covered by   
   Process Monitor (procmon). For example, System would be in there.   
   Even though I have not the foggiest clue what "System" means in terms   
   of abusing filesystems. For example, my RAMDrive may be charged   
   to System, as belonging to System, and in some cases, RAMDrives   
   actually lived in Ring0. But they are not all that way.   
      
   For example, right now in Task Manager   
      
                    Working Set (memory)   
   System           101 GB   
      
   The RAMDrive is 99000 MB at the moment. That's the size I use   
   when placing virtual machine files on it. Permanent copies   
   are not needed, as the virtual machine file sets can be   
   discarded after testing a feature.   
      
      Paul   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)