Home     |     .Net Programming    |     cSharp Home    |     Sql Server Home    |     Javascript / Client Side Development     |     Ajax Programming

Ruby on Rails Development     |     Perl Programming     |     C Programming Language     |     C++ Programming     |     IT Jobs

Python Programming Language     |     Laptop Suggestions?    |     TCL Scripting     |     Fortran Programming     |     Scheme Programming Language

Cervo Technologies
The Right Source to Outsource

MS Dynamics CRM 3.0

Fortran Programming Language

JPG image size

This Salford Fortran95 (3-4 years old version) program

    use clrwin
    integer*4 hinitsize, vinitsize, nb_colours, ier
    character*128 File

    call get_dib_size@(File, hinitsize, vinitsize, nb_colours, ier)
    print*,' FileToOpen, hinitsize,vinitsize,nb_colours=',File(1:40),&

works fine with JPG and BMP files of smaller size but crashes when I
try to load 4000x2500 pixel image from 10 megapixel camera. Do you
experience the same behavior?
Thanks in advance

On May 1, 10:29 am, rrr7@gmail.com wrote:

Have you asked in one of the Silverfrost discussion forums?

see http://forums.silverfrost.com/index.php

There is a forum devoted to ClearWin there.

-- elliot

On May 1, 11:10 am, e p chandler <e@juno.com> wrote:

I'm waiting for their confirmation. Problem with this furum site is
that instead of sending confirmation of creating account to ME they
arranged that ADMIN has to approve this :-[        ]

"Your account has been created. However, this forum requires account
activation by the administrator. An e-mail has been sent to them and
you will be informed when your account has been activated"

On May 1, 9:29 am, rrr7@gmail.com wrote:

Just a guess, but older versions may have been designed only to handle
8-bit images max.  GINO had that limitation back when 24/32-bit images
were fairly rare.
I presume that you are able to read the messages in the forums, but you are
not able to post. Go to the "support" forum on the silverfrost forums site,
and use the search facility. The thread you should look for can be found if
you do a search on "create_graphics_region@". There is a discussion there
about the maximum possible size of a graphics region that can be created.
It appears to vary from machine to machine, and differs with the amount of
RAM installed, and whether it is running Win2000 or XP. I don't think that
the issue was finally resolved, but the general consensus appears to be that
there is a setting in windows that affects this, and may be something to do
the memory management in Windows' virtual memory system (so presumably
it can be altered in the Registry).

The following code (original to be found on the forum) goes through
graphics sizes and will help you zoom in on the max size your system will
do without tweaking the registry (I don't know how) - after you have found
the limit using a step of 100 in the DO loop, change the start and end
and increment, and re-run.


! Graphics Test
INTEGER*4 :: I, i4PCXHandle, i4PCXWidth, i4PCXHeight, i4Err
DO I=1,10000,100
i4Err=CREATE_GRAPHICS_REGION@(i4PCXHandle,i4PCXWidth, i4PCXHeight) ! Setup
image area
WRITE (10,*)I, i4Err
CLOSE (10)

<gary.l.sc@lmco.com> wrote in message


Are the files coming off your camera jpegs?  I usually have to render an
image to make it .jpg

Furthermore, the files are *huge* and are going to trip your error clause
coming off the camera without rendering.

I got up to  5135  x   3851  (with a 4:3 aspect ratio) on a 1 Gb Win XP Pro
system before I couldn't allocate a DIB because the routine returned a fail


Add to del.icio.us | Digg this | Stumble it | Powered by Megasolutions Inc