Ibrowse & jpegtmp?huh

[Gav]

Yeah when a jpeg is loading in ibrowse it asks for volume jpegtmp?what the hell is that?
It was fine before hand its just the past few days its went weird?
Thanks

[SSSMoves]

Have you tried assign the ...jpgtmp...

just look what it does!!!
It is reallly weard

[Damion]

Yes, add an assign to your sys:s/user-startup,

assign jpegtmp: ram:t

Or where ever

[carls]

You shouldn't assign JPEGTMP to RAM: because JPEGTMP is an assign that is used for "virtual memory" when decoding jpegs on AmigaOS. Assign it to a suitable partition your hard drive.

[Mad-Matt]

you should be able to specify where you want the jpeg temp files to go from within IB, Html, Images option i think.  By default jpegtmp: but can be set to ram:t

[carls]

No, you still shouldn't put it in RAM:

See this thread here at amiga.org

[Damion]

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.

[carls]

Are you not listening to me? :-)

It's totally useless to put it in your Ram Disk.
If you don't want to use swapping while decoding JPEGs, simply turn the memory limit off in IBrowse's settings.

Putting it in Ram: would be similar to using a Ram Disk as your swap partition in Linux. It might work, but what's the point? If you don't like the disk access, turn the swapping of instead :-)

There's a reason why they call it _virtual_ memory, y'know...

[Damion]

:-)

[SSSMoves]

I assign it to RAM if people like it or not it works fine

[futaura]

I assign it to RAM if people like it or not it works fine

It may work fine, but you can achieve the same by switching off the JPEG memory limit, in the IB prefs.  This will make JPEG decoding much more efficient - swapping to the ram disk will just slow things down.  Yes, it will work fine, until you get a disk full requester for the ram disk - then you might start having a problem if all your memory has been used for swap files :nervous:

[JetRacer]

carls: The jpgtemp is just a quick hack by a clueless individual so that the jpeg decoder would run on a vanilla A1200. It never takes the free mem into consideration and always use the jpgtemp for storage. That is highly improper when loading html pages with >20 small jpeg images in it. People who got the ram should assign it to ram:t.

Everybody:

Keeping the IB cache in ram: speeds things up considerably. Plus it's safer that way. IB2.X leaves cache files open on exit, locked threads which makes cache files "in use", etc. You don't want it to trash your HDD. Such defect cache files will cause a crash next time you use IB to surf the same site using cache content.

The IB cache is probably responsible for 90% of all crashes.

[Hooligan_DCS]

@Jetracer
Correct me if I am wrong, but arent cookies saved to ib_cache? Which means if I for example at www.ann.lu set some settings, they would be saved to ram and therefore not usable on next boot == need to set them every time you browse there.

[carls]

@JetRacer
If you're right, then I'm wrong, and I'm sorry... I guess I should go :rtfm: :-)

But why is there a "memory used"-slider in IBrowse if it's ignored?

[Damion]

>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.