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. 


loblolly986

Member
  • Content Count

    7
  • Donations

    $0.00 
  • Joined

  • Last visited

Community Reputation

2 Neutral

About loblolly986

Profile Information

  • OS
    none specified
  • Country

Flags

  • Country Flag

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. @Wunderbar98 - Roy's package adds support for additional ciphers such as ChaCha20-Poly1305 and a SHA384-based cipher; it doesn't just enable a couple existing about:config settings by default. A couple screenshots of the ciphers listed in my updated installation's about:config are below. Roy's forked RetroZilla repo is here (different patches are stored as separate "branches"): https://github.com/roytam1/RetroZilla "Pull requests" page for rn10950's repo with requests by Roy that haven't yet been merged: https://github.com/rn10950/RetroZilla/pulls
  2. The comparison is actually ~29.7 MiB vs. ~33.8 MiB looking at the uncompressed size of Roy's updated 7z package vs. the official 2.2 ZIP package, respectively. The official package includes some additional executables and DLLs compared to Roy's package. To at least some degree, this is evidently due to Roy's retrozilla.exe being statically linked with various libraries (~9 MiB in size) while the official 2.2 retrozilla.exe is dynamically linked (and is 156 KiB in size); note that Roy's package is missing most of the DLLs in the "components" folder. Static linking can carry less overall size overhead when the static libraries are only used by one executable, or when the linker omits parts of the libraries that aren't used by the program. Again, you'd have to ask Roy to be sure about the rest of the omissions. Some of them may have been unintentionally omitted, or they could simply be optional (but still may be worth having). I should clarify that when I suggested extracting Roy's package over an existing 2.2 installation, I did not mean replace the 2.2 installation. I meant extract it on top of the existing installation; any 2.2 files not included in Roy's package will still remain. I should also note that if one is concerned about messing up an existing RetroZilla installation, just make a backup copy of it (and perhaps your profile folder as well). I backed up my installation (and K-Meleon as well), but haven't yet had a need for the backup.
  3. Regarding NVIDIA ForceWare drivers for NT 4.0: 77.56 is the last "Quadro certified" release, but the last of the "regular" releases is 77.72. The problem with the control panel software is that it is just another example of shoddy software from a Microsoft-kool-aid-drinking developer that expects you to have crap like IE installed just to use your video drivers. I highly recommend *not* bloating an NT 4 installation with invasive Microsoft frameworks like IE to cater to such crapware. In this case it only really needs the following (the first two should preferably be added before installing the drivers): - SHLWAPI.DLL. I extracted and use the version from IE 3.01, as it is much smaller than versions from IE 4 and later. - The "Version" entry under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Internet Explorer should be set to an IE 5 or 6 (preferably 6) version number so that nView won't whine about the lack of IE. I use "6.0.9999.9999". - The nView Desktop Manager Setup Wizard didn't work until I installed the Visual C++ 6.0 runtime redistributable; probably it only needs the updated comctl32.dll provided by the included 50comupd.exe package, which can also be found separately. This part can be considered optional, as the Setup Wizard didn't seem to offer anything not configurable in the main settings pages. (Note: unless you are using a multi-monitor setup or need to temporarily enable them to use the LCD calibration screen, I would recommend keeping the nView Desktop Manager features disabled, as the hooks they install in running applications cause a considerable bump in memory usage.) With the above, the software seems to by and large work fine. I've tried versions 66.93, 71.84, and 77.72 and experimented with their multi-monitor support. On such setups, 77.72 has a bug where clicking the "Device Settings >>" button on the "nView Display Settings" property page caused the dialog to hang and max out the CPU instead of showing the menu. In 71.84 it works fine; as such, I would recommend 71.84 over 77.72 unless you have a specific need for something provided by 77.72. 71.84 and 77.72 do not show the Display Wizard after the first reboot following installation on a multi-monitor system; 66.93 does show the wizard but it does not work properly, with some settings not taking effect; the corresponding settings in the main property pages work fine. Perhaps I should have tried one or more of the "Quadro certified" releases, but they appeared to be target specifically at users of Quadro cards. Looking at NVIDIA's documentation, it seems they may have continued building NT 4 drivers after 77.72, but the functionality actually got worse (e.g. removal of PCI Express support). Note that while the NVIDIA Driver Helper Service (nvsvc32.exe) is not configured with "Allow service to interact with desktop" enabled, it actually circumvents this and maintains a hidden window on the desktop anyway - creating the same security problems (and triggering the same NT bug with the disappearing "Shutdown in Progress dialog) as any other interactive service that does this. Unless you require one of the specific features that depend on the service (it is supposedly involved with the hotkey feature, and I suspect application-specific profiles also), I recommend disabling it. I am currently satisfactorily using 71.84 with a GeForce 6800 PCI Express card. The OpenGL 3D screen savers included with NT look good with antialiasing enabled.
  4. I haven't tried the RetroZilla package on its own myself but would think it would run fine. The chief advantage I know of to just extracting it over an existing 2.2 installation is that, assuming you used the 2.2 EXE installer, you'd still have the desktop and Start Menu shortcuts provided by the installer. You'd have to ask Roy about the differences in which files are included versus the official 2.2 release. It doesn't appear that rn10950 has made any changes to the GitHub source repository since releasing 2.2, so any differences would more or less be Roy's fixes and updates. I extracted the package over the 2.2 installation on my NT 4.0 system and haven't regretted it.* My understanding is the K-Meleon package is just an updated version of the official 1.5.4 7z package with components taken from RetroZilla, hence why it includes k-meleonW9x.exe (for NT 4 and 9x) in addition to k-meleon.exe (the official EXE installer only installs one or the other---renamed to k-meleon.exe if needed---depending on your OS). K-Meleon is a Gecko-based browser that uses native Win32 widgets for the "chrome" (dialogs and, sadly, scroll bars still use XUL apparently). * For NT 4 I'd suggest checking out Roy's build of QtWeb 3.8.4 available here (this is a portable program; move it to a suitable installation folder, (optionally) rename it to QtWeb.exe, and launch it. Note: it requires SHLWAPI.DLL extracted from IE 3 or newer). This browser provides considerably better rendering abilities over the current RetroZilla, and the TLS 1.2 cipher support provided by OpenSSL 1.0.1e was still enough to get quite far on the web last I checked. I'm hoping to make and release my own build in the near future that builds upon Roy's patches with additional improvements, hopefully including updating OpenSSL to the latest 1.1.1 release to provide support for TLS 1.3 and the latest ciphers. Maybe I'll be able to update the QtWebKit engine to a slightly newer version as well. (Not sure if it could be easily ported to 9x; maybe with the UnicoWS library?)
  5. Regarding TLS in RetroZilla, note that Roytam1 released an unofficial build of RetroZilla with updated cipher support earlier this year: http://o.rths.ml/gpc/files1.rt/retrozilla-suite-tls12-20200131.7z You can extract the contents of this over an existing RetroZilla 2.2 installation to update it. This update appears to also make the about:config additions to manually enable certain ciphers unnecessary (those entries were no longer highlighted in bold after I installed the update). Roy also released a copy of K-Meleon 1.5.4 with the same updated cipher support; you can also extract this over an existing K-Meleon 1.5.4 installation (and replace k-meleon.exe with k-meleonW9x.exe): http://o.rths.ml/gpc/files1.rt/K-Meleon1.5.4en-US.tls12.7z
  6. Don't have a 2000 system handy at this time, but on Vista one disables the "Use personalized menus" setting under the classic Start Menu customization settings.
  7. If there aren't compatible official drivers available for your SATA/AHCI controller, or you would prefer a "generic" solution, check out UniATA.
×
×
  • Create New...