ICLAS COMMON QUESTIONS AND ANSWERS LANSPOOL AND PRINTING PROBLEMS Q1: The printer attached to the server won't print. The print jobs never appear in the queue. A1: A) If it is Novell 2.15 or 2.12, check to see if there is an autoexec.sys file in the \SYSTEM subdirectory. If it exists, delete it. B) Go into PCONSOLE and choose print queue information, choose currently attached servers. If it is blank, escape back and choose queue server, insert, and choose SERVERNAME_ls_vap. Exit PCONSOLE and down the server. When you reboot the server, make sure you answer yes to loading the vaps. C) If it is Novell 2.2, you MUST have an autoexec.sys file in the \SYSTEM subdirectory that contains at least the following 3 lines: p 0 create lpt1 p 0 add printq_0 s 0 printq_0 Also make sure printq_0 has been created using pconsole or by typing "q printq_0 create" at the server console prompt. This only has to be done once and therefore is not required in the autoexec.sys file. Q2: I am getting an error message, "VAP not able to login as printstation." A2: Some files have become corrupted. You will need to delete the old lanspool files and reinstall the latest patches. There are 2 patches that will accomplish this for you: LSREMOVE and LNSPOOLX. Both these files are available from the TA BBS or through you Education SE. If you do not have a way to obtain these, you will manually have to perform these functions. Go to the subdirectory LOGIN\AUTOLOG for ICLAS 1.3 and earlier versions. For ICLAS 1.4, it is in the autolog2 subdirectory. Delete the file clswsdef that has no extension. Go to the LOGIN\LANSPOOL subdirectory and delete the LANSPOOL.INI file. Go into PCONSOLE and choose print queue information and delete all the ls_print_queues, leaving only printq_0 and printq_1. Down the server, bring it back up and reinstall ICLAS from diskettes (see installation manual for information) and down the server again. After bringing up the server again, this message should not reappear. Q3: When using a banner page, the first user of the day prints fine. Every user after that gets a banner page with the name of the user who logged in first that day. A3: There is a problem with the Novell capture file. Download the CAP121.ZIP file from Netwire or order it from IBM Defect Support. Q4: The workstation definitions are not being recognized by the system, even though the printstations are. You might also receive an error message when logging in at any workstation of "No default queue name can be found on server SERVERNAME." A4: Go to the server console : prompt and type p. You should see a list of the printers defined to the server as network printers. You must have at least one printer defined as a network printer to the server. In Novell 2.15 and earlier versions, this is created by going into netgen, custom installation, miscellaneous maintenance, printer maintenance and spooling at least one printer. With 2.2, you must create an autoexec.sys file that is copied into the \SYSTEM subdirectory. This file must contain at least 3 lines. p 0 create lpt1 p 0 add printq_0 s 0 printq_0 Make sure that printq_0 has been created prior to this using pconsole or by typing "q printq_0 create" at the server console : prompt. Q5: During making a printstation or during boot, I get an error message, "Unable to locate SERVERNAME.vap". A5: Usually this indicates that the vap has not been loaded. Go to the server console : prompt and type vap. This will list all of the vaps that are currently in use by the system. If there are none listed, then the vaps were not loaded during install. Down and reboot the server and answer yes to load the vaps during boot. If this does not fix the problem, delete the lanspool.vap file in the \SYSTEM subdirectory and copy the file from the last ICLAS diskette. If this does not fix the problem, then you may be missing additional files and will need to reinstall ICLAS from diskettes. Q6: Getting an error message at the server during boot after the VAP is loading, "Unable to login as print server SERVERNAME_ls_vap OXFF." A6: This indicates that someone has changed the password for lanspool. Lanspool has to have a password of LAN. Login as Sysop and go into Netware Utilities from the main menu. Choose printer console, print server information, select SERVERNAME_ls_vap, choose change password and enter LAN as the password and then again to verify. You will then need to down the server and reboot to take effect. Q7: When trying to create a printstation, there are no queues listed. A7: When you are creating a print station, you will get a listing of available printservers. You must choose the Print Server name of the server to which you are attached. If you choose the name of another server, you will not get a list of any available queues from which to choose. You must be logged in to the server for which you are making printstation assignments. If you are logged in to the server and still do not see any print queues available, there could be some corrupt lanspool files. You will need to delete the old lanspool files and reinstall the latest patches. There are 2 patches that will accomplish this for you: LSREMOVE and LNSPOOLX. Both these files are available from the TA BBS or through you Education SE. If you do not have a way to obtain these, you will manually have to perform these functions. Login as SYSOP and go into PCONSOLE. Delete all the ls_print_queues. Make sure printq_0 and printq_1 are not deleted. Delete \LOGIN\LANSPOOL\*.*, delete \LOGIN\AUTOLOG\CLSWSDEF or \LOGIN\AUTOLOG2\CLSWSDEF and delete \SYSTEM\LANSPOOL.VAP. Down the server, reinstall ICLAS from diskettes (see the installation manual for instructions), down the server again and recreate printstation and workstation assignments. Q8: When trying to create a printstation, no print servers are showing up in the list and you can't insert to add any. A8: Check to see if there is a token ring adapter in the server that is not cabled to the MAU. If so, connecting to the MAU should enable you to see the printserver(s). If this does not fix the problem, You will need to delete the old lanspool files and reinstall the latest patches. There are 2 patches that will accomplish this for you: LSREMOVE and LNSPOOLX. Both these files are available from the TA BBS or through you Education SE. If you do not have a way to obtain these, you will manually have to perform these functions. Go to \SYSTEM and delete the LANSPOOL.VAP, go to \LOGIN\LANSPOOL and delete all the files, go to \LOGIN\AUTOLOG for ICLAS 1.3 and earlier or \LOGIN\AUTOLOG2 for ICLAS 1.4 and delete a file called CLSWSDEF. Also, choose netware utilities from the sysop main menu and choose printer queues or printer console, choose print queue information and delete all the ls_print_queues. Then down the server, bring it back up and reinstall ICLAS from diskette. Down the server again and bring it back up. Q9: Getting error message, "Vap not able to login as printserver lanspool.vap 0XFC." A9: This error is caused when files have become corrupted. You will need to delete the old lanspool files and reinstall the latest patches. There are 2 patches that will accomplish this for you: LSREMOVE and LNSPOOLX. Both these files are available from the TA BBS or through you Education SE. If you do not have a way to obtain these, you will manually have to perform these functions. Go to \SYSTEMand delete the LANSPOOL.VAP, go to \LOGIN\LANSPOOL and delete all files, go to \LOGIN\AUTOLOG or \LOGIN\AUTOLOG2 and delete CLSWSDEF. Choose Netware Utilities from the main SYSOP menu and go into Printer Console or Printer Queues, choose Print Queue information and delete all the ls_print_queues. Down the server, reinstall ICLAS from diskettes and down the server again. Also, very occasionally, this can be caused by the password for the print server being changed. Go into Netware Utilities, Choose Print Queue Management or Printer Console, depending on the version of ICLAS that you have. Once you are in Pconsole, choose Print Server Information, choose your SERVER_NAME_LS_VAP, enter and change password to LAN. If you get a purple box saying this is a duplicate password, then it was already set to LAN. Q10: None of the print jobs will print until the user exits from the application program. A10: The timeout is not set correctly. Choose Netware Utilities from the SYSOP menu, then choose System Configuration, Supervisor Options and System Login Script. On the line that begins with #spool, change the timeout to timeout=5 or some other number. If you have it set to 0, the timeout feature is disabled and nothing will print until you exit the program. If you change it to another numerical value, it will wait that number of seconds before sending the job to the printer from the print queue. If it is set correctly in the system login script, check the individual program start instructions to see if a spool or capture command is used and make changes to the timeout there as well. Q11: I am trying to create a printstation in ICLAS 1.4 and get an error message, "Another user is making printstations at this time. Printstations can only be created on one workstation at a time." There is no one else logged in as SYSOP trying to make assignments. A11: When you are creating a printstation, there is a file called UNLOCKED that is renamed to LOCKED. Look in the \LOGIN\LANSPOOL subdirectory. You should see a file by the name of UNLOCKED. If you see a file called LOCKED, rename it to UNLOCKED and you should be able to go in and create printstations. If you have both files, delete the LOCKED file and it should now work. Q12: I have installed Edlan 1.0 and it will not print. The jobs get to PRINTQ_0, show a status of Adding, Ready, Active and then disappear from the queue but nothing ever prints. A12: If it is a Model 80, go in with the reference diskette and change the LPT1 port to PARALLEL_2 instead of PARALLEL_1. If this does not work or you have a PS/2 other than a Model 80, you will probably need to change the configuration of the printers in Netware 2.15. Edlan 1.0 and 1.01 installed COM1 as Printer 0 and LPT1 as Printer 1. Use the Edlan #3 diskette and perform Miscellaneous Maintenance to make these changes: Boot with Edlan Diskette #3, type Maint. After you review a list of drives, press escape, if list is correct, press enter and you will be presented with the installation options menu. Choose Customer Installation Options, select Miscellaneous Maintenance, and then Printer Maintenance. Delete the spooling for both COM1 and LPT1. Then select LPT1 first and spool it as Printer 0, and if desired, spool COM1 as Printer 1. Highlight return to previous menu and Enter to return to the Miscellaneous Maintenance menu. Press escape to save several times until asked if you want to use the new printer definitions. Select Yes and enter, choose Return to Previous Menu on the Customer Installation menu and choose Continue Installation on the Installation Options menu. Select Yes to install networking software. You should be returned to the DOS prompt when all processing is complete. Your printing should now work correctly after downing the server and rebooting and loading the LANSPOOL.VAP. Q13: I used LSREMOVE and installed the 3.01 LANSPOOL patch. Now my workstations won't keep their printstation assignments. A13: You will need to copy the file named IBM$RUN.OVL from \PUBLIC to \LOGIN\LANSPOOL. This should fix the problem. Q14: After powering off the workstation or server, it is no longer recognized as a printstation. A14: If booting from diskette, check the autoexec.bat file to make sure that it contains these 3 lines after netdrive and before clssetv: cd\login\lanspool node /A >nul (The A must be capitalized) cd\login If booting remotely, the autoexec.bat file on the diskette used during dosgen to create the remote boot image must contain the 3 lines listed above. If not certain, redo the dosgen. Also, a copy of the autoexec.bat has to be in both the \LOGIN and the \LOGIN\LANSPOOL subdirectories. ICLAS COMMON QUESTIONS AND ANSWERS LOGIN PROBLEMS AND QUESTIONS Q1: When a user is trying to login, they get an error message, "Unable to create SERVERNAME\SYS:login\autolog\2.LGN." (or SERVERNAME\SYS:login\autolog2\2.LGN. This could be any number) A1: Whenever you login to ICLAS, there is a file created that contains all your login information and the name comes from the station connection number to which you physically attach to the file server. Each time you login, a new file is created. The first thing to check is to make sure that you have enough disk space or directory entries available to be able to create this file. Check this through VOLINFO or Volume Space Information from the SYSOP main menu. Also, if the file has become corrupted and can't be written over, then you will get this file creation error. This especially happens if the file is a zero byte file. Go to the correct subdirectory and delete this file and you should now be able to login as that station number. Q2: Getting an error message when logging in, "Invalid command.com, system halted." A2: Once you boot your system and connect to the network, it will use the COMMAND.COM from the server in \PUBLIC\DOS\V3.30, (or the correct version number of DOS with which you are booting your workstation. Type VER at a DOS prompt on the workstation to check.) instead of the local drive, if there is one. Using the map command, check to see that you are mapped to the correct DOS version. If it is correct, check the date and size of the command.com on the workstation and on the server to make sure they are identical. Also check to make sure you do not have a copy of COMMAND.COM in any subdirectory other than DOS by typing "ndir COMMAND.COM /sub" at the root directory. Delete all copies of COMMAND.COM you find that are not in the DOS subdirectories. Q3: I am logging in as SYSOP at the non-dedicated server and am getting an error message, "Insufficient disk space, path not found." A3: You probably do not have a large enough vdisk or ramdrive specified on the server machine. When you login, several files are copied to the vdisk or ramdrive and if you don't have enough space, the files cannot be copied. Therefore, when these files try to run, you will get errors. Check the config.sys file and make certain that you have at least a 10K vdisk or ramdrive. The statement should read: DEVICE=VDISK.SYS 10 128 or DEVICE=RAMDRIVE.SYS 10 128 Q4: I am trying to login as SYSOP with ICLAS 1.4 and keep getting an error message of "Invalid Directory" that keeps scrolling down the screen. What is causing this? A4: This is caused by a bug in one of the files for ICLAS 1.4. This is fixed in the patch for ICLAS 1.4 called CLS14FIX.TG0 from the TA BBS. You may also get this patch from your Education SE. Q5: In a school that has never required passwords for their users we are suddenly getting errors when the users login that their passwords have expired. How can I get around this problem? A5: There are 2 temporary fixes that will work to fix this problem until an official fix is available. Login as SYSOP, go into Novell Utilities, choose System Configuration, User Information and you will be presented with a list of all users. Mark all the users that you want to change at one time by using the F5 and cursor down keys (MAKE SURE YOU DO NOT CHOOSE THE PC-CLAS_LOGIN_DO_NOT_REMOVE ID). Then choose Accout Restrictions. FIX 1) Set Require password to yes and escape. You will be prompted if you want to make this change for all users, choose yes. Then mark all the users again and go back into Account Restrictions and set this back to No for all users. This will reset all the accounts and should fix the problem. FIX2) Set Require password to yes and cursor down to the days between forced changes and set it to 365. This will force users to have a password, but they won't have to change it all year. ICLAS COMMON QUESTIONS AND ANSWERS APPLICATION PROBLEMS AND QUESTIONS Q1: Trying to start a program from a student's menu and getting error, "Unable to open" or "Unable to create" or "Unable to locate" messages for .USE file, .DAT file, .BKM file, or .TRN file. A1: Try removing from the teacher's menu and adding back again. Also, check in the courses\application name to see if the file by that name is actually there. If not, it could be that the program didn't install properly. Try removing the program from ICLAS and reinstalling from diskette. Also, check the volume space and number of directory entries available to make sure you have enough space. Q2: I am trying to use the option from the student's or teacher's menu to run a program from the A: drive and it just keeps going back to the menu. A2: When you use the option to run a program from the A: drive by typing CTRL-A, it will look on the diskette in the A: drive for a file called G.BAT. If it finds one, it will run that program. If it doesn't find a G.BAT file on the diskette, it will run the G.BAT that is resident in vdisk memory and will bring you back to your menu. To be able to use this option, create a G.BAT file on your program diskette with the correct program start instructions. Q3: I have 50 licenses for my software, but can't get that many people signed on and using it. A3: There are 3 things that can subtract from the number of available stations that can be connected into a software program and take additional license counts: 1.) The students are not properly exiting the program. Make sure they logoff properly and are not just shutting off the system so the license count can be relinquished. 2.) The program start instructions include a %V%G or a G. This will load ICLAS again and is not necessary. If you have either of these, it will not release the license count back to the server so delete the %V%G or G. 3.) The program start instructions include a batch file name without using the "call" command to start it. Also make sure that the batch file does not invoke or contain a %V%G or a G. In order to reclaim license counts once one of these has happened, you will need to down the server. Q4: I have a school that does not want their students to be able to get out of their applications and exit to DOS. Is there a way to prevent this? A4: Yes, you can stop them exiting out of the application and getting to DOS by altering the program start instructions. From the sysop main menu, choose Modify Program Install Options. Select whether the application is Courseware or Office Applications. You should then see a list of all the application programs you have installed on the server. Choose the application you want to change and hit F10. This will bring up the screen you saw when you first installed the application. The line that we will want to change is the Program Start Instructions line. This line contains several commands separated by the carat symbol (^). This is similar to a batch file in that each command is executed whenever you choose this program off the menu. You will need to put a command in as the very first command, so go to the beginning of the instructions and make sure that your insert key is turned on (the cursor will be a blinking block when you are in insert mode and a blinking underline when you are in replace mode). The first command should be: comspec=Y:command.com /C Also, be sure to put the carat (^) as a separator between this command and the original start instruction text. Go to the very end of the program start instructions by hitting the end key and type in as the last instruction: comspec=Y:command.com This will keep students from getting out to the DOS prompt while they are using this application and will just bring them back in to the application. Q5: When I try to start a program, I get an error message of "Could not add comspec=Y:command.com to the local environment variables." A5: This is caused when the DOS shell is not large enough to hold all the variables that are set by ICLAS. The default size of the shell is 160 bytes. To fix this problem, add a line to the config.sys that reads: shell=command.com /E:1024 /P This will set the environment space to 1024 bytes and should be large enough for all the variables to be set correctly. Q6: I am getting "Out of Environment space" errors on my workstation. A6: This is cause by the same reason as Q5. Proceed with the A5 as the solution. Q7: I would like to use the network at times, but at other times I would like to only use my local fixed disk on my workstation. How can I do this? A7: There is a command on the ICLAS diskette #1 called harddisk. Put ICLAS diskette #1 into the diskette drive of your workstation and type harddisk. This will add some items to your autoexec.bat and will copy some files to your fixed disk that will present you with a menu when you first boot your machine. This menu will give you the choice of being able to "Access the Network" or "Run without the Network." If you choose to access the network, it will issue the commands of IPX, NET3 and other commands to connect you to the server. Q8: I am trying to set up a fixed disk workstation using the harddisk command in ICLAS with DOS 5.0 or DOS 4.0. How do I get it to work? A8: The harddisk command sets up menus that allow you to use the network or use your local machine without connecting to the network. This defaults to the settings for DOS 3.3. In order to use this menu with another version of DOS, you will have to alter the menu options. The menu that gives you the option to run with the network or use your local machine is called STARTUP.MNU and is copied from the ICLAS diskette during the harddisk command. You will need to edlin this file and change the line that has the option to "Access the Network." Following the option, you will notice that there are commands separated by the carat (^). The one that you will need to change is NET3. Change this to the current shell file you are using: NET4, NET5, or NETX and coy this file to the fixed disk. Also, you will need to insert the command CLSSETV between the NETDRIVE command and the G command. Save this file and exit and once you reboot your workstation, you should be able to login to the network correctly when choosing this option. Q9: I am trying to load some Basic Skills software and the screen goes black and the workstation locks up when I try to load it. What could be causing this? A9: This is usually caused by a corrupt file. All the Basic Skills software programs use a file called KERNEL42.EXE in the \COURSES\B_SKILLS subdirectory. If this file becomes corrupt, it will cause this error. Also, make sure that you do not have any other KERNEL files in this subdirectory with any other numbers. You can delete the KERNEL42.EXE and recopy it from the ICLAS diskettes. In ICLAS 1.4, this file is dated 6/18/91 and is 24471 bytes. Q10: I installed Microsoft Works and then later copied a printer driver to the subdirectory. Works will not print using the new printer driver, but will still print using the printer drivers that previously existed. A10: You will need to reinstall Works. It will not see any drivers that you add after installation. Q11: I am trying to run an application program and am getting an error that I am out of memory. What can I do to fix this problem? A11: First check to make sure that your workstation has a minimum of 640K. This is required for many application programs. Next, check the AUTOEXEC.BAT of the workstation boot diskette for any terminate and stay resident programs that might be taking up memory. If you are in doubt about any of the items, remove the line or remark out the line and reboot to see if it clears up any memory. There is also one file within ICLAS that takes up quite a bit of memory. The file is called CLSRES and is called from within the CLS.BAT file when the workstation logs on. This file runs the pop-up menu that lets you control printers and messaging by pressing the CTRL-ESC keys. If you do not need this menu, you can gain back the 22K of memory it takes up. The CLS.BAT file is located in \LOGIN. Simply edit the file and remark out the line that contains the CLSRES command. Q12: When students send a job to print from an application, the print jobs will not print until the student exits from the application program. A12: The timeout is not set correctly. Choose Netware Utilities from the SYSOP menu, then choose System Configuration, Supervisor Options and System Login Script. On the line that begins with #spool, change the timeout to timeout=5 or some other number. If you have it set to 0, the timeout feature is disabled and nothing will print until you exit the program. If you change it to another numerical value, it will wait that number of seconds before sending the job to the printer from the print queue. If it is set correctly in the system login script, check the individual program start instructions to see if a spool or capture command is used and make changes to the timeout there as well. ICLAS COMMON QUESTIONS AND ANSWERS ICLAS PROBLEMS OR QUESTIONS Q1: I have installed ICLAS 1.4 in an environment where there are also ICLAS 1.3 servers on the network. The customer will need to be able to passthru from the 1.4 to 1.3 servers and vice versa. A1: In the ICLAS installation manual, on page 6-4, is an explanation of how to accomplish this. You will need to prepare a transfer diskette from ICLAS 1.4 and take it to the 1.3 or earlier servers. This will update the passthru files to a later version so you will now be able to communicate with a 1.4 server. Q2: I am trying to run the tape backup program from the sysop main menu and it tells me to create a batch file to be able to do this. What needs to be in this batch file? A2: If you are using the PS/2 Internal Tape Backup, for ICLAS 1.4, you will need to apply the patch INTTAPE4 which is available from your Education SE or the TA BBS. For ICLAS 1.2 or 1.3, use INTTAPE2, which is also available from the same sources. This patch contains the correct batch files to allow the PS/2 Internal Tape Backup Program to be run from the SYSOP main menu. If you are using some other tape backup software, you will need to create a batch file using the correct parameters for that particular program. Q3: I am trying to run the IBM internal tape backup program from the server with Novell 2.15 and it locks up the server. A3: There is an incompatibility with the Novell 2.15 shell and the IBM internal tape backup program. You will need to run the Net3.com or Net4.com file from 2.12 on the server or workstation where you are backing up. The Net3.com and Net4.com files from 2.12 are available from your IBM Education SE or from the TA BBS. There is no Net5 or Netx.com files, so you will be unable to backup using a DOS 5.0 machine. You will also need to make sure you have the internal tape program V1.12 or 1.13. Q4: I am trying to run the IBM internal tape backup program from the server with Novell 2.2. It appears to execute the program correctly, but gives an error message of "Access denied" on the 2 bindery files, NET$BVAL.SYS and NET$BIND.SYS which are hidden files located in the \SYSTEM subdirectory. A4: There is an incompatibility with the Novell 2.2 shells and the IBM internal tape backup program. You will need to run the Net3.com or Net4.com file from 2.12 on the server or workstation from which you are running the tape backup software. The Net3.com and Net4.com files from 2.12 are available from your IBM Education SE or from the TA BBS. Also make sure you are using the Internal Tape Backup Program V1.12 or 1.13. There are no Net5 or Netx.com files that you can use with Novell 2.12, so you cannot perform the backup with a DOS 5.0 machine. Another method you could use to accomplish this is to run bindfix. This will create a copy of the bindery files on the server machine. Run backup after the findfix and the copies will be backed up. Then, you can run restore and then run bindrest. This will take the backup of the bindery files and make them the current bindery files. Q5: What version of the IBM Internal Tape Backup Program is supported with ICLAS? A5: You will need to run the Internal Tape Backup Program 1.12 or 1.13. Versions of the tape program prior to 1.12 did not backup the Novell bindery files. Q6: I am getting an error 51 on my workstation or server. A6: An error 51 usually indicates a cabling or hardware problem occuring with baseband networks. It could also indicate a bad baseband adapter card. Also check your baseband network to make sure that there is no more than 1 wrap plug in the entire network. Q7: I am using ICLAS 1.4 and have assigned my workstation to a specific server from the SYSOP main menu but my workstation is not attaching to it automatically. A7: There are 2 steps to assigning a workstation to attach to a specific server: 1) Login as SYSOP at the workstation, go into workstation assignments, Server Assignments and choose the printer. 2) On the workstation boot diskette, you must copy the file CLSSRVST.EXE onto the diskette and include in the AUTOEXEC.BAT the line CLSSRVST after NETDRIVE and before CLSSETV. Q8: Someone was performing some maintenance on the system and now no one can login. A8: This occurs when the userid PC-CLAS_LOGIN_DO_NOT_REMOVE was removed or was assigned a password. You will need to edit the AUTOEXEC.BAT file on a workstation and remove the last line that issues the G command. Boot the system with the diskette and at the Novell F: prompt, login as supervisor. You will need to reinstall ICLAS in order to restore this ID and allow ICLAS users to be able to login again. Q9: None of my users are showing up in ICLAS. If I go into Novell Utilities, System Configuration, User Information, I can see them all. A9: The first step you should do is to run BINDFIX to repair any possible errors in the Novell bindery files that hold all USERIDS and their associated access rights. After this has completed, locate your ICLAS diskettes, insert diskette 1 and type PHOENIX. This will take the Novell bindery files and convert them into ICLAS user files. After Phoenix completes, go to the file ALLUSERS.CLS in \ADMIN and rename it to ALLUSERS.OLD. Phoenix creates a file called PHOENIX.CLS. Rename it to ALLUSERS.CLS. You should now be able to see all your users in ICLAS. Q10: I am going into Set System Defaults from the SYSOP main menu in ICLAS 1.4 and when I try to change the setting for Turn On Banner to No, I get an error message in a red box that says "Cannot open NET$LOG.DAT file. Press any key to continue." A10: The NET$LOG.DAT file is the file name of the system login script. This file is probably flagged incorrectly. Hold down the ALT key and type E-S-C to get to DOS. Change to the \PUBLIC subdirectory and type "flag NET$LOG.DAT srw". Type G to go back to the ICLAS menu and go back into Set System Defaults. You should now be able to set the banner to no. This problem is fixed in the latest ICLAS 1.4 patches. Q11: I need to use DOS 5.0 with ICLAS 1.3 or earlier and it will not work. A11: ICLAS 1.3 and earlier versions require workstations to have a vdisk loaded. They do not recognize the ramdrive of DOS 5.0. You will need to get a patch called CLASDOS5.EXE that will allow these earlier versions of ICLAS to recognize the ramdrive. Q12: I am trying to login to an ICLAS 1.4 server and am getting an error message of "Invalid Directory" when I try to login as SYSOP on the non-dedicated file server. If I login as any other user, it works. Also, if I login as SYSOP from another workstation, it works fine. What is causing this error? A12: This may be caused by the vdisk or ramdrive on the non-dedicated server not being large enough. Check in the config.sys of the server for the size. You should have your vdisk or ramdrive set to a minimum size of 10K. The command should look something like this: DEVICE=VDISK.SYS 10 128 If it is set to 6K as indicated in some of the ICLAS text, this will not be large enough to store everything that is needed on the server machine. Q13: I am trying to use a diskless Model 55 or Model 35 and keep getting an error message to insert a diskette. A13: Diskless machines can only be used with ICLAS 1.4 because they can't use a vdisk. ICLAS 1.4 is the only version of ICLAS that does not require a vdisk. You must use a CONFIG.SYS in the NET$DOS.SYS remote boot image file that does NOT designate a vdisk. If you do have a vdisk statement, ICLAS will try to run the G.BAT program from the vdisk rather than the server. When it does not find the file in a vdisk, it will prompt you to insert a diskette. If you do not specify a vdisk, ICLAS will look for the files on the server, which is the correct location, and will not prompt you to insert a diskette. Q14: I have several student ID's that were created without passwords. I now want to assign passwords to them, but they do not have an option on their menu to change their password. How can I update this? A14: When you create a student ID, there is a menu that is created for that student. During the creation, you are asked if you want to use the password option. If you do not assign a password and do not use the password option, the menu that is copied is students.mnu. If you do use the password option or assign a password, the studentp.mnu is copied for the user. The only difference in these 2 files is that the studentp.mnu file has the option for changing the password. When the student is created, the studentp.mnu or students.mnu is copied to the \STUDENTS\MENUS subdirectory as the userid, padded with underlines to equal 8 characters followed by __# and this menu is used from then on. (i.e. the user tom would have a menu called tom_____.__#) To change this menu, you would need to copy the studentp.mnu over the top of the user's menu. The student would then have the option of changing his password. To accomplish this for the entire group of students, you could login as SYSOP, go into List/Modify User Information, choose the type of student by typing an s in the type user field and pressing F10. This will bring up a list of all the student users. If you press F3, you can save all these users to a file on diskette after pressing the right arrow key. Then delete all these students from ICLAS by choosing Remove User IDs. Once they have been removed, ALT E-S-C to DOS and cd\ADMIN. Rename the students.mnu to students.old and copy studentp.mnu to students.mnu. Type G to go back to SYSOP menu and choose Add New User IDs. Press F2 to Include a File and give the name of the file that you previously saved with all the student id's. This will re-add all the student users who will now all have the menu with the change password option. Once you do that, go out the \ADMIN, delete the students.mnu and rename the students.old back to students.mnu for future use. Another way to fix this problem without having to delete the students is to go out to \ADMIN and rename the students.mnu to students.old and copy studentp.mnu to students.mnu. Then insert ICLAS 1.4 diskette #5 and type a:cls14mnu. This will force an update of all the menu files for each user and your students should then have the menus with the change password option. Then simply delete the students.mnu and rename students.old to students.mnu. Q15: In a school that has never required passwords for their users we are suddenly getting errors when the users login that their passwords have expired. How can I get around this problem? A15: There are 2 temporary fixes that will work to fix this problem until an official fix is available. Login as SYSOP, go into Novell Utilities, choose System Configuration, User Information and you will be presented with a list of all users. Mark all the users that you want to change at one time by using the F5 and cursor down keys (MAKE SURE YOU DO NOT CHOOSE THE PC-CLAS_LOGIN_DO_NOT_REMOVE ID). Then choose Accout Restrictions. FIX 1) Set Require password to yes and escape. You will be prompted if you want to make this change for all users, choose yes. Then mark all the users again and go back into Account Restrictions and set this back to No for all users. This will reset all the accounts and should fix the problem. FIX2) Set Require password to yes and cursor down to the days between forced changes and set it to 365. This will force users to have a password, but they won't have to change it all year. Q16: I have some corrupt files in ICLAS. Is there any way that I can force my ICLAS 1.4 files to be recopied from diskette? A16: Yes, you can actually trick the system into believing it has an earlier version of ICLAS and therefore, force it to recopy all the ICLAS files. There is a file by the name of CLSV1.40 in \PUBLIC. If you rename it to CLSV1.20 or CLSV1.30, ICLAS will think that you have a previous version of ICLAS installed. You should go through a normal ICLAS installation by typing A:G and all the ICLAS files should be copied as if it were a brand new installation of this version. Q17: How can I attach to a preferred server with ICLAS? A17: In ICLAS 1.4, you would need to login as SYSOP, choose workstation assignments, and Server Assignment. Choose the server that you would like this workstation to always attach to. Then as step 2, you must copy the CLSSRVST.EXE file to the workstation boot diskette from the ICLAS 1.4 diskette and also put the CLSSRVST command in the autoexec.bat of the workstation between NETDRIVE and CLSSETV. In ICLAS versions prior to 1.4, you have 2 options. 1) If you have a workstation shell that is version 3.01 or higher, you can specify a preferred server on the NETx line in the autoexec.bat -- i.e. NETX PS=server_name. 2) If you have a shell prior to 3.01, you can put the following command in your autoexec following NETDRIVE: LOGIN server_name\PC-CLAS_LOGIN_DO_NOT_REMOVE To see what version of the shell you have, type NETX I and this will give you information about the shell with the version number. Q18: How can I upgrade ICLAS to let 100 users attach to the server? A18: There is a program called the 100 User upgrade. This program, like the original ICLAS program, is available through the EduQuest Marketing Rep. or Systems Engineer. Q19: If I am using an IBM Bridge, do I need to use source routing? A19: Yes, you will need to load ROUTE.VP0 on your 286 server by copying this file into the \SYSTEM subdirectory. It will then load once the server is rebooted. On a 3.11 server, you will need to load ROUTE.NLM either manually at the server prompt, or through the server's autoexec.ncf file. Also, on every workstation, you will need to copy ROUTE.COM to the boot diskette and load this file between IPX and NETx. Q20: I am trying to passthru to another server. Sometimes it will work and sometimes it will not. If I try and do a Novell attach command or a Novell slist command, sometimes I can see the other server, but not all the time. A20: Usually, this is caused by the incorrect LAN Addresses being used during installation. When installing Netware and choosing the LAN driver, it will also prompt you to enter a LAN address. This is very important when you are connecting different networks. Every adapter card that is connected to the same physical network has to have the same network address. Each adapter card that is on a separate physical network has to have a different LAN address. For instance, if I have a Token-Ring and a Baseband adapter in one server, they will need to have different network addresses because they are connected to two different networks. You can check to see what the LAN address setting is by using the :CONFIG command at the server prompt (ALT E-S-C out to DOS at the server, type console and you will be at the Novell server prompt of :). This will tell you the type of network adapter, which driver was chosen and also what LAN address was assigned during installation. Also, if your servers are non-dedicated, the DOS process also has its own address. Each DOS address has to be unique and different from every other LAN address and DOS address in the school. If you need to change the LAN address, you will need to perform maintenance on the servers, which will vary depending on the method of installation that you used initially and which version of Novell you are using. ICLAS COMMON QUESTIONS AND ANSWERS EDLAN PROBLEMS AND QUESTIONS Q1: What are the different versions of software programs included with EDLAN? A1: EDLAN 1.0/1.01 EDLAN 1.1 Novell 2.15 2.2 ICLAS 1.3 1.4 Microsoft Works 2.0a 2.0a Excelsior Grade 1.6 N/A Excelsior Grade2 N/A 1.0 Excelsior Quiz 2.5 2.5 LANSchool 3.0 3.01 Linkway 2.00 2.01 Express Publisher 1.1 2.0 Q2: How can I install Edlan onto an Ethernet server? A2: Edlan includes drivers for both Token Ring and Baseband adapters in the installation program. Ethernet drivers are not included. To install Edlan onto an Ethernet server, you will need to install Novell from diskettes. Once Novell is installed, you can then use the Edlan tape to install both ICLAS and the software tools. Q3: I am trying to install Edlan and am getting message, "In order to install Advanced Netware, you must perform the following steps:" A3: This indicates that you probably do not have enough memory. Edlan requires a minimum of 4MB to install. Q4: I am installing Edlan 1.0 or 1.01 and can't get it to work on the Model 90/95. A4: The Model 90/95 require the latest SCSI drivers that were not included on the Edlan 1.0 tape. You will need to install Novell from diskette on the Models 90 and 95 after you get the latest SCSI drivers and copy them onto the DSK_DRV_001 diskette. You can then install ICLAS and the tools from the tape after you boot the server. Q5: I am trying to run the Microsoft Works setup program and the program hangs. How can I fix this problem? A5: There is a bug in the Microsoft Works setup that will cause the program to hang if the Network adapter is not set to IRQ2. If your adapter is set the IRQ2, the program works properly. The only fix at this time is to make sure the adapter hardware is setup correctly to IRQ2. Q6: Where is the PCN2.RPL file when you install your system from EDLAN 1.0? A6: This file is copied into the \SYSTEM subdirectory when you install using Edlan 1.0. Q7: I am trying to run the Microsoft Works setup and can't get it to work on the server. A7: The Microsoft Works setup cannot be run from a server. It must be run from a workstation. Q8: How can I increase directory entries in Edlan? A8: With Edlan 1.0 and 1.01, you will need to boot the server with Edlan Diskette #3. Once you boot the server, type Maint and go into Miscellaneous Maintenance. Choose Volume Maintenance and change the directory entries to the number that you choose. Escape once you have made your changes. With Edlan 1.1, boot with Edlan diskette #1, choose Option 6 for Netware System Maintenance. You will then be presented with a menu of options you can change after you are prompted to insert the OSOBJ diskette. Increase the number of directory entries (up to the maximum of 32,768) and escape out once you have made all your changes. ICLAS COMMON QUESTIONS AND ANSWERS REMOTE BOOT PROBLEMS AND QUESTIONS Q1: What will I need to do to be able to remote boot a workstation? A1: You will need the following files on the server: - Token.RPL or PCN2.RPL in the \LOGIN subdirectory - RPL.VP1 in the \SYSTEM subdirectory and this VAP must be loaded when the server is booted - a NET$DOS.SYS file in the \LOGIN subdirectory. This file is created from the DOSGEN process. You will need a workstation boot diskette that currently works and allows you to connect to the server. Running DOSGEN takes these files on the workstation boot diskette and compresses them into the one file called NET$DOS.SYS. This is then the image that the remote boot system will be looking for when it connects to the server. In addition to these files, you will also need to copy the autoexec.bat file into the \LOGIN and \LOGIN\LANSPOOL subdirectories. Also, you will need to make sure that your hardware on the workstation is correctly setup for remote boot. The Token-Ring adapter requires the addition of an eprom (a chip that you add to the card) that will enable remote boot. (The new token-ring adapters already include this feature. You can identify these by looking at the adapter card itself. If there is a spot that you could plug a chip into, you have one of the older adapter cards. If your adapter card has no space where a chip could be added, you probably have one of the newer adapter cards.) For baseband, you will need to set the jumpers or switches on the AT bus adapter to enable remote boot. For microchannel adapters, this is set using the reference diskette. Q2: I am remote booting into a server and I can attach to the server, but am getting a message "Missing Batch file." A2: The image file is looking for the autoexec.bat file. You need to copy the autoexec.bat from the diskette that you used to create your image into the \LOGIN and \LOGIN\LANSPOOL subdirectories. Q3: Can I use diskless machines to attach to an ICLAS server? A3: Diskless machines can be used with ICLAS 1.4 only because it is the only version of ICLAS that does not require the use of a vdisk or ramdrive. Q4: I am booting a diskless machine to an ICLAS 1.4 server, but I am getting a message to "Insert diskette with batch file." What is causing this message? A4: You will receive this message when you are booting a diskless machine to an image that contains a vdisk or ramdrive specified in the config.sys. You cannot have a vdisk specified in the config.sys for a diskless machine. If you do specify a vdisk, ICLAS 1.4 will assume that the G.BAT file will be stored in the vdisk and this is the file it is looking for. With diskless machines, since they do not have any local DOS drives, the first network drive is A: instead of F: as it is on machines that do have local drives. Therefore, when you boot a diskless machine, the vdisk is set up initially, but is written over once you attach to the network. If you do not specify a vdisk or ramdrive with ICLAS 1.4, the files are copied to the server rather than the vdisk. Redo the image to not include a vdisk or ramdrive in the config.sys and you should be able to boot correctly. ICLAS COMMON QUESTIONS AND ANSWERS SERVER BOOT PROBLEMS AND QUESTIONS Q1: When I boot my server, it always asks me if I want to load the VAPS. Is there any way to have these automatically load without having to manually answer this question? A1: Yes, you will need to create a file called SERVER.CFG that will be located in the \SYSTEM subdirectory. In this file, put the line: VAP WAIT 10 This will automatically load any vaps located in the \SYSTEM subdirectory after waiting 10 seconds to give you a chance to choose not to load them. Q2: When I boot my server, it takes an extremely long time to boot, generally over 30 minutes. Most of this time is spent "Checking Bindery." There are a large number of userids in the server. A2: You probably specified "Limit Disk Space" as yes during the installation. When you select this option, the server must count the allocated disk space for each userid during the boot process. If you set the option to no, it will no longer require the time to check this disk space allocation and will significantly reduce the boot time. To reconfigure the operating system and set this parameter to no will require a reinstallation of Netware from diskettes. You should perform an Advanced Install and be sure to specify that this machine is NOT the server. This will prevent any information from being written to the file server and will be written to diskette instead. Once you complete the installation, go back into installation and choose to Maintain Existing Server. This time be sure to specify that this machine IS the server. Q3: What is the recommended way to upgrade an existing 2.15 or 2.2 server to Novell 3.11? A3: There is a document that is available from the TA BBS or from your Education SE that is called UPGTO311. This document lists in great detail how to accomplish this.