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. 


  • Content Count

  • Donations

  • Joined

  • Last visited

Community Reputation

5 Neutral

About -SnooPY-

Profile Information

  • OS
    XP Pro x86
  • Country

Recent Profile Visitors

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

  1. I think the reason is that SysListView32 contains editable cell ( "Name"). There are many examples to change the background color of the cells for a simple ListView, but I could not find a working example to change the background color of the editable cells. I even want to write a small wrapper, but I still could not figure out what different ComCtl32.dll in Windows XP and Windows 7/8/10 (both have version 6.0). If someone here has the re-engineering skills and can help determine which functions are missing or otherwise implemented in XP, I would be very grateful for your help.
  2. I am sorry for possible offtopic, but somebody can explain how to use the Common Controls 6.0 and, respectively, Visual Styles in Windows XP? For example, in uTorrent 3.5.5 under XP standard ListView control is as follows: I suspect that there is a bug here. The active element should be sky blue, and the remaining elements of the alternate white / gray or white only, if this setting is disabled.
  3. I also can’t check any livestreams now. Perhaps, the results will be slightly different. So far we can only state that any "non-DASH" streams work fine in all cases. Thank you for your experiments, they were very useful. It became completely clear that the problem was most likely not in FFmpeg, not in OpenSSL, and not in mbedTLS. Good luck!
  4. You are absolutely right, this is clearly not mentioned anywhere. I want to emphasize what I think the problem is the lack of OpenSSL support. Of course, I could be wrong. Yesterday I tried to watch the live broadcast from Facebook: https://www.facebook.com/snookernews2u/videos/418828755653697 And got a 404 error. Today the situation is different. Now it’s not a live broadcast and stream coding "on the fly" through FFMpeg just doesn’t happen: [cli] [info] Found matching facebook plugin for URL https://www.facebook.com/snookernews2u/videos/418828755653697/ [plugin.facebook] [error] Skipped DASH manifest with SegmentBase streams [cli] [info] Available streams: sd (worst, best) [cli] [info] Opening stream: sd (http) Nevertheless, everything works fine, because FFMpeg is not used at all.
  5. Sorry to interfere, but what about the Streamlink project? It also does not work officially under XP, but I managed to build and run it. The problem is that FFMpeg with OpenSSL support is required for normal operation. I know that @Reino regularly builds FFMPeg for XP and even tried the FFMpeg buildscript that @Reino created. But unfortunately, all executable files are compiled by default without OpenSSL support and I don’t know how to enable this option when compiling from a script. Would you recommend something? Thanks a lot.
  6. I may be wrong, but it seems to me that everything is OK. Thanks a lot for the hint.
  7. Has anyone tested the SHCreateItemFromParsingName function? I have a suspicion that it is not implemented or is working with errors. I tried to analyze the sources on GitHub and found at least three different versions: https://github.com/Skulltrail192/One-Core-Api/blob/master/dll/wrappers/base/shell32_wrapper/shellitem.c - the function looks quite normal (line 566); https://github.com/Skulltrail192/One-Core-Api/blob/master/dll/wrappers/base/shell32_wrapper_new/shellitem.c - the function is commented out (line 566); https://github.com/Skulltrail192/One-Core-Api/blob/master/dll/wrappers/dependencies/shellnew/unimplemented.c - the function is "empty" (line 66). Is there a way to check which version was used for the final build of shell32.dll? Thanks a lot.
  8. Can anyone clarify the situation with [Export forward replacements]? Please advise what can be done to make this section disappear? Thanks a lot. I try to patch Revo Uninstaller and get the following log: ============================================================ [Patches needed] ... ntext.dll=Forwards KERNELXP.dll=Forwards ... RevoUninPro.exe=No problems found. [Export forward replacements] ntdll.ExpInterlockedPopEntrySListEnd= ntdll.ExpInterlockedPopEntrySListFault= ntdll.ExpInterlockedPopEntrySListResume= ntdll.NtAddDriverEntry= ntdll.NtApphelpCacheControl= ntdll.NtDeleteDriverEntry= ntdll.NtEnumerateDriverEntries= ntdll.NtGetTickCount= ntdll.NtModifyDriverEntry= ntdll.NtQueryDriverEntryOrder= ntdll.NtSetDriverEntryOrder= ntdll.NtUnloadKey2= ntdll.NtWaitForMultipleObjects32= ntdll.NtWow64CsrAllocateCaptureBuffer= ntdll.NtWow64CsrAllocateMessagePointer= ntdll.NtWow64CsrCaptureMessageBuffer= ntdll.NtWow64CsrCaptureMessageString= ntdll.NtWow64CsrClientCallServer= ntdll.NtWow64CsrClientConnectToServer= ntdll.NtWow64CsrFreeCaptureBuffer= ntdll.NtWow64CsrGetProcessId= ntdll.NtWow64CsrIdentifyAlertableThread= ntdll.NtWow64CsrNewThread= ntdll.NtWow64CsrSetPriorityClass= ntdll.NtWow64DebuggerCall= ntdll.NtWow64GetNativeSystemInformation= ntdll.NtWow64QueryInformationProcess64= ntdll.NtWow64QueryVirtualMemory64= ntdll.NtWow64ReadVirtualMemory64= ntdll.RtlAcquirePrivilege= ntdll.RtlAddVectoredContinueHandler= ntdll.RtlAllocateActivationContextStack= ntdll.RtlCopyMappedMemory= ntdll.RtlFormatMessageEx= ntdll.RtlFreeActivationContextStack= ntdll.RtlGetCriticalSectionRecursionCount= ntdll.RtlIsCriticalSectionLocked= ntdll.RtlMultipleAllocateHeap= ntdll.RtlMultipleFreeHeap= ntdll.RtlReleasePrivilege= ntdll.RtlRemoveVectoredContinueHandler= ntdll.RtlSetUnhandledExceptionFilter= ntdll.ZwAddDriverEntry= ntdll.ZwApphelpCacheControl= ntdll.ZwDeleteDriverEntry= ntdll.ZwEnumerateDriverEntries= ntdll.ZwGetCurrentProcessorNumber= ntdll.ZwLoadKeyEx= ntdll.ZwModifyDriverEntry= ntdll.ZwQueryDriverEntryOrder= ntdll.ZwQueryOpenSubKeysEx= ntdll.ZwSetDriverEntryOrder= ntdll.ZwUnloadKey2= ntdll.ZwWaitForMultipleObjects32= advapi32.AddMandatoryAce= ntext.RtlAddVectoredContinueHandler= kernel32.BaseCheckRunApp= kernel32.BasepCheckBadapp= kernel32.EnumSystemFirmwareTables= fileextd.GetFileInformationByHandleEx= kernel32.GetSystemFileCacheSize= kernel32.GetSystemFirmwareTable= kernel32.IsNLSDefinedString= shlwapi.PathIsValidCharA= shlwapi.PathIsValidCharW= advapi32.RegCopyTreeW= advapi32.RegDeleteKeyExA= advapi32.RegDeleteKeyExW= advapi32.RegDeleteTreeA= advapi32.RegDeleteTreeW= advapi32.RegGetValueA= advapi32.RegGetValueW= advapi32.RegLoadMUIStringA= advapi32.RegLoadMUIStringW= ntext.RtlRemoveVectoredContinueHandler= fileextd.SetFileInformationByHandle= ============================================================
  9. You probably mean these files, but I can’t download any of them. UPDATE 1: On the second attempt, I managed to find the full archive here. UPDATE 2: A more detailed analysis of the above files revealed that these are different versions. In particular, kernel32.dll is much larger, does not depend on ntext.dll and psapi.dll, and does not contain, for example, the GetUserDefaultLocaleName function. On the third attempt, I hope I found what I was looking for (and this is really part of the One-Core-API).
  10. I'm not sure what I am asking here correctly, but there is a project on our forum that uses a modified version of kernel32.dll from Windows XP (kernelxp.dll). Now I needed other DLLs (shellxp.dll, userxp.dll, ...), but unfortunately I did not find them in the One Core API. Tell me, please, where can I find them? I do not want to permanently install the entire package and replace system files with it. Please advise what can be done. Thank you very much!
  11. Yesterday I built a (working?) version of the _openssl.pyd extension for Python 3.7.1 using MinGW 4.9.2 (I will be very grateful for any feedback) : https://www13.zippyshare.com/v/olH5qzDq/file.html I was forced to use pre-built binaries, LIBS and INCLUDES from the official Python distribution and the previously mentioned project Curl for Windows by Viktor Szakats. Now you just need to install cryptography 2.6.1, and then replace the files libcrypto-1_1.dll and libssl-1_1.dll in the directory with Python.exe and the _openssl.cp37-win32.pyd file in Lib\site-packages\cryptography\hazmat\bindings Your version of Cryptography 2.6.1 and the version of OpenSSL 1.1.1b from @Mathwiz also work great for Python 3.4, but I don’t have the opportunity to use Win7+ and VS2015+ to build a version compatible with Python 3.7.1. Thank you all and good luck!
  12. You can also check OpenSSL 1.1.1b MinGW build from the Curl for Windows project. The only thing left is to build the latest Cryptography using these DLLs. Does anyone know how to build * .pyd files?
  13. Exactly! And the problem with Cryptography in Python is just a consequence of this "inaccuracy".
  14. I apologize for not being clear. Personally, I only have Win XP, but as far as I understood, @heinoganda successfully tested the latest Cryptography up to 2.6.1 under Win 7 with Python 3.4. In theory, in newer versions of Python (3.5, 3.6 and 3.7) there should also be no problems under Win 7. I just meant that. IMHO, we already have OpenSSL with XP support in the form of libcrypto-1_1.dll and libssl-1_1.dll files. Unfortunately, I still can not figure out how to build *. pyd files for Python. Cryptohraphy package is not well documented for this case.
  15. Cryptography performance does not depend on the version of Python. The only problem is that the new cryptography package (v2.5 - v2.6.1) includes incompatible pre-built binaries (_openssl-cp37-win32.pyd, etc ...), which for some reason is not possible to rebuild with XP support. Although @hotnuma already pointed to the source code: https://github.com/openssl/openssl/blob/master/crypto/rand/rand_win.c We are interested in lines from 20 to 40. It is enough not to link bcrypt.lib and the compatibility problem will disappear.
  • Create New...