List of Bugfixes in BW version B40c.061

BaanIVc: # 10142 (VHNT4493): BW: activate message window when connection to server is lost

From: Source Manager 
Date: Mon, 9 Oct 2000 14:19:32 +0200 (METDST)

                                                                             
Release: BaanIVc                                             Date: 2000/10/09

Script:      MergeProject
Project:     VHNT4493
Created on:  BaanIVc
Type:        bugfix

Problem:
Problem Description (Customer terms)
When connection to server is lost, the message window should pop up, but is doesn't.

Problem Description (Technical terms)
The message window should be mapped and raised.

Workaround
None

Solution
sockdata.cpp:
add log_window_map_raised when connection is lost


Test Procedure
Connect to a bshell and kill the bshell

Affected Executables
bw.exe


Scopus defectnumber(s)	Scopus casenumber(s)	Priority (e.g. 10)

TCS remark id(s)	Priority (e.g. not workable)

Comments




BaanIVc: # 9912 (VHNT4409): Solved bug in ds layer!

From: Source Manager 
Date: Wed, 20 Sep 2000 14:30:22 +0200 (METDST)

                                                                             
Release: BaanIVc                                             Date: 2000/09/20

Script:      MergeProject
Project:     VHNT4409
Created on:  BaanIVc
Type:        bugfix

Problem:
Problem Description (Customer terms)
Ds layer dumped core

Problem Description (Technical terms)

Workaround

Solution
Solved core dump in DS layer.


Test Procedure

Code-change Type
bugfix

Affected Executables
BW, BA, BX, Bshell

Scopus defectnumber(s)	Scopus casenumber(s)	Priority (e.g. 10)



BaanIVc: # 10379 (VHNT4695): BW: improve AppStart string expansion

From: Source Manager 
Date: Wed, 8 Nov 2000 17:06:33 +0100 (MET)

                                                                             
Release: BaanIVc                                             Date: 2000/11/08

Script:      MergeProject
Project:     VHNT4695
Created on:  BaanIVc
Type:        bugfix

Problem:
Problem Description (Customer terms)
BW crashes when supplying very long strings to AppStart

Problem Description (Technical terms)
The internal buffer used by AppStart is only 260 bytes long.

Workaround
Use a dynamically allocated buffer of a better size.

Test Procedure
session ttaad5511m000

Affected Executables
BW.exe

Scopus defectnumber(s)	Scopus casenumber(s)	Priority (e.g. 10)

TCS remark id(s)	Priority (e.g. not workable)



BaanIVc: # 10270 (VHNT4625): BW: Option Dialog Logfile in \log

From: Source Manager 
Date: Wed, 25 Oct 2000 09:58:40 +0200 (METDST)

                                                                             
Release: BaanIVc                                             Date: 2000/10/25

Script:      MergeProject
Project:     VHNT4625
Created on:  BaanIVc
Type:        bugfix

Problem:
Problem Description (Customer terms)
log file produced by Option Dialog does not appear in correct directory

Problem Description (Technical terms)
bw.log is created in current directory instead of $BSE/log

Workaround
none

Solution
bwerror.c:
use $BSE\log\bwtrace.log
instead of $CWD\bw.log

Test Procedure
use Option Dialog and save messages to file

Affected Executables
bw.exe

Scopus defectnumber(s)	Scopus casenumber(s)	Priority (e.g. 10)



BaanIVc: # 10757 (BDNT4953): BW4: m_help.log file produced when using default bwc file

From: Source Manager 
Date: Fri, 5 Jan 2001 15:06:47 +0100

                                                                             
Release: BaanIVc                                             Date: 2001/01/05

Script:      MergeProject
Project:     BDNT4953
Created on:  BaanIVc
Type:        bugfix

Problem:
Problem Description (Customer terms)
bw creates $BSE/log/m_help.log when exiting.
it only happens when bw was started via the default bwc file

Workaround
don't use the default bwc file.
remove m_help.log when it becomes too big

Test Procedure
start bw via the default bwc file and then exit

Affected Executables
bw.exe

Scopus defectnumber(s)	Scopus casenumber(s)	Priority (e.g. 10)
106245                  566560,575341,878979    30




BaanIVc: # 10514 (VHNT4788): BW4: SetDIBits fails

From: Source Manager 
Date: Fri, 24 Nov 2000 17:01:15 +0100

                                                                             
Release: BaanIVc                                             Date: 2000/11/24

Script:      MergeProject
Project:     VHNT4788
Created on:  BaanIVc
Type:        bugfix

Problem:
Problem Description (Customer terms)
Message window with "SetDIBits failed, etc..." pops up for each started session

Workaround
none

Test Procedure
Start a session from the menu browser.
The baan logo should appear for a short time and nothing should be logged in the message window.

Affected Executables
bw.exe

Scopus defectnumber(s)	Scopus casenumber(s)	Priority (e.g. 10)



BaanIVc: # 9936 (VHNT4296): Introduce BW_MAX_RETRIES variable.

From: Source Manager 
Date: Thu, 21 Sep 2000 14:06:55 +0200 (METDST)

                                                                             
Release: BaanIVc                                             Date: 2000/09/21

Script:      MergeProject
Project:     VHNT4296
Created on:  BaanIVc
Type:        bugfix

Problem:
Problem Description (Customer terms)
In case of  connections via wide area networks (telephone lines, modems and so on there is a timeout in BW
that produces a popup window with the message "connection with server lost".

Problem Description (Technical terms)
In case of a socket error "WSAWOULDBLOCK" BW goes into a retry mechanism, waiting for the rest of the data
to be received. Firstly a number of immediate retries (RETRIES_NOWAIT) are done, and after that a number of
delayed retries (MAX_RETRIES). The delay is about 55ms (RETRY_TIME).
Sometimes the delay MAX_RETRIES*RETRY_TIME seems to be too short. Therefore the MAX_RETRIES (which is 600) is 
made adjustable by setting the environment variable BW_MAX_RETRIES. In case BW_MAX_RETRIES is set, MAX_RETRIES
becomes the value of BW_MAX_RETRIES.

So, in case BW_MAX_RETRIES is set to 1000, maximum 1000 delayed retries will be done in stead of 600.
If BW_MAX_RETRIES is set bigger then 6000, MAX_RETRIES will set to the default, 600. 
If BW_MAX_RETRIES is set smaller then 600, MAX_RETRIES will also set to the default of 600.

Furthermore tcp parameters TcpMaxConnectRetransmissions and TcpMaxDataRetransmissions can be adjusted to
avoid connection timeouts.

Workaround
no workaround

Affected Executables
bw.exe

Scopus defectnumber(s)		Scopus casenumber(s)		Priority (e.g. 10)
101302			857083			30



BaanIVc: # 10834 (BDNT4967): After save bwc file not displayed in BECS on Windows2000

From: Source Manager 
Date: Tue, 16 Jan 2001 11:45:26 +0100

                                                                             
Release: BaanIVc                                             Date: 2001/01/16

Script:      MergeProject
Project:     BDNT4967
Created on:  BaanIVc
Type:        bugfix

Problem:
Problem Description (Customer terms)
After Save or Save As the Baan Windows Configuration file (bwc file) is not displayed in BECS.
Doing a refresh does not help either.

Problem Description (Technical terms)
Default the bwc file is saved at the desktop. Physically the file is save in directory %USERPROFILE%\Desktop.
It should be saved in the %BSE%\lib\user directory.

Workaround
Use Save As method, and select manually directory %BSE%\lib\user to save the bwc file.

Test Procedure
Install on a fresh Windows2000 system for the first time the client binaries.
Start BECS and create a new bwc file.
Press Save and specify a name.
After saving press Refresh button in BECS, and bwc file should be displayed by BECS.

Affected Executables
becs.exe

Scopus defectnumber(s)	Scopus casenumber(s)	Priority (e.g. 10)
106967			-			20