• Content count

  • Joined

  • Last visited

Community Reputation

3 Neutral

About Mathwiz

Profile Information

  • OS
  • Country
  1. I wanted to add that kb3172605 is still somewhat buggy. First, as Microsoft has documented, it still breaks Intel Bluetooth devices. Second, on my work PC it breaks Mitel's VOIP software (MiCollab 6.0) just as kb3161608 did. So it may not be a solution to slow Windows Update scans for everyone. The link I provided to Woody's InfoWorld article contained its own link to this page. It's a little hard to follow but gives a workaround. (Unfortunately the workaround may change next Patch Tuesday.) It involves installing a couple of updates on dencorso's blacklist (I'd suggest kb3083710 and kb3102810 for Win 7, kb3083711 and kb3102812 for Win 8.1; despite being on the blacklist, these appear to be relatively safe from both a telemetry and a Win 10 perspective), as well as downloading and installing five security fixes manually (bypassing the search for updates). Once this is done the search for additional updates is purported to take under 15 minutes. I just hate "roll-up" updates. Why couldn't Microsoft have addressed each issue with a separate update? That way, even if there are problems with one, you could still install the others.
  2. That hours-long update cycle is a bug. KB 3161608 was supposed to fix it but was itself buggy. So, it was recently replaced by KB 3172605 for Windows 7, and KB 3172614 for Windows 8.1. Here's an article on the topic: You can try installing the appropriate KB 31726nn update for your system. Hopefully Microsoft finally got it right (at least as far as Windows Update is concerned). They do not seem to include any Win 10 nonsense, as far as I can tell. Unfortunately all these patches do seem to include telemetry so you'll probably also want a telemetry blocking solution (as discussed a few posts ago).
  3. The end (of all this GWX nonsense) appears to be near:
  4. Back in my Win98 days (and I still use my Win98 PC once in a while), I needed a similar wild-card capability for ad blocking, and used a freeware program called DNSKong for this purpose. I just Googled it and apparently, it still exists - and it seems to run fine on Win 7 (someone will need to try it on Win 8 through 10): If you set up DNSKong, add the above domains (w/o the * or "=" parts) to DNSKong's named.txt file and, in combination with the numerous hosts entries added by Spybot Anti-Beacon, you should be set. Depending on your router, you may also be able to set up the above blocks there; but that process varies greatly from one router to another and isn't possible on all of them. BTW, I agree we should try to avoid telemetry updates in the first place if/when feasible. But for those of us not quite ready to ditch Windows updates altogether, updates with telemetry are likely to sneak through on occasion. (In particular, the latest "Windows update update" appears necessary for updates to finish in a reasonable amount of time, and is likely to include the WU telemetry introduced back in December.) So a combination of strategies - both blocking bad updates and blocking telemetry servers - seems more prudent than relying on either strategy alone.
  5. My concern with 3161608/3161647 is telemetry: presumably all updates to the WU client include 3112343, listed on post 1 as "This update also improves the ability of Microsoft to monitor the quality of the upgrade experience." But if it's the only fix for days-long WU downloads, our only realistic choices may be either to live with it or live without updates. Or maybe not. Has anyone tried this from
  6. Do you get the same error if you run the Dolphin emulator under KernelEx 4.5.2? Remember 4.5.2015.x is experimental; it is not even a beta release. So it may have some bugs that 4.5.2 does not have.
  7. I think you must have HOSTS and localhost confused. WINSSL has nothing to do with HOSTS files, it simply shakes hands with a server that has SSL encryption and allows Win98 to connect.. Thats it, thats all. There is a batch file that create .pem certs. I guess they could be equivalent to each other.It isn't totally obvious what Nomen is doing, but my guess is he's using a trick I also use: putting the IP address of localhost ( into my HOSTS file for web sites I don't want to connect to (e.g., banner advertising sites). This can speed up browsing because instead of wasting time downloading ads you didn't want to look at anyway, your browser just tries to download the ad from your own PC. A problem with this trick is that where the ad was supposed to appear, you get an ugly rectangular box with no image to fill it. To get around this, I use a "local only" web server on my PC that feeds small "dummy" images to fill those boxes. However, this only works with blocked http: sites, not https: ones. I thought about using WinSSLWrap for the blocked https: sites. My idea was to use it in reverse, letting it listen on port 443 using SSL, and connect to my local web server on port 80. But then I realized it wouldn't work: it would always serve the same certificate, no matter which site the browser was trying to access, and that would trigger the browser's "site name mismatch" warning.
  8. Fair enough. As I said, there are ways around it if you're creative enough. So, yes, to be completely correct in every detail, to use the full 4GB you would need either a 64-bit OS or one of the 32-bit Windows Server OSes you mentioned. But I don't think server editions of Windows were ever remotely under consideration by either the OP or anyone else. Windows XP was indeed the first Windows with a 64-bit edition, AFAIK.
  9. Reallly? I guess that until 64 bit systems came out the world servers must have been very short of memory. jaclaz Really. At least with Intel's 32-bit architecture. 2^32 is ~ 4 billion, so their 32-bit processors could only address 4 GB. But some of that address space is needed for non-RAM uses, so only about 3-3.5 GB (maybe a bit more) is accessible in the 32-bit address space. The remainder is only accessible with additional addresses; that generally means a 64-bit OS. There are ways around it, if you're creative enough. (Remember "expanded memory" back in the old 16-bit days?) Edit: and now I've read your final post, and apparently you agree! So why the snarky comment?
  10. I'd start with the unofficial 98SE Service Pack 3.nn (whatever version he's up to) and KernelEx 4.5.2; both are in the Windows 9x Member Projects subforum. They'll let you use newer software and hardware than you could otherwise. If your laptop has more than 1 GB of RAM, you'll need to do some extra work to install Win98; see this thread for more info. Edit: Just in case, I should mention that some folks have run into incompatibilities between the 98SE Service Pack 3 and KernelEx. I haven't had any trouble yet, but I only installed the "main" Service Pack 3 updates. If you do run into problems, you can install KernelEx to default to "disabled" and only enable it for the software that needs it, such as Opera 10.x, 11.x, or 12.00-12.02. (Opera versions newer than 12.02 won't work on 98SE even with KernelEx.)
  11. That feature would come in handy playing video recorded by cheap DVRs like the iView, Homeworx, eMatic, etc. On FAT32 HDDs those boxes break recordings at 4GB boundaries and number them sequentially like that.
  12. You'd need a 64-bit OS to use all 4GB of RAM. Not sure about Windows 95, but 98 and ME will use 3+ GB with rloew's RAM Limitation patch. It's not free but it doesn't cost much. Haven't tried NT4 or Win2K but I assume both will use the same 3+ GB. No patch should be needed for them. Win 9x/ME also won't use both CPU cores. Again I'm not sure about NT4 or Win2K.
  13. Batteries? D'oh! That should have been the first thing we suggested. All this discussion and nobody else (including me) thought to mention the obvious, but better late than never.
  14. My M$ wireless mouse and PS/2 receiver have switches, with the positions labeled "1" and "2." I assume that sets the frequency to use. (Unfortunately I couldn't find the actual RF frequencies it uses documented anywhere! I'm guessing maybe 418 MHz and 433 MHz, since those two frequencies are commonly used for these kinds of devices, at least in the US....) I don't know if wireless keyboards in Germany have a similar switch, but if they do you might give it a try. (Make sure to switch both the keyboard and receiver! If they don't match, it won't work.) All these problems could just be RF interference from something else in or near your living room PC.
  15. I haven't looked at keygen.bat yet, but from the sound of it, I'd guess it's used to generate private/public key pairs. ( is revamping their site and their docs are temporarily screwed up, so I can't tell much more at the moment.) I'll take a closer look tonight and reply back, but if I'm right, you probably only need it to create your own certificates, for one of two purposes: Client certificates (to be used instead of a user ID & password to identify yourself to a server) If you're running your own server and want to secure it with SSL (using wrap.exe in reverse of how you and I are using it)Edit: I was right. It uses OpenSSL to generate a private/public key pair. Technically, it generates a 2048-bit RSA key, which is the de facto standard for SSL certificates today. The public key is included in a certificate that is set to expire after one year. OpenSSL will prompt you for identifying info for the certificate. The batch file then combines the certificate and private key into a .pem file, presumably for use with wrap.exe. (Since the .pem file contains your private key, you should not give it to anyone else.) End of Edit. So most folks probably don't need to worry about it. BTW, here's a definition I found here for the .pem file format: Also of note, from the same page: