World: r3wp

They should add that and we should have a command like the one you 
gave as a mezz function

You could always use CALL to get this info and the parse it.

What OS?

yeah I know I actually have to do that now with a call to netstat 
-aon

You could always use CALL to get the open ports on the host system 
and the parse it. What OS? Do you want support for?

I'm working on a project now that I want to send out but don't want 
it to look so much like a batch file as much as having its own capabilities 
inherent.

Lower level access in rebol is only possible either through CALL 
or via a SYSTEM CALLS using the DLL access.

Yeah the DLL wont cut it as this would require the use of my /sdk 
license and the company wont go with that.

The CALL function really helps now though

I really hope RT puts some functions in to free REBOL distros such 
as remote registry capabilities

Then we can use it for administrative purposes and role it out to 
40,000 plus desktops

Why not just use SDK. Surely a BigCo can afford it. Besides I think 
is better to distribute such tool in an encaped form.

You don't want someone changing the src code of a script that manipulates 
the registry of a host environment.  Too much security risk, 80% 
of security problems oringinate inside the companies infrastructure.

Its strange but they wont purchase things that are not accepted by 
the application development teams to support other clients.  The 
only way to really penetrate the big companies in this regard is 
to have one heck of a salesman that can talk about standards and 
support or bring it in free where there is no costs or penalties.

Well with XP pro which is our common operating environment scripts 
can be set to run under certain credentials

We currently have WSH carry much of that load

Really strange... What about "A build it and they will come strategy"?

That's just not realistic enough

We have perl used extensively as well

Why?  If you create something you give it to users, and they start 
using it. They may push presure on the Echolons to favor your solution.

The biggest obstacle to making an encapped module in this environment 
is knowledge distribution

For example, if we rolled out an encapped file to 40,000 desktops 
and someone walked up and said who did this and they said Paul did 
- then they would say what happens if Paul leaves us.

You mean you are the only one with rebol knowledge?

They would never let them get themselves that vulnerable.  To much 
risk

I'm sure we have others in the company but not on this account - 
I'm it.

Well. You pointed them to network Rebol consultants that could support 
them. (Gabriele, Robert, Cyphre, Ladislav, Greg, DideC, Nenad and 
others...)

One time I created a nice program that would go out and check backups 
on the servers.  Because it was an executable file they got rid of 
the system - even though it was better than anything else we had.

That isn't good enough unfortunately

They need to be able to pick up a phone and get results.  We deliver 
Service Level Agreements that costs a lot of money when they are 
not met.

Also if you write document your script really well and show the code 
is easy to follow (cookbook tutorial) you may gain your boss trust 
and their request for other agents inside your company to learn Rebol.

You gotta remember when I say we have 40,000 desktops that isn't 
a typo.  We have teams dedicated to certain tasks including an application 
development team

I don't think the problem is about free features in free-rebol vs 
sdk. It is about education of the decision makers.

I'm not part of that team.  I'm part of the field services team which 
handles administrative functions.

Yeah Jaime your partially correct but if WSH can do it for free why 
REBOL - get my point?

I think you need to keep trying on viral approach, sneak some code 
there, and convince others to acept it.

I have made an application here and there that has been noticed but 
mine are all free - I don't charge and I'm bound that if I did make 
anything particularly useful they would own it anyway.

Why REBOL? (Thats a loaded question). Part of the answer is because 
it makes your life easier. So freeing your cycles and potentially 
the cycles of others, making the company more efficient.

Therefore, I see no way to penetrate the REBOL product into the environment 
unless I make a killer app or unless we can do the better work with 
REBOL at the same costs or better.

(Lets move to Chat)

ok

(Better lets create a new group)

Jaime - I noticed that the broadcast address that returns from that 
ipconfig function is not correct in cases where the netmask is different 
than 255.255.255.0.  Maybe a bug in get-modes when used on the interfaces.

Jaime, the port does not need to be ope. Just get-modes udp:// 'interfaces 
(or tcp://)

*open

Thanks Gabriel. Here is a shorter version, thanks to your hint.

ipconfig: has [interfaces] [
    foreach dev interfaces: get-modes udp:// 'interfaces  [
        print reform compose [
            join dev/name ":" "flags" mold dev/flags newline
            "^-inet" dev/addr "mask" dev/netmask 

            (either dev/broadcast [["broadcast" dev/broadcast]][""])

            (either dev/dest-addr [["dest-addr" dev/dest-addr]][""])
        ]
    ]
    interfaces
]

I know how to set the title of the window in REBOL/View, but how 
can I change the title of a REBOL core console?

with a system call

win-lib: make object! [	
	user-lib: load/library %user32.dll
	SetWindowText: make routine! [
		handle			[integer!]
		Title			[string!]
		return:			[integer!]
	] user-lib "SetWindowTextA"
	
	set 'WindowTitle func [
		Title [string!] 
	] [
		SetWindowText get-modes system/ports/system 'window Title
	]
]

WindowTitle "eFishAnt Ink"

can't remember who gave me that...

For POP3 and email fans:


   http://www.rebol.org/cgi-bin/cgiwrap/rebol/documentation.r?script=do-pop-scheme.r


Gives you easy access to LIST, TOP, UIDL, etc. for your spam delete 
scripts or whatever.