Home  
Login
Username:

Password:

Remember me



Lost Password?

Register now!
Sections
Who's Online
45 user(s) are online (8 user(s) are browsing News)

Members: 0
Guests: 45

more...
Support us!
Recent OS4 Files
OS4Depot.net
Recent Replied Topics
Software News : Ranger 1.41
Posted by ssolie on 2009/12/15 1:56:14 (1208 reads) News by the same author
Software News

Ranger has been updated to version 1.41 and includes a few new features especially for AmigaOS 4.1 users. Download Ranger from OS4Depot or use AmiUpdate.

Changes include:
- Added home directory (aka PROGDIR:) field to DOS/Processes tab.
- Added monitor DDC information to Hardware/Gfx Boards tab.
- Added new effects fields to Screen and Window attributes in the GUI/Objects tab.
- Added Exec/IntHandlers tab which displays information about the interrupt handlers.

Note that some new features require AmigaOS 4.1 Update 1 which has not yet been released.

Printer Friendly Page Send this Story to a Friend Create a PDF from the article
The comments are owned by the author. We aren't responsible for their content.
Author Thread
kas1e
Published: 2009/12/15 10:05  Updated: 2009/12/15 10:08
Home away from home
Joined: 09/11/2007
From: Russia
Comments: 3961
 Re: Ranger 1.41
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) )
Kicko
Published: 2009/12/15 19:15  Updated: 2009/12/15 19:15
Just can't stay away
Joined: 10/25/2007
From: Gothenburg / Sweden
Comments: 1167
 Re: Ranger 1.41
I too think its really behavour of an app to have to press on refresh for every funktion.

Anyway thanks for the update
TSK
Published: 2009/12/15 19:34  Updated: 2009/12/15 19:34
Just can't stay away
Joined: 02/23/2007
From: Finland, the land of Santa, sauna, sisu and salmiakki
Comments: 1011
 Re: Ranger 1.41
Quote:
just auto-refresh all the time when user press on gadget

+1

Refreshing the list of the Exec/IntHandlers locks up my system completely every time.
Mrodfr
Published: 2009/12/16 6:53  Updated: 2009/12/16 17:38
Quite a regular
Joined: 10/14/2008
From: France
Comments: 647
 Re: Ranger 1.41
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
ZeroG
Published: 2009/12/16 17:08  Updated: 2009/12/16 17:08
Not too shy to talk
Joined: 12/08/2006
From: Germany
Comments: 391
 Re: Ranger 1.41
@Mrodfr
From the Roadshow docs:
Quote:

The interface driver will have its own ideas about the maximum transmission size. You can therefore only suggest a smaller value than the driver's preferred hardware MTU size.
Mrodfr
Published: 2009/12/16 17:48  Updated: 2009/12/17 6:48
Quite a regular
Joined: 10/14/2008
From: France
Comments: 647
 Re: Ranger 1.41
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 ???
ssolie
Published: 2009/12/17 15:43  Updated: 2009/12/17 15:43
Amigans Defender
Joined: 11/26/2006
From:
Comments: 983
 Re: Ranger 1.41
Quote:
imho will be cool to have first refresh by default

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).
ssolie
Published: 2009/12/17 15:45  Updated: 2009/12/17 15:45
Amigans Defender
Joined: 11/26/2006
From:
Comments: 983
 Re: Ranger 1.41
Quote:
Refreshing the list of the Exec/IntHandlers locks up my system completely every time.

Please email me the bug report and maybe we can figure this one out.
ssolie
Published: 2009/12/17 15:47  Updated: 2009/12/17 15:47
Amigans Defender
Joined: 11/26/2006
From:
Comments: 983
 Re: Ranger 1.41
Quote:
Can SAM users really could use MTU=1518

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.
TSK
Published: 2009/12/17 16:50  Updated: 2009/12/17 16:50
Just can't stay away
Joined: 02/23/2007
From: Finland, the land of Santa, sauna, sisu and salmiakki
Comments: 1011
 Re: Ranger 1.41
@ssolie

I have to do hard reset so I can't get any Reaper output.
ssolie
Published: 2009/12/18 5:01  Updated: 2009/12/18 5:01
Amigans Defender
Joined: 11/26/2006
From:
Comments: 983
 Re: Ranger 1.41
Quote:
I have to do hard reset so I can't get any Reaper output.

Please use email to report bugs. Thank you.
Kicko
Published: 2009/12/18 19:14  Updated: 2009/12/18 19:14
Just can't stay away
Joined: 10/25/2007
From: Gothenburg / Sweden
Comments: 1167
 Re: Ranger 1.41
Thanks for the update
gregthecanuck
Published: 2009/12/19 1:59  Updated: 2009/12/19 1:59
Just popping in
Joined: 12/05/2006
From: Vancouver, Canada
Comments: 164
 Re: Ranger 1.41
Quote:
I did not do that initially because some queries require using Forbid() or Disable().

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

Cheers!
General
Site sponsors
Advertise Here

Site statistics
Registered members
  1326
Logged in last:
  24 hours, 53
  7 days, 103
  30 days, 151
Top Posters
1 kas1e   kas1e 3961
2 ChrisH   ChrisH 3187
3 orgin   orgin 3057
4 Chris   Chris 3020
5 samo79   samo79 2873
6 Raziel   Raziel 2693
7 LiveForIt   LiveForIt 2565
8 Antique   Antique 2452
9 328gts   328gts 2107
10 Mikey_C   Mikey_C 2043
New Members
tomnic79   tomnic79 09/27/2016
Obi   Obi 09/24/2016
Hedeon   Hedeon 09/01/2016
TenLeftFingers   TenLeftFingers 08/17/2016
drGspot   drGspot 07/25/2016
DrMcCoy   DrMcCoy 06/13/2016
Helloworld   Helloworld 05/28/2016
strim   strim 05/26/2016
SMC   SMC 03/24/2016
Kremlar   Kremlar 03/14/2016
Powered by XOOPS 2.0 © 2001-2016 The XOOPS Project