code:

---

;
; For Test stuff, duh.
;
break on
?"Site           : " + @site
?"UserName       : " + @userid
?"WUserName      : " + @Wuserid
?"Fullname       : " + @Fullname
?"Comment        : " + @Comment
?"LanRoot        : " + @LanRoot
?"Machine Domain : " + @DOMAIN
?"Login Domain   : " + @LDOMAIN
?"SID            : " + @SID
$sid2name = SIDTONAME ("@SID")
?"sid2name       : " + $sid2name

---

KIX32 test.kix is the syntax I used.

I added this to keep it on screen for a while at least:

code:

---

?"press any key to continue..."
GET$

---

I don't know. I just started a cmd prompt on Windows 2000 SP2 into a directory that is not on my path.

I have the KiXtart 2000 v4.00 Beta 2 in this directory.
I ran this code and it pops open a new DOS BOX and immediately goes away.

code:

---

"Hello"

---

I don't run the 2000 code daily, but I could swear that did not happen last week.

No answer yet, but I can confirm the same problem.

NTDOC

[This message has been edited by NTDOC (edited 26 June 2001).]

So umm did this Beta 2 have some sort of time bomb in it? The scripts ran just fine last week.

The KiX32C.exe version works the same as KiX 3.6x in that it runs in the current console. This means that if you run KIX32 just like you always have, and the new Beta .EXE is in you path before the old .EXE, then your scripts will behave differently - you will get the "flashing console" effect.

The first thing I do when I get the next Beta is to rename the exes the other way around, ie KiX32C.exe is the consoleless version and KiX32.exe is the old fashioned version using the current console. I belive the live version of KiX2k will be like this also.

hth

cj

------------------
cj's scripts page
cj's User Guide - 14 May 2001

chrismat@ozemail.com.au

Jochen

_________________________

cj

------------------
cj's scripts page
cj's User Guide - 14 May 2001

chrismat@ozemail.com.au