WES Eval time bug

  • Thread starter Thread starter Henning
  • Start date Start date
Image, the 120 days evaluation time has became 48 (useful) hours. After that
it consumes 100% cpu. See wpabaln.exe topic.

Well, also when I load XPFull in the target designer I can go and have
luch/coffe while it loads...

/Henning
 
Something isn't right. It should be 120 days. Is the time/date on the target
close to the time/date of the development system?

--
Regards,

Sean Liming
www.sjjmicro.com / www.seanliming.com
Book Author - XP Embedded Advanced, XP Embedded Supplemental Toolkit
 
Yes, the clock has almost the same date/time (seconds diff) on the HW.
Same thing if run on the target HW, or in a VirtualBox.

It looks bad that M$ is trying to sell a $900+ late beta for evaluation.
The mentioned problem is reported to dissapear if one buys a license.
Another thing is when building a Swedish install, not everything is like in
a Swedish XP Pro, there is still NOT Swedish texts for examle in cmd and in
the controlpanel and elsewhere.

/Henning
 
You must log in or register to reply here.

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

Moving from Eval Toolkit to Full Toolkit 1
problem going from eval to licensed development environment 1
How to install DUA script compiler? 1
Javascript to retrieve Gridview cell text 1
XPE - Full Version Vs Evaluation 2
eval can't find function 7
will not eval a function name from a table. 3
registered copy still thinks it's eval 1

Back
Top