------------------
Just

My best advice would be to start by reading through the Sample scripts that come with the distribution, then read through Bryce's Starter's Guide And if you have questions after that, I would recommend using the search tool on this fine site to search both discussion areas because chances are someone has asked something similar in the past. If you can't find it there, post a question, and if it's regarding a problem with a script, post the script, or a section of it, to give us an idea of what's occuring. And last but certainly not least, Have fun with it!

------------------
"He was a good little monkey and always very curious..."

[This message has been edited by Paul_Berquam (edited 07 December 2000).]

------------------
Jesse
------------------
For more scripting help and examples, click here.

[This message has been edited by Elvis2000 (edited 10 December 2000).]

Welcome to "da-board" friend !

I second Paul's suggestion that you read Bryce's starter's guide.

My other advise is that you start small - write some simple scripts and get them running on your workstation first.

Learn the language - then start tackling the slightly more challenging task of getting a domain login script working (you'll be a pro by then).

If your running Win9x workstations - pay special attention to the section in the manual about setting up your KXRPC service.

And yup - have fun (we do) and don't be shy about asking questions on the board here (they're actually a bunch of pretty cool guys and gals).

Shawn.

------------------
Just

If you don't mind me asking...

What made you turn your attention toward KIX? The reason I ask is just one of plain curiosity

Bryce

------------------
Just

here is the one major point that sold me on kix.

The whole collection of group commands! In WSH this is an extremely complicated process especially if you wanted to emulate kix's INGROUP() command.

Kix isn't used for viruses! (yet...... Don't think for a sec that it couldn't! )

It's small overhead.

Ease of use! Anyone who was taught BASIC, or knows BASIC, can easily pick up kix in a matter of days.

Bryce

------------------
Just

I agree with Bryce and would add ...

If we're talking logon scripts and if logon performance is one of your goals... stick with KiX ...

Under the covers - WSH relies on OLE Automation for most (all) of it's functionality and Automation places two extra layers of interface abstraction between you and the actual Windows API's that do the work.

For example - in a logon script scenario WSH has to load an extra object into it's address space just to map a drive. To set environment variables - another object has to be created...

Don't get me wrong, I'm a huge OLE & WSH fan and while the performance difference shouldn't be that great (because they're both interpreted languages after all) - KiX has been engineered specifically for this type of work - and has most (if not all) the requirements builtin...

The other thing is that KiX is actively being worked on from a development standpoint. We're expecting a lot of major enhancements (good things) in the next few releases and in KiXtart2000. Things that will make KiX even more usefull as a general purpose scripting language...

So I wouldn't give up the "ghost" (no pun intended) just yet ...

I'm rambling !

Shawn.

[This message has been edited by Shawn (edited 10 December 2000).]

------------------
Just