Nice tool, but as i pointed on os4depot, imho will be cool to have first refresh by default. Because right now it looks like this: user run it, press on any gadget, and have "empty" list and need to press "refresh". Which is a bit strange .. Imho better make or only one time auto-refresh when user first time press on the gadget, or (what is much better), just auto-refresh all the time when user press on gadget (imho that will be very easy to add, and it will increase usability a lot). By gadget i mean these ones which at top. Like you press on Exec gadget, and first sub-gadget are "Tasks", so, for that action auto-refresh. (in general, all other apps works like that ( i mean scout, artm and others) )

I too think its really behavour of an app to have to press on refresh for every funktion.

Anyway thanks for the update

Quote:
+1

Refreshing the list of the Exec/IntHandlers locks up my system completely every time.

on Ranger, MTU value is 1518 (I'm at the job) and not 1460, as setted on my SAM ???

EDIT: real values.

Stack: 1518 Hardware: 1518 Bytes

@Mrodfr
From the Roadshow docs:
Quote:

Hello,

For me, MTU:1500 for PPPOA and MTU:1492 for PPPOE and not more.
That mean I'm surprised for 1518 (who now I know It's the idea of the maximum transmission size of the driver).

In ENV/roadshow/mssdltf, I have 1500.

Ranger should show:
Stack: 1500 Hardware: 1518 Bytes

and not:
Stack: 1518 Hardware: 1518 Bytes

BTW, ranger show Roadshow values as 1500\n when changed the value with an editor and use enter or with the command in a shell.

Ranger is a great tool, and with bubble help for all, wil become a great information system tool IMHO.

For sure, also the big possibility that I don't understand all

Can SAM users really could use MTU=1518 ???

Quote:
I did not do that initially because some queries require using Forbid() or Disable(). As a compromise, I will enable refreshing for any tab that does not use Forbid/Disable for the query.

The reason is simply because Ranger is a tool for programmers and testers to debug issues. This usually means you run Ranger after a crash so the system is already in an indeterminate state (e.g. hitting Ignore button on Grim Reaper).

Quote:
Please email me the bug report and maybe we can figure this one out.

Quote:
I've designed Ranger to report only the truth. It's not my fault you can't handle the truth....

And yes, the Sam has always used that MTU and the ethernet driver enforces it.

@ssolie

I have to do hard reset so I can't get any Reaper output.

Quote:
Please use email to report bugs. Thank you.

Thanks for the update

Quote:
Are you aware of any upcoming API changes that remove the need for using Forbid calls?

Cheers!