Note that I have no immediate plans on any kind of wicked voodoo for my implementation / usage.

Thanks...

-=- jd -=-

( I'll likely just grab the final'ized v4 and wait & see what you guys say.... )

I would definitely 100% without a doubt go with KiXtart Version 4.01 ... there are still some very minor unknown, unresolved issues but don't let that stop you. In fact, I cringe now everytime I have to go back to coding in 3.63 ... not too sure if anyone else will back me up here on this one ? I mean, it's not like your setting-up a production environment or anything, right ?

-OldDawg

oops forgot - get this one:

KiXtart 4.01

-Shawn

[ 19 December 2001: Message edited by: Shawn ]

Let say if I start my computer from fresh install for the following OS:
- Windows NT 4.0 SP 1
- Windows 95 (4.0.950)
- Windows 98 (4.10.1998)
does anyone know any support file required for running Kix 4.0?

Thanks,
Tan

See also,
KiXtart Error in NT Event Log for more on that.

All the increased functionality and the blazing speed more than makes up for it.

If you stay on Windows NT 4.0 SP 1 without updating to SP6a then you are asking for problems. There has to be over 3,000 fixes since SP1 "most" software available today will not install with less then SP3 on NT 4.0

DawgBoy... - GO WITH KiXtart v4.01 You won't be sorry. It can do everything v3.63 can and then some... If it works good for systems running 1,000s of machines, I'm sure it will work just fine on a Home system.

As far as what your tyring to do with Linux and SAMBA ... You tell us your success and failures as I don't think too many other users are trying to do that.

I asked this question is not because I want to stay on Windows NT 4.0 SP1, but I want to know the minimum requirements for Kix 4.0 in order to make it run properly.

So, later on, I can set all necessary installations for updating the operating systems in the Kix script, but to make it runs in the lower level environments is first thing first!

I tested beta version of Kix 4.0 before on fresh installation on some OS's and I found an error of missing required .dll file, so this makes me a bit hesitate to upgrade.

Tan

True, the early vesions of the release candidates had a dependency on a newer version of DCOM (OLE) but Ruud fixed that long time ago. You might want to re-evaluate KiXtart 4.01 on freshly imaged machine. Plus, I just read in one of the other forums that Ruud has fixed the set dacl issue and 4.02 is being beta tested as we speak.

Other than that dacl issue, I can't think of any show stoppers.

-Shawn

Ruud has put following release information to kixtart 4.02 build 67 - beta release

Fixes in 4.02 (build 67) beta release:

• Added workaround for 'Failed to set DACL' error on Windows NT 4.0.
  
• Changed default script-extension search order to .KIX, followed by .SCR.
  
• Fixed performance issue in UBound(), VarType(), VarTypeName().
  
• Enhanced SidToName() to drop prefix of wellknown/builtin SIDs.
  
• 'Close' menu option of console is now removed (rather than grayed), unless
  run in debug mode or run outside the logonsequence.
  
• Added a new group-information-cache for Windows NT/2000/XP clients.
  This feature should signigicantly improve start-up time of KiXtart,
  especially for remote/dial-up clients.
  

Why a beta of a minor release?
Ruud's reaction:
Well, mainly because of the new group-info-cache. The feature has of course been
tested, but considering the importance of InGroup, I want to be sure there are no
gotchas.

greetings.