I've made the switch to Windows XP in...


  

328 members have voted

  1. 1. I've made the switch to Windows XP in...

  2. 2. Before Windows XP I used:

    • Windows 3.x
    • Windows 95
    • Windows 98/98 SE
    • Windows Me
    • Windows NT 3.x
      0
    • Windows NT 4.0
    • Windows 2000
    • Linux
    • Mac OS Classic
      0
    • Mac OS X
      0
    • OS/2
      0
    • Other (specify below)
  3. 3. I've since switched from Windows XP to...

    • Windows Vista
    • Windows 7
    • Mac OS X
    • Linux
    • Other (specify below)
    • You can pry Windows XP from my cold dead hands.


Recommended Posts

Poll closely related to the 10th anniversary thread.

I've switched to XP in 2001, coming from Windows 2000, and have since switched to Mac OS X (iMac) and Windows 7 (laptop).

Note: You can make multiple selections in the third question.

My family's new computer in 2002 ran XP SP1 (before that we had a Windows 95 machine from 1997). I got my own desktop in 2003-ish (a second hand P3), running 98, then XP.

My first laptop in 2004 (a crappy Dell Inspiron 1150) came with XP SP1a. Several second hand desktops (with 98 or XP) later I built my own machine in 2008. It originally dual-booted XP and Vista (and in early 2009 Windows 7 beta/RC builds), then I upgraded to Windows 7 in October 2009 when 7 RTMed. Still got the same 2008 PC (and I tihnk even the same Win7 build) - solid as a rock! :D

I got ME in 2001 on a Tosh Satellite when I went to uni. Loved that lappy apart from the WEAK graphics. In 03 I built my own machine (Which was badass back then and still runs strong now). When I started this job in 08 I purchased a new laptop which had Vista but only for a month or 2 as I managed to get a early discounted retail copy on Win7 and haven't looked back since.

I bought a new computer with xp on it in dec 2004. Before that i used Win ME. Then i bought a laptop with vista on it in oct 2009, as soon as 7 came out i switched to Win7.

yeah and i have switched from Windows 1 to Windows 8 Beta today

It started to get unbearable when web-pages got more fancy. Back then I used to only use my computer for building terrible Angelfire websites, running games from the mid-90's, and posting on forums.

It started to get unbearable when web-pages got more fancy. Back then I used to only use my computer for building terrible Angelfire websites, running games from the mid-90's, and posting on forums.

wow i thought you were kidding....you should've at least tried win95

I switched to XP immediately from Windows ME, which was a complete nightmare compared to '98 SE; I seem to recall ME liked to BSoD a lot, was far less reliable than '98 and lacked the level of support that 98 had; I was glad to switch to XP as soon as I possibly could and I never regretted it; XP was a great OS from day one.

Back in the day, my old 486 with 8mb RAM, ran Windows 3.1, upgraded that to Windows 95 shortly after it was released, my next comp was a pentium 120, 32mb ram, ran windows 98, upgraded to a Celeron 333, 64mb ram, that ran 98 until XP was released, by the time Vista was relased, I had an Athlon XP 1800+, now I have a Pentium E5200 running 7 (Y)

wow i thought you were kidding....you should've at least tried win95

I would have needed a processor upgrade. I didn't have the interest in upgrading nor did I want to commit money to upgrading so I just made do with what I had. For the most part, the computer was fine until multi-media and advanced scripting exploded on the web. I did have access to Windows 98 and Windows ME computers but I hardly used them because they were slower and more crash-prone than mine.

Had Windows Me installed on one computer for a while, until W2K came out, then all computers had that. Installed XP on everything shortly afterwards. Never used that POS Vista for more than 10 minutes on a couple of computers.

Now, all but one computer is Windows 7. Easily the best MS has done yet.

For my Windows boxes, switched over once SP1 came out in 2002. The RTM build was a little wonky at first, that and I had some driver issues if I recall, stayed with 2KPro till then. I remember the same old rants on various forums about XP when it first came out too.. XP's slow, bloated, buggy, 95 boots faster, doesn't have all my drivers, doesn't play all my old games, I'm scared of change, etc etc. Some things never change.

Now, all but one computer is Windows 7. Easily the best MS has done yet.

+1, definitely their best desktop OS yet, and rather fond of 2008R2 as well on the server end.

Had a Windows 95 machine, then got a new computer that came with Windows ME. It ran fine for the first year or so, then it would crash weekly and we had to keep taking it into the computer store. The computer store got sick of us and gave us a free copy of XP.

My pre-XP OS was Windows Me. I know a lot of people considered it to be the devils work but, for some reason, it always worked great for me - and obviously being newer than Windows 98SE meant whenever I did a reinstall, there was less stuff to install / patch.

Happy Windows 7 Ultimate 64bit user now! Proabably because I got a free copy of it in the goodie bag when I went to TechEd in 2009 ;) Thanks Microsoft! ;)

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • I sort of agree with you on that. I had a telescope - a real hefty thing, although only around 500CHF - that got me so fascinated about the stars and planets. I would stare for hours, amazed that I could see the craters of the moon or the rings of Saturn in "realtime" (quotations because, y'know, speed of light and whatnot). A friend of mine has a telescope like the one mentioned in the review, and the pictures are amazing to look at. But there is something missing for me. I may as well just go to NASA's website and look through their gallery.
    • As opposed to catching bad press because it's the engine's fault? You didn't really think this through did you? lol. The engine has all the tools a dev needs to optimize their game, Epic isn't gonna hold their hand to make sure they use them. Also, Epic isn't forcing anyone to use Lumen, Nanite or super high resolution meshes and textures. Just because Nanite can render meshes with millions of polygons doesn't mean you should use it like that, in fact, Epic recommends you avoid doing that. Most of the stuttering can easily be fixed by cutting down on unique shaders by using master materials and generating a PSO cache and compiling every shader before loading the game and managing what must be loaded and unloaded at runtime, it's up to the developer to set all that up properly.
    • I think it depends on what you're looking for to do, and the time you have to spare. With my Dwarf 3, I easily spend 3-4 hour sessions; half an hour driving to an un-light polluted place, another half hour unpacking and setting up the smart scope + tripod for equatorial tracking, then 15 more minutes mucking around with settings and shooting calibration frames, spending a few hours shooting, merging with past photo sessions, etc. It's crazy how time flies and I often get home later than I expected. It's something I still need to set aside a good part of an evening to do, all in all. For one session, where you often need like four for best results when it comes to deep space objects. Even with a smart scope like Dwarf 3, regular non-astro photography is still way more approachable to people getting into photography. I find this is a time consuming niche no matter how I go about it. With practice, I can probably begin cutting time here but I think where smart scopes find their home is among people who love to shoot the night sky but don't have the spare time to go deep with the "navigator level" attunement to the night sky itself in addition to everything else. Having said this, _if_ you have even more time to spend on this hobby, it will probably be even more rewarding to do it more by hand and learn the skies and the details of how it all works.
    • I misread the title and thought Teams itself would be redesigned. Imagine having this one as a native WinUI app.
    • Dell, HP PCs ran into endless reboot, BitLocker recovery loops but Windows 11 isn't to blame by Sayan Sen Last month Neowin reported on a major issue on Dell systems wherein a bug in its official support tool was leading to endless blue screen of death (BSOD) and restarts. Following our report, Dell officially acknowledged its SupportAssist-related crash issue, confirming that the culprit is not Microsoft's operating system but rather a faulty version of its own remediation software. In a newly published support advisory, Dell stated that version 5.5.16.0 of Dell SupportAssist Remediation and Alienware SupportAssist Remediation can trigger blue screen errors and unexpected system restarts. The company notes that the problematic component operates independently of the main SupportAssist application, meaning users should not remove the primary SupportAssist software when troubleshooting the issue. According to Dell, the crashes are linked specifically to the SupportAssist Remediation service, which is bundled with SupportAssist OS Recovery Tools, and as such it has since released an updated version, 5.5.16.1, which is said to resolve the problem. Affected users are advised to first verify whether version 5.5.16.0 is installed by checking the Installed Apps section in Windows Settings. If so, Dell recommends updating SupportAssist OS Recovery Tools through either SupportAssist's "Update Software" feature or Dell Command Update. Dell also advises users to back up important data before performing the update and to ensure systems remain connected to power throughout the installation process. If you are still having issues though make sure to report to the Dell support forum. As it turns out though Dell is not the only PC maker currently dealing with update-related headaches as HP is also facing a separate but probably equally frustrating issue involving recent Windows Secure Boot updates that were released with recent Windows 11 Patch Tuesdays. Similar to Dell, HP also put up its own support article where it explains the issue. The company says that affected devices could hit a brick wall when booting as they run into a BitLocker recovery loop after the April 2026 updates. The problem appears to affect systems wherein the new UEFI Secure Boot CA 2023 certificates fail to apply properly. As such affected users will find themselves entering their recovery key over and over again despite the system otherwise functioning normally. HP says such PCs should be updated to the latest available BIOS version and configured with the necessary Secure Boot certificates before installing Microsoft's Windows 11 Patch Tuesday updates. Systems that are already experiencing the problem may require BIOS configuration changes to restore normal boot behavior. Admins can find information regarding that in the support article here on HP's official website.
  • Recent Achievements

    • One Month Later
      DJC50PLUS earned a badge
      One Month Later
    • Week One Done
      DJC50PLUS earned a badge
      Week One Done
    • Proficient
      Eric Biran went up a rank
      Proficient
    • Dedicated
      Conjor earned a badge
      Dedicated
    • Week One Done
      Windows Guy earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      493
    2. 2
      PsYcHoKiLLa
      246
    3. 3
      Steven P.
      72
    4. 4
      +Edouard
      69
    5. 5
      neufuse
      68
  • Tell a friend

    Love Neowin? Tell a friend!