~TABLE 17--COPYING FILES TO HARD DRIVEEnd TimeH: M: S Activity2:35:10what should hard drive be named?--2:44:502:45:502:51:452:52:502:54:452:58:402:59:203:OO:OO24:50copy files to hard drive from floppy disk-ansi.sys. whatdoes backup do? chkdsk, diskcomp, diskcopy, edlin. Paul:I don't like this backspace, wonder what esc.com is. what isfind? format copied. what is freq? can't find explanationfor freq-skip it. graftabl, graphics, join. what is all <strong>the</strong> keystuff? only keyb is documented. what is setup? checkingdocumentation. what's share, subst, try tree, what's vdisk,wtdatim? make dir for <strong>the</strong> files copiedmake directory \util for o<strong>the</strong>r files.fix prompt-didn't install prompt command, documentationdoesn't lead one through it very well. make an autoexecfile-edlin doesn't work, copy autoexec from disk in a:,rename and try to edlin again. once again bad command orfile name. lost in directory, realize that directory doesn'thave edIin. change directory with edlin. edlin autoexec filecheck if prompt works. turn <strong>of</strong>f machine, <strong>the</strong>n turn onmachine. it works! (no date & time request)create basic directory and copy basic files.copy remaining utility files to \util (assign, attrib, fdisk, find,join, key", label, more, remove restore, select, setup, share,sort, subst, tree, wtdatim).copy A:gwbasic to hard driveWe now have a system!Total
RECOMMENDATIONSIt is clear from <strong>the</strong> previous section that participants had numerous problems withsetting up <strong>the</strong> <strong>PC</strong>-<strong>8.</strong> The evidence takes <strong>the</strong> form <strong>of</strong> both comments from typical users andan etmpiric analysis <strong>of</strong> setup task times. These problems have arisen because <strong>the</strong> originalpro&uct concept dicl not call for customer setup. When human factors/ergonornicconsiderations are not given priority early in design, it is unlikely <strong>the</strong> resulting product willbe easy to use (or in this case, easy to set up).It may seem to some that <strong>the</strong> setup problems reported here can be eliminated byimproving <strong>the</strong> documentation. While that will certainly help, <strong>the</strong> ultimate solution mustincluide modification <strong>of</strong> <strong>the</strong> packaging, hardware, and s<strong>of</strong>tware as well. Specifically, keysuggested changes include:@making <strong>the</strong> hardware self-documenting,consolidating most <strong>of</strong> <strong>the</strong> setup information into one manual,eliminating mixed language documentation,making much greater use <strong>of</strong> illustrations,adding "open me first," "this side up," and unpacking instructions, and a list <strong>of</strong> 'contents on <strong>the</strong> outside <strong>of</strong> each shipping box,reshaping t,he foam in <strong>the</strong> cabinet shipping box to facilitate unpacking it, and0 providing batch files to handle most <strong>of</strong> <strong>the</strong> system configuration.All <strong>of</strong> <strong>the</strong>se suggestions are expanded upon in <strong>the</strong> section that follows.1. As a general principle, hardware should be self-documenting. To achieve this,every part should be labeled with a name, and if possible a number. The name should beengra.ved in <strong>the</strong> mold for plastic and cast metal parts, and printed on circuit boards. Thename should face <strong>the</strong> customer when <strong>the</strong> part is removed from its package and be visiblewhen it is installed. So, for example, with circuit boards, <strong>the</strong> name should be on <strong>the</strong> top <strong>of</strong><strong>the</strong> card and also, so one can identify it without opening <strong>the</strong> cabinet, on <strong>the</strong> outside <strong>of</strong> <strong>the</strong>foot. Because <strong>NCR</strong>'s market is multilingual, it will be a challenge to make <strong>the</strong> labelslegible given <strong>the</strong> limited space available.With <strong>the</strong> present design <strong>of</strong> <strong>the</strong> <strong>PC</strong>-8, <strong>the</strong> only source <strong>of</strong> information about setting itup is <strong>the</strong> written documentation, Ideally, it should be obvious from <strong>the</strong> hardware how toset it up and <strong>the</strong> documentation should be a secondary source. Fur<strong>the</strong>rmore, <strong>the</strong> currentsetup procedure assu:mes that people go through <strong>the</strong> documentation step-by-step, never