Hi all!

I have serious troubles with 'secondary' application launching. Let me explain. I use DirWork as a manager and I launch lots of other programs from it, like cygnus editor to edit text files.
BUT!!! When I launch the DirWork by 'Execute Command' menu item, everything works just fine, but when I launch the DirWork from Ambient or from panel, it just doesn't launch anything.

Here I attach a part of working snoopdos.log:

Count Process Name Action Target Name Options Res.
----- ------------ ------ ----------- ------- ----
1 <Unknown> Execute Run >NIL: HD1:Others/CygnusEd/CEd Batch OK
2 [4] <Unknown> ChangeDir System:C
3 [4] Run Open NIL: Write OK
4 [4] Run RunCommand HD1:Others/CygnusEd/CEd 16384 0
5 [4] Run System 0
6 [5] Run Open NIL: Write OK
7 [5] Run ChangeDir System:C
8 [4] Run FindVar RC Local OK
9 [4] Run FindVar Result2 Local OK

And here goes a non working (ambient) part of the same:

Count Process Name Action Target Name Options Res.
----- ------------ ------ ----------- ------- ----
1 DW Execute Run >NIL: HD1:Others/CygnusEd/CEd Batch OK
2 [4] <Unknown> ChangeDir System:C
3 [4] Run Open NIL: Write OK
4 [4] Run RunCommand HD1:Others/CygnusEd/CEd -178330 Fail
5 [4] Run FindVar RC Local OK
6 [4] Run FindVar Result2 Local OK


Can anyone explain why does this happen? How to avoid it? Why is there the negative number option with the RunCommand? I guess this should be the stacksize... and so that's why it simply doesn't work with negative stack size...

Bye, MarK.

Voices in the air whispers.. "lose the DirWork... lose the DirWork.. use Magellan instead... ... ..Magellan..."

Are You trying to be funny? This isn't a DirWork problem. On my system it happens with every application. I'm not able to launch anything from anything unless I run it from shell or from Execute command. The same happend with DOpus also

I'm almost sure, that it's just some wrong settings in my system, but I don't know how to make it working.

btw: magellan sucks imo


[ Edited by MarK on 2004/9/14 7:25 ]

SnoopDos on another application, see what good old snoopy has to say about it.

You don't see it in my first post?

it seams, that the stacksize is set badly...
and I repeat, that this happens with every application launched from Ambient... The DirWork was used only as an example...

Bye, MarK.

ps: snoopdos isn't that old atleast not the MOS native version

[ Edited by MarK on 2004/9/14 7:48 ]

Quote:

No, not really

Quote:

Well you didn't mention the problem happens with anything else but DirWork, did you?

Have the same problems after booting from clean MOS install cd?

Quote:
Ouch, sure, sorry, as I said, this was just one of many examples...

Quote:
No, but... why, I cannot open the volume requester by a simple clicking on the Ambient, while I can, when I boot from CD?

Bye, MarK.

Your first post was missing some stuff that I expect to see in a snoopdos log

Take a look at your wbstartupdrawer. remove some stuff. see if it stops. look at the user-startup, see what's called. check your mui classes too.

What more did You expect? This was the only difference between the two logs...

I have just recalled, that I'm also unable to open the shell window by the NewShell menu item in the ambient... Probably the same cause... I will investigate a bit tonight... Thanks for now

Bye, MarK.

It looks like you are missing some libraries (even though this should most likely come up in snoopdos). Compare the libraries in your mossys:libs directory with the libraries on your Morphos-install cd -> do the same for the "classes" dir. It's possible that you (or an installer) replaced the morphos-native libs with amiga-os ones by accident.

Ouch, that's quite possible... I will check this out. But... it sounds a bit strange... Thanks anyway.

Bye, MarK.

Quote:

Corrupted icon.library? Have you checked the icon information. If you look to the icon information is there also a negative stacksize set?

Copy icon.library from cd to sys:mossys/libs I once had trouble with the iconlibrary, but that was in the MOS1.2 days (or was ist 1.1, anyway, long ago...)

Well, icon information works pretty well. The problem isn't here, but somewhere else. Launching the program from Ambient works well, but when the program launches another program from itself, it fails (probably) because of the negative stacksize (which is (probably) set correctly by the parental application) value... I will investigate tonight anyway.

Bye, MarK.

Looks weird. Options field display stacksize for RunCommand() and negative value is very wrong...

When I will get back to my Peg tonight, I will check it more carefully and send next post with results.

Does anyone here have similar problem? I guess no...

Bye, MarK.

Hi, Mark!

Maybe no library is missing, but an (68k?) one in Sys:libs
is disturbing an original one in MOSYS:libs....
You should check out if there's a lib with same name in
sys:libs AND MOSYS:libs.....
Just a guess....
Good luck!
frostwork

Mark,

Do you have RexxMast running? If so, are you sure you are using the correct Arexx libraries?

I have had the same problems that you describe when I ran RexxMast. It wasn't until I finally got the Arexx stuff straightened out that the problem went away.

--Aaron

Yes, RexxMast was the problem... Well, not the RexxMast itself, but the old rexxsyslib.library... But when I have no rexxmast running, or if I make it working with the morphos native library, no arexx can be used... (I use it with UAE_MOS)...

Can anyone here explain, why?

Then I hope this will be fixed with next MorphOS release

Bye, MarK.