Archive of UserLand's first discussion group, started October 5, 1998.

Solution for Visible Windows-based HTTP apps

Author:Brent Simmons
Posted:12/14/1998; 12:49:56 AM
Topic:Visible Windows-based HTTP apps
Msg #:1166 (In response to 1153)
Prev/Next:1165 / 1167

I have a solution that works so far on two machines, one running IIS 4 on NT Server and the other running PWS on NT Workstation. This solution allows Frontier's UI to be visible when running behind IIS using the iisFrontier.dll. (Untested with .asp pages, but should work the same.)

I'd like to hear any comments from IIS and COM experts about my solution: if there are potential problems with it, I'd like to know.

If you're willing to try a not thoroughly tested solution, here's what you do. After making sure IIS and Frontier are not currently running:

1) From the Start Menu, click Run.

2) Type dcomcnfg and click OK.

3) The Distributed COM Configuration Properties dialog box appears. Scroll to the bottom of the Applications tab window.

4) Select the line that reads: UserLand, Frontier, Server

5) Click Properties.

6) Click the Identity tab.

7) To the question:

"Which user account do you want to use to run this application?"

Click the radio button labelled:

"The interactive user."

This means that when Frontier is launched by IIS, it will be launched in the currently logged-in user's space, not in the invisible IIS desktop.

This also probably means that you'll always have to log into a machine running Frontier, unless you switch back to:

"The launching user."

8) Click OK.

9) Click OK again.

There are responses to this message:

This page was archived on 6/13/2001; 4:46:31 PM.

© Copyright 1998-2001 UserLand Software, Inc.