In this chapter:
You can do more with Windows than play Solitaire (most days, anyway). Here's
how to set up new programs--and your old favorites, too...
When you add a new program to your PC, it has to go through a short getting-acquainted
drill with the rest of your computer. The whole process is not that different from
what you would do during the new-employee orientation program your first day on a
new job. You'll meet the folks in the mail room, someone will issue you a phone number
and a badge, and you'll pick up an armload of office supplies. After that, the boss
will show you your new cubicle and your old computer (unless you landed a really
great job, that is, in which case you'll get a corner office and a shiny new Pentium
PC).
So, how does orientation work for a new application program? First, it has to check in with Windows, and then, if necessary, it introduces itself to other programs you use. It has to find a home folder, and it has to make a note of any special instructions that you give it. Sound like a lot of administrative overhead? It needn't be. A good installation program takes care of all those details behind the scenes.
The nice thing about Windows programs is that they all work pretty much alike, starting with the installation. Most of the time, setting up a new application is a simple point-and-click proposition. But you can speed up the process if you know how to add a new piece of Windows software to your system.
These days, most software arrives on a handful of floppy disks or a CD-ROM. The most popular way to get started is to put a disk in your drive and run an installation program--usually called Setup. It's so easy, in fact, that Windows can do the process automatically: click the Start button and choose Settings, Control Panel; then double-click the Add/Remove Programs icon. You'll see a dialog box like the one in Figure 10.1. Click the Install button, and follow the wizard's instructions, clicking Next and then Finish as you complete each step.
Fig. 10.1
To set up a new Windows program (or get rid of one you don't want anymore), use the Add/Remove Programs utility in the Windows Control Panel.
TIP: Some programs have taken the idea of automatic installation to an extreme.
With some AutoPlay CD-ROMs, for example, all you have to do is insert the CD into your drive and click a button. Other programs, especially updated software that you download from Microsoft's World Wide Web site, offers to install itself automatically if you give Windows the OK. When Windows makes this kind of offer, just say yes.
Almost all Windows Setup programs ask the same questions over and over again: In which folder would you like the program files to be stored? Do you want to install all of the program, or just parts of it? Do you want to create a new group of icons cascading out from the Programs entry on the Start menu? Once you've answered all the questions, you're ready for the tedious work of swapping floppy disks. (Unless your software came on a CD-ROM, of course, in which case all you need to do is sit back and watch--once you see the Setup program start to copy files to your hard disk.)
TIP: Just say yes! Windows and Windows programs that use SETUP will almost always suggest the best place to store files. These preferences are called defaults, and you're less likely to get into trouble if you simply accept the defaults. If Microsoft Office wants to create a folder called C:\MSOFFICE, let it.
Occasionally, the Windows Setup program will ask you some more detailed questions. For example, a word processor might ask you if you'd like to install its built-in grammar-checking module, or it might ask for your name and address so it can add that information automatically to your letters and envelopes. In some cases, the program will even order you to shut down Windows and restart so that it can be sure that all the changes it made actually go into effect. Answer the questions as best you can, but don't worry too much: There's no such thing as a failing grade, and you can always run the Setup program again if you miss something important the first time around.
If everything went well, the new program probably added itself to the Start menu. To find the program icon, click the Start button, select Programs, and look for the folder that contains the new icon. When you find it, click and hold your breath. If it starts and runs properly, congratulations! You've successfully installed the new program.
Why does Setup have to be so complicated? Why can't you just copy a bunch of files to your hard disk and get to work? Well, with a few programs you can, but those efficient little marvels are few and far between.
There are good reasons for using the official installation routine, not the least of which is consistency: You can be sure you won't miss an important step.
The Setup routine typically copies all the program files and stores their locations, a description of the data files the application uses, any personal preferences you enter, and all the technical information the program needs to communicate properly with Windows. By the time Setup is done, you might have files scattered all over your hard disk: Besides the application's own folder, you can sometimes find new files in a special Windows NT folder called System32 and in the place where you store your data.
If even one of those pieces is missing, your new application probably won't work.
And that's why it pays to follow the standard operating procedure, even if it seems
a bit overcomplicated.
Q&A: I just added a new program, and now I can't find it. What should I do?
Click the Start button and choose Find, Files or Folders. In the box labeled Named, type part of the name you're looking for. Click the Find Now button, and if you're lucky the shortcut to your program will appear in the list below. If you still can't find it, choose View, Arrange Icons, by Date. The most recent files will float to the top, and your new program may be there. Once you find it, drag its icon onto the Start menu to add it to the top of the list.
The Add/Remove Programs Wizard is convenient, but it isn't actually that smart. It does nothing more than search your floppy disk and CD-ROM for a file called Setup (or Install). What happens when it can't find that file? You'll see a dialog box like the one in Figure 10.2.
Fig. 10.2
Oops! If the Wizard can't finish the job, you'll have to step in and do it yourself. Click the Browse button to start.
What happened? One of two things, probably. Here's what to do in either case:
Fig. 10.3
When the Wizard can't find a Setup program, look for a Setup Information icon like this one, then right-click and choose Install.
Q&A: Windows told me that some of the files I'm trying to install are older than the ones I already have. What's that all about?
When you use the Setup program that comes with some Windows programs (especially older ones), watch carefully as status messages flash by on the screen. Windows will warn you when a program tries to add files to the System or System32 folder on your computer. Now, if the files were from 1993 and you were using a version of Windows that was produced in 1992, this would probably be the right thing to do. But it's definitely a no-no to put those 1993 files in the 1996 version of Windows NT.
Fortunately, Windows anticipates this possibility and asks your permission before it replaces a shiny new file with an out-of-date one. Just keep the newer files and you'll be OK.
When is a Windows program not a Windows program? When it's an old Windows program that doesn't understand how to work with Windows NT 4.0, of course.
Now, there's nothing wrong with being old--sooner or later it happens to all of us. But the single biggest problem with Windows programs that were developed before mid-1995 is that they don't understand how to deal with long file names. If you use one of these older programs, any files you use with that program will be limited to eight characters and a three-character extension.
For a graphic example of the problem, look at Figure 10.4. On the top is the up-to-date Windows NT version of Notepad. Go ahead and open a file--it's not hard to tell what's inside each one. But now look at the old Notepad from Windows 3.1, below. The same files show up with cryptic, confusing names like TO-DOL~1.TXT. Is that your to-do list? Probably, but who can be sure?
Fig. 10.4
One great reason to insist on new, 32-bit versions of your programs. The new Notepad (above) shows you plain-English file names; the old version (below) keeps you guessing.
When you walk into a computer superstore, you'll see aisle after aisle of Windows software. All told, you can take your choice of thousands of programs. Is that good news? Well, that depends. People have been writing Windows programs for years. Some are good programmers, some aren't. Some programs that worked just fine under old versions of Windows will do all sorts of screwy things when you try to use them with Windows NT.
If you've installed a program successfully but encounter odd behavior when you try to run it, don't assume you're doing something wrong. You could be looking at a bug--simply put, whoever wrote the program made a mistake. Sometimes you can work around bugs; other times you can't. But it helps to know what you're up against.
What kind of software should you feed Windows NT? Well, it can digest almost any Windows programs, even those 16-bit programs that were originally designed years ago for Windows 3.1. But Windows NT runs best on a steady diet of new 32-bit software.
What's the difference? Why should you care whether your software is 16 bits or 32?
Each bit represents a digit in Windows' binary counting system, and the total defines how much working room a program has in memory. Programs written in 16 bits can work with a puny 64 kilo- bytes of memory at a time, or roughly as much as you'll find in a pocket calculator. By contrast, 32-bit software means Windows NT programs can use up to 4 gigabytes of memory, which is a lot of breathing room. The old programs spend all their time moving data through this tiny block of memory (a process called paging), while you wait.
All that memory is what makes it possible for Windows NT to keep track of long filenames and to keep multiple programs going without getting confused.
How can you be sure your software is up-to-date? One surefire way is to look on
the box. If the box says it's compatible with Windows NT 4.0, you'll have no problems.
If the box has the Windows 95 logo on it, it's a 32-bit program and will probably
work well with Windows NT (although there are some Windows 95 programs that don't).
And if it's an old 16-bit program (designed for use with Windows 3.1), don't be surprised
if you encounter some problems.
Here are a few of the puzzling symptoms you might see when you run into a bug in
a program.
Plain English, please!Protection? Is this some kind of racket? Nope. Windows is talking about memory. Every program you run should have its own chunk of memory that no other program can touch. If another program's data accidentally gets mixed into that space, there's no telling what can happen. But it's usually not good.
Suppose your office building has a well-organized team of messengers whose job is to carry packages from one suite to another, all day long. Each time a messenger picks up a package, he checks the address label and delivers it to its destination. But what happens if a package is mislabeled? Maybe the freshly ground coffee goes to the person who changes the toner in the copy machine, while the toner ends up in the coffee room. (Bleccchh.)
Windows has built-in protection against this sort of thing, designed to keep your other programs from being damaged by a buggy program. The usual cure is to shut down the guilty program, no questions asked. The moral? Save your data regularly!
Fig. 10.5
Here's what a General Protection Fault error message looks like. It's a warning that something's gone wrong, and displays some techno-babble for any programmer who might be looking over your shoulder.
If your computer consistently acts up when you try to run one particular program, contact the company that made the software (or ask your network administrator to contact them) and ask if they know about the problem. They might have a new, fixed version they can send you. If they don't, ask them when they're going to fix the bug.
TIP: What should you do if your computer crashes? Don't kick the computer; instead, close any open files (if you can) and restart your com- puter. Windows NT has a special program that repairs any damaged files on the hard disk each time you start up. This extra step will make sure you don't have any serious problems that will get worse later.
You might have a collection of DOS programs that you've been using for years, and when you upgraded to Windows NT, they remained on your computer. Surprisingly, Windows NT makes it very easy to deal with old DOS programs, the kind that don't use windows, icons, and--in some cases--even the mouse. If you have one of these programs, the easiest way to set it up is to drag its icon onto the Start button; then, to launch it, click its entry in the Start menu.
Most DOS programs work just fine under Windows NT. But some need a bit of special treatment, and the first place to look when you're having trouble is on the program's Properties page. Right-click the program icon, then choose Properties. You'll see a dialog box with six tabbed sheets, each one filled with complicated options. You can find a few helpful things among all that mumbo-jumbo.
TIP: Windows stores all the technical details about how to run a DOS program in a special type of shortcut called a Program Information File. The extension attached to is DOS name is the same as its abbreviation--PIF. When you use the DOS Properties sheet, you're actually making changes to this PIF shortcut. Don't be confused when you see the original program and this shortcut in the same folder--clicking either one will start your program just fine.
Here's some hard-won advice on whether and when to mess with the shortcuts for your DOS programs:
If you absolutely must fiddle with DOS applications, here's where to look.
General
Strictly informational. There's almost nothing you can change here.
Security
You can check the restrictions on a file here, but these settings probably won' t
effect your DOS programs
Program
If you have trouble starting the program, try setting the Working folder to be the
same as the one in which the program is stored. You can also click in the Shortcut
key box and define a Ctrl- or Alt- key combination that will pop up the program in
a hurry. The windows NT button is strictly for experts.
Font
Scroll through the list of fonts to make the text in the window bigger or smaller
Memory
Most of these are strictly for propellerheads, but if your program is causing trouble,
check the Protected box and try again. Also try setting the EMS and XMS memory options
to Auto.
Screen
Do you want the program to run in a window or a puff up to fill the entire screen?
You make the call. You can also have a DOS toolbar on a window, if you'd like.
Misc.
More technical mumbo-jumbo, except for the Allow Screen Saver check box. Some DOS
programs freeze at the mention of screen savers. If your program is like that uncheck
the Allow screen saver here so that your screen saver won't start while your using
the program.
Fig. 10.6
Working out the kinks in an MS-DOS program. Windows can offer detailed help if you're having problems getting a DOS program to work properly.
To start a program, you don't have to click its icon. If you've found a file that was created by that program, you can double-click that file's icon and launch the program instantly, with the file you clicked already loaded.
How does it work? Well, Windows knows that every file on your PC has a first name and a last name. The first names have to be unique, but the last name (also known as the file extension) works just like your family name to identify a family of files that look and act somewhat alike. When you double-click one of these files, Windows looks up its file type and says, "OK, the DOC extension means this is a document, and I need to use WordPad to open it."
Here are a few important facts about this whole process:
Plain English, please!How does a file type get registered? When you first set up a program, part of the process includes telling Windows which file types it can open and save. For instance, when you install Microsoft Word, the Setup program tells Windows to reserve the .RTF and .DOC extensions for its use. These extensions are "registered"--that is, added to a master list of extensions that Windows knows about. When you double-click a data file to open it, Windows looks in this list to see which program to use.
Why is this important? Because you can double-click a file and it will start up the program that recognizes it. You save time and effort because you don't have to start the program, then go looking for the file, then load it. Windows does it all in one smooth operation.
Q&A: I have two files in the same folder with the same name. How can that be?
They have the same first name, but their last names are different, and because the extensions are hidden, you can't see the differences. One might be called Windows.exe, while the other is Windows.ini. You can tell them apart in one of two ways: by the icon that the files use; or by right-clicking and looking on each file's Properties sheet to see its file type.
Working with file types isn't hard. Here's how to train Windows to open WordPad whenever you double-click a file with the extension .LTR.
Fig. 10.7
Teaching Windows how to associate a file extension with an application.
Fig. 10.8
Does this file go with that program? Here's where to find out.
TIP: Hold down the Shift key and then right-click a file to see the Open With menu instead of the Open menu. This technique can come in very handy if you have two programs (like Microsoft Word and WordPad, for example) that you might want to use at different times to open up .DOC files. Only one of the applications can be associated with .DOC files, but the Open With menu lets you pick either one.
© Copyright, Que Corporation. All rights reserved.