Leaderboard

Is something broken? Because just because there hadn't been a release in 7 weeks, it doesn't mean that the software is abandoned.

Why do you say that ??? @NotHereToPlayGames Good question! And I’ll go one step further. It’s always the same people who don’t really have anything meaningful to contribute, but when it comes to hurling insults, they’re always first in line.

Uh you know about, guess why the Centaury. But scatter no way, shall I spend the time solely on the mypal, nevertheless you ask free may be I to give a good tip, whatever, I see you must add new functions too.

@reboot12 Grok tells, that it is impossible to bring a modern Wlan card to life under XP SP3. But I am very near to exact this, the correct(!) firmware is already loaded and started in the 9560 Wlan card Dietmar 9560!WifiEnableBringupInterrupts: b57039a0 8bff mov edi,edi 9560v40: enable INTx bringup mask=80000001 === V51_ALIVE_WAIT === eax=8c965000 ebx=8ca73130 ecx=8052b704 edx=0000002b esi=8c965000 edi=00479000 eip=b5704ac0 esp=b7b6e6b8 ebp=b7b6e71c iopl=0 nv up ei ng nz ac pe nc cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00000296 9560!WifiWaitForInitialAlive: b5704ac0 8bff mov edi,edi # ChildEBP RetAddr Args to Child 00 b7b6e6b4 b5703582 8c965000 00000000 b7b6e924 9560!WifiWaitForInitialAlive (FPO: [Non-Fpo]) (CONV: stdcall) 01 b7b6e71c b5700d0c 8c965000 8052b704 b7b6e748 9560!WifiAttemptFirmwareBootstrapGen2V2+0x1632 (FPO: [Non-Fpo]) (CONV: stdcall) 02 b7b6e72c b5705959 8c965000 8c965000 00000000 9560!WifiAttemptFirmwareBootstrap+0x3c (FPO: [Non-Fpo]) (CONV: stdcall) 03 b7b6e748 b7bc3dea b7b6e784 b7b6e78c b7bbf200 9560!MiniportInitialize+0x2b9 (FPO: [Non-Fpo]) (CONV: stdcall) 04 b7b6e900 b7bc39cc 8cae4f20 b7b6e924 b7b6e9cc NDIS_b7bb9000!ndisMInitializeAdapter+0x3b7 (FPO: [Non-Fpo]) ;dv /t /v">05 b7b6e9d4 b7bc38ba 8cae4f20 00000000 8cc7b218 NDIS_b7bb9000!ndisInitializeAdapter+0xb9 (FPO: [Non-Fpo]) 06 b7b6ea08 b7bc4daf 8cc180e4 8ca73ae0 8cc18008 NDIS_b7bb9000!ndisPnPStartDevice+0xd6 (FPO: [Non-Fpo]) 07 b7b6ea38 804ef18f 8ca73030 8cc18008 b7b6eab4 NDIS_b7bb9000!ndisPnPDispatch+0x306 (FPO: [Non-Fpo]) 08 b7b6ea48 80592b63 b7b6eab4 8cf4ce50 00000000 nt!IopfCallDriver+0x31 (FPO: [0,0,0]) 09 b7b6ea74 80592be1 8ca73030 b7b6ea90 00000000 nt!IopSynchronousCall+0xb7 (FPO: [Non-Fpo]) 0a b7b6eab8 804f61ea 8cf4ce50 8caf1220 00000001 nt!IopStartDevice+0x4d (FPO: [Non-Fpo]) 0b b7b6ead4 8059229b 8cf4ce50 8caf1201 00000000 nt!PipProcessStartPhase1+0x4e (FPO: [Non-Fpo]) 0c b7b6ed2c 8059276e 8cf049e8 00000001 00000000 nt!PipProcessDevNodeTree+0x1db (FPO: [Non-Fpo]) 0d b7b6ed54 804f6996 00000003 8055b5c0 8056485c nt!PiProcessStartSystemDevices+0x3a (FPO: [Non-Fpo]) 0e b7b6ed7c 8053876d 00000000 00000000 8cf3e020 nt!PipDeviceActionWorker+0x170 (FPO: [Non-Fpo]) 0f b7b6edac 805cff64 00000000 00000000 00000000 nt!ExpWorkerThread+0xef (FPO: [Non-Fpo]) 10 b7b6eddc 805460de 8053867e 00000001 00000000 nt!PspSystemThreadStartup+0x34 (FPO: [Non-Fpo]) 11 00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16 9560v40: poll[alive-wait] ltr=88C888C8 bootstage=00000000 ipc=003B1000 sleep=00000000 rfid=00105110 alive=0 pnvm=0 notif=00/00 seq=0000 len=0 scan=0 cand=0 === V51_RX_SCAN ===

Upstream issue submitted: https://repo.palemoon.org/MoonchildProductions/UXP/issues/3001 It was caused by the second link you posted.

AFAIK there is a general problem to delay system and application services in Windows XP which means this feature isn't supported. In my case I never needed it. But I had a look into my installed version and you're absolutely right. No chance of delaying system and application services in Windows XP. But anyway, Glarysoft's Quick Startup in version 5.10.1.143 is great and does its job very well.

That's not the way. You have to compare by performing a binary comparison. Read my guide! Step 11.

And in which way did you check the correct version of wuaueng.dll?

Please upload your WindowsUpdate.log located in C:\Windows!

Alright, I see, proxy is deactivated. I thought it is activated.

Ok, actually it should look like mine:

As @RainyShadow said above these registry entries can only enable or disable ciphers which already exist in file schannel.dll. Here is a link: https://www.ssl.com/de/wie-man/Wählen-Sie-die-richtigen-Cipher-Suites-in-der-Schannel-DLL/ And replacing files is simple but in most cases it won't work at all. A lot of dll files have dependencies and need special registry entries too. Some people have already tried that. For example here:

Have a look into this thread: It's all about TLS, SSL, ProxHTTPSProxy and a lot of observations relating to schannel.dll where Ciphers are provided.

Well done! We have to do what we are able to. On my old test computer I have already edited the config.ini to my needs. You know I try to do things my way. But anyway, thanks for the hint! Very nice of you!

Thanks, but I will not provide download-links to Russian servers anymore. Sorry, it's very sad but we must make a mark, no matter how small it is! Besides, the changes are minor and can be done by users themselves according to their needs. Generally I try to provide download-links pointing to locations of original sources. But anyway, thanks for your offer! BTW, a modified and updated version of ProxHTTPSProxyMII 1.3a (20150527) for old computers which haven't got a CPU with SSE2 instruction set, will be soon released by me when test phase has been successfully completed.