Thread: XP Validation
View Single Post
  #35  
Old January 17th 18, 02:49 AM posted to microsoft.public.windowsxp.general,alt.windows7.general
Diesel
external usenet poster
 
Posts: 937
Default XP Validation

Java Jive news Mon, 15 Jan 2018 16:34:19 GMT in alt.windows7.general, wrote:

It depended upon user choices made - I always chose to be
notified of updates, and I would choose which and when to
install, in which case Obviously in the former case, you had to
be logged on


Which isn't the default setting.


A choice had to be made during installation, and whatever choice
was made became the default setting for that machine until and if
subsequently it was changed. And as based on your pathetic record
most probably you'll try and bull**** some more, note that I've
just checked by doing a fresh XP install from scratch. The
relevant choices presented were ...


I've yet to try bull****ting you or anyone else about anything on
this subject. You just can't stand the fact that you didn't know
nearly as much about XP or the various licensing schemes MS offered
concerning it. And, what ****es you off the most was the fact you
were wrong, flatout, wrong, concerning the OP's inability to get
updates if they opted to load VLK edition. You incorrectly assumed
they'd be fuxored for updates from that point forward. You had no 1st
hand knowledge of using a well known script called WSUS to do this
for you.

Hell, you had to perform a useless test to ensure your KEY didn't
deactivate due to old age. Which clearly shows you didn't/likely
still don't understand how different keys worked or how the
activation process works at a lower level. Further, you didn't
provide the OP an easy answer to his initial question with a single
command line which brings up the activation options available to
them.

On the contrary, that seems to be a significant difference between
us -


No, you don't. You tried the old troll tactic of snip unread,
anything that got too technical for your level of understanding and
labeled it as bull**** when it wasn't.

The fact you felt it necessary to verify your key hadn't expired only
confirms that you really *don't* know how the activation routines
work.

And, you haven't addressed the issue I brought up concerning SLIC
based installs; because you have no actual first hand knowledge of
the subject.

I fact check, you bull****.


You try to pass off what I wrote as bull****, certainly.

Besides the above experimental fact
checking about how updates were delivered to XP machines, I've
also been fact checking that part of your post concerning WSUS,
and have found that once again you were bull****ting, but first
let's remind ourselves of the order of things ...


It does help to have the right program to test with...

http://download.wsusoffline.net/

wsusoffline-wxp-enu.iso

Do you know what that is? It's an iso which contains the XP updates I
pulled when used WSUS to do it for me. ALL XP updates current at the
time the file was created. Which, I already offered to send to the op
along with the vlk iso and a valid VLK key for it.

Note that there was no mention there or in the rest of his
original post of anything to suggest that he was other than an
average bod, probably a home user, trying to validate an old
installation of XP, or that he might have had access to a VLK.
This was the relevant part of your reply ...


Incorrect.

Months after purchasing a XP Pro refurbished laptop I am getting a
* in the tray and wanting to validate. I have used every day for
hours.

I tried all the options and they all failed that are presented
from the menu at the * in the tray.

Several of the webpages that get opened are blank.


You have a couple of options...You can continue trying via the
browser method, but, you need to update ie6 to atleast sp1 or, go
with ie8.

Alternatively, you can try this from console to bring up the
activation window I described above and go from there. Keep in mind,
it renders in html, so if your copy of ie is foobared, this may not
work. Each line requires you to press enter after it, naturally.

open cmd.exe via start/run
cd\windows\system32\oobe
msoobe /a

I went on to provide various other options the OP has available to
them if that doesn't work out, including tossing the XP version they
have in lieu of XP VLK edition. You incorrectly assumed that if they
went that route, updates wouldn't be possible; but you were wrong.
Myself and many others (check alt.comp.freeware) have succesfully
used WSUS to obtain XP updates, specifically.

On 02/01/2018 02:01, Diesel wrote:
Wait, I lied. There's actually another option, but, it's not
exactly a legal one. That is, if you really want to keep XP
pro. You'll have to reinstall it, from scratch though.


... to which I replied ...

No, not really viable, as the rebuilt installation will not get
any updates, not even the ones originally targeting XP.


... to which you replied in your usual superior tone ...

Wrong answer. You've evidently never heard of WSUS. You might
want to google a bit about it.


... so I did, partly because I thought it might actually be
useful, but I was disappointed - why am I not particularly
surprised that advice from you should be found wanting?

https://docs.microsoft.com/en-us/win...istration/wind
ows-server-update-services/get-started/windows-server-update-servic
es-wsus


You're an idiot. WSUS offline update is NOT a product of Microsoft.
http://download.wsusoffline.net/

It helps, you know, if you're going to check something, that you
actually checked the same thing the other person was writing about,
instead of what you incorrectly assumed they were writing about.

Do you do many tests with erroneous assumptions and chastise the
other person when your tests fail?

They're not even much use to me - why would I, or anyone, want
to upgrade an otherwise perfectly good recent PC or laptop that is
running a workstation OS comfortably to run a server OS requiring
2GB of extra RAM, just to drag a much older outdated laptop or two
kicking and screaming into the present?


See above. You're clearly in way over your head.

So I return to my original criticism of what you wrote, to rebuild
an XP installation from scratch now that end-of-support has passed
is not a viable option for most people, because, without jumping
through many difficult hoops, it won't get any security updates,
and, from what we've learned from the OP since, 'most people'
appears to include him.


It's clearly not something you should be entrusted with doing, that's
for sure. You can't even find the correct program to get the updates
with.

I rest my case. You are an arrogant bull****ter, to whom I've
already paid far more attention than your childish
attention-seeking deserves, and will not be paying any more.


Again, I wasn't bull****ting about anything I wrote. But, you clearly
are NOT the technician you claimed to be, either. Not only did you
feel it necessary to double check your own key to make sure it didn't
expire (they don't), you went so far as to lookup an entirely
different thing concerning WSUS; further indicating you KNEW NOTHING
of this programs existance:

http://download.wsusoffline.net/

And yet, you have the audacity to call me an arrogant bull****ter?
ROFL! You know something, when I go to test a program, I make sure
the program I'm testing is the same ****ing thing the person wrote
about. You clearly, don't even do that. You're so arrogant in fact,
you couldn't be bothered to ask for clarification on WSUS; you just
assumed I was writing about something else entirely and went from
there. Asshat.



--
To prevent yourself from being a victim of cyber
stalking, it's highly recommended you visit he
https://tekrider.net/pages/david-brooks-stalker.php
================================================== =
Read what I mean, not what I write.
Ads