Bugfixes BW version 7.1c.04.147 =============================== MaintCorelli: # 13785 (BDNT7595): BW5: Add on to project BDNT7227 Date: Tue, 16 Apr 2002 10:16:37 +0200 Created on: MaintCorelli Type: bugfix Problem Description (Customer terms) Shell out from Baan, open vi, insert 1 , vi inserts 2 's. Workaround First put the focus on the window of the (k)shell, type another character than TAB, and then type TAB. Test Procedure 1. Login Baan, running on an unix server, using BW 2. File: Run Program, type in ksh, and turn on "External Program", press OK 3. Now ottstpvtemul is started, start vi editor, in insert mode: press one time the tab key. now only 1 tab should be inserted. Affected Executables BW.exe Motive source Scopus Defect 206208 ------------------------------------------------------------------------------ MaintCorelli: # 13649 (BDNT7313): Improvements of Uninstall BW Client Date: Wed, 27 Mar 2002 08:50:47 +0100 Created on: MaintCorelli Type: bugfix Problem Description (Customer terms) After uninstalling the BW client not everything is removed. Workaround Remove manually the components left after uninstall. Test Procedure test scenario 1: Install the BW client on a clean windows os. (no BW installed before) UnInstall this BW client, and check that the following components are removed: - Program Folder referring to this environment - Files in %SystemRoot%\baan (Only the file %SystemRoot%\baan\uninst\_isdel.exe is left behind) - Registry Entries in HKLM\software\baan test scenario 2: Install the BW client. Install a second BW client, using the same Program Folder name as the previous (e.g. Baan ERP) Uninstall the first BW client installed Now, the Program Folder "Baan ERP" should not be removed, as it is still in use by the environment left. Also directory and files in %SystemRoot%\baan should not be removed. And only the registry settings referring to this environment should be removed (HKLM\SOFTWARE\Baan\). Affected Executables setup.exe setup.ins unsetup.ins baanmsg.dll Scopus defectnumber(s) Scopus casenumber(s) Priority (e.g. 10) 206494 921814 20 647648 -------------------------------------------------------------------------------- MaintCorelli: # 13561 (BDNT7337): BSE_TMP found not accessable on Windows95, 98 or Me Date: Mon, 18 Mar 2002 08:46:30 +0100 Created on: MaintBaanIVc Type: bugfix Problem Description (Customer terms) The following message is logged on Windows95, 98 or Me: Log_mesg: c:\program files\baan\tmp: not accessable; defaulting to TEMP directory Althought the directory c:\program files\baan\tmp is accessable. Workaround No workaround Test Procedure >From a Windows 96 machine: Using BW, log in Baan. Print something to a Windows Printer, having Preview mode switched on. Check your BW.log, or BWPRINT.log file: no message, as described in Problem Desc. should be logged. Also the .bpf file should be created in the BSE_TMP directoy, and not in the TEMP directory. Affected Executables bw.exe, bwprint.exe, etc. Scopus defectnumber(s) Scopus casenumber(s) Priority (e.g. 10) 123005 666647 20 -------------------------------------------------------------------------------- MaintCorelli: # 13482 (BDNT7227): BW5: One tab key press is interpreted as 2 tab key presses. Date: Thu, 7 Mar 2002 12:09:21 +0100 Created on: MaintCorelli Type: bugfix Problem Description (Customer terms) Shell out from Baan, open vi, insert 1 , vi inserts 2 's. Workaround no workaround Test Procedure 1. Login Baan, running on an unix server, using BW 2. File: Run Program, type in ksh, and turn on "External Program", press OK 3. Now ottstpvtemul is started, start vi editor, in insert mode: press one time the tab key. now only 1 tab should be inserted. Affected Executables BW.exe Scopus defectnumber(s) Scopus casenumber(s) Priority (e.g. 10) 206208 934719 30 -------------------------------------------------------------------------------- MaintCorelli: # 13325 (BDNT7118): Fixed possible bug in including typelib in resource file Date: Fri, 15 Feb 2002 15:25:19 +0100 Created on: MaintCorelli Type: bugfix Problem Description (Customer terms) Fixed possible mistake in compiling BWC.dll Problem Description (Technical terms) Visual Studio 'optized' some defines away, if a resource file (bwc.rc) is modified, causing bwc.dll not to operate with visual basic anymore (since the typelib was removed from the dll). Affected Executables bwc.dll ----------------------------------------------------------------------------------------------------------