|
Answer» Oops. The du utility from the Windows 2000 RESOURCE kit is handy.
Code: [Select]S:\>du /q pdf-dir Files: 10 Directories: 8 Size: 5,670,819 bytes Size on DISK: 5,670,819 bytes
Code: [Select]S:\>for /f "tokens=1-3" %A in ('du /q pdf-dir ^| find "Size:"') do @echo %B %C 5,670,819 bytes I guess I don't have du.
Code: [Select]C:\>du /q PROGRAM files dir 'du' is not recognized as an internal or external command, operable program or batch file. Keep in mind here that directory/drive/ and folder sizes will all be reported differently depending on the reporting agent itself... This is commonly known as computer chaos and is built into every machine ever assembled...Quote This is commonly known as computer chaos and is built into every machine ever assembled... Right! Now I would like to know what is it about US humans that this bothers us so much. This question comes up again and again. Why do people BECOME agitated because the machine can not provide a precise status report?Because we're Human...Quote from: nubia on February 20, 2009, 06:51:32 PM I guess I don't have du.
Code: [Select]C:\>du /q program files dir 'du' is not recognized as an internal or external command, operable program or batch file.
Quote from: Dias de verano on February 19, 2009, 03:44:21 PMThe du utility from the Windows 2000 Resource kit is handy.
Code: [Select]S:\>du /q pdf-dir Files: 10 Directories: 8 Size: 5,670,819 bytes Size on disk: 5,670,819 bytes
Code: [Select]S:\>for /f "tokens=1-3" %A in ('du /q pdf-dir ^| find "Size:"') do @echo %B %C 5,670,819 bytes
|