[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference utrop1::linkworks_v3

Title:	LinkWorks V3.0 Notes Conference
Notice:	LNX_APO = APO issues, LINKWORKS_V3 = V3.0 issues
Moderator:	tacklr.apd.dec.com::TACK_Lm::TACK_L

Created:	Tue Jun 28 1994
Last Modified:	Fri Jun 06 1997
Last Successful Update:	Fri Jun 06 1997
Number of topics:	2269
Total number of notes:	8338

2183.0. "Problems with the memory cache...." by KERNEL::SIMPSONR (fred) Fri Apr 04 1997 13:29

Windows NT V4 and Windows V3.1   LinkWorks V3.0.8

Initially he saw the problem with .REG files (export registry text files)
on his NT desktop. The changes would not be taken, so he would log out of
system to get the changes to apply. When running VB programs and admin changes
in fact anything that reads the cache (memory cache not disk cache) causes the
problem, it does not see the latest updates. Admin and config seam
to get this issue more than most. He deleted the cache (the physical cache
file) and it still did not work properly. He believes that it must be held in
memory. In Windows 95 it works fine. He believes that this is a LinkWorks
problem or an NT platform disk caching system. In order to get the changes
implemented, close all programs and restart NT, or log off your account
and log on again. This appears to clear the cache properly. He can readily
reproduce this.

Any ideas?
Cheers,
Richard Simpson.

T.R	Title	User	Personal Name	Date	Lines
2183.1		elec5.uto.dec.com::maandag_j		`Mon Apr 07 1997 12:35`	5
	Richard, What are the changes you are talking about? Jos
2183.2		KERNEL::SIMPSONR	fred	`Tue Apr 22 1997 16:33`	25
	Hi Jos, Sorry that it took me so long to reply. Here is an example of how they reproduce the problem: o Boot up NT. The registry settings for LinkWorks will be set to the live system o He then logs into LinkWorks o Next he pushes a button that runs a visual basic routine that lists the users id, organisational unit, name etc (it is an information button). It simply gets the desk reference and works on the user id of the desk and retrieves the information from the disk cache. This works fine. o He then logs out of LinkWorks o He double clicks on the .REG file with settings for a test LinkWorks domain. o Runs LinkWorks. He is now logged into the test system without any problems. In the title bar it has his correct name. o But if he now runs the same VB program using the push button. It now comes up with a completely different user's information. On 95 this works fine. Is this LinkWorks or an NT bug? Cheers, Richard.
2183.3		hlsw01.uto.dec.com::MAANDAG_J	European LinkWorks Support Center	`Wed Apr 23 1997 11:01`	18
	Richard, I don't understand this. THe user's id of the user they get the info from in the latter case is that the same user-id of the first example? If that is the case it seems that they are still working on old cache files. That is strange sinve LNX itself also uses the cache files. Puzzled.. In my office I work on two different NT 4.0 systems and I am often switching between different servers but never came across this problem. I'm not changing the registry by hand though. To switch from server I start LNX with the -host option (...\lnx -host<hostname> Works fine for me. Jos
2183.4		KERNEL::SIMPSONR	fred	`Tue May 20 1997 17:41`	10
	Hi Rob (the customer :)) Has tried using the -host and it works, but he still would like to know if the problem he has found is with LinkWorks or NT as he wants to use the button that he has setup as detailed in the previous replies to this notes, can someone look into this? Cheers, Richard.