| **DONOTDELETE** |
| (Lurker) |
| 2001-10-11 05:45 PM |
Nothin' but beeps
|
I have about 5,001 questions so far, but I'll start with this one. I have a test DC set up, with a test box joined to it. Both are Win2K. I have installed KiXtart in the netlogon share directory. I have the test user profile set to run login.bat which looks like this...
@echo off
%0\..\kix32.exe %0\..\cpu.KIX
%0\..\kix32.exe %0\..\os.KIX
%0\..\kix32.exe %0\..\McAfee.KIX
%0\..\kix32.exe %0\..\welcome.KIX
%0\..\kix32.exe %0\..\memory.kix
:END
These are some fairly generic kix scripts I downloaded from kixtart.org. I have tried running just one script at a time, I have tried commenting out just one script. It doesn't matter. I just get a series of beeps (4 actually) and none of the scripts seem to run.......
Jochen
|
| (KiX Supporter) |
| 2001-10-11 06:38 PM |
|
Re: Nothin' but beeps
|
Glenn,
what happens if you REM the line @echo off ,
and add a 'pause' before :END ...
That doesn't solve the problem but shed some light on it !
On for the next 5000 questions 
Jochen
| **DONOTDELETE** |
| (Lurker) |
| 2001-10-11 07:10 PM |
Re: Nothin' but beeps
|
I tried that, but the scripts still close out the DOS window - I just now mapped the netlogon drive as E: and manually ran each script like this:
c:>e:\kix32.exe e:\os.kix
scripts ran (still closed out DOS window) - the memory.kix still beeps - the McAfee script actually writes a file to my hard drive - the others don't appear to be doing any thing.....
I'm sure there's a better way to do this.....
| **DONOTDELETE** |
| (Lurker) |
| 2001-10-11 08:35 PM |
Re: Nothin' but beeps
|
I had the same problem then I changed my batch file that launches the Kix script to this.
%o\...\kix32.exe \\servername\path\scriptfile.kix
then check your memory.kix file to see what code it is using or post the memory.kix file to the forum
| **DONOTDELETE** |
| (Lurker) |
| 2001-10-11 10:37 PM |
Re: Nothin' but beeps
|
hmmm.....well, I got the McAfee.kix script to work, sort of. I used the "%0\..\" for the path and that worked. It writes a debug file and a log file to the test box hard drive, but NOW what? I'm not even sure what these files are telling me.
I got the CPU.kix to work ONCE.....but now I don't remember the syntax I was using at the time. It hasn't worked since. The "%0\..\" doesn't seem to work on that one.....
Confused as hell....
| MCA |
| (KiX Supporter) |
| 2001-10-15 02:53 AM |
|
Re: Nothin' but beeps
|
Dear,
Welcome to the board.
How did you download those scripts from the kixtart.org board? By copy the
script part from the topics?
Which version of kixtart you are running?
We doesn't know a section were you can find scripts for downloading.
Only Henri has make by the scripts entry on the main page of the kixtart.org
site a link to our site http://home.wanadoo.nl/scripting .
This site contains above scripts. Some scripts requires additional programs
for running f.e. cpu.kix and possibly memory.kix.
Scripts will run normally correct.
For cpu.kix we use an additional program which is included in our cpu.zip
file. It is of course possible that this external program can get the right information
for your type of machine.
By the memory.kix the internal programs aren't available or doesn't return
the correct output. We normally runs it with the additional program memory.exe.
The welcome.kix was special developped for windows NT environment. No real checking
for Windows 2000 or Windows XP. This script doesn't have any effect for Windows 9x systems.
Symbol 
on our homepage has been linked to related http://kixtart.org topic.
Greetings.