作为屏幕保护程序 VB6 操作复杂的应用程序
我正在编写一个规范，将我们最复杂的应用程序之一转换为作为屏幕保护程序运行的应用程序。
目前，该应用程序将从文件系统中读取数据注册表（用户，但将转换为本地计算机）并生成多个子可执行文件，使用 WMP SDK 和其他图像和 Flash 媒体显示库在屏幕上绘制媒体元素。有些是操作系统本机的，有些则不是。
它是用 VB6 编写的，并且必须继续进行此转换。
该应用程序当前作为交互式帐户空间中的应用程序运行。通常使用以管理员身份登录的帐户或其他高级帐户。此应用程序必须在未作为屏幕保护程序登录的情况下运行。
为我的研究做这件事的资源很少。
我很想知道 SO 社区的意见。考虑到在此上下文中操作 EXE 的安全限制，在未登录时将应用程序作为屏幕保护程序运行时是否有任何限制。作为屏幕保护程序运行的 EXE 是否会阻止生成其他子进程或限制读取文件或注册表信息。
直接显示或直接绘制有图形处理限制吗？系统 ODBC 还可以使用吗？
这适用于 Windows XP 和 Windows Windows 7。
感谢您抽出时间。
I'm in the process of writing a specification to convert one of our most complex applications into an application which runs as a screensaver.
Currently this application will read from the file system & registry (User, but will be converted to Local Machine) and spawn multiple child executables drawing media elements on screen using WMP SDK and other media display libraries for images and flash. Some native to the OS, some not.
It is written in VB6 and must continue to be for this conversion.
This application currently operates as an application in the interactive account space. Usually with an account logged in as an administrator, or other highly elevated account. This application must operate without been logged in as a Screensaver.
Resources on doing this for my research are scant.
I'm keen to know the opinions of the SO community. Are there any limitations when running applications as screen savers when not logged in, considering security limitations of operating EXE's in this context. Are EXEs running as screensavers prevented from spawning other child processes or limited in reading file or registry information.
Are there any graphics handling restrictions with direct show or direct draw? Can systen ODBC's still be used?
This applies to Windows XP & Windows 7.
Thank you for your time.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
我想我会回来结束这一切。
经过与 Microsoft 的一些测试和讨论后，发现在未登录时无法将复杂的应用程序作为屏幕保护程序运行。
Windows 登录屏幕上使用的会话在设计上具有有限的桌面堆分配。尝试使用多个资源或打开多个窗口是行不通的，因为堆只会耗尽内存。
经过测试和 MS 自己的话证明。
Thought I'd come back and close this off.
After some testing and discussions with Microsoft it turns out you cannot run complex applications as a screensaver when not logged in.
The session used at the windows log in screen has a limited desktop heap allocation by design. Attempting to use multiple resources or open many windows will not work as the heap will simply run out of memory.
Proven by testing and by MS's own word.