Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation on 09/26/2018 in all areas

  1. That's what Bill Gates did and look what happened. Windows hasn't been the same.
    2 points
  2. Not 100% sure this is the correct place for this but it is a 'software' program I guess. For anyone using 'The Proxomitron' created by Scott R. Lemmon years ago ... Scott R. Lemmon - Wikipedia https://en.wikipedia.org/wiki/Scott_R._Lemmon Over at the 'The Un-Official Proxomitron Forum' there is a member by the name of Amy that has been working on Proxomitron for over a year looking for bugs and fixes ... the project has been named Proxomitron Reborn and she has released the latest update on Sep 04, 2018 ... http://prxbx.com/forums/showthread.php?tid=2331&page=6 ------------------------------------------------------------- Sep. 04, 2018, 02:45 AM (This post was last modified: Sep. 05, 2018 02:50 AM by amy.) amy RE: Proxomitron Reborn 4.5.2.0 has been released! This fixes a lot of latent bugs which Scott never got around to (and some, like the multithreading ones, which wouldn't have been visible nor easily reproducible on the single-core hardware of the time), so it can be considered the first improvement release of The Proxomitron since 2003! Quote:- Fix opening local file URLs - Fix buffer overflow in proxy test function - Stabilise and refine header filter ordering - URL: filters are now applied first, and also show first in the list. They are sorted respectively alphabetically. - Clarify file URLs for opening blocklists: URL commands must be enabled to do so, and if not, a warning message is shown. - Fix date checking for If-Modified-Since in local file requests. Original code would always respond with "not modified", possibly causing caching problems with local file replacements. - Fix Show URL in browser for https and add option to include scheme. When adding a URL to a blocklist, the menu option to open in browser was broken for https URLs. Now that has been fixed, and a checkbox added to allow you to include the scheme (https:// or http://) when adding to the list. - Fix unintentional sign-extension in base-64 encoding. Non-ASCII basswords and such should now encode and decode correctly. - Fix allow IP range comparison. This was accidentally introduced in the rebuild and not in 4.5j. - Fix duplicate load and image handle leak when loading textures - Fix tray icon tooltip (now it says Bypassed when... bypassed) - Fix memory leak in $STOP() - Fix memory leak in SSLeayShutdown() - Fix handling of FEXTRA and FHCRC for gzip format - Fix Allow for Session certificate dialog with multiple parallel connections. It will not continue asking the same host if you have multiple parallel connections and already said Allow for Session once. - Fix erroneous check of return value when setting OpenSSL certificate callback - Fix header filter count decrement race condition. No more erroneous "Filters In Use" with 0 active connections - Fix saving and restoring window sizes (for multiple-monitor users) - Fix multithreaded OpenSSL initialisation race condition crash - Fix positioning of context menus for multiple-monitor systems - Various cleanup/removal of dead-ends in code. Thanks for all the feature suggestions --- better SSL/TLS filtering support seems to be "most wanted" at the moment, but here's a list of things planned for 4.6: - Generate and cache appropriately-named certificates (like ProxHTTPSProxyMII, but integrated) - A way to better manage the Certificate Error exception list and make it persistent (how about in blockfile format? ) - Allow local.ptron and proxy itself to be accessed via HTTPS, although I'm not sure what browsers can make use of the latter - $REM() for comments in patterns (requested by mizzmona) The following 7 users say Thank You to amy for this post: soccerfan, mizzmona, prxymouse, zoltan, referrer, usr, Callahan ----------------------------------------------------------- I mention this for anyone interested in and still using Proxomitron. ...
    1 point
  3. @BTTB In any case, the POSReady updates were installed with the parameter -n (-nobackup), which means that they can not be uninstalled regularly. If updates are installed via AU / WU or MU this is not the rule. Furthermore, a big thank you to @Mathwiz, who drew your attention to the fact with KB4134651-v2. From me you have only the "remedy" to uninstall the original update KB4134651-v2, so you could install the modified KB4134651-v2 correctly. An info in the first post of this topic regarding KB4134651-v2 would be appropriate, as long as no adequate update is available. Hopefully the MS will finally wake up and bring the oleaut32.dll file back to a state where all Windows XP variants work correctly again.
    1 point
  4. Sorry it turned out to be more involved than I first thought, but at least it's all working now. Computers do seem to have a way of making simple things complicated....
    1 point
  5. Thanks. Whole problem lies in Microsoft Win8.1+ (and higher) bug (errr, they called it "feature by design"), that it does not report all CPU-supported features when Hyper-V is enabled (i.e. when Hyper-V is disabled, it reports "Skylake-based processors", but when Hyper-V is enabled, it reports "Core 2 Duo 8000 series"). I will try to develop some workaround but I must ensure that it does not influence backward-compatibility.
    1 point
  6. Hi dencorso, Thank you for your donation of $50.00. We look forward to improving the forums and stay online with your donation. Thanks MSFN
    1 point
  7. @BTTB I wrote to you via PM that you have to uninstall KB4134651-v2 and not KB4134651. The file version of KB4134651-v2 is higher than that of KB4134651, so it is sufficient to uninstall KB4134651-v2! If you can not uninstall KB4134651-v2, I can create a suitable uninstaller for you (ENU, DEU and FRA possible).
    1 point
  8. @Ruan: Does Sandboxie still work on Vista? Let us know if there's a version that won't work. If you are still avoiding the Meltdown and Spectre patches for Sandboxie's sake, that might have been the issue here.
    1 point
  9. Beta channel for Adobe Flash Player was updated September 20 to 31.0.0.118, and is confirmed working on Windows XP. https://labs.adobe.com/downloads/flashplayer.html Chrome 45 and newer PPAPI: https://fpdownload.macromedia.com/pub/labs/flashruntimes/flashplayer/install_flash_player_ppapi.exe Chrome 44 and older, and Mozilla Firefox (NPAPI): https://fpdownload.macromedia.com/pub/labs/flashruntimes/flashplayer/install_flash_player.exe Internet Explorer: https://fpdownload.macromedia.com/pub/labs/flashruntimes/flashplayer/install_flash_player_ax.exe Uninstaller: https://fpdownload.macromedia.com/pub/labs/flashruntimes/flashplayer/uninstall_flash_player.exe
    1 point
  10. Prudence is always good, but, provided there's one %windir%\system32\oleaut32.dll things will work OK. A second identical copy at %windir%\system32\dllcache\oleaut32.dll should be present, too, but just for the sake of backup, as you do know. And absence of %windir%\system32\oleaut32.dll will cause a lot of things not to work, but should not prevent booting and reaching desktop.
    1 point
  11. Cert_Updater updated to version 1.4 Various features implemented so that no obsolete sst files are installed. It is now possible to use additional download sources for existing download sources (up to 5), one another download source has already been added. Further information can be found in the file "Info Version 1.4.txt". to the updated version
    1 point
  12. Well, of course you can! ... sort of: boot Win 7 and search your XP partition for all copies of oleaut32.dll and delete 'em all! Then boot XP (it should still boot despite that missing file) and install heinoganda's modded update. This procedure works. What we don't know, however, is whether your current issue is due to oleaut32.dll, but if it is, then this procedure must solve it.
    1 point
  13. You must be joking. What if while you are away to the supermarket another member of the family actually pilfers something from the fridge? Your list would be out of date , and not only, you will also likely be accused (usually by the same member of the family that sacked the fridge) how you don't care about him/her and his/her needs/likings. Also, cannot really say if it can be configured this way, you could program it so that you can have an SMS or e-mail on your phone as soon as someone opens the fridge door (this usually happens between 2:00 and 3:00 in the morning[1], how can you deprive yourself of this nice feature?) jaclaz [1] Right after you will have finally managed to catch sleep again, after having being wakened by the message your "smart" outdoors camera sent you arounf 1:00 and that came out as being a false alarm [2] [2] to be exact false alarm #217 since you installed the IP enabled camera
    1 point
  14. I share your sentiments, particularly since I've seen a month or two where I got a problem-causing update and had to seperate it from the good ones. Annoying to be sure, but at least I could get rid of the trouble-maker. Getting back to KB4338380, I've made several comments over the past month which bear on it. Briefly it solves a memory related problem which isn't likely to apply to most of us, unless we have really intrusive neighbors with lots of knowledge about MS operating systems. My guess is whether it applies to your system is probably a function of how much RAM memory you're using -- I've got 16 GByte on an x64 system; you (and Chronius, also with an x86 system) probably have less on your system.
    1 point
  15. These updates are not yet ready for use by most users. They are not compatible with USP3, SE2ME, or UPXed files. Updating a previous KernelEx 4.5.x installation with just the new DLLs misses the registry and Core.ini changes that go with them. I am currently testing nine new files. (I am having no problems with .db files in any of many browsers.) Please do not create any more packages until I post these new files. This should be in the next few days. Then we can coordinate a full installation for limited (MSFN.org) release. I already have more API improvements for the following update. If I can also resolve the aforementioned compatibility issues, I'd like us to have a Release Candidate by the end of September and a Final for general distribution the first week of October. Until then, remember that currently this is not an open beta for just anyone to access and try. These update files are only for testing by registered members of MSFN.org who are interesting in helping me improve KernelEx. As previously discussed, no file attachments from this thread should be redistributed in any form on outside servers.
    1 point
  16. Well @roytam1tomorrow I pull the plug on Vista, so I wish you guys all the luck in the world with updated ports of New Moon and Serpent. You've done some good work. But I will be making the Quantum leap as of Sunday. Cheers! :)
    1 point
×
×
  • Create New...