topbanner_forum
  *

avatar image

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

Login with username, password and session length
  • August 17, 2019, 08:11 AM
  • Proudly celebrating 13 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 - sba [ switch to compact view ]

Pages: prev1 [2] 3next
26
Screenshot Captor / Re: Invalid Monitor Handle
« on: June 18, 2012, 01:32 PM »
if you need a tester for preliminary builds...

27
Screenshot Captor / Re: Invalid Monitor Handle
« on: June 18, 2012, 11:23 AM »
I hate to say, but the problem is still there with 3.06.01...

28
Screenshot Captor / Re: Invalid Monitor Handle
« on: May 23, 2012, 06:59 AM »
I hate to say, but just got the problem with 3.04.01

29
Screenshot Captor / Re: Invalid Monitor Handle
« on: April 11, 2012, 11:24 AM »
I hate to say, but just got the problem again with 3.03.01...

30
Screenshot Captor / Re: "Help on fields" formatting issue
« on: April 10, 2012, 07:58 AM »
BTW, where does one find the documentation for things like %windowtitlepure% or %windowtitle%?

31
Screenshot Captor / "Help on fields" formatting issue
« on: April 10, 2012, 04:19 AM »
Hi,

Just had to reconfigure the ScreenShot Captor preferences for the filenames, and hit the "Help on fields" button.

The formatting is rather poor:
- the field code and description are not separated from each other
- the descriptions should be "tab-aligned" (if you see what I mean)

More an annoyance than anything else, but improving this would "add polish" to the product  :P

32
I sometimes do yell at my monitor, too  :P

33
You're welcome.

And sorry if you get the feeling I got you frustrated. Bugs are a fact of life, we're just humans  :P


Have a good sleep!

34
I've intentionally restored the virtualstore stuff (incl. the DcUpdater file for DcUpdater claiming it's 1.28.1), installed your new build, and it does ignore the virtualstore information.

35
Note that in order to get your system back to normal letting DcUpdater update itself to 1.30.01 is not enough. You must delete the following two directories:

C:\Users\<user>\AppData\Local\VirtualStore\Program Files (x86)\ScreenshotCaptor
C:\Users\<user>\AppData\Local\VirtualStore\Program Files (x86)\DcUpdater

(removing ' (x86)' if you're not running 64-bit Windows).

Otherwise, DcUpdater will keep believing 1.28.01 is installed and will reinstall 1.30.01 forever.


HTH

36
U're welcome.

Indeed I'd experienced this kind of problem for quite some time, but hadn't bitten the bullet 'til today.

I'm assuming a public update to DcUpdater (that it will detect ;-) ) will be online soon.

37
The plot thickens.

Here's what I have just done (running as a non-admin user):

- shut down ScreenShotCaptor
- destroy both C:\Users\sba\AppData\Local\VirtualStore\Program Files (x86)\ScreenshotCaptor and
C:\Users\sba\AppData\Local\VirtualStore\Program Files (x86)\DcUpdater directories
- launch ScreenShotCaptor -- nothing happens in the virtualstore
- perform an update check using ScreenShotCaptor's context menu: this launches DcUpdater which recreates both directories with the following contents:


DcUpdater/:
Installables        dcupdater.dcupdate

DcUpdater/Installables:
ClipboardHelpAndSpell.dcupdate  ProcessTamer.dcupdate
FindAndRunRobot.dcupdate        ScreenshotCaptor.dcupdate
FlipbookPrinter.dcupdate        TheFormLetterMachine.dcupdate
LaunchBarCommander.dcupdate     URLSnooper.dcupdate
PointMotivator.dcupdate         UnicodeImageMaker.dcupdate

ScreenshotCaptor/:
ScreenshotCaptor.dcupdate

Could be that DcUpdater attempts to update part of this in the non-virtualized directory (or just opens files in read-write mode even if it just wants to read?), this fails, causing the virtualization to do its magic?

38
The problem is that there was another file at:

C:\Users\sba\AppData\Local\VirtualStore\Program Files (x86)\ScreenshotCaptor\ScreenshotCaptor.dcupdate

that contained 2.103.01

This file was probably created by either:
- installing ScreenShotCaptor without using "run as administrator"
- running ScreenShotCaptor as a non-admin user just after installation

In either case, the file virtualization mechanism (introduced in Vista) has kicked in and redirected the attempt to write to C:\Program Files (x86)\ScreenshotCaptor (which a non-admin user is not allowed to do).


After I have deleted C:\Users\sba\AppData\Local\VirtualStore\Program Files (x86)\ScreenshotCaptor and relaunched ScreenShotCaptor, DcUpdater reports the correct version, BUT the file C:\Users\sba\AppData\Local\VirtualStore\Program Files (x86)\ScreenshotCaptor\ScreenshotCaptor.dcupdate has been recreated.

Unfortunately I fear that at the next update ScreenShotCaptor might update C:\Users\sba\AppData\Local\VirtualStore\Program Files (x86)\ScreenshotCaptor\ScreenshotCaptor.dcupdate, leaving C:\Program Files (x86)\ScreenshotCaptor\ScreenshotCaptor.dcupdate unchanged, causing another version discrepancy.

Another explanation would be that running ScreenShotCaptor as an admin user will populate C:\Program Files (x86)\ScreenshotCaptor\ScreenshotCaptor.dcupdate, whereas running an update check from within ScreenShotCaptor running as non-admin user will cause DcUpdater to look at C:\Users\sba\AppData\Local\VirtualStore\Program Files (x86)\ScreenshotCaptor\ScreenshotCaptor.dcupdate.

Get the picture?

IMVHO running an app should not populate a per-user file containing version information. Instead, the app's installer should populate a system-wide file containing version information. But I'm just wearing my software developer hat on here ;-)

P.S. Without Process Monitor I would not have been able to troubleshoot this.

39
DcUpdater / DcUpdater reports incorrect version of installed app
« on: April 03, 2012, 10:04 AM »
Hi,

I have ScreenShotCaptor 3.03.01 installed (that's what its About box says) still DcUpdater reports I have 2.103.01 installed... and thus wants to upgrade.

What's up, doc?


40
Screenshot Captor / Re: Invalid Monitor Handle
« on: April 02, 2012, 10:19 AM »
great! just drop a note here to notify me where there's something I can give a shot  :P

41
Screenshot Captor / Re: Invalid Monitor Handle
« on: April 02, 2012, 02:35 AM »
Indeed, I'm not able to repro the problem with just PrtSc

42
Screenshot Captor / Re: Invalid Monitor Handle
« on: March 29, 2012, 10:42 AM »
Repro'ed it on my first attempt (dunno if all steps are mandatory):

- took a screenshot of an app on the 1st monitor (actually discarded it in the "what's next" dialog)
- took a screenshot of an app on the 2nd monitor (actually discarded it in the "what's next" dialog)
- connected to the machine using Remote Desktop from another PC that has only one monitor
- closed the Remote Desktop session  (not a logoff!)
- reconnected to the dual-monitor PC's console
- hit Alt+PrtSc
- got the error message ==> had to close ScreenShot Captor


43
Screenshot Captor / Re: Invalid Monitor Handle
« on: March 29, 2012, 05:04 AM »
I get the exact same problem, might be related to using Remote Desktop on a single-monitor machine to access my dual-monitor machine...

44
Yep.

45
Hi,

While I can understand where this technically comes from, it is rather user-unfriendly to have region screenshots made with Shift+PrtSc tagged with an application name of "Program Manager", resulting in filenames such as "Screenshot of 'Program Manager'  on 20091204105334"

I would suggest to change that "Program Manager" to something else, such as "(screen region)"...

What do you think?

46
Seems problem is fixed in 2.57.01

Now I get a filename of:

d:\private_sba\net\Captures\http___www.donationcoder.com_Forums_bb_index.php_topic=16214.0_Screenshot Captor 2.44.01 hangs when capturing IE window - DonationCoder.com - Windows Internet Explorer - 20090708110844.png

(ONE line)

Great job!

47
I'll hold my breath  :-[

48
My first tests on 2.56.01 pass succesfully  8)

49
Problem is half-fixed.

SSC doesn't hang anymore, it's just unable to generate a valid filename.

For instance, if I capture the very IE8 window I'm typing into, I get:

---------------------------
SCREENSHOT CAPTOR - ERROR SAVING FILE
---------------------------
Error saving file 'd:\private_sba\net\Captures\http___www.donationcoder.com_Forums_bb_index.php_topic=16214.0
Screenshot Captor 2.44.01 hangs when capturing IE window - DonationCoder.com - Windows Internet Explorer 20090610154818.png'.



 Filename or path may be too long or on missing drive letter, etc.



 Change filename below or use File->Save As menu to specify filename, or File->Discard File to skip saving this file.
---------------------------
OK   
---------------------------

It seems SSC generates the following filename:

d:\private_sba\net\Captures\http___www.donationcoder.com_Forums_bb_index.php_topic=16214.0^M
Screenshot Captor 2.44.01 hangs when capturing IE window - DonationCoder.com - Windows Internet Explorer 20090610154818.png

IOW the filename contains an embedded newline.

My configuration specifies

%windowtitle% %customdate%

as the filename template.

This might be related to %windowtitle% expanding to <URL><newline><page title>...


50
Need I say more?

It used to work, so seems like a regression induced by the latest upgrade...

I'm running 2.53.01.

Pages: prev1 [2] 3next