Upgrade OEM to Retail?

[Joe Campbell]

Folks,

I built my own computer from components purchased from www.newegg.com, which
"entitled" me to purchase an OEM version of the software (on CD, of course).
I did so without much thought to the limitations an OEM distro has over a
Retail version.

I'm currently unable to install any "Optional Components," and am concerned
that this may be due to running the OEM version. Can someone please point me
to an article explaining exactly what I gave up by buying the OEM version?

Also, is it possible to upgrade an OEM version to full retail capabililty?

Thanks,

Joe

 

[Carey Frisch [MVP]]

Installing optional components should not be a problem
with an OEM version of Windows XP. Can you describe
any error messages you receive?

--
Carey Frisch
Microsoft MVP
Windows XP - Shell/User

------------------------------------------------------------------------------------------------------


| Folks,
|
| I built my own computer from components purchased from www.newegg.com, which
| "entitled" me to purchase an OEM version of the software (on CD, of course).
| I did so without much thought to the limitations an OEM distro has over a
| Retail version.
|
| I'm currently unable to install any "Optional Components," and am concerned
| that this may be due to running the OEM version. Can someone please point me
| to an article explaining exactly what I gave up by buying the OEM version?
|
| Also, is it possible to upgrade an OEM version to full retail capabililty?
|
| Thanks,
|
| Joe

 

[Jim Macklin]

The problem with installing the "optional components" has
nothing to do with the OEM. You should be able to use
add/remove Windows components (Control Panel) or run the CD
install program menu.

You can buy a retail CD and do a repair install, using the
new product key (AFAIK)

OEM CDs from Microsoft, as sold by New Egg, are the same as
retail full install CDs except they will not do upgrade
installs. The OEM OS is limited to installs on only one
computer but a retail OS may be moved from computer to
computer (one at a time).


| Folks,
|
| I built my own computer from components purchased from
www.newegg.com, which
| "entitled" me to purchase an OEM version of the software
(on CD, of course).
| I did so without much thought to the limitations an OEM
distro has over a
| Retail version.
|
| I'm currently unable to install any "Optional Components,"
and am concerned
| that this may be due to running the OEM version. Can
someone please point me
| to an article explaining exactly what I gave up by buying
the OEM version?
|
| Also, is it possible to upgrade an OEM version to full
retail capabililty?
|
| Thanks,
|
| Joe
|
|

 

[Willit]

There is no diffrence in the two versions other than you
can only do a clean install with the OEM unless you re-
burn it and change the setupp.ini then it becomes a
retail.

-----Original Message-----
Folks,

I built my own computer from components purchased from

www.newegg.com, which

 

[JAX]

Very interesting Willit, tell me more, please.

JAX

 

[Carey Frisch [MVP]]

Willit does not know what he is suggesting....and its bogus.

--
Carey Frisch
Microsoft MVP
Windows XP - Shell/User

------------------------------------------------------------------------------------


| Very interesting Willit, tell me more, please.
|
| JAX

 

[Willit]

http://www.thetechguide.com/howto/setuppini.html


Then, burn like a slipstream with a burn program.

http://www.theeldergeek.com/slipstreamed_xpsp1_cd.htm

 

[Willit]

Not true , not true and you know it.....lol

 

[Willit]

once again we have a MVP that thinks they know everything
and is willing to show that they don't Please post back
and tell then how you like your OEM turned Retail. I use
it everyday.

http://www.thetechguide.com/howto/setuppini.html

WinXP's setupp.ini controls how the CD acts. IE is it an
OEM version or retail? First, find your setupp.ini file
in the i386 directory on your WinXP CD. Open it up, it'll
look something like this:

ExtraData=707A667567736F696F697911AE7E05
Pid=55034000

The Pid value is what we're interested in. What's there
now looks like a standard default. There are special
numbers that determine if it's a retail, oem, or volume
license edition. First, we break down that number into
two parts. The first five digits determines how the CD
will behave, ie is it a retail cd that lets you clean
install or upgrade, or an oem cd that only lets you
perform a clean install? The last three digits determines
what CD key it will accept. You are able to mix and match
these values. For example you could make a WinXP cd that
acted like a retail cd, yet accepted OEM keys.

Now, for the actual values. Remember the first and last
values are interchangable, but usually you'd keep them as
a pair:

Retail = 51882 335
Volume License = 51883 270
OEM = 82503 OEM

So if you wanted a retail CD that took retail keys, the
last line of your setupp.ini file would read:

Pid=51882335

And if you wanted a retail CD that took OEM keys, you'd
use:

Pid=51882OEM

Note that this does NOT get rid of WinXP's activation.
Changing the Pid to a Volume License will not bypass
activation. You must have a volume license (corporate)
key to do so.

 

[JAX]

Thanks Willit,

I have witnessed a few of Carey's odd responses to other posts.

JAX

 

[Willit]

If you saw the shots of the GUI's will be totally
diffrent after you re-do it, good time to slipstream in
sp1 at the same time.

 

[JAX]

Thanks, I'm on it. I will stick in the "Rollup" as well.

Cheers, JAX

 

[Carey Frisch [MVP]]

The Windows XP EULA states:

"You may not reverse engineer, decompile, or disassemble the
Software, except and only to the extent that such activity
is expressly permitted by applicable law notwithstanding
this limitation".

 

[Willit]

Oh, you found out that I was right and now you're going
to try to be a lawyer and try to interpret the EULA for
me.

except and only to the extent that such activity
is expressly permitted by applicable law notwithstanding
this limitation

All written by MS for their benefit.

 

[Carey Frisch [MVP]]

No, you are not right, just foolish and deceiving.
Has cheating and deception become a way of life for you?

--
Carey Frisch
Microsoft MVP
Windows XP - Shell/User

-----------------------------------------------------------------------------------


| Oh, you found out that I was right and now you're going
| to try to be a lawyer and try to interpret the EULA for
| me.
|
| except and only to the extent that such activity
| is expressly permitted by applicable law notwithstanding
| this limitation
|
| All written by MS for their benefit.

 

[Gary Tait]

The Windows XP EULA states:

"You may not reverse engineer, decompile, or disassemble the
Software, except and only to the extent that such activity
is expressly permitted by applicable law notwithstanding
this limitation".

Catch is though, this is a plaintext file, not software in itself.

 

[Willit]

Look , you're the one that made this personal. You were
wrong then and you are now.

Carey Frisch said:

"Willit does not know what he is suggesting....and its
bogus."

It's not bogus and you know it.

 

[Willit]

Great observation !!!!!!

It's amazing that ppl will put MS MVP behind their name
and call others names and make moral judgments, when they
are representing a company that has been tried and
convicted many times for doing the same thing and worse.
Can't they see that they have associated themselves with
someone that is just using them. They have no Idea how
long I may have been a MVP before I saw the light.

 

[Joe Campbell]

Carey,

Thanks for responding.

Although I'm using the failure to install fax from the Optional Components
menu as an example, in fact, I am unable to install any of the optional
components (i.e., fax, IIS, Management and Monitor Tools, etc).

My Windows CD is "Windows XP Professional Version 2002 Service Pack 1." Am I
correct in assuming that SP 1 was atuomatically installed?

When I run Setup from the XP Pro disk, the Copy Error box pops up with the
message "Setup cannot copy file fxapi.dl_", and the browse box is
prepopulated with the path F:\i386 (where the XP CD is located). All the
requested files are there, but pressing the Open button or double-clicking
the file returns me to the
original Copy Error dialog.

All the requested files are ALSO present on my C: drive in a directory
entitled UIU, but when I browse to them I get the same result. I've even
tried decompressing the DL_ files into DLLs, but the installer still refuses
to accept them.

Any help would be appreciated. I can provide screen shots, but they're not
very revealing.

Thanks,

Joe Campbell

P.S.

Another bit of info. When I installed XP Pro, the CDROM drive was assigned
letter E:. I later partitioned the drive to letters C:,D:, and E: which
shifted the CDROM drive to F:. When I first tried to install the option
components, I noticed that the Copy Error dialog was prepopulating the "Copy
files from" box with "E:/i386." I figured that the system had not allowed
for this change, so I changed the registry [HKEY_LOCAL_MACHINE \SOFTWARE
\Microsoft \Windows NT \CurrentVersion] Sourcepath from E: to F:. The
dialogs now correctly call for F:, but this didn't fix the main problem.

 

[Frank]

The statement below is really either slander or libel.
WTF are they getting these MVP' now????

: No, you are not right, just foolish and deceiving.
: Has cheating and deception become a way of life for you?
:
: --
: Carey Frisch
: Microsoft MVP
: Windows XP - Shell/User
:
: --------------------------------------------------------------------------
---------
:
: :
: | Oh, you found out that I was right and now you're going
: | to try to be a lawyer and try to interpret the EULA for
: | me.
: |
: | except and only to the extent that such activity
: | is expressly permitted by applicable law notwithstanding
: | this limitation
: |
: | All written by MS for their benefit.
: