Welcome, Guest. Please login or register.

Author Topic: Ibrowse & jpegtmp?huh  (Read 4094 times)

Description:

0 Members and 1 Guest are viewing this topic.

Offline Damion

Re: Ibrowse & jpegtmp?huh
« on: May 21, 2003, 09:16:59 PM »
Yes, add an assign to your sys:s/user-startup,

assign jpegtmp: ram:t

Or where ever :)

 

Offline Damion

Re: Ibrowse & jpegtmp?huh
« Reply #1 on: May 21, 2003, 11:25:50 PM »
Like I said, assign it where ever. I put it
in RAM and have no problems, but other
people assign it to a physical disk. Some
programs (photogenics or PPaint if I recall)
assign JPEGTMP to RAM:T by default during
install, so it's definately an acceptable
practice. Perhaps if you have only a small
amount of fastram then a disk is better.

 

Offline Damion

Re: Ibrowse & jpegtmp?huh
« Reply #2 on: May 21, 2003, 11:43:18 PM »
:-)
 

Offline Damion

Re: Ibrowse & jpegtmp?huh
« Reply #3 on: May 24, 2003, 09:29:14 PM »
>then you might start having a problem if all
>your memory has been used for swap files

Except that this never happens. The memory is
only occupied  temporarily. After progressively
loading about 50 different jpegs with IBrowse,
the most I lost at one time was about 1.5MB
(and I suspect this was mostly memory needed
for display purposes). It's just a small area
of memory that is used (and reused) for decoding.

(edit) The memory - slider (for jpegtemp in
Ibrowse) only adjusts the amount of memory that
can be used within "jpegtemp" to decode. So
you could set it to a small amount if you only
had a small amount of fastram (slightly slower
decoding speeds) or higher/off with more
fastram (slightly faster decoding speeds).
The memory is returned after use, and in my
experience rarely is <2mb used at once.