Recommended Longhorn system requirements

[hermes]

greg_barton writes "At first I thought this was a joke, but this article
from Microsoft Watch confirms it: 'Microsoft is expected to recommend that
the 'average' Longhorn PC feature a dual-core CPU running at 4 to 6GHz; a
minimum of 2 gigs of RAM; up to a terabyte of storage; a 1 Gbit, built-in,
Ethernet-wired port and an 802.11g wireless link; and a graphics processor
that runs three times faster than those on the market today.'"

http://slashdot.org/articles/04/05/04/2223237.shtml?tid=137&tid=185&tid=190&
tid=201

http://www.microsoft-watch.com/article2/0,1995,1581842,00.asp

Heh, that brings up one heck of a feasibility issue!

--
hermes
DRM sux! Treacherous Computing kills our virtual civil liberties!
http://www.cl.cam.ac.uk/~rja14/tcpa-faq.html

Windows XP crashed.
I am the Blue Screen of Death.
No one hears your screams.

Yesterday it worked.
Today it is not working.
Windows is like that.

 

[Mike Brannigan [MSFT]]

greg_barton writes "At first I thought this was a joke, but this article
from Microsoft Watch confirms it: 'Microsoft is expected to recommend that
the 'average' Longhorn PC feature a dual-core CPU running at 4 to 6GHz; a
minimum of 2 gigs of RAM; up to a terabyte of storage; a 1 Gbit, built-in,
Ethernet-wired port and an 802.11g wireless link; and a graphics processor
that runs three times faster than those on the market today.'"

http://slashdot.org/articles/04/05/04/2223237.shtml?tid=137&tid=185&tid=190&
tid=201

http://www.microsoft-watch.com/article2/0,1995,1581842,00.asp

Heh, that brings up one heck of a feasibility issue!

A piece of idle speculation on their part.
Also be very careful with phrase such as "... Microsoft Watch confirms it:
'Microsoft is expected ..."
A third party publication confirms nothing if it prints an expectation based
on no referenced source.
Windows "Longhorn" is still a significant time away and system requirements
for it are no where near being set.
A lot can happen in the hardware world in timescales measured in years.

For real information on Windows "Longhorn" see:-

http://msdn.microsoft.com/Longhorn/understanding/preparing/default.aspx
and
http://msdn.microsoft.com/Longhorn/default.aspx

--
Regards,

Mike
--
Mike Brannigan [Microsoft]

This posting is provided "AS IS" with no warranties, and confers no
rights

Please note I cannot respond to e-mailed questions, please use these
newsgroups

 

[Art]

Thanks for making sure this newsgroup has accurate information. Is
there something wrong with the Windows Update site since it started
giving me a date/time error today and this never happened before?

 

[hermes]

Before the MVP (M$ Victim Poster) Hermes responded, Mike Brannigan
[MSFT] typed:

http://slashdot.org/articles/04/05/04/2223237.shtml?tid=137&tid=185&tid=190&

A piece of idle speculation on their part.
Also be very careful with phrase such as "... Microsoft Watch
confirms it: 'Microsoft is expected ..."
A third party publication confirms nothing if it prints an
expectation based on no referenced source.

"That's according to developer sources close to the company. Microsoft
officials would not comment on the Longhorn reference implementation."

This is the referenced source they named. How does "developer sources close
to the company" equate to "idle speculation on thier part"?

Windows "Longhorn" is still a significant time away and system
requirements for it are no where near being set.
A lot can happen in the hardware world in timescales measured in
years.

For real information on Windows "Longhorn" see:-

http://msdn.microsoft.com/Longhorn/understanding/preparing/default.aspx
and
http://msdn.microsoft.com/Longhorn/default.aspx

--
Regards,

Mike


http://slashdot.org/articles/04/05/04/2223237.shtml?tid=137&tid=185&tid=190&

--
hermes
DRM sux! Treacherous Computing kills our virtual civil liberties!
http://www.cl.cam.ac.uk/~rja14/tcpa-faq.html

Windows XP crashed.
I am the Blue Screen of Death.
No one hears your screams.

Yesterday it worked.
Today it is not working.
Windows is like that.

 

[Art]

<snip>
I guess we will have to wait and see with the Longhorn System
requirements and in the meantime I will be happy with my Microsoft
Windows 98 Second Edition that is unaffected by the Sasser worm. The
9x code still has life and will be supported by Microsoft until 30
June 2006 unless they extend support again. LOL I am truly sorry to
those of you who seem to think that XP is secure. Don't say I have
not warned you about some of the problems with XP and I do not plan on
multi-booting with it until these security issues have been fully
addressed. See:
http://www.eeye.com/html/Research/Upcoming/index.html
for problems that the NT source code is still suffering under. Carpe
Diem to 9x and MSDOS.

 

[Mike Brannigan [MSFT]]

"That's according to developer sources close to the company. Microsoft
officials would not comment on the Longhorn reference implementation."

This is the referenced source they named. How does "developer sources close
to the company" equate to "idle speculation on thier part"?

For accurate developer information not from some one close to but directly
from us to them you can see details of the specs and possible requirements
for graphics subsystems at
http://www.microsoft.com/whdc/device/display/graphics-reqs.mspx
If you look at the Aero and even at the Glass Aero specs you will see these
are actually still in the bounds of today's graphics cards and not the
speculated " graphics processor that runs three times faster than those on
the market today"

Best not to listen to rumour and third party speculation.
If you are interested in deep technical requirements for device support in
Windows Longhorn you can find out more at
http://www.microsoft.com/whdc/driver/LDK/default.mspx

This is the same information we give the OEMs and the "developer sources
close to the company"

--
Regards,

Mike
--
Mike Brannigan [Microsoft]

This posting is provided "AS IS" with no warranties, and confers no
rights

Please note I cannot respond to e-mailed questions, please use these
newsgroups

Before the MVP (M$ Victim Poster) Hermes responded, Mike Brannigan
[MSFT] typed:http://slashdot.org/articles/04/05/04/2223237.shtml?tid=137&tid=185&tid=190&

A piece of idle speculation on their part.
Also be very careful with phrase such as "... Microsoft Watch
confirms it: 'Microsoft is expected ..."
A third party publication confirms nothing if it prints an
expectation based on no referenced source.

"That's according to developer sources close to the company. Microsoft
officials would not comment on the Longhorn reference implementation."

This is the referenced source they named. How does "developer sources close
to the company" equate to "idle speculation on thier part"?

Windows "Longhorn" is still a significant time away and system
requirements for it are no where near being set.
A lot can happen in the hardware world in timescales measured in
years.

For real information on Windows "Longhorn" see:-

http://msdn.microsoft.com/Longhorn/understanding/preparing/default.aspx
and
http://msdn.microsoft.com/Longhorn/default.aspx

http://slashdot.org/articles/04/05/04/2223237.shtml?tid=137&tid=185&tid=190&
--
hermes
DRM sux! Treacherous Computing kills our virtual civil liberties!
http://www.cl.cam.ac.uk/~rja14/tcpa-faq.html

Windows XP crashed.
I am the Blue Screen of Death.
No one hears your screams.

Yesterday it worked.
Today it is not working.
Windows is like that.

 

[Mike Kolitz]

"That's according to developer sources close to the company. Microsoft

officials would not comment on the Longhorn reference implementation."

This is the referenced source they named. How does "developer sources close
to the company" equate to "idle speculation on thier part"?

Because it doesn't give you any more information than saying "yeah, this guy
I know... well, he heard from his girlfriend's sister's friend's aunt's..."

You're making an assumption that because someone is simply identified as
being "close to" Microsoft that they actually have an idea of what's going
on, which isn't necessarily the case. "Close to" could mean that the guy or
gal has an apartment near the Microsoft campus, for all we know.

I'm not saying that the information in the article is wrong - I don't know
what the recommended hardware requirements will be. All I'm saying is that
you shouldn't put a lot of faith in that information until you get it from
the people who actually *know*. In this case, that's Microsoft.

--
Mike Kolitz MCSE 2000
MS-MVP - Windows Setup & Deployment

Before the MVP (M$ Victim Poster) Hermes responded, Mike Brannigan
[MSFT] typed:http://slashdot.org/articles/04/05/04/2223237.shtml?tid=137&tid=185&tid=190&

A piece of idle speculation on their part.
Also be very careful with phrase such as "... Microsoft Watch
confirms it: 'Microsoft is expected ..."
A third party publication confirms nothing if it prints an
expectation based on no referenced source.

"That's according to developer sources close to the company. Microsoft
officials would not comment on the Longhorn reference implementation."

This is the referenced source they named. How does "developer sources close
to the company" equate to "idle speculation on thier part"?

Windows "Longhorn" is still a significant time away and system
requirements for it are no where near being set.
A lot can happen in the hardware world in timescales measured in
years.

For real information on Windows "Longhorn" see:-

http://msdn.microsoft.com/Longhorn/understanding/preparing/default.aspx
and
http://msdn.microsoft.com/Longhorn/default.aspx

http://slashdot.org/articles/04/05/04/2223237.shtml?tid=137&tid=185&tid=190&
--
hermes
DRM sux! Treacherous Computing kills our virtual civil liberties!
http://www.cl.cam.ac.uk/~rja14/tcpa-faq.html

Windows XP crashed.
I am the Blue Screen of Death.
No one hears your screams.

Yesterday it worked.
Today it is not working.
Windows is like that.

 

[Art]

Thanks again for all the information. :>

message : : >
: > "That's according to developer sources close to the company.
Microsoft
: > officials would not comment on the Longhorn reference
implementation."
: >
: > This is the referenced source they named. How does "developer
sources
: close
: > to the company" equate to "idle speculation on thier part"?
: >
:
: For accurate developer information not from some one close to but
directly
: from us to them you can see details of the specs and possible
requirements
: for graphics subsystems at
: http://www.microsoft.com/whdc/device/display/graphics-reqs.mspx
: If you look at the Aero and even at the Glass Aero specs you will
see these
: are actually still in the bounds of today's graphics cards and not
the
: speculated " graphics processor that runs three times faster than
those on
: the market today"
:
: Best not to listen to rumour and third party speculation.
: If you are interested in deep technical requirements for device
support in
: Windows Longhorn you can find out more at
: http://www.microsoft.com/whdc/driver/LDK/default.mspx
:
: This is the same information we give the OEMs and the "developer
sources
: close to the company"
:
: --
: Regards,
:
: Mike
: --
: Mike Brannigan [Microsoft]
:
: This posting is provided "AS IS" with no warranties, and confers no
: rights
:
: Please note I cannot respond to e-mailed questions, please use these
: newsgroups
:
: : > Before the MVP (M$ Victim Poster) Hermes responded, Mike Brannigan
: > [MSFT] typed:
: > > : > >> greg_barton writes "At first I thought this was a joke, but
this
: > >> article from Microsoft Watch confirms it: 'Microsoft is
expected to
: > >> recommend that the 'average' Longhorn PC feature a dual-core
CPU
: > >> running at 4 to 6GHz; a minimum of 2 gigs of RAM; up to a
terabyte
: > >> of storage; a 1 Gbit, built-in, Ethernet-wired port and an
802.11g
: > >> wireless link; and a graphics processor that runs three times
faster
: > >> than those on the market today.'"
: > >>
: > >>
: > >
: >
:
http://slashdot.org/articles/04/05/04/2223237.shtml?tid=137&tid=185&tid=190&
: > >> tid=201
: > >>
: > >> http://www.microsoft-watch.com/article2/0,1995,1581842,00.asp
: > >>
: > >> Heh, that brings up one heck of a feasibility issue!
: > >>
: > >
: > > A piece of idle speculation on their part.
: > > Also be very careful with phrase such as "... Microsoft Watch
: > > confirms it: 'Microsoft is expected ..."
: > > A third party publication confirms nothing if it prints an
: > > expectation based on no referenced source.
: >
: > "That's according to developer sources close to the company.
Microsoft
: > officials would not comment on the Longhorn reference
implementation."
: >
: > This is the referenced source they named. How does "developer
sources
: close
: > to the company" equate to "idle speculation on thier part"?
: >
: > > Windows "Longhorn" is still a significant time away and system
: > > requirements for it are no where near being set.
: > > A lot can happen in the hardware world in timescales measured in
: > > years.
: > >
: > > For real information on Windows "Longhorn" see:-
: > >
: > >
http://msdn.microsoft.com/Longhorn/understanding/preparing/default.aspx
: > > and
: > > http://msdn.microsoft.com/Longhorn/default.aspx
: > >
: > > --
: > > Regards,
: > >
: > > Mike
: > >
: > > : > >> greg_barton writes "At first I thought this was a joke, but
this
: > >> article from Microsoft Watch confirms it: 'Microsoft is
expected to
: > >> recommend that the 'average' Longhorn PC feature a dual-core
CPU
: > >> running at 4 to 6GHz; a minimum of 2 gigs of RAM; up to a
terabyte
: > >> of storage; a 1 Gbit, built-in, Ethernet-wired port and an
802.11g
: > >> wireless link; and a graphics processor that runs three times
faster
: > >> than those on the market today.'"
: > >>
: > >>
: > >
: >
:
http://slashdot.org/articles/04/05/04/2223237.shtml?tid=137&tid=185&tid=190&
: > >> tid=201
: > >>
: > >> http://www.microsoft-watch.com/article2/0,1995,1581842,00.asp
: > >>
: > >> Heh, that brings up one heck of a feasibility issue!
: > >>
: > >> --
: > >> hermes
: > >> DRM sux! Treacherous Computing kills our virtual civil
liberties!
: > >> http://www.cl.cam.ac.uk/~rja14/tcpa-faq.html
: > >>
: > >> Windows XP crashed.
: > >> I am the Blue Screen of Death.
: > >> No one hears your screams.
: > >>
: > >> Yesterday it worked.
: > >> Today it is not working.
: > >> Windows is like that.
: >
: > --
: > hermes
: > DRM sux! Treacherous Computing kills our virtual civil liberties!
: > http://www.cl.cam.ac.uk/~rja14/tcpa-faq.html
: >
: > Windows XP crashed.
: > I am the Blue Screen of Death.
: > No one hears your screams.
: >
: > Yesterday it worked.
: > Today it is not working.
: > Windows is like that.
: >
: >
:
:

 

[Art]

Remember Longhorn is a work in progress and probably will not be
released until early 2007.

: > "That's according to developer sources close to the company.
Microsoft
: > officials would not comment on the Longhorn reference
implementation."
: >
: > This is the referenced source they named. How does "developer
sources
: close
: > to the company" equate to "idle speculation on thier part"?
:
: Because it doesn't give you any more information than saying "yeah,
this guy
: I know... well, he heard from his girlfriend's sister's friend's
aunt's..."
:
: You're making an assumption that because someone is simply
identified as
: being "close to" Microsoft that they actually have an idea of what's
going
: on, which isn't necessarily the case. "Close to" could mean that
the guy or
: gal has an apartment near the Microsoft campus, for all we know.
:
: I'm not saying that the information in the article is wrong - I
don't know
: what the recommended hardware requirements will be. All I'm saying
is that
: you shouldn't put a lot of faith in that information until you get
it from
: the people who actually *know*. In this case, that's Microsoft.
:
: --
: Mike Kolitz MCSE 2000
: MS-MVP - Windows Setup & Deployment
:
:
: : > Before the MVP (M$ Victim Poster) Hermes responded, Mike Brannigan
: > [MSFT] typed:
: > > : > >> greg_barton writes "At first I thought this was a joke, but
this
: > >> article from Microsoft Watch confirms it: 'Microsoft is
expected to
: > >> recommend that the 'average' Longhorn PC feature a dual-core
CPU
: > >> running at 4 to 6GHz; a minimum of 2 gigs of RAM; up to a
terabyte
: > >> of storage; a 1 Gbit, built-in, Ethernet-wired port and an
802.11g
: > >> wireless link; and a graphics processor that runs three times
faster
: > >> than those on the market today.'"
: > >>
: > >>
: > >
: >
:
http://slashdot.org/articles/04/05/04/2223237.shtml?tid=137&tid=185&tid=190&
: > >> tid=201
: > >>
: > >> http://www.microsoft-watch.com/article2/0,1995,1581842,00.asp
: > >>
: > >> Heh, that brings up one heck of a feasibility issue!
: > >>
: > >
: > > A piece of idle speculation on their part.
: > > Also be very careful with phrase such as "... Microsoft Watch
: > > confirms it: 'Microsoft is expected ..."
: > > A third party publication confirms nothing if it prints an
: > > expectation based on no referenced source.
: >
: > "That's according to developer sources close to the company.
Microsoft
: > officials would not comment on the Longhorn reference
implementation."
: >
: > This is the referenced source they named. How does "developer
sources
: close
: > to the company" equate to "idle speculation on thier part"?
: >
: > > Windows "Longhorn" is still a significant time away and system
: > > requirements for it are no where near being set.
: > > A lot can happen in the hardware world in timescales measured in
: > > years.
: > >
: > > For real information on Windows "Longhorn" see:-
: > >
: > >
http://msdn.microsoft.com/Longhorn/understanding/preparing/default.aspx
: > > and
: > > http://msdn.microsoft.com/Longhorn/default.aspx
: > >
: > > --
: > > Regards,
: > >
: > > Mike
: > >
: > > : > >> greg_barton writes "At first I thought this was a joke, but
this
: > >> article from Microsoft Watch confirms it: 'Microsoft is
expected to
: > >> recommend that the 'average' Longhorn PC feature a dual-core
CPU
: > >> running at 4 to 6GHz; a minimum of 2 gigs of RAM; up to a
terabyte
: > >> of storage; a 1 Gbit, built-in, Ethernet-wired port and an
802.11g
: > >> wireless link; and a graphics processor that runs three times
faster
: > >> than those on the market today.'"
: > >>
: > >>
: > >
: >
:
http://slashdot.org/articles/04/05/04/2223237.shtml?tid=137&tid=185&tid=190&
: > >> tid=201
: > >>
: > >> http://www.microsoft-watch.com/article2/0,1995,1581842,00.asp
: > >>
: > >> Heh, that brings up one heck of a feasibility issue!
: > >>
: > >> --
: > >> hermes
: > >> DRM sux! Treacherous Computing kills our virtual civil
liberties!
: > >> http://www.cl.cam.ac.uk/~rja14/tcpa-faq.html
: > >>
: > >> Windows XP crashed.
: > >> I am the Blue Screen of Death.
: > >> No one hears your screams.
: > >>
: > >> Yesterday it worked.
: > >> Today it is not working.
: > >> Windows is like that.
: >
: > --
: > hermes
: > DRM sux! Treacherous Computing kills our virtual civil liberties!
: > http://www.cl.cam.ac.uk/~rja14/tcpa-faq.html
: >
: > Windows XP crashed.
: > I am the Blue Screen of Death.
: > No one hears your screams.
: >
: > Yesterday it worked.
: > Today it is not working.
: > Windows is like that.
: >
: >
:
:

 

[hermes]

Before the MVP (M$ Victim Poster) Hermes responded, Mike Kolitz typed:
::: "That's according to developer sources close to the company.
::: Microsoft officials would not comment on the Longhorn reference
::: implementation."
:::
::: This is the referenced source they named. How does "developer
::: sources close to the company" equate to "idle speculation on thier
::: part"?
::
:: Because it doesn't give you any more information than saying "yeah,
:: this guy I know... well, he heard from his girlfriend's sister's
:: friend's aunt's..."
::
:: You're making an assumption that because someone is simply
:: identified as being "close to" Microsoft that they actually have an
:: idea of what's going on, which isn't necessarily the case. "Close
:: to" could mean that the guy or gal has an apartment near the
:: Microsoft campus, for all we know.
::
:: I'm not saying that the information in the article is wrong - I
:: don't know what the recommended hardware requirements will be. All
:: I'm saying is that you shouldn't put a lot of faith in that
:: information until you get it from the people who actually *know*.
:: In this case, that's Microsoft.
::
:: --
:: Mike Kolitz MCSE 2000
:: MS-MVP - Windows Setup & Deployment

I see your point Mike, and what you say makes sense. But I tend to trust
any source which does not have a proven criminal background much more than
one that does have a proven criminal history.

--
hermes
DRM sux! Treacherous Computing kills our virtual civil liberties!
http://www.cl.cam.ac.uk/~rja14/tcpa-faq.html

Windows XP crashed.
I am the Blue Screen of Death.
No one hears your screams.

Yesterday it worked.
Today it is not working.
Windows is like that.

::
::
:: ::: Before the MVP (M$ Victim Poster) Hermes responded, Mike Brannigan
::: [MSFT] typed:
:::: ::::: greg_barton writes "At first I thought this was a joke, but this
::::: article from Microsoft Watch confirms it: 'Microsoft is expected
::::: to recommend that the 'average' Longhorn PC feature a dual-core
::::: CPU running at 4 to 6GHz; a minimum of 2 gigs of RAM; up to a
::::: terabyte of storage; a 1 Gbit, built-in, Ethernet-wired port and
::::: an 802.11g wireless link; and a graphics processor that runs
::::: three times faster than those on the market today.'"
:::::
:::::
::::
:::
::
http://slashdot.org/articles/04/05/04/2223237.shtml?tid=137&tid=185&tid=190&
::::: tid=201
:::::
::::: http://www.microsoft-watch.com/article2/0,1995,1581842,00.asp
:::::
::::: Heh, that brings up one heck of a feasibility issue!
:::::
<snip>

 

[Bruce Chambers]

Greetings --

Because it's the journalistic equivalent of "A guy my brother's
friend's uncle knows..." Hold on to your credulity until they can
name names.

Bruce Chambers

--
Help us help you:




You can have peace. Or you can have freedom. Don't ever count on
having both at once. -- RAH

 

[Art]

The release date of Longhorn is not set (from Microsoft)and as far as
I know neither are the system requirements as of yet.

: Greetings --
:
: Because it's the journalistic equivalent of "A guy my brother's
: friend's uncle knows..." Hold on to your credulity until they can
: name names.
:
: Bruce Chambers
:
:
: ::
::
:: This is the referenced source they named. How does "developer
:: sources close
:: to the company" equate to "idle speculation on thier part"?

 

[Alex Nichol]

I see your point Mike, and what you say makes sense.

Bear in mind that a lot of people got the preview at the PDC and have
been running it on modest machines compared with that suggestion. And
that probably has a lot of early inefficient code, with debugging
extras.

I think it more likely that someone speculated that by say 2007/8 (when
Longhorn will be mainstream) an average machine will quite probably be
something like that, and so Longhorn has to be designed to work
effectively on it. The author has then made the quite unjustified
deduction that the base machine will need to be way up there too - this
is like all the people we see around here claiming you need maybe a 2
GHz/ 1 GB machine to run XP. But it makes a story - journalists like
this are never too worried about underlying fact

 

[Art]

Can we say sensational journalism? LOL

: hermes wrote:
:
: >I see your point Mike, and what you say makes sense.
:
: Bear in mind that a lot of people got the preview at the PDC and
have
: been running it on modest machines compared with that suggestion.
And
: that probably has a lot of early inefficient code, with debugging
: extras.
:
: I think it more likely that someone speculated that by say 2007/8
(when
: Longhorn will be mainstream) an average machine will quite probably
be
: something like that, and so Longhorn has to be designed to work
: effectively on it. The author has then made the quite unjustified
: deduction that the base machine will need to be way up there too -
this
: is like all the people we see around here claiming you need maybe a
2
: GHz/ 1 GB machine to run XP. But it makes a story - journalists
like
: this are never too worried about underlying fact
:
:
: --
: Alex Nichol MS MVP (Windows Technologies)
: Bournemouth, U.K. (e-mail address removed)8E8L.org (remove the D8 bit)