Jump to content

WSC4

Member
  • Posts

    65
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    Australia

Posts posted by WSC4

  1. Sorry,  I used the wrong word "hang".   Yes, their circle pops up and then nothing happens.  You can get out of the site, go elsewhere or close the browser with no problems.

    I have tried New Moon 28, Mypal 68 and 360 Extreme Explorer.  All the latest versions.  Even tried the general.useragent.override trick and @AstroSkipper HTTPSProxy.exe with TLS 1.2 support with no luck.

    It does not matter, because I'm going to close down my account with them anyway.

  2. On 11/19/2023 at 9:18 PM, seven4ever said:

    Still have problem with 64 bit's Mypal 68 release on Xp 64 with  "Couldn't load XPCOM" message at start.

    000103.gif.04fd74a0d7ac32a00a85b64a729a3469.gif

    @seven4everYes.  I have the same problem running it on my XP 64-bit OS

    https://github.com/Feodor2/Mypal68/releases/download/68.13.7b/mypal-68.13.7.en-US.win64.zip

    This is noted at GitHub by @feodor2The release devote to x64, but on xp64 its likely fails to run, please look discussion about in issues.  For х64 nothing was changed, please look corresponding issue.

    I have look at the Issues page and cannot find anything about the XP 64-bit  XPCOM problems.  Where is it please?

    https://github.com/Feodor2/Mypal68/issues

  3. On 11/25/2023 at 10:53 AM, roytam1 said:

    NM28XP build:

    Win32 https://o.rthost.win/palemoon/palemoon-28.10.7a1.win32-git-20231125-d849524bd-uxp-b47d46219f-xpmod.7z
    Win32 IA32 https://o.rthost.win/palemoon/palemoon-28.10.7a1.win32-git-20231125-d849524bd-uxp-b47d46219f-xpmod-ia32.7z
    Win32 SSE https://o.rthost.win/palemoon/palemoon-28.10.7a1.win32-git-20231125-d849524bd-uxp-b47d46219f-xpmod-sse.7z
    Win64 https://o.rthost.win/palemoon/palemoon-28.10.7a1.win64-git-20231125-d849524bd-uxp-b47d46219f-xpmod.7z

    Official UXP changes picked since my last build:
    - Issue #2361 - Base implementation of Navigator.Clipboard (3478c01fc8)
    - Issue #2361 - Remove clipboard-read code (e0a7c35dcc)
    - Bug 1332825 - Use move semantics in MozPromise::All() and AllPromiseHolder. (543e41f3ac)
    - Issue #2361 - Enable Navigator.clipboard by default. (7fce3acfa9)
    - [WebGL] Turn on more validation/error checking in webgl (when not on Win) (acd204e85e)
    - [DOM] Check if rootDoc is secure context for web compat (71ce058b03)
    - [Network] Fix relative URL path starting with multiple slashes (d55111c4fd)
    - [DOM] Improve MessagePort state machine. (114daae894)
    - [WebGL] Flip the validation state for gl_KHR_no_validation. (56bcdf7ca0)

    No official Pale-Moon changes picked since my last build.

    No official Basilisk changes picked since my last build.

     Update Notice:
    - You may delete file named icudt*.dat inside program folder when updating from old releases.

    @roytam1  Thank you for the bug / issue fixes in New Moon 28.10.7a1 64-bit 25th Nov 2023.  I was using the 15th July 2023 build and could not log into my Australia Post account yesterday.  It was coming up with enable JavaScript messages and disable ad block (which was disabled) messages.  Tried a few user agent override tricks but they did not help.  Wasted all day on it and should have come here first.

  4. On 10/12/2023 at 8:26 AM, UCyborg said:

    Got Panda running on XP x64, you will need to install Application Verifier 4.0. And .NET Framework 4.0 too of course if you don't have it yet, the antivirus' management interface uses it. If you don't update the framework fully, might be a good idea to at least have KB2600211 as well to have some bugs of initial release fixed.

    Run Application Verifier (from Application Verifier folder in Programs folder).

    File->Add Application, you don't have to browse to any actual file, just type Stub.exe in the File name field and confirm. Repeat the process for Setup.exe.

    Edit both entries like so, you don't need Basics, so uncheck it, then check HighVersionLie under Compatibility. Right-click on HighVersionLie->Properties, here you need to put in Windows Vista's info (crazy, I know, it's also funny that MS's own online installer for .NET Framework 4.0 tries to download an update for Windows Vista when executed on XP x64). I was going off MS documentation really quick, so maybe some flag is missing in that Suite mask field, but it'll work for this, I only list fields I changed:

    Major version: 6
    Build number: 6003
    Service pack major: 2
    Suite mask: 512
    Product type: 1
    CSD version: Service Pack 2

    Save the changes, run the Panda installer (the official installer pulls the latest version from http://acs.pandasoftware.com/Panda/FREEAV/Promo_pd/FREEAV.exe (thanks @VistaLover), this was version 22.01.01 when this post was revised). First time around, before revising this post, the older 22.00.01 was tried from Major Geeks, there were some trouble with it and it refused to work properly next day.

    I only changed (checked) Offline installation option during setup.

    After installation is complete, delete entries from Application Verifier and save.

    spacer.png

    I'm afraid I have had no luck with this in trying to get Panda installed on XP 64-bit.

    As promised some weeks ago, I decided to try out all @UCyborg hard work that he put into getting this going.

    I started on a bare-bones install of XP 64-bit and installed .NET Framework 4.0.  Then installed all the 16 KB updates for .NET Framework 4.0 that are listed on Windows Update as well as KB2600211.  Rebooted.  Installed Application Verifier 4.0 and applied the instruction for stub.exe and setup.exe

    2023-11-2718_06_46-GreenShot.png.c62101b0ab122ed88b4c8d4546d88fe9.png

    Ran the Panda installer FREEAV.exe

    It still will not get past the Panda windows that states:  .NET Framework 4.0 is needed.  I have double checked and .NET Framework 4.0 Client is Version 4.0.30319  The same with .NET Framework 4.0 Extended.  All the KB updates for .NET 4 are all there and listed in Add Remove Programs.

    The only thing I can think of is the rest of the 200 Windows Updates are not installed yet.  I can not see the point in installing these as they have nothing to do with .NET.

  5. On 11/17/2023 at 1:27 AM, AstroSkipper said:

    This service works with the old ProxHTTPSProxyMII 1.3a. As you can see, the old proxy already supports the TLS 1.2 protocol. Therefore, it should work with MU/WU. But one thing is clear: ProxHTTPSProxyMII 1.3a is obsolete and won't work properly with many sites in these days.matrix.gif

    OK.  I have tried many workarounds at Windows Update using this version.  I have found more with the error code 0x800706B5..  A cut from the WindowsUpdate.log:

    2023-11-19    13:46:24:078    2112    850    Setup      * IsUpdateRequired = No
    2023-11-19    13:46:43:968    2112    850    COMAPI    -------------
    2023-11-19    13:46:43:968    2112    850    COMAPI    -- START --  COMAPI: Search [ClientId = WindowsUpdate]
    2023-11-19    13:46:43:968    2112    850    COMAPI    ---------
    2023-11-19    13:46:43:984     736    770    Service    WARNING: GetUserTokenFromSessionId failed with error 800706b5 for session 0
    2023-11-19    13:46:43:984    2112    850    COMAPI    WARNING: Unable to listen to self-update/shutdown event (hr=0X800706B5)
    2023-11-19    13:46:43:984    2112    850    COMAPI    WARNING: Unable to establish connection to the service. (hr=800706B5)
    2023-11-19    13:46:43:984    2112    850    COMAPI      - WARNING: Exit code = 0x800706B5

    GetUserTokenFromSessionId  It mentions Service before the warning.  Would that have anything to do with a setting in the registry service key?

    I have gone through your section General and specific solutions for problems regarding AU/WU/MU in Windows XP and Manually reset Windows Update components (KB971058).  Then also the Complete guide for restoring IE's access to WU/MU website using ProxHTTPSProxy or HTTPSProxy in Windows XP.  I have done this twice, and I have done all you steps down to 21 a number of times.

    22. If unfortunately none of all these 21 steps helped you, then you should presumably think about a complete reinstallation of Windows XP.

    I won't do that.  I'll try sfc /scanboot  Then do step 11 again.  If it fails again, I'll forget about it and move on.

  6. Thanks for your info on this, AstroSkipper.

    It is Microsoft Outlook 2007 which is bundled with Office Professional 2007.  Yes, it is old I guess, but I'm use to it.

    As a matter of fact, it does work with Gmail with either POP3 or IMAP set.  No problems to send and receive.  It uses SSL and TLS.  Unfortunately, I cannot get outlook.com (outlook.live.com) to work.  They say their setting are:

    IMAP server:  outlook.office365.com

    IMAP port:  993

    IMAP encryption:  TLS

    SMTP server name:  smtp-mail.outlook.com

    SMTP port:  587

    SMTP encryption:  STARTTLS

    I am now reading articles that beginning December 1, 2022, Microsoft will begin turning off the Transport Layer Security (TLS) 1.0 and 1.1 protocols for POP3 and IMAP4 and enforce the use of TLS 1.2.

    I would say that is the reason I cannot connect.  Especially with XP 64-bit and no POSReady updates. :-(

  7. On 11/11/2023 at 2:28 PM, DanR20 said:

    FWIW it looks like Microsoft did away with the previous usable Hotmail format so now the default string in 52.0 and 55.0 will take you to the bare minimum format similar to gmail's. Changing the string in about:config to Firefox's most recent will render their newer buggy version so that's the choice.   

    Yes, I have this problem in New Moon 28, 64-bit using outlook.live.com.

    I have in about:config general.useragent.override.outlook.live.com and still cannot get rid of their bare format.  What is your string value for this please? 

  8. Hello AstroSkipper,

    Thank you for your reply on this and for all your help.  Greatly appreciated.  I am still working on it and studying it and found his posts On decommissioning of update servers for 2000, XP, (and Vista?) as of July 2019.

    On a completely different note and off topic, I found some information on your first page about Area of application for ProxHTTPSProxy or HTTPSProxy.  You mention:

    Some e-mail clients like eM Client or Eudora are using IE engine too.

    I was just wondering if your proxies can be used for the Microsoft Outlook client in some way please?

  9. 000089.gif.87ff015f58dfcd04e48cd6ff0ded38b3.gif

    The old saying:  don't count your chickens...

    On 11/11/2023 at 9:18 PM, AstroSkipper said:

    As far as I can remember, @maile3241 had problems using IE 8 for accessing MU/WU and used IE 6 instead. He wrote about that in the past. Therefore, it could be a possible reason for the error.

    You are correct about this. There are 2 or 3 page about the discussion about this way back in March last year on page 103:

    He mentions:  "I got the error 0x80072F78 (with IE8) when checking for updates,  Under Win Xp x64, unfortunately you cannot access the WU website because you cannot install the necessary PosReady updates."  The 3 PosReady updates I could not install on XP 64-bit made it impossible to get IE 8 working.  Even KB942288-V4  was not enough.  All his screen shots are of IE 6.  I wish I had read those pages in more detail last week.

    I will uninstall IE 8 back to IE 6 and try again.  I wonder if IE7 would work also?

  10. Using XP 64-bit and Internet Explorer 8, and I have made some progress and have now arrived at this page:

    000094.thumb.gif.76661d84f67fca85ef4a5bcf2d5d54c0.gif000095.gif.817554dce59e0067dbcf6bc2d691db93.gif

    I am too scared to click Start Now.

    5. Before installing updates, apply "PosReady.reg" if not already done.  <==  I did this anyway, but because of the failed updates, it may have no effect.
    6. Install these four updates  KB4467770, KB4019276, KB4493435, KB942288-V3.  <== All these updates are x86 and will not install on XP 64-bit.  I did find KB942288-V4 which is x64 and installed OK.
    7. Apply "Tls 1.2.reg".  <==  I did run this for what it's worth.
    8. Execute "rootsupd.exe".  <==  applied this.
    9. Install the latest Windows Update Agent 7.6. It's version 7.6.7600.256.  <== This is maile3241's install.com and not the incorrect Microsoft Update Agent.

    Why is ProxHTTPSProxMII showing https://outlook.live.com and https://login.live.com in the window?

  11. 13 hours ago, ItCoder said:

    It does open, but pressing the the buttons has the same Error number: 0x800706B5

    11 hours ago, ItCoder said:

    Check if your patched wuaueng.dll is 1,xx MB or 2,xx MB. If it's 1,xx MB it's the 32bit version which won't work on 64bit systems. You can try putting it in SysWow64, but I don't know if it works.

    Yes, they are the correct size.  Just over 2 MB.

    13 hours ago, AstroSkipper said:

    As far as I can remember, @maile3241 had problems using IE 8 for accessing MU/WU and used IE 6 instead. He wrote about that in the past. Therefore, it could be a possible reason for the error.

    I am actually reading the January 2022 page.  I think the poster was using Windows 7 64-bit and IE 8.  I will go through those KB updates one-by-one and check for x64 versions and install those and the reg files and pray. :-)

     

  12. OK.  I have run maile3241's install.com this time again and checked the system32 and the dllcache.  Booted an external drive of an XP install I have and pasted those files  The wuaueng.dll files do not have a digital signature and are the correct versions from his install.  No luck.  Still getting the error.

    I did note that maile3241 was using Internet Explorer 6 back then.  I am using IE 8.  Could that be a possible reason for the error?

    Before I Install these four updates  KB4467770, KB4019276, KB4493435, KB942288-V3, I looked at them via the Microsoft Update Catalog.   POSReady 2009 (KB4467770) update Architecture: is X86.  I don't thing that is going to install on XP 64-bit.

    000093.gif.1aed04a28e0340d12908c893971feb58.gif

    I thought so.  I had to have a go anyway.

  13. I checked wuaueng.dll and it did not have the digital signature.  Also, wuaueng.dll was not in the dllcache directory.  I did not know about the WUForce option.  Running it Without it, the Update Agent said the agent was up to date and did nothing.

    I just ran it with the the force option and it installed OK this time.  wuaueng.dll now has the digital signature in system32 and the dllcache directory.  Rebooted the machine,  Launched the ProxHTTPSProxyMII v1.3a by maile3241 and then into Windows Update.

    Unfortunately, the Express or Custom button still went to error.

    I think those KB updates need to be installed.  I will go through your numbers 5 to 8 and see if that helps.

  14. Thank you AstroSkipper.

    Those "Could Not Find C:\WINDOWS\System32\Dllcache\wuaueng.dll"  errors could be a bug in the script if the agent was already installed.   I have looked at system32 and the 7.6.7600.256. Windows Update Agent,. wuaueng.dll, was updated mid 2021.  I cannot remember doing this manually.

    http://download.windowsupdate.com/windowsupdate/redist/standalone/7.6.7600.320/windowsupdateagent-7.6-x64.exe

    I will try again and with the above link being for 64-bit..

    Actually, It did go through your steps last week but only the Manually reset Windows Update components (KB971058).  I have not done these yet:

    5. Before installing updates, apply "PosReady.reg" if not already done.
    6. Install these four updates  KB4467770, KB4019276, KB4493435, KB942288-V3. Credits to @maile3241.
    7. Apply "Tls 1.2.reg". Credits to @maile3241.
    8. Execute "rootsupd.exe".
    9. Install the latest Windows Update Agent 7.6. It's version 7.6.7600.256.

  15. Thank for all your help on this.  I did run his Install.cmd again to update the Windows Update Agent.  I may not have noticed what it said the first time, but I have noted this:

    Installing KB2868626 to enable SHA-256 support
    Adding registry entries

    Updating Root Certificates

    Installing latest Windows Update Agent

    Replacing wuaueng.dll with patched file
    Could Not Find C:\WINDOWS\System32\Dllcache\wuaueng.dll
    A duplicate file name exists, or the file
    cannot be found.
    The process cannot access the file because it is being used by another process.

    I'll try install.cmd again in safe mode.  I did check for problems in the event log service with ProxHTTPSProxy running and no errors showed up.

  16. For the last week, I have been experiment with the first page on this.

    11.2.1. Downloads related to the TLS 1.2 proxies

    11.2.2. Downloads related to the TLS 1.3 proxies

    I got TLS 1.2 proxies working and was able to open Windows Update.  However, clicking the Express or Custom buttons would not load.  I then installed the TLS 1.3 proxies and PopMenu TLS 1.3 3V3 but these would not install at all.  I think it is an XP 64-bit problem.  I read through the page again and saw this:

    Due to support of SHA1 for signing certificates ProxHTTPSProxyMII 1.3a can be used in a Windows XP Professional x64 system to access MU successfully. More recent versions use SHA256 to sign certificates and fail while accessing MU. But that also means ProxHTTPSProxyMII 1.3a is not secure and should only be used if there is no other option.

    I am running XP Professional x64.  Does that mean I am stuck with only ProxHTTPSProxyMII 1.3a in the 11.1. Archived Downloads {obsolete} section?

  17. 14 hours ago, ItCoder said:

    You should click on Advanced on the last screen and put the IP address only into "Secure", leaving the other ones blank. The Proxy works only with HTTPS.

    Thank you and that worked.  I now get this:

    000090.gif.546bb850f7cf80580472ba1309953353.gif

    The ProxHTTPSProxyMII screen is now showing this and looks a lot better:

    000083.gif.fe19c10df87131af009ea32203222066.gif

    Launching Windows Update:

    000088.gif.5751f49a6aea9709face20f5191229e6.gif

    I thought I was 100% there and spoke too soon.  Unfortunately, when I click either the Express or Custom button, This happens:

    000089.gif.8375fe4ab40d1690b061854fbcd0f9ed.gif

    Any help on Error number 0x800706B5 please?

  18. On 3/5/2022 at 6:12 AM, maile3241 said:

    Windows Update for Xp x64 edition and W2k3

    I found a new opportunity. Cr to @whenever by Tuopf https://www.prxbx.com/forums/showthread.php?tid=2172. This version of ProxhttpsProxy creates a Sha1 certificate and is compatible with most Windows versions. With this version of ProxhttpsProxy, it is possible to update Windows Server 2003 (not tested) and Win Xp x64 edition. IE6 is sufficient.

    download link: https://www.mediafire.com/file/ftq6dnsccuq54p4/ProxHTTPSProxyMII_1.3a.zip/file

    WU-patch: http://www.mediafire.com/file/1ontv0vkh0ghfbi/Restore_WU_XP_2003.7z/file

    I have already edited the Config.ini so that you can work directly with ProxhttpsProxy. When opening ProxhttpsProxy a new certificate is generated. This certificate must be stored in the local computer's trusted certificate store.

    Make sure TLS 1.0 and Http 1.1 is enabled via proxy and the Windows Update patch is installed! It works without additional updates!

    It is also suitable if the CPU does not support SSE2.

    @AstroSkipper What do you say? Is it a good option?

    4DlZmCp.png

    I am running Windows XP 64-bit, and I have studied your post that you posted over a year ago.  I have downloaded the file and installed it and the WU Patch and have done everything that you said to do.  This is what I get when running Windows Update:

    000080.gif.e24f556149f42155038c2fe6e69211f3.gif

    000081.thumb.gif.80802458ba4a337ae8d91e2b3c0594c0.gif

    000082.gif.67e921601b5eb738b0b6cd2abfb04278.gif

    Are these setting correct?  Any help on this please?

  19. On 10/17/2023 at 4:54 AM, AstroSkipper said:

    You have actually asked the question to the wrong person. @UCyborg got it working on Windows XP 64-bit.  And if you had read this thread carefully, you would have noticed that a link was already provided by @WSC4 that explains and documents the Application Verifier programme in detail.  First read, then ask is actually the normal and correct way. jexplique.gif

    I think it was a bit unfair to chide and read the Riot Act to the poster on this.  It was not easy to see the link that I put in and you could easily glance over it.  I have edited my post in the previous page to make it more readable with a better link.

    Also, if you are running a monitor in high resolution, the font size on the forum pages is very small and hard to read.  I'm running 2560 x 1440.  Some weeks ago by accident, I looked at the top of the screen and saw this:

    Customiser.gif.d41d25d64d67a9a29b0ac55adbdbf076.gif

    The Customiser button:  Larger font size for posts?

    This is so much better, and I can now cancel my appointment with the optometrist. :-)

  20. 11 hours ago, AstroSkipper said:

    Update notification! update.gif

    Panda Free Antivirus has been updated and is now of version 22.01.01. Furthermore, I added the link to @UCyborg's post Got Panda running on XP x64 and @VistaLover's provided, alternative link for the offline installer to my article.
     

    Panda Free Antivirus is still compatible with Windows XP (SP3 32 bit editions only).

    Before I had a go of installing this a month ago, I should have looked at the Panda Security Support sites.

    https://www.pandasecurity.com/en/support/card?id=84021

    Minimum requirements of our Panda Dome products.

            Windows 11
            Windows 10 (32/64-bits)
            Windows 8/8.1 (32/64-bits)
            Windows 7 (32/64-bits)
            Windows Vista (32/64-bits)
            Windows XP 32-bits (SP3 or later)

    https://www.pandasecurity.com/homeusers/downloads/docs/product/help/pd/en/160.htm

    The minimum requirements that your computer must meet to install your Panda product are as follows:

    Windows 7 (32-bit and 64-bit), Windows Vista (32-bit and 64-bit), Windows XP (32-bit with SP3 or later), Windows 8 (32-bit and 64-bit), Windows 8.1 (32-bit and 64-bit), Windows 10 (32-bit and 64-bit), Windows 11 (64-bit).

    However, they do say they supported XP 64-bit for Panda for Desktops and Panda for File Servers.  When was this dated?

    https://www.pandasecurity.com/en/support/card?id=40061

    Windows 2000 Professional    Windows XP (32-bit Edition)
    Windows 2000 Server    Windows XP (64-bit Edition)
    Windows Server 2003    Windows Server 2008
    Windows Vista (32-bit Edition)    Windows 7 (32-bit Edition)
    Windows Vista (64-bit Edition)     Windows 7 (64-bit Edition)

    What are the minimum installation requirements for Panda Security for Desktops?

    https://www.pandasecurity.com/en/support/card?id=40027

    Operating Systems: Windows 8.1, Windows 8, Windows 7 (32 and 64-bit), Windows Vista (32 and 64-bit), Windows XP (32 and 64-bit) and Windows 2000 Professional SP4..

    And way back in 2009 they had this:  Try the Beta version of Panda Internet Security 2009

    Panda Internet Security 2009 is compatible with the following operating systems: Windows Vista (32-bit and 64-bit) and Windows XP (32-bit and 64-bit).

×
×
  • Create New...