avatar image

Welcome, Guest. Please login or register.
Did you miss your activation email?

Login with username, password and session length
  • Thursday May 19, 2022, 9:53 am
  • Proudly celebrating 15+ years online.
  • Donate now to become a lifetime supporting member of the site and get a non-expiring license key for all of our programs.
  • donate

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - TurboJosh [ switch to compact view ]

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

Simply download 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 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 :

cacert.pem (I think these 2 are the same file, simply renamed)

along with:


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.


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:

But that link takes you to some random domain squatter.

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:

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.

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.

I dont recall having a crash in ScreenshotCaptor before, but I did today.  v2.93. 

I was scrolling down through the list of ClipArt Objects (arrows and such), when it popped up an error dialog, I dont recall the contents, but it was something like an access violation.  I was able to hit OK and continue operating.  But scrolling any more would give the same error.  So I closed ScreenshotCaptor and reopened.  Then I did the same thing and scrolled the clipart down really fast to see if it would crash, and got a "List index out of bounds".

I was able to get a user.dmp from DrWatson (Windows XP) for the crash, and I ran an analysis I'll include at the end of this message.

Then I upgraded to 2.95 and I couldn't immediately reproduce the error.  But since I didnt see anything in the Version History regarding the ClipArt, I wanted to let you know of this malfunction.

Here's the WinDbg analysis:

00689a7a 8b7e08          mov     edi,dword ptr [esi+8]

EXCEPTION_RECORD:  ffffffff -- (.exr 0xffffffffffffffff)
ExceptionAddress: 00689a7a (ScreenshotCaptor+0x00289a7a)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 00000000
   Parameter[1]: 00000008
Attempt to read from address 00000008

PROCESS_NAME:  ScreenshotCaptor.exe

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".



READ_ADDRESS:  00000008

00689a7a 8b7e08          mov     edi,dword ptr [esi+8]





LAST_CONTROL_TRANSFER:  from 00689abc to 00689a7a

WARNING: Stack unwind information not available. Following frames may be wrong.
0013fc98 00689abc 03167e01 00688fc4 018f4af8 ScreenshotCaptor+0x289a7a
0013fc9c 03167e01 00688fc4 018f4af8 018f3401 ScreenshotCaptor+0x289abc
0013fca0 00688fc4 018f4af8 018f3401 005072db 0x3167e01
0013fca4 018f4af8 018f3401 005072db 004fad85 ScreenshotCaptor+0x288fc4
0013fca8 018f3401 005072db 004fad85 006dfdd2 0x18f4af8
0013fcac 005072db 004fad85 006dfdd2 00000000 0x18f3401
0013fcb0 004fad85 006dfdd2 00000000 01a03b80 ScreenshotCaptor+0x1072db
0013fcb4 006dfdd2 00000000 01a03b80 0000000b ScreenshotCaptor+0xfad85
0013fcb8 00000000 01a03b80 0000000b 0195dc00 ScreenshotCaptor+0x2dfdd2

STACK_COMMAND:  ~0s; .ecxr ; kb


SYMBOL_NAME:  ScreenshotCaptor+289a7a

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: ScreenshotCaptor

IMAGE_NAME:  ScreenshotCaptor.exe


FAILURE_BUCKET_ID:  NULL_CLASS_PTR_DEREFERENCE_c0000005_ScreenshotCaptor.exe!Unknown


WATSON_STAGEONE_URL:  http://watson.micros...89a7a.htm?Retriage=1

Followup: MachineOwner

In the left hand Screenshot Panel, by default it is Sorted "by Date - Newest at Bottom".

If I rename a file via the Name textbox at the bottom of the screen and then hit CTRL-S, it changes the timestamp of the file to the current time.  Is there a way to avoid this so the timestamp remains original?  When the timestamp changes to new, it puts the screenshot at the bottom of the Screenshot Panel, but for me I have a large number of screenshots and often the timestamp is what keeps related screenshots grouped together.  When I change a filename, now that 1 file is at the bottom, away from the rest of the group taken at the same time.

I guess I'm confused, under what circumstances does ScreenshotCaptor change a shot's timestamp, and when does it preserve the original timestamp?  I wonder if I would have just right-click Renamed the screenshot in the Screenshot Panel, if it would have preserved the timestamp (and therefor, it's original position in my list).

But because of the bug I mentioned in a seperate thread, I was afraid to rename via the Screenshot Panel because the .objects file doesn't get renamed with it.  Mouser had suggested to use the bottom File textbox for renaming, in order to preserve the .objects file, but now I have this timestamp issue.

Thanks for any clarification.

I keep ScreenshotCaptor opening all the time so it's ready anytime I want to snap the screen.

But I also often use ScreenshotCaptor for specific projects, and it's a pain to mix my project-specific screenshots into my "general screenshot dump directory".

Is there a way we could add a feature to Tray icon right click menu, that lets you point to the menu and the sub-menus are several Favorite Target Folders with a checkmark next to the current one?  And maybe an extra menu that says "Configure Favorite Targets" or something?

Renaming a file doesn't seem to maintain the .png.objects file which stores the markup objects (arrows, etc.).

Moving a file with objects using MoveTo Folders should also move the .png.objects file but doesn't seem to?

Is this expected or how can I take action to preserve my .png.objects data so my screenshots remain editable?

PS: Just donated $10 to the site to say thanks for ScreenshotCaptor!

Wow, I just found this recommendation to try "Everything 1.2" and it is UNBELIEVABLE!!  I would have killed to learn about this software 10 years sooner!  It's one of the best pieces of software I have ever seen.  So good, why doesn't Windows come with this built in?  Windows built in Indexing Service is a laughable useless farce compared to Everything!

"Everything" builds a full index within 1 second!  It relies upon the NTFS USN Journal so it only works on NTFS drives.

I tried Google Desktop but couldn't get it to build an index right away and found it's "" Http server program interface to be overly complicated and bloated.

Everything is just a dream come true.  EXTREMELY, BLISTERING fast, and outrageously small, lean and efficient.

Thank you VERY much to whoever recommended it.

Screenshot Captor / Re: Version number anomaly
« on: October 06, 2010, 12:31 PM »
EDIT: Nevermind - I see in latest version 2.84.01 the EXE Version information is correct. Thanks.

This fix may be implemented already and if so, this message can be ignored.

But if not, I wanted to agree with kzinnato.  I have always considered the EXE Version tab (FileVersion and ProductVersion) to be the authoritative way of determining the product version.  I strongly suspect Microsoft's official MSDN documentation would agree on this.

I have a disk catalogging program "WhereIsIt?" that relies on this version information (among other uses), and I would be shocked if a program's version did not match.

So, one more vote for the proper version #   :D

The new Auto Move Older screenshots feature is a nice one for sure.

But in my opinion it is inappropriate for it to be enabled by default.  I found this out by surprise after upgrading ScreenshotCaptor recently.  I guard my data very carefully and found this an unwarranted manipulation of my data without my approval.

I also have Picasa and some other photo programs that rely upon my images being in certain folders and structures, so for ScreenshotCaptor to suddenly take my screenshots hostage and move them to a new series of folders , presents a risk to my configuration.

I hope you will reconsider auto-enabling this option.  Or at least post a one-time dialog upon upgrade, to notify users of this change in folder management.

I Googled for a ScreenshotCaptor update today and was surprised to see that TechSmith is paying to advertise their commercial SnagIt product by purchasing the "ScreenshotCaptor" keyword.  Thought you guys might like to be aware of this:


Pages: [1]