Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation on 03/11/2019 in all areas

  1. Windows 10 is also very un-customizable compared to XP, which basically blasted the door open on UI skinning. You had many options available if Luna or Windows Classic didn't suit your tastes (even a few direct from MS). Even if you manage to restore some sanity to the look of 10, an update comes along and wrecks your hard work, as well as altering many of your settings, crushing your anti-telemetry safeguards and rearranging the UI like the chairs on the deck of the Titanic.
    3 points
  2. Win 10 is a rolling disaster. Win 8 (and, I assume, 8.1) aren't bad as long as you install Classic Shell so you don't have to deal with the "Metro" UI. With Win 8, you can get WMC for the Pro version, and IIRC there's even a Web site where you can get Win 7's "gadgets" back. (Gadgets were removed in 8 for "security;" IOW, M$ didn't want to deal with patching any security holes that might crop up, so they just dropped gadgets in Win 8 entirely. Ironic since Win 7 & its gadgets are supposedly supported for another year.) I think Win 7 Pro is the last version with "XP Mode" (XP in a VM), though. If you have 7 Pro, grab XP mode while you can; it's still the best solution for folks needing XP for older programs and 7+ for newer ones!
    2 points
  3. Trying to build it now. Despite the fact that I'm building on WinXP, I still had to explicitly tell it to build for WinXP: perl Configure VC-WIN32 -D_WIN32_WINNT=0x0501 Without the -D just about every test failed; apparently the stupid Configure script just assumes Win 7+ rather than grabbing the version it's actually running on . That may explain why so many of the "compatible with XP" builds aren't actually compatible with XP. Edit: Final (apparently XP-compatible) build of OpenSSL v1.1.1b is about 3 MB when written to a .7z archive file. You can download it from my company's Web site.
    2 points
  4. Nah, he just took the latest 64-bit drivers that are functional on Vista (368.81) and modified its INF a bit. He also removed a device ID of one of the older cards for some reason. The whole thing is based on a big and bold assumption that the drivers released in July 2016 are somehow able to drive the cards released in September 2018 and later.
    2 points
  5. I think @win32 gets the last .... "Word"
    2 points
  6. I have done it once. It was either Windows 95 OSR2 or Windows 98. The disks were from Gateway and I am thinking there were either 33 of them or that the 33rd disk was bad. It was a failure of an install, as one of the disks was unreadable, and this after installing for about an hour and a half.
    2 points
  7. All initial software products have bugs. However, I enjoy Windows XP and Windows 7 more than Windows 10. I've tried Windows 10 just to see what all the "excitement" is about. It still feels rudimentary and unfinished nearly four years later. I also have concerns about the quality control being employed, since there have been numerous buggy updates to Win10 and Microsoft recently laid off thousands of QA personnel. For me, the difference with Windows 10 vs XP and 7 is that 10 has a lot more "phoning home" telemetry parts to it, and you have to jump through a few hoops to disable it all. Also, it's more work to disable automatic updates; with Windows XP and 7 you simply went into the Control Panel ==> Automatic Updates ==> Turn off Automatic Updates. Finally, Classic Shell is a must since I don't care for the Windows 10 interface at all! Your average home user is not likely to know how and/or jump through the hoops, which is why they stay with Windows XP and 7.
    2 points
  8. the first thing I do right after a clean XP installation is to swap over to the classic menu (task bar / properties) to me the Classic Start (Shell) app is a must for all of them 7, 8, 10 on W7 and later the desktop quick access icon is at the lower right corner and you are not able to manually place icons anywhere inside folders !!!
    1 point
  9. You see , that is definitely a good one! jaclaz
    1 point
  10. I am not sure if that is a good or a terrible pun Just in case I will preventively retaliate jaclaz
    1 point
  11. I'm not sure I possess "the drive" to do it! :p (thank you, thank you)
    1 point
  12. Funny. I remember people saying more or less that same thing about XP it was still the latest and greatest. And Vista. AND 7.... It just keeps getting worse with each new release I guess. Me too. Computers, in many ways, seemed much more interesting then, despite their limitations. The hardware industry has, in my opinion, become rather boring and unimaginative lately. The data mining, ad and SaaS industries, however, are in their prime right now. c
    1 point
  13. If you feel like experiencing the real pain, check Windows 98 from floppies (all 39 of them) in real-time: jaclaz
    1 point
  14. Have new build generated by ProxHTTPSProxy v1.5 (Rev3b), various python modules updated (cryptography-2.6.1_openssl-1.1.0j), config.ini supplemented by some entries, CA certificates (cacert.pem) updated and alternativ cacert.pem from MSCerts (Cert_Updater) 11/28/2018. If anyone has interest please write a PM to me. Info: At Python 3.44 the support ends in March 2019. With the latest official cryptography module version 2.6.1 (Feb 28, 2019) ProxHTTPSProxy does not work on Windows XP anymore. Last official working version 2.4.2 (Nov 21, 2018).
    1 point
  15. My school uses XP on their POS machines. Everything else is 7 or 10. And yes, the ThinkCentre is old enough to be (co-)branded IBM. There are still plenty of IBM POS systems floating around my area, but the screens were out of my sight.
    1 point
  16. that's easy Petr. Intel Yonah CPUs are 32bit only, no 64bit support -instruction set is always 32bit. Coreinfo app is reporting wrong info for the T2300E CPU as that processor is 32bit/x86 only. the CPU-Z tool should report better accurate info about the T2300e CPU than Coreinfo. I tried to boot from Win10 v1809 install media (either the regular Win10 1809 versions or the LTSC 2019 release) on an old Dell Inspiron e1405 laptop [which also uses Intel 945GM chipset] and it would just hang on the Windows logo screen for many hours doing nothing (no spinning dots on that boot screen). That is until I changed the processor from an Intel Core Duo T2700 (Yonah) to an Intel Core 2 Duo T7600 (Merom). After upgrading the CPU to the T7600, I booted again from the v1809 usb install media and it went through with no problems and no lockups. Edit 2/28 about the Dell e1405: It seems the v1803 release of win10 worked fine with the Intel Yonah Core Duo CPU on the dell e1405 laptop but not the v1809 release; only when I upgraded the CPU to any Socket M based Intel Merom CPU that I can run the 1809 version. So upgrade the processor on the Fujitsu-Siemens Esprimo Q5010 machine to an Intel T7200, T7400 or T7600 processor and see what happens (may also need a BIOS update to support the T7200/T7400/T7600 processors since my Dell e1405 laptop already had bios support for these cpus w/ bios rev. A10) And for the MSI 915GM Speedster-FA4 computer, you are better off running Win10 LTSB 2016, which is based on v1607 (see that is why I like to run the older LTSB/LTSC editions of Win10 on old hardware that can't work with newer Win10 releases, except for LTSC 2019 which requires newer hardware) that problem eventually got fixed by MS starting with the KB4476976 update in late January 2019, which resolves the compatibility problem with older AMD graphics cards. Edit 2/28: There's a topic in the Ten forums about running Win10 on really old hardware, especially old machines using Intel 915G/GM chipsets.
    1 point
×
×
  • Create New...