[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference hydra::amiga_v1

Title:AMIGA NOTES
Notice:Join us in the *NEW* conference - HYDRA::AMIGA_V2
Moderator:HYDRA::MOORE
Created:Sat Apr 26 1986
Last Modified:Wed Feb 05 1992
Last Successful Update:Fri Jun 06 1997
Number of topics:5378
Total number of notes:38326

2549.0. "Process monitor program for Amy???" by WAV12::HICKS (I could have had a DS3100!!!!) Tue May 09 1989 14:24

    Hi all:
    
    Does anyone know of the existence, name, location of a program to
    monitor and/or kill jobs or processes on the Amiga?
    
    This question is inspired by the process monitor found on the
    DECwindows "User Executive".  It gives you the ability to scroll
    through everything that's running, and kill jobs if need be.  Very
    handy, especially for something that's bombed without exiting.
    
    Is there an equivalent for Amy?
    
    <<< Tim >>>
T.RTitleUserPersonal
Name
DateLines
2549.1TALLIS::MCAFEESteve McAfeeTue May 09 1989 14:4719
    
    The problem is that Amy's OS doesn't keep track of all the system
    resources.  A task kill program is possible, but it won't necessarily
    be able to free up memory, etc.
    
    A well written Amiga program should be able to clean up after itself.
    If this is the case you can then use STATUS or TASKX (PD program) to
    find out the task number and BREAK to send a break to the task.  The
    program running in that task should then abort itself.  Many (read
    most) programs don't seem to support this even though it is quite
    easy.
    
    If this doesn't work I usually use TASKX or CHANGETASKPRI to lower the
    task's priority so that it doesn't run.  Eventually you have to reboot
    to get the resources back.
    
    sorry,
    
    steve
2549.2WJG::GUINEAUTue May 09 1989 15:0411
Look into XOPER (on WJG::AMIGA:XOPER.ARC).  It's about as close as you get.


One thing that really bugs me about the Amiga Exec is the way is allows
any name for a task. Under VMS, you have a process name (like Amy's task names)
except VMS doesn't let 2 processes have the same name (not in the same group 
anyway..)  It would be nice if the Amiga EXEC would assure that a unique task 
name gets assigned to each task.

John
2549.3Thanks, I'll give XOPER a shot...WAV12::HICKSI could have had a DS3100!!!!Wed May 10 1989 19:211
    
2549.4And there's TInfo...FRAMBO::BALZERThu May 11 1989 06:0411
    
    If XOper should turn out to large or you want to just take a quick
    look at what's going on, try Tinfo (Task-Info) from my fellow brewer
    and Vice-President, Heiko Rath. :-)
    It's somewhere on Tape::User1:<Amiga> (Zoo???) and gives you still
    more intimate information on a specific task. 
    But for constant monitoring, XOper is the way to go. Just don't
    trust it's CPU usage information too much...
    
    -	<CB>
    
2549.5Also SHOW on WJG::WJG::GUINEAUFri May 12 1989 09:1322
I wrote a small utility called SHOW  (I even use it all the time :-)

It will display just about every EXEC list (tasks, memory, ports, 
libraries, etc)

It's hidden inside WJG::AMIGA:FIND.ARC

which also includes a little hack called (what else) FIND which
will take a starting and ending address in Amys memory (defaults to the ROM)
and will attempt to match strings of printable ASCII characters. When it finds
one, it will display them until it hits an unprintable one. It will then
append a CR so the strings print neatly on your screen.

In ROM, it finds neat things like "Dale Luck - THE Amiga Wizard" and a bunch
of other interesting stuff...

Use SHOW to look at tasks (show -t), then find trackdisk.device in the list.
Get it's address in memory from the list and use FIND to dump a few Kbytes
starting at trackdisk's address. It says something about ATARI (I forget what)

John