Treesize Professional User's Manual

Total Page:16

File Type:pdf, Size:1020Kb

Treesize Professional User's Manual TreeSize Professional User's Manual ©1995-2010 by Joachim Marder e.K. TreeSize Professional ©1995-2010 by Joachim Marder e.K. All rights reserved. No parts of this work may be reproduced in any form or by any means - graphic, electronic, or mechanical, including photocopying, recording, taping, or information storage and retrieval systems - without the written permission of the publisher. Products that are referred to in this document may be either trademarks and/or registered trademarks of the respective owners. The publisher and the author make no claim to these trademarks. While every precaution has been taken in the preparation of this document, the publisher and the author assume no responsibility for errors or omissions, or for damages resulting from the use of information contained in this document or from the use of programs and source code that may accompany it. In no event shall the publisher and the author be liable for any loss of profit or any other commercial damage caused or alleged to have been caused directly or indirectly by this document. Printed: Januar 2010 Development Contact JAM Software GmbH Joachim Marder Max-Planck-Str. 22 Ajoschi Roth 54296 Trier Harald Binkle Germany Tobias Päutz Marcel Dütscher Trade Register No. HRB 4920 (AG Wittlich) Klaus Sausen Volker Schumacher FAX: +49-700-70707059 Chrisitan Wiwie E-mail: [email protected] Thomas Breuer WWW: http://www.jam-software.com I Table of Contents 1 Overview 1 2 Installation 1 3 Quickstart 2 4 What's New 3 5 Tips & Annotations 14 6 TreeSize Column for Explorer 15 7 Wasted Space 16 8 Notes on NTFS 16 9 Printing 18 10 FAQ 18 10.1 Gener.a..l. ./. .R..e..g..i.s.t.r..a..t.i.o..n.. ......................................................................................................... 18 10.2 Main P..r.o..g..r.a..m... ...................................................................................................................... 20 10.3 Printin.g.. ./. .E..x..p..o..r..t. .................................................................................................................. 24 10.4 File Se..a..r.c..h.. .......................................................................................................................... 24 11 Windows & Tabs 26 11.1 Toolba..r.s.. .............................................................................................................................. 27 11.2 Directo..r.y.. .T..r.e..e.. ...................................................................................................................... 28 11.3 Drive P..a..n..e..l. .......................................................................................................................... 28 11.4 Chart ................................................................................................................................... 29 Tree Map .......................................................................................................................................................... 30 11.5 Details.. ................................................................................................................................. 31 11.6 Extens.i.o..n..s.. ........................................................................................................................... 32 11.7 Users ................................................................................................................................... 33 11.8 Age of. .F..i.l.e..s.. ......................................................................................................................... 34 11.9 Top 10.0.. .F..i.l.e..s.. ....................................................................................................................... 35 11.10 History.. ................................................................................................................................. 35 12 Options 36 12.1 View T..a..b.. ............................................................................................................................. 36 12.2 Scan T..a..b.. ............................................................................................................................. 37 12.3 Includ.e.. ./. .E..x..c.l.u..d..e.. .T..a..b.. .......................................................................................................... 38 12.4 Colum.n..s.. ./. .E..x..p..o..r.t. .T..a..b.. .......................................................................................................... 39 12.5 Startup.. .T..a..b.. .......................................................................................................................... 42 TreeSize Professional - Table of Contents I II TreeSize Professional 12.6 Miscel.l.a..n..e..o..u..s. .T..a..b.. ............................................................................................................... 42 12.7 Age of. .F..i.l.e..s.. .T..a..b.. .................................................................................................................. 43 13 The Menus 43 13.1 File M.e..n..u.. ............................................................................................................................ 44 13.2 Export. .S..u..b..m...e..n..u.. .................................................................................................................. 45 13.3 Edit M.e..n..u.. ............................................................................................................................ 46 13.4 Branch.. .M...e..n..u.. ....................................................................................................................... 46 13.5 View M...e..n..u.. .......................................................................................................................... 46 13.6 Sort M.e..n..u.. ............................................................................................................................ 48 13.7 File Se..a..r.c..h.. .M...e..n..u.. ................................................................................................................ 48 13.8 Tools M...e..n..u.. .......................................................................................................................... 48 13.9 Contex..t. .M...e..n..u.. ...................................................................................................................... 48 14 File Search 51 14.1 The Fi.l.e.. .S..e..a..r.c..h.. .W...i.n..d..o..w... ..................................................................................................... 52 File Search Me...n..u.. ................................................................................................................................................... 53 File Search Op..t.i.o...n..s.. ............................................................................................................................................... 56 14.2 Bigges..t. .F..i.l.e.. .S..e..a..r.c..h.. ............................................................................................................. 57 14.3 Oldest. .F..i.l.e.. .S..e..a..r.c..h.. ............................................................................................................... 57 14.4 Tempo..r.a..r.y.. .F..i.l.e.. .S..e..a..r..c.h.. .-. .C...o..n..f.i.g..u..r.a..t.i.o..n.. ............................................................................... 58 14.5 Interne..t. .F..i.l.e.. .S..e..a..r..c.h.. ............................................................................................................. 59 14.6 Duplic.a..t.e.. .F..i.l.e.. .S..e..a..r.c..h.. .......................................................................................................... 59 14.7 Custom... .F..i.l.e.. .S..e..a..r.c..h.. ............................................................................................................. 60 Custom File S.e...a..r.c..h... .-. .S..e...a..r.c..h... .f.o..r.. .F..i.l.e.. .N...a..m...e...s.. ................................................................................................... 61 Custom File S.e...a..r.c..h... .-. .S..e...a..r.c..h... .f.o..r.. .F..i.l.e.. .D...a..t.e..s... ..................................................................................................... 61 Custom File S.e...a..r.c..h... .-. .S..e...a..r.c..h... .f.o..r.. .F..i.l.e.. .S...i.z..e..s.. .a..n...d.. .A...t.t.r..i.b..u...t.e..s... .......................................................................... 62 Custom File S.e...a..r.c..h... .-. .S..e...a..r.c..h... .f.o..r.. .F..i.l.e.. .O...w...n...e..r..s.. ................................................................................................. 63 14.8 Move c..h..e..c..k..e..d.. .f.i.l.e..s. .............................................................................................................. 64 Unicode Zip fi.l.e..s.. .................................................................................................................................................... 66 15 Schedule TreeSize Tasks 66 15.1 Sched.u..l.e.. .D..i.a..l.o..g.. .................................................................................................................. 66 15.2 Comm.a..n..d.. .L..i.n..e.. .O...p..t.i.o..n..s. ....................................................................................................... 68 16 Copyright & Contact 74 Index 75 TreeSize Professional - Table of Contents Overview
Recommended publications
  • Better Performance Through a Disk/Persistent-RAM Hybrid Design
    The Conquest File System: Better Performance Through a Disk/Persistent-RAM Hybrid Design AN-I ANDY WANG Florida State University GEOFF KUENNING Harvey Mudd College PETER REIHER, GERALD POPEK University of California, Los Angeles ________________________________________________________________________ Modern file systems assume the use of disk, a system-wide performance bottleneck for over a decade. Current disk caching and RAM file systems either impose high overhead to access memory content or fail to provide mechanisms to achieve data persistence across reboots. The Conquest file system is based on the observation that memory is becoming inexpensive, which enables all file system services to be delivered from memory, except providing large storage capacity. Unlike caching, Conquest uses memory with battery backup as persistent storage, and provides specialized and separate data paths to memory and disk. Therefore, the memory data path contains no disk-related complexity. The disk data path consists of only optimizations for the specialized disk usage pattern. Compared to a memory-based file system, Conquest incurs little performance overhead. Compared to several disk-based file systems, Conquest achieves 1.3x to 19x faster memory performance, and 1.4x to 2.0x faster performance when exercising both memory and disk. Conquest realizes most of the benefits of persistent RAM at a fraction of the cost of a RAM-only solution. Conquest also demonstrates that disk-related optimizations impose high overheads for accessing memory content in a memory-rich environment. Categories and Subject Descriptors: D.4.2 [Operating Systems]: Storage Management—Storage Hierarchies; D.4.3 [Operating Systems]: File System Management—Access Methods and Directory Structures; D.4.8 [Operating Systems]: Performance—Measurements General Terms: Design, Experimentation, Measurement, and Performance Additional Key Words and Phrases: Persistent RAM, File Systems, Storage Management, and Performance Measurement ________________________________________________________________________ 1.
    [Show full text]
  • System Calls System Calls
    System calls We will investigate several issues related to system calls. Read chapter 12 of the book Linux system call categories file management process management error handling note that these categories are loosely defined and much is behind included, e.g. communication. Why? 1 System calls File management system call hierarchy you may not see some topics as part of “file management”, e.g., sockets 2 System calls Process management system call hierarchy 3 System calls Error handling hierarchy 4 Error Handling Anything can fail! System calls are no exception Try to read a file that does not exist! Error number: errno every process contains a global variable errno errno is set to 0 when process is created when error occurs errno is set to a specific code associated with the error cause trying to open file that does not exist sets errno to 2 5 Error Handling error constants are defined in errno.h here are the first few of errno.h on OS X 10.6.4 #define EPERM 1 /* Operation not permitted */ #define ENOENT 2 /* No such file or directory */ #define ESRCH 3 /* No such process */ #define EINTR 4 /* Interrupted system call */ #define EIO 5 /* Input/output error */ #define ENXIO 6 /* Device not configured */ #define E2BIG 7 /* Argument list too long */ #define ENOEXEC 8 /* Exec format error */ #define EBADF 9 /* Bad file descriptor */ #define ECHILD 10 /* No child processes */ #define EDEADLK 11 /* Resource deadlock avoided */ 6 Error Handling common mistake for displaying errno from Linux errno man page: 7 Error Handling Description of the perror () system call.
    [Show full text]
  • 'DIY' Digital Preservation for Audio Identify · Appraise · Organise · Preserve · Access Plan + Housekeeping
    'DIY' Digital Preservation for Audio Identify · Appraise · Organise · Preserve · Access Plan + housekeeping Part 1 (10:00am-10:50am) Part 2 (11:00am-11:45am) 10:00am-10:10am Intros and housekeeping 10:50am-11:00am [10-minute comfort break] 10:10am-10:30am Digital Preservation for audio 11:00am-11:15am Organise (Migrate) What material do you care 11:15am-11:45am Store, Maintain, Access about and hope to keep?_ Discussion & Questions 10:30am-10:50am Locate, Appraise, Identify What kind of files are you working with?_ Feel free to Using Zoom swap to ‘Grid View’ when slides are not in use, to gage ‘the room’. Please use the chat Please keep function to your mic on ask questions ‘mute’ when while slides not speaking. are in use. Who are we? • Bridging the Digital Gap traineeship scheme • UK National Archives (National Lottery Heritage Fund) • bringing ‘digital’ skills into the archives sector Why are we doing these workshops? • agitate the cultural record to reflect lived experience • embrace tools that support historical self-determination among non- specialists • raise awareness, share skills, share knowledge What is digital preservation? • digital material is vulnerable in different ways to analog material • digital preservation = “a series of managed activities undertaken to ensure continued access to digital materials for as long as necessary.” Audio practices and technological dependency Image credit: Tarje Sælen Lavik Image credit: Don Shall Image credit: Mk2010 Image credit: Stahlkocher Image credit: JuneAugust Digital preservation and ‘born-digital’ audio Bitstream File(s) Digital Content Rendered Content • codecs (e.g. LPCM) • formats and containers (e.g.
    [Show full text]
  • Amateur Computer Group of New Jersey NEWS Volume 39, Number 01 January 2014
    Amateur Computer Group of New Jersey NEWS Volume 39, Number 01 January 2014 Main Meeting/Election Report ACGNJ Meetings Brenda Bell, ACGNJ For the very latest news on ACGNJ meetings, please On December 6, 2013, we held our Annual Business visit the ACGNJ Website (www.acgnj.org). Meeting, with 8 persons attending. Having reached a Board of Directors Meeting: December 31, 7:00 PM quorum, the meeting was called to order at 9:09 PM. MOVED to Friday, January 3, 7:00 PM. Mike Redlich presented a President's Report. (Due to the New Year's Holiday) Malthi Masurekar presented a Treasurer's Report. Board of Directors Meeting: Friday, Jan 3, 7:00 PM Several topics were raised for discussion, including Mike Redlich (president (at) acgnj.org) membership issues and outreach to other clubs. Main Meeting: Friday, January 3. 8:00 PM Election results. Without discussion, and with no Mike Redlich (president (at) acgnj.org) additional candidates being nominated for our two Lunics (Linux/UNIX): Monday, January 6, 8:00 PM still open Director positions, John Raff moved that Andreas Meyer (lunics (at) acgnj.org) the Secretary cast one vote for the pat slate. The Investing: Thursday, January 9, 8:00 PM motion was seconded and carried. Jim Cooper (jim (at) thecoopers.org). President: Michael Redlich NJ Gamers: Friday, January 10, 6:00 PM Vice-President: Wendy Bell Gregg McCarthy (greggmajestic (at) gmail.com) Secretary: Brenda Bell Treasurer: Malthi Masurekar Layman’s Forum: Monday, January 13, 8:00 PM Directors (Two year term, through end of 2015): Matt Skoda (som359 (at) gmail.com) Gregg McCarthy Java: Tuesday, January 14, 7:30 PM John Raff Mike Redlich (mike (at) redlich.net) Frank Warren Window Pains: Friday, January 17, 7:00 PM Directors (From last year, through end of 2014): !!!WARNING!!! This meeting will NOT be held in Bob Hawes our usual location.
    [Show full text]
  • Troubleshooting : Virtual Desktop Service
    Troubleshooting Virtual Desktop Service NetApp September 23, 2021 This PDF was generated from https://docs.netapp.com/us-en/virtual-desktop- service/Troubleshooting.reviewing_vds_logs.html on September 23, 2021. Always check docs.netapp.com for the latest. Table of Contents Troubleshooting . 1 Troubleshooting Failed VDS Actions . 1 Internet Connection Quality Troubleshooting . 6 Enable Desktop Wallpaper for User Sessions . 9 Troubleshooting Printing Issues . 11 Azure vCPU Core Quota . 12 Unlocking User Accounts . 15 Troubleshooting Virtual Machine Performance . 17 DNS Forwards for Azure ADDS & SSO via O365 identity . 28 Troubleshooting Application Issues . 34 Troubleshooting Troubleshooting Failed VDS Actions Overview Much of the logging that happens in VDS is not exposed in the web UI due to the sheer volume of it. More detailed logs are found on the end point. These logs are described below. In VDS v5.4+, the logs are found in the following folder path: C:\programdata\cloudworkspace In previous version of VDS, they can reside in the following paths: C:\Program Files\CloudWorkspace\ C:\Program Files\CloudJumper\ C:\Program Files\IndependenceIT\ File type also varies by VDS version, log files are either .txt or .log files found in sub-folders of the above outlined path. Automation logs CW VM Automation Service log CwVmAutomationService.log The CW VM Automation service is a Windows Service that is responsible for the management of all Virtual Machines in the deployment. As a Windows Service it is always running in a deployment, but has two main modes of operation: Scheduled Task Mode and Event Mode. Scheduled Task Mode consists of activities that are performed on the VMs as part of a schedule, including collection sizing and performance data, rebooting VMs, checking on state (on or off) vs rule sets generated by the Workload Schedule and Live Scaling features.
    [Show full text]
  • Listener Feedback Q&A
    Transcript of Episode #100 Listener Feedback Q&A #21 Description: Steve and Leo discuss questions asked by listeners of their previous episodes. They tie up loose ends, explore a wide range of topics that are too small to fill their own episode, clarify any confusion from previous installments, and present real world "application notes" for any of the security technologies and issues they have previously discussed. High quality (64 kbps) mp3 audio file URL: http://media.GRC.com/sn/SN-100.mp3 Quarter size (16 kbps) mp3 audio file URL: http://media.GRC.com/sn/sn-100-lq.mp3 INTRO: Netcasts you love, from people you trust. This is TWiT. Leo Laporte: Bandwidth for Security Now! is provided by AOL Radio at AOL.com/podcasting. This is Security Now! with Steve Gibson, Episode 100 for July 12, 2007: Your questions, Steve’s answers. It’s time for Security Now!, our 100th episode. We need streamers. We need - we’re actually recording this on the 4th of July. You’d think there’d be some fireworks. But no. Nothing. Steve Gibson: No. Leo: Unlike some of the other shows, we’re just going to go along about our business. But congratulations, Steve. My deepest thanks for allowing us to carry this on the TWiT network. It is absolutely, after TWiT, the flagship podcast, it’s the one everybody talks about. Steve: Well, I’ve been really, really happy that we did it, Leo. I wouldn’t be doing it were it not for you because, you know, you make me get up..
    [Show full text]
  • Life in the Fast Lane: Optimisation for Interactive and Batch Jobs Nikola Marković, Boemska T.S
    Paper 11825-2016 Life in the Fast Lane: Optimisation for Interactive and Batch Jobs Nikola Marković, Boemska T.S. Ltd.; Greg Nelson, ThotWave Technologies LLC. ABSTRACT We spend so much time talking about GRID environments, distributed jobs, and huge data volumes that we ignore the thousands of relatively tiny programs scheduled to run every night, which produce only a few small data sets, but make all the difference to the users who depend on them. Individually, these jobs might place a negligible load on the system, but by their sheer number they can often account for a substantial share of overall resources, sometimes even impacting the performance of the bigger, more important jobs. SAS® programs, by their varied nature, use available resources in a varied way. Depending on whether a SAS® procedure is CPU-, disk- or memory-intensive, chunks of memory or CPU can sometimes remain unused for quite a while. Bigger jobs leave bigger chunks, and this is where being small and able to effectively exploit those leftovers can be a great advantage. We call our main optimization technique the Fast Lane, which is a queue configuration dedicated to jobs with consistently small SASWORK directories, that, when available, lets them use unused RAM in place of their SASWORK disk. The approach improves overall CPU saturation considerably while taking loads off the I/O subsystem, and without failure results in improved runtimes for big jobs and small jobs alike, without requiring any changes to deployed code. This paper explores the practical aspects of implementing the Fast Lane on your environment.
    [Show full text]
  • Winreporter Documentation
    WinReporter documentation Table Of Contents 1.1 WinReporter overview ............................................................................................... 1 1.1.1.................................................................................................................................... 1 1.1.2 Web site support................................................................................................. 1 1.2 Requirements.............................................................................................................. 1 1.3 License ....................................................................................................................... 1 2.1 Welcome to WinReporter........................................................................................... 2 2.2 Scan requirements ...................................................................................................... 2 2.3 Simplified Wizard ...................................................................................................... 3 2.3.1 Simplified Wizard .............................................................................................. 3 2.3.2 Computer selection............................................................................................. 3 2.3.3 Validate .............................................................................................................. 4 2.4 Advanced Wizard....................................................................................................... 5 2.4.1
    [Show full text]
  • 007-2007: the FILENAME Statement Revisited
    SAS Global Forum 2007 Applications Development Paper 007-2007 The FILENAME Statement Revisited Yves DeGuire, Statistics Canada, Ottawa, Ontario, Canada ABSTRACT The FILENAME statement has been around for a long time for connecting external files with SAS®. Over the years, it has grown quite a bit to encompass capabilities that go beyond the simple sequential file. Most SAS programmers have used the FILENAME statement to read/write external files stored on disk. However, few programmers have used it to access devices other than disk or to interface with different access methods. This paper focuses on some of those capabilities by showing you some interesting devices and access methods supported by the FILENAME statement. INTRODUCTION – FILENAME STATEMENT 101 The FILENAME statement is a declarative statement that is used to associate a fileref with a physical file or a device. A fileref is a logical name that can be used subsequently in lieu of a physical name. The syntax for the FILENAME statement is as follows: FILENAME fileref <device-type> <'external-file'> <options>; This is the basic syntax to associate an external file or a device to a fileref. There are other forms that allow you to list or clear filerefs. Please refer to SAS OnlineDoc® documentation for a complete syntax of the FILENAME statement. Once the association has been made between a physical file and a fileref, the fileref can be used in as many DATA steps as necessary without having to re-run a FILENAME statement. Within a DATA step, the use of an INFILE or a FILE statement allows the programmer to determine which file to read or write using an INPUT or a PUT statement.
    [Show full text]
  • Download File Management and Processing Tools
    File Management and Processing Tools Published January 2018 CONTACT US Division of Library, Archives and Museum Collections | [email protected] File Management and Processing Tools Contents Introduction ................................................................................................................................................................................... 3 Bulk operations ............................................................................................................................................................................. 3 Duplicate file finding and deduplication ......................................................................................................................................... 4 Disk space analysis....................................................................................................................................................................... 4 Image viewer ................................................................................................................................................................................. 5 Integrity checking .......................................................................................................................................................................... 5 Last Updated January 2018 2 Introduction This guidance document provides a list of software tools that can assist in electronic file management and processing. This document is intended for records managers at state agencies,
    [Show full text]
  • SUGI 23: It's Only Temporary
    Coders© Corner It’s Only Temporary Janet Stuelpner, ASG, Inc., Cary, North Carolina Boris Krol, Pfizer, Inc., New York, New York ABSTRACT METHODOLOGY Very often during an interactive SAS® session, it is In previous versions of the SAS system, it was not necessary to create temporary external files. From possible to define both SAS data sets and ASCII release 6.11 of the SAS System we have the ability files in the same directory. Now there is an easy to create a flat file within the same directory that way to do it. contains SAS data sets. There are benefits to using this new technique. This paper will show you how to FILENAME fileref CATALOG ‘catalog’; define this file in the WORK directory and the benefits of its use. Above is a very general FILENAME statement. The words in upper case are required to remain the INTRODUCTION same. The fileref can be any valid file reference. The ‘catalog’ must be in the form: It is easy to create a permanent file using a LIBNAME statement for SAS data sets or a library.catalog.entry.entrytype FILENAME statement for external files. However, each operating system has its own mechanism for where library must be WORK and entrytype must be creating a file that is temporary in nature. By SOURCE. If this structure is adhered to, the definition, a temporary file, whether it is a SAS data temporary file will be created in the WORK set or an external file, is one that is deleted at the directory. The most common temporary library is end of the SAS session.
    [Show full text]
  • 11.6. Tempfile — Generate Temporary Files and Directories — Python V2
    Navigation • index • modules | • next | • previous | • Python v2.6.4 documentation » • The Python Standard Library » • 11. File and Directory Access » 11.6. tempfile — Generate temporary files and directories¶ This module generates temporary files and directories. It works on all supported platforms. In version 2.3 of Python, this module was overhauled for enhanced security. It now provides three new functions, NamedTemporaryFile(), mkstemp(), and mkdtemp(), which should eliminate all remaining need to use the insecure mktemp() function. Temporary file names created by this module no longer contain the process ID; instead a string of six random characters is used. Also, all the user-callable functions now take additional arguments which allow direct control over the location and name of temporary files. It is no longer necessary to use the global tempdir and template variables. To maintain backward compatibility, the argument order is somewhat odd; it is recommended to use keyword arguments for clarity. The module defines the following user-callable functions: tempfile.TemporaryFile([mode='w+b'[, bufsize=-1[, suffix=''[, prefix='tmp'[, dir=None]]]]])¶ Return a file-like object that can be used as a temporary storage area. The file is created using mkstemp(). It will be destroyed as soon as it is closed (including an implicit close when the object is garbage collected). Under Unix, the directory entry for the file is removed immediately after the file is created. Other platforms do not support this; your code should not rely on a temporary file created using this function having or not having a visible name in the file system. The mode parameter defaults to 'w+b' so that the file created can be read and written without being closed.
    [Show full text]