"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.