Microsoft WordArt 2.0
Microsoft WordArt 2.0 MSWordArt.2 MSWordArt.2 WordArt Weird Aaaaarrrrggghhhhhh! Charles V. Balch, Spring 96. Ver. 1 Using computers and computer applications is occasionally frustrating. You will encounter “impossible” tasks, equipment failure and “unpredicted” results. An important part of learning to use computers is learning how to deal with and minimize these frustrations. SAVE YOUR WORK OFTEN! I tend to save at least every five minutes or whenever something “odd” happens. Don’t get frustrated. Mistakes are a part of life. Stop. Think. Relax. Don’t try to get your work done at the last minute. Tasks are much easier soon after the material has been covered and not immediately before they are due. Try repeating command sequences that should work. Perhaps you accidentally hit the wrong key. Don’t repeat the same command more than three times. If it is not working, figure out why. Don’t spend more than about five minutes repeating the things that don’t work. Getting frustrated does not help. Try things that MIGHT work. Look up the commands. Make sure that you have them right. …
Download the original document · Plain text (TXT) · Browse the archive · How this archive works
Original source: https://web.archive.org/web/19961207065807id_/http://manta.uvi.edu:80/cerit/classdoc/WINDOWS/help.doc
SHA-256 af8c5d31260bc28aa90bd428a523ce456f89f8d003db4ac3e64601a8288cf433
Re-using this document
Our description, tagging, arrangement, extracted text and machine transcripts are released under CC0 1.0. We assert nothing about the document itself.
Archive identifier LF-af8c5d31260b
Document text
Microsoft WordArt 2.0 MSWordArt.2 MSWordArt.2 WordArt Weird Aaaaarrrrggghhhhhh! Charles V. Balch, Spring 96. Ver. 1 Using computers and computer applications is occasionally frustrating. You will encounter “impossible” tasks, equipment failure and “unpredicted” results. An important part of learning to use computers is learning how to deal with and minimize these frustrations. SAVE YOUR WORK OFTEN! I tend to save at least every five minutes or whenever something “odd” happens. Don’t get frustrated. Mistakes are a part of life. Stop. Think. Relax. Don’t try to get your work done at the last minute. Tasks are much easier soon after the material has been covered and not immediately before they are due. Try repeating command sequences that should work. Perhaps you accidentally hit the wrong key. Don’t repeat the same command more than three times. If it is not working, figure out why. Don’t spend more than about five minutes repeating the things that don’t work. Getting frustrated does not help. Try things that MIGHT work. Look up the commands. Make sure that you have them right. Help is everywhere. Look to manuals, third party books, and more knowledgeable persons (me, lab monitors, people sitting next to you). Try pressing the help button (F1). Look under the help menu for cue cards and/or a tutorial. If you are getting nowhere, finish the parts that you can. Maybe you did something . Perhaps you accidentally gave a command that causes the computer to act oddly. If you can’t figure out how to get out of your corner, save your work, exit Windows, log off, turn the computer off and start again. Maybe the computer is . Try using another computer. Check for viruses. There is a virus scanner on the login menu. Keep a notebook. Write descriptions of problems and their solutions (when you get them). Save and print the parts of your tasks that you could accomplish. Did I mention to save your work? Save your work. Make a backup of your disk! At some point it will probably be lost or destroyed. Remember that computers are not always logical. Try to figure out how the programmers were thinking. The same command will always do the same thing under the same circumstances. Have the circumstances changed? Programming Concerns and Tricks Make sure that you understand the problem. Try working out the problem on paper. Write your code to mimic the steps you used to get your solution. Don’t get fancy. Make sure your program works before adding bells and whistles. Watch those variables. Step through your program with a debug watch window or create many temporary message boxes to report your values. Use descriptive variable names. Follow that code. Does your program execute in the order you expect it to? Make sure you have a general solution. What happens when a user enters “wrong” data? Is the data really wrong or did you just not anticipate it. FILENAME \p \* MERGEFORMAT H:\!DOCS\CLASSDOC\WINDOWS\HELP.DOC 9Fîu Microsoft WordArt 2.0 MSWordArt.2 MSWordArt.2 WordArt Weird ÷$,1 ExSt H:\!DOCS\MSOFFICE\WINWORD\TEMPLATE\NORMAL.DOT GENERAL HINTS Charles V. Balch Charles V. Balch Aaaaarrrrggghhhhhh! Charles V. Balch, Spring 96. Ver. 1 Using computers and computer applications is occasionally frustrating. You will encounter “impossible” tasks, equipment failure and “unpredicted” results. An important part of learning to use computers is learning how to deal with and minimize these frustrations. SAVE YOUR WORK OFTEN! I tend to save at least every five minutes or whenever something “odd” happens. Don’t get frustrated. Mistakes are a part of life. Stop. Think. Relax. Don’t try to get your work done at the last minute. Tasks are much easier soon after the material has been covered and not immediately before they are due. Try repeating command sequences that should work. Perhaps you accidentally hit the wrong key. Don’t repeat the same command more than three times. If it is not working, figure out why. Don’t spend more than about five minutes repeating the things that don’t work. Getting frustrated does not help. Try things that MIGHT work. Look up the commands. Make sure that you have them right. Help is everywhere. Look to manuals, third party books, and more knowledgeable persons (me, lab monitors, people sitting next to you). Try pressing the help button (F1). Look under the help menu for cue cards and/or a tutorial. If you are getting nowhere, finish the parts that you can. Maybe you did something . Perhaps you accidentally gave a command that causes the computer to act oddly. If you can’t figure out how to get out of your corner, save your work, exit Windows, log off, turn the computer off and start again. Maybe the computer is . Try using another computer. Check for viruses. There is a virus scanner on the login menu. Keep a notebook. Write descriptions of problems and their solutions (when you get them). Save and print the parts of your tasks that you could accomplish. Did I mention to save your work? Save your work. Make a backup of your disk! At some point it will probably be lost or destroyed. Remember that computers are not always logical. Try to figure out how the programmers were thinking. The same command will always do the same thing under the same circumstances. Have the circumstances changed? Programming Concerns and Tricks Make sure that you understand the problem. Try working out the problem on paper. Write your code to mimic the steps you used to get your solution. Don’t get fancy. Make sure your program works before adding bells and whistles. Watch those variables. Step through your program with a debug watch window or create many temporary message boxes to report your values. Use descriptive variable names. Follow that code. Does your program execute in the order you expect it to? Make sure you have a general solution. What happens when a user enters “wrong” data? Is the data really wrong or did you just not anticipate it. FILENAME \p \* MERGEFORMAT H:\!DOCS\CLASSDOC\WINDOWS\HELP.DOC lVä3UK lVä3Ua /Vä3UK /Vä3Ua Normal Heading 1 Heading 2 Heading 3 Heading 4 Heading 5 Heading 6 Default Paragraph Font Header Footnote Text List Table Footnote Reference Bibliography Example Quote Question Answer wfxRecipient wfxFaxNum Heading UVZc0 Telecom_Out Telecom_In Page_Heading wfxDate Title_Heading wfxTime wfxSubject Footer Charles V. Balch"H:\!DOCS\CLASSDOC\WINDOWS\HELP.DOCÿ@HP LaserJet 4 Plus/4M Plus LPT3: HPPCL5E HP LaserJet 4 Plus/4M Plus HP LaserJet 4 Plus/4M Plus Symbol Palatino Book Antiqua Wingdings Courier Courier New 4cö% GENERAL HINTS Charles V. Balch Charles V. Balch