Simple CLI program to close all open windows?

[DEAT]

Hi EAB,

Is there a program that runs via CLI/AmigaDOS script that will simply close (or kill) all open programs and drawers in WB except the script it's running from? Preferably 68000/KS 1.3/512kb+512kb compatible. The only program I can find that has this functionality is DesktopToilet which I found at:

http://cd.textfiles.com/amigama/amigama199803/WWW/ctools/www.ctools.pp.se/DT/index.html


...but unfortunately it requires 8MB of fast RAM for some reason, and only runs on KS 2.0+.

I'm not looking for any commodities or GUI programs, and I'm not interested in using ARexx since I'm trying to keep my scripts KS 1.3 compatible.

[Minuous]

There is no system-legal way to do this prior to OS3.5.

[thomas]

Originally Posted by Minuous

There is no system-legal way to do this prior to OS3.5.

What has been added in 3.5 which makes it more legal? If you think of the Workbench ARexx port, with this you can only close Workbench drawers. You cannot kill running programs and close their windows.

[Minuous]

I was thinking of WB windows, missed the part about programs.

There's no way to close programs and deallocate all their resources safely on any version, as there is no record kept of what task owns what resource.

[meynaf]

Closing wb drawers isn't explicitly needed, just close wb itself.
For running apps, i guess you could just open a popup asking the user to close all of them.
But this brings the question : why wanting to do that.
If you just want to bring the system down, no need to close apps before.

[DEAT]

Originally Posted by Minuous

There is no system-legal way to do this prior to OS3.5.

That's unfortunate, thanks for helping!

Originally Posted by meynaf

But this brings the question : why wanting to do that.
If you just want to bring the system down, no need to close apps before.

It's mostly for freeing up RAM on low-end Amigas, as I've noticed that parent drawers still remain in RAM after they've been closed until the last child drawer has been closed. I've noticed a couple of games which can run from HD (despite not being intended to) don't bother checking for available RAM before throwing a guru, so I was hoping for a failsafe. Doing a check for available RAM and aborting the script is a fine alternative, it just means doing more trial and error on top of figuring out what can run on HD beyond what HOL has listed

[daxb]

Why not upgrade some more RAM then?

[bwldrbst]

Originally Posted by DEAT

That's unfortunate, thanks for helping!

It's mostly for freeing up RAM on low-end Amigas, as I've noticed that parent drawers still remain in RAM after they've been closed until the last child drawer has been closed. I've noticed a couple of games which can run from HD (despite not being intended to) don't bother checking for available RAM before throwing a guru, so I was hoping for a failsafe. Doing a check for available RAM and aborting the script is a fine alternative, it just means doing more trial and error on top of figuring out what can run on HD beyond what HOL has listed

On Aminet there is a package called CloseWorkBench that might suit your needs.

If not, and you're a programmer, there is an OS function to close WB, CloseWorkBench. It attempts to close the Workbench screen to free up memory however it probably won't work if you've got other windows open on that screen.