Windows 2000 Modernization Tips

13»

Comments

  • edited June 28

    @win32 said:
    Ethernet or WLAN? WLAN requires a client not bundled with the OS, which is linked in the first post.

    Does it look good in device manager?

    Its called Ethernet Adapter, under Other Devices in device manager.
    I also cant get any sound.

  • You probably have HD audio, so try KB888111. It can't be installed properly after USP5.1 (slipstream only) but I think it will work after installing URP1.

    And try this for ethernet (Realtek RTL 81xx): https://www.techspot.com/drivers/driver/file/information/8557/

  • edited June 29

    @win32 said:
    You probably have HD audio, so try KB888111. It can't be installed properly after USP5.1 (slipstream only) but I think it will work after installing URP1.

    And try this for ethernet (Realtek RTL 81xx): https://www.techspot.com/drivers/driver/file/information/8557/

    Can you give me the download for KB8881111? Most downloads i could find were full of viruses.
    Also the ethernet driver's link is dead.

  • Still same problem with audio.
    And network problem has been fixed, thank yiu.

  • edited June 29

    If you installed the KB then the OS started to prompt you that a audio device on high definition audio bus was found, good. If not, then you'd have to slipstream the KB into your installation media with nLite and reinstall the OS (a repair install might be possible over the existing one).

    In any event, try this driver first. I've used this exact one on my workstation: https://drivers.softpedia.com/get/SOUND-CARD/REALTEK/Realtek-ALC880-ALC882-ALC883-ALC885-ALC887-ALC888-ALC889-ALC260-ALC262-ALC268-ALC272-ALC273-ALC662-ALC663-ALC861-HD-Audio-Driver-218-for-2000-XP.shtml

  • @win32 said:
    Now I've got some advice regarding virtualization software on Windows 2000.

    Preferably, install a program that is compatible with the vanilla OS (and with the OS identifier set to win2k), as installing newer versions under the guise of XP or 7 will confuse them, and not install services that are necessary for it to function. In fact any program that natively supports 2000 should be installed without any trickery for best results.

    In fact, I blue screened win2k when installing 7 x64 in VMware Player 3.1.2 (workstation 7.x based). Attempting to enable Aero caused it to crash and eventually corrupt the VMs (in Vista and 7), then I had problems with my mouse being unresponsive.

    How do i do that if i have kernelex installed?

  • It was more of a note to myself I made after I installed some software with the OS identifier accidentally set to XP or 7 using NNN4NT5, which comes with blackwingcat's fcwin2k package (and the "Windows 2000 Power Pack" that comes with newest kernels). For stuff like virtualizers or antivirus software which rely on device drivers, they could be installing ones very, very incompatible with Windows 2000 and could destabilize the OS.

    NNN4NT5 is for cases when installers are bootstrapped in that the installer loads another installer and they both check the OS version. Things can get messy if you forget to reset it back to 2000 SP4 and try to install OS components or anything that relies on device drivers.

  • edited July 2

    One weird thing popped up today. Seems that if I try to load any SSL sites in Internet Explorer (like Google), they won't work anymore. Same thing happens when trying to load my e-mail in Outlook. Yet, I can still load my e-mail under Windows 95, also in Outlook 2000.

    Edit: Updating the extended kernel to 3.0b fixed the issue.

    I believe installing Visual Studio 6 may have caused the problem. That's the only change I had made to the system.

  • I failed to mention the prerequisites for running Adobe CS5/6 installers. I was befuddled for awhile because I tried to run it, failed and discovered my previous notes in this thread lacked these important details.

    Turns out that .NET Framework 3.5 and the VC++ 2008 runtime are required in addition to setting NNN4NT5 to report the OS as 7 SP1.

    Damn this thread is messy!

  • @win32 said:
    I failed to mention the prerequisites for running Adobe CS5/6 installers. I was befuddled for awhile because I tried to run it, failed and discovered my previous notes in this thread lacked these important details.

    Turns out that .NET Framework 3.5 and the VC++ 2008 runtime are required in addition to setting NNN4NT5 to report the OS as 7 SP1.

    Damn this thread is messy!

    I installed Photoshop CS5.1 Extended the other day and set the OS version in NNN4NT5 to Windows XP SP3. Then once it installed, I set it back to Windows 2000 and used FCWIN to save the OS version for just that application to Windows XP SP3. Runs like a charm now. I don't think I have .net 3.5 installed (at least, I don't see it in Add/Remove Programs)...

  • edited July 7

    Hmm... from what I remember I couldn't get the installers to run with only .NET 2.0 SP2 and before installing VC++ 2008 the file copying process was blocked by an "lack of administrative privileges error".

    It is kinda weird because they don't need .NET on XP (or possibly 1.1, which comes with XP SP2/3). Maybe there's some common control in the package that enables it to run. Do you have any other update packages from BWC?

  • I did have VC++ 2008 installed because it came bundled with OpenOffice.org, but according to the registry and Add/Remove Programs, I only have .net 2.0 SP1. I wonder if we have different installers or something.

  • edited July 7

    That would be strange for the CS5.5 installer to work in a case where CS5 and CS6's don't work. I don't have it on hand but I've looked at some screenshots of it and it appears to be identical to CS5.

    Since I've installed those two things, I have also gotten the Office 2010 installer to run. However, with everything in the Professional Plus package checked, it fails at a certain point. Unchecking Microsoft Groove on win2k is necessary for Office 2007 to install, but unchecking its successor (SharePoint Workspace) doesn't help here either.

  • edited July 16

    An attempt to replace the NTVDM/WOW32 subsystem with the far superior one from Windows Server 2003 SP2 (which is the same one from XP) has failed due to missing functions in ntdll.dll and apphelp.dll.

    I'll be back for you, XP. We already got your device manager and your wannacry patches, now you will lose tie in the native DOS/win16 compatibility battle :p

Sign In or Register to comment.