reloading ME w/o cd

[kony]

WHEN the key changes is immaterial...build #, cd's produced, etc. The
important point is that the key is tied to the cd...and DOES change.
Not every key will work with every cd...and that was the point we were
all trying to tell you.

I can appreciate that now, but still I feel as though the odds of a key
working are better than was implied. I still don't necessarily agree that
"tied to a CD" is a suitable description of the situation though, as I am
100% certain I've done so previously, for exampe, Compaq keys on IBM discs
(installed on the Compaq system to do without their infernal
QuickRestore).

 

[Remo]

All the windows cds are identical, what they do is to give you one of
the valid passwords(your licence code). The licence sticker shows them
that you paid for the OS and you are a legal user. So u may copy
another windows ME cd from a friend and enter your licence code. It
will work..

 

[~misfit~]

You guys have just been lucky.

There are literally hundreds of different cd keys.

As a matter of fact, there's a utility program put out by MSFT...so
that you can change your key in XP if you happened to have one of the
keys that they blacklisted. That blacklisted key would prevent you
from being able to install service pack 1.

Just like to point out that this thread has ME in the subject. XP is
different to ME.

There is not a unique key for EVERY CD...that would take millions, of
course. So maybe that's how you guys got lucky.

But there are definitely hundreds...probably thousands...of different
keys out there.

Of course. Millions. Each licence has a different key.

 

[~misfit~]

Because probably 100,000 or so cd's have the same key. I'm just
guessing on the number. But as I said...there is NOT a unique key for
EACH CD...only for a SERIES of CD's...maybe 100,000...maybe
500,000...dont' know for sure.

You have this all wrong Trent. Each CD will take *any* valid key. I don't
know what the parameters are that makes a key valid, maybe some sort of set
of rules that say things like: "if number three entry is x then number eight
enrty is x +/- three". It would be impossible to have every valid key listed
on each CD so there must be set of rules that make each key valid.

That's how people write key-generators, by working out these rules. Get a
large enough sample and run them through an analyser.

No...the original cd will only install with the key that is on that
cd. You can CHANGE that key...as my above example implies. But
that's not the same as installing.

As I just said, there isn't a key number on the CD, just a validation proggy
that allows the install if the key that is input fills the criteria.

 

[~misfit~]

As another followup, I have tried a couple different systems, ME
licenses, and one DID install with a different CD (that what came
with the system/license) but the other didn't, refused the key (that
was already known valid as it was used to do the first install on the
system). Apparently the difference is the OS build number, or at
least that seems to be the case.

So it seems we're both half right and half wrong... it can work but
not with just any-old-disc.

That is probably because they were slightly different releases of the OS.
The validation logrithim had been changed.

 

[~misfit~]

House keys and car keys are the same way. Its doubtful that your
house key will work in your neighbor's door. But it WILL work in
someone else's door...somewhere.

Completely different. A lock doesn't check to see that the key is a valid
one. Your analogy is flawed, that is the case of 'one lock, one key'. MS
OS's don't work like that. It's the same with a lot of proggies, they have a
validation logrithim that checks the *format* of the key is valid.

 

[~misfit~]

All the windows cds are identical, what they do is to give you one of
the valid passwords(your licence code). The licence sticker shows them
that you paid for the OS and you are a legal user. So u may copy
another windows ME cd from a friend and enter your licence code. It
will work..

Agreed, as long as it was the exact same release of ME, not a later or
earlier revision.

 

[hu man]

Ya know, it's a complete shame that this thread went on and on and on and
nobody even remotely helped the original poster. Somewhere in that
bickering, someone could have made some useful suggestions.
Jtiche:
Now that you have your comupter running OK, for now, maybe you should do
some maintainance. Do a good cleanup, run disk clean up and allow it to
clean everything. Then, download Ad-aware or Spybot (free), update them and
run them, remove all of the spyware. Then, download an antivirus if you
don't have one AVG is free), if you do, update it and run it. Also, go to
Windows Update and see if you have all of the critical updates.
Once you are done all of that, run a ScanDisk, then run the Disk
Defragmenter. This may make your machine run much better. Good Luck

 

[Trent©]

You have this all wrong Trent. Each CD will take *any* valid key. I don't
know what the parameters are that makes a key valid, maybe some sort of set
of rules that say things like: "if number three entry is x then number eight
enrty is x +/- three". It would be impossible to have every valid key listed
on each CD so there must be set of rules that make each key valid.

I think Kony has already proven that your statement is not correct.



Have a nice week...

Trent

Follow Joan Rivers' example --- get pre-embalmed!

 

[Trent©]

Completely different. A lock doesn't check to see that the key is a valid
one.

Sure it does. What part of this don't you understand?

OS's don't work like that. It's the same with a lot of proggies, they have a
validation logrithim that checks the *format* of the key is valid.

Check your registry. I think you'll find a SPECIFIC key listed there.
This key, in many cases, is read by MSFT when you log onto their site
for updates, etc.


Have a nice week...

Trent

Follow Joan Rivers' example --- get pre-embalmed!

 

[DevilsPGD]

In message <<[email protected]>> kony

In fact, the big OEMs don't even use that CD they send with the system,
they clone the drives from same souce drive(s) then each installation uses
it's own licensed key, eventually, but that key also works with the CD
shipped with the system... more evidence that the CD isn't tied to the
key.

In most cases there are classes. You can't use a "OEM" or a "retail
FULL" or a "upgrade-only" key in a mismatched version. Additionally,
you can't always use one OEM key with an OEM key from another
manufacturer.

In XP it's a little different, it just bypasses the activation
requirement under some circumstances (OEM keys are popular this way, I
can reinstall my laptop without activation -- If I pop the same OEM CD
into my desktop I can install, but I need to activate with my laptop's
key -- I reinstalled with my desktop's key, and it worked) -- Note that
this CD is a real Windows CD, slightly customized with drivers, it is
not an image of an installed hard drive or anything like that.

 

[~misfit~]

I think Kony has already proven that your statement is not correct.

I think you (and Dave) may find that the case where he tried it and it
didn't work will be a slightly different release of ME.

 

[~misfit~]

Sure it does. What part of this don't you understand?

LOL, you're an argumentative little bugger aren't you? So it checks that the
key isn't one that was just cut down at the locksmith's? i.e. a third-party
key? You started this analogy.

Check your registry. I think you'll find a SPECIFIC key listed there.
This key, in many cases, is read by MSFT when you log onto their site
for updates, etc.

This has absolutely nothing to do with the discussion Stacey and frankly I'm
surprised that you seem to have entirely missed the point.

That key in the registry is there because *I* put it there when I installed
Windows. It wasn't on the CD that I installed Windows off, and that is the
issue we are discussing. See if you can find a list of valid keys on an
install CD for Windows. Or this registry entry you mentioned.

 

[kony]

That is probably because they were slightly different releases of the OS.
The validation logrithim had been changed.

Yes, that's what I'm thinking. Now I'm wondering if there's an easy
method of determining the build number, like using another windows box to
check the properties on the "setup.exe" file.

I guess the main thing to remember is, OP and anyone else should insist
that their PC come with the OS CD, else be a whole lot cheaper.

 

[Trent©]

Ya know, it's a complete shame that this thread went on and on and on and
nobody even remotely helped the original poster. Somewhere in that
bickering, someone could have made some useful suggestions.

You need to learn to read for comprehension.

We didn't try to help him...because he no longer needed any help. If
you'll read his subsequent post, he said he solved his problem.

That leaves us room to bicker and pout!! lol


Have a nice week...

Trent

Follow Joan Rivers' example --- get pre-embalmed!

 

[hu man]

Actually Trent, YOU are the one that needs to read for comprehension. Go
back and read his second post again and try for a third time also. It states
that, and I quote, "This seems to have corrected the problems I was having,
at least for now". Seems means to give the impression of or to appear to be
and at the end of his statement is, at least for now. In other words, it may
have or may not have actually fixed the problem. So, I felt that with all of
the time and energy everyone was wasting in this thread, someone could have
given him some advice. It wouldn't have hurt.

 

[Trent©]

LOL, you're an argumentative little bugger aren't you? So it checks that the
key isn't one that was just cut down at the locksmith's? i.e. a third-party
key? You started this analogy.

And its a valid analogy. You just don't understand it! lol

This has absolutely nothing to do with the discussion Stacey and frankly I'm
surprised that you seem to have entirely missed the point.

Then we should move on.


Have a nice week...

Trent

Follow Joan Rivers' example --- get pre-embalmed!