VLM - "Cannot Transfer Control" And "Error 5"

DocumentID: 626129
Revision Date: 29-Feb-96 1:41:33 PM

The information in this document applies to:
WordPerfect® 6.0 for DOS

Problem

Solutions: Problem 1: Running VLM 1.10 and WP 6.0 from a workstation without a local drive causes a "Cannot Transfer Control" error when the user tries to shell out to DOS or run Grammatik a second time. This happens because the .BSW files are left open (Read-Only) when the user switches back into WP 6.0. Answer 1: Use the /DA startup option to prevent this problem. The /DA option will not affect the ability to shell out to DOS or to run Grammatik. How/Why 1: The /DA option disables the DOS task switcher API support, which makes Launcher look like a "multi-tasking" program to the VLM drivers. The .BSW files are left open and Read-Only from the first attempt to shell out. Using the /DA startup option should eliminate the problem when using VLMs by disabling Launcher's DOS task switcher API support. Problem 2: The message "Error 5 - Reading Overlay" displayed when a user printed a calendar twice, launching WordPerfect 6.0 for DOS. The error "Can't Transfer Control" would then display. The calendar printed fine the first time; however, the error messages displayed when the user tried to print the same calendar a second time. Answer 2: The user removed the VLM drivers and the problem no longer occurred. Using the /DA startup option should also correct this problem. How/Why 2: The "Error 5" message is equivalent to "Access Denied." Even though this user had sufficient rights in the temporary directory on the network, something was conflicting with the temporary file deletion process. The actual temp file was the .BSW file. This is a known problem with the VLM drivers. The .BSW file is created and given a Read-Only attribute, but when the user tries to change the attribute back to normal to delete the .BSW file, the "Error 5" and/or "Access Denied" messages occur. Using older network drivers (i.e., NETX) eliminated the problem. Novell is aware of this problem and is working on a solution. Problem 3: On a Novell network with VLMs loaded, the error "Can't Release Control" displays when a customer tries to swap from WordPerfect 6.0 for DOS to Office 4.0. Answer 3: To correct the problem, the customer re-optimized the memory manager. The customer is now using IPX and NETX instead of the VLMs for Novell 4.0. Using the /DA startup option may also correct this problem. Problem 4: On Novell Network version 3.12 with VLM drivers loading, exiting a DOS application and the Shell version 4.0 the message "Type Exit to Return to Application" appeared with the DOS prompt. When entering the shell and the same DOS application and exiting the DOS application and Shell, the system locked. Answer 4: Starting the Shell with the /DA startup option resolves this problem. The /DA option disables the DOS task switcher API support, which makes Launcher look like a "multi-tasking" program to the VLM drivers. The .BSW files are left open and Read-Only from the first attempt to shell out. Using the /DA startup option should eliminate the problem when using VLMs by disabling Launcher's DOS task switcher API support.

Answer:

Details:

Product specifications, packaging, technical support and information (*Specifications*) refer to theUnited States retail English version only. Specifications for other versions may vary. All Specifications, claims, features, representations, and/or comparisons provided are correct to the best of our knowledge of the date of publication, but are subject to change without notice.OUR MAXIMUM AGGREGATE LIABILITY TO YOU AND THAT OF OUR DEALERS AND SUPPLIERS IS LIMITED. IT SHALL NOTEXCEED THE AMOUNT YOU PAID TO ACCESS THE INFORMATION. SEE LEGAL DISCLAIMER.