[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [MiNT] Keyboard-problem with XaAES helmut-branch

To: <mint@lists.fishpool.fi>
Subject: Re: [MiNT] Keyboard-problem with XaAES helmut-branch
From: Peter Slegg <p.slegg@scubadivers.co.uk>
Date: Sat, 12 Jun 2010 11:23:40 +0200 (GMT)
In-reply-to: op.vd6mpzd5ofd6j1@descaro.mshome.net
List-help: <mailto:ecartis@lists.fishpool.fi?Subject=help>
List-id: <mint.lists.fishpool.fi>
List-owner: <mailto:tjhukkan@fishpool.fi>
List-post: <mailto:mint@lists.fishpool.fi>
List-subscribe: <mailto:mint-request@lists.fishpool.fi?Subject=subscribe>
List-unsubscribe: <mailto:mint-request@lists.fishpool.fi?Subject=unsubscribe>
References: <op.vd6mpzd5ofd6j1@descaro.mshome.net>
Reply-to: Peter Slegg <p.slegg@scubadivers.co.uk>
Sender: mint-bounce@lists.fishpool.fi

On Sat, 12 Jun 2010 12:14:13 , "Helmut Karlowski" <helmut.karlowski@ish.de> wrote:
> Am 12.06.2010, 11:01 Uhr, schrieb Peter Slegg <p.slegg@scubadivers.co.uk>:
>
> > Is there any way to see what is using RAM ?
>
> It's displayed in the xaaes-taskmanager (SZ).
>
What if the app is closed but the ram is still grabbed ?

Is there any util that gives a map of what is in RAM ?

Peter

Follow-Ups:
- Re: [MiNT] Keyboard-problem with XaAES helmut-branch
  - From: "Helmut Karlowski" <helmut.karlowski@ish.de>

References:
- Re: [MiNT] Keyboard-problem with XaAES helmut-branch
  - From: "Helmut Karlowski" <helmut.karlowski@ish.de>

Prev by Date: Re: [MiNT] Keyboard-problem with XaAES helmut-branch
Next by Date: Re: [MiNT] Keyboard-problem with XaAES helmut-branch
Previous by thread: Re: [MiNT] Keyboard-problem with XaAES helmut-branch
Next by thread: Re: [MiNT] Keyboard-problem with XaAES helmut-branch
Index(es):
- Date
- Thread