Page 1 of 1

WinFrame / ACTION_CHANGE_SIGNAL

Posted: Thu Oct 30, 2025 2:57 pm
by gdridi
Hello!

I have a crash on my A1222FEupdate3 when using piped command like:

"run dir | dir" from a script file say co and

Protect co +s
Then
SystemTags("co", TAG_DONE); // my console

Here are The grim reaper images :

Image

Image

Image


What is WinFrame 2 Process ?

Is console.device.kmod really on error?

How to implement ACTION_CHANGE_SIGNAL ?


Regards
DGILLES

Re: WinFrame / ACTION_CHANGE_SIGNAL

Posted: Fri Oct 31, 2025 10:53 am
by colinw
So what else would you expect with an unterminated taglist pointing to
random stack memory. ?

Seriously !!

Re: WinFrame / ACTION_CHANGE_SIGNAL

Posted: Fri Oct 31, 2025 8:42 pm
by gdridi
I added TAG_DONE but it was in place in my code.

Sorry,
DGILLES

Post scriptum
My code is unstable with FEupdate2|3 , I think this is because of enhancer and run, dir commands from V54 installed in my A1222.
All is ok with my SAM440ep FEupdate0

Re: WinFrame / ACTION_CHANGE_SIGNAL

Posted: Sat Nov 08, 2025 6:29 pm
by gdridi
Hello,

It seems the bug is the same with :

viewtopic.php?t=4743&start=10

FEupdate0 is ok (from iso CD)
Console.device was it already replaced with a C version?

What is "WinFrame X Process" is it console or graphics ?

It seems to be parallel operatings in background like excerpts in samo post?
Or when run or pipe with AmigaDOS commands?


Regards,
DGILLES

Re: WinFrame / ACTION_CHANGE_SIGNAL

Posted: Tue Nov 18, 2025 7:59 pm
by gdridi
With FEa1222 no FEupdate3 and no EnhancerPack,
It didn’t bug (no Grim reaper).
Also,
I boot on VGAproductivity on A1222+