Messages - TurboJosh [ switch to compact view ]

Pages: [1] 2 3next
1
DcUpdater / Re: DcUpdater fails to check for updates [SOLVED!]
« on: May 20, 2020, 03:35 AM »
I SOLVED IT!

SOLUTION:
Simply download http://downloads.dlang.org/other/libcurl-7.68.0-WinSSL-zlib-x86-x64.zip and extract the 32-bit libcurl.dll and replace the one in your DcUppdater.exe directory. Badda bing, badda boom! Success on the very first try.

You can stop reading here.



Notes for ScreenshotCaptor Developers:

I just spent 1 hour fiercely attempting to debug this issue. I'm not really a software developer but I know enough. I found it's the 2010 version of libcurl.dll that DcUppdater.exe (yes a typo, 2 P's) uses lacks modern SSL support.

After MUCH ProcMon.exe trial and error with a dozen various copies of libcurl that all failed due to various OpenSSL certificate library issues and dozens of DLL dependencies, I finally found a version that works!! And it's all in 1 single file! (the http://downloads.dlang.org/other/libcurl-7.68.0-WinSSL-zlib-x86-x64.zip linked above)

From what I can tell, this build of libcurl is specially compiled to use Windows SSL support rather than the default OpenSSL libraries and files etc, which is why it's so conveniently self contained all in 1 DLL. I'm using Windows 7 64-bit (but DcUppdater.exe is 32-bit).

However, if you need to support older OS like XP that may possibly (?) lack the current SSL support, then the solution will be to use a modern build of libcurl.dll with OpenSSL support instead, as that completely bypasses using any Windows SSL support (which is why Firefox can still connect to SSL websites on Windows XP but Chrome cannot. Firefox uses their own OpenSSL support while Chrome depends on Windows's SSL support.)

Unfortunately I tried very hard, and still was unsuccessful in getting the OpenSSL version to work. (I didn't find the much simpler Windows SSL version until the end.) ProcMon showed it trying to open C:\Program Files (x86)\Common Files\SSL which did not exist, so I created it, then I tried adding the :

curl-ca-bundle.crt
and/or
cacert.pem (I think these 2 are the same file, simply renamed)

along with:

libcrypto-1_1.dll
libcurl.dll
libcurl-4.dll
libeay32.dll
libssl-1_1.dll
ssleay32.dll
zlib1.dll

Which got DcUppdater.exe to run but still had various errors depending which versions I tried. I found a number of libraries from searching my hard drive, along with some libcurl binary distributions online. Ultimately it kept trying to open an openssl.cnf and I copied one of those but that didn't work either and I reached a dead end, unless the solution was to edit the openssl.cnf to match the location of the cacert.pem which I did not try.

Josh

2
UrlSnooper / Broken link on URLSnooper homepage
« on: January 22, 2016, 06:13 PM »
On the left hand yellow column, it talks about a general video streaming downloading discussion linking here: http://pub25.ezboard.com/bstreemeboxvcr

But that link takes you to some random domain squatter.

3
Bug: The word "Override" is misspelled as "Overide" in at least 2 places in the program. A code search & replace should solve that.

Usability: When I do a capture and the Post-Capture Dialog pops up, I often enter a filename in the "Overide filename" (sic) textbox, and then decide I want the screenshot saved somewhere besides my default screenshot folder, so I click Save Image As.. But then I'm frustrated because the filename I just painstakingly typed in is gone. Could the program be updated to persist the "Override" filename when clicking Save Image As?

Thanks again for this wonderful, FAST, efficient, 32-bit software! No .NET bloat here!  :Thmbsup:

4
I run ScreenshotCaptor always and typically have workstation uptime of 2-8 weeks on Windows XP 32 bit between reboots. Today I noticed my ScreenshotCaptor.exe USER Handles were up to 1114 and GDI at 764. This seems rather high, like there's a leak happening over time. I've probably taken 20 screenshots in the past 2 weeks.

Side note: I used open source "Process Hacker 2" (a high tech clone of Process Explorer) to view my Handle usage, which I have to monitor because I run out of desktop heap and other evidently limited resources, ultimately causing my desktop to crash. (I've increased my Desktop Heap to 12228 and that greatly helps but ultimately I still exhaust it because I typically open so many things simultaneously.)

Is there anything I can do to help track down and solve this handle leak? NirSoft has GDIView which if you leave running, shows counters of each app's GDI handle usage as it increases/decreases with time. But I'm not really an expert on what the different types mean.

5
Official Announcements / Re: January 2013 Giveaway Winners!
« on: January 21, 2013, 05:10 PM »
I'm so grateful!  I couldn't be happier about Hard Disk Sentinel Pro.  Thanks to everyone involved with organizing this.  Really a generous thing you're doing.

Pages: [1] 2 3next
Go to full version