bluebolt

Mine looks like this with Firefox 41.0 on W2K Pro from tomasz86’s November 2014 HFSLIP, UUR and .net frameworks. I don’t recall which kernel is used there. No version of Firefox had ever been installed on this machine before: I guess the “stub” version is a problem.

Is that correct? Anyway, here is the link I use to the full installer: https://www.mozilla.org/en-US/firefox/all/ EDIT: I tested Firefox 41.0 dragging the exe to the Application Compatibility Launcher, and it offline-installed fine.

Once you drag the exe file into the Application Compatibility Launcher, be sure to click the bar at the top of the Application Compatibility Launcher window (to “select” it, if you will) before you press the Enter key.

The link doesn’t work for me, either. Never heard of “viglink.”

Wow, Tomasz, I wonder just how far this can go? If your success in direct-porting (or whatever you would call it) these XP updates continues, when you get around to working on W2k Pro UURollup, you may find…there’s not much left to do!

Is the HFSLIP 2000 download supposed to be only 478 KB?

Quite a “contrast” with the old HFSLIP… I started testing your HFSLIP 2000, and lo and behold…I can actually “behold” it now! Thanks for changing HFSLIP’s “two shades of gray” color scheme, I definitely won’t miss that. Nice.

That’s one of the main questions we face once deciding to pursue advanced Windows 2000 Professional installation. In a sense there are two distinct ways to go (notwithstanding the “infinity” of whatever else people can come up with on their own): blackwingcat extended kernel included in Unofficial Update Rollupone of blackwingcat’s more recent extended kernel releases …since there seems to be a conflict between the two. So you can use HFSLIP and / or nLite (for examples) to perfect your own Windows 2000 Professional OS disc, and use one of BWC’s latest extended kernel and extended core releases. Or you can use the Unofficial Update Rollup that tomasz86 makes, the latest of which includes BWC’s extended kernel circa November 2014 (or, you can create appropriate SFXCAB files and update UUR for HFSLIP yourself). The good news is that we may soon have the best of both worlds, so to speak, if tomasz86 decides to pursue an up-to-date HFSLIP package and / or UUR that includes BWC’s (or whomever’s) most advanced extended kernel release: http://www.msfn.org/board/topic/156521-unofficial-sp-52-for-microsoft-windows-2000/page-32#entry1103672

If you installed BWC’s kernel on top of the extended kernel already included in UUR, that has been known to cause problems.

Hi tomasz86, when you “add a new HFSLIP section” to your website, do you plan to update HFSLIP and / or UUR with blackwingcat’s latest kernel?

Which driver did you try? Does everything look okay in Control Panel / Sounds and Audio Devices? My Z-77 Biostar boards also have the Realtek ALC892 audio chipset, and there’s never been any problem with W2K Pro. When I first bought those boards, Biostar offered a Windows 2000 driver, but somewhere along the way (sigh…) they not only dropped W2K support from their latest audio driver download, but didn’t even keep the old driver available. Fortunately I hung on to it. I wonder if Phenomic used an older ASUS audio driver, e.g. 2012/08/15? I would think the Realtek R2.74 executable (from the Realtek site) would work as well. What is the nature of the failure? No audio at all? Intermittent?

Windows 2000 “Update Rollup” was always such an oddity. Just what did they have in mind? Someone obviously thought the idea would go somewhere or other (Update Rollup 2?) but the concept apparently never took off. We know the rest, and what a turnaround: no more service packs for W2K Pro, not even a final Service Pack. At least there were some cumulative updates released later. They short-changed XP on service packs as well, as their longer-term strategy took shape: don’t compete with alternative operating systems, get rid of them. So far they’ve more or less cut off both support and hardware (we here being a little less “cut off” than most computer users, buyers and builders, because of what we know). Going forward (if you can call it that) the creep clearly intends to cut off installation of anything other than the Rolling Nightmare it calls Windows 10, which frankly looks to me like one long, evolving Service Pack to nowhere. I’d rather fight than switch.

I love the smell of 8 cores in the morning. Smells like...victory.

When I enter the term “BM site:jp blackwingcat jre-8u51-windows-i586.tar.gz” Google search returns just one result (here is the direct link): http://blog.livedoor.jp/blackwingcat/archives/1894625.html That page includes the download link (click “Java SE Runtime Environment 8 – Downloads”) and instructions. Here is the direct download link: http://www.oracle.com/technetwork/java/javase/downloads/jre8-downloads-2133155.html

As a first step you’ll want the download, and blackwingcat has provided a handy way to find such things on his site, by entering the following term in the Google search engine: BM site:jp blackwingcat + what you want In this case you would enter the term BM site:jp blackwingcat jre-8u51-windows-i586.tar.gz which will bring up the relevant page of bwc’s site, and the download link. You may want to use the Bing or Google translators.

My bravery level varies with the age and expense of my computer, and the value of what I have on it... So I bravely downloaded and installed all of today's available POS updates on an older, inexpensive test machine. Everything's jake so far, no problems, at least with the basic function and look of the computer.

All the drives were formatted NTFS, all machines administrator only. Sorry, I didn't check out the permissions or the regkeys.

Okay, I just tried the "System Restore" fix on my parents' Acer XP Home computer, and it worked again. I did it a little differently this time: I first set the restore point manually, then immediately--without so much as a reboot--ran System Restore back to that point. In other words, I basically just restored the existing system set. Once again, this exercise alone was enough to eliminate the Event Viewer errors. The fix again has survived multiple restarts.

You got me, submix8c, I don't see any sense in it either. I don’t think the restorations had any affect on the updates; the E520 and 3000 computers already had all POS updates installed from June, and I used the shortest rollback available. For instance, I only restored the E520 back to the first of July, just three days ago. Literally the only updates “undone” by the restorations would be AVG, which I re-updated after the restorations with no ill effects. It seems that the act of running System Restore is per se the solution. Unfathomable, as yet.

I found out how to get rid of the six recurring Errors in Event Viewer. Poking around the Dell XPS (the machine the Errors mysteriously vanished from on 4/8/2015), I noticed that I had run a “System Restore” at 10:52:57 A.M., which I do vaguely remember, as I hadn’t used that function on any computer in at least a couple of years: So I proceeded to test for solution on the two Dell machines that still had the six Event Viewer Error listings. I simply ran System Restore to the nearest point (July 1st) on the Dell E520, and it worked! I restarted the computer a few times, and the Errors are gone. I then did a full shutdown, came back later and pushed the power button, let the desktop settle in, and the “fix” remained, as can be seen here: Then I tested the “System Restore” fix on the Dell 3000, restarted the computer a couple of times, and again the Event Viewer Errors have been eliminated. When I’m next at my parents’ place, I will test the fix on their Acer computer as well, and report back with results. Again, apparently all that has to be done to eliminate the Event Viewer Errors is to run a System Restore. @glnz, if you try this on your computers, could you please post your results here? Having delved into this thing for no apparent reason, I’m curious to find out if this works for anyone else.

I’ve now followed up on the suggestions made here. @w2k4eva, I think your implications--as I read them, that (1) this is probably not simply a Dell problem, and (2) these 1904 informations may just have been generated by having opened Help files--both appear to be spot-on. I was able to check Event Viewer on my parents’ computer this evening (Acer Atom with Windows XP Home, POS registry fix applied, all updates installed). There I found the same six Error listings as my Dell machines, confirming that it is not merely a Dell-related problem. (Plus, my “3000” Dell is actually a “3000n,” and my “E520” Dell is actually an “E520n,” meaning I ordered these without an operating system. I have Windows XP Pro installed on each, so they don’t even have the Dell “factory install image”). I don’t know of any negative consequences to these Errors, but it is interesting, especially whatever happened on that one Dell machine after 4/8/2015 that eliminated the six Errors: So that’s what I’ll be thinking about. [other related information: these machines all have AVG (not Avast), and all are run in administrator mode (no other users or accounts added)]

Looking at my three Dell machines that have the six Event Viewer Errors in question, I tried to see what was different about the one that no longer has the errors… I checked out the Event Viewer/Application list to see what happened after each set of six boot-up Error entries, to tell what changed after 4/8/2015 on that machine that did not change on the other two Dell computers? The difference is the six “HHCTRL Event ID: 1904” informations, which can be seen in this screen grab: And here is what the Properties look like for one of them: Out of my depth here, but it does seem peculiar that there happen to be six 1904 Information entries on 4/8/2015 (after which no more of the six Errors), and no such informations on the two Dell machines where the six Errors have persisted.

@w2k4eva, the screenshots in post #493 are from my “daily driver” internet machine, which I boot daily (at least), and the error entries are there from every bootup from 1/3/2015 to 4/8/2015, since which date the errors have disappeared. I’ve now taken a look at three other machines; one of them shows no such errors, but the other two do have the six errors present every boot right up through today 7/1/2015. So, I’ve now checked out a total of six Windows XP machines, all of which have every POS update offered (usually applied within a couple of days of issue), similar software environments, and results regarding the six errors in question look like this: msi Atom XP Pro: no errors evereMachines Atom XP Home: no errors evercustom-built machine XP Pro: no errors everDell XPS XP Pro used daily: errors from 1/13/2015 to 4/8/2015 (but none since)Dell E520 XP Pro: errors from 1/13/2015 through 7/1 (today)Dell 3000 XP Pro: errors from 11/11/2014 through 7/1 (today) If I’m not mistaken, both of the problem machines used by member glnz are Dell machines. I’m sensing a pattern here, and it’s spelled…DELL. Too bad I’m not technical enough to see why the problem vanished on my daily Dell XPS computer in April. I’ll have to think about that one.

Having only superficially followed the line of discussion introduced by member glnz in post # 407, I hope I’m not just getting in the way here, but FYI… I’ve never had any problems installing POS updates, and haven’t experienced any problems with my systems, but on one of three machines I checked Event Viewer does show these six errors starting in January: and ending in April: So whatever was broken in January was fixed in April?

You can't be sure of it. Business contracts supersede even the Constitution of the country, and they withstand challenges all the time (look up people vs. condo associations, for example). Given the modern change in nature of corporations, where they're becoming ever more evil/predatory without bounds, this is especially disturbing. -Noel In truth this only matters if the contract itself is actually legal, because the terms of any contract are subject to law, just as law is superior to equity. Unfortunately, truth is in short supply. It has been said that “equity is brutal,” and courts don’t hesitate to demonstrate that even as those contracts become ever more difficult for us to avoid. This is not something that’s likely to end well.