Recommended Posts

Stable? You must be drunk or got hit in the head

Compared to Win me and Windows98 it had an NT kernel. Protected memory. It was impossible to crash unless something ran as a device driver or ran as administrator and tampered with another memory stack somewhere.

WINDOWS 98 had no concept of memory management for most apps. BSOD galore.

In 2001 XP was simply amazing

Compared to Win me and Windows98 it had an NT kernel. Protected memory. It was impossible to crash unless something ran as a device driver or ran as administrator and tampered with another memory stack somewhere.

WINDOWS 98 had no concept of memory management for most apps. BSOD galore.

In 2001 XP was simply amazing

 

It was still a crashy mess, BSODs were a common thing till vista really 

I never had one ... ok I had one Irq not less than or equal to due to a crappy via driver that I fixed.

People aren't afraid to leave that os because they are stubborn. They remember the horrors of daily reboots before XP.

With good hardware and drivers XP was great for it's time. True insecure and terribly outdated today but that commercial brought a flash black to me in my link

?? Nostalgia, there's still companies using it...

 

XP wasn't good until SP1.

 

It was good pre SP1. I used it day 1 :)

 

Compared to WindowsME it was a MUST. The issue with SP 1 was some older chipsets and security bug. I used blackICE before the built in firewall with XP SP 1 and just built a blazing 700 MHz Pentium III with a solid intel board. No problems at all. Yes it was slower at the time but I had a HUGE 384 megs of ram to handle it. Yes I could only do 5 tabs in Mozilla before it ran out of ram. :-)

 

Yes the companies are idiots. To this day I refuse to work for anyone running XP unless it is in a VM or some piece of non networked equipment. Someone who does not value IT that much will fire you when their own incompetence hits and does not assign value to your role. Bad combo.

?? Nostalgia, there's still companies using it...

 

XP wasn't good until SP1.

 

 

Here's nostalgia - 

 

Wow voice recognition was truly aweful in that link. He had to talk like a robot in slow mode. I am used to GoogleNow today

  • Like 1

Companies aren't idiots, not all companies put IT as their number 1 priority.

 

Good luck missing out on money if you're refusing jobs, that's just stupid. I know my local mechanic probably doesn't like working on some of the ###### boxes customers bring in, but he won't refuse to fix hem. 

 

Windows 2000 was used up until XP SP2 in a lot of companies. 

XP  was still better than this whole tablet infestation MS is following in this decade. 

 

Sounds like you're just afraid of change </sarcasm.

 

I think microsoft realized the tablet thing didn't take off like everyone thought it would.  Still need our sexy pcs.

The idea of what they're doing with 10 is interesting, and might just work.

 

 

I hated windows 8 and 81. But 10 is nice.

 

Looking at windows xp now, man that thing was ugly. Looked so sexy at the time, ha. funny how things can change like that.

XP wasn't good until SP2 (That's when they started doubling down on security, that was the whole point of SP2), and these days anything short of SP3 is basically broken.

Of course, even XP SP3 is still broken, no version of IE is secure on XP, anybody still using it on the internet needs to be using Firefox or Chrome.

  • Like 2

It was very nice of MS to let a 3 year old with crayons design the interface, though.

 

Anyway, XP was way more stable than 9x, but not nearly as stable as what followed. So.... progress?

  • Like 3

I didn't listen to the commerce, but that was fine.  I remember though when Microsoft was about to release it, they had to change the slogan from what you see in the video due to the Sept 11, attacks. 

 

https://www.neowin.net/news/yes-you-can-new-windows-xp-slogan

 

I have logged into Windows XP systems lately, and I have to admit, that while I have some nostalgia, I am glad they have moved on.

This is all I remember about XP:

 

windows-xp-blue-screen-death-bliss.jpg

Oh, and this:

 

308.jpg

 

YIKES OMG. I am so glad the infections with IE 6 especially pre-SP 2 are gone. Yes people still get infected more than ever but I see bonzia buddy which I complete forgotten about and the miltion different toolbars and everyone and their brother installing auto-starts to make their programs load faster slowing bootup time. Ok Dot I do not miss that about XP you win hands down.

 

But my BSOD drastically went away with XP expect when I bought a few shady boards with poor drivers. Windows 98 based on DOS just let programs run wild stealing and over writing ram addresses and causing constant crashes. It was defective by design and I was a Windows hater back then as a result. Truly awful.

Don't forget this.. I so don't miss the pre-DWM days.

happytrail.png

 

Mostly skipped XP myself.. didn't get passable till SP2 but that period (and most of Vista, till the last service pack) was where I spent most of my desktop computing time on other operating systems. The last time I literally saw a BSOD on my own hardware, barring one cooling failure which isn't the OS's fault, was with XP.  Fairly regular occurrence, never mind Explorer itself taking a dive just because it felt like it.  Was a nice improvement to 95 sure but certainly don't find myself ever missing the thing.  Terrible x64 support.  Don't get me started on "Documents and Settings".. like nobody ever uses a console? Sheesh.

Stable? You must be drunk or got hit in the head

 

It was stable.  Obviously not as stable as Vista, 7 or 8x...but more so than its predecessors.  Progress does that.

 

This is all I remember about XP:

 

 

Oh, and this:

 

 

 

haha...guess you never got work done since you maintained an infected computer (if that is all you remember your XP looking like) 

  • Like 2

Don't forget this.. I so don't miss the pre-DWM days.

happytrail.png

 

 

 

I do remember this, lol... It was used to occur mostly in full-screen games. Roadrash game always gave me this glitch.  :p

Windows 10 would have no problem taking XP users from XP if they just offered a windows XP mode. Whether it was a graphical interface (dare I say theme) or the options to sandbox the old apps (OS) into a XP mode.  10 should offer a secondary host OS option  to just plug in the old XP drive and continue from there. 

Windows 10 would have no problem taking XP users from XP if they just offered a windows XP mode. Whether it was a graphical interface (dare I say theme) or the options to sandbox the old apps (OS) into a XP mode. 10 should offer a secondary host OS option to just plug in the old XP drive and continue from there.

My point was the XP commercial with Madonnas ray of light gave nostalgia. Not still live in 2001

I do remember this, lol... It was used to occur mostly in full-screen games. Roadrash game always gave me this glitch.  :p

It's not actually a glitch, it's a side effect of how Windows handled rendering things to the screen pre-DWM. Back then, every application rendered directly to the screen framebuffer, in a back to front fashion (Wallpaper then taskbar, etc.). Because of that, every single time a window moved, Windows would tell the applications behind it to repaint the contents of their windows to the framebuffer, and the application in front of it would then overwrite it with their contents (Which is really really dumb, lots of work done for content that's never seen, that's why moving windows around caused CPU usage spikes in random applications below the moving one). The problem happens when one of those background applications locked up, so it stopped repainting the window contents, so when you moved a window that was above the hung application, the hung app couldn't repaint its window and the contents of the moving window would be left in the framebuffer in that area (Similar to the winning animation in Solitaire, it moved the cards without clearing the previous frame)

The DWM changed everything, instead of rendering directly to the screen framebuffer, each application actually renders to a separate buffer in memory, and every time something changes the DWM comes along and re-composites those buffers to the screen. Downside is, you've got increased memory usage due to each application having separate buffers rather than sharing them (But they're on the GPU so who cares), upside is that now when a application hangs, the DWM still has a complete copy of the window contents, and can apply snazzy effects like desaturating it to show it's hung. And because each buffer is separate, Windows doesn't have to inform applications that a window is covering them, so no more random CPU usage spikes in background applications when you move a window around.

You've got the ability in Vista and 7 to disable the DWM though (Which people did because they thought it helped performance :laugh:), so the pitfalls still exist there. It wasn't until 8 that Microsoft actually enforced the DWM as the one true rendering pipeline, even on crap systems without a working GPU, thanks to WARP. Also the implementation of the buffer sharing in Vista disabled GDI hardware acceleration (GDI being the Windows 3 graphics API), that was apparently a problem at the time, but when Microsoft fixed it in 7 nobody cared.

never been a windows fan - especially now since i really know and understand linux and it's endless advantages - but one thing has to be said:

win xp was an amazing step from win 9x, much more stable, better structured, finally a new desktop theme (it was not THAT bad back in 2001) and soon lots of customization was possible. all in all probably the windows i used for most of the time and the one overall i liked most.

then came win vista, again lot's of visual changes i loved, bought the ultimate edition to get all ultimate extras. they never arrived, and things started to go downhill ever since.

This topic is now closed to further replies.
  • Posts

    • But the reality is it will work for people's needs, and they don't care about the technology that makes it. Clearly not everyone's needs, but that low end space where personal laptops were only used to type emails, watch content and browse websites, but they didn't want to do that on a small screen device. Heck, writing that out I can now see the connection and reason it'll do so well. Apple is about experience. If the experience is bad, they don't release it. Low end Windows laptop manufacturers up until this point have not taken that into consideration ever before, so slow laggy usage with brittle slimey plastic shells were common. I hope that the low end space at least creates better physical products that last a bit longer, and if Microsoft get their act together, they could also have a solid OS on such low end hardware that would actually make the experience work for what the hardware was intended for. The fact that the CPU is a "cellphone", sorry mobile phone processor is irrelevant. It's about the experience, and so far, that sounds quite solid.
    • Hello, Bonjour is Apple's implementation of a multicast-DNS service, which allows devices running Apple's software and/or hardware to find each other on your local network.  I believe the Windows version was last updated around 2010. If you do not need it, you can stop and disable the Bonjour service in the Services Control Manager (filename: SERVICES.MSC).  Once you have done that, the operating system will no longer attempt to load the service. Regards, Aryeh Goretsky  
    • This AMD RX 9070 16GB GPU that performs close to Nvidia 5070 is under $600 by Sayan Sen With the memory shortage that's prevalent nowadays, discounts are super-hard to get. As such we post good deals whenever they pop up. Recently, we covered a few great discounts on SSDs wherein you can get a 4TB TeamGroup NVMe PCIe Gen4 drive for just $400 thanks to a special coupon. If you want a faster product but don't need all that capacity, you can also opt for Samsung's 990 PRO 2TB that is on sale for its lowest price in over three months. Let's say though that you are on the hunt for a 1440p gaming card. In that case AMD's RX 9070 non-XT can help, and with its 16GB VRAM, you can also run AI models locally without worrying about bottlenecking (check out our recent 9070 GRE reviews for gaming and productivity to get an idea). The PowerColor Reaper variant of the RX 9070 is currently on sale for just $580 which is a very good price in the current state of affairs (purchase link under the specs table down below). The Reaper cooler on this 9070 uses a triple‑fan design with ring‑blade fans, paired with premium dual ball bearings to extend lifespan and reduce friction. "Intelligent" fan control allows the fans to remain idle at lower temperatures, only spinning up when the GPU is under load. A nickel‑plated copper base makes direct contact with both the GPU and memory modules, helping to spread heat evenly. PowerColor also applies Honeywell PTM7950 phase‑change thermal interface material (TIM), which fills microscopic gaps between the die and heatsink for more efficient thermal transfer. The fan shroud is shorter in height as the firm has made it such that it can be used in certain SFF (small form factor) cases. The technical specifications of the Reaper RX 9070 are given in the table below: Specification Value Stream Processors 3584 Units Video Memory 16GB GDDR6 Memory Speed 20.0 Gbps Memory Interface 256-bit Engine Clock Game Clock: up to 2070 MHz Boost Clock: up to 2520 MHz Bus Standard PCI Express 5.0 x16 Display Connectors 1 x HDMI 2.1b, 3 x DisplayPort 2.1a Maximum Resolution DisplayPort: 7680 × 4320 HDMI: 7680 × 4320 Board Dimensions 289mm × 111mm × 41mm 304mm × 127mm × 42mm (with bracket) Slot 2 Minimum System Power Requirement 600W Power Connectors Two 8-pin PCI Express Get the PowerColor Reaper RX 9070 at the links below (you get only a 90-day warranty on Woot): PowerColor Reaper Radeon RX 9070 16GB Graphics Card (RX9070 16G-A): $579.99 (Sold and Shipped by Amazon US) (Was: $700) PowerColor Reaper Radeon RX 9070 16GB Graphics Card (RX9070 16G-A): $559.99 (Sold and Shipped by Woot US) Good to know This Amazon deal is U.S. specific, and not available in other regions unless specified. We only use first-party seller links (at the time of article publishing); ensure that you purchase from a first-party seller link only. Check out Today's Deals on Amazon | or our recent tech deals. Become a Prime member (for Students or SNAP) via Neowin Get Prime Access - Prime for half price (for qualifying Medicaid, EBT, SNAP) Subscribe to Prime Video, Audible Plus, Music Unlimited or Kindle Unlimited via Neowin As an Amazon Associate, we earn from qualifying purchases.
    • Are they marketed as an entry into astronomy or astrophotography? I do astrophotography. With big rigs, lots of computers, cables and headaches. I love it. And by learning this ridiculously complex hobby, I’ve learned about the objects I’m shooting. Astronomy followed from photography.
    • Microsoft confirms Recycle Bin bug across all versions of Windows by Usama Jawad A couple of days ago, we reported that the latest Patch Tuesday update has seemingly resulted in a lot of issues for many users, including OneDrive and Dropbox access problems, BitLocker recovery lockouts, and BSODs. Although Microsoft is yet to acknowledge these bugs, it has confirmed another, relatively smaller issue across all supported versions of Windows. In an update on its Windows Release Health Dashboard, Microsoft has confirmed that after installing June's Patch Tuesday update (KB5094126), you'll experience unexpected behavior when leveraging Recycle Bin. Basically, when you attempt to delete an item from the Recycle Bin, the confirm dialog will show you the internal file name of that content rather than the actual name. For example, the file may be named abc.png, but the confirm dialog will ask if you're sure that you want to permanently delete $Rxxxxx.png from the Recycle Bin. This is pretty much it for the scope of the bug itself; it just displays the wrong name in the confirm dialog. The correct name will be shown in the list view of the Recycle Bin and if you restore the file, it will return with the correct name as well. This issue affects pretty much all supported versions of Windows client and server, including: Client: Windows 11, version 26H1; Windows 11, version 25H2; Windows 11, version 24H2; Windows 11, version 23H2; Windows 10, version 22H2; Windows 10 Enterprise LTSC 2021; Windows 10 Enterprise LTSC 2019; Windows 10 Enterprise LTSB 2016 Server: Windows Server 2025; Windows Server 2022; Windows Server 2019; Windows Server 2016; Windows Server 2012 R2; Windows Server 2012 As things currently stand, Microsoft is working on a concrete solution that will be released in a "future" Windows update. It remains to be seen if the firm will wait till the next Patch Tuesday or roll out an out-of-band (OOB) fix. The good news is that commercial customers can deploy a workaround right now, but they will have to reach out to Microsoft Support for Business for additional details.
  • Recent Achievements

    • Week One Done
      Jordan Smith earned a badge
      Week One Done
    • Reacting Well
      BizSAR earned a badge
      Reacting Well
    • First Post
      AndreaB earned a badge
      First Post
    • Week One Done
      Huge Trailer earned a badge
      Week One Done
    • Week One Done
      Classifyskilleducation earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      579
    2. 2
      +Edouard
      184
    3. 3
      PsYcHoKiLLa
      75
    4. 4
      Michael Scrip
      72
    5. 5
      neufuse
      64
  • Tell a friend

    Love Neowin? Tell a friend!