I had a feeling that it was down for everyone. But I still don't know why you rolled your eyes when you gave the link @911medic: Looks like the host got their act together, but I just tried now, says your bandwidth has been exceeded. I think this indicates that you really need to find a different host
Bleh... I've relied on MDL for a while now, sort of a silent lurkar for the most part, but referencing it for all sorts of stuff. Maybe I can help give something back... hostfile.org - go post the file there, it'll never get deleted or run out of bandwidth. And no ads, no in-betweener download pages, no crap, just a direct link. I'd know, I built the place. =P (edit: OK, understandable, can't post "links" until I get 20 posts. Doesn't that just encourage spamming though?) Meanwhile, I continue bashing my head against this Windows XP netbook (Compaq Mini CQ10) that has a worn-off product key. I used the OEM flavor of XP but not an HP-specific one. I made a full backup of the system before wiping (in a WIM image), and have tried piecing together oembios.* (including the CAT in catroot), and the oobeinfo.ini, the SLP key, etc., and the damn thing just will not stop reporting "Not Activated" in MGADiag. MGADiag reports product ID type 2, "OEM SLP", and the strings for SLP 1.0 are in the BIOS according to SLIC Toolkit (it's not modded, so they darn well oughttabe). Hopefully I can find some answers... but at least I can give you that little link edit: What the hell. Even MGADiag says this stuff should all be working! "OEM Activation 1.0 Data--> BIOS string matches: yes" *scratches head* edit: yep, this tool fixed it. somehow. found a mirror by searching "mirror" in this thread, ran the tool, pulled together the 4 OEMBIOS files from the backup WIM, ran it, and wham bam, next reboot and msoobe /a said "already activated". Awesome! Now save the next guy an hour of fiddling and host the file somewhere reliable (above, wink wink)
Oh my god, I would remove that link to the 0x... ".com" website ASAP! That site is nothing but a scampit of despicable deceptive practices (linking to them in a clickable link gives them a search-engine boost!)... first thing that caught my eye was the Microsoft logo - Microsoft wouldn't slap their logo on something like that unless it was on the official MS website; when MS owns a "somethingsomething .COM" domain, it just redirects to a page on their site. That's totally fake. Then, I saw the links. "Download 0X80004002 Fix" -> 0x80004002.reimage.revenuewire.net/reimage-pc-repair/download "Download Latest Windows Update" -> 0x80004002.pcdriversheadqu.revenuewire.net/driver-detect/download Kill them with fire!! Companies like these are what are being protested at Wall Street at this very moment... edit: OK, well, this issue is COMPLETELY UNRELATED to the topic you posted in (I just realized that, hurp), but: 1. go to Start/Run (or press WinKey + R), and enter "net stop wuauserv", hit OK. 2. go to C:\Windows and delete the SoftwareDistribution folder. It's a folder used to make Windows Update faster by caching and storing information about Windows Update. This information is also stored in the registry and is rebuilt if this folder is deleted. We're not talking 4chan "delete system32" here. Don't do that. 3. Start/Run (or WinKey+R), and enter "cmd", hit OK. 4. Enter "openfiles" at the prompt and hit enter. If you get an error, open an elevated command prompt (google that) and continue. 5. Paste these lines at the prompt. This re-registers any broken Windows Update components. Amusingly, this is the only true piece of information on that 0x... .COM website, but needs to be modified to execute in sequence, not all at once: start /w REGSVR32 WUPS2.DLL /S start /w REGSVR32 WUPS.DLL /S start /w REGSVR32 WUAUENG.DLL /S start /w REGSVR32 WUAPI.DLL /S start /w REGSVR32 WUCLTUX.DLL /S start /w REGSVR32 WUWEBV.DLL /S start /w REGSVR32 JSCRIPT.DLL /S start /w REGSVR32 MSXML3.DLL /S net start wuauserv exit ... Any errors you get, don't mind them - this is just a bulk list of files that ought to be present, but sometimes aren't. 6. Now, try Windows Update again. If that fails, well... find a new topic.
Thanks FalconFour for your reply. My concern in querying the error is that since I have used VLK and OEMBIOS changer; can I perform these steps for error rectification?
@911medic I have corrected some of the typos in the readme and rewrite it in a well-organized () way; can I upload it for ur review??
Looks good. need to make a txt file also for the batch to open. In the odd event someone doesnt have a pdf reader...I may have other solution, but it will have to wait a couple of days..
When I try to run the CMD, it fails with the message: "unable to find the specified registry key or value". This appears to be similar to the problem described in post #340 in this thread. I have tried to manually add the required keys and values listed near the beginning of the CMD file, but I don't have much registry editing experience, and I can't seem to get it to work. Can someone walk me through exactly what I need to add or change in the registry in order to make this work? By the way, my system is already on XP Pro SP3, if that makes a difference. Thank you!
Try this oem.cmd script..it omits the first screen.... View attachment 12842 You just unrar the file and replace in the changer folder...it is a simple batch you can review at you leisure..
strange problem. i have used the oembios changer tool many times. it always worked. it was used on a volume license winxp pro cd that was slipstreamed with sp3 and tweaked with nlite. tonight i decided to install winxp from scratch. i then installed sp2, then sp3. i did the initial win updates and wga ran and said its not valid. i then ran the oembios changer and the program starts that cmd screen but it shuts down immediately. in other words the program doesnt stay on that screen with the various choices to uncompress the files etc. its just a typical compaq presario desktop with plenty of oembios files to choose from. anyone ever experience this? regards