Jump to content

win32

Member
  • Posts

    1,266
  • Joined

  • Last visited

  • Days Won

    79
  • Donations

    0.00 USD 
  • Country

    Canada

Everything posted by win32

  1. The AC'97 emulated by VirtualBox may not use the HDA bus. In this case, try the Realtek driver: https://drivers.softpedia.com/get/SOUND-CARD/REALTEK/Realtek-AC97-Audio-Codecs-NT-A404.shtml Or you can use the emulated Sound Blaster 16 which should be the path of least resistance for older OSes.
  2. Are you using a recent version of 7zip (v16 or above, though I think v9.xx+ is good enough)? You can also try using @i430VX's installer: http://i430vx.strangled.net/files/XP/RoyTam Browser Installer.exe
  3. win32

    MITM Checker

    Only one handshake failure on Windows 10 1809.
  4. Windows NT 4 service packs are cumulative. You can go from RTM to SP6a in one shot. And VirtualBox guest additions were available for NT4, well at least eight years ago when I last virtualized it, which would negate the need for the SNAP driver. For reference there is also a SNAP video driver for NT4.
  5. At a local supermarket: I had also stopped at an office with a beige P!!!/4 tower complete with two CD-ROM and two floppy drives. It wasn't on though or else I would have grabbed two XPs in one day!
  6. Adobe After Effects and Premiere Pro CS4 are the last 32bit versions and the last to be supported on XP. I tried installing Premiere Pro CS6 on XP x64 and there are missing functions (which I can't remember) but the PE version is indeed 5.2. All other Adobe products work up to CS6 in both x86 and x64 versions, but Photoshop CS6 is artificially crippled on XP with 3D and other advanced GPU-accelerated features disabled. Using application verifier or fcwin2k to make photoshop.exe and gpu_sniffer.exe think that they're running on Windows 7 SP1, then enabling GPU acceleration will fix that issue and it works as it would on a newer OS.
  7. @Nojus2001, you're definitely not alone. A weather forum I used to visit that closed sometime late last year or early this year was revealed to be running on Server 2003 until the bitter end. I'm sure that it's found itself mired into tonnes of big corporate networks too. It makes a wonderful workstation OS as well. And this is my 15-hour-old XP x64 install: :
  8. Here is my Windows for Workgroups 3.11 desktop. The OS is running on a FAT32 partition under MS-DOS 7.1 (Windows 95 OSR 2.5) on my IBM PC 300GL: And the same machine on Windows 95: And Windows 2000. For seven years I ran a 95/2k dualboot on my only desktop until I could start moving up in the PC world:
  9. Yes, it turns out i don't need to install windows 1.01 to play reversi after all! When we thought MS was giving up on XP they surprised us again!
  10. Thanks for finding that. That is the version 1 that they kept tucked away nicely enough that DDG didn't index it.
  11. I would like to use this opportunity to say that only the very first version (no SP) of the compatibility pack is compatible with Windows 2000 (vanilla; haven't tried later ones with the extended kernel). This version is no longer available from Microsoft though. So I wouldn't bother with updates in that case.
  12. The Windows 9x theme engine originated with the win95 plus! pack, then was bundled with 98/Me. And as such the themes encompassed the things mentioned above, as well as screensavers. I believe that Plus! 98 refined the themes applet by allowing for a monthly rotation of themes; that particular version was burrowed away in Windows 2000 (run themes.exe to use it). You can make and save your own theme files in addition to using the ones from the plus packs (and bundled with the later 9x OSes); a few downloadable ones are circulating but I can't remember because they are intertwined with the XP-style themes. You may also be interested in the LiteStep skinning engine, which supports 9x and win2k: http://litestep.net/ Unfortunately many of the newer themes don't like running on win2k and some of their dependencies are MIA. But if you pick up the "LS Installer" and then find some early 2000s themes you should be good
  13. Both updates include the exact same updated file (2003-based OSes get two files updated). So it doesn't matter which one is applied (unless POS XP blocks regular XP updates)
  14. The thing is that USP 5.1, whilst being built like a real Windows 2000 service pack, was not officially supported by MS. KB888111 predates USP 5.1 but is not included in it so it's considered superseded by the USP according to its QFE (which it's not) and doesn't install properly. The MS equivalent to the USP, SP4 UR1 (which is problematic in its own ways) should not have these issues due to it not being equivalent to a full SP. You could also use the HFSLIP FullPack (beware of nLite driver integration-related issues), which doesn't involve USP 5.1 and includes KB888111
  15. sorry about that. It was added in XP. I did recently note that in another thread that the Thinkpad T/R60 soundmax HD audio driver installer has an issue in which it will not detect the HD audio bus driver (KB888111) if the hotfix is installed after USP5.1. I also couldn't install the audio drivers manually, so it appears to be an issue at the OS level which may affect other HDA drivers The workarounds are to: -slipstream KB888111 into your installation media -install KB888111 before installing USP 5.1
  16. That is strange. Is the Windows Audio service enabled? Are there any resource/IRQ conflicts with the onboard audio? (latter is unlikely post-9x and especially with other drivers installed)
  17. More new features coming to win10 1903: But what I can't get over is the order in which the OSes evolve at the end. The lack of quality control has spread to M$ marketing!
  18. To avoid the issue where the audio drivers refuse to install on a ThinkPad T60/R60 (and possibly similar models), slipstream KB888111 along with USP5 and/or other updates when installing Windows 2000. Then it will PnP detect audio and modem devices on the HDA bus on first boot! There is also a caveat of running win2k on battery and trying to play some more-graphically intensive games (like Space Cadet Pinball and above): gameplay is incredibly jerky. I think disabling all power management options in the BIOS could solve that but I haven't tried yet.
  19. Have you tried this driver package (v6.10b)? It supports Windows 2000: https://driverscollection.com/?H=VT1708S&By=VIA&dpage=2
  20. You will have to install the USB drivers manually. Try ones other than those the OS has chosen by default, which the "update driver wizard" will show when clicking on the problem devices. What is your onboard audio? Realtek audio should work on vanilla win2k.
  21. You must have installed the Japanese version. The English version has no such issues (on my hardware) And even then, you can rename the start menu items to their original names. I know that BWC's VMware player 3.1.x tool does the same thing to My Documents and My Computer.
  22. That remark was in reference to the previous sentence about multithreaded versions of Firefox (given that Chromium 69 is multithreaded, which was cited as an advantage over the older Firefox-based builds that also run natively on vanilla XP). It was somewhat off-topic as well so I apologize nonetheless.
  23. @BTTB, Chromium-family browsers use multiple processes, whereas older Firefox-family browsers use a single process and typically in x86 Windows, a single process can only use up to 2 GB of memory (unless /3GB is set to assign 3 GB to programs and 1 GB for the kernel). Firefox 54 is the first multithreaded version, and 53 was successfully run on Windows 2000 extended kernel by @blackwingcat. I wonder if later 5x versions are possible with the kernel wrappers available for XP?
  24. I prefer Windows 2000 over other OSes for these reasons (among others): -I like the coloured box motif. The old Windows flag is the best. -Scales very well to hardware, running on a 486SX with 32 MB RAM to a i7-6950X with 32 GB (I have a Xeon X5670 with 12 GB DDR3-1333) -feels slicker than later Windows OSes. I can't get over how XP and 2003 take a split-second to bring CPU information in system properties whereas on 2000 it's instant. The only issues are with lack of MTP support and that my room feels like a sauna after running my workstation for a few hours (win2k forces my Xeon to run constantly at ~3.192 GHz, when it's supposed to be 2.93 GHz stock and with dynamic frequency scaling). If I succumb to heat stroke this summer because of Windows 2000, my next stop will be 2003 x86.
  25. uBlock Origin (latest version) works properly when the browser is run on Windows 7. It seems to run smoother as well.
×
×
  • Create New...