Recommended Posts

I have both a legal and illegal copy of xp pro. Honestly when I format I use the illegal copy to install because 1, it has sp1 already where as my legal copy doesn't. and 2 I don't have to call ms and tell them why my key is being used again like I do when I use my legal copy.

So I could care less if they do this or not. If they block illegal copies then I'll just use my legal one...

  • 4 weeks later...
You kidz might wanna check this one out. :p

Microsoft Corrects: No XP SP2 for Pirated Copies.

The original link did look a bit fishy to me as well.

/me shrugs.

Welcome to neowin.

I won't flame you like others might, but I'll let you know that generally it isn't a good move to bump a thread that is about a month old. :)

  • 3 weeks later...
I have both a legal and illegal copy of xp pro. Honestly when I format I use the illegal copy to install because 1, it has sp1 already where as my legal copy doesn't. and 2 I don't have to call ms and tell them why my key is being used again like I do when I use my legal copy.

So I could care less if they do this or not. If they block illegal copies then I'll just use my legal one...

Just wait for the slipstreamed iso with SP2. ;)

:rolleyes: The 640 means absolutely nothing when it comes to legal/illegal keys. Do you guys honestly think there's a little flag in all the keygens and the illegal keys that says "I'm illegal!" when you install it? You think Windows just says "Oh, ok, I'll use this illegal one anyway, I just won't activate"... WTF!?! Get a clue before you guys spout off garbage. There's a special forumla that Windows uses to verify a key, and a special generator at Microsoft that generates the keys. Sure, they will have info in them like retail, OEM, VLK, etc. but Windows can't possibly know if it's a pirated key. If it did, don't you think you'd all be ******? The thing is, Microsoft put code in the key validation sequence of SP1 and higher to check the key you entered against a blacklist of known pirated keys. If the key you enter is in that list, Windows won't accept it, even though the RTM version would have (because it's a legal key, it's use is just out of control). Microsoft can add to this blacklist whenever they please, and this is what you have to worry about.

What was said in that thread could have been a rumor. Don't believe everything you hear online. Unless you have personal experience with something, how can you ever be sure of how it works? ;)

it was confirmed by many people.... legit corp editions have a 640 PID, and the blue list Keegan makes other keys too, so ms blacklisted the other PIDs

a keygen was made to generate 640 PIDs only

The only thing that ticks me off about XP is that you have to call MS to activate your computer if you make hardware changes. I'll rather put up with a MAC or Linux over crap like that.

I want to control when and how many times i reinstall XP. It's not like they charged $20.00 for the software in the first place. All of windows OS's are based on the previous Predecessor from 98 - XP and the price is always the same as if it's all new code being written.

it was confirmed by many people.... legit corp editions have a 640 PID, and the blue list Keegan makes other keys too, so ms blacklisted the other PIDs

a keygen was made to generate 640 PIDs only

I know about that. But what are you saying? How does any of this suggest that SP2 will or will not block more keys?

The only thing that ticks me off about XP is that you have to call MS to activate your computer if you make hardware changes. I'll rather put up with a MAC or Linux over crap like that.

I want to control when and how many times i reinstall XP. It's not like they charged $20.00 for the software in the first place. All of windows OS's are based on the previous Predecessor from 98 - XP and the price is always the same as if it's all new code being written.

Give me a break :rolleyes: Activation takes maybe 5 minutes, and it's a free call. Assuming you don't install everything that you can find, you shouldn't have to reinstall XP that often. If you learn just a little bit about the insides of XP, you should rarely have to reinstall it, i mean like once in maybe several years.

And FYI - there are two lines of Windows (well, only one now). Windows 2000 and XP are versions of Windows NT, which was written more or less from the ground up with IBM during the OS/2 project...

it was confirmed by many people.... legit corp editions have a 640 PID, and the blue list Keegan makes other keys too, so ms blacklisted the other PIDs

a keygen was made to generate 640 PIDs only

If that were true, then a lot of people who acquired VLKs through Universities, MSDN, MSDAA, etc. won't be able to install SP2 :p Does that really make sense? ...I think not

I know about that. But what are you saying? How does any of this suggest that SP2 will or will not block more keys?

Circaflex said that certain PID numbers are going to be blacklisted, you said it might be a rumor.

All i did was confirm there really are certain PID numbers (ie certain keys) blocked in SP2 (RC2 at least) which worked fine in SP1.

Of course everything can change in the final...

i don't like helping a month old bumped thread stay in the main page :unsure:

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • Absolutely NOBODY has suggested such a conclusion. I am affirming the sober reality check that AV2's overall market adoption will take longer than AV1's adoption rate -- which, by the way, is the whole point of the article! While PCI-SIG is productive (on paper), other WGs have created all sorts of confusing progress plans that consumers have tuned-out of their improvements... HTML/W3C, USB, HDMI, BT, WIFI (ieee802.11) as a few other groups where spec naming conventions, split progress paths, overlapping ambitions... I'm not critiquing the AV specs group; I'm simply affirming that adoption for AV2 faces headwinds beyond the macroeconomics of it all.
    • Segra 1.5.2 by Razvan Serea Segra is a free, open-source OBS-powered game recorder offering fast gameplay capture, instant clips, AI highlights, deep game integration, and seamless uploads—perfect for gamers, streamers, and content creators. Lightweight, fast, zero bloat. Segra key features: Automatic Game Recording: Begin capturing gameplay the moment your game launches, with zero manual setup. Instant Clipping: Save important moments instantly using a customizable hotkey—perfect for highlights, montages, or quick shares. Segra AI Highlights: Let Segra automatically detect kills, assists, deaths, and key events to generate polished highlight reels without manual editing. Gameplay Uploads: Upload recordings and clips directly to Segra.tv for fast sharing and cloud access. Deep Game Integration: Enjoy advanced game-data tracking across hundreds of supported titles, enabling smart highlight generation and stat-informed clipping. High-Performance Capture: Record up to 4K at 144 FPS using OBS-powered technology with minimal performance impact, supporting NVENC, AMD VCE, and custom quality controls. Segra Editor: Edit recordings easily with timeline controls, segment management, and event-based navigation to build the perfect clip. Customization Options: Adjust hotkeys, output formats, storage paths, codecs, capture quality, and performance settings for a tailored recording experience. Segra 1.5.2 changelog: Settings: Added an Airplane Mode that hides account, login, and upload features. Storage: Added a button to migrate videos into the recording path after changing it. Import: Added auto-scroll and a highlight pulse to videos right after importing. Recording: Added graceful handling of low disk space and output failures, finalizing files safely with clear errors. Recording: Added a guard blocking recording when any drive exceeds 99% full. OBS: Removed the download timeout to support users with slow internet. Clips: Fixed an error modal incorrectly appearing when clip creation was cancelled. Settings: Fixed the content folder path not refreshing in the UI after changes. Updates: Improved error handling for multiple simultaneous update checks. Stability: Fixed a WebSocket reconnect loop that ran while the window was backgrounded. Dependencies: Updated project dependencies. Maintenance: Removed dead code, reduced duplication, and fixed several latent bugs. Download: Segra 1.5.2 | 73.1 MB (Open Source) View: Segra Homepage | Github | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • No thanks! WebView trash is unacceptable. I only use software that's native.
  • Recent Achievements

    • Collaborator
      Asgardi earned a badge
      Collaborator
    • Conversation Starter
      mobandz earned a badge
      Conversation Starter
    • Apprentice
      fernan99 went up a rank
      Apprentice
    • One Month Later
      nothanks earned a badge
      One Month Later
    • One Month Later
      B2Proxy earned a badge
      One Month Later
  • Popular Contributors

    1. 1
      +primortal
      468
    2. 2
      PsYcHoKiLLa
      245
    3. 3
      Skyfrog
      79
    4. 4
      FloatingFatMan
      69
    5. 5
      Michael Scrip
      60
  • Tell a friend

    Love Neowin? Tell a friend!