Re: [suse-security] WindowsXP contact it's home ?!
At 09:10 AM 12/14/2001 -0800, you wrote:
If you consistently prevent XP from contacting Microsoft, it will quit working after sixty days.
Do you know this for a fact? That would imply that you can't run WindowsXP without an Internet connection, which I find hard to belive - there's still plenty of offices and home computers without Internet connections. Do you know this from eXperience (pun intended), or did you red that somewhere?
I think this particular call is just setting the system time, but the license code also depends on servers at Microsoft.
Bear
-- To unsubscribe, e-mail: suse-security-unsubscribe@suse.com For additional commands, e-mail: suse-security-help@suse.com
---------------------------------------------------- Jonathan Wilson System Administrator Cedar Creek Software http://www.cedarcreeksoftware.com Central Texas IT http://www.centraltexasit.com
On Fri, 14 Dec 2001, JW wrote:
At 09:10 AM 12/14/2001 -0800, you wrote:
If you consistently prevent XP from contacting Microsoft, it will quit working after sixty days.
Do you know this for a fact? That would imply that you can't run WindowsXP without an Internet connection, which I find hard to belive - there's still plenty of offices and home computers without Internet connections.
Do you know this from eXperience (pun intended), or did you red that somewhere?
I'm a QA analyst in my day job. We installed XP in our QA lab (which has no internet connections) to test software on when it first came out in MSDN. Sixty days later it quit working. Any attempt to boot on that box popped up a dialog telling us to get all the system information together and call Microsoft to get the license validation code. We never did though; we were shifting at that point to the NT testing phase, so we reimaged the XP machine instead. Microsoft started selling XP on October 25, so I figure a couple days before Christmas this is going to start biting the general public. Bear
Hi This is slighly off-topic, but I wonder, if this could be really true. Have you ever activated xp by phone or internet ? If not, this is the normal behavior. Windows stops working after a defined period without activating. Regards M. Rauter
I'm a QA analyst in my day job. We installed XP in our QA lab (which has no internet connections) to test software on when it first came out in MSDN. Sixty days later it quit working. Any attempt to boot on that box popped up a dialog telling us to get all the system information together and call Microsoft to get the license validation code. We never did though; we were shifting at that point to the NT testing phase, so we reimaged the XP machine instead.
Microsoft started selling XP on October 25, so I figure a couple days before Christmas this is going to start biting the general public.
Bear -- To unsubscribe, e-mail: suse-security-unsubscribe@suse.com For additional commands, e-mail: suse-security-help@suse.com
Am Freitag, 14. Dezember 2001 21:59 schrieb Ray Dillinger:
I'm a QA analyst in my day job. We installed XP in our QA lab (which has no internet connections) to test software on when it first came out in MSDN. Sixty days later it quit working. Any attempt to boot on that box popped up a dialog telling us to get all the system information together and call Microsoft to get the license validation code. We never did though; we were shifting at that point to the NT testing phase, so we reimaged the XP machine instead. Thats ok if You try to use a TIME-LIMITED version from MSDN. They stated this on the folder, on the disk and on the sideletter. If Microsoft say "This willnot work longer than 60 days" please believe them.
-- Mit freundlichen Grüßen / best regards Ing. Rainer Pietsch ---------------------------------------------------------- PCS - Claudia Pichler & Co. KEG Märzstraße 116 / 1-4 A-1150 Wien ---------------------------------------------------------- mail: r.pietsch@pcs-at.com web: http://www.pcs-at.com tel.: +43 (1) 98 52 693 / 15 fax.: +43 (1) 98 52 693 / 20 ----------------------------------------------------------
I have every right to be "down" on Microsoft, it's personal. The first time I ever heard of the company, its CEO started by tarring me and everybody who liked to share source code with the sentence "you are all thieves," and he's never apologized. I was horrified when DOS started to become popular since the CEO was already a known asshole. A few years later, he proved it again: Remember "DOS isn't done till Lotus won't run!" on a big banner over the cubicle farm in Redmond? At just about the time that MicroSoft was coming out with its own spreadsheet? Hey, if it was any good, why couldn't it have won in a fair competition? Or more to the point, if *THEY* were any good, why couldn't they have competed fairly? And now that there are alternatives available again, why do business with assholes? I have to learn Bill's crap because people use it at work. But as a QA analyst, I get to see first hand exactly how crappy it is under a serious stress test, and I wouldn't recommend it to anyone even if it were free. Hell, I wouldn't even recommend to anyone *STEALING* Microsoft software, because every bit of it you use malfunctions in irritating ways unless you're using other bits, and pretty soon life starts sucking real hard if you go that route, because some of the bits of it that other parts need are horribly buggy and just a Bad Idea to run (like outlook) or infuriating because they try do do things you don't want done (like word). So don't go getting on my case about being down on Microsoft, okay? I'm down on them for reasons that are valid, true, and deserved, and I'm not about to change. Sorry about the flamage, and I'll shut up about it now; but this is all true, and it needed to be said. Bear
participants (4)
-
JW -
Michael Rauter -
Rainer Pietsch -
Ray Dillinger