Scroll capture - Errors and Home button

[msirovy]

Hello,

the software has a great potential. However for scrolling capture, I have encountered following problems:

1) If the number of screenshot is over about 200, the following message appears when finished: "Not enough storage is available to process this command"
2) I have tried to divide the task into two (100 + 100) however the "Home" button is automatically pushed and it always starts at beginning. Would it be possible to disable the autopush of Home button or make it as an option?

3) The save as separate files function is great! Thank you. (the internal combining function does not work best for me, but this way I can use external tools intended for panorama stitching).

Best regards,

Martin.

[mouser]

Ok a couple of things:

1. When the scrolling window capture dialog comes up, on the left hand side you will actually see a maximum memory use option -- In today's modern pc, you should be able to make that number a lot bigger than the default -- that may solve your memory isses.
2. Starting out sending home button -- ok maybe I can add an option to disable that.
3. Thanks for saying you appreciate the feature -- I know most people don't know about it or have use for it so it's nice to hear that someone does.

[msirovy]

Ad1) The memory limit was set to 12 GB, so I suppose it is not memory problem (the allocated memory from task manager was about 1,5 GB)
Ad2) The option to disable the autopush of home button would be usefull.

Best regards and big thanks for your development and time spent.

Martin.

[Ath]

A 32 bit application, like Screenshot Captor, can allocate a max of about 1.5GB memory, so setting it to 12GB isn't probably gonna help much...
(unless, ofcourse, mouser added memory handling for > 2GB per process)

[ro0ter]

Hello mouser,

Any news on the disabling of sending a home key when starting a scrolling window capture?

Thank you,
ro0ter

[mouser]

Thanks for the reminder -- I'm going to release a new SC update soon and I'll try to add the option.

[jity2]

Dear Mouser,

I think I have a similar problem with the scrolling window capture (for some non downloadable Google Drive shared big pdf files.).
Maybe an idea : The "save each capture as a separate image" feature is great but could it be automatic without keeping all the capture images in RAM memory at once ? Like that no more RAM problem !
I.e. : Screenshot Captor saves each screenshot file on the hard drive just before scrolling to the next page.
Next I could split the saved images files at once for instance with XnView (See : Tools/Batch processing). And make a big pdf out of it.

Many thanks in advance

[mouser]

Can you try the new beta and the new option to not sent HOME key (see Misc options tab):

Download beta version (4.39.0 BETA) from here (or portable).

[206]

thanks mouser,

I had the same problem with the memory and even when I increased the memory on the screenshot program to 4 gig it was still giving me this error and my computer RAM is 16 gig and the program was using only one gig.

if i Change the range of IRPStackSize as explained here  https://thegeekpage.com/how-to-solve-not-enough-storage-available-to-process-this-command-error-on-windows-10/ should it fix the problem?

[basterma]

Hello,
Where is this option "save each capture as a separate image".  I can't find it.

Thank you

thanks mouser,

I had the same problem with the memory and even when I increased the memory on the screenshot program to 4 gig it was still giving me this error and my computer RAM is 16 gig and the program was using only one gig.

if i Change the range of IRPStackSize as explained here  https://thegeekpage.com/how-to-solve-not-enough-storage-available-to-process-this-command-error-on-windows-10/ should it fix the problem?