locking workstation

[chickeybaby]

Hi,

something weird happens to my workstation. I have a
specific type of software loaded and performing in the
background. if i lock my workstation and then go away and
come back in half an hour or so, the software closes down.

Is there any reason for this? When i was using the same
software with windows 2000 it would never close down after
i locked the workstation.

Any ideas?

thanks

 

[Wesley Vogel]

You might ask the "specific type of software" makers.

 

[NobodyMan]

Hi,

something weird happens to my workstation. I have a
specific type of software loaded and performing in the
background. if i lock my workstation and then go away and
come back in half an hour or so, the software closes down.

Is there any reason for this? When i was using the same
software with windows 2000 it would never close down after
i locked the workstation.

Any ideas?

thanks

Without knowing any details that you thoughtfully didn't provide:

XP is not Win2k. Why do expect apps installed on both to work the
same?

 

[Daniel]

Without knowing any details that you thoughtfully didn't provide:

XP is not Win2k. Why do expect apps installed on both to work the
same?

I don't have full knowledge of what the original poster meant, but...

- if the software works normally on XP when the machine is in use, it
doesn't sound like an OS version issue...
- ... but rather some configuration on XP that stops the software from
working (both in the sense of "halts execution" and "malfunctions").

I've had strange experiences with hibernation on XP, but locking alone
shouldn't affect active processes, or...?

/Daniel

 

[NobodyMan]

I don't have full knowledge of what the original poster meant, but...

- if the software works normally on XP when the machine is in use, it
doesn't sound like an OS version issue...
- ... but rather some configuration on XP that stops the software from
working (both in the sense of "halts execution" and "malfunctions").

I've had strange experiences with hibernation on XP, but locking alone
shouldn't affect active processes, or...?

/Daniel

I thought the OP was pretty clear: the program doesn't behave the
same under XP as it did in 2000.

Why should it? Although XP and 2000 are similiar, they are after all
not the same OS, just based on the same kernel.