I have written code to start a Windows Terminal Client session and follow the ID of that process. It all worked fine for over 2 years.
Now systems are being upgraded to Windows 7 64 bit and my program fails to follow the process ID. It seems that Windows 7 starts the Terminal Client program and then switches to an other process ID. This cannot be seen in the process manager since the first process ID only lasts for microseconds.
The question is: can i follow this change of process ID? I cannot do it by tracking the window title because multiple terminal sessions are possible and they all have the same name.
!--removed tag-->
No one has replied yet! Why not be the first?
Sign in or Join us (it's free).