ME inside XP

"VanguardLH" <V@nguard.LH> wrote in message
news:T_GdncHRPoPru9bVnZ2dnUVZ_gCdnZ2d@comcast.com. ..
> "VanguardLH" wrote in
> <news:rICdnZ-5cKH2uNbVnZ2dnUVZWhednZ2d@comcast.com>:
>
> > "Norman" wrote in <news:u51#vQMyIHA.2188@TK2MSFTNGP04.phx.gbl>:
> >
> >> I think it was Mike Maltby (sp?) that pointed me to it.
> >
> > Pointed you to it WHERE? In a newsgroups post? If so, search Google
> > Groups for posts submitted by Mike Maltby.
> >
> > http://groups.google.com/groups?scor...+author:maltby
> >
> > The only technical newsgroup shown to where he posted was for 1 post
> > back in 2003 in the Windows ME newsgroup. You didn't pick a unique
> > enough moniker to go Google Group searching on it to find whatever
> > newsgroup discussion you were involved in before that discussed whatever
> > it is that you vaguely remember.
> >
> >> I was only toying
> >> with concerns of XP install and not getting SATA to run in ME at the
time.
> >
> > Not an issue in a virtual machine, like when using Virtual PC or VMWare
> > Server (both free, I prefer VMWare). All the hardware except the CPU is
> > emulated inside the virtual machine.
> >
> >> It stated at the MS site that it was intended for XP users that had
software
> >> that would not run in XP. And allowed an install of say ME in a box,
shell,
> >> something like that. All of the XP drivers would be used.
> >
> > Yep, the parent or host OS still has to communicate with the real
> > hardware through the use of drivers. All hardware except the CPU is
> > emulated with the virtual machine. You don't need drivers in the
> > virtual machine. However, you don't get the full feature set of your
> > real hardware. You get the emulated hardware which supports
> > legacy-grade hardware requirements. Don't expect to play games within a
> > virtual machine. You never mentioned WHAT you wanted to run within a
> > Windows ME environment.
>
> Something I forgot to mention about licensing. When you upgrade, you do
> not get another license for Windows. If you upgraded to Windows XP from
> Windows ME then you lost your license for Windows ME. Upgrades do not
> increase the number of license that you have. All upgrades must trace
> back through a single license to a full version that was used as the
> initial OS. Once you upgrade, the prior version is no longer valid for
> use.
>
> When installing Windows within a virtual machine, you are required to
> have a license to run it there. So if Windows XP is your host OS and
> Windows ME is your guest OS (in the virtual machine) then you need 2
> licenses: one for Windows XP and another for Windows ME.
>
> You never mentioned WHY you think you need Windows ME. What application
> won't run under Windows XP, even in compatibility mode?


The OP did mention why:
it was a case of ME not "seeing" the SATA drive.
If there is an ME driver for SATA, it should work.

"philo" wrote in <news:eGQgfoYyIHA.4816@TK2MSFTNGP03.phx.gbl>:

> "VanguardLH" <V@nguard.LH> wrote in message
> news:T_GdncHRPoPru9bVnZ2dnUVZ_gCdnZ2d@comcast.com. ..
>> "VanguardLH" wrote in
>> <news:rICdnZ-5cKH2uNbVnZ2dnUVZWhednZ2d@comcast.com>:
>>
>>> "Norman" wrote in <news:u51#vQMyIHA.2188@TK2MSFTNGP04.phx.gbl>:
>>>
>>>> I think it was Mike Maltby (sp?) that pointed me to it.
>>>
>>> Pointed you to it WHERE? In a newsgroups post? If so, search Google
>>> Groups for posts submitted by Mike Maltby.
>>>
>>> http://groups.google.com/groups?scor...+author:maltby
>>>
>>> The only technical newsgroup shown to where he posted was for 1 post
>>> back in 2003 in the Windows ME newsgroup. You didn't pick a unique
>>> enough moniker to go Google Group searching on it to find whatever
>>> newsgroup discussion you were involved in before that discussed whatever
>>> it is that you vaguely remember.
>>>
>>>> I was only toying
>>>> with concerns of XP install and not getting SATA to run in ME at the
> time.
>>>
>>> Not an issue in a virtual machine, like when using Virtual PC or VMWare
>>> Server (both free, I prefer VMWare). All the hardware except the CPU is
>>> emulated inside the virtual machine.
>>>
>>>> It stated at the MS site that it was intended for XP users that had
> software
>>>> that would not run in XP. And allowed an install of say ME in a box,
> shell,
>>>> something like that. All of the XP drivers would be used.
>>>
>>> Yep, the parent or host OS still has to communicate with the real
>>> hardware through the use of drivers. All hardware except the CPU is
>>> emulated with the virtual machine. You don't need drivers in the
>>> virtual machine. However, you don't get the full feature set of your
>>> real hardware. You get the emulated hardware which supports
>>> legacy-grade hardware requirements. Don't expect to play games within a
>>> virtual machine. You never mentioned WHAT you wanted to run within a
>>> Windows ME environment.
>>
>> Something I forgot to mention about licensing. When you upgrade, you do
>> not get another license for Windows. If you upgraded to Windows XP from
>> Windows ME then you lost your license for Windows ME. Upgrades do not
>> increase the number of license that you have. All upgrades must trace
>> back through a single license to a full version that was used as the
>> initial OS. Once you upgrade, the prior version is no longer valid for
>> use.
>>
>> When installing Windows within a virtual machine, you are required to
>> have a license to run it there. So if Windows XP is your host OS and
>> Windows ME is your guest OS (in the virtual machine) then you need 2
>> licenses: one for Windows XP and another for Windows ME.
>>
>> You never mentioned WHY you think you need Windows ME. What application
>> won't run under Windows XP, even in compatibility mode?
>
> The OP did mention why:
> it was a case of ME not "seeing" the SATA drive.
> If there is an ME driver for SATA, it should work.

In a virtual machine, there are no SATA drives. All hardware except the
CPU are emulated in a virtual machine. So that a SATA drive is used by
the host OS is unimportant when running Windows ME within a virtual
machine.

"VanguardLH" <V@nguard.LH> wrote in message
news:rICdnZ-5cKH2uNbVnZ2dnUVZWhednZ2d@comcast.com...
> "Norman" wrote in <news:u51#vQMyIHA.2188@TK2MSFTNGP04.phx.gbl>:
>
>> I think it was Mike Maltby (sp?) that pointed me to it.
>
> Pointed you to it WHERE? In a newsgroups post? If so, search Google
> Groups for posts submitted by Mike Maltby.
>
> http://groups.google.com/groups?scor...+author:maltby
>
> The only technical newsgroup shown to where he posted was for 1 post
> back in 2003 in the Windows ME newsgroup. You didn't pick a unique
> enough moniker to go Google Group searching on it to find whatever
> newsgroup discussion you were involved in before that discussed whatever
> it is that you vaguely remember.

What can I say, Shenan found it.
>
>> I was only toying
>> with concerns of XP install and not getting SATA to run in ME at the
>> time.
>
> Not an issue in a virtual machine, like when using Virtual PC or VMWare
> Server (both free, I prefer VMWare). All the hardware except the CPU is
> emulated inside the virtual machine.
Can you expand upon your choice and why?
Or are you saying the distinction is that VMWare is 'emulated inside' vs.
Virtual PC, stated below 'emulated with'?
>
>> It stated at the MS site that it was intended for XP users that had
>> software
>> that would not run in XP. And allowed an install of say ME in a box,
>> shell,
>> something like that. All of the XP drivers would be used.
>
> Yep, the parent or host OS still has to communicate with the real
> hardware through the use of drivers. All hardware except the CPU is
> emulated with the virtual machine. You don't need drivers in the
> virtual machine. However, you don't get the full feature set of your
> real hardware. You get the emulated hardware which supports
> legacy-grade hardware requirements.
So then it does not truly emulate, it just comes close?

Don't expect to play games within a
> virtual machine. You never mentioned WHAT you wanted to run within a
> Windows ME environment.

Darned, you are raining on my joy, at least a little since I have not fully
explored what I'd run on the virtual machine.
Norman

"VanguardLH" <V@nguard.LH> wrote in message
news:T_GdncHRPoPru9bVnZ2dnUVZ_gCdnZ2d@comcast.com. ..
> "VanguardLH" wrote in
> <news:rICdnZ-5cKH2uNbVnZ2dnUVZWhednZ2d@comcast.com>:
>
>> "Norman" wrote in <news:u51#vQMyIHA.2188@TK2MSFTNGP04.phx.gbl>:
>>
>>> I think it was Mike Maltby (sp?) that pointed me to it.
>>
>> Pointed you to it WHERE? In a newsgroups post? If so, search Google
>> Groups for posts submitted by Mike Maltby.
>>
>> http://groups.google.com/groups?scor...+author:maltby
>>
>> The only technical newsgroup shown to where he posted was for 1 post
>> back in 2003 in the Windows ME newsgroup. You didn't pick a unique
>> enough moniker to go Google Group searching on it to find whatever
>> newsgroup discussion you were involved in before that discussed whatever
>> it is that you vaguely remember.
>>
>>> I was only toying
>>> with concerns of XP install and not getting SATA to run in ME at the
>>> time.
>>
>> Not an issue in a virtual machine, like when using Virtual PC or VMWare
>> Server (both free, I prefer VMWare). All the hardware except the CPU is
>> emulated inside the virtual machine.
>>
>>> It stated at the MS site that it was intended for XP users that had
>>> software
>>> that would not run in XP. And allowed an install of say ME in a box,
>>> shell,
>>> something like that. All of the XP drivers would be used.
>>
>> Yep, the parent or host OS still has to communicate with the real
>> hardware through the use of drivers. All hardware except the CPU is
>> emulated with the virtual machine. You don't need drivers in the
>> virtual machine. However, you don't get the full feature set of your
>> real hardware. You get the emulated hardware which supports
>> legacy-grade hardware requirements. Don't expect to play games within a
>> virtual machine. You never mentioned WHAT you wanted to run within a
>> Windows ME environment.
>
> Something I forgot to mention about licensing. When you upgrade, you do
> not get another license for Windows. If you upgraded to Windows XP from
> Windows ME then you lost your license for Windows ME. Upgrades do not
> increase the number of license that you have. All upgrades must trace
> back through a single license to a full version that was used as the
> initial OS. Once you upgrade, the prior version is no longer valid for
> use.
Nada problem. I have two of WME. Also two of 95, one of 98, and yet 98SE.
>
> When installing Windows within a virtual machine, you are required to
> have a license to run it there. So if Windows XP is your host OS and
> Windows ME is your guest OS (in the virtual machine) then you need 2
> licenses: one for Windows XP and another for Windows ME.
>
> You never mentioned WHY you think you need Windows ME. What application
> won't run under Windows XP, even in compatibility mode?

Paperport printer will not install to XP SP2.
Norman

"philo" <philo@privacy.net> wrote in message
news:eGQgfoYyIHA.4816@TK2MSFTNGP03.phx.gbl...
>
> "VanguardLH" <V@nguard.LH> wrote in message
> news:T_GdncHRPoPru9bVnZ2dnUVZ_gCdnZ2d@comcast.com. ..
>> "VanguardLH" wrote in
>> <news:rICdnZ-5cKH2uNbVnZ2dnUVZWhednZ2d@comcast.com>:
>>
>> > "Norman" wrote in <news:u51#vQMyIHA.2188@TK2MSFTNGP04.phx.gbl>:
>> >
>> >> I think it was Mike Maltby (sp?) that pointed me to it.
>> >
>> > Pointed you to it WHERE? In a newsgroups post? If so, search Google
>> > Groups for posts submitted by Mike Maltby.
>> >
>> > http://groups.google.com/groups?scor...+author:maltby
>> >
>> > The only technical newsgroup shown to where he posted was for 1 post
>> > back in 2003 in the Windows ME newsgroup. You didn't pick a unique
>> > enough moniker to go Google Group searching on it to find whatever
>> > newsgroup discussion you were involved in before that discussed
>> > whatever
>> > it is that you vaguely remember.
>> >
>> >> I was only toying
>> >> with concerns of XP install and not getting SATA to run in ME at the
> time.
>> >
>> > Not an issue in a virtual machine, like when using Virtual PC or VMWare
>> > Server (both free, I prefer VMWare). All the hardware except the CPU
>> > is
>> > emulated inside the virtual machine.
>> >
>> >> It stated at the MS site that it was intended for XP users that had
> software
>> >> that would not run in XP. And allowed an install of say ME in a box,
> shell,
>> >> something like that. All of the XP drivers would be used.
>> >
>> > Yep, the parent or host OS still has to communicate with the real
>> > hardware through the use of drivers. All hardware except the CPU is
>> > emulated with the virtual machine. You don't need drivers in the
>> > virtual machine. However, you don't get the full feature set of your
>> > real hardware. You get the emulated hardware which supports
>> > legacy-grade hardware requirements. Don't expect to play games within
>> > a
>> > virtual machine. You never mentioned WHAT you wanted to run within a
>> > Windows ME environment.
>>
>> Something I forgot to mention about licensing. When you upgrade, you do
>> not get another license for Windows. If you upgraded to Windows XP from
>> Windows ME then you lost your license for Windows ME. Upgrades do not
>> increase the number of license that you have. All upgrades must trace
>> back through a single license to a full version that was used as the
>> initial OS. Once you upgrade, the prior version is no longer valid for
>> use.
>>
>> When installing Windows within a virtual machine, you are required to
>> have a license to run it there. So if Windows XP is your host OS and
>> Windows ME is your guest OS (in the virtual machine) then you need 2
>> licenses: one for Windows XP and another for Windows ME.
>>
>> You never mentioned WHY you think you need Windows ME. What application
>> won't run under Windows XP, even in compatibility mode?
>
>
> The OP did mention why:
> it was a case of ME not "seeing" the SATA drive.
> If there is an ME driver for SATA, it should work.
>
>
Thanks Philo, among other possibilities. And I did not realize I'd have to
answer to the piracy police before getting an answer.
Norman

"VanguardLH" <V@nguard.LH> wrote in message
news:-f2dnQoXIN-YO9HVnZ2dnUVZ_u2dnZ2d@comcast.com...
> "philo" wrote in <news:eGQgfoYyIHA.4816@TK2MSFTNGP03.phx.gbl>:
>
>> "VanguardLH" <V@nguard.LH> wrote in message
>> news:T_GdncHRPoPru9bVnZ2dnUVZ_gCdnZ2d@comcast.com. ..
>>> "VanguardLH" wrote in
>>> <news:rICdnZ-5cKH2uNbVnZ2dnUVZWhednZ2d@comcast.com>:
>>>
>>>> "Norman" wrote in <news:u51#vQMyIHA.2188@TK2MSFTNGP04.phx.gbl>:
>>>>
>>>>> I think it was Mike Maltby (sp?) that pointed me to it.
>>>>
>>>> Pointed you to it WHERE? In a newsgroups post? If so, search Google
>>>> Groups for posts submitted by Mike Maltby.
>>>>
>>>> http://groups.google.com/groups?scor...+author:maltby
>>>>
>>>> The only technical newsgroup shown to where he posted was for 1 post
>>>> back in 2003 in the Windows ME newsgroup. You didn't pick a unique
>>>> enough moniker to go Google Group searching on it to find whatever
>>>> newsgroup discussion you were involved in before that discussed
>>>> whatever
>>>> it is that you vaguely remember.
>>>>
>>>>> I was only toying
>>>>> with concerns of XP install and not getting SATA to run in ME at the
>> time.
>>>>
>>>> Not an issue in a virtual machine, like when using Virtual PC or VMWare
>>>> Server (both free, I prefer VMWare). All the hardware except the CPU
>>>> is
>>>> emulated inside the virtual machine.
>>>>
>>>>> It stated at the MS site that it was intended for XP users that had
>> software
>>>>> that would not run in XP. And allowed an install of say ME in a box,
>> shell,
>>>>> something like that. All of the XP drivers would be used.
>>>>
>>>> Yep, the parent or host OS still has to communicate with the real
>>>> hardware through the use of drivers. All hardware except the CPU is
>>>> emulated with the virtual machine. You don't need drivers in the
>>>> virtual machine. However, you don't get the full feature set of your
>>>> real hardware. You get the emulated hardware which supports
>>>> legacy-grade hardware requirements. Don't expect to play games within
>>>> a
>>>> virtual machine. You never mentioned WHAT you wanted to run within a
>>>> Windows ME environment.
>>>
>>> Something I forgot to mention about licensing. When you upgrade, you do
>>> not get another license for Windows. If you upgraded to Windows XP from
>>> Windows ME then you lost your license for Windows ME. Upgrades do not
>>> increase the number of license that you have. All upgrades must trace
>>> back through a single license to a full version that was used as the
>>> initial OS. Once you upgrade, the prior version is no longer valid for
>>> use.
>>>
>>> When installing Windows within a virtual machine, you are required to
>>> have a license to run it there. So if Windows XP is your host OS and
>>> Windows ME is your guest OS (in the virtual machine) then you need 2
>>> licenses: one for Windows XP and another for Windows ME.
>>>
>>> You never mentioned WHY you think you need Windows ME. What application
>>> won't run under Windows XP, even in compatibility mode?
>>
>> The OP did mention why:
>> it was a case of ME not "seeing" the SATA drive.
>> If there is an ME driver for SATA, it should work.
>
> In a virtual machine, there are no SATA drives. All hardware except the
> CPU are emulated in a virtual machine. So that a SATA drive is used by
> the host OS is unimportant when running Windows ME within a virtual
> machine.
I think Philo was pointing out that if WME had SATA drivers it would work in
WME.
And if I had drivers I would not be considering the VM to run ME or 98 for
legacy software, sidestepping the issue of not being to use my SATA drive in
WME.
Norman