Skip to main content
Participant
November 13, 2018
Answered

Saving resized files

  • November 13, 2018
  • 1 reply
  • 652 views

Having resized my photo to a smaller size to save it a message comes up , could not complete save command because there is not enough memory. [RAM]  But my computer has loads of memory ???

Can anyone help as at present elements is not a lot of use to me if I cannot resize and save my photos.

    This topic has been closed for replies.
    Correct answer MichelBParis

    chrisg37942683  wrote

    Having resized my photo to a smaller size to save it a message comes up , could not complete save command because there is not enough memory. [RAM]  But my computer has loads of memory ???

    Can anyone help as at present elements is not a lot of use to me if I cannot resize and save my photos.

    This message looks like the one following the bug which was created by the Microsoft Windows 10 (1803) update on PSE 14,15 and 2018.

    Error: An integer between 50 and 8 is required | Elements | Windows 10

    What's your OS, OS and Elements version?

    1 reply

    MichelBParis
    MichelBParisCorrect answer
    Legend
    November 13, 2018

    chrisg37942683  wrote

    Having resized my photo to a smaller size to save it a message comes up , could not complete save command because there is not enough memory. [RAM]  But my computer has loads of memory ???

    Can anyone help as at present elements is not a lot of use to me if I cannot resize and save my photos.

    This message looks like the one following the bug which was created by the Microsoft Windows 10 (1803) update on PSE 14,15 and 2018.

    Error: An integer between 50 and 8 is required | Elements | Windows 10

    What's your OS, OS and Elements version?

    Participant
    November 14, 2018

    Not sure what you mean by OS, but elements version is 218

    Regards

    Chris

    MichelBParis
    Legend
    November 14, 2018

    OS is operating system: Mac or Windows.

    Elements version is probably PSE 2018.

    So, if you are on Windows 10, you are probably with the 1803 build which created the bug I referred to.

    If you are on a Mac, ignore my suggestion.