Jump to content

Welcome to MSFN Forum
Register now to gain access to all of our features. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, post status updates, manage your profile and so much more. This message will be removed once you have signed in.
Login to Account Create an Account



Photo

Confused with RTM versions? Read this

- - - - -

This topic has been archived. This means that you cannot reply to this topic.
14 replies to this topic

#1
Aaron

Aaron

    The MSFN Banana

  • Patrons
  • 5,767 posts
  • Joined 17-August 01
Last night and this morning, IRC has been plagued with questions and a lot of different answers/views were said. There was so much confusion going about. After reading for hours and hours it soon cleared up in my head, and these are the facts:

Windows XP is final, and has been released to manufacturers (RTM), It is build 2600 (not 2600.1 or 2600.3 or anything 2600.x its just build 2600)

The manufacturers have the OEM version, it has no 120/180 day evaluation timebomb included. It only has the 30 day activation. After 30 days you will be locked out. (This is called RTM OEM)

The RTM Build 2600 that appeared on WindowsBeta.mirosoft.com last night for beta testers is the final RTM build WITH the timebomb. So Beta Testers have the final copy, but they can't use it for very long. (This is called RTM Evaluation)

Neither versions (OEM and EVAL) have debug code.

The one we want leaked is the RTM OEM.

*** If you are having trouble understanding this, please reply with the parts you don't understand and I will try and make it more clearer as possible.


How to remove advertisement from MSFN

#2
XPerties

XPerties

    MSFN OG Senior

  • Patrons
  • 2,994 posts
  • Joined 18-August 01
There is no certian file name for the oem version. For instist last night a frined called me and said "Im downloading rtm 2600", when in fact he redownloaded the previous version of 2600 before rtm. Would you know if its something like windows_xp2600_oemrtm.whistler??.....Just a example. And Im sure when you find it youll post it...ya?


-Regards, Chris



You want some Glock with that?
★ :::: Xbox Live GamerTag = ScreamingSkulls


#3
Aaron

Aaron

    The MSFN Banana

  • Patrons
  • 5,767 posts
  • Joined 17-August 01
[img:8a6e7293e0]http://vzone.virgin.net/aaron.stevens/windowsbeta_rtm.gif[/img:8a6e7293e0]

Above, is WindowsBeta, which beta testers can access. As you can see, the RTM OEM is not available on there.

The second file "usa_2600_x86eval.pro_whistler.iso" is the final build, WITH the 120/180 day evaluation Timebomb.

#4
XPerties

XPerties

    MSFN OG Senior

  • Patrons
  • 2,994 posts
  • Joined 18-August 01
Thanks AaronXP



You want some Glock with that?
★ :::: Xbox Live GamerTag = ScreamingSkulls


#5
Benholio

Benholio
  • Member
  • 7 posts
  • Joined 21-August 01
I believe that the iso dates for RTM should be Wed Evening. So if you get a RTM and all the files are compiled Wed Evening/Thur morning then it is the OEM ISO.


Ben

#6
Zheka

Zheka
  • Member
  • 1 posts
  • Joined 25-August 01
Begin of SETUPREG.HIV must also contain something else, than .R.e.t.a.i.l..o.b.j..i.3.8.6..T.B.O.M.B.1.8.0...H.I.V.

#7
Aaron

Aaron

    The MSFN Banana

  • Patrons
  • 5,767 posts
  • Joined 17-August 01
Here's some extra info:

from http://www.microsoft...on/mpavlfaq.asp

it says: "A VLK must be used with Select CD or Worldwide Fulfillment (WWF) CD media (aka volume licensing CD media). VLKs cannot be used with retail full packaged product or OEM CD media."

Volume Licence Keys are like corporate keys, that bypass activation completely. Unfortunately, it cannot be used on an OEM or Retail copy. So, to use a VLK, you will need a corporate version of RTM for the key to work. Its unknown when we will see a VLK leak....

#8
Rick

Rick

    Senior Member

  • Member
  • PipPipPipPip
  • 585 posts
  • Joined 18-August 01
Thanks Aaron for clearing up the mess! What I am really trying to get to is where can I look to see that I got the version that I thought I downloaded (inside windows). i.e. The download from eDonkey said that I was downloading 2600, however I read that there were fakes being distributed that were nothing more than RC2. Get what I'm asking?

Rick
Welcome to MSFN!

Read the Forum Rules
Posted Image

#9
XPerties

XPerties

    MSFN OG Senior

  • Patrons
  • 2,994 posts
  • Joined 18-August 01
I believe the answer to your questio0n have already been posted. Take a look at [b:00d2c0cc71]Benholio[/b:00d2c0cc71] and [b:00d2c0cc71]AaronXP[/b:00d2c0cc71] post.


-Regards, Chris



You want some Glock with that?
★ :::: Xbox Live GamerTag = ScreamingSkulls


#10
Aaron

Aaron

    The MSFN Banana

  • Patrons
  • 5,767 posts
  • Joined 17-August 01
Here's some more info that should help, from =epyx= (thanks!!)

There seems to be a lot of confusion about build numbering in here, so I thought I would try and set the record straight about build number "2600".

As some others have tried to pointed out, there are actually two "2600" builds in circulation:

* usa_2600__x86fre.pro_whistler.iso
* usa_2600_x86eval.pro_whistler.iso

Only the second one (the 120-day Evaluation build) truly qualifies as RTM. The other "2600" was created several days prior to RTM and MS openly admitted that a few bugs were fixed right up until the night before Aug 24. So even though they share the same build number, they aren't identical and should properly have different numbers. The "2600" released about a week ago is not RTM.

=epyx=

#11
TTT

TTT
  • Member
  • 9 posts
  • Joined 25-August 01
So Aaron,

What kind of iso file sizes are valid so far?

I have seen many different ones out there.:confused

Nice board guys by the way

#12
Rick

Rick

    Senior Member

  • Member
  • PipPipPipPip
  • 585 posts
  • Joined 18-August 01
Okay, thanks for clearing that up Aaron...now it all makes sense and using the previous replies, I think I am armed with enough info to get the right one.

You are the greatest!!!


Rick
Welcome to MSFN!

Read the Forum Rules
Posted Image

#13
Benholio

Benholio
  • Member
  • 7 posts
  • Joined 21-August 01
The group Sinister is currently floating 2 versions of thier Eval XP around at the moment. The fist one is usa_2600_x86eval.pro_whistler.xxx and the Second is similar but conatians the Word Autopatch or fixed in it. The Autopatch one is rumored to have a trojan in it so everyone be careful. The first one though is A Straight copy off of Beta Web. So if you goto the Sinister FTP then get the vanilla and the sinister patch and scan it with NAV before cracking.

#14
hollowplayer

hollowplayer
  • Member
  • 3 posts
  • Joined 01-September 01
the no activation iso version call usa_2600__x86.pro_no_activation, it doesn't built in activation thing, the oem version is only for dell computer, if anybody got ftp server i will upload.

#15
Traveller

Traveller
  • Member
  • 4 posts
  • Joined 07-September 01
Someone in this post wasn't sure whether a VLK Corporate version would be leaked out? Well going to eDonkey and searching, lo and behold there's a VLK version. Downloaded it and burned it to a CD, then installed it. Ran without a hitch, and it asked for the VLK, which the man who upped the ISO was thoughtful enough to put inside the ISO. Needless to say I'm running the real deal and I didn't have to activate it either (and NO timebomb).