XP Mode as "Server"

Hi --

You can't load FrontPage Extensions in Windows 7, apparently, so it
looks like the only choice I have to keep my FrontPage webs local will
be to stick them in an XP Mode VM. I have this working just fine.

Question: How to activate this VM at startup? Do I need to just stick
some minor little application on it, and have that in my startup group?

Thanks... Karl

--
[.NET: It's About Trust!]

Karl E. Peterson was thinking very hard :
> You can't load FrontPage Extensions in Windows 7, apparently, so it looks
> like the only choice I have to keep my FrontPage webs local will be to stick
> them in an XP Mode VM. I have this working just fine.
>
> Question: How to activate this VM at startup? Do I need to just stick some
> minor little application on it, and have that in my startup group?

Apparently, I was out-thinking myself. I figured, why not just install
FrontPage 2003 on that VM!? Well, uh, when I do, then try to start it,
I'm told:

To open a virtual application, the virtual machine must be closed.

Huh. That seems rather odd...

--
[.NET: It's About Trust!]

Karl E. Peterson expressed precisely :
> Karl E. Peterson was thinking very hard :
>> You can't load FrontPage Extensions in Windows 7, apparently, so it looks
>> like the only choice I have to keep my FrontPage webs local will be to
>> stick them in an XP Mode VM. I have this working just fine.
>>
>> Question: How to activate this VM at startup? Do I need to just stick some
>> minor little application on it, and have that in my startup group?
>
> Apparently, I was out-thinking myself. I figured, why not just install
> FrontPage 2003 on that VM!? Well, uh, when I do, then try to start it, I'm
> told:
>
> To open a virtual application, the virtual machine must be closed.
>
> Huh. That seems rather odd...

OKAY!!! This is seriously cool! :-)

So I close the VM, and fire up FrontPage from the Start Menu under XP
Mode. Hot damn, it works. The webs on that VM are totally available.

And, oddly enough, even after I close all instances of FrontPage, the
webs are still accessible via browser from the host. WTF's up with
that? Apparently, it's hibernated? But if that's so, then how can the
web pages be so snappy?

Inquiring minds...

--
[.NET: It's About Trust!]

"Karl E. Peterson" <> wrote in message
news:...
> Karl E. Peterson expressed precisely :
>> Karl E. Peterson was thinking very hard :
>>> You can't load FrontPage Extensions in Windows 7, apparently, so it
>>> looks like the only choice I have to keep my FrontPage webs local will
>>> be to stick them in an XP Mode VM. I have this working just fine.
>>>
>>> Question: How to activate this VM at startup? Do I need to just stick
>>> some minor little application on it, and have that in my startup group?
>>
>> Apparently, I was out-thinking myself. I figured, why not just install
>> FrontPage 2003 on that VM!? Well, uh, when I do, then try to start it,
>> I'm told:
>>
>> To open a virtual application, the virtual machine must be closed.
>>
>> Huh. That seems rather odd...
>
> OKAY!!! This is seriously cool! :-)
>
> So I close the VM, and fire up FrontPage from the Start Menu under XP
> Mode. Hot damn, it works. The webs on that VM are totally available.
>
> And, oddly enough, even after I close all instances of FrontPage, the webs
> are still accessible via browser from the host. WTF's up with that?
> Apparently, it's hibernated? But if that's so, then how can the web pages
> be so snappy?
>
> Inquiring minds...
>
> --
> [.NET: It's About Trust!]
>
>
The vm does not hibernate immediately. It is on a timer so that you get
quick response to repeat requests. It only hibernates when the timer runs
down (about five minutes).

The other thing you saw happens if you have been using the vm directly. It
has to log you out so that the remote app can use the machine.

Bill Grant presented the following explanation :
>
> "Karl E. Peterson" <> wrote in message
> news:...
>> Karl E. Peterson expressed precisely :
>>> Karl E. Peterson was thinking very hard :
>>>> You can't load FrontPage Extensions in Windows 7, apparently, so it looks
>>>> like the only choice I have to keep my FrontPage webs local will be to
>>>> stick them in an XP Mode VM. I have this working just fine.
>>>>
>>>> Question: How to activate this VM at startup? Do I need to just stick
>>>> some minor little application on it, and have that in my startup group?
>>>
>>> Apparently, I was out-thinking myself. I figured, why not just install
>>> FrontPage 2003 on that VM!? Well, uh, when I do, then try to start it,
>>> I'm told:
>>>
>>> To open a virtual application, the virtual machine must be closed.
>>>
>>> Huh. That seems rather odd...
>>
>> OKAY!!! This is seriously cool! :-)
>>
>> So I close the VM, and fire up FrontPage from the Start Menu under XP Mode.
>> Hot damn, it works. The webs on that VM are totally available.
>>
>> And, oddly enough, even after I close all instances of FrontPage, the webs
>> are still accessible via browser from the host. WTF's up with that?
>> Apparently, it's hibernated? But if that's so, then how can the web pages
>> be so snappy?
>>
>> Inquiring minds...
>
> The vm does not hibernate immediately. It is on a timer so that you get
> quick response to repeat requests. It only hibernates when the timer runs
> down (about five minutes).

Yeah, that did ultimately happen. I guess that makes sense. Almost
like someone thought about this. :-)

> The other thing you saw happens if you have been using the vm directly. It
> has to log you out so that the remote app can use the machine.

Well, it's like one of those "gotta see it" kinda things. I like it.

--
[.NET: It's About Trust!]

Karl E. Peterson wrote:
> Bill Grant presented the following explanation :
>>
>> "Karl E. Peterson" <> wrote in message
>> news:...
>>> Karl E. Peterson expressed precisely :
>>>> Karl E. Peterson was thinking very hard :
>>>>> You can't load FrontPage Extensions in Windows 7, apparently, so it
>>>>> looks like the only choice I have to keep my FrontPage webs local
>>>>> will be to stick them in an XP Mode VM. I have this working just
>>>>> fine.
>>>>>
>>>>> Question: How to activate this VM at startup? Do I need to just
>>>>> stick some minor little application on it, and have that in my
>>>>> startup group?
>>>>
>>>> Apparently, I was out-thinking myself. I figured, why not just
>>>> install FrontPage 2003 on that VM!? Well, uh, when I do, then try
>>>> to start it, I'm told:
>>>>
>>>> To open a virtual application, the virtual machine must be closed.
>>>>
>>>> Huh. That seems rather odd...
>>>
>>> OKAY!!! This is seriously cool! :-)
>>>
>>> So I close the VM, and fire up FrontPage from the Start Menu under XP
>>> Mode. Hot damn, it works. The webs on that VM are totally available.
>>>
>>> And, oddly enough, even after I close all instances of FrontPage, the
>>> webs are still accessible via browser from the host. WTF's up with
>>> that? Apparently, it's hibernated? But if that's so, then how can
>>> the web pages be so snappy?
>>>
>>> Inquiring minds...
>>
>> The vm does not hibernate immediately. It is on a timer so that you
>> get quick response to repeat requests. It only hibernates when the
>> timer runs down (about five minutes).
>
> Yeah, that did ultimately happen. I guess that makes sense. Almost
> like someone thought about this. :-)
>
>> The other thing you saw happens if you have been using the vm
>> directly. It has to log you out so that the remote app can use the
>> machine.
>
> Well, it's like one of those "gotta see it" kinda things. I like it.
>

It's called RTFM

KissThis used his keyboard to write :
> It's called RTFM

Bite me.

--
[.NET: It's About Trust!]

Karl E. Peterson wrote:
> KissThis used his keyboard to write :
>> It's called RTFM
>
> Bite me.
>
Snappy response moron. Why don't you do a little leg work instead of
whining.

KissThis wrote :
> Karl E. Peterson wrote:
>> KissThis used his keyboard to write :
>>> It's called RTFM
>>
>> Bite me.
>>
> Snappy response moron. Why don't you do a little leg work instead of whining.

What would ever brighten /your/ day, then? Luser...

--
[.NET: It's About Trust!]