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


erpdude8 last won the day on June 2 2020

erpdude8 had the most liked content!

Community Reputation

63 Excellent


About erpdude8

  • Birthday 04/29/1979

Contact Methods

  • Website URL

Profile Information

  • OS
    Windows 7 x64

Recent Profile Visitors

4,057 profile views
  1. yup, Win8.0 (NT 6.2) removed both the start button & start menu (the UI was barely a mess there) Win8.1 only restored the start button but not the start menu
  2. not exactly WinXP x86/32bit is NT 5.1.2600 WinXP x64 is NT 5.2.3790 (shares same "kernel" as Server 2003) that's because XP x64 uses the Server 2003 kernel codebase
  3. Ok I just edited my previous post to mention a Latitude E6400 & E6410, which DO have XP x64 support E6420 & higher do not have it
  4. hmm, what kind of Dell laptop do you have, legacyfan? support for X64 WinXP was limited and varied by different PC manufacturers & models only certain Dell business PCs like the Optiplex 7010 & Latitude E6400 / E6410 had official XP 64bit driver support.
  5. no. the ms catalog site should still work - ms catalog is the modern day "ms download center" yea, so much for the SHA1pocalypse (hah!) my friend's old HP a1600n desktop PC with XP media center edition 2005 (patched with SP3 and a lot of the post-EOL XP updates) is still working recently
  6. an observation from me about KB3020338 - that patch is actually an oleaut32.dll bugfix and not related to RDP; on the other hand, KB3020388 is an RDP patch but is for Win7/Server 2008 R2 only and does not exist for xp embedded. while there is no custom xp equivalent of KB3020338, it is superseded by KB4466388 (which does have a custom xp patch) and KB4493563 which have newer oleaut32.dll files
  7. this version of rsaenh.dll is included in KB4459091 update for XP embedded (need posready reg hack to install on other XP x86 editions) also need to update schannel.dll file (KB4459091 has 5.1.2600.7567 of that DLL file) edit - also read the following from this MS forum thread: so KB968730 is not really needed at all as newer updates include it
  8. highly unlikely that this forum will stop working
  9. unfortunately still MS never really released a KB4507704 DST patch for XP Posready thru WU (they may have tried to produce one at one point but ultimately decided not to post it up) I have to remind you about the comment you made here almost a year ago. the info written in MS support article 4507704 remains inaccurate for XP x64 (64bit) yes, up to Aug. 2019 but for XP x86 (32bit) no - up to June 2019 (with KB4501226 for xp posready)
  10. aahhh shoot! v5.131.2600.6459 of the crypt32.dll file is included in the KB2868626 (MS13-095) security update for XP which renders the KB968730 hotfix worthless (a bit late in realizing this, Dave). also reading this from MS technet forums: edit: a slightly older crypt32.dll file for XP is also included in the KB2808679 update (also makes KB968730 hotfix useless), which prevents internal URL port scanning (to me this feels like a security fix even though it isn't classified as such) - I have both KB2808679 & KB2868626 updates installed on a friend's old eMachines P
  11. this is very good news for Vista users out there because Microsoft will be retiring support for .NET Framework versions 4.6.1 and earlier by April 2022 as recently mentioned here and here (Vista users need to be aware of this).
  12. except that Microsoft recently announced that they will be retiring support for certain 4.x versions (including .NET 4.6) next year in April 2022. also announced here as well. best to find a way to install & use .NET 4.6.2 or better under Vista by April of next year
  13. according to this specs sheet from Dell, the Dell Latitude E6230 laptop can support up to 16 gigs of RAM (2x8Gb) - that's what this Crucial site says. install a pair of 8Gb RAM chips before attempting to install & run a Win10 X64 OS
  14. edit: previous comment removed an 8.0/8.1 key from an MSDM table could activate 10 but not the other way around (aka. a W10 key won't activate W8.x)
  15. I second that, Tripredacus even my dad's Toshiba Satellite C55Dt-A 2013 laptop (used to have Win8.1 pre-installed) which is currently running Win10 Home x64 v2004 build 19041.928 have no problems going into and out of hibernation mode. the Toshiba laptop already has latest BIOS and recent amd radeon graphics & newest Realtek audio/LAN/Wireless drivers installed maybe OP has either a bios problem or a driver problem on the laptop that prevented proper hibernation
  • Create New...