ࡱ; x=H  !"#$%&'()*+,-./0123456789:;<NG?@ABCDEFZIJKLMuOPQRSTUVWXYwj\]^_`abcdefghitlmnopqrsvyz{|}~Root Entry FbCompObjbWordDocumentObjectPool``  !"#$%&'()*+,-./359:;<=>?@ABC FMicrosoft Word 6.0 Document MSWordDocWord.Document.6; ࡱ; L( *w,(ࡱ;  FA&L Express Graphic ALEditor ALEditorࡱ; ࡱ; ܥe3 e528Mbyte drives. EZ-Drive Functional Description ( Fully Automatic Installation Typical installation on a new hard drive involves. . . Running EZ Selecting Fully Automatic Installation and Inserting a bootable DOS diskette when prompted to do so. After these three steps, the machine can be booted from the hard drive. Selecting "Fully Automatic Installation" instructs EZ-Drive to install only drives with no data on them. Existing drives with data on them will not be affected. If you want other than the default installation, you can either select "Specify Custom Installation" from the main menu or use command-line switches (see page  PAGEREF switches \* MERGEFORMAT 14) when executing EZ-Drive. ( Specify Custom Installation Custom installation allows you to specify options of the installation. It is only advised if the Automatic Installation was not successful, or if you want options set other than the defaults. The following options are available: Select Drive Options Setup Newly-Installed Drives Only Overwrite and Setup Hard Drive 0 Overwrite and Setup Hard Drive 1 Menu items 2 through 3 will only appear if existing installed drives are detected in the system. Select Installation Type Custom Drive Type (if needed) If you are unsure that the CMOS has a matching or user-definable type you will want to select this option. EZ-Drive will automatically determine if a custom drive type is needed. Custom Drive Type (forced) If the CMOS does not have a matching or user-definable type you will want to select this option. You would also want to do this to gain plug-and-play capabilities. The drive can be moved to another system, and the drive type in the new systems CMOS can be set to any type as long as it is equal to, or smaller than, the actual size of the drive and the drive will boot and work normally. Regular BIOS Installation EZ-Drive will use the closest type, which more than likely will result in the loss of some drive capacity. Select Partition Option Setup Drive(s) with One Large Partition This will divide the drive up into only 1 partition unless using DOS 3.30. If using DOS 3.30 then partition size is limited to 33MB and so large drives will require many partitions. The best solution in this situation is to upgrade to a later O/S version. Also note that cluster size increases with partition size. Very large cluster sizes may be undesirable to users that primarily store small files on the drive. In this case the drive will need to be setup with multiple partitions. Setup Drive(s) with Multiple Partitions Multiple partitions will be equal in size. Select Format Type Quick DOS Format This does not scan the entire disk for bad sectors but is very quick. This is the type used in Automatic Installation and is recommended for new drives that are defect free. Regular DOS Format This option scans the disk for bad sectors and is recommended for older drives that may contain defects. Select CMOS Option Set CMOS Drive Type(s) Don't Set CMOS Drive Type(s) Some BIOS types cannot be correctly set by EZ-Drive. If this is the case you will need to manually set the CMOS drive types and choose the Dont Set CMOS Drive Type(s) option. ( Change Installed Features The following features can be changed by selecting Change Installed Features. either right after drive installation or at a later time. You must re-boot the system from the hard drive for changes to take effect. Maximum Overdrive Maximum Overdrive enables multiple-sector per interrupt read/write. ( Installation Help This option will allow you to receive online context information during the installation of the hard drive. What EZ-Drive Leaves Behind There are two major goals of EZ-Drive. The first is to quickly and easily install the hard drive(s). The second is to install special features that can be either absolutely necessary (such as the Custom Drive Type and large drive support) or enhanced features (such as multiple read/write). When EZ-Drive installs special features, a special program (boot code) is placed onto hard drive 0 (C:) that is loaded into memory at boot time. When the EZ-Drive program is being loaded a blue and white banner is displayed. This banner displays the features that are enabled for the drive(s). It is important to note that when your installation does not require special features then the EZ-Drive program will not be placed on the drive and the installation will leave the drive in the same state as if it were manually setup without EZ-Drive. After Drive Installation When EZ-Drive completes its installation drive 0 will be bootable and any other drives in the system will be accessible. The only file visible on drive 0 will be command.com. You must now install any other software required for personal use. This typically includes one or more of the following. All DOS files If none of the special features are installed by EZ-Drive, there are no special precautions concerning the installation or use of MS-DOS. If special features are installed then you will need to... Turn on your PC without a floppy in the A: drive (as though you are going to boot from the hard drive). As soon as you see Hold the Ctrl key down to boot from a floppy. . . print on the screen, hold down the Ctrl key, and you will be prompted to insert a floppy. Insert the first disk in the DOS set and press enter to boot the computer. DOS setup will then load and run normally. Note: DRVSPACE compression is not designed to support >528 Million byte drives so it will not successfully work on an area of a drive larger than this limit. It is important to note that this is a DRVSPACE limitation and not EZ-Drive. Windows 3.1, Windows for Workgroups 3.11 The installation of Windows is done as usual, no special provisions need to be made. See the next item for information on 32-bit disk access. OS/2, Window NT, Windows 95 This version of EZ-Drive does not support these operating systems. Please contact Seagate Technical Support. Special Windows 32-bit driver (MH32BIT.EXE) The 32-bit Windows driver that is included with EZ-Drive must be installed in order for Windows 32-bit disk access (FastDisk) to work properly with large drives (>528Mbytes). This driver does not support DMA transfers nor LBA mode. This drive will only work if the EZ-Drive code is loaded. It is not a stand-alone 32-bit driver. Install the driver by running the SETUP program that is on the EZ-Drive diskette from within Windows. Hardware Related Issues Hardware Incompatibilities EZ-Drive is known not to work with the following hardware: Toshiba laptops MCA class machines XT class machines IDE Adapter Issues EZ-Drive is compatible with most IDE adapters. Local Bus adapters are supported when using 16-bit mode. 32-bit transfers and advanced PIO modes are supported through the Local Bus manufacturers own drivers. These drivers are supplied by the Local Bus manufacturer and must be installed after EZ-Drive has completed the drive installation. A retail version of EZ-Drive is available that natively supports all Local Bus features without the need for manufacturers drivers. This version can be purchased directly from Micro House. Incorrectly Installed or Defective Drives The most typical problems encountered when using EZ-Drive will be hardware related. EZ-Drive may error with a message indicating you should check the cabling, jumpers, and connections. This error indicates that EZ-Drive was unable to communicate successfully with the drive, but cannot be more specific. Improper cabling (reversed), improper power supply (insufficient or absent), or a bad drive or card can cause this error, but it is most often caused by improper jumpering. A common scenario is one in which you are installing a second drive, and have not changed the jumpers on the primary drive from Stand-Alone to Master. Other hardware errors involve being unable to write to the boot areas of a drive. This will result in an error message such as. . . UNABLE TO WRITE TO ROOT DIRECTORY AREA or UNABLE TO WRITE TO FAT AREA #1 Unless there is a problem with the cabling, these errors are almost always caused by a bad drive. Incompatibility Between Drive and Machine Some machines will be very finicky about the drives installed into them. Typically, EZ-Drive appears to go through the installation correctly, but the machine will not reboot from the hard drive. Usually the blue and white logo is not displayed. This indicates that the machine is not getting as far as trying to boot from the hard drive. This is not a problem with the EZ-Drive code, since it is not even getting loaded. Often the drive is correctly set-up on the software side of things (this can be confirmed by moving the drive to a more standard machine and having it boot). Usually the problem is not with the drive, but rather a conflict between the drive and the machine. This conflict must be resolved at the hardware level, though not by using EZ-Drive. Machines that seem to cause this problem include smaller brands and Zeniths. Also, BIOS (even AMI) before 1988 can cause a C: drive error message. Pressing F1 will usually allow the drive to boot and be correctly accessible, but you will have to press F1 with each boot. Additionally, on some Compaq computers the BIOS will return an error message upon boot. Pressing F1 will allow the drive to boot normally. Caching Controllers Caching controllers will sometimes interfere with the operation of EZ-Drive while installing the drive. Disable any hardware or software caching. Often disabling the caching is not sufficient, in which case the card should be swapped out for a non-caching interface card. Once set up, the drive can be used successfully on a caching controller. Unrecognized BIOS Drive Tables In some cases EZ-Drive will not recognize the BIOS drive table of a BIOS. In such a case, EZ-Drive will not set the CMOS, but will setup the drive with a Custom Drive Type. You may have to set the CMOS type to drive type one (1) manually through the systems CMOS setup program. This is successful for all tested systems that meet this description, including PS/2s (non-MCA). Software Related Issues If you experience difficulties while using EZ-Drive, the first thing to do is make sure that no other software is loaded besides the essentials of DOS. This can be done by booting from a clean floppy. If EZ-Drive is unable to access a drive that you have installed, it is likely due to a hardware problem. To confirm this, set the drive to type 1 in CMOS. Though usually only 10MB, being set in CMOS will instruct the BIOS to perform drive diagnostics. If you get a hardware error while booting up with the drive set in CMOS, you must resolve the hardware error before attempting to use any software such as EZ-Drive. Operating System (DOS) Versions You must have a diskette containing the DOS boot files handy. A good diskette to use is the first diskette in the DOS set. EZ-Drive is compatible with the following DOS versions: SYMBOL 183 \f "Symbol" \s 12 \h Microsoft MS-DOS Versions 3.0 and later SYMBOL 183 \f "Symbol" \s 12 \h IBM PC-DOS Versions 3.1 and later SYMBOL 183 \f "Symbol" \s 12 \h Digital Research DR-DOS Version 6.0 SYMBOL 183 \f "Symbol" \s 12 \h Novell DOS Version 7.0 SYMBOL 183 \f "Symbol" \s 12 \h Compaq DOS Version 3.31 Do Not Write-Protect! Do not write protect the EZ-Drive floppy diskette! EZ-Drive must write important information to the diskette while installing drives. Unrecognized DOS Boot Records A potential software conflict is that of encountering an unrecognized DOS Boot Record. An unrecognized DBR can be caused by. . . An unrecognized version of DOS A virus An invalid DOS Boot Record (DBR) or Various other unknown (but usually harmless) sources. Upon encountering an unrecognized DBR, EZ-Drive will post a warning message: UNRECOGNIZED DOS BOOT RECORDEZ-Drive has detected an unrecognized DBR on the floppy. EZ-Drive will transfer this DBR, but the drive will not boot if the DBR is not valid. If your drive does not boot, after the error message insert a bootable floppy diskette and press enter. Then SYS your hard drive. A DBR from an unrecognized version of DOS will allow the drive to boot. A virus may or may not allow the drive to boot. An invalid DBR will make the drive unable to boot. Other harmless deviations will usually allow the drive to boot. Any and all of these cases can be repaired by booting from the hard drive, pressing the CTRL key to boot correctly off of a floppy disk, and SYSing the hard drive (and floppies) with DOSs SYS command once the installation is complete. Checksum Failure Upon being launched, EZ-Drive will perform a checksum upon itself to confirm that it has not been altered. This checksum test can fail due to. . . A virus A bad floppy diskette / bad copy Intentional altering of the program That copy of the software is unusable and will need to be replaced. Clean Boot If problems are encountered, always ensure that you boot from a clean floppy, with no autoexec.bat or config.sys. This is particularly true if you are installing a second drive. You should not boot from the first drive. You should instead boot from a clean floppy. Bootable DOS Diskette The EZ-Drive diskette is not bootable. The customer should boot from a clean floppy diskette, then run EZ-Drive. EZ-Drive will ask for a bootable DOS diskette. This should be the same diskette, or at least the same DOS version as the diskette used to boot. Boot Code Error Messages Error messages reported by the EZ-Drive boot code upon execution at boot time are: OS ERROR - It can be remedied by pressing Ctrl when booting to get the EZ-Drive boot code loaded, pressing enter to boot from a floppy, then SYSing the hard drive now that the correct parameters are loaded in memory. PART ERROR - There is a problem with the partition table. The partition table has been damaged. Unless you have more advanced tools for data recovery (such as DrivePro from Micro House), the drive can only be repartitioned and formatted with EZ-Drive or DOS. LOAD ERROR - There was a problem reading data from the drive. This error is rare, and is almost always caused by a hardware problem. CHN ERR - There is a problem chaining to other parts of the EZ-Drive Boot Code. This is caused by damage to the boot code, often by a virus. It can often be repaired by running EZ /MBR. NO ACTIVE - There is no active primary partition. This can be fixed by making the primary partition active with FDISK. EZ-Drive Boot Code This section briefly describes the EZ-Drive boot code and some important items to note. Boot Code EZ-Drive can, and usually will, install special code to support a drive. This code is written to the boot area of the master or C: drive. It loads each time the hard drive boots. Loading of the special boot code is synonymous with the appearance of the blue and white logo at boot-up. Booting From Floppy Diskette IMPORTANT: If the machine is booted directly from floppy, the special code is not loaded and the drive will not be properly accessible. To safely boot from floppy, you must boot from the hard drive far enough to see the gray message instructing you to press the Ctrl key, then press and hold the Ctrl key when instructed to do so. Pressing the Ctrl key too early may result in a keyboard error. Pressing it too late will result in booting from the hard drive. Proper results are achieved when you press the Ctrl key after seeing the initial message and holding it down until the next message appears. When this operation is performed correctly, the machine will load the support Code, then go into a pause mode and display a message instructing you to insert a bootable floppy and press enter. At this point you should insert a bootable floppy (it does not need to be DOS) and press enter. The machine will boot from the floppy with the support Code loaded in memory. Removing EZ-Drive Boot Code Should you wish to remove the EZ-Drive boot code, it is very simple. However, first ensure that you are aware of the implications. First make sure you back up any critical data. Then if your system requires the Custom Drive Type, you will have to repartition and format their drive to use it without the EZ-Drive boot code. If there is a Custom Drive Type installed and you do not need it (because the CMOS is set to the exact same parameters) you can remove the boot code and continue using the drive without having their data affected in any way. Obviously you should back-up your data in case you dont actually have your system setup correctly. If the drive has >528 Millionbyte Support installed and the Micro House Boot Code is no longer desired, the drive must be repartitioned and formatted with DOS/BIOS limits of 16 heads, 1024 cylinders and 63 sectors/track. In this case you will definitely lose all existing data on the drive. The way to remove the EZ-Drive boot code is to boot directly from floppy (not safe floppy boot) and run FDISK /MBR. This will replace it with a fresh copy of the standard DOS boot code (MBR) from FDISK. Re-installing EZ-Drive Boot Code Whether or not a drive was originally installed with the EZ-Drive boot code, one can usually be installed successfully by running EZ /MBR. This will install a fresh copy of the EZ-Drive boot code along with a Custom Drive Type if one was previously installed. If the >528 Million byte Support is damaged (by virus, FDISK /MBR, SETUP /x /z, sector editor, or other means) the drive can usually be restored by running EZ /MBR. EZ-Drive Problem Resolution The following questions are helpful in obtaining information necessary in debugging failed installations. Most installations fail due to incorrect jumper settings on the hard drive(s), incompatible master / slave drives, or an unusual non-standard BIOS. If EZ-Drive is having difficulty accessing the hard drive, set the drive in CMOS to type 1 (10MB). Setting a drive in CMOS will have the machine BIOS instruct the drive to perform its self diagnostics. If there is a hardware problem, the BIOS will usually error out with a HDD controller failure or equivalent message. In order for EZ-Drive to work successfully, the machine needs to be able to boot with the drive set to a type in CMOS other than 0 without getting a hardware error. Did EZ-Drive appear to go through the installation successfully, or did it encounter problems along the way? If there were no problems encountered, the drive is probably set up correctly with software, so start to look for a hardware incompatibility with the machines BIOS. If the problem is getting the drive to boot, what is the exact error message when trying to boot from the hard drive? Is the message in blue and white? (if so, it is from the EZ-Drive Boot Code). Try booting from the hard drive and then run DOS SYS on the hard drive. When you boot from the hard drive, do you see a blue and white logo? If so, the EZ-Drive Code is installed. If not, it is not installed. If you used to see the blue and white logo and now no longer do, the EZ-Drive Code may have been required to use the drive but has been deleted. You may be able to successfully replace the boot code by running EZ /MBR. If you are unable to boot from the hard drive, can you see the drive if you boot from floppy? If so, back up any critical data and then attempt to make the drive bootable with DOS SYS. Windows Message WDCTRL cannot be loaded. . . This message is due to the custom EZ-Drive 32-bit Windows driver not being loaded. EZ-Drive is shipped with a custom Windows 32-bit disk driver that must be installed after installing EZ-Drive. This custom driver adds support to Windows for large drives (over 528Mbytes). To install this driver run SETUP that is on the EZ-Drive diskette from within Windows. Support Quick Reference The following items regarding EZ-Drive are frequently encountered when supporting the product. To Remove EZ-Drive CodeBoot from floppy disk with FDISK on it Type FDISK /MBR and press Enter DOS prompt appears EZ-Drive is now removed from drive(s).WARNING!!! If the drive was setup with a Custom Drive Type or Large Drive Support, you will have to partition and format the drive again. This will be the case when the drive is not supported by the BIOS table of the computer or the drive has more than 1024 cylinders. To Re-establish EZ-Drive CodeBoot from a floppy Type EZ /MBR DOS prompt appears EZ-Drive is now placed on the drive(s).Cannot install OS/2, Warp, or Windows NT  Please contact Seagate Technical Support.Can I use EZ-Drive to install the drive and use a Boot Manager? If the Boot Manager re-writes the MBR, it cannot be done. If instead the Boot Manager uses multiple system files it will work.How do I install DOS?Turn on your PC without a floppy in the A: drive (as though you are going to boot from the hard drive). As soon as you see Hold the Ctrl key down to boot from a floppy. . ., hold down the Ctrl key, and you will be prompted to insert a floppy. Insert the first disk in the DOS set and press enter to boot the computer and run DOS setup.Error message Unable to load WDCTRL when booting WindowsRun SETUP that is on the EZ-Drive diskette from within Windows.Master or Slave not recognizedNot all drives work together, especially drives from different manufacturers. Check and recheck the jumper settings on all drives. Command Line Switches Switches are available to specify the way in which EZ-Drive installs the hard drive(s). These options are also selectable during the installation if you select the Specify Custom Installation option. Switches should only be necessary for non-default installations or when experiencing problems. /? or /h Help. Displays the supported command-line switches and additional helpful information. /# Specify number of partitions to install. As the default, EZ-Drive will use the minimum number of partitions required to install your drive (1 for DOS 4.01 and greater). By using this switch you can specify how many partitions to use, equally sized. Replace the # with an actual number (i.e. /3 would install 3 partitions.) /color Force color mode. This switch is only needed for computers that have a non-standard video display. If your screen is displaying difficult to read shades then use this switch. /custom Install EZ-Drive Custom Drive Type. See page 2 PAGEREF Custom \* MERGEFORMAT Error! Bookmark not defined. for an explanation of this feature. /max Enable Maximum Overdrive. Maximum Overdrive enables multiple-sector read/write per interrupt for all hard drive(s) that support it. /mbr Install Micro House boot code needed to enable any of the special features. This is only needed if you have run FDISK /MBR, done the MSDOS5.0/6.x upgrade without special precautions (refer to page 11+  PAGEREF floppyError! Bookmark not defined.), or by some other means overwritten the Micro House boot code and you need to reinstall it without reformatting the drive. /mono Force monochrome mode. This switch is used when EZ-Drive does not detect your monochrome or page-white monitor. If your screen is hard to read, try using this switch. /nocmos Don't set CMOS drive types. Only needed when you are setting the CMOS drive type manually using your system CMOS setup program before or after EZ-Drive has completed its setup of the drive. This is usually not necessary and is not recommended. /only1024 Truncate cylinders to 1024. Install a 528+ MByte drive using the DOS limitation of <528MBytes. This causes a completely standard installation of the drive, but sacrifices all of the drive capacity beyond 528Mbytes. /over[0/1/both] Forces reformat (overwrite) of existing drive(s). Use "0" for the first physical drive 0, "1" for the second physical drive 1. "Both" overwrites both drives on the primary card., EZ-Drive will have you confirm that you really want to do this before overwriting any existing information. /verify Perform surface scan of entire hard drive. Normally EZ-Drive will only scan the DBR, both FATs, and the root directory for bad sectors. This switch causes the entire hard drive to be scanned for potentially bad areas. This switch should not be required for new IDE drives as you should never have bad sectors on them. PAGE  EZ-Drive Users Guide ( PAGE  PAGE 1 (  :$' { Gz { W @  { W @dW @--`$.   , , ( "    X X N H E D D E I O X X ) l n l ----`$.   , , ( "    X X N H E D D E I O X X ) l n l --'  { W @dW @-%{ {  {-'  { W @dW @-- $s os ! s ---- $s os ! s --'  { W @dW @--$O s *  O ----$O s *  O --'  { W @dW @--`$."%,H#&++&##%&+%+%&#H,%%"%"%,HH,%"----`$_852114414  FPaPaOle PIC LMETA >(( [  w* 8  w* 8ia8-%=-'  w* 8ia8--$ɪeeɪ---- "$ɸɸssɸɸeŜeŜWŜWŜ--'  w* 8ia8--$vv---- "$̄ۄvŹvŹhŹhŹ--'  w* 8ia8--$&&00&----$&&00&--'  w* 8ia8--$#080?0Ƌ.0#0----$#080?0Ƌ.0#0--'  w* 8ia8--$ R0Rɍɍoo__CCƍƍ0R0----$ R0Rɍɍoo__CCƍƍ0R0--'  w* 8ia8--$ =~f~fPfPf==----$ =~f~fPfPf==--'  w* 8ia8--$ k=kZ~Z~A~=k=----$ k=kZ~Z~A~=k=--'  w* 8ia8--l8:0:ɹ-GaȎКȵd'пЙtP- ǵƎЙxЂamG[-L72ƹ0:0zƢ.99e=Й94->UȼfȒpess----@$:0:ɹ-GaȎКȵd'пЙtP- ǵƎЙxЂamG[-L72ƹ0:0--.$zƢ.99e=Й94->UȼfȒpess--'  w* 8ia8--8-G0Gǜǹ- Q { ӧȹȲӢȮ?ȩȝǓDžsӵ]ӪwәǍӇǟrǭ]ǷDǾ) ƾӼƱӔƛtƀ[`G<:20G0Ư-AOY`dǯgg----^$-G0Gǜǹ- Q { ӧȹȲӢȮ?ȩȝǓDžsӵ]ӪwәǍӇǟrǭ]ǷDǾ) ƾӼƱӔƛtƀ[`G<:20G0--($Ư-AOY`dǯgg--'  w* 8ia8--$ ڕڕڕ"ە"ۉډڕ----$ ڕڕڕ"ە"ۉډڕ--'  w* 8ia8--*$ƪۉœۉooNۉ9ۉ9HHۻEۜHۜizƛۜśۜśۻśƪ----*$ƪۉœۉooNۉ9ۉ9HHۻEۜHۜizƛۜśۜśۻśƪ--'\\\%s\%sUpdaࡱ; CompObj RObjInfoOle10Native  Ole10ItemName0 U-;&T, WHITE, BLACK, MAGENTA, BLUE, CYAN, GREEN, YELLOW,RED,Ash<, CharcoalP, CinderP, Dolphin, Dove,Fieldstone2, Flannel, FlintP, Frost, Mortar, MouseV, Onyx\, Oyster , Sage, SmokeF, Whale<\d\dSS(SSO(SLj%/7EZ-Drive Bar Onlyf:ʪeЮ"= b=WGW=ծ/#$ɪeeɪ cj%/7f:ʪeЮ/%$vv c6(n1vRԯ/%$&&00& c&0&0wԙ/%$#080?0Ƌ.0#0 c#0T#0֙/%$ R0Rɍɍoo__CCƍƍ0R0 cR0ƍȑR0ƍpٙ/%$ =~f~fPfPf== c=.%=Ǧ/%$ k=kZ~Z~A~=k= cZ=ZȔ%Z=ʦ/% :0:0ϙ$ :0:ɹZdЙZ0ƹ0:0 c:0:0ϙ/%$ z==Й=.sess c=s ɤ=sϛ/%+ G0#VG0ҙ$G0GǜFҎȍӕ]ӪǪ~GcW00G0 cG0#VG0ҙ/%$ Ư^gǯgg cgq [g/%+$ ڕڕڕ"ە"ۉډڕ cډ"wډ"/%$ƪۉœۉooNۉ9ۉ9HHۻH۷EۨEۜHۜizƛۜśۜśۨś۷śۻśƪ c9ۉŪw9ۉŪr/%+ࡱ; -14998 -15067 -9169 -13769ࡱ; ࡱ; Lh3ࡱ;  FA&L Express Graphic ALEditor ALEditorࡱ; ࡱ; -15370 -15780 -14396 -14629ࡱ; ."%,H#&++&##%&+%+%&#H,%%"%"%,HH,%"--'  { W @dW @--`$."$*5F+0!200<*G!P[__Fc+i$q"q>>"G$M+QFQOI<3(F5*$"----`$."$*5F+0!200<*G!P[__Fc+i$q"q>>"G$M+QFQOI<3(F5*$"--'  { W @dW @--v$9"%)>Yw #! {11'#%+02,q_I;0(%+:Qmm----v$9"%)>Yw #! {11'#%+02,q_I;0(%+:Qmm--'  { W @dW @--b$/#%*5E$&+i+tmg_ UH)$ 6CMSUYYmUmSMC61*:*I+U1^?aXgXg----b$/#%*5E$&+i+tmg_ UH)$ 6CMSUYYmUmSMC61*:*I+U1^?aXgXg--'  { W @dW @--0$\ \ f l p p l f c \ \ \ ----0$\ \ f l p p l f c \ \ \ --'  { W @dW @--f$1A < "   ] 1    % 2 8 = : 6 / * %   , f   $ 3 A ----f$1A < "   ] 1    % 2 8 = : 6 / * %   , f   $ 3 A --'  { W @dW @--$ p p k k x x s s p ----$ p p k k x x s s p --'  { W @dW @-- $y y } { { y ---- $y y } { { y --'  { W @dW @--z$;!   ; Z v  ! 3 C P \ dv kZ o; p o j c Z O A 2 ! ! . : C J S V SK Kz D ; / !   z K    ! ! ----F$!!   ; Z v  ! 3 C P \ dv kZ o; p o j c Z O A 2 ! --6$! . : C J S V SK Kz D ; / !   z K    ! --'  { W @dW @--p$6` ` ] W T K K | y x x: : 6 / K K W ] ` x, x |    $ + x, ` ----P$&` ` ] W T K K | y x x: : 6 / K K W ] ` --"$x, x |    $ + x, --'  { W @dW @--x$:{j[!N-C=:Q3h-.28ALY&i/{2/&hQ=-!{{&)0<Kr {#m aXQIGJrRKY<b0n){&{----D$ {j[!N-C=:Q3h-.28ALY&i/{2/&hQ=-!{--6${&)0<Kr {#m aXQIGJrRKY<b0n){&--'M,,,,,Motࡱ; _852114413P6' tjvP6'  FPaPaPPOle t^&G&W&G&W&G& W v&&w&71PPIC, 7 uZ9wr9s dž<  Wv v2LrMETA_MM]M&UR =8RT[h>Z  3 *  3 * *--`$.ęġ(Ĥ1į56651( ` `QHCBBÏ Œ   ĸŪ ţšřęÚĮęıĘĭSęę----`$.ęġ(Ĥ1į56651( ` `QHCBBÏ Œ   ĸŪ ţšřęÚĮęıĘĭSęę--'  3 * *-%GŵG-'  3 * *-- $|0| `|---- $|0| `|--'  3 * *--$DonƐ Do----$DonƐ Do--'  3 * *--n$5ĆĎđ%Ě*Ĩ+Ļ+ğ*IJ%``UNJIJIğI4Ɵ4ƟğƞIJƙƒƇƇIJƿğƿĻĨĚđĎĆŇĆŇĎŒđřĚŞĨşĻşIIĻJĨNĚUđ`Ď`ĆĆ----n$5ĆĎđ%Ě*Ĩ+Ļ+ğ*IJ%``UNJIJIğI4Ɵ4ƟğƞIJƙƒƇƇIJƿğƿĻĨĚđĎĆŇĆŇĎŒđřĚŞĨşĻşIIĻJĨNĚUđ`Ď`ĆĆ--'  3 * *--n$5ņũŎŵտ؝źUŎťŸ ,9CƷKƤQƍUUUƺVƦ[ƙcƑnƎnƆ/Ɔ/Ǝ:ƑAƙFƦGƺGPE|=Ơ6Ʈ-ƹ"źűŤŁUźťŘŐŎņũņ----n$5ņũŎŵտ؝źUŎťŸ ,9CƷKƤQƍUUUƺVƦ[ƙcƑnƎnƆ/Ɔ/Ǝ:ƑAƙFƦGƺGPE|=Ơ6Ʈ-ƹ"źűŤŁUźťŘŐŎņũņ--'  3 * *--$@ƀƀƍƐƈŲƂŞƈŏƘńƱŀńŏƞ'ư;[py|ƍƥƸƹƮƤƓƭƇƐnymƀƆƈƏƗƠƪƹơ{hW9"ƦŜřŘƾŚƬŠƞũƔŴƑſƓƘƠƫƀ----$@ƀƀƍƐƈŲƂŞƈŏƘńƱŀńŏƞ'ư;[py|ƍƥƸƹƮƤƓƭƇƐnymƀƆƈƏƗƠƪƹơ{hW9"ƦŜřŘƾŚƬŠƞũƔŴƑſƓƘƠƫƀ--'  3 * *--h$2džǎǐǘǥǸǣǶƞƪǀƥǀƑǬƅǺǾuOHA<Ǿ8Ǫ8/`/p0{6ƂEƆ`Ƌ`Ƌņł{p`88Ǡ:ǚ>ǗeǗwǙņǠŋǧŐǰŔŚŚdždž----h$2džǎǐǘǥǸǣǶƞƪǀƥǀƑǬƅǺǾuOHA<Ǿ8Ǫ8/`/p0{6ƂEƆ`Ƌ`Ƌņł{p`88Ǡ:ǚ>ǗeǗwǙņǠŋǧŐǰŔŚŚdždž--'  3 * *--6$ž&.2332.& m maYTSSTYammžž----6$ž&.2332.& m maYTSSTYammžž--'  3 * *--j$32- ķĭğŜěfĞ.Īó((.(+ƹ&ƹżŹż÷åÖÉÀz:x]zŃŦĈēĢĴ  2----j$32- ķĭğŜěfĞ.Īó((.(+ƹ&ƹżŹż÷åÖÉÀz:x]zŃŦĈēĢĴ  2--'  3 * *--z8!Dǒ/ǕǠ ǰ"HqƗƹ - D[ nĎęǹġǗĥqħHĥ"Ġ×Ë}ǰlǠYǕDǒDǥUǩddzoxÄ ćHĄDžypeVD2#DžH %dz3ǩDǥ----F$!Dǒ/ǕǠ ǰ"HqƗƹ - D[ nĎęǹġǗĥqħHĥ"Ġ×Ë}ǰlǠYǕDǒ--6$DǥUǩddzoxÄ ćHĄDžypeVD2#DžH %dz3ǩDǥ--'  3 * *--r8&WWVSK== ő őŃ{wvvqĈq  ħmĻdQ7ùëÐƾ=ƾ=KSWv_vw{ÅËàðúþļ.ķ?İLĦUď]v_----P$&WWVSK== ő őŃ{wvvqĈq  ħmĻdQ7ùëÐƾ=ƾ=KSW--$$v_vw{ÅËàðúþļ.ķ?İLĦUď]v_--'  3 * *--z8!?Ł+ńō Ŝį%JlċĦż)?UhxżƆŦƐŋƘlƜJƞ%ƜƗŏńůvŜfōSń?Ł?őOŔ]Şhŭq|%|\rőjŧ_ŹP?.Źŧ ő\% ŭ!Ş/Ŕ?ő----F$!?Ł+ńō Ŝį%JlċĦż)?UhxżƆŦƐŋƘlƜJƞ%ƜƗŏńůvŜfōSń?Ł--6$?őOŔ]Şhŭq|%|\rőjŧ_ŹP?.Źŧ ő\% ŭ!Ş/Ŕ?ő--'  3 * *--$ ǟâǟâǯäǯäǟèǟèǝÞǝÞǟ----$ ǟâǟâǯäǯäǟèǟèǝÞǝÞǟ--'  3 * *--*$ǯùǝöǝòǬòǬîǝìǝìǯîǯîǤíǟîǟòǯóǯ÷ǟ÷ǟ÷Ǥ÷ǯùǯ----*$ǯùǝöǝòǬòǬîǝìǝìǯîǯîǤíǟîǟòǯóǯ÷ǟ÷ǟ÷Ǥ÷ǯùǯ--' tBF&t$&t"&t&t&t &t&ࡱ; CompObj 417F07Fg-,14,14g-&g-17Fh7F7F 24 244RObjInfo64GFOle10NativeGF4GFGFdGFkOle10ItemNameGFGFGFGFGF7  U-;&T, WHITE, BLACK, MAGENTA, BLUE, CYAN, GREEN, YELLOW,RED,Ash<, CharcoalP, CinderP, Dolphin, Dove,Fieldstone2, Flannel, FlintP, Frost, Mortar, MouseV, Onyx\, Oyster , Sage, SmokeF, Whale<\dd\d\d\ dS (S (S&(S(. hairlineSSdS/(S`(S(S(#\Micro House Gray Scale!Ǔ0`¹Ş$)ęġ1ġ6ı6661 ` `GBBBÏ Œ   īššřęÚĮęIJĘıĘĭSęę cĒU͋ę Q/%"GŵG b8V!)ψ)GŵGG/#$|0| `| c,\ƀzҖ0`| /%$DonƐ Do cjsHoon -Ƽ/%$-ĆĎ$Ď+ğ+Ļ+ğ+ĺ$``OIĺIğI4Ɵ4ƟğƟĺƘƇƇƿĺƿğƿĻſğĎĎĆŇĆŇĎŘĎşğşĻşIIĻIğOĎ`Ď`ĆĆ cĆC7Ćt-/%$#ņũŎŻŎřźUŪ >UƨUUUƺUƜ\ƎnƎnƆ/Ɔ/Ǝ@ƎGƜGƺGPGƎ<ŖUźřŎŎņũņ cņnOH0өņn 1/%$1ƀƀƌƒƐƎƂŲƂŖƂŀƢŀŀ Ɨ ư;NaƍƱƹƙƈƝnymƀƆƆƉƏƛơƹƲ{E&ưŘŘƾŘƤťƑŴƑƑƺƀ cyƀbѺϦ0yƀ./%$,džǎǎǚǸǣƞƪǀƥǀƙǡƌǾuOH=8Ǿ8Ǫ8/`/x/ƃ1Ɔ`Ƌ`ƋņŃx`88Ǡ8Ǜ;Ǘ>ǗeǗ~ǗœǜŔŚŚdždž cdžŪndžŪW-/%$ž-3333- m mZSSSSZmmžž cžm ?˶Ύžm Cd/%$ 2-ıěŰěfěĪ"((.(+ƹ&ƹ ŽŹŹåŹxx]xĞ2 cxŹ22˭ТxŹ2f/% ƋîmdԠƒçDR$ Dǒ ǒHƹDńŧǹħHħ~ǒDǒ cƋîmdԠƒçDR/%$ DǥvǥÇÇHćǗyDǗHǥDǥ cƞÎiǥÇEQ/%+ =ƾ ?˾Ҏ=ƾ d$WWWU== ő őyvvvqĈq  ħmhDôƾÐƾ=ƾ=UWW c=ƾ ?˾Ҏ=ƾ d/%$ v_vv}ÅËéþþľ[Ė_v_ cvþ_vþ_/%+ āŞQͽ50āŞ@.$ ?ŁŁ%ċ?}ƞŋƞ%ƞxŁ?Ł cāŞQͽ50āŞ@./%$ ?őnő%lr? l%ő?ő cđđ?-/%+$ ǟâǟâǯäǯäǟèǟèǝÞǝÞǟ cǝèǯMg˞ǝèǯǦ/%$ǯùǝöǝòǬòǬîǝìǝìǯîǯîǤîǤíǡíǟîǟòǯóǯ÷ǟ÷ǟ÷ǡ÷Ǥ÷Ǥ÷ǯùǯ cǝùǯqʓˬǝùǯǦ/%+ࡱ; SummaryInformation417F07F(37Fh7F-7FExSt8 Oh+'0 D h   @d C:\WINWORD\TEMPLATE\NORMAL.DOTEZ-Drive Product Description Lael Pierce Lael Pierce@[@q^@ HH@ Microsoft Word 6.010O~T !:;TVacǼǯ按U]]]c uD`kV]uD]cV]c]cU]c U]bc U]bc e uDU]bc e UV]bc uD;2K uD;2vKU]UV]UV]U]c uD;2K uD;2vKuD]6cwy8 N P q s 8 : a    !"?'<.,/0Bٹ J Uc J UcVc J Uc uDcV]ccUc J Uc]c]cU]c]cU]cU]]I2^l1 !!V"s""#$$$$1%3%C%E%X%Z%m%%''m++;0O011E3G3_3`333.4645555m6u6666666774757T7U7z7{7777777788%888@8888-9/9N9P9X9Z9~99='==== uDcV]c]ccU]c]cU]cY====U>`>m??@@@@AABBXC_CDDDDDDD E)FFFJ2J3M7MNN}P~PPPWWfYgYYYYYzZ[[[\.\Z\\]2]]^^_!______```IaJavaaabbbbMcNc_cgc{cccuDc ] c ] V]]cU]U]c]U]c]c]cTccccccc dsdtdddDeEeUeVereseee ff'f/fffff7g?gggghhhIiQiiiiiiijjkkkk k k k#k$k*k+k1k2k3k4k5k6k7k8k:k;kT>U>ddh 3& ' ( )  l* 3& ' ( ) `hhU>`>l?m??@@@@ABXCDDDDDDDDDDD E(FFFJ2JyKzKMNN}PPPQhdh<<& ( dh$QQSSTTUUWWWWWeYfYYYYYZ?ZRZ" h 4h$ hP 4hPhx& ( hdhRZyZzZ[[[[[[\\-\.\/\Y\Z\ZZV& h 4hN ' hP 4hN Plt" Pl4t" $ hP 4hZ\\\]]2]]^^^__!_o_____``wsnll& ( ! P 4h! P 4hl4t" $ hP 4hP``IaJavabbbbMcNc{ccc dsdtddeeffffgghhhhiiijjk k$%$$x$%$$`%pppphpphp$ k k k!k"k#k7k8k9k:k;k)C~MgV\eQRZZ\` k