DOCSLIB.ORG

RIDGE ROS Text Editing Guide

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
RIDGE ROS Text Editing Guide ROS Text Editing Guide RIDGE 9051 'A ROS Text Editing Guide RIdge Computers Santa Clara, CA first edition: 9051 (SEP 84) © Copyright 1984, Ridge Computers. All rights reserved. Printed in the U.S.A. PUBLICATION HISTORY Manual TItle: ROS Text Editing Guide first editon: 9051 (SEP 84) NonCE No part of this document may be translated, reproduced, or copied in any form or by any means without the written permission of Ridge Computers. The information contained in this document is subject to change without notice. Ridge Computers shall not be liable for errors contained herein, or for incidental or consequential damages in connection with the use of this material. ACKNOWLEDGEMENT This software and documentation is based in part on the fourth Berkeley Software Distribution, under license from the regents of the University of California. We acknowledge the following individuals for their part in its development: Ken Arnold, Rick Blau, Earl Cohen, Robert Corbett, John Foderaro, Mark Horton, Bill Joy, Randy King, Jim Kleckner, Steve Levine, Colin McMaster, Geoffrey Peck, Rob Pike, Eric Scott, and Eric Shienbrood. These tutorial guides are based on documents created at Bell Laboratories to describe UNIX System software, and at the University of California, Berkeley, to describe bsd 4.2. Credits are given on the first page of each document contained in this volume. Some text has been changed to more accurately describe Ridge Computers' implementation of the software. Inappropriate material may have been deleted. UNIX is a trademark of Bell Laboratories. -ii- 9051 PREFACE The ROS Text Editing Guide (manual 9051) is a collection of tutorial documents on text,. editing software available with the Ridge Operating System. These sections supplement the editor reference pages in the ROS Reference Manual (9010). TABLE OF CONTENTS Tab ROS Reference Label Manual Page RED IT - Ridge Editor redit( 1) ED - ED editor ed( 1) Advanced ED - more on ED ed( 1) EX ref - EX editor reference section eX(1) EDIT - EDIT editor edit( 1) EX JED IT - EX and EDIT combined reference ex( 1), edit( 1) VI - VI editor introduction vie 1) VI ref - VI editor reference section vie 1) SED - Stream Editor sed( 1) 9051 -iii- -iv- 9051 REDIT - Ridge Text Editor Reference Manual CHAPTER I INTRODUCTION This manual documents redit, the Ridge text editor. An explanation of each of the com­ mands and operations is given, as well as a short tutorial. This manual also explains differences encountered between the Ridge Monochrome Display and the Text Terminal (Televideo 950). After having read this document, the reader should be able to create and edit files using redit, using either type of terminal. No knowledge of the Ridge 32 system on the reader's part is assumed beyond a minimal acquaintance with the operating system. The reader is referred to the R£dge Operat£ng System (ROS) Reference Manual for such basic operating system information as particu­ lars of file and directory structure, and allocation information for discs. OVERVIEW The Ridge text editor, redit, is a full-screen, strikeover editor that allows the user to create and modify text files. This chapter briefly describes redit and discusses file struc­ ture and types, display formats, and selected blocks and windows. Redit combines the attributes of a screen- and a line-oriented editor in such a way that the user can define and modify entire blocks of text while retaining control over indivi­ dual line operations. Screen-oriented attributes allow such features as windows and powerful block commands. The combination of these features allows the user simultane­ ous access into different areas of a file or multiple files (Figure 1). Line-oriented attri­ butes allow the user to perform operations such as insert/delete line or character, or search-and-replace with various options, as well as to build user-definable command files that execute complex/repetitive editing functions. Redit is not a formatting program; post-processing (with nroff, for example) is necessary to format output. Nor is redit a multiple mode editor; the editor is always in strikeover mode. Changes or alterations are made by overwriting text directly on the display. ·9051A -1- Text Editing REDIT Screen Movable Window Text File Figure 1. Windows on Text File Editing is performed using function and other editing keys, and through commands entered on the command line. (Virtually all keyboard keys function normally with reclit­ -e.g., backspace moves one character left.) Editing capabilities are thus broken into two groups: • EDITOR COMMANDS With this group, the liser enters the command into the command entry area (top line) of the screen. • PREDEFINED OPERATIONS These operations are invoked directly by function keys. The predefined operations have been imple­ mented using various combinations of the editing commands, and represent the most commonly used editing tasks. GENERAL DESCRIPTION This section describes the logical structure of text files, ASCII and work files, screen for­ mats, and the concept of selected blocks and windows. Logical Structure of Text Files A text file consists of a set of records referred to as lines. Each line has a length attri­ bute; the length describes the position of the last non-blank character in the line. The length of a line may range from zero (0) to 128 characters. A length of zero denotes a blank line. -2- 9051A Text Editing REDIT Each line can be identified by its position relative to the beginning of the file. The posi­ tion (line number) has a value in the range of 0 to 99,999,999, inclusive. Lines are effectively renumbered if preceding lines are inserted or deleted. Ascn Files and Work Files "ASCII file" refers to a file that is directly readable by such Ridge subsystems as the editor, language compilers, and utility programs. When an existing ASCII file is to be edited, the file is first copied to a "work file." The work file provides rapid, random access to any place in the text; this file is not directly readable by other Ridge subsys­ tems. During the editing session, changes to the text are made only to the work file, not to the ASCII file. At the end of the editing session, the text portion of the work file is copied to a new ASCII file. The work file is saved by default between editing sessions, which provides three benefits: time spent copying the ASCII file to the text file at the beginning of the editing session is eliminated, some contextual information (such as current position in the file and tab settings) is maintained across editing sessions, and the work file is an additional backup to the ASCII file. (Chapter 3 explains how to save a "lost" work file. In the user's directory, the work file bears a ".e" extension to the original ASCII file name. So, for an ASCII source file named "prime.s", a work file named "prime.s.e" is created. Screen Format The Ridge system supports two terminals: the Ridge Monochrome Display and the Text Terminal (Televideo TVI-950C). The Monochrome Display is bit-mapped and a range of font sizes have been developed for it; consequently, the screen format varies according to font size. While the Monochrome Display does not display exactly 72 increments per inch, the font sizes are close approximations to those of typographic fonts. Figure 2 shows the screen format for the Monochrome Display and Figure 3 that of the Text Terminal. 1 ................. 30 .......................................... 128 +------------------------------------------------------~-----//----+ 1 <adv/cmd> I] <advisory> : [<command input area> I 2 <hdr/sel> I] <fname> @ <tline> I <sfname> <stline .. > <sbline> I 3 <text1> I [ I 4 <text2> I I 5 <text3> I I 49 <text47> I I 50 <cmd> IS1:Select S2:Clear S3:Copy S4:Move S5:Break S6:Fill S7:XeqCmd S8:Exit +---------------------------------~--------------------------//----+ Figure 2. Monochrome Display Screen Format 9051A -3- Text Editing REDIT 1 ................. 30 ................................. ; ........ 80 +------------------------------------------------------------//----+ 1 <adv/cmd> I]<advisory> : [<command input area> I 2 <hdr/se1> I]<fname> @ <t1ine> I <sfname> <st1ine .. > <sb1ine> I 3 <text1> I [ I 4 <text2> I I 5 <text3> I I 24 <text22> I I 25 <cmd> 11:Prev 2~Next 3:Se1 4:Copy 5:Brk 6:Fi11 7:Undo 8:A 9:B 10:C 11:Cmdl +------------------------------------------------------------//----+ Figure 3. Text Terminal Screen Format In these illustrations, the following notation is used: ] Denotes the beginning of an area into which the user cannot enter text (a protected area). [ Denotes the beginning of an area into which the user can enter text (an unprotected area). <adv/cmd> Advisory /command area. <advisory> is where error messages are displayed; <command input area> is where editor commands can be entered. <hdr/sel> Window header and selection status area. The window header con­ sists of three parts: <fname> The name of the file visible in the window. @ The currency indicator which is displayed if the window is current. <tline> The line number of the line at the top of the window. indent The selection status area displays the state of the currently selected block of text (see the SELECT command). The selection status area consists of three parts: . <sfname> The name of the file containing the currently selected block. <stline> The line number of the top line of the currently selected block. (On the Monochrome Display, <stline> is used to indicate both the top and bottom lines of a selected block for sizes 16 and above because the screen isn't wide enough to accommodate the <sbline> field for these larger fonts.) <sbline> The line number of the bottom line of the currently selected block. <textl .. n> Area of the screen in which text is displayed. The cursor may be placed anywhere within this block for editing; entering text over exist­ ing text automatically replaces that text.
Load more

Recommended publications
  • Administering Unidata on UNIX Platforms
    C:\Program Files\Adobe\FrameMaker8\UniData 7.2\7.2rebranded\ADMINUNIX\ADMINUNIXTITLE.fm March 5, 2010 1:34 pm Beta Beta Beta Beta Beta Beta Beta Beta Beta Beta Beta Beta Beta Beta Beta Beta UniData Administering UniData on UNIX Platforms UDT-720-ADMU-1 C:\Program Files\Adobe\FrameMaker8\UniData 7.2\7.2rebranded\ADMINUNIX\ADMINUNIXTITLE.fm March 5, 2010 1:34 pm Beta Beta Beta Beta Beta Beta Beta Beta Beta Beta Beta Beta Beta Notices Edition Publication date: July, 2008 Book number: UDT-720-ADMU-1 Product version: UniData 7.2 Copyright © Rocket Software, Inc. 1988-2010. All Rights Reserved. Trademarks The following trademarks appear in this publication: Trademark Trademark Owner Rocket Software™ Rocket Software, Inc. Dynamic Connect® Rocket Software, Inc. RedBack® Rocket Software, Inc. SystemBuilder™ Rocket Software, Inc. UniData® Rocket Software, Inc. UniVerse™ Rocket Software, Inc. U2™ Rocket Software, Inc. U2.NET™ Rocket Software, Inc. U2 Web Development Environment™ Rocket Software, Inc. wIntegrate® Rocket Software, Inc. Microsoft® .NET Microsoft Corporation Microsoft® Office Excel®, Outlook®, Word Microsoft Corporation Windows® Microsoft Corporation Windows® 7 Microsoft Corporation Windows Vista® Microsoft Corporation Java™ and all Java-based trademarks and logos Sun Microsystems, Inc. UNIX® X/Open Company Limited ii SB/XA Getting Started The above trademarks are property of the specified companies in the United States, other countries, or both. All other products or services mentioned in this document may be covered by the trademarks, service marks, or product names as designated by the companies who own or market them. License agreement This software and the associated documentation are proprietary and confidential to Rocket Software, Inc., are furnished under license, and may be used and copied only in accordance with the terms of such license and with the inclusion of the copyright notice.
    [Show full text]
  • AEDIT Text Editor Iii Notational Conventions This Manual Uses the Following Conventions: • Computer Input and Output Appear in This Font
    Quick Contents Chapter 1. Introduction and Tutorial Chapter 2. The Editor Basics Chapter 3. Editing Commands Chapter 4. AEDIT Invocation Chapter 5. Macro Commands Chapter 6. AEDIT Variables Chapter 7. Calc Command Chapter 8. Advanced AEDIT Usage Chapter 9. Configuration Commands Appendix A. AEDIT Command Summary Appendix B. AEDIT Error Messages Appendix C. Summary of AEDIT Variables Appendix D. Configuring AEDIT for Other Terminals Appendix E. ASCII Codes Index AEDIT Text Editor iii Notational Conventions This manual uses the following conventions: • Computer input and output appear in this font. • Command names appear in this font. ✏ Note Notes indicate important information. iv Contents 1 Introduction and Tutorial AEDIT Tutorial ............................................................................................... 2 Activating the Editor ................................................................................ 2 Entering, Changing, and Deleting Text .................................................... 3 Copying Text............................................................................................ 5 Using the Other Command....................................................................... 5 Exiting the Editor ..................................................................................... 6 2 The Editor Basics Keyboard ......................................................................................................... 8 AEDIT Display Format ..................................................................................
    [Show full text]
  • COMMAND LINE CHEAT SHEET Presented by TOWER — the Most Powerful Git Client for Mac
    COMMAND LINE CHEAT SHEET presented by TOWER — the most powerful Git client for Mac DIRECTORIES FILES SEARCH $ pwd $ rm <file> $ find <dir> -name "<file>" Display path of current working directory Delete <file> Find all files named <file> inside <dir> (use wildcards [*] to search for parts of $ cd <directory> $ rm -r <directory> filenames, e.g. "file.*") Change directory to <directory> Delete <directory> $ grep "<text>" <file> $ cd .. $ rm -f <file> Output all occurrences of <text> inside <file> (add -i for case-insensitivity) Navigate to parent directory Force-delete <file> (add -r to force- delete a directory) $ grep -rl "<text>" <dir> $ ls Search for all files containing <text> List directory contents $ mv <file-old> <file-new> inside <dir> Rename <file-old> to <file-new> $ ls -la List detailed directory contents, including $ mv <file> <directory> NETWORK hidden files Move <file> to <directory> (possibly overwriting an existing file) $ ping <host> $ mkdir <directory> Ping <host> and display status Create new directory named <directory> $ cp <file> <directory> Copy <file> to <directory> (possibly $ whois <domain> overwriting an existing file) OUTPUT Output whois information for <domain> $ cp -r <directory1> <directory2> $ curl -O <url/to/file> $ cat <file> Download (via HTTP[S] or FTP) Copy <directory1> and its contents to <file> Output the contents of <file> <directory2> (possibly overwriting files in an existing directory) $ ssh <username>@<host> $ less <file> Establish an SSH connection to <host> Output the contents of <file> using
    [Show full text]
  • Windows Command Prompt Cheatsheet
    Windows Command Prompt Cheatsheet - Command line interface (as opposed to a GUI - graphical user interface) - Used to execute programs - Commands are small programs that do something useful - There are many commands already included with Windows, but we will use a few. - A filepath is where you are in the filesystem • C: is the C drive • C:\user\Documents is the Documents folder • C:\user\Documents\hello.c is a file in the Documents folder Command What it Does Usage dir Displays a list of a folder’s files dir (shows current folder) and subfolders dir myfolder cd Displays the name of the current cd filepath chdir directory or changes the current chdir filepath folder. cd .. (goes one directory up) md Creates a folder (directory) md folder-name mkdir mkdir folder-name rm Deletes a folder (directory) rm folder-name rmdir rmdir folder-name rm /s folder-name rmdir /s folder-name Note: if the folder isn’t empty, you must add the /s. copy Copies a file from one location to copy filepath-from filepath-to another move Moves file from one folder to move folder1\file.txt folder2\ another ren Changes the name of a file ren file1 file2 rename del Deletes one or more files del filename exit Exits batch script or current exit command control echo Used to display a message or to echo message turn off/on messages in batch scripts type Displays contents of a text file type myfile.txt fc Compares two files and displays fc file1 file2 the difference between them cls Clears the screen cls help Provides more details about help (lists all commands) DOS/Command Prompt help command commands Source: https://technet.microsoft.com/en-us/library/cc754340.aspx.
    [Show full text]
  • Getting to Grips with Unix and the Linux Family
    Getting to grips with Unix and the Linux family David Chiappini, Giulio Pasqualetti, Tommaso Redaelli Torino, International Conference of Physics Students August 10, 2017 According to the booklet At this end of this session, you can expect: • To have an overview of the history of computer science • To understand the general functioning and similarities of Unix-like systems • To be able to distinguish the features of different Linux distributions • To be able to use basic Linux commands • To know how to build your own operating system • To hack the NSA • To produce the worst software bug EVER According to the booklet update At this end of this session, you can expect: • To have an overview of the history of computer science • To understand the general functioning and similarities of Unix-like systems • To be able to distinguish the features of different Linux distributions • To be able to use basic Linux commands • To know how to build your own operating system • To hack the NSA • To produce the worst software bug EVER A first data analysis with the shell, sed & awk an interactive workshop 1 at the beginning, there was UNIX... 2 ...then there was GNU 3 getting hands dirty common commands wait till you see piping 4 regular expressions 5 sed 6 awk 7 challenge time What's UNIX • Bell Labs was a really cool place to be in the 60s-70s • UNIX was a OS developed by Bell labs • they used C, which was also developed there • UNIX became the de facto standard on how to make an OS UNIX Philosophy • Write programs that do one thing and do it well.
    [Show full text]
  • Georgia Department of Revenue
    Form MV-9W (Rev. 6-2015) Web and MV Manual Georgia Department of Revenue - Motor Vehicle Division Request for Manufacture of a Special Veteran License Plate ______________________________________________________________________________________ Purpose of this Form: This form is to be used to apply for a military license plate/tag. This form should not be used to record a change of ownership, change of address, or change of license plate classification. Required documentation: You must provide a legible copy of your service discharge (DD-214, DD-215, or for World War II veterans, a WD form) indicating your branch and term of service. If you are an active duty member, a copy of the approved documentation supporting your current membership in the respective reserve or National Guard unit is required. In the case of a retired reserve member from that unit, you must furnish approved documentation supporting the current retired membership status from that reserve unit. OWNER INFORMATION First Name Middle Initial Last Name Suffix Owners’ Full Legal Name: Mailing Address: City: State: Zip: Telephone Number: Owner(s)’ Full Legal Name: First Name Middle Initial Last Name Suffix If secondary Owner(s) are listed Mailing Address: City: State: Zip: Telephone Number: VEHICLE INFORMATION Passenger Vehicle Motorcycle Private Truck Vehicle Identification Number (VIN): Year: Make: Model: CAMPAIGN/TOUR of DUTY Branch of Service: SERVICE AWARD Branch of Service: LICENSE PLATES ______________________ LICENSE PLATES ______________________ World War I World
    [Show full text]
  • Dot at Command Firmware Release 4.0.0 Release 3.3.5
    Product Change Notification Software Release Notes Dot AT Command Firmware Release 4.0.0 Release 3.3.5 MultiTech xDot® MultiTech mDot™ Date: March 30, 2021 Contents Product Change Notification (PCN) Number PCN 03302021-001 (Dot) I. Overview II. Suggested Action Plan I. Overview MultiTech announces the availability of new AT Command III. Release 4.0.0 Overview Firmware for use on MultiTech® Long Range LoRa® Modules: MultiTech xDot® (MTXDOT Series) IV. Release 3.3.5 Overview MultiTech mDot™ (MTDOT Series) V. Schedule New versions are currently available for download and VI. Flashing mDot Firmware evaluation: VII. Part Numbers Impacted Release 4.0.0 (shipping in June 2021) Release 3.3.5 VIII. Mbed OS Overview IX. xDot Overview Release 4.0.0 will released into standard MultiTech product starting in June 2021. Currently, product ships with X. mDot Overview Release 3.2.1 XI. xDot Micro Developer Kit II. Suggested Action Plan XII. Additional Information Customers Review the information in this PCN and forward to Attachments others within your organization who are actively Identifying Firmware Version involved with the development of IoT applications using the MultiTech xDot and MultiTech mDot. Identifying Date of Manufacture Consider downloading the firmware available on MultiTech or Mbed websites to check compatibility mPower & mLinux Software with existing deployments. PCN 03302021-001 (Dot) Page 1 of 12 https://support.multitech.com Review the release schedule for the upcoming firmware release and understand the effect on your manufacturing and deployment schedules. Distributors Forward this announcement to others within your organization who are actively involved in the sale or support of LoRa-enabled sensors.
    [Show full text]
  • Dell EMC Powerstore CLI Guide
    Dell EMC PowerStore CLI Guide May 2020 Rev. A01 Notes, cautions, and warnings NOTE: A NOTE indicates important information that helps you make better use of your product. CAUTION: A CAUTION indicates either potential damage to hardware or loss of data and tells you how to avoid the problem. WARNING: A WARNING indicates a potential for property damage, personal injury, or death. © 2020 Dell Inc. or its subsidiaries. All rights reserved. Dell, EMC, and other trademarks are trademarks of Dell Inc. or its subsidiaries. Other trademarks may be trademarks of their respective owners. Contents Additional Resources.......................................................................................................................4 Chapter 1: Introduction................................................................................................................... 5 Overview.................................................................................................................................................................................5 Use PowerStore CLI in scripts.......................................................................................................................................5 Set up the PowerStore CLI client........................................................................................................................................5 Install the PowerStore CLI client..................................................................................................................................
    [Show full text]
  • Linking + Libraries
    LinkingLinking ● Last stage in building a program PRE- COMPILATION ASSEMBLY LINKING PROCESSING ● Combining separate code into one executable ● Linking done by the Linker ● ld in Unix ● a.k.a. “link-editor” or “loader” ● Often transparent (gcc can do it all for you) 1 LinkingLinking involves...involves... ● Combining several object modules (the .o files corresponding to .c files) into one file ● Resolving external references to variables and functions ● Producing an executable file (if no errors) file1.c file1.o file2.c gcc file2.o Linker Executable fileN.c fileN.o Header files External references 2 LinkingLinking withwith ExternalExternal ReferencesReferences file1.c file2.c int count; #include <stdio.h> void display(void); Compiler extern int count; int main(void) void display(void) { file1.o file2.o { count = 10; with placeholders printf(“%d”,count); display(); } return 0; Linker } ● file1.o has placeholder for display() ● file2.o has placeholder for count ● object modules are relocatable ● addresses are relative offsets from top of file 3 LibrariesLibraries ● Definition: ● a file containing functions that can be referenced externally by a C program ● Purpose: ● easy access to functions used repeatedly ● promote code modularity and re-use ● reduce source and executable file size 4 LibrariesLibraries ● Static (Archive) ● libname.a on Unix; name.lib on DOS/Windows ● Only modules with referenced code linked when compiling ● unlike .o files ● Linker copies function from library into executable file ● Update to library requires recompiling program 5 LibrariesLibraries ● Dynamic (Shared Object or Dynamic Link Library) ● libname.so on Unix; name.dll on DOS/Windows ● Referenced code not copied into executable ● Loaded in memory at run time ● Smaller executable size ● Can update library without recompiling program ● Drawback: slightly slower program startup 6 LibrariesLibraries ● Linking a static library libpepsi.a /* crave source file */ … gcc ..
    [Show full text]
  • EZ-SCREEN LP Instruction Manual
    EZ-SCREEN® LP Low-Profile Safety Light Screen Instruction Manual Original Instructions 140044 Rev. G 27 April 2018 © Banner Engineering Corp. All rights reserved 140044 EZ-SCREEN® LP Low-Profile Safety Light Screen Contents 1 About This Document .............................................................................................................................................5 1.1 Important . Read This Before Proceeding! .....................................................................................................................5 1.2 Use of Warnings and Cautions ...........................................................................................................................................5 1.3 EU Declaration of Conformity (DoC) ..................................................................................................................................5 1.4 Banner Engineering Corp Limited Warranty ......................................................................................................................6 1.5 Contact Us ......................................................................................................................................................................... 6 2 Introduction ............................................................................................................................................................ 8 2.1 Features .............................................................................................................................................................................8
    [Show full text]
  • AR400 User Guide 2.7.1
    AR400 SERIES User Guide Software Release 2.7.1 AR410 AR440S AR441S AR450S AR400 Series Router User Guide for Software Release 2.7.1 Document Number C613-02021-00 REV F. Copyright © 2004 Allied Telesyn International Corp. 19800 North Creek Parkway, Suite 200, Bothell, WA 98011, USA. All rights reserved. No part of this publication may be reproduced without prior written permission from Allied Telesyn. Allied Telesyn International Corp. reserves the right to make changes in specifications and other information contained in this document without prior written notice. The information provided herein is subject to change without notice. In no event shall Allied Telesyn be liable for any incidental, special, indirect, or consequential damages whatsoever, including but not limited to lost profits, arising out of or related to this manual or the information contained herein, even if Allied Telesyn has been advised of, known, or should have known, the possibility of such damages. All trademarks are the property of their respective owner. Contents CHAPTER 1 Introduction Why Read this User Guide? ............................................................................... 7 Where To Find More Information ...................................................................... 8 The Documentation Set .............................................................................. 8 Technical support .............................................................................................. 9 Features of the Router .....................................................................................
    [Show full text]
  • Your Performance Task Summary Explanation
    Lab Report: 11.2.5 Manage Files Your Performance Your Score: 0 of 3 (0%) Pass Status: Not Passed Elapsed Time: 6 seconds Required Score: 100% Task Summary Actions you were required to perform: In Compress the D:\Graphics folderHide Details Set the Compressed attribute Apply the changes to all folders and files In Hide the D:\Finances folder In Set Read-only on filesHide Details Set read-only on 2017report.xlsx Set read-only on 2018report.xlsx Do not set read-only for the 2019report.xlsx file Explanation In this lab, your task is to complete the following: Compress the D:\Graphics folder and all of its contents. Hide the D:\Finances folder. Make the following files Read-only: D:\Finances\2017report.xlsx D:\Finances\2018report.xlsx Complete this lab as follows: 1. Compress a folder as follows: a. From the taskbar, open File Explorer. b. Maximize the window for easier viewing. c. In the left pane, expand This PC. d. Select Data (D:). e. Right-click Graphics and select Properties. f. On the General tab, select Advanced. g. Select Compress contents to save disk space. h. Click OK. i. Click OK. j. Make sure Apply changes to this folder, subfolders and files is selected. k. Click OK. 2. Hide a folder as follows: a. Right-click Finances and select Properties. b. Select Hidden. c. Click OK. 3. Set files to Read-only as follows: a. Double-click Finances to view its contents. b. Right-click 2017report.xlsx and select Properties. c. Select Read-only. d. Click OK. e.
    [Show full text]