Finally determined that this was the error I was having:
Win 7 64-bit
Quadro FX 1800M
Some of the world drudgingly use Windoze, especially those of us who are menu-adverse Luddites who prefer command-line compilation and scripting (and who frequently work in places where we are trying to get the customer up from stone knives and bear skins and menus are for order-out).
I recently got this hot new box, spec’d by IT and containing required IT-ish applications but would be handy for working on-the-road, and started the process of getting CUDA installed. Very disappointed: I’ve been using PuTTY to access the local Windoze box like it was any of the dozen Linux boxes that I use every day, including the embedded, rugged, deployable Linux box that is running a very interesting CUDA application. However, after much experimentation I determined that there was this permissions issue (“session 0” mentioned above) which was not going away.
Of course, that’s after installing and de-installing CUDA 4.0 x64 and 3.2 x64, currently working with 4.0 x32.
Basically no sshd access to CUDA on a Windoze box.
Had I known the right question to ask, I may have been here days ago. Thank you for verifying my findings.
PS: Linux CUDA has no such issue, although Linux ATI CAL actually does with default X Window Server configurations.
Research would seem to indicate that TCC is not appropriate for a Quadro FX 1800M either: did I get that right?
The Cygwin local bash shell, which uses the STUPID WINDOWS CONSOLE, so cuts and pastes are DIFFERENT and STUPID and CLUMSY AND ERROR PRONE, and command-line compilations get chewed up.
However, I have found that I can bring up a local xterm using the Cygwin X Window Server run from a bash shell in the STUPID WINDOWS CONSOLE, and THAT allows more UNIX-ish cut-and-paste.
I hope that helps somebody in the same soup.
Now I get to re-try CUDA 4.0 x64…
Thank God I will never spec a Windoze box for a customer…