TITLE: Manual Installation of Novell DOS 7 DOCUMENT ID: TID21031 DOCUMENT REVISION: 1 DATE: 23MAY94 ALERT STATUS: Yellow README FOR: NA NOVELL PRODUCT and VERSION: Novell DOS 7 ABSTRACT: NA --------------------------------------------------------------------- DISCLAIMER: THE ORIGIN OF THIS INFORMATION MAY BE INTERNAL OR EXTERNAL TO NOVELL. NOVELL MAKES EVERY EFFORT WITHIN ITS MEANS TO VERIFY THIS INFORMATION. HOWEVER, THE INFORMATION PROVIDED IN THIS DOCUMENT IS FOR YOUR INFORMATION ONLY. NOVELL MAKES NO EXPLICIT OR IMPLIED CLAIMS TO THE VALIDITY OF THIS INFORMATION. --------------------------------------------------------------------- ISSUE: Some rare situations have made it impossible to run the automated install procedure for Novell DOS 7. Until this and any other future install issues get resolved, it may be necessary to "manually" install Novell DOS 7. Note that this procedure does not fully install the Windows utilities for Novell DOS 7, nor does it guarantee the ability to make your computer a peer-to-peer server. Please note concerning "lockup" that sometimes an 8088 or other slow machine may appear to lock during the installation, when in reality it is processing information. If your machine is slow, do not assume your machine has locked unless you see no change or activity for over 15 minutes. MAKE THE HARD DRIVE BOOTABLE If your install disks are the size of your machine's A: drive, boot from the Novell DOS 7 #1 disk. When you see the message "Starting DOS...", immediately press the F5 key. If you press it soon enough, the machine will boot to the DOS prompt rather than into the INSTALL program. (Note that you can actually press the F5 key before "Starting DOS..." appears, as long as the machine's power-on self-test is done; this is usually indicated by a beep two or three seconds before "Starting DOS..." appears.) From the A:\> prompt, type SYS C: and press enter. At this point, the C: drive will be able to boot Novell DOS 7.0. If your install disks are not the size of your machines A: drive and your hard drive currently boots DR DOS 6.0, you should boot your hard drive as normal, place the Novell DOS #1 disk in the B: drive, and from the B:\> prompt type SYS C: and press . If your install disks are not the size of your A: drive and your hard drive currently boots a version of DOS other than DR DOS 6.0, do the following: 1. Boot your system from its hard drive, as you normally would, and place the Novell DOS 7 #1 disk in the B: drive. 2. Give the command INSTALL and press enter. 3. After you reach the screen with "Continue Installation" and "Generate Bootable Floppy Disk" options, select "Generate Bootable Floppy Disk" and press . This will require you to place a floppy disk in your A: drive. This disk will be formatted, so make sure it does not contain any files you need. 4. After INSTALL is done creating the bootable floppy, exit INSTALL and reboot your machine with both floppy disks in their drives. 5. After you reach the A> prompt, switch to the B> drive by typing B: and pressing . 6. Then type SYS C: and press . At this point, the C: drive will be able to boot Novell DOS 7.0. If your machine locks up before you reach the option to generate a bootable floppy disk, you will need to generate the disk on another machine which has the same size A: drive as the problem machine. Then follow the instructions in the previous paragraph, beginning with "...reboot your machine, with both floppy disks in their drives." REBOOT YOUR MACHINE FROM THE HARD DRIVE 1. Take each floppy disk you have been using out of each drive and reboot the machine. 2. When you see "STARTING DOS..." message, press the F5 key. This will cause Novell DOS 7 to skip your CONFIG.SYS and AUTOEXEC.BAT files. This is desirable because your existing files may try to load drivers that only function under other versions of DOS. INSTALL FILES ALTERNATIVE 1: BACKUP/RESTORE METHOD If you intend to use the PERSONAL NetWare portion of Novell DOS 7, you may want to use this method of installing the files, especially if you intend to make the machine a server. This method is not necessarily fast; however, it is usually easier than a complete manual installation. It will allow you to fully configure the network, which may not be possible otherwise. If INSTALL is failing, it is possible that SETUP will fail also. SETUP is required to configure a server and so the following may be necessary: - If you have another machine available to you that will let you run the Novell DOS 7 INSTALL, you may want to install Novell DOS 7 to it, backup the NWDOS, NWCLIENT, and NWCNTL (hidden) subdirectories (and all their subdirectories), and restore them to the machine on which you cannot run INSTALL. - You will want to have any network options configured as completely as possible before backing up the information, so be sure to run SETUP after installation to configure the network. - If you do not have a backup and restore method in place, you can use the Novell DOS backup and restore commands, located on Utilities disk #2 (3.5" HD set) or disk #3 (5.25" HD set). Note that you should not attempt to run both of these machines as SERVERS (sharing the machine's resources) if they were configured identically. Having more than one SERVER with the same name can cause conflicts. If you intend to use both machines as SERVERS on the network, do the following: 1. After you have backed up the machine which successfully installed, delete the contents of its NWCLIENT and NWCNTL (hidden) directories. 2. Then run SETUP. It will allow you to reinstall the network files to this machine. Use a different USER NAME than you did originally, so it will create a different SERVER NAME. After following the above steps, installation should be complete. Depending on the original problem with INSTALL, you may not be able to run SETUP to reconfigure things. Most of the settings controlled by SETUP can be performed manually. However, some settings cannot be performed manually, such as, enable SERVER or enable or enabling Boot Security. If you do not have another machine available, continue with the next installation alternative. Note, however, the best way to get complete network functionality is to use the backup and restore method listed above. ALTERNATIVE 2: COPY/UNPACK METHOD 1. After booting Novell DOS 7 from your hard drive, create a directory called NWDOS by typing MD C:\NWDOS and pressing . 2. Change into that subdirectory by typing CD C:\NWDOS and pressing . 3. Put the first Novell DOS disk in your floppy disk drive and type the command XCOPY A:\*.* C:\NWDOS /HRV and press . Repeat this command for EACH of the disks in the install set, except for the PERSONAL NetWare Tutorial disk. 4. Make a new attempt to install. At this point, you may actually be able to run the automated INSTALL, even though it failed in the past. Although it is not likely to work, it is worth trying because it could save you much time. Type the command C:\NWDOS\INSTALL and press . If this fails, continue with the following steps: 5. Manually unpack the files. a. From inside the NWDOS directory, type the command PNUNPACK *.?_ /o and press . This should unpack one file, called DEFAULT.FB. b. Then type the command PNUNPACK *.??_ /o and press . This should unpack a large number of files and may take 20 minutes to over an hour, depending on the speed of your machine. c. Rename the INSTALL program to SETUP, by typing the command REN C:\NWDOS\INSTALL.EXE C:\NWDOS\SETUP.EXE and pressing . 6. At this time, you may be able to use SETUP to copy the network files to their correct locations. To do this, type SETUP and press enter. 7. If you reach the main menu, select NETWORKING and press . You will be told the network files are not installed. SETUP will offer to install them for you. Accept this; however, when it lists the source path for the network files as A:\, change it to C:\NWDOS. If this attempt fails, continue with the following steps: Many of the files you have unpacked can remain in the Novell DOS directory (C:\NWDOS). However, some files belong in the root directory, and the network files belong in different directories. At the end of this document is a list of where a normal Novell DOS install puts its files. Note that if you were not able to run the automated INSTALL or SETUP earlier, you most likely will not be able to make the machine a server. 1. You may want to use the commands COPY, XCOPY, or MOVE to place these files in their proper locations. This step will be very time consuming, but can be sped up some if you make use of the HISTORY feature in the CONFIG.SYS and carefully use wildcards to specify filenames. Use the commands DOSBOOK HISTORY or DOSBOOK WILDCARDS from the NWDOS directory for more information on these features. You can get help on COPY, XCOPY, and MOVE by typing the command and then a "/?" (without the quotes). 2. After you have moved the files, you may want to delete the original packed files from your NWDOS directory. This can be done by giving the following commands from inside the NWDOS directory: NOTE: Be careful. If the commands are entered wrong, you could delete files that are needed. XDEL *.?_ /r XDEL *.??_ /r Please note that many network files don't get installed automatically unless they are specifically asked for, that is, network card drivers. Therefore, some files you find in your NWDOS directory may not be on this list. If you have a file in the NWDOS directory that is not on this list, it most likely belongs in the NWCLIENT directory. c:\autoexec.bat c:\command.com c:\config.sys c:\ibmbio.com c:\ibmdos.com c:\nwdos.386 c:\security.bin c:\nwclient\auto.vlm c:\nwclient\bind.vlm c:\nwclient\conn.vlm c:\nwclient\drivers.dos c:\nwclient\fio.vlm c:\nwclient\general.vlm c:\nwclient\hostmib.mib c:\nwclient\hrmib.exe c:\nwclient\hrmib.ini c:\nwclient\ibm_run.ovl c:\nwclient\ibmfddi.bin c:\nwclient\ins.oem c:\nwclient\ipxncp.vlm c:\nwclient\ipxodi.com c:\nwclient\lsl.com c:\nwclient\mdgdos02.bin c:\nwclient\mib2if.vlm c:\nwclient\mib2prot.vlm c:\nwclient\nds.vlm c:\nwclient\ne1000.com c:\nwclient\ne1000.ins c:\nwclient\ne1500t.com c:\nwclient\ne1500t.ins c:\nwclient\ne2.com c:\nwclient\ne2.ins c:\nwclient\ne2000.com c:\nwclient\ne2000.ins c:\nwclient\ne2100.com c:\nwclient\ne2100.ins c:\nwclient\ne2_32.com c:\nwclient\ne2_32.ins c:\nwclient\ne3200.com c:\nwclient\ne3200.ins c:\nwclient\net.exe c:\nwclient\neta.hlp c:\nwclient\neta.ovl c:\nwclient\netbios.exe c:\nwclient\netu.hlp c:\nwclient\netu.ovl c:\nwclient\netu2.ovl c:\nwclient\netw.exe c:\nwclient\netx.vlm c:\nwclient\nlmigrat.exe c:\nwclient\nmr.vlm c:\nwclient\ntr2000.com c:\nwclient\ntr2000.ins c:\nwclient\null.com c:\nwclient\null.ins c:\nwclient\nwp.vlm c:\nwclient\nwrcon.pif c:\nwclient\odinsup.com c:\nwclient\pnw.mib c:\nwclient\pnw.vlm c:\nwclient\pnwdiag.dat c:\nwclient\pnwdiag.exe c:\nwclient\pnwdiag.hlp c:\nwclient\pnwdiags.exe c:\nwclient\pnwdiags.hep c:\nwclient\pnwmib.vlm c:\nwclient\pnwtrap.mib c:\nwclient\pnwtrap.vlm c:\nwclient\print.vlm c:\nwclient\redir.vlm c:\nwclient\rsa.vlm c:\nwclient\security.vlm c:\nwclient\server.exe c:\nwclient\stpipx.com c:\nwclient\stpudp.com c:\nwclient\taskid.com c:\nwclient\tbmi2.com c:\nwclient\textutil.idx c:\nwclient\tran.vlm c:\nwclient\upatch.exe c:\nwclient\version.exe c:\nwclient\vlm.exe c:\nwclient\wsasn1.vlm c:\nwclient\wsreg.vlm c:\nwclient\wssnmp.vlm c:\nwclient\wstrap.vlm c:\nwclient\nls\1252_uni.001 c:\nwclient\nls\1252_uni.002 c:\nwclient\nls\1252_uni.003 c:\nwclient\nls\1252_uni.031 c:\nwclient\nls\1252_uni.032 c:\nwclient\nls\1252_uni.033 c:\nwclient\nls\1252_uni.034 c:\nwclient\nls\1252_uni.039 c:\nwclient\nls\1252_uni.041 c:\nwclient\nls\1252_uni.044 c:\nwclient\nls\1252_uni.045 c:\nwclient\nls\1252_uni.046 c:\nwclient\nls\1252_uni.047 c:\nwclient\nls\1252_uni.049 c:\nwclient\nls\1252_uni.061 c:\nwclient\nls\1252_uni.081 c:\nwclient\nls\1252_uni.351 c:\nwclient\nls\1252_uni.358 c:\nwclient\nls\437_uni.001 c:\nwclient\nls\437_uni.003 c:\nwclient\nls\437_uni.031 c:\nwclient\nls\437_uni.032 c:\nwclient\nls\437_uni.033 c:\nwclient\nls\437_uni.034 c:\nwclient\nls\437_uni.039 c:\nwclient\nls\437_uni.041 c:\nwclient\nls\437_uni.044 c:\nwclient\nls\437_uni.046 c:\nwclient\nls\437_uni.049 c:\nwclient\nls\437_uni.061 c:\nwclient\nls\437_uni.358 c:\nwclient\nls\uni_1252.001 c:\nwclient\nls\uni_1252.002 c:\nwclient\nls\uni_1252.003 c:\nwclient\nls\uni_1252.031 c:\nwclient\nls\uni_1252.032 c:\nwclient\nls\uni_1252.033 c:\nwclient\nls\uni_1252.034 c:\nwclient\nls\uni_1252.039 c:\nwclient\nls\uni_1252.041 c:\nwclient\nls\uni_1252.044 c:\nwclient\nls\uni_1252.045 c:\nwclient\nls\uni_1252.046 c:\nwclient\nls\uni_1252.047 c:\nwclient\nls\uni_1252.049 c:\nwclient\nls\uni_1252.061 c:\nwclient\nls\uni_1252.081 c:\nwclient\nls\uni_1252.351 c:\nwclient\nls\uni_1252.358 c:\nwclient\nls\uni_437.001 c:\nwclient\nls\uni_437.003 c:\nwclient\nls\uni_437.031 c:\nwclient\nls\uni_437.032 c:\nwclient\nls\uni_437.033 c:\nwclient\nls\uni_437.034 c:\nwclient\nls\uni_437.039 c:\nwclient\nls\uni_437.041 c:\nwclient\nls\uni_437.044 c:\nwclient\nls\uni_437.046 c:\nwclient\nls\uni_437.049 c:\nwclient\nls\uni_437.061 c:\nwclient\nls\uni_437.358 c:\nwclient\nls\uni_col.001 c:\nwclient\nls\uni_col.002 c:\nwclient\nls\uni_col.003 c:\nwclient\nls\uni_col.031 c:\nwclient\nls\uni_col.032 c:\nwclient\nls\uni_col.033 c:\nwclient\nls\uni_col.034 c:\nwclient\nls\uni_col.039 c:\nwclient\nls\uni_col.041 c:\nwclient\nls\uni_col.044 c:\nwclient\nls\uni_col.045 c:\nwclient\nls\uni_col.046 c:\nwclient\nls\uni_col.047 c:\nwclient\nls\uni_col.049 c:\nwclient\nls\uni_col.061 c:\nwclient\nls\uni_col.081 c:\nwclient\nls\uni_col.351 c:\nwclient\nls\uni_col.358 c:\nwclient\nls\uni_mon.001 c:\nwclient\nls\uni_mon.002 c:\nwclient\nls\uni_mon.003 c:\nwclient\nls\uni_mon.031 c:\nwclient\nls\uni_mon.032 c:\nwclient\nls\uni_mon.033 c:\nwclient\nls\uni_mon.034 c:\nwclient\nls\uni_mon.039 c:\nwclient\nls\uni_mon.041 c:\nwclient\nls\uni_mon.044 c:\nwclient\nls\uni_mon.045 c:\nwclient\nls\uni_mon.046 c:\nwclient\nls\uni_mon.047 c:\nwclient\nls\uni_mon.049 c:\nwclient\nls\uni_mon.061 c:\nwclient\nls\uni_mon.081 c:\nwclient\nls\uni_mon.351 c:\nwclient\nls\uni_mon.358 c:\nwclient\nls\english\dosrqstr.msg c:\nwclient\nls\english\ipxodi.msg c:\nwclient\nls\english\mib2if.msg c:\nwclient\nls\english\mib2prot.msg c:\nwclient\nls\english\netc.msg c:\nwclient\nls\english\nlmigrat.msg c:\nwclient\nls\english\nmr.msg c:\nwclient\nls\english\pnwdiags.msg c:\nwclient\nls\english\pnwmib.msg c:\nwclient\nls\english\pnwtrap.msg c:\nwclient\nls\english\server.msg c:\nwclient\nls\english\stpipx.msg c:\nwclient\nls\english\stpudp.msg c:\nwclient\nls\english\taskid.msg c:\nwclient\nls\english\tbmi2.msg c:\nwclient\nls\english\textutil.msg c:\nwclient\nls\english\wsasn1.msg c:\nwclient\nls\english\wsreg.msg c:\nwclient\nls\english\wssnmp.msg c:\nwclient\nls\english\wstrap.msg c:\nwclient\rpl\dosgen.exe c:\nwclient\rpl\ether.rpl c:\nwclient\rpl\nearserv.exe c:\nwclient\rpl\pcn2l.rpl c:\nwclient\rpl\rboot.rpl c:\nwclient\rpl\rpl.com c:\nwclient\rpl\rplfix.com c:\nwclient\rpl\rplodi.com c:\nwclient\rpl\token.rpl c:\nwcntl\handle c:\nwcntl\resource c:\nwcntl\security c:\nwcntl\server c:\nwcntl\user c:\nwcntl\workgrp c:\nwdos\1050.cpi c:\nwdos\4201.cpi c:\nwdos\4208.cpi c:\nwdos\5202.cpi c:\nwdos\ansi.sys c:\nwdos\append.exe c:\nwdos\assign.com c:\nwdos\attrib.exe c:\nwdos\backup.com c:\nwdos\chkdsk.exe c:\nwdos\choice.com c:\nwdos\command.ico c:\nwdos\comp.com c:\nwdos\country.sys c:\nwdos\create.com c:\nwdos\cursor.exe c:\nwdos\dblbuf.sys c:\nwdos\dconvert.com c:\nwdos\dconvrt2.exe c:\nwdos\debug.exe c:\nwdos\default.fb c:\nwdos\default.ini c:\nwdos\default.nd7 c:\nwdos\delpurge.exe c:\nwdos\delwatch.exe c:\nwdos\devswap.com c:\nwdos\diskcomp.com c:\nwdos\diskcopy.com c:\nwdos\diskmap.exe c:\nwdos\diskopt.exe c:\nwdos\display.sys c:\nwdos\dosbook.exe c:\nwdos\doskey.exe c:\nwdos\dpmi.exe c:\nwdos\dpms.exe c:\nwdos\driver.sys c:\nwdos\edit.com c:\nwdos\ega.cpi c:\nwdos\emm386.exe c:\nwdos\emmxma.sys c:\nwdos\exe2bin.exe c:\nwdos\fastopen.com c:\nwdos\fbx.exe c:\nwdos\fbxfil.hlp c:\nwdos\fbxhelp.hlp c:\nwdos\fc.com c:\nwdos\fdisk.com c:\nwdos\filelink.exe c:\nwdos\find.exe c:\nwdos\format.com c:\nwdos\graftabl.com c:\nwdos\graphics.com c:\nwdos\help.bat c:\nwdos\himem.sys c:\nwdos\hwtestx.fbm c:\nwdos\join.exe c:\nwdos\keyb.com c:\nwdos\label.com c:\nwdos\lock.exe c:\nwdos\mem.exe c:\nwdos\memmax.com c:\nwdos\mode.com c:\nwdos\more.com c:\nwdos\move.exe c:\nwdos\netwars.exe c:\nwdos\nlsfunc.exe c:\nwdos\nwcache.exe c:\nwdos\nwcache.ov1 c:\nwdos\nwcache.ov2 c:\nwdos\nwcdex.exe c:\nwdos\nwdos.ini c:\nwdos\nwdos.nd7 c:\nwdos\password.exe c:\nwdos\pnunpack.exe c:\nwdos\preview.exe c:\nwdos\print.com c:\nwdos\printer.sys c:\nwdos\readme.txt c:\nwdos\recover.com c:\nwdos\rendir.exe c:\nwdos\replace.exe c:\nwdos\restore.com c:\nwdos\rpldoc.txt c:\nwdos\sconvert.exe c:\nwdos\screate.sys c:\nwdos\screxec.exe c:\nwdos\script.exe c:\nwdos\sdefrag.com c:\nwdos\sdefrag2.exe c:\nwdos\sdres.exe c:\nwdos\sdscan.exe c:\nwdos\security.ovl c:\nwdos\serno.exe c:\nwdos\setup.exe c:\nwdos\setup.hlp c:\nwdos\setup.ini c:\nwdos\setup.nd7 c:\nwdos\setup2.exe c:\nwdos\setver.exe c:\nwdos\share.exe c:\nwdos\sort.exe c:\nwdos\stacfm.dll c:\nwdos\stacfm.hlp c:\nwdos\stachigh.sys c:\nwdos\stacker.com c:\nwdos\stacker.exe c:\nwdos\stacload.bin c:\nwdos\subst.exe c:\nwdos\sys.com c:\nwdos\taskmgr.exe c:\nwdos\taskmgr.ini c:\nwdos\taskmgr.nd7 c:\nwdos\touch.exe c:\nwdos\tree.com c:\nwdos\ui.cdb c:\nwdos\undelete.exe c:\nwdos\unformat.com c:\nwdos\uninstal.exe c:\nwdos\unstack.com c:\nwdos\unstack2.exe c:\nwdos\ut.cdb c:\nwdos\vdisk.sys c:\nwdos\vipx.386 c:\nwdos\vir-info.vrb c:\nwdos\winswap2.exe c:\nwdos\xcopy.exe c:\nwdos\xdel.exe c:\nwdos\xdir.exe --------------------------------------------------------------------- Any trademarks referenced in this document are the property of their respective owners. Consult your product manuals for complete trademark information. ---------------------------------------------------------------------