CompuServe Messages

Dave: I'm still using Workbench 1.3, so this _may_ not be the same for WB 2.0x. In 1.3 there are two things that would cause what you describe to happen. One is that the program needs more "stack" space (i.e. a certain amount of memory set aside for it called a stack). Usually, this can be fixed by increasing the number in the "stack" requestor for the icon (select the icon, go to the Workbench menu and then select "info". _If_ you created a "tool" icon, there should be a requestor on the window which alows you to set a number for the stack. Try 20000.) The other problem in 1.3 is that some program just won't work with workbench. There is a way around, however, and that is iconx, a program in your "c" directory. To use iconx to run a program from the workbench that normally can only be run from the shell, you create a script that is identical to the command you would use to start the program from the shell. Then you create a "project" icon that has the same name as the script. Then, you select the icon, select the Workbench menu, select "info", and put c:iconx in the box called "default tool". Then, when you double click on the icon, it looks in the "c" directory, and runs iconx. Iconx opens a little shell, feeds it the script, and the shell sits around until you are finished using that program run by the script, and then shuts down. If this is not the same in AmigaDOS 2.0xx, others should jump in and correct me! – via Whap!