Hi.
What are all those strange characters starting with =?
They seem to clutter up posts with mime attached html.
~r tma
Hi.
Please forgive if you really want to attach html.
Please check the date on this.
I am a few days behind reading email.
You may have already fixed this problem.
Do you know that you are posting in mime attached duplicate html?
Can you please explain why the mime attached html?
If so, may I please ask which mail program is creating these html attachments,
under which OS, and why?
I am absolutely certain that it is not my mail program, or anything on my end,
though your mail program may hide them from you.
This is why others may not have pointed out the mime attached html problem.
Your mime attached html post, which I have appended,
is exactly what I received.
Are you using html to display anything other than plain text?
Unless you really are using the html features,
the defaults should be set to both post and answer in plain text,
or uuencode, if plain text is not an option.
your answer mode should also be set to
answer in plain text, or answer in uuencode,
not to answer in kind.
I am most concerned about viruses in unintended attachments.
If you must quote me, please put your comments first.
I have already listened to mine.
I read email with speech.
So it is not possible to scroll past the quotes without listening to them again,
to quickly get to the new information.
The mime attached html is far from speech friendly!
--
Thanks much again as always.
From [log in to unmask] Mon Jan 29 15:08:59 2007
Return-Path: <[log in to unmask]>
Received: from pagent1.arc.nasa.gov (pagent1.arc.nasa.gov [128.102.31.161])
by arc.nasa.gov (8.13.8/8.13.8) with ESMTP id l0TN8rki011028
for <[log in to unmask]>; Mon, 29 Jan 2007 15:08:53 -0800 (PST)
Received: from lychee.ease.lsoft.com (lychee.ease.lsoft.com [209.119.0.145])
by pagent1.arc.nasa.gov (8.12.11.20060308/8.12.11) with ESMTP id l0TN5FbL018164
for <[log in to unmask]>; Mon, 29 Jan 2007 15:05:15 -0800
Received: from ORANGE ([209.119.0.68]) by lychee.ease.lsoft.com (StrongMail Enterprise 1.0-6(2.00.238)); Mon, 29 Jan 2007 18:05:15 -0500
X-Mailer: StrongMail Enterprise 1.0-6(2.00.238)
X-SMHeaderMap: mid="X-MailingID"
X-MailingID: 00000::00000::00000::00000::<mailto:[log in to unmask]>::342575
X-Destination-ID: <[log in to unmask]>
X-VirtualServerGroup: UNDEF
Received: by LISTSERV.ICORS.ORG (LISTSERV-TCP/IP release 14.5) with spool id
14371982 for [log in to unmask]; Mon, 29 Jan 2007 18:05:14
-0500
Received: from [89.145.219.86] by ORANGE.HOSTING.LSOFT.COM (SMTPL release 1.0r)
with TCP; Mon, 29 Jan 2007 18:05:14 -0500
MIME-Version: 1.0
Content-Type: multipart/alternative;
boundary="----_=_NextPart_001_01C743F9.ED766FEC"
Content-class: urn:content-classes:message
X-MimeOLE: Produced By Microsoft Exchange V6.5
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [VICUG-L] FW: VISTA "Upgrade" Drops Compliance Checking,
Requires Old OS to Install
Thread-Index: AcdDjsv7Pi7/0e9MRcW4vfyNWRX1tQATIJYQAABw+nAAAMFJkAAGT7dQ
References: A<02ed01c743e0$2ea37cb0$1a90ba44@christestcmp>
Message-ID: <[log in to unmask]>
Date: Mon, 29 Jan 2007 23:05:17 -0000
Reply-To: George Bell <[log in to unmask]>
Sender: "Visually Impaired Computer Users' Group List" <[log in to unmask]>
From: George Bell <[log in to unmask]>
Subject: Re: [VICUG-L] FW: VISTA "Upgrade" Drops Compliance Checking, Requires Old OS to Install
X-To: Christopher McMillan <[log in to unmask]>
To: [log in to unmask]
In-Reply-To: A<02ed01c743e0$2ea37cb0$1a90ba44@christestcmp>
Precedence: list
List-Help: <http://listserv.icors.org/SCRIPTS/WA-ICORS.EXE?LIST=VICUG-L>,
<mailto:[log in to unmask] VICUG-L>
List-Unsubscribe: <mailto:[log in to unmask]>
List-Subscribe: <mailto:[log in to unmask]>
List-Owner: <mailto:[log in to unmask]>
List-Archive: <http://listserv.icors.org/SCRIPTS/WA-ICORS.EXE?LIST=VICUG-L>
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 mlx=0 adultscore=0 adjust=0 reason=mlx engine=3.0.0-0701160000 definitions=main-0701290048
X-Scanned-By: MIMEDefang 2.58 on 128.102.119.101
Status: RO
Content-Length: 23391
This is a multi-part message in MIME format.
------_=_NextPart_001_01C743F9.ED766FEC
Content-Type: text/plain;
charset="windows-1250"
Content-Transfer-Encoding: quoted-printable
Oh boy! What a shame. You won=92t be able to simply buy an
upgrade for your brand new system, and share an XP disk
between friends.
=20
Sorry, but finally Microsoft are leading the way, and of
course other much poorer software developers, who have been
ripped off for ages now, will follow.
=20
Not before time!
=20
George.
=20
_____ =20
From: Visually Impaired Computer Users' Group List
[mailto:[log in to unmask]] On Behalf Of Christopher
McMillan
Sent: 29 January 2007 20:01
To: [log in to unmask]
Subject: [VICUG-L] FW: VISTA "Upgrade" Drops Compliance
Checking, Requires Old OS to Install
Importance: High
=20
Vista "upgrade" drops compliance checking, requires old OS
to install=20
1/28/2007 3:11:14 PM, by HYPERLINK
"http://arstechnica.com/staff/palatine.ars"Ken Fisher
Microsoft's quest to closely control the way Windows Vista
can be used on PCs has taken a turn for the worse as new
information indicates that the company is breaking tradition
when it comes to Windows Vista upgrades. With Windows Vista,
users will not be able to use upgrade keys to initiate
completely new installations. It is a change that will
affect few users, but enthusiasts will certainly be amongst
those pinched.=20
Upgrade versions of Windows Vista Home Basic, Premium, and
Starter Edition will not install on any PC unless Windows XP
or Windows 2000 is already on the machine in question. In
years previous, upgrade versions of Windows could be
installed on any PC. If a PC did not have an older version
of Windows installed, users could provide an older
installation CD of Windows for verification. After dropping
a qualifying CD in the CD-ROM drive, the installation
routine would verify the disc and you'd be on your way. With
this approach, one could use an "upgrade" copy of Windows to
lay a new Windows install on a computer.=20
One again, Microsoft appears to have made licensing
decisions without considering how people actually use their
products. Last fall the company trotted out changes to its
retail licensing that HYPERLINK
"http://arstechnica.com/news.ars/post/20061102-8140.html"wou
ld have punished users who frequently upgrade their PC
hardware had the company not relented. Now Microsoft seeks
to complicate our ability to start a crisp, new install with
an upgrade version. Why?=20
A 'per device' obsession
Microsoft has been adamant in recent years that Windows is
licensed per device and not per person. One practical
ramification of this viewpoint is that the company typically
does not allow users to install one copy of Windows across
multiple machines, even if only one machine is in use at a
time. According to Microsoft, only the full retail license
of Windows Vista can be transferred to new devices (
HYPERLINK
"http://arstechnica.com/news.ars/post/20060905-7663.html"ret
ail pricing here). HYPERLINK
"http://arstechnica.com/news.ars/post/20070124-8696.html"OEM
versions are ostensibly tied to motherboards, and upgrade
versions are now technically tied to previous installations.
What does all of this mean on a practical level? Users who
purchase upgrade copies of the aforementioned versions of
Vista will find that they can only upgrade PCs that already
have Windows installed. HYPERLINK
"http://support.microsoft.com/default.aspx/kb/930985/en-us"K
B930985 clearly states: "you cannot use an upgrade key to
perform a clean installation of Windows Vista." According to
Microsoft, this happens because Windows Vista does not check
for upgrade compliance. If you do not have a previous
installation of Windows available, Microsoft recommends that
you "purchase a license that lets you perform a clean
installation of Windows Vista."=20
For its part, Microsoft seems to be confident that the Vista
repair process should be sufficient to solve any problems
with the OS, since otherwise the only option for disaster
recovery in the absence of backups would be to wipe a
machine, install XP, and then upgrade to Vista. This will
certainly make disaster recovery a more irritating
experience.=20
Fortunately, the change will not mean that users cannot
install Windows Vista to a new directory. Windows Vista's
upgrade process includes the option of backing up previous
installations, and in fact, HYPERLINK
"http://arstechnica.com/news.ars/post/20060730-7384.html"in
some scenarios a "clean" upgrade is required. "Clean" or
not, the requirement that the previous OS be installed puts
a bit of a damper on those of us that like the do periodic
system refreshes.=20
What does Microsoft hope to gain out of all of this? I can
only speculate. First, the change prevents a dual-license
situation with all of the free Vista upgrade coupons out
there. If things worked according to the old scheme, people
with upgrade coupons would essentially get a "free" OS
because they could install the Vista upgrade anywhere, and
continue to use the version of Windows XP that came with
their computer. Did Microsoft fear that this would happen
quite a bit? It seems like an unlikely scenario.=20
Second, and likely more important to Microsoft, this should
make it difficult for users to use a single upgrade copy of
Vista throughout the years. I'm quite sure many of you in
readerland have done exactly that in years past: build a
computer, use your Windows upgrade disc. Build a new box
three years later, use that same upgrade disc. Microsoft's
preference would be for users in such situations to either
purchase OEM copies for each new machine, or pay for a full
version of the retail product.=20
--=20
Sincerely,=20
Christopher McMillan
Rehabilitation Engineer
HYPERLINK
"http://www.ceektechnology.com"http://www.ceektechnology.com
HYPERLINK
"http://ceektechnology.spaces.live.com"http://ceektechnology
.spaces.live.com
HYPERLINK
"mailto:[log in to unmask]"[log in to unmask]
203 404 7275 Work Number
203 286 2156 Fax Number=20
Chrismcmillan Skype Username
HYPERLINK
"mailto:[log in to unmask]"christophermcmillan@
hotamil.com MSN Messenger Username=20
_____ =20
Leave list: HYPERLINK
"mailto:[log in to unmask]"vicug
[log in to unmask]
VICUG-L is archived on the World Wide Web at HYPERLINK
"http://listserv.icors.org/archives/vicug-l.html"http://list
serv.i cors.or g/archives/vicug-l.html=20
Send questions on list operation to HYPERLINK
"mailto:[log in to unmask]"vicug-l-request@l
istserv.icors.org=20
--
No virus found in this incoming message.
Checked by AVG Free Edition.
Version: 7.5.432 / Virus Database: 268.17.12/655 - Release
Date: 28/01/2007 13:12
--=20
No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.5.432 / Virus Database: 268.17.12/655 - Release
Date: 28/01/2007 13:12
=20
VICUG-L is the Visually Impaired Computer User Group List.
Archived on the World Wide Web at
http://listserv.icors.org/archives/vicug-l.html
Signoff: [log in to unmask]
Subscribe: [log in to unmask]
------_=_NextPart_001_01C743F9.ED766FEC
Content-Type: text/html;
charset="windows-1250"
Content-Transfer-Encoding: quoted-printable
<p>
<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:st1=3D"urn:schemas-microsoft-com:office:smarttags" =
xmlns=3D"http://www.w3.org/TR/REC-html40">
<head>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dwindows-1250">
<meta name=3DGenerator content=3D"Microsoft Word 11 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]--><o:SmartTagType
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags" =
name=3D"place"/>
<!--[if !mso]>
<style>
st1\:*{behavior:url(#default#ieooui) }
</style>
<![endif]-->
<style>
<!--
/* Font Definitions */
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman";}
h2
{mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:18.0pt;
font-family:"Times New Roman";
font-weight:bold;}
h3
{mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:13.5pt;
font-family:"Times New Roman";
font-weight:bold;}
a:link, span.MsoHyperlink
{color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{color:blue;
text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman";}
p
{mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:12.0pt;
font-family:"Times New Roman";}
p.newsdate, li.newsdate, div.newsdate
{mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:12.0pt;
font-family:"Times New Roman";}
span.EmailStyle20
{mso-style-type:personal;
font-family:"Times New Roman";
color:blue;
font-weight:normal;
font-style:normal;
text-decoration:none none;}
span.EmailStyle21
{mso-style-type:personal;
font-family:Arial;
color:blue;
font-weight:normal;
font-style:normal;
text-decoration:none none;}
span.EmailStyle22
{mso-style-type:personal;
font-family:Arial;
color:blue;
font-weight:normal;
font-style:normal;
text-decoration:none none;}
span.EmailStyle24
{mso-style-type:personal-reply;
font-family:Arial;
color:navy;}
@page Section1
{size:612.0pt 792.0pt;
margin:72.0pt 90.0pt 72.0pt 90.0pt;}
div.Section1
{page:Section1;}
-->
</style>
</head>
<body lang=3DEN-GB link=3Dblue vlink=3Dblue>
<div class=3DSection1>
<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>Oh boy! What a shame. =
You won’t be
able to simply buy an upgrade for your brand new system, and share an XP =
disk
between friends.<o:p></o:p></span></font></p>
<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p>
<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>Sorry, but finally Microsoft are =
leading
the way, and of course other much poorer software developers, who have =
been ripped
off for ages now, will follow.<o:p></o:p></span></font></p>
<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p>
<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>Not before =
time!<o:p></o:p></span></font></p>
<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p>
<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>George.<o:p></o:p></span></font></p>=
<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p>
<div>
<div class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font =
size=3D3
face=3D"Times New Roman"><span lang=3DEN-US style=3D'font-size:12.0pt'>
<hr size=3D2 width=3D"100%" align=3Dcenter tabindex=3D-1>
</span></font></div>
<p class=3DMsoNormal><b><font size=3D2 face=3DTahoma><span lang=3DEN-US
style=3D'font-size:10.0pt;font-family:Tahoma;font-weight:bold'>From:</spa=
n></font></b><font
size=3D2 face=3DTahoma><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:Tahoma'>
Visually Impaired Computer Users' Group List
[mailto:[log in to unmask]] <b><span =
style=3D'font-weight:bold'>On Behalf
Of </span></b>Christopher McMillan<br>
<b><span style=3D'font-weight:bold'>Sent:</span></b> 29 January 2007 =
20:01<br>
<b><span style=3D'font-weight:bold'>To:</span></b> =
[log in to unmask]<br>
<b><span style=3D'font-weight:bold'>Subject:</span></b> [VICUG-L] FW: =
<st1:place
w:st=3D"on">VISTA</st1:place> "Upgrade" Drops Compliance =
Checking,
Requires Old OS to Install<br>
<b><span style=3D'font-weight:bold'>Importance:</span></b> =
High</span></font><span
lang=3DEN-US><o:p></o:p></span></p>
</div>
<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'><o:p> </o:p></span></font></p>
<h2><st1:place w:st=3D"on"><strong><b><font size=3D5 face=3D"Times New =
Roman"><span
lang=3DEN-US =
style=3D'font-size:18.0pt'>Vista</span></font></b></strong></st1:place><s=
trong><b><font
face=3D"Times New Roman"><span lang=3DEN-US> "upgrade" drops =
compliance
checking, requires old OS to install</span></font></b></strong><span
lang=3DEN-US> <o:p></o:p></span></h2>
<p class=3Dnewsdate><font size=3D3 face=3D"Times New Roman"><span =
lang=3DEN-US
style=3D'font-size:12.0pt'>1/28/2007 3:11:14 PM, by <a
href=3D"http://arstechnica.com/staff/palatine.ars"><font =
color=3D"#008902"><span
style=3D'color:#008902'>Ken =
Fisher</span></font></a><o:p></o:p></span></font></p>
<p><font size=3D3 face=3D"Times New Roman"><span lang=3DEN-US =
style=3D'font-size:12.0pt'>Microsoft's
quest to closely control the way Windows Vista can be used on PCs has =
taken a turn
for the worse as new information indicates that the company is breaking
tradition when it comes to Windows Vista upgrades. With Windows Vista, =
users
will not be able to use upgrade keys to initiate <i><span =
style=3D'font-style:
italic'>completely new</span></i> installations. It is a change that =
will
affect few users, but enthusiasts will certainly be amongst those =
pinched. <o:p></o:p></span></font></p>
<p><font size=3D3 face=3D"Times New Roman"><span lang=3DEN-US =
style=3D'font-size:12.0pt'>Upgrade
versions of Windows Vista Home Basic, Premium, and Starter Edition will =
not
install on any PC unless Windows XP or Windows 2000 is <i><span
style=3D'font-style:italic'>already</span></i> on the machine in =
question. In years
previous, upgrade versions of Windows could be installed on any PC. If a =
PC did
not have an older version of Windows installed, users could provide an =
older
installation CD of Windows for verification. After dropping a qualifying =
CD in
the CD-ROM drive, the installation routine would verify the disc and =
you'd be
on your way. With this approach, one could use an "upgrade" =
copy of
Windows to lay a new Windows install on a computer. =
<o:p></o:p></span></font></p>
<p><font size=3D3 face=3D"Times New Roman"><span lang=3DEN-US =
style=3D'font-size:12.0pt'>One
again, Microsoft appears to have made licensing decisions without =
considering
how people actually use their products. Last fall the company trotted =
out
changes to its retail licensing that <a
href=3D"http://arstechnica.com/news.ars/post/20061102-8140.html"><font
color=3D"#008902"><span style=3D'color:#008902'>would have punished =
users who
frequently upgrade their PC hardware</span></font></a> had the company =
not
relented. Now Microsoft seeks to complicate our ability to start a =
crisp, new
install with an upgrade version. Why? <o:p></o:p></span></font></p>
<h3><b><font size=3D4 face=3D"Times New Roman"><span lang=3DEN-US =
style=3D'font-size:
13.5pt'>A 'per device' obsession<o:p></o:p></span></font></b></h3>
<p><font size=3D3 face=3D"Times New Roman"><span lang=3DEN-US =
style=3D'font-size:12.0pt'>Microsoft
has been adamant in recent years that Windows is licensed <i><span
style=3D'font-style:italic'>per device</span></i> and not <i><span
style=3D'font-style:italic'>per person</span></i>. One practical =
ramification of
this viewpoint is that the company typically does not allow users to =
install
one copy of Windows across multiple machines, even if only one machine =
is in
use at a time. According to Microsoft, only the full retail license of =
Windows
Vista can be transferred to new devices ( <a
href=3D"http://arstechnica.com/news.ars/post/20060905-7663.html"><font
color=3D"#008902"><span style=3D'color:#008902'>retail pricing =
here</span></font></a>).
<a =
href=3D"http://arstechnica.com/news.ars/post/20070124-8696.html"><font
color=3D"#008902"><span style=3D'color:#008902'>OEM versions =
</span></font></a>are
ostensibly tied to motherboards, and upgrade versions are now =
technically tied
to previous installations. <o:p></o:p></span></font></p>
<p><font size=3D3 face=3D"Times New Roman"><span lang=3DEN-US =
style=3D'font-size:12.0pt'>What
does all of this mean on a practical level? Users who purchase upgrade =
copies
of the aforementioned versions of <st1:place =
w:st=3D"on">Vista</st1:place> will
find that they can only upgrade PCs that already have Windows installed. =
<a
href=3D"http://support.microsoft.com/default.aspx/kb/930985/en-us"><font
color=3D"#008902"><span =
style=3D'color:#008902'>KB930985</span></font></a> clearly
states: "you cannot use an upgrade key to perform a clean =
installation of
Windows Vista." According to Microsoft, this happens because =
Windows Vista
does not check for upgrade compliance. If you do not have a previous
installation of Windows available, Microsoft recommends that you =
"purchase
a license that lets you perform a clean installation of Windows =
Vista." <o:p></o:p></span></font></p>
<p><font size=3D3 face=3D"Times New Roman"><span lang=3DEN-US =
style=3D'font-size:12.0pt'>For
its part, Microsoft seems to be confident that the Vista repair process =
should
be sufficient to solve any problems with the OS, since otherwise the =
only
option for disaster recovery in the absence of backups would be to wipe =
a
machine, install XP, and <i><span =
style=3D'font-style:italic'>then</span></i>
upgrade to <st1:place w:st=3D"on">Vista</st1:place>. This will certainly =
make
disaster recovery a more irritating experience. =
<o:p></o:p></span></font></p>
<p><font size=3D3 face=3D"Times New Roman"><span lang=3DEN-US =
style=3D'font-size:12.0pt'>Fortunately,
the change will not mean that users cannot install Windows Vista to a =
new
directory. Windows Vista's upgrade process includes the option of =
backing up
previous installations, and in fact, <a
href=3D"http://arstechnica.com/news.ars/post/20060730-7384.html"><font
color=3D"#008902"><span style=3D'color:#008902'>in some scenarios a
"clean" upgrade is required</span></font></a>. =
"Clean" or
not, the requirement that the previous OS be installed puts a bit of a =
damper
on those of us that like the do periodic system refreshes. =
<o:p></o:p></span></font></p>
<p><font size=3D3 face=3D"Times New Roman"><span lang=3DEN-US =
style=3D'font-size:12.0pt'>What
does Microsoft hope to gain out of all of this? I can only speculate. =
First,
the change prevents a dual-license situation with all of the free =
<st1:place
w:st=3D"on">Vista</st1:place> upgrade coupons out there. If things =
worked
according to the old scheme, people with upgrade coupons would =
essentially get
a "free" OS because they could install the <st1:place =
w:st=3D"on">Vista</st1:place>
upgrade anywhere, and continue to use the version of Windows XP that =
came with
their computer. Did Microsoft fear that this would happen quite a bit? =
It seems
like an unlikely scenario. <o:p></o:p></span></font></p>
<p><font size=3D3 face=3D"Times New Roman"><span lang=3DEN-US =
style=3D'font-size:12.0pt'>Second,
and likely more important to Microsoft, this should make it difficult =
for users
to use a single upgrade copy of <st1:place w:st=3D"on">Vista</st1:place>
throughout the years. I'm quite sure many of you in readerland have done
exactly that in years past: build a computer, use your Windows upgrade =
disc.
Build a new box three years later, use that same upgrade disc. =
Microsoft's
preference would be for users in such situations to either purchase OEM =
copies
for each new machine, or pay for a full version of the retail product. =
<o:p></o:p></span></font></p>
<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
lang=3DEN-US
style=3D'font-size:12.0pt'><br clear=3Dall>
<br>
-- <br>
Sincerely, <br>
<br>
Christopher McMillan<br>
Rehabilitation Engineer<br>
<a =
href=3D"http://www.ceektechnology.com">http://www.ceektechnology.com</a><=
br>
<a =
href=3D"http://ceektechnology.spaces.live.com">http://ceektechnology.spac=
es.live.com</a><br>
<a =
href=3D"mailto:[log in to unmask]">[log in to unmask]</a>&nbs=
p;
<br>
203 404
7275 &nb=
sp; &nbs=
p;
Work Number<br>
203 286
2156 &nb=
sp; &nbs=
p;
Fax Number <br>
Chrismcmillan =
&=
nbsp; Skype
Username<br>
<a =
href=3D"mailto:[log in to unmask]">christophermcmillan@hotam=
il.com</a> MSN
Messenger Username <o:p></o:p></span></font></p>
</div>
</body>
</html>
<hr>
<p>
Leave list:
<a href=3D"mailto:[log in to unmask]">
[log in to unmask]</a>
<p>
VICUG-L is archived on the World Wide Web at
<a
href=3D"http://listserv.icors.org/archives/vicug-l.html">http://listserv.=
i
cors.or g/archives/vicug-l.html</a>
<p>
Send questions on list operation to
<a href=3D"mailto:[log in to unmask] ">
[log in to unmask]</a>
<BR>
<FONT SIZE=3D2>--<BR>
No virus found in this incoming message.<BR>
Checked by AVG Free Edition.<BR>
Version: 7.5.432 / Virus Database: 268.17.12/655 - Release Date: =
28/01/2007 13:12<BR>
</FONT><BR>
<FONT SIZE=3D2>--<BR>
No virus found in this outgoing message.<BR>
Checked by AVG Free Edition.<BR>
Version: 7.5.432 / Virus Database: 268.17.12/655 - Release Date: =
28/01/2007 13:12<BR>
</FONT>
<hr>
<p>
Leave list:
<a href=3D"mailto:[log in to unmask]">
[log in to unmask]</a>
<p>
VICUG-L is archived on the World Wide Web at
<a
href=3D"http://listserv.icors.org/archives/vicug-l.html">http://listserv.i
cors.or g/archives/vicug-l.html</a>
<p>
Send questions on list operation to
<a href=3D"mailto:[log in to unmask] ">
[log in to unmask]</a>
------_=_NextPart_001_01C743F9.ED766FEC--
VICUG-L is the Visually Impaired Computer User Group List.
Archived on the World Wide Web at
http://listserv.icors.org/archives/vicug-l.html
Signoff: [log in to unmask]
Subscribe: [log in to unmask]
|
