[Intel Navigation Header]

    ProShare(TM) Software: Error Messages

    Contents:

    • CANNOT START AN OLE SERVER APPLICATION...
    • ERROR CREATING PALLETTE
    • GPF IN MODULE GDI.EXE
    • NETWARE INITIALIZATION FAILED - NETWARE ERROR.
    • NETBIOS NETWORK NAME IN USE - LANTASTIC 5.0
    • UNABLE TO PROCESS COMMAND: SERVER BUSY
    • CAN'T CONNECT
    • NETWARE SHELL 3.33A TO 3.26A: PROSHARE SOFTWARE TIMES OUT
    • GPF IN OLESVR.DLL
    • GPF IN MODULE S3645K.DRV - CUSTOMER REPORT
    • GPF IN MODULE VBA.DLL
    • UNABLE TO EXECUTE TASK: ...
    • SETUP UNABLE TO EXPAND FILE ISTBMPS.DLL
    • SOFT MODEM ERROR: UNABLE TO LOAD DSP FILE.
    • UNABLE TO LOAD SENHOOKS.DLL SENSOR WILL NOT LOAD
    • CANNOT START FILE TRANSFER. CHECK CONNECTION.
    • ERROR: TCP/IP INITIALIZATION FAILED
    • NETBIOS NETWORK NAME IN USE - LANMANAGER 3.0
    • COULD NOT ACCESS LOGIN INFORMATION FOR SERVER <SERVERNAME>
    • DEBUG MESSAGE #1...
    • CALL TO UNDEFINED DYNALINK
    
    

    CANNOT START AN OLE SERVER APPLICATION...

    
       Symptom
    
       You get the error "Cannot start an OLE server application.  The
    
       application may not be installed on your machine, or it may not be
    
       properly registered."
    
    
    
       Description
    
       The application that the OLE object originated from may not be properly
    
       registered under Windows.
    
    
    
       Solution
    
       Try pasting the same object into another application (i.e. Microsoft
    
       Write).  If the problem still occurs contact the manufacturer of the
    
       software that the OLE object originated from for information.
    
    
    
       Registration problems can usually be solved by reinstalling the
    
       application.
    
    
    
    

    ERROR CREATING PALLETTE

    
       If you get the error "Error Creating Pallette" while attempting to print
    
       from the ProShare software, try using a lower resolution Windows video
    
       driver.
    
    
    
       If the problem goes away, report the video card model and manufacturer
    
       as well as the the video driver that was used when the error occurred. 
    
       Include the driver file name and revision level.
    
    
    
       Note:  One customer reported this error while using an AMI Fast View VLB
    
       video card using the "True Color" video driver for that card.  Changing
    
       to the 64K or 256 color driver worked fine.
    
    
    
    

    GPF IN MODULE GDI.EXE

    
       If you receive the error, "GPF in module GDI.EXE" try using a lower
    
       resolution video driver for Windows, or a driver that supports fewer
    
       colors.
    
    
    
    

    NETWARE INITIALIZATION FAILED - NETWARE ERROR.

    
       If you get the error, "NetWare Initialization Failed - NetWare Error,"
    
       run the Communication Test that comes with the ProShare software. The
    
       Communication Test has a specific test for NetWare.
    
    
    
       Note:
    
    
    
            This error can occur if VIPX.386 is not listed on the Network= 
    
            line in the Windows SYSTEM.INI, [386Enh] section.
    
    
    
            This error can also occur if the IPX or IPXODI you're using are
    
            outdated.  If you're running IPX, it must be v3.10 or later, IPXODI
    
            must be v1.20 or later.
    
    
    
       Note: Typing IPX at the DOS prompt will usually return the version
    
       number of IPX that is loaded, you can also type NVER at the DOS prompt
    
       to get version information.  Customers can be directed to contact their
    
       Novell reseller to update the IPX.COM file.
    
    
    
    

    NETBIOS NETWORK NAME IN USE - LANTASTIC 5.0

    
       Since in this case the error "NetBIOS Network Name in Use" was received
    
       using Lantastic 5.0,  we ran a program called AI LAN BIOS and changed
    
       some existing settings. The existing values were:
    
    
    
       MaxNames=20
    
       MaxNCB=20
    
       MaxSessions=20
    
    
    
       The above values are not the defaults installed by Lantastic 5.0 . The
    
       defaults are:
    
    
    
       MaxNames=32
    
       MaxNCB=8
    
       MaxSessions=32
    
    
    
       After resetting these values to the defaults, the ProShare software
    
       worked fine.
    
    
    
    

    UNABLE TO PROCESS COMMAND: SERVER BUSY

    
       When attempting to open a OLE object in the ProShare software notebook,
    
       clicking the mouse on the OLE object too many times will cause the
    
       message, "Unable to Process Command: Server Busy" to appear.  To avoid
    
       this, click on the shared OLE object only once, then go to the Edit
    
       menu.  At the bottom of the Edit menu you should have the option to
    
       select the linked object.  In some applications you will be presented
    
       with additional options.
    
    
    
    

    CAN'T CONNECT

    
       If you're attempting to use ProShare software on two network
    
       workstations cabled directly to each other (no server) and you get an
    
       error about a failed connection the cable may not be wired correctly. 
    
       The transmit and receive wires need to be reversed much like a null
    
       modem serial cable.  The correct pin connections can be found in your
    
       network board's documentation.
    
    
    
       This occurs only when making a network connection between two
    
       workstations connected directly to each other.
    
    
    
    

    NETWARE SHELL 3.33A TO 3.26A: PROSHARE SOFTWARE TIMES OUT

    
       The following issue has been reported.
    
    
    
       Given the following Novell network Shell drivers on different systems:
    
    
    
       SYSTEM A  has  Shell v3.33a
    
       SYSTEM B  has  Shell v3.26a
    
       SYSTEM C  has  Shell v3.10a
    
    
    
       The issue arises when System A attempts a network connection to System
    
       B.  The response on A's screen is "Attempting network connection", then
    
       the connection times out, and the message is "NetWare Error, Unable to
    
       complete network connection...."
    
    
    
       This may be a backward compatibility issue w/Shell 3.33a to 3.26a.
    
    
    
       When System B attempts a network connection to System A, no problem.
    
    
    
       When System A attempts a network connection to System C, no problem. 
    
       And  likewise System B to System C is no problem.
    
    
    
       System A can complete a network connection to other systems that are 
    
       running Shell v3.33a without any problem.
    
    
    
    

    GPF IN OLESVR.DLL

    
       If you run PCTools as your Windows shell, and you try to run a
    
       WordPerfect 6.0 OLE object from the ProShare software notebook, you will
    
       get a "General Protection Fault in module OLESVR.DLL" if  WordPerfect is
    
       not open.  This does not occur if WordPerfect is already open.  This is
    
       not specific to the ProShare software.  
    
    
    
       With PCTools as the shell, the same problem occurs when double clicking
    
       on a WordPerfect OLE object in Microsoft Word.
    
    
    
       To avoid this, keep WordPerfect running in the background while
    
       attempting the OLE.
    
    
    
    

    GPF IN MODULE S3645K.DRV - CUSTOMER REPORT

    
       Customer Report:
    
       When using the 640x480x256 color driver for a 512K Quadtel S3 VGA card a
    
       customer reported an application error when clicking on any ProShare
    
       software menu item.  If she chooses the Ignore button on the error
    
       message she gets the message "PSDATA caused a GPF in module S3645K.DRV
    
       at 0003:E089".  She is using v1.32 of DELL's video drivers for her
    
       chipset.  This is the latest version.  She does not get this message
    
       when she switches to the Quadtel 16 color video driver. 
    
    
    
       The troubleshooting work-around is to switch to a driver provided by
    
       Microsoft.
    
    
    
    

    GPF IN MODULE VBA.DLL

    
       Symptom
    
       Importing an Excel 5.0 file causes a General Protection Fault (GPF) in
    
       module VBA.DLL.
    
    
    
       Description
    
       Intel is still investigating the problem, workarounds are noted for now.
    
        This information will be updated as new information becomes available.
    
    
    
       Solution
    
    
    
       One way to work around this problem is to open Excel and print the
    
       document to the PSDATA capture driver instead of using the File Import
    
       feature of the ProShare software.  Both processes provide the same
    
       results.
    
    
    
       You can also work around this problem by having Excel open before
    
       executing File Import from within the ProShare software, but you will
    
       need to switch to Excel to press the OK button on the print dialog
    
       before the document will be *printed* to the notebook.
    
    
    
       Note:  After the General Protection Fault occurs, the file is still
    
       printed to the ProShare notebook, however, your available Windows
    
       resources will be reduced by a small amount.  To free up the resources
    
       again you will need to restart Windows.
    
    
    
    

    UNABLE TO EXECUTE TASK: ...

    
       If you get the message: "Unable to Execute Task: 
    
       C:\TEMP\~PROxxxx.TMP\SETMAIN.EXE" try the following (in the order they
    
       are listed):
    
    
    
         1. Close all programs and exit Windows.
    
    
    
         2. Copy LZEXPAND.DL_ from Windows 3.1 disk #2 into the \WINDOWS\SYSTEM
    
            directory.
    
    
    
         3. From the \WINDOWS\SYSTEM directory type:  EXPAND LZEXPAND.DL_
    
            LZEXPAND.DLL
    
    
    
         4. Restart Windows and reinstall ProShare software.
    
    
    
       Note: You must have DOS 5.0 or higher to do this.
    
    
    
    

    SETUP UNABLE TO EXPAND FILE ISTBMPS.DLL

    
       Symptom
    
       New install and gets error message right after trying to run A:SETUP.
    
       *SETUP unable to  expand file ISTBMPS.DLL.  Make sure \TEMP directory
    
       has 500k free and run SETUP again."
    
    
    
       Description
    
       Incorrect version of LZEXPAND.DLL Dated 9-13-93   
    
    
    
       Solution
    
       See solution for "Unable to Execute Task... SETMAIN.EXE".
    
    
    
    

    SOFT MODEM ERROR: UNABLE TO LOAD DSP FILE.

    
       Customer Report:  Problems with Cardinal modem.
    
    
    
       Symptom
    
       ERROR when trying to open application.  D:\DMODEM\DATA144C.CAR
    
    
    
       Solution
    
       The Cardinal modem uses a DSP manager that tells the modem which
    
       application is going to use the modem and downloads the init string to
    
    
    
       the modem.  The same error may occur trying to run the communications
    
       test for the modem.  The manual has a LEARN function that identifies
    
       what an application is trying to initialize the modem to, and saves it
    
       for future use when the application is run.
    
    
    
    

    UNABLE TO LOAD SENHOOKS.DLL SENSOR WILL NOT LOAD

    
       The error message "Unable to load SENHOOKS.DLL sensor will not load"
    
       occurs when the SENHOOKS.DLL file is missing or corrupted.  Another
    
       cause can be  that the ICOMM.INI and/or the PSDATA.INI files are not
    
       correct.
    
    
    
       If you have two installations, or installed to a different directory,
    
       the INI files may not have been updated properly.  In this case, the
    
       program may simply be looking in the wrong place for SENHOOKS.DLL.
    
    
    
       To correct the problem, uninstall and reinstall ProShare software, then
    
       check that the HomeDir= and HelpDir= entries under the [PROSHARE]
    
       section of ICOMM.INI point to the installation directory.
    
    
    
    

    CANNOT START FILE TRANSFER. CHECK CONNECTION.

    
       If you try to transfer a file that's currently open (for example, a .DLL
    
       that's running under Windows, an .EXE file, or a document file in Word
    
       6.0 or spreadsheet in Excel 5.0) the file transfer will fail.  You will
    
       receive the error message "Cannot start file transfer.  Check
    
       connection".  The problem isn't with the connection, but with the open
    
       file.  The solution is to close the open file and try again.  If you
    
       have multiple files queued up, you'll get the error and none of the
    
       files will be sent.  This is only known to occur with Word 6.0 and Excel
    
       5.0.
    
    
    
       The transfer status will show that the remaining files that should have
    
       been transferred are in the queue.  They will not be transferred, but
    
       can be aborted.
    
    
    
    

    ERROR: TCP/IP INITIALIZATION FAILED

    
       Symptom
    
       Error:  *TCP/IP Initialization Failed* when invoking the ProShare
    
       software using Novell LAN Workplace TCP/IP.
    
    
    
       Description 
    
       1.  The file NOVASYNC.EXE is missing from the Novell Lan Workplace
    
       software directory.
    
    
    
       2.  There is not enough low memory (below 640K) for TCP/IP to function
    
       correctly.
    
    
    
       Solution 1:
    
       Run the TCP/IP tests in the Communications Test program that comes with
    
       the ProShare software.  The TCP/IP Listen Test will fail if you do not
    
       have the file NOVASYNC.EXE in your LAN Workplace directory.  If you do
    
       not have this file, you can obtain a copy from your Novell software
    
       distributor.
    
    
    
       Solution 2:
    
       While using the ProShare software, try disabling the other transport
    
       options such as modem, NetWare or NetBIOS if they are active, then try
    
       enabling TCP/IP. 
    
    
    
       Solution 2b:
    
       If the problem persists, free up more low DOS memory by unloading
    
       drivers and TSRs that load before Windows is started.
    
    
    
       Note: During Intel's testing problems were seen with 524K of free memory
    
       available.  With 536K, the problems went away.  The exact amount
    
       required is unknown, but if the system has 540K or less of free low-DOS
    
       memory, then a memory problem should be investigated.  It is likely that
    
       this number will vary depending on the manufacturing of the TCP/IP
    
       transport being used.
    
    
    
    

    NETBIOS NETWORK NAME IN USE - LANMANAGER 3.0

    
       Symptom
    
       You get the error *NetBIOS Network Name In Use* when invoking the
    
       ProShare software using IBM LanManager v3.0 w/ NetBIOS.  
    
    
    
       Description
    
       There were not enough NetBIOS resources available.
    
    
    
       Solution
    
       This error almost always indicates a need to increase specific NetBIOS
    
       resources, specifically NetBIOS commands and sessions.  For IBM
    
       LanManager 3.0, increase the NetBIOS commands and sessions parameters by
    
       editing the CONFIG.SYS file.  For IBM LanManager 3.0 there is a line
    
       that reads Device=DXMT0MOD.SYS (zero after *T* and letter O in *MOD*). 
    
       Adding (or increasing) C=20 S=20  resolves the problem.
    
    
    
    

    COULD NOT ACCESS LOGIN INFORMATION FOR SERVER <SERVERNAME>

    
       Symptom
    
       Error: *Could not access login information for server <servername>.* 
    
    
    
       Description
    
       An attempt was made to access the bindery information for a server that
    
       you are not logged in to.  The problem occurs when you select the Show
    
       All Servers check box in the NetWare search of the ProShare software. 
    
       In this case the NetWare search will find additional servers that you
    
       are not logged in to.  You will not be able to access the bindery tables
    
       of these servers that you are not logged in to resulting in the error
    
       above.  By default, the NetWare Search feature will display all servers
    
       that you are currently logged in to.  In general, when you are logged in
    
       to a server you are granted access to the server*s bindery containing
    
       all the names and network addresses of everyone who is currently logged
    
       in to that server.
    
    
    
       Solution
    
       Do not use the Show All Servers check box when searching for other
    
       ProShare software users to connect with.  If you cannot find your
    
       colleague by using the NetWare search, ask them directly for their
    
    
    
       NetWare address.  Your NetWare address can be displayed by choosing
    
       Conference, Setup, while in the ProShare application.
    
    
    
    

    DEBUG MESSAGE #1...

    
       Symptom
    
       Error: "Debug message #1 additional info 12704 note video driver and
    
       resolution and call tech support."
    
    
    
       Description
    
       There is an older version of the file WINMEM32.DLL loading.  The
    
       ProShare software installs the file WINMEM32.DLL into the WINDOWS
    
       directory, but another application may have already loaded an older
    
       version of  WINMEM32.DLL into memory.
    
    
    
       Solution
    
       Rename or delete all other copies of the file WINMEM32.DLL from the hard
    
       disk except for the one in the WINDOWS directory.  Restart Windows.
    
    
    
       The file date of the WINMEM32.DLL file should be 8/26/93.  If necessary,
    
       this file can be expanded from disk #3 of the Premier Edition software
    
       or the Video System 200 1.6 software diskettes using the DOS EXPAND
    
       utility.  Place the file into the WINDOWS directory so it can be shared
    
       by other apps that may need it.
    
    
    
       Note: A product called MaxMate by Visioneer can have an older
    
       WINMEM32.DLL file that can cause the Debug Message #1 error.
    
    
    
    

    CALL TO UNDEFINED DYNALINK

    
       Symptom
    
       Error: "Call to undefined dynalink" when starting the ProShare software
    
       or when selecting Conference, Setup.
    
    
    
       Description
    
       A partially installed TCP/IP stack.  The customer was not using any
    
       network software but a file called WINSOCK.DLL existed in the customer's
    
       WINDOWS directory.  TCP/IP vendors that support TCP/IP under Windows
    
       will provide a WINSOCK.DLL file with their software.
    
    
    
       The ProShare software checks to see if TCP/IP support exists under
    
       Windows when choosing Conference, Setup.  In this case it appears that
    
       some Windows drivers for TCP/IP support existed from a previous
    
       installation of some unkown TCP/IP stack, but the DOS TSR(s) necessary
    
       for the TCP/IP stack had been deleted.  
    
    
    
       Solution
    
       Rename the file WINSOCK.DLL and restart Windows.
    
    

    Trademark information