Recommended Posts

  • 3 months later...


Windows Me was a joke, it was so crash prone that I (and most people i knew) could not last a week with it.

 

Unbelievable, that it was released in the state it was.   No machine was immune to crashing.

 

Actually I loved ME, never had any problems with it, but then I was running it on a 'top of the line' k6-III 450 with 384mb of ram and a rage pro AGP on the first system, and a 1ghz Athlon, 384mb DDR and a radeon 9650 (later upgraded with a x850AGP.) and 33.6k ISA modem until I went broadband and got an ISA 10mb ethernet card.  I didnt use pci for net cards as most were software based and back then every cpucycle counted.  Hardware-controller based network cards were a must.  I ran 95 on the k6-III which was a k5 133 when it was first built, and ME was a nice step up from 95.

I still run ME in a VM for old games.

 

ME hates crappy hardware, and runs best on AMD processors.  It needs a true hardware 3d accelerated gpu with at least 4mb of memory on the card if you want a trouble-free system.

 

XP was awesome.  I was slow to upgrade from ME as some apps werent nt-friendly so it wasnt until I got an Athlon xp-1800+ and 512mb of ram that I made the switch.
initially It took a little getting used to the new GUI but as soon as I got a feel for it, I was really impressed.  I still run XP on a dedicated game machine (phenomII955BE 4gb ram radeon HD5850).
XP has been the workhorse on all my machines since I migrated from ME, but now my main system runs win7.  I skipped vista completely, running XP until 7 came out.
dont like 8-8.1 but in time 10 will probably be the new 7 as 7 is the new XP now.

 

speaking of nostalgia, who else remembers the AM486dx66, Win3.11, and VESA localbus.

This topic is now closed to further replies.
  • Posts

    • The problem isn't with Epic, it's with the platform holders like Steam and Nintendo, they should be a lot more strict in their review process.
    • Hello, Installed here without issue. Regards, Aryeh Goretsky
    • Microsoft updates Visual Studio Code with easier language model discovery and in-app search by Paul Hill Microsoft has released Visual Studio Code 1.125, its latest weekly release. This week, the company has focused on discovering and installing extra language models via the Marketplace; searching the web and securely browsing over remote connections without leaving VS Code; choosing how long VS Code waits before installing extension updates; and delivering managed Copilot settings through existing device management tooling. In older versions of VS Code, extensions could contribute their own model providers, but to find these extensions, you needed the right tags to search for in the Extension view. Now, the Language Models editor gives you an Install Model Providers button that opens the Extensions view, which is filtered to extensions that contribute model providers, making it easier to find and install them. Once you install a provider, its model will appear in the model picker. If you use the integrated browser much, you can now look up information without leaving VS Code by typing a query into the integrated browser’s address bar. It will use your configured search engine, the same way a standalone browser does. You can use workbench.browser.searchEngine to pick a search engine. When the browser is opened in a remote workspace, it's now possible to proxy HTTP(S) traffic via the remote connection. This allows you to connect to any ports or services that can only be accessed from the remote machine. If you read our coverage from two weeks ago about VS Code 1.123, you might have seen that extension updates have a two-hour delay as a safety measure. In this update, Microsoft is giving you the ability to configure the time of the delay. You can find it under extensions.autoUpdateDelay. Finally, with this update, admins can deliver managed GitHub Copilot settings through native device management (MDM) channels on Windows and macOS, in addition to account-based enterprise settings files. Settings delivered via MDM appear as policy-enforced in VS Code and can’t be overridden locally. Future updates will extend the supported policy keys across Copilot surfaces. You can download the update from the Visual Studio Code website now.
    • "it opens up new doors for people who prefer using Edge, but cannot be bothered to configure a Microsoft account" You already have a Microsoft account if you are using Windows 11, because you can't set it up without one.
  • Recent Achievements

    • Week One Done
      Classifyskilleducation earned a badge
      Week One Done
    • One Month Later
      eurospharma62 earned a badge
      One Month Later
    • Week One Done
      With What earned a badge
      Week One Done
    • Week One Done
      Harris Gilbert earned a badge
      Week One Done
    • One Month Later
      Vincian earned a badge
      One Month Later
  • Popular Contributors

    1. 1
      +primortal
      543
    2. 2
      +Edouard
      171
    3. 3
      PsYcHoKiLLa
      84
    4. 4
      ATLien_0
      64
    5. 5
      neufuse
      64
  • Tell a friend

    Love Neowin? Tell a friend!