Jump to content
MSFN is made available via donations, subscriptions and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. ×


  • Content Count

  • Joined

  • Last visited

  • Days Won

  • Donations


TrevMUN last won the day on February 25

TrevMUN had the most liked content!

Community Reputation

71 Excellent


About TrevMUN

  • Birthday 10/19/1983

Contact Methods

  • Website URL

Profile Information

  • OS
    XP Pro x64

Recent Profile Visitors

2,340 profile views
  1. Honestly, since I was able to find that Technet article describing the KBs which give the various XP versions SHA-2 functionality, I wasn't worried. Far as I'm concerned, we had our answer: XP may not have initially come with SHA-2 support, but Microsoft provided some functionality in later updates. Especially once people tracked down the relevant updates and put them up for download. If something happens, I've got the installation on hand. And we've got @legacyfan and @erpdude8 to thank for that.
  2. Wait ... huh? I read through that thread and I'm a bit confused. Are those guys saying that updates after KB968730 also discreetly provide SHA-2 functionality to XP, and updates all the DLLs that would require the upgrade for said functionality? Or ... are they perhaps saying the updates can be verified/code signed with SHA-1 and SHA-2? EDIT: I think it's the latter. I just hunted down the relevant URL for that update. Of course, it required going to the Wayback Machine, but if you take a look you can see that the relevant installation files have both an SHA-1 and SHA-256 hash.
  3. I haven't yet applied the Server 2003 SHA-2 update on my rig, so I just tested this as well, setting the date to May 10 at 1:25 AM. On New Moon and Firefox ESR, I get "SEC_ERROR_OSCP_OLD_RESPONSE" on some HTTPS sites but not others. The same sites are still accessible on Advanced Chrome and Chrome 49, however. I tried to see if anything changed if I set the date to May 17, but the same sites would still break on the same browsers, while the other sites that did not break remained unbroken. That's very peculiar.
  4. I had this nagging feeling that there was more to the story of SHA-1 troubles than just not being able to use Windows Update anymore, but given how little I understand of how all this works, I didn't think my concerns would be taken seriously. This is part of why I had nagging concerns. Consider: how many developers go out of their way to support XP for any length of time once dev kits stop providing support by default? Most would just consider it not worth the trouble, I presume. Only in enthusiast circles would you actually see people taking care to make sure XP users can still run a
  5. I just took a look at my rig's DLL, too: version number 5.131.3790.5235. I wonder if that's different for XP64 though? Does XP64 have a different version of crypt32 by default, and after the hotfix?
  6. I don't know. I tried looking into what this means for XP. Over on VOGONS there was some talk about the Windows Update issue, and this was mentioned: Microsoft Technet has a blog post from 2010 saying this: No information's provided for XP64, and my rig doesn't appear to have either hotfix. I'm not even sure which one would apply to XP64.
  7. Damn, Arctic ... what you've got is exactly the kind of setup I hope to have! I have a growing collection of machines that I want to set up like that, or something like the U-shaped desk The 8-Bit Guy made for his studio. (My aforementioned daily driver, Palouser, is XP64; my main personal laptop, Etesia, is XP32. The Gateway2000 machine I mentioned previously is Marin, and the Windows 10 hand-me-down is Levanter. I also have an OpenBSD machine I've been toying with using Palouser's old 2009 hardware, Ostwind. But I have still more machines for future projects ...) Having a computer room
  8. OHRRPGCE! Damn, that's a name I haven't heard in a long time! Back when I was in high school in the 90's I used to run with a group that worked on making games with that. Something rather charming about the way BAM conversions of MIDI sounded. That and Verge and Megazeux. What a time that was. I wonder about Visual Studio. I know that newer versions up and dropped support for compiling to XP; is it possible to re-implement support somehow?
  9. So this may or may not be a niche topic, and I'm only just now learning about this even though I had just done a quick run to a nearby Fry's to get some tech accessories and anti-static bags; but as of February 24th, the electronics store franchise up and went out of business. In many ways, the writing has been on the wall for a two or so years, and there was a lot of speculation about the franchise's pending death. I remember things seeming some of the aisles bereft of goods in mid 2019 and being told by employees there were issues with the supply chain, as inventory slowly dwindled furt
  10. Yeah. I was looking into it and, at least at a cursory glance, Dell actually didn't support XP64 for the Latitude E6430. Even though XP32 is explicitly supported. The only available driver/software downloads are for XP32. I'm a bit surprised. That might not be the be-all end-all; there could be drivers out there which Dell doesn't have listed on this page. You might try asking @XP-x64-Lover for help; if they're out there, she might know where.
  11. What motherboard do you have? Or is there a motherboard you're looking at getting?
  12. I think whether or not it'll be worth it to you depends on what you like to do with your XP machine and what parts you're able to get. During XP's support period, XP64 had a reputation for not being supported by hardware/software. I personally have rarely run into that issue ... at least until after XP lost favor with Microsoft, and compilers stopped providing support for XP, thus causing newer programs to not work. But that's a hurdle all XP OSes face. The main advantage with XP64 is the ability to run 64-bit programs. If you're doing things that require a lot of RAM (e.g. running a
  13. We'll see what the future holds, but like most of the other responses so far, I've no intention of giving up Windows XP for my daily driver computer. Even when I had decided to stick with XP back in the Vista days I knew that would mean eventually needing other machines for certain tasks. After all, Microsoft first tried to force gamers into upgrading to the newest Windows OS with Halo 2's release (and with deciding to make DX10 Vista-only, a tactic they've repeatedly used since). So I knew even back then I'd need a dedicated gaming PC not running XP at a certain point. Yet here I am, sti
  14. Although it's been half a year, I'd just like to add for @FelixPls1's benefit (and anyone else looking for help with slow XP installs on older hardware) there was an old thread I posted years ago when I was having a problem with a Celeron laptop that ran XP, overheated very easily even when idling, and was generally sluggish. @tomw gave me a link to a tutorial at AskVG which might help increase system responsiveness even if none of these remedies actually address the problem. The guide helped make the laptop much faster to boot and not as quick to overheat. I'd also check some of the othe
  • Create New...