SysMon 1.20 per AmigaOS4

[Amiga Supremo]

Come dicevo,
ho aspettato AmiUpdate e come per magia, TUTTO risolto (meno il bug al lancio di SysMon durante l'emissione della musichetta d'avvio di AmigaOS 4.1U5).

[zzd10h]

Hello,
Amiga Supremo, you too, like Samo79, have a "recoverable alert" when you launch SysMon when the jingle is playing ?

If yes, could you say me what is your config, please ?

I have never be able to reproduce this problem...
zzd10h

[samo79]

Come dicevo,
ho aspettato AmiUpdate e come per magia, TUTTO risolto (meno il bug al lancio di SysMon durante l'emissione della musichetta d'avvio di AmigaOS 4.1U5).

Hai un recoverable alert giusto ?

Prova ad impostare il tooltype DEBUGSLEEP almeno a "7" o più, infine riavvia l'Amiga e riprova sempre lanciando SysMon durante il jingle di boot

Questo è un problema stranoto che non è ancora riuscito a fixare, considera che la stragrande maggioranza dei nostri test è stata fatta solo per risolvere sta cosa, purtoppo però senza tanta fortuna ..

Altra cosa, questo problema all'avvio lo hai solo su Sam440 oppure anche su AmigaOne ?

P.S.

Hey Guillaume welcome !

[Amiga Supremo]

@ zzd10h
Many thanks for SysMon!
My hardware configuration is as follows:
AmigaONE XE G4@1000, 2GB RAM, RADEON 9250 256MB, AmigaOS 4.1u5.

@ samo79
Dove mi trovo ora ho a disposizione soltanto l'AmigaONE.
La SAM mini itx @667 , la SAM flex Vento @800 e il PEGASOS II G4@1000 si trovano altrove.

Adesso provo il suggerimento che mi hai dato e ti faccio sapere.

[Amiga Supremo]

Prova ad impostare il tooltype DEBUGSLEEP almeno a "7" o più, infine riavvia l'Amiga e riprova sempre lanciando SysMon durante il jingle di boot

Purtroppo il problema resta.

[samo79]

Dove mi trovo ora ho a disposizione soltanto l'AmigaONE.
La SAM mini itx @667 , la SAM flex Vento @800 e il PEGASOS II G4@1000 si trovano altrove.

Capisco, ti ho fatto questa domanda perchè sul computer di zzd10h (un Pegasos 2) questo problema non si è mai presentato quindi ormai eravamo convinti che fosse un problema specifico sulle Sam

Adesso provo il suggerimento che mi hai dato e ti faccio sapere.

Attivando questa tooltype imposti un ritardo di X secondi, in pratica SysMon (anche quando avviato) rimane "disattivo" per i secondi impostati dal tooltype.. questo inibisce il problema all'avvio, però c'è una controindicazione, se lanci SysMon in una qualsiasi altra situazione (che non sia al momento del boot) devi aspettare quel tot secondi prima di poterlo usare

Ho fatto molte prove e l'attesa minima è 7 secondi, se scendi a 6 riappare il recovery alert, mentre se alzi i valori (sopra 7) il programma funziona bene ma ovviamente necessità di più secondi di attesa .. quindi almeno qui sulla mia Sam la soluzione da compromesso ideale è 7 secondi, questo ovviamente finchè non si risolve alla radice sto problema !

Purtroppo il problema resta.

Prova ad impostare "10", e poi se non va ancora su su a salire ..

[zzd10h]

Thank you Amiga Supremo (and hello Samir)
Yes I wanted to see if you have too a SAM440. Therefore it's not a SAM problem, and there is a french user who tests with a SAM440 and no problem for him.
I have just tested to put my Locale in Italian => no recoverable alert during cold or warm start.

If you put SysMon in your Network-startup, does it works ?

And could you please say me what do you have in your WBStartup and if you have some special things in your user-startup

Me, I have
WBStartup :
Amidock
AsyncWB
Deficons
RAWBInfo
ScreenBlankerEngine
ClickToFront
ContextMenus
RinghioServer
FKey
MouseBlanker
WindowThumbs
LimpidClock

User-startup : (do you have this program ? I test to remove it, no recoverable alert)
run >NIL: c:noalert.elf
run >NIL: c:nodisplayalert.elf

Thanks for your feedback :)

[Amiga Supremo]

If you put SysMon in your Network-startup, does it works ?

No.

For the other questions:

1) In WBStartup I have:
Amidock
AsyncWB
Deficons
RAWBInfo
ScreenBlankerEngine
ClickToFront
ContextMenus
RinghioServer

2) In my User-startup there are no the following lines:
run >NIL: c:noalert.elf
run >NIL: c:nodisplayalert.elf

[samo79]

@Guillaume

On my system there were no problem when starting SysMon from the Network-startup.
As i said numerous time in general this recovery alert comes when you start it "quickly" at the system uptime (for example if you have SysMon iconified on AmiDock and you click on the SysMon's icon within the first seconds)

So in this case more or less exactly when the system is playing the boot sound

This does not means that the problem is strictly related to the execution of the audio sample but only that the program does not seem to be able to "initialize" itself in the first seconds of the system uptime

I think we should only understand why SysMon can't be started within the first seconds of the system uptime, then maybe the problem can be fixed

[zzd10h]

Yes, i understood that the problem is not the sound but the start of the system...
You said "first seconds", I just realized that on my system Amidock is not available before 10-15 seconds and therefore I can't click "really" at start time, but the sound is still playing.
Is your amidock available just when your workbench is launched ?

Amiga Supremo,
if you enable the option STARTSYSTEM=OFF, is the alert still here ?
And could you try, please, to install noguru (with add of the 2 lines in your user-startup) ?
http://eu.os4depot.net/index.php?functi ... noguru.lha
What is the problem when you put SysMon on your network-startup ? What is the line that you add to this file ?

Sorry for all theses questions but as I said, I can't reproduce this problem...

[samo79]

You said "first seconds", I just realized that on my system Amidock is not available before 10-15 seconds and therefore I can't click "really" at start time, but the sound is still playing.

10-15 seconds ?
Why that mutch ?

Is your amidock available just when your workbench is launched ?

Yes, max 1 second or 2 not more ! ..

Please try to start your AmiDock bar in a reasonable time, then put SysMon on it and retry
Maybe we have found the reason why you was never able to reproduce the issue

[zzd10h]

How can I speed up the start of Amidock ?
It's still in first place in the wbstartup Prefs.
I will test tomorrow to put it in the user-startup and/or to change his priority from 0 to higher value.

I hope that it just that and that I will be able to reproduce the bug !

[zzd10h]

No way to reproduce the problem.
Samir, I have sent to you a mail with a link to a video showing my Peg booting and SysMon launching from AmiDock...

[samo79]

No way to reproduce the problem.
Samir, I have sent to you a mail with a link to a video showing my Peg booting and SysMon launching from AmiDock...

Check your mailbox

[zzd10h]

On the video, SysMon is NOT launched from network-startup but is launched by clicking on amidock.
Like you, no ?