[Crossle86]

Greg,
I found this info with web search and it makes sense, though I am reluctant to change the system wide default shell. I'd rather change it for the Driver user. Now given all this, I expected to find the registry key that causes the old DS program to launch as shell for the Driver user. But I could not find any key that would cause any shell to launch other than explorer.exe. What gives? How is the DS program launched as the shell for the driver user?

Now, I think I have a work around (try tomorrow), but I'd really like to understand what is going on here. This should not be nearly this much trouble assuming I have not made some mistake that is causing these problems with a simple DS update.

Additionally, if I run the updated DS as the developer user as a regular windows app, the DS appears with the title bar and window borders. The NI and our custom DS code that displays the upper area of the DS (camera, and indicators buttons etc) also displays but things are not sized right because of the title bar and borders on the lower part of the DS display. So I select the button on the lower DS that gets rid of the title bar and borders and the lower part of the DS displays correctly or at least as I expect it to and as I want it to. But, at the same time, the upper part of the DS display is trashed. The camera section remains but the tabbed area completely disappears. This happens with the NI version shipped with the DS and with our customized version. this is not helpful as it precludes just running the DS logged on as developer.

Is there an ini file setting that starts the DS without title bars and borders?