Jump to content

DosFreak

Member
  • Posts

    82
  • Joined

  • Last visited

  • Days Won

    3
  • Donations

    0.00 USD 
  • Country

    United States

DosFreak last won the day on October 21 2022

DosFreak had the most liked content!

1 Follower

About DosFreak

Profile Information

  • OS
    95

Recent Profile Visitors

3,448 profile views

DosFreak's Achievements

14

Reputation

  1. Steam is a bloated POS anyway. Download the game on a machine with a supported OS. Copy to the game to the XP machine. I can't be any more specific on this forum unfortunately.
  2. I'm not near my file server right now but I do remember testing BuildGDX w/kernelex on 98SE and ME Java 8 U231 and Azul Java 8.0.292 IIRC, you need to install 8 U152 and then extract the Java 8 U231 files to the java directory for working java with 2000 BWC and XP. I'd be suprised if that version of Azul Java didn't work on XP since it works with kernelex https://www.vogons.org/viewtopic.php?p=989192#p989192 https://www.vogons.org/viewtopic.php?p=907228#p907228
  3. You are still better off with Vmware Player 3.01 or Vmware Workstation v7.1.3 but to each their own.
  4. This is from a note I made for myself back in 2010: v1.6.6 is the last version to work on Windows 2000 but BlackWingcat modified Vboxc.dll and Vboxdrv.sys in VirtualBox 2.0.4 so that version works in Windows 2000. 1. Download VirtualBox 2.0.4 2. Run the install, when it errors out leave the error up. 3. Go to the TEMP directory in your profile and make a copy of the VirtualBox .msi. 4. Edit the .MSI with Orca and remove the LaunchConditions. 5. Install VirtualBox 2.0.4. 6. Download "vb202-4w2k.zip" from BlackWingCat. 7. Reboot. 8. Extract the contents of "vb202-4w2k.zip" to their proper locations. 9. Execute VirtualBox.
  5. Purchase Private Internet Access Use this: https://www.codeproject.com/Articles/5323785/OpenVPN-for-Windows-XP#topic16 or setup your router to connect to the VPN
  6. https://colinfinck.de/posts/modern-visual-studio-meets-ancient-windows/ https://colinfinck.de/posts/targeting-25-years-of-windows-with-visual-studio-2019/ https://github.com/enlyze/EnlyzeWinCompatLib/tree/clang This issue may allow 9x compatibility and appears to mention the functions mentioned at stackoverflow: https://github.com/enlyze/EnlyzeWinCompatLib/issues/1 The below may or may not apply anymore but it's something I've been meenting to look into: https://stackoverflow.com/questions/19516796/visual-studio-2012-win32-project-targeting-windows-2000/53548116#53548116
  7. Can't commit to this since working other things but I really should since I need to for the https://www.vogons.org/viewtopic.php?f=5&t=84578&hilit=vogonsorg Here are some interesting links: https://www.vogons.org/viewtopic.php?f=5&t=87617 https://www.vogons.org/viewtopic.php?p=1021297#p1021297 (This post and various others before it) Stay far away from MSYS2 unless you use a win32 thread build of mingw-w64 and compile all third party libraries yourself. pacman and vpkg precompiled binaries are all posix. Last time I tested mingw-w64 on Linux and WSL were win32 thread. As of 2021 latest current GCC could compiled for NT3.51+. For Posix XP support was broken with those commits. So right now if I were to start I would: 1. Verify on Linux and WSL that latest GCC win32 thread could compile a working binary. If so and don't need posix then you're done! 2. If Posix needed then download a last known working build by downloading a working mingw-w64 package from repos, start from before those commits. My MSYS2 environment where I compiled via clang for XP was created on 5/31/2018. 3. Once you have a working Posix environment then save it and keep it safe! 4. Download mingw-w64 from just after those two commits, revert them and compile. If working environment then save it! 5. Work upwards until you have the latest mingw--64 Keep in mind that pre-compiled mingw-w64 is i686+ so if you need to support less than that you'll need to recompile. I'm lazy so I just use regular mingw for i386+ for those binaries but it's always been on my list to look into recompiling mingw-w64 for that support. You shouldn't have to limit yourself to an old version of VS, latest version should be fine as long as you use mingw-w64 to compile unless I'm missing something.
  8. The XP/W2k3 on Modern Hardware thread continues on a different forum: https://www.win-raid.com/t9792f45-Lets-continue-on-WinCert.html /EDIT Sorry, didn't see the post above.
  9. v0.41a for 98SE-ME-NT4-2000 on the host v17 works if you use BWC. Eventually I'll get around to patching the latest ver of SDL2 for Windows 2000 and compiling a pcem build for vanilla 2000 but still working on getting my VMs setup. https://github.com/vogonsorg/SDL/issues/1 https://www.vogons.org/viewtopic.php?f=5&t=84578
  10. Not that it has anything to do with the topic but if you have a 64bit processor then with vmware player 2.5.5 or 3.0.1 (with BWC changes) you can run 7 64bit as a guest on a Windows 2000 host. Something to try would be qemu 1.0.1 http://vpsland.superglobalmegacorp.com/install/qemu-1.0.1.7z or 2.7 (with BWC) on Windows 2000.
  11. 9x vmware-workstation-4.5.3 Qemu 0.15.0 w/kernelex Bochs 2.3.7 Bochs 2.6.11 w/kernelex Bochs 2.7 might work with kernelex https://www.bttr-software.de/download/bochs/ If above requires SSE2 then try Bochs 2.6.6 w/ kernelex
  12. To download Windows Updates for 2000 to Vista: 1. Use your own WSUS server (Win 2022 WSUS goes all the way back to Windows 2000) and point XP to it or 2. Go here https://forums.mydigitallife.net/threads/restore-windows-update-for-windows-xp-server-2003.82538/ and follow the instructions in the readme for WSUS proxy. The proxy works fine on XP itself so no need to run it on another machine unless you want to update Windows 2000 then you'll need to run the proxy on XP+ and run the minitool on 2000. Verified all this last week on both 2000, XP 32bit and 64bit and Vista 32bit and 64bit (for Vista I used the Windows Update client fix for Vista 6003 instead) https://forums.mydigitallife.net/threads/restore-windows-update-for-windows-xp-server-2003.82538/ For POS just add the registry key but beware if the CPU doesn't support SSE2.
  13. If you are interested in mods try gzdoom 4.1.3 first, if video card not supported then try lzdoom.
  14. The below are the highest versions that work on each OS the last time I tested: DOS eternity-dos-v33920-7 FastDoom 0.8.7 MBF 2.04 95 Zdoom LE 2.8.1f 98SE-ME Chocolate Doom 2.3.0 Crispy Doom 3.2 Doom Legacy 1.48.8 PrBoom+ 2.5.1.4 Rude 2.5.0c ZDoom32 2.8.6 98SE-ME (KernelEX) chocolate-doom-20210726-win32 crispy-doom-20210725-win32 PrBoom+ 2.5.1.7um Rude 3.1.0pre Woof! 6.2.0 2000 (BWC) Crispy Doom 4.3 2000 (BWC) - XP 32 LZDoom 3.88a 8-8-2021 (change major version) XP 32bit chocolate-doom-20211019-win32 crispy-doom-20211019-win32 Doom Retro 4.3 10-15-2021 Eternity-x86-4.03.00-pre-412-g47dcc309 10-18-2021 gzdoom 4.1.3 6-8-2019 PrBoom+ 2.5.1.7um 6-16-2019 Rude 3.1.0pre11 10-31-2020 Woof! 7.0.0 9-27-2021 dsda-doom 0.21.3 8-30-2021 Vista 32bit gzdoom 4.4.2 k8vavoom 4.1 PrBoom+ 2.6um Vista 64bit gzdoom 4.5.0
  15. Post here: https://github.com/joncampbell123/dosbox-x/issues
×
×
  • Create New...