IIS and XP Home vs Pro

[Carla]

A windows pro in another group told me today that the IIS
extensions could only be used with XP-Pro, not the home
edition. Just confirming: is this true?

I actually don't know which XP we have for sure (and won't
know until later tonight; I just know my husband THINKS he
installed IIS over the weekend when he re-did the server
extensions to work with XP on our local server. If the
above is true, would "HomeXP" even let him install IIS?

On a related note, in my other thread Kevin suggested doing
a "recalculation" of links in case some internal pointers
to my exisiting webs got messed up during the OS
transition. That "recalc" would be on the server end in its
settings, not something I do from my desktop inside my old
webs, right?

 

[Jon Spivey]

Hi Carla,
It's true the extensions can only be installed on XP Pro not home - this is
because home does not support IIS. If your husband has in fact installed IIS
then you must have XP Pro

Jon
Microsoft MVP - FP

 

[Guest]

Thanks John... you're right. We do have Pro. Hub just got
home and confirmed it.

He/we also confirmed that my browser sees IIS running (with
an http;//machinename command). So now I'm back where I
started this AM, a Front Page app that wont talk to its
local server and sees all my existing webs as mere
collections of html files, not actual webs. I can't even
make a new web and publish it to the network drive. Nor
will any "old" web page display in the browser if it's sent
to the browser by my FP.

He's going to look at the tips I collected, but says the
pointer issue looks moot to him because nothing about where
the old webs live, or the names in the file path, has
changed during the transition from NT to XP on our server
and he's not aware of any "recalculate links" option on the
server side. (I also tried a "recalc" from inside one of my
old webs and it made no difference there either.)

However, he's now convinced he has to wade into the big fat
book and figure out what he might have missed, so that's
where things stand right now <g>.

Meanwhile, any more ideas or tips on what may be amiss are
still welcome!

 

[Kevin Spencer]

Okay, we need to define some terms here.

He/we also confirmed that my browser sees IIS running (with
an http;//machinename command). So now I'm back where I
started this AM, a Front Page app that wont talk to its
local server and sees all my existing webs as mere
collections of html files, not actual webs.

Installing a web server doesn't create webs any more than installing a file
system creates files. A web server is just that - a piece of software that
serves requests for objects that reside under its authority. To browse webs
on a web server, they must be created first. If you have disk-based webs
elsewhere on the machine, you will have to create server-based webs from
them. This can be done using the File|NewWeb...|Import Web Wizard command in
FrontPage. You have to define the HTTP URL of the new web (e.g.
"http://localhost/ChildWeb1"), and then browse to the current file location
of the web files/folders to import the files and folders (etc) to your
server (your new web on the web server). See the FrontPage Help files for
details.

started this AM, a Front Page app that wont talk to its

Misunderstanding what FrontPage IS is a common problem. FrontPage is merely
a suite of tools for creating web sites and web pages. I'm not sure what you
mean by a"a FrontPage app," but the only "FrontPage app" is the FrontPage
client software. You can create what FrontPage refers to as a "FrontPage
Web" with it, but that is simply a web site with FrontPage server extensions
installed.

It is extremely important to understand these terms in order to use
FrontPage successfully (or to build any web site using any tools
successfully).

--
HTH,
Kevin Spencer
..Net Developer
Microsoft MVP
Big things are made up
of lots of little things.

 

[Guest]

Thanks Kevin. Your thorough explanations are helping a lot,
since you're right there's a lot of the (current) lingo
that is just not obvious until it is explained, even to
those of us who have been using FP (for fairly simple webs)
virtually since its beginning.

All I know is that everything worked fine on the client
side before the OS change on our home server, and nothing
about the paths or permissions had changed since then.

So the notion that my prior client-side webs were now being
seen as something "disk-based" that need to be converted to
"server-based" is a big paradigm shift, and totally new
information to me at least. However that was handled in
prior revs of FP over a server with NT, it was transparent
to me as the end-user, and there was nothing to flag the
fact that I needed to take this extra "import" step now
that the server has gone to XP.
the only "FrontPage app" is the FrontPage CLIENT SOFTWARE.

When I said "Front Page app" I was trying to draw a
distinction between the suite of tools on my own desktop
with which I create/open/save/publish webs and the tools
that one installs on your own network server, if you happen
to have one. ("Server" is another term that gets confused
in such a set-up too, as there is no obvous (to me) way to
distinguish between the extensions at my Internet web host
and the extensions on the server in my basement.)

I worry that the increasing complication of all of this is
going to kill home networking eventually, as few of us have
the time to spend dozens of hours updating our personal
knowledge base every time we do an upgrade; yet we live in
a world where upgrading is increasingly not-optional. Thus
we often also lack the level of expertise to make sense of
what we are told even when we put in those dozens of hours.

That's why the continuing patience of people like you in
places like this matters a lot. And for that patience, as
well as your instructions, I am grateful.

I will start a new thread with a more specific query
related to the (new/different) error message I now get
since my hub installed a newer rev of the '02 extensions.