Unable to get data from the clipboard
aurgathor
Pro after Alt-Print Screen (a screen or window shot!)
if the image is over a certain size, I get:
Unable to get data from the clipboard.
OK
OS is W2K with all the recent patches.
a) what can be causing this?
b) how can I fix it?
TIA,
J.
David Bullock [MSFT]
Is that the exact text of the error? I wasn't able to map that error to a
specific resolution, in either Jasc's database or the MS Knowledge Base.
How much RAM in the system, and how large does the copied image have to be
to fail?
You may want to try clearing or deleting the pagefile, per the following KB
article:
http://support.microsoft.com/default.aspx?scid=KB;EN-US;255205
The pagefile (pagefile.sys) will be recreated when you boot back into
Windows 2000.
Also see:
"Out of Memory" Error Message Appears...
http://support.microsoft.com/default.aspx?scid=KB;EN-US;126962
--
David Bullock, MCSE, MCSA, A+
Windows NT/2000/2003 Setup Support
This posting is provided "AS IS" with no warranties and confers no rights.
Please reply to the newsgroup so that others may benefit.
"aurgathor" <spa...@if-you.com> wrote in message
news:a44b80d689fd35a0...@news.teranews.com...
aurgathor
"David Bullock [MSFT]" <dav...@online.microsoft.com> wrote in message
news:ulDv3wZn...@TK2MSFTNGP11.phx.gbl...
> Hi J,
> Is that the exact text of the error?
Yes.
> I wasn't able to map that error to a
> specific resolution, in either Jasc's database or the MS Knowledge Base.
>
> How much RAM in the system, and how large does the copied image have to be
> to fail?
The system contains 640 megabytes of RAM right now,
the pagefile has a minimum size of 512 meg, max is 2 gig.
Pagefile is not on the boot drive, it's on a dedicated HD.
Actual numbers from my a day or two old task manager
screenshot -- this is a normal load, BTW.
Physical Memory
Total 654888
Available 159304
System Cache 184020
Commit Charge:
Total 814380
Limit 1161804
Peak 869868
>and how large does the copied image have to be to fail?
It actually depends on how much memory is used -- if
my system has over 600 - 700 meg comitted, a 640x480
image is more than enough to cause a failure.
While writing this message I just tried to copy and paste
the complete display (1280 x 1024 x16bit) using "Print
Screen" then "Paste as a new image", and to much of my
surprise it did work just fine. Just had a 6 hours long power
outage and consequently, a very recent (1 hour ago) restart,
so I only had about 300 meg committed when I tried it.
This seem to indicate that the problem is not with PaintShop Pro.
I'll repeat the the test in a few hours when my RAM usage
will start to approach the usual level.
I can try to clear the pagefile next time I reboot; I never
get out of memory error message, so unless the clipboard
is in the desktop heap, that article shouldn't apply to me.
Thanks for your reply
J.
David Bullock [MSFT]
Still not finding any information in the MS database, but that seems less
surprising now. It definitely seems to be an error generated by PSP rather
than Windows.
Can you paste screenshots into other applications (MS Paint, Word)?
If so, a *workaround* would be to paste the screenshots into MS Paint, then
open the image in PSP. It would definitely also be a good idea to talk with
Jasc support, this issue may be a quick-fix preference change or something
like that.
And one more question: within PSP, are you opening a new / blank image
before attempting to paste in the screenshot?
--
David Bullock, MCSE, MCSA, A+
Windows NT/2000/2003 Setup Support
This posting is provided "AS IS" with no warranties and confers no rights.
Please reply to the newsgroup so that others may benefit.
"aurgathor" <spa...@if-you.com> wrote in message
news:01e7ddc5c6f28af1...@news.teranews.com...
> .
> >
> > I'll repeat the the test in a few hours when my RAM usage
> > will start to approach the usual level.
> >
>
> I just tried it now (450 meg commited ATM) and
> a full display copy and paste failed. It did work
> with the lot smaller error dialog, though.
>
> PS: I just realized I left the "the" out of my original
> post, so it wasn't exactly the exact message. ;-)
>
>
>