Bugfixes BW version 6.2a.03.03.123


MergeProject: Grieg: # 8318 (VHNT3235): Add -giveaway command line option to BW.

Date: Thu, 9 Mar 2000 10:26:11 +0100 (MET)

                                                                             
Release: Grieg                                               Date: 2000/03/09

Script:      MergeProject
Project:     VHNT3235
Created on:  Verdi
Type:        bugfix

Problem:
Problem Description (Customer terms)
A time ago was a new functionality introduced in BW which when a bwc file is created the the username is encrypted within the password in password64 parameter. User can only run if their login name matchs with the user name which is encrypted with the password.

If that is not the case, the password field becomes empty and users should fill in the password when loging on the Baan application.

This new functionality have created the following problem. The Baan Job Daemon service runs under LocalSystem account and the jobd.bwc file is configured beforehand (evt. via de Baan NT Manager) and the password is saved under an account other than the LocalSystem account. When the jobd.bwc is executed by the the Baan Job Daemon Service (jobd.exe) on Windows NT, the password field should be filled by user since the username (account) who created jobd.bwc may not match with the username of the user.
 
It is suggested that the user should not be confronted with the password dialog when the Baan Job daemon is started.

Problem Description (Technical terms)
A new option is introduced. When configuring bwc file, the username which is encrypted with the password can be specified with the option -giveaway.

Workaround

Test Procedure
Create a bwc file for a friend with the password field specified. Let the friend run the bw with the bwc file. S/He should be able to run bw without specifing password field.

Affected Executables
bw.exe
bwconfig.dll

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

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




MergeProject: Grieg: # 8326 (VHNT3245): Fixing defects after merging project VHNT3235 (Verdi I) to Grieg.

Date: Thu, 9 Mar 2000 14:50:38 +0100 (MET)

                                                                             
Release: Grieg                                               Date: 2000/03/09

Script:      MergeProject
Project:     VHNT3245
Created on:  Grieg
Type:        bugfix

Problem:
Problem Description (Customer terms)

Problem Description (Technical terms)
Fixing defects after merging project VHNT3235 (Verdi I) to Grieg.

Workaround

Test Procedure

Affected Executables
BW.exe

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

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



MergeProject: Grieg: # 8984 (VHNT3718): New Japanese resoures

Date: Thu, 25 May 2000 09:00:43 +0200 (METDST)

                                                                             
Release: Grieg                                               Date: 2000/05/25

Script:      MergeProject
Project:     VHNT3718
Created on:  Grieg
Type:        bugfix

Problem:
Problem Description (Customer terms)
Double byte katakana Japanese resource file added to BW resources.

Problem Description (Technical terms)
See above.

Workaround
None

Test Procedure
Test on Japanese Windows system.

Affected Executables
bw.exe

Scopus defectnumber(s)	Scopus casenumber(s)	Priority (e.g. 10)
xxxxx			yyyyy			zz

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




MergeProject: Grieg: # 9280 (VHNT3900): Use of correct slashes for path BSE and BSE_TMP when used in argument of program started by app_start

Date: Wed, 5 Jul 2000 12:34:15 +0200 (METDST)

                                                                             
Release: Grieg                                               Date: 2000/07/05

Script:      MergeProject
Project:     VHNT3900
Created on:  Grieg
Type:        bugfix

Problem:
Problem Description (Customer terms)
When starting for example a program like: winword ${BSE_TMP}\worddoc on a windows
platform, winword cannot find worddoc because the ${BSE_TMP} is expanded using unix slashes. 

Problem Description (Technical terms)
To start winword app_start(winword "${BSE_TMP}\worddoc", ${BSE_TMP}, "", stdout, stderr)
is used. When expanding ${BSE_TMP} conversion is made to unix slashes.

Workaround
Hardcode the path to worddoc.

Test Procedure
Take care a text file "worddoc" is available in ${BSE_TMP} on the pc running bw.exe
Execute app_start(winword "${BSE_TMP}\worddoc", ${BSE_TMP}, "", stdout, stderr)
Winword should be able to find and open worddoc now.

Affected Executables
bw.exe

Scopus defectnumber(s)	Scopus casenumber(s)	Priority (e.g. 10)
96914			506137,535271,831502	20

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




MergeProject: Grieg: # 9294 (VHNT3520): tssinfo: solve compiler errors caused by VHNT3457

Date: Thu, 6 Jul 2000 10:30:21 +0200 (METDST)

                                                                             
Release: Grieg                                               Date: 2000/07/06

Script:      MergeProject
Project:     VHNT3520
Created on:  Corelli
Type:        bugfix

Problem:
Problem Description (Customer terms)
compiler error in tssinfo.c

Problem Description (Technical terms)
struct field changes in tss.h

Workaround
none

Test Procedure
compile

Affected Executables
tssinfo
bshell
bw

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

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