Author Topic: LATEST VERSION INFO THREAD - ScreenshotCaptor - v4.42.0 beta - July 21, 2022 (Read 1284133 times)

mouser · « **Reply #700 on:** April 05, 2018, 07:22 PM »

The screencast video link on the top-level post is a 404.

Thanks dj. The screencast videos got moved around when the new site was made, I still have to fix all the links to those. I've replaced the link on the first post with one to a youtube tour of SC for now.

hubi · « **Reply #701 on:** April 05, 2018, 07:37 PM »

Thanks for updates. Really noticed the better performance/more responsiveness.

Just wondering if you have any idea on how long on when you think you will have time to make the changes to the toolbar I requested i.e. add buttons for

Pixelate Inside selected region
Splice out strip by selection -Deluxe effects
Splice out strip by selection

Original request

Toolbar
-hubi (March 12, 2018, 07:05 PM)

djMot · « **Reply #702 on:** April 06, 2018, 03:01 PM »

I think you're confusing the thumbnail panel with the "clipart panel".

The thumbnail panel, which is (almost) always on screen and shows the content of your current screenshot directory, has no such right-click "browse here" entry, but only because there has always been an easy way to browse your current screenshot directory, from the main menu. From the main menu choose "GoTo-> " and then the 2nd item down is "Explore at current screenshot directory". Or to do it fast hit Alt+G and then E.

The new feature is for the Clipart Object functionality, which allows you to drop special clipart images on your screenshots and manipulate them as objects.
-mouser (April 05, 2018, 07:17 PM)

Ah. My bad. Noob user.

mouser · « **Reply #703 on:** April 06, 2018, 05:08 PM »

Ah. My bad. Noob user.

Not at all -- there are a lot of features to keep track of.. Don't be shy about posting questions or feature requests!

mouser · « **Reply #704 on:** December 02, 2018, 06:16 AM »

Minor update:
v4.31.1 - Dec 2, 2018

[Improvement] Print menus now show target printer name
[BugFix] Hotkeys with Alt in them could confuse the new preset-size capture mode functions.

KodeZwerg · « **Reply #705 on:** December 02, 2018, 06:43 AM »

Download latest stable version from Official Web Page: HERE.

LATEST VERSION:

v4.31.1 - Dec 2, 2018
-mouser (May 04, 2006, 01:22 AM)

I am confused, if i follow link, there is only 4.29.0 download offered or version number not updated on that link?

Screenshot Captor - DonationCoder_com – Opera - 02_12.jpg

LATEST VERSION INFO THREAD - ScreenshotCaptor - v4.42.0 beta - July 21, 2022

mouser · « **Reply #706 on:** December 02, 2018, 06:56 AM »

Thanks for the reminder, web page now updated.

cranioscopical · « **Reply #707 on:** December 02, 2018, 08:34 AM »

Thanks for the continual updates... much appreciated

IainB · « **Reply #708 on:** December 05, 2018, 05:13 PM »

@mouser: Feedback - I have been stumped by an error.
ScreenshotCaptor v4.31.1 NOT WORK (dl 2018-12-06)
I initially installed it via DCUpdater, but it failed to start.
I then tried installing it from .ZIP Portable, but to no avail.

Results are consistent and repeatable:
At SC startup, the SC Systray icon momentarily shows, but then it fails/abends with the error message:

---------------------------
Screenshot Captor
---------------------------
System Error. Code: 1722.

The RPC server is unavailable.
---------------------------
OK
---------------------------

Not sure what "The RPC server" is referring to. I can't identify a file/app of that description on the HDD and it doesn't seem to be an identifiable Service process.

I reverted to ScreenshotCaptor v4.29.0 Portable (dl 2018-04-13) - which works fine.
Then I reinstalled ScreenshotCaptor Portable v4.31.1 (dl 2018-12-06), but it still abends.
So I reverted to v4.29.0 again and shall continue using that until a fix/workaround is provided for the latest version.
OS is Win10-64 PRO.

KodeZwerg · « **Reply #709 on:** December 05, 2018, 05:19 PM »

I use the latest Setup.exe version and run on Windows 10 x64 latest build, the options i use (create a screenshot and save) are working like ever.

Could you try Setup.exe aswell to minimize error to portable package?

IainB · « **Reply #710 on:** December 05, 2018, 09:58 PM »

@KodeZwerg:

I use the latest Setup.exe version and run on Windows 10 x64 latest build, the options i use (create a screenshot and save) are working like ever.

Could you try Setup.exe aswell to minimize error to portable package?
-KodeZwerg (December 05, 2018, 05:19 PM)

This was addressed to me - right?

I indicated that I initially used the CHS setup (through DCUpdater).
I then tried Portable.zip
Same result - System Error. Code: 1722.
I then reverted to the earlier version and tried the whole thing (Setup and then Portable install) again.
Same result - System Error. Code: 1722.

So the causal problem would seem to be in the latest version. Specifically - by deduction - it would seem to be in one or more of the three (apparently only) updated files:

ScreenshotCaptor.chm 3551838 10/10/2018 4:06 PM 10/10/2018 4:06 PM
ScreenshotCaptor.dcupdate 1104 29/11/2018 4:07 PM 29/11/2018 4:07 PM
ScreenshotCaptor.exe 9465096 29/11/2018 4:07 PM 29/11/2018 4:07 PM

mouser · « **Reply #711 on:** December 05, 2018, 10:08 PM »

I'm having a hard time imagining why you would get that error with Screenshot Captor.. and you're saying reverting to prior version works? That is bizarre. Anyone else?
Are you using some kind of network mapped drive? Or maybe some antivirus program doing something weird..

IainB · « **Reply #712 on:** December 06, 2018, 01:56 AM »

@mouser:

I'm having a hard time imagining why you would get that error with Screenshot Captor.. and you're saying reverting to prior version works? That is bizarre. Anyone else?
Are you using some kind of network mapped drive? Or maybe some antivirus program doing something weird..
-mouser (December 05, 2018, 10:08 PM)

Thanks for responding.
I know what you mean. I sometimes have a hard time imagining that I will be able to get up in the mornings, but it usually all works out somehow.
There have been no recent changes to mapped drives or anything. The system remains relatively stable (or whatever passes for "stable" with Win10...).

My drives: (what I use most)

The HDD.
3 x Cloud Drives (accessed fairly frequently).
1 x Cloud Drive (accessed occasionally).
1 x 2GB dynamically changing RAMdrive (set as the TEMP variable).

The only slightly unusual thing I do with drives (have done for ages) is set hard links to cloud storage volumes/folders. I use these hard links as virtual folders, some of which are my main "working folders".
The hard links are very stable and never cause any problems. The drives I use are unlikely to be causing the problem, because - and as you have also observed - the earlier version of SC consistently works OK, whereas it is only the latest version of SC which consistently does not.

The only "odd" thing I have found with folders is the mysteriously-appearing "QL folter temp", which I referred to in a Launch Bar Commander - Latest Version thread. I wondered whether it might have something to do with the observed LBC long delays.

mouser · « **Reply #713 on:** December 06, 2018, 01:59 AM »

Can you try making two new directories for the new version portable, and old version portable. In both cases dont put a screenshotcaptor.ini file in there on the first run so they both start with default directories.
I didn't make any change to the program that I can imagine could be causing this problem, so I'm still guessing it has something to do with where it thinks its trying to store your data files or screenshot files.

Anyone else having this problem?

OH wait I can think of one change that COULD be responsible.. the code that gets the default printer name!!!!

I'm guessing your default printer is unavailable or a network printer of some sort, etc.

IainB, I've sent you a link to a beta version. Let me know how it works for you. If it still gives error I'll remove the code.

KodeZwerg · « **Reply #714 on:** December 06, 2018, 03:33 AM »

The "RPC server unavailable" error can occur for the following reasons:

DNS problems

Time synchronization problem

RPC service is not running

Network connectivity problem

Troubleshooting:
DNS problems - Check the DNS pointing on each DC.
http://support.micro...scid=kb;EN-US;825036

Time synchronization problem - PDC role owner in forest root domain should be a authorative time server.
http://support.microsoft.com/kb/816042

RPC service-
Ensure the RPC service is running.

Network connectivity-
Ensure that the important well-known ports required in a domain environment are open on the firewall between these DCs, use the Portqry tool.
http://blogs.technet...cation-scenario.aspx

Additional, Active Directory Replication Over Firewalls
http://social.techne...-over-firewalls.aspx

Ports requirement for AD.
http://technet.micro...dd772723(WS.10).aspx

Taken from MS TechNet

mouser · « **Reply #715 on:** December 06, 2018, 03:51 AM »

The problem was the new version asks Windows for the name of the current (default) printer. It seems that that function call can throw an exception, and I wasn't testing for that. That error was the exception, it probably happens if your current printer is a network printer that is offline, or something like that. Now I check for an exception being thrown and just don't use the new feature of displaying the current printer name in the menus.

I've uploaded a new version to fix the bug, hopefully it didn't hit too many folks.

smaragdus · « **Reply #716 on:** December 06, 2018, 01:01 PM »

@mouser
I could not find what is new in Screenshot Captor version 4.31.2.

mouser · « **Reply #717 on:** December 06, 2018, 01:20 PM »

It seems the previous release (4.31.1) could throw an exception in certain unusual circumstances regarding a disconnected remote printer.. The new version fixes that.

smaragdus · « **Reply #718 on:** December 06, 2018, 01:47 PM »

@mouser
Thanks for the express reply.

Kopejkin · « **Reply #719 on:** December 07, 2018, 07:56 AM »

Hi!

1) Please tidy up the data on the site!
Version 4.31.1 is listed, but version 4.31.2 is being loaded.

2) In the online help there is no data on changes in new versions.

3) For several years now, DirectX capture has not worked.

Maybe you need to hide or delete this command from the main menu of the program?
In addition, there is no this command in the context menu of the program icon in the tray.

regards!

mouser · « **Reply #720 on:** December 30, 2019, 05:43 PM »

Minor beta update, hoping to get back into the swing of more frequent updates:
v4.35.1 beta - Dec 30, 2019

[BugFix] Mobile phone or other photos with rotation information are now auto-rotated to correct orientation.
[Improvement] Updated compatible version of Mouser's Media Browser for image file management/browsing.
[MinorImprovement] Create new folder here function will now ensure the new folder is uniquely named.
[MinorImprovement] Minor tweaks to option descriptions.
[Improvement] Added preconfigured tools for The Gimp, and Corel Paint Shop Pro (will be auto populated in Tool menu if found installed)
[BugFix] The tool system (sctool) configuration files were not finding programs in the x64 C:\Program Files\ directory if the tool was configured as in %ProgramFiles%
[BugFix] Red box object capture could capture a larger area of the screen when capturing whole windows on Windows 10.
[BugFix] Code to fetch printer name could throw exception

hubi · « **Reply #721 on:** December 30, 2019, 08:13 PM »

Thanks for the update. However there is a small problem with this update, it does not work with XP. When you run it you get the an error 'Failed to start because DWMAPI.DLL was not found'.

If you are dropping support for XP that is fine. If not, then can you fix this. According to one post I read "... it is possible to have an application using dwmapi that will run on XP - you just need to disable the dwmapi parts using DelayLoading".

mouser · « **Reply #722 on:** December 30, 2019, 08:19 PM »

How strange.
I certainly do not intend to be dropping support for xp, and I'm trying to think what would I would have changed to cause that error..

Can you tell me what version you were using previously? I think that's very important for me to figure out to track down what change is causing that error.

mouser · « **Reply #723 on:** December 30, 2019, 08:21 PM »

If you run the latest official non-beta, do you not get that error?

To put it another way.. I'm trying to figure out if Screenshot Captor never worked with Win XP, or if it worked with it up until this latest version, etc. i.e. is this a new error or an old one?

hubi · « **Reply #724 on:** December 30, 2019, 08:30 PM »

No I don't. Reverted back to 4.31.2 and it works fine.