Amiga.org

Amiga computer related discussion => Amiga Software Issues and Discussion => Topic started by: duesi on February 06, 2003, 01:28:34 PM

Title: IBrowse again
Post by: duesi on February 06, 2003, 01:28:34 PM

When I open different Homepages
i get a requester that says

Insert JPEGTMP in any drive

Is an assign missing in user-startup or what ?

This error appears on an all new IBrowse2.3 installation...

Any help ?

Title: Re: IBrowse again
Post by: carls on February 06, 2003, 01:31:32 PM

A lot of programs dealing with JPEG images needs this AFAIK.
I keep a partition on my second hard drive where I have vmem, browser-caches etc. I also have JPEGTMP assigned to a directory on this drive.

Title: Re: IBrowse again
Post by: Paul_Gadd on February 06, 2003, 01:33:42 PM

Put in user-startup

Assign JPEGTMP: whereeveryouchoose:

I have it set as Assign JPEGTMP: T:

Title: Re: IBrowse again
Post by: Cluke on February 06, 2003, 01:34:17 PM

Actually in the case JPEGTMP: if you have any decent amount of memory at all (16MB>) then it is best just assign it to T:

Title: Re: IBrowse again
Post by: Nick on February 06, 2003, 01:40:58 PM

I have 128mb of RAM and still assign it to my Temp: partition. Why use memory when you don`t have to? I try to use my HD for a lot of things. I`m sick of running out of RAM. Most annoying!

Title: Re: IBrowse again
Post by: duesi on February 06, 2003, 01:43:42 PM

OK thanks works fine...

Title: Re: IBrowse again
Post by: blobrana on February 06, 2003, 02:36:36 PM

Have a search in the prefs...
(remember to double-click on the entries on left)
You will see that you can choose a path for  jpgtemp:

Choose RAM: if you have lots, or another HD/Partition , (it`s for caching images) makes it a bit more stable...

Title: Re: IBrowse again
Post by: Cluke on February 06, 2003, 03:52:58 PM

Quote

Choose RAM: if you have lots, or another HD/Partition , (it`s for caching images) makes it a bit more stable...

It's not for caching images, it's for temporary data storage during JPEG decoding. Hence it makes more sense to have in RAM as it is temporary in nature and much quicker as well!

Title: Re: IBrowse again
Post by: blobrana on February 06, 2003, 04:16:45 PM

tnx for pointing it out...(sloppy post on my part).

@Nick
Hear THAT, RAMS: a LOT faster :-D

Title: Re: IBrowse again
Post by: futaura on February 06, 2003, 04:30:57 PM

Seems to be some mis-information concerning this issue, so I'll set things straight ;-)

The JPEG decoder can be set to use a user defined amount of memory - if the decoder needs more, it is then that it uses the swap space.  So, the whole point of this is that JPEGTMP: should be assigned to a physical disk and not a ram disk.  If you want the decoder to use more ram (in particular, decoding progressive JPEGs requires much more ram than standard JPEGS), then there's usually an envvar to set that - I can't remember the name, but...

In the IBrowse image settings, you can change the swap space location (defaults to JPEGTMP:, IIRC). And if you prefer for IBrowse not to use the swap dir ever, then move the memory limit slider so that it shows "No limit".  Technically, this has the same effect as setting swap to ram:, but this is a much more efficient way to do it (will use less ram, and is faster, since the libjpeg backing store functions aren't used anymore).

Title: Re: IBrowse again
Post by: KennyR on February 06, 2003, 04:48:41 PM

And just to add a little bit to Futuara's info: if you set JPEGTMP: to RAM: then it'll probably fragment your memory. At least, it did here. So don't. ;-)

Title: Re: IBrowse again
Post by: Nick on February 06, 2003, 07:15:37 PM

Well I like to have an efficient system. Its maybe a tiny bit quicker in RAM, but I`m using my SCSI HD anyway, so its not that slow.