home *** CD-ROM | disk | FTP | other *** search
- PROBLEMS ENCOUNTERED WHEN RUNNING "LANBIOS"---
-
- PROBLEM: When I run LANBIOS I get the error message, "No LANtastic
- Hardware present at this address....."
-
- REMEDY: 1. Check for any other adapters in your computer
- which could be sharing the same or parts of the 32K
- address block between 640K and 1MG that the LANtastic
- adapter maps. Remove the other adapters and see if
- the same message is returned. You can try other address
- locations on the LANtastic adapter or if the another
- adapter has jumpers or dip switches that can be changed
- to prevent address conflicts with the LANtastic adapter,
- change it accordingly.
-
- 2. Check to see if you are running Expanded Memory.
- Expanded memory makes use of the available area in your
- PC between 640K and 1MG. Most Expanded memory managers
- have a way to EXCLUDE blocks of memory that are being
- used by other adapters. You should EXCLUDE the 32K block
- corresponding to the address setting on the LANtastic
- adapter. These 32K block addresses are located on page
- 6 of the "LANtastic 2Mbps LAN Adapter User's Manual."
- If you are using the default address of 6 on the
- LANtastic adapter, then you should EXCLUDE D800-DFFF.
- Check your Expanded Memory Manager documentation for
- details on your specific software.
-
- 3. Make sure that when you type in LANBIOS with optional
- configuration parameters that you are not adding spaces
- between the parameter, the "=" and the number.
- WRONG: LANBIOS irq = 3
- RIGHT: LANBIOS irq=3
-
- 4. Make sure that you are typing in the whole word.
- WRONG: LANBIOS addr=5
- RIGHT: LANBIOS address=5
-
- PROBLEM: LANBIOS does not install or return an error message.
- The curser just sits there and locks my computer up.
-
- REMEDY: 1. Remove any memory resident program that you are
- running before LANBIOS. This includes keyboard speedup
- programs, screen savers and some disk cache programs.
-
- 2. If you are running DOS 3.2, you should try booting
- from 3.1 or 3.3. DOS 3.2 has errors in the internal
- stack handler and can cause lock ups and server
- disconnections.
-
-
- PROBLEMS ENCOUNTERED WHEN RUNNING "REDIR"---
-
- PROBLEM: REDIR does not install or return an error message.
- The curser just sits there and locks my computer up.
-
- SOLUTION: You have an irq conflict with another adapter board in
- your computer. If you do not have a second comm port
- set the LANtastic adapter to irq=3. Make sure that when
- you run LANBIOS that you specify irq=3.
-
-
- PROBLEMS ENCOUNTERED WHEN RUNNING "SERVER"---
-
- PROBLEM: When I run the SERVER program I never get an installed
- message. It just hangs and locks up my computer.
-
- REMEDY: You are running SideKick. Run SideKick after you have
- run SERVER. Memory resident programs can interfere with
- the SERVER program scheduling.
-
- OTHER MISC. PROBLEMS ENCOUNTERED
-
- PROBLEM: I can't seem to login to more than two machines. It
- doesn't matter which two. I get the error
- message, "Duplicate redirection or login to network
- node..."
-
- REMEDY: 1) Check version numbers on all your computers by
- typing "redir" at the DOS prompt. Each computer should
- be running a 2.xxU or 2.xxG version in order to login
- more than two times.
-
- 2) Next on each workstation that will be logging into
- more than the default number of two servers, you must
- add: logins=n where n is the number of logins that you
- will be doing from that workstation. The syntax is as
- information, see page 7-2 of your LANtastic NOS User's
- Manual.
-
- 3) If you are logging in more than 1 time using the
- same Username and Password, you must specify the number
- of concurrent logins for that user. See your LANtastic
- NOS User's Manual page 6-5 for more information.
-
- 4) Invoke the NET_MGR program and select the "server
- startup parameters" area. Check the "maximum users"
- parameter, it should be set to the number of users that
- you expect will be logging into this server. See the NOS
- User's Manual, page 6-17 for further info.
-
-
- PROBLEM: My application program won't print until I exit the
- program.
-
- REMEDY: Add the line: NET LPT TIMEOUT 10 to your network batch
- file or at the DOS prompt. See page 10-1 of your
- LANtastic NOS User's Manual for more information.
-
-
- PROBLEM: My application program now prints without exiting on
- the server, but it still won't print until I exit the
- program on the workstation.
-
- REMEDY: You must put the NET LPT TIMEOUT 10 on all your
- workstations and servers that are using a network
- printer.
-
-
- PROBLEM: I am able to print fine from all my workstations, but
- once I print one time from a workstation I can no
- longer print from the server where the printer is
- actually located. I get the error message, "Not ready
- error writing device lpt1, Abort, retry...."
-
- REMEDY: If you are using the server's printer as a shared
- resource you must log the server into itself and issue
- a NET USE LPTn command as you did on the workstations.
- This is a safety feature so that you will not get
- intermixed print jobs from the server printing locally
- and workstations printing through the spooler. See
- page 10-3 of your LANtastic NOS User's Manual for more
- information.
-
-
- PROBLEM: I have my banner page "enabled" but all I get is a
- blank page.
-
- REMEDY: The banner page prints to a width specified in "page
- width." The default page width is equal to 0. Set
- your page width equal to 80 for most printing.
-
-
- PROBLEM: I think I have set up all my NET USE LPT1
- \\HOST\@PRINTER statements correctly on my workstation
- and server but it still won't print.
-
- REMEDY: In NET_MGR under "server startup parameters" the option
- "despooling" should be "enabled." Once you have
- changed that or any other option in "server startup
- parameters" you will need to reboot your server.
-
-
- PROBLEM: I tried to delete a file from the print queue and it
- says "deleted" but it will not go away.
-
- REMEDY: You must "halt" the queue and then you may delete print
- jobs. Then select "start" to start the print queue
- again.
-
- PROBLEM: I receive the error message, "FATAL internal stack
- failure, system halted" periodically.
-
- REMEDY: You are using DOS 3.2. DOS 3.2 has errors in the
- internal stack handler. Use DOS 3.1 or 3.3.
-
-
-