jedi@clark-emh.arpa (05/07/88)
Hello everyone, it's me again. Ok, now that I have the compress/zoo/arc and other such programs... My problem now is the SH program. I have a version of the sh program, however, everytime that I use it, my amiga locks up and I either get the ol' GURU or the Software Error message. Is there a new version of this program that works, and if so, where can I find it?? Thanks in advance, I have had lots of success with other questions here, and feel sure that I will have the same luck this time (please) Thanks Mike Hampton Jedi@Clark-EMH.arpa
Chad_The-Walrus_Netzer@cup.portal.com (05/10/88)
In article <2422@louie.udel.EDU>, (Mike Hampton) writes: >Hello everyone, it's me again. Ok, now that I have the compress/zoo/arc >and other such programs... My problem now is the SH program. I have >a version of the sh program, however, everytime that I use it, my amiga >locks up and I either get the ol' GURU or the Software Error message. Try setting your stack to AT LEAST 12000 (more like 20000) before you use the sh/shar program... More if you still have trouble. This should stop your GURU's (This is a known problem with "sh". It's a stack monger.) You might want to also set your stack to a level higher than 4000 in your startup-sequence, as your needs justify. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Chad 'The_Walrus' Netzer -> AmigaManiac++ "Fat chance!!!" - William Tell's son
keithd@cadovax.UUCP (Keith Doyle) (05/13/88)
>In article <2422@louie.udel.EDU>, (Mike Hampton) writes: > Try setting your stack to AT LEAST 12000 (more like 20000) >before you use the sh/shar program... More if you still have trouble. >This should stop your GURU's (This is a known problem with "sh". It's a >stack monger.) What are these guys doing that takes up so much stack space? Seems to me you have to try pretty hard to create a program that hogs up so much. I've never had ANY problem with ANY program I've been working on with regards to stack. Why is everyone else having so much trouble? Are people passing entire RastPort structures on the stack instead of pointers, or what? Further, 1) what is the best way to determine how much stack you actually ARE using? and 2) why don't such programs set their stack explicitly if it's too small, I wouldn't think it's all that hard to do (haven't looked however). Keith Doyle # {ucbvax,decvax}!trwrb!cadovax!keithd Contel Business Systems 213-323-8170
keithd@cadovax.UUCP (Keith Doyle) (05/13/88)
>In article <2422@louie.udel.EDU>, (Mike Hampton) writes: > Try setting your stack to AT LEAST 12000 (more like 20000) >before you use the sh/shar program... More if you still have trouble. >This should stop your GURU's (This is a known problem with "sh". It's a >stack monger.) What are these guys doing that takes up so much stack space? Seems to me you have to try pretty hard to create a program that hogs up so much. I've never had ANY problem with ANY program I've been working on with regards to stack. Why is everyone else having so much trouble? Are people passing entire RastPort structures on the stack instead of pointers, or what? Further, 1) what is the best way to determine how much stack you actually ARE using? and 2) why don't such programs set their stack explicitly if it's too small, I wouldn't think it's all that hard to do (haven't looked however). Keith Doyle # {ucbvax,decvax}!trwrb!cadovax!keithd Contel Business Systems 213-323-8170
keithd@cadovax.UUCP (Keith Doyle) (05/13/88)
>In article <2422@louie.udel.EDU>, (Mike Hampton) writes: > Try setting your stack to AT LEAST 12000 (more like 20000) >before you use the sh/shar program... More if you still have trouble. >This should stop your GURU's (This is a known problem with "sh". It's a >stack monger.) What are these guys doing that takes up so much stack space? Seems to me you have to try pretty hard to create a program that hogs up so much. I've never had ANY problem with ANY program I've been working on with regards to stack. Why is everyone else having so much trouble? Are people passing entire RastPort structures on the stack instead of pointers, or what? Further, 1) what is the best way to determine how much stack you actually ARE using? and 2) why don't such programs set their stack explicitly if it's too small, I wouldn't think it's all that hard to do (haven't looked however). Keith Doyle
bakken@hrsw2.UUCP (David E. Bakken) (05/16/88)
In article <2092@cadovax.UUCP>, keithd@cadovax.UUCP (Keith Doyle) writes: > > What are these guys doing that takes up so much stack space? Seems to me > you have to try pretty hard to create a program that hogs up so much. > I've never had ANY problem with ANY program I've been working on with > regards to stack. Why is everyone else having so much trouble? > I'm working on a plotting program that prints postscript and to epson-like printers. It currently needs 100K-150K of stack space to not bomb with normal sets of points in the epson quadrouple density mode. That's not the graphics sort of stack hogging you were asking about but it is one example where a large stack is needed. -- Dave Bakken Boeing Commercial Airplanes (206) 277-2571 uw-beaver!apcisea!hrsw2!bakken Disclaimer: These are my own views, not those of my employers. Don't let them deter you from buying the 747 you've been saving hard for.