|
||||||||||||||
Connection Problem Links:LT Winmodem 56K users: You may find some useful inforamtion about your modem and 56K connections at 808hi.com/56k/x2-lucent.htm#firmwareNOTE for other 56K users: You may find some useful inforamtion about your modem and 56K connections at one of the following locations: 56k.com Ask Mr. Modem Modem Initialization Strings - Site 1 Modem Initialization Strings - Site 2 PC Modem Initialization Strings Common Error Messages:Dial-Up Networking Refuses to Remember Passwords:There are several posiblilities you can try, but there is no guarentee that these will fix the problem. These are taken directly from Microsoft's Tech Support page.Solution #1: Double-click on the Network icon in Control Panel, and choose the Identification tab. Although the Workgroup and Computer Description have no use in Dial-up Networking, the Computer Name must be your login for your ISP (Internet Service Provider). Make any necessary changes, and press OK when finished. You'll have to restart Windows, but once you're back in, try again. Double-click on your connection icon. This time, your correct login will be in the login field, and you should be allowed to type in your password. Remember to turn on Save Password if it's not grayed out. Note: If you don't have an Identification tab, see Installing and Coping with Dial-Up Networking to make sure Dial-Up Networking is installed correctly. Solution #2: Try re-creating the connection by opening up the Dial-Up Networking Window and double-clicking on Add New Connection. Solution #3: Check out Microsoft's technical note regarding the disabled Save Password option, as well as Microsoft's technical note describing how the password isn't saved. Solution #4: Double-click on the Passwords icon in Control Panel, and click on the User Profiles tab. Select Users can customize their preferences..., choose the desired options below, and click OK. Restart Windows95 - when asked for a username and password, leave the password field blank. When asked if Windows95 should remember settings for this user, answer Yes. Solution #5: Occasionally, the Password List (pwl) files get corrupted - try deleting (or renaming) all *.PWL files in your Windows directory. Solution #6: Refer to Installing and Coping with Dial-Up Networking to make sure Dial-Up Networking and all the necessary components are installed correctly. Note: try adding the Client For Microsoft Networks into the network section of Control Panel if it's not already there. Solution #7: If you have more than one connection, and the password checkbox is turned off for at least one, none of them will work. Solution #8 (if the password box is disabled): Run the Registry Editor (REGEDIT.EXE). Open HKEY_LOCAL_MACHINE\ SOFTWARE\ Microsoft\ Windows\ CurrentVersion\ Network\ Real Mode Net. If you see autologon (on the right side) with a value of 00, double-click on it, and replace the value with 01 00 00 00 00. You'll have to restart Windows for this change to take effect. Note: Some users have reported this behavior only after installing Microsoft's Service Pack 1, which is incidentally supposed to alleviate this problem. Common Error Messages:General Protection Fault Error:Solution :1. Close the error message. (in Windows 95 click on 'Details') 2. Write down the entire General Protection Fault message. 3. Note exactly what you were doing when you got the error message. 4. Quit all open applications. 5. Quit Windows. 6. Reboot the computer. 7. Restart Windows and the program you were running. 8. Try to duplicate the error. 9. If the General Protection Fault error returns and the rest of this document does not help you solve the problem, then call our Technical Support for assistance. Note: Providing the above information will help immensely in the troubleshooting of your problem. A General Protection Fault (GPF) in Windows 3.1 can occur when one program in memory attempts to access another area of memory not assigned to it. In other words, something running within the Windows environment has made a call to a location in memory that it did not have access to, potentially overwriting and corrupting other program code in that area of memory. When Windows detects this, it closes down the offending program and announces that a GPF has occurred. Another situation where a GPF may occur involves the passing of parameters between applications and the Windows environment. Invalid parameters affect the performance of Windows and its applications by forcing an invalid instruction. This is usually the result of an application's internal program code incorrectly passing specific data that could not be correctly interpreted for Windows or another Windows application. The result is often a GPF. Note: Perform the steps below to resolve the error (given in order of the most likely solutions, down to those that may help solve the problem). Before you start make sure that you followed the directions for installation in the README.TXT file. Have you tried uninstalling and reinstalling Navigator? Have you tried shutting down all other applications before running Navigator? During the installation were any other programs running in your task list (ctrl-alt-del in Windows 95/98/NT or ctrl-esc in Windows 3.x)? 1. Using a program in Windows called SYSEDIT.EXE, you can edit four important system files. These are the AUTOEXEC.BAT, CONFIG.SYS, WIN.INI, and the SYSTEM.INI. Choose the 'File' menu and select 'Run' to start SYSEDIT.EXE. You may want to unload any extra programs that may be loading when you start your computer. The C:\CONFIG.SYS and/or C:\AUTOEXEC.BAT could contain devices or programs that load and run in the background until they are needed (like a screen saver, office toolbar, or virus detector, for example). At the beginning of your WIN.INI file check the 'Load=' and 'Run=' lines if you have one or both of them. You can put a "REM" comment in front any line that you feel is not necessary, one at a time, and then try running Navigator after restarting your computer. This trial and error process will help to find the problem that is causing your error. When you have fixed your errors, you can always remove the "REM" comments by using SYSEDIT again. Also check your Startup group in Windows for programs that load when windows starts. In your AUTOEXEC.BAT: Verify that SET TEMP=C:\TEMP (You only need this line in Windows 3.x because Windows 95 automatically sets C:\WINDOWS\TEMP; check this variable by running SET at the dos prompt; make sure the directory is empty; do not use the 'SET TMP=' environment variable.) Make certain that WINDOWS is the first directory mentioned in your PATH statement. (Navigator will use the PATH when it searches for the Winsock.dll file just before connecting. Search for Winsock.dll in our knowledge base for more information. The DialUp Networking Winsock.dll file is 42 kilobytes, the Netscape Shiva Winsock.dll file is 30,516 bytes, and for Remote Access on NT it is 2,990 bytes.) Increase or add the following statements in your CONFIG.SYS file: FILES=99 BUFFERS=40 (or 10,0 if you run Smartdrive in the AUTOEXEC.BAT) STACKS=9,256Add the following lines in Windows 3.x only. DEVICE=C:\DOS\HIMEM.SYS /M:1 DEVICE=C:\DOS\EMM386.EXE NOEMS (do not use HIGHSCAN) SHELL=C:\DOS\COMMAND.COM c:\DOS /e:2048 /p2. Perform CHKDSK on your hard drive to check for corrupt files. To do this, exit windows. Go to an MS DOS prompt. Type: CHKDSK /F . If DOS reports corrupted (cross links, etc. ) files, select N. Afterwards, try running SCANDISK (do not check 'automatically fix errors') and DEFRAG.EXE from Windows. EDITOR'S NOTE: Use caution when running DEFRAG.EXE and make a backup of your important files before beginning. Loss of power to the PC while file de-fragmentation is in progress can result in complete loss of hard drive contents. 3. Check your settings for Virtual Memory. Open the '386_enh' control panel in Windows 3.x and click the button that says Virtual Memory. In Windows 95 just right mouse click on the 'My Computer' icon on your desktop and choose 'Properties'. You should have it set to permanent and between 2-3 times the size of your RAM. In Windows 95 it is handled automatically, so you will not need to change it. In Windows 3.x just reboot after you make your changes and close the control panel. 4. In Windows 3.x, try starting Windows from the C:\> prompt with the command: WIN /3 /D:X. This command will exclude certain memory mapping addresses if you are using EMM386. In Windows 95 you could try booting the computer in Safe Mode by hitting the F8 key when your computer says "Starting Windows 95". 5. In Windows 3.x verify the following in the SYSTEM.INI. COMM.DRV=COMM.DRVIn the '[ 386_enh ]' section, the following should also exist. DEVICE=*VCD On a laptop, be careful about the changes that you make to the PCMCIA modem related drivers. Some PCMCIA modem cards replace some of the system drivers with their own and changing them back to what is suggested above could cause your modem to stop working. The drivers suggested above come with windows and should work fine with any modem that is Windows compatible. In Windows 95 you will not have a problem. 6. Check your conventional memory, it should be greater that 500KB from within windows. Check the system resources by choosing Help >> About Program Manager in Windows 3.x or right click on 'My Computer' and choose 'Properties' in Windows 95/98. The system resources should be greater that 80% for troubleshooting purposes. Empty the recycle bin if you have one. Search and destroy all temporary files on your system by using '*.tmp' in your search query. Empty the Netscape memory cache and disk cache by using the Preferences window in Navigator. Check the system (PCs) time setting. EDITOR'S NOTE: Technical Support has found that 580 KB of "conventional memory" is typically required to prevent "Unable to create network socket" error messages. See also: 960923-7 (Netscape Knowledge Base) 7. After all the steps above, reinstall the software that caused the error message. If all of these steps do not prevent the error message, the program may not be capable of running in your current Windows configuration. Contact whomever you purchased Navigator from and they may have an updated version or patch available. If you can, check our website for a later version of your Navigator. Other causes of a General Protection Faults in Navigator: If you are getting General Protection Faults in Navigator when trying to print, you may need to update your printer driver. You can locate the latest drivers at your printer manufacturers web site. Check to see if you have Corel OfficeSuite DAD Bar loading at startup (or if it's in the Tasklist at all). Turn the bar off and print. This should resolve the problem. In the older Navigator 3.x, the Live3d plugin has 3d engine trouble with 3 older graphics cards and requires minor configuration changes. These video cards are ATI Graphics Ultra Pro Mach 32, ATI Graphics Ultra Pro Mach 64, and Matrox MGA. The latest drivers for these cards should fix the problem. Of course, Communicator now uses Cosmo instead of Live3d. If you are running a Logitech mouse you may need to get the drivers updated. Go to the logitech web site on the internet. Ref. : http://help.netscape.com Ref. : Netscape Knowledge Base article 970702-6 (Color, BOLD and "EDITOR'S NOTE " added for emphasis.) Common Error Messages: |
||||||||||||||
|