Jump to content
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble

MSFN is made available via donations, subscriptions and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. Alternatively, register and become a site sponsor/subscriber and ads will be disabled automatically. 


DosFreak

Member
  • Content Count

    40
  • Donations

    $0.00 
  • Joined

  • Last visited

Community Reputation

2 Neutral

About DosFreak

Profile Information

  • OS
    95
  • Country

Recent Profile Visitors

940 profile views
  1. Never had that error message. Vmware 6.5.5 is the last ver to run on Windows 2000 vanilla. Vmware 7.1.3 with Blackwingcat files VMWare Workstation v7.1.3 (This was from back in 2011 so not sure what the latest ver of Vmware is now with extended core) 1. Installers errors out on not being compatible with Windows 2000. 2. Use FCWIN2k from the KDW wrapper to fake Windows XP SP3 to begin the install. 3. When the install gets to a dialog window DO NOT CLICK THROUGH. 4. Go to the TEMP directory of your profile. 5. Make a copy of the vmware folder. 6. Close vmware setup and fcwin2k. 7. Make a backup copy of "vmware workstation.msi" 8. Modify vmware player.msi with Orca and remove the LaunchCondition. 9. Executing vnetlib.exe in installation folder you will receive the following error: "The procedure entry point GetInheritanceSourceW could not be located in the dynamic link library ADVAPI32.dll" YOU MUST PERFORM STEP #10 OTHERWISE VMWARE WORKSTATION WILL NOT INSTALL!! 10. Install the KDW wrapper and install advapi32.dll 11. Install Vmware Workstation. 12. During install you may receive the following errors: --------------------------- vmnat.exe - Entry Point Not Found --------------------------- The procedure entry point CancelIPChangeNotify could not be located in the dynamic link library IPHLPAPI.DLL. --------------------------- vmware-authd.exe - Entry Point Not Found --------------------------- The procedure entry point GetProcessImageFileNameW could not be located in the dynamic link library PSAPI.DLL. Just press OK to contiune. (We will fix these errors later) 13. After install is done reboot. 14. Download vm313a.zip from Blackwingcat. 15. Modify the script to reflect changes for vmware workstation instead of player. 16. Run the script and then reboot. 17. Vmware Workstation should now work.
  2. https://www.vogons.org/viewtopic.php?f=5&t=68600&p=779629#p779629 This seems to work pretty well in a VM. There seems to be a mouse input error in Windows 2000 (left mouse click to fire keeps firing) in a VM not sure if a Vmware tools issue or an SDL2 issue with blackwingcat extended core and the usual issue with relative\absolute mouse control issues with VMs. Possibly mouse issue in 98. Mouse works in game menus but not in game. Need to verify not a vmware issue. Going to test the above on a physical machine eventually.
  3. For testing you can try masking the feature bit with Vmware. This was helpfully when troubleshooting mingw compiled programs that had issues running on certains cpus. I haven't tested with Windows updates yet. https://www.vogons.org/viewtopic.php?f=31&t=55706&start=20#p767756
  4. Is there any reason you want VS2010 on 2000? VS2008 works and can compile for NT3.51-2000. (Use with legacyextender for NT3.51-95-98-NT4) VS 2019 can compile for XP. If you do get VS2010 working on Windows 2000 there is no guarantee the compiled executable will work since VS2010 does not support 2000. (Obviously using the Blackwingcat Kernel works around this). https://www.tapatalk.com/groups/win2kgaming/visual-studio-2008-on-windows-2000-t515.html For my projects where I use VS I use VS2008 for NT3.51-2000 and VS2019 for XP but I use my host Windows 10 for compiling.
  5. If you want to try something slightly newer with TLS 1.2 support here is Opera 10.70 Build 9071: https://www.vogons.org/viewtopic.php?f=24&t=12102&start=20#p730673 As roytam1 mentioned above his QtWeb 3.8.4 build works great as well.
  6. Don't know if this is helpful or not but according to this http://wp.xin.at/archives/4479 you can compile OpenSSL to not rely on Windows bcrypt or CryptAPI using the no-engine switch
  7. AES-GCM, 256 bit keys, TLS 1.2 Was the TLS 1.2 update ever released for 2003?
  8. If I use ProxHTTPSProxyMII with the SSL passthru it appears to work. Without the proxy I get the same error as you do. Tested on Windows 2000. When I enter this URL in IE: http://www.update.microsoft.com/microsoftupdate/v6/default.aspx?ln=en-us The proxy shows: [10:54] 000 [D] SSL Pass-Thru: https://www.update.microsoft.com:443/ [10:54] 000 [D] SSL Pass-Thru: https://www.update.microsoft.com:443/
  9. I have no interest in that game at all but it was interesting how they decided people were using DX9 to get rid of shadows versus people using DX9 because that's all their video card was capable of....unless they are going to provide DX9 feature level support with DX11 so people with DX9 cards can still play the game. They probably aren't though since people with DX9 cards are poor and shouldn't be playing games on old hardware. (Usual Steam forum user answer). heh. Wonder if Linux users care about this since ProtonDB recommends disabling DX11.
  10. I've done some more testing: https://www.vogons.org/viewtopic.php?f=24&t=12102 Windows 95 Vanilla: 10.10 KernelEx 10.70 Build 3488 with modifications to opera.exe and opera.dll Windows 98 Vanilla: 10.63 KernelEX v12.02 Build 1578 NT4 Vanilla: 10.63 10.70 Build 9071 with modifications to opera.exe For 2000 Vanilla: v12.02 Build 1578 BlackwingCat Extended Kernel v38.0.2190.0 v12.18 Build 1872
  11. https://www.vogons.org/viewtopic.php?f=24&t=12102&p=83132#p83132 OFFICIAL Use v12.02 Build 1578 UNOFFICIAL (Use Advanced Chrome 54 instead) Use v38.0.2190.0 Use BlackWingcat Windows 2000 Extended Kernel v2.9b Launch with --no-sandbox
  12. If you check the \bin and \packages folder you'll see a cef folder and files. These are different based on the version of Windows. So XP and 7 files are different. They are all loaded by Steam.exe so if for example MS compiles their files for Vista+ and/or remove the XP specific files and/or change their backend servers to TLS 1.3 then that will likely kill it. If you care about your games remove your reliance on the Steam client. It's not that difficult to get rid of and still play your games. Make sure you have the steam.cfg option set to prevent updates and/or block writes to the packages folder if you insist on using the Steam client.
  13. I looked into this a bit the other day. Steam is looking for APIs that Windows 2000 (not even with Extended Kernel) does not have. It doesn't matter anyway since Steam XP support has been dropped and even though it still works it remains to be seen what the next Steam update will bring and Steam requires TLS 1.2 (at least SteamCMD does) which 2000 does not support. It's best not to use the Steam client anyways since there are working methods to run Steam games without Steam and those methods do work on Windows 2000.
  14. SteamCMD still works fine on XP. Check my vogons post. You'll need to install and enable the TLS 1.2 update. It's a PITA to use and you'll have to redownload all your games. I personally don't see any issues discussing and sharing old versions of the Steam client but it depends on how the forums are moderated. Really though best not to deal with the Steam client since it's unecessary anyway. The community has pretty much solved most of the issues as far as Windows Steam games are concerned.
  15. I had posted a topic previously on this but it was taken down. If you check the Deep Thought forums at vogons you'll see a guide created by myself for running your Steam games without Steam. The only thing you'd potentially need Steam or SteamCMD for is downloading your games and when those no longer work you can always download the games on another computer and copy them over. Currently Steam and SteamCMD (Requires TLS 1.2) but who knows what the next update will bring wether on the client or the backend.
×
×
  • Create New...