Corinna Vinschen wrote: > > Only exes require the TS-aware bit. Two interesting snippets from MSDN: > > http://msdn.microsoft.com/en-us/library/cc834995(VS.85).aspx
But in order to set this flag without problems cropping up, you must satisfy: * The application does not run as a system service (that is, LUID=System). This probably isn't an issue for cygwin-1.7 and beyond, given the changes in how services are installed. (Dang, I need to release an updated csih...) * The application does not write to the HKEY Local Machine registry hive for user specific data or configuration. Hmm. regtool? /proc/registry? Either way, you lose. If we go one way, then you can't use regtool or /proc/registry to manipulate the virtualized registry entries, if you're trying to fix something related to a non-TS (windows) app. If we go the other way, then you can't use regtool or /proc/registry to manipulate the "real" non-virtualized registry. Ditto for virtualized vs. non-virtualized /Program\ Files, /Windows, etc. THERE's the reason to keep an old cygwin-1.5 installation laying around! <g> > http://msdn.microsoft.com/en-us/library/01cfys9z.aspx "/TSAWARE is not valid for drivers, VxDs, or DLLs. " Yep, need to fix aslr.exe to not do that. Also, I think I might use aslr to set the flag on my copy of NotePad++. I hate having to install the syntax colorizer plugins into both my and admin's virtualized Program Files directory...for every update... -- Chuck -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/