Hi, i got my eval copy of win xp 64 pro bout a month ago. today i installed a
new OCZ ram chip and needed to reset cmos so i could boot. i forgot to reset
the time ...then booted into 64 and it said "this copys time for evaluation
is up" or close to that. i've reset the clock now but error still happens.
any suggestions?

RE: Eval. period over after about a month? by Darrellg

Darrellg
Wed Nov 30 12:36:10 CST 2005

Hello John,
Your choices are to upgrade to a non-eval version or to reinstall clean the
64-bit eval version.
Changing the time, caused the OS to expire. There isn't a way to reset
this once it occurs other than upgrading to non-eval media.
Installing clean however would give you another 120 days.
Thanks,
Darrell Gorter[MSFT]

This posting is provided "AS IS" with no warranties, and confers no rights
--------------------
<Thread-Topic: Eval. period over after about a month?
<thread-index: AcX0oTL1iVI4kVaGS2KF9e31P947zg==
<X-WBNR-Posting-Host: 71.197.142.229
<From: "=?Utf-8?B?am9obiAxOQ==?=" <john 19@discussions.microsoft.com>
<Subject: Eval. period over after about a month?
<Date: Mon, 28 Nov 2005 20:56:03 -0800
<Lines: 5
<Message-ID: <2F9483BD-9F03-48FC-9612-2882308B8468@microsoft.com>
<MIME-Version: 1.0
<Content-Type: text/plain;
< charset="Utf-8"
<Content-Transfer-Encoding: 7bit
<X-Newsreader: Microsoft CDO for Windows 2000
<Content-Class: urn:content-classes:message
<Importance: normal
<Priority: normal
<X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
<Newsgroups: microsoft.public.windows.64bit.general
<NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
<Path: TK2MSFTNGXA02.phx.gbl!TK2MSFTNGXA03.phx.gbl
<Xref: TK2MSFTNGXA02.phx.gbl microsoft.public.windows.64bit.general:22932
<X-Tomcat-NG: microsoft.public.windows.64bit.general
<
<Hi, i got my eval copy of win xp 64 pro bout a month ago. today i
installed a
<new OCZ ram chip and needed to reset cmos so i could boot. i forgot to
reset
<the time ...then booted into 64 and it said "this copys time for
evaluation
<is up" or close to that. i've reset the clock now but error still happens.
<any suggestions?
<