Jump to content

Problem viewing an image in a terminal server session...


Recommended Posts

Guest Brad Pears
Posted

We have a windows 2003 terminal server. One of our users called me this

morning and said she was sent a .jpg image by the another user and she

received an error when attempting to open the 1 mb image. The error she

received was "The image is too large". The application "Microsoft Photo

Editor" is what was being used to open the image when she double clicks on

it...

 

I then tried my own terminal server session andreceived the same error

message.

 

The configuration is set to 16 bit graphics for terminal server sessions. I

changed it to 24, logged off and back on again and received the same error.

In the past there have not been any issues opening .jpg images of this size.

 

Does anyone have any ideas as to what may be happening here at all?

 

Thanks, Brad

  • Replies 2
  • Created
  • Last Reply
Guest Dragos CAMARA
Posted

RE: Problem viewing an image in a terminal server session...

 

hi,

I have no info on MS PhotoEditor but I can tell you that some programs have

a limit on the dimensions of an image file.

If you check the PhotoEditor help files it may tell you the maximum image

dimensions - i think is 32MB .

http://support.microsoft.com/kb/190655

 

It may be worth a try to resize your image to a smaller size.

 

did you tryed to open on paint? maybe is corupted.

 

--

Dragos CAMARA

MCSA Windows 2003 server

 

 

"Brad Pears" wrote:

> We have a windows 2003 terminal server. One of our users called me this

> morning and said she was sent a .jpg image by the another user and she

> received an error when attempting to open the 1 mb image. The error she

> received was "The image is too large". The application "Microsoft Photo

> Editor" is what was being used to open the image when she double clicks on

> it...

>

> I then tried my own terminal server session andreceived the same error

> message.

>

> The configuration is set to 16 bit graphics for terminal server sessions. I

> changed it to 24, logged off and back on again and received the same error.

> In the past there have not been any issues opening .jpg images of this size.

>

> Does anyone have any ideas as to what may be happening here at all?

>

> Thanks, Brad

>

>

>

Guest Brad Pears
Posted

Re: Problem viewing an image in a terminal server session...

 

Thanks for that... I guess I was thinking that because the file was only

1mb on disk - that's roughly all it would take up in RAM but I am wrong. It

is quite conceivable that the 1mb disk file did break the 32mb RAM barrier -

hence the error...

 

Thanks again, Brad

 

"Dragos CAMARA" <dragos_c@remove-this.hotmail.com> wrote in message

news:B32B09D6-868B-4E81-B718-672E6B479E3E@microsoft.com...

> hi,

> I have no info on MS PhotoEditor but I can tell you that some programs

> have

> a limit on the dimensions of an image file.

> If you check the PhotoEditor help files it may tell you the maximum image

> dimensions - i think is 32MB .

> http://support.microsoft.com/kb/190655

>

> It may be worth a try to resize your image to a smaller size.

>

> did you tryed to open on paint? maybe is corupted.

>

> --

> Dragos CAMARA

> MCSA Windows 2003 server

>

>

> "Brad Pears" wrote:

>

>> We have a windows 2003 terminal server. One of our users called me this

>> morning and said she was sent a .jpg image by the another user and she

>> received an error when attempting to open the 1 mb image. The error she

>> received was "The image is too large". The application "Microsoft Photo

>> Editor" is what was being used to open the image when she double clicks

>> on

>> it...

>>

>> I then tried my own terminal server session andreceived the same error

>> message.

>>

>> The configuration is set to 16 bit graphics for terminal server sessions.

>> I

>> changed it to 24, logged off and back on again and received the same

>> error.

>> In the past there have not been any issues opening .jpg images of this

>> size.

>>

>> Does anyone have any ideas as to what may be happening here at all?

>>

>> Thanks, Brad

>>

>>

>>


×
×
  • Create New...