Simply can't seem to get a RUN command to work. - KiXtart.org - official site

You are not logged in. [Log In] KiXtart.org website » Forums » KiXtart » Basic Scripting » Simply can't seem to get a RUN command to work.

Page 2 of 2

2

Topic Options

#188724 - 2008-07-13 02:12 PM Re: Simply can't seem to get a RUN command to work. [Re: Arend_]
Glenn Barnas Glenn Barnas KiX Supporter Registered: 2003-01-28 Posts: 4401 Loc: New Jersey	There are two issues that need to be resolved before trying alternate script start methods... The first is the proper command syntax, which finally seems to have been resolved. Without that, RunOnce and WScript methods would fail just the same. The second issue is the behavior of the install command after it has successfully been invoked. Using the syntax I recommended, with redirection to status and error logs, we can determine what's going on. Rick stated that "the error log said path not found" - If you post the actual data from the logs, instead of a vague interpretation, we could determine where that message is coming from. If you get a message like: Code: 'c:\temp\junk.exe' is not recognized as an internal or external command, operable program or batch file. its coming from the operating system, and you need to check your code to be sure that the mapped drive is available and you're specifying the correct location for the command. However, if you get a different message that states that some file can't be found, it's more likely that my prior explanation is appropriate - you are running the install command, but it can't find the rest of the files it needs to complete the install. You'll need to map the drive, make that drive active, CD to the install folder, and THEN run the install command. Hey - waitaminute!! Your initial command was "\\server\ezaudit\ezstart.exe". Then you say you mapped the drive to "Y:", and then ran "\ezaudit\ezstart.exe". Isn't "ezaudit" the share name? If it is, all you need to do is go to the ROOT of Y: and run "ezatart.exe" with your args. However, if "ezaudit" is not shared, it would explain why none of the UNC paths work. What is the server name? What is the share name? If you map the drive to that share manually, what do you see when you run DIR? (post the actual command output, please) Glenn _________________________ Actually I am a Rocket Scientist! $\:D$
Top

#188726 - 2008-07-14 10:01 AM Re: Simply can't seem to get a RUN command to work. [Re: Glenn Barnas]
Arend_ Arend_ MM club member Registered: 2005-01-17 Posts: 1896 Loc: Hilversum, The Netherlands	Since this is not tech support, and Glenn does tend to make things overly complicated... Could you please try the following: - Copy the .exe file (and the rest from the exaudit dir) to a location on your C: Drive and just double click it. If that fails then you have a problem that kix cannot solve. If it works: - Copy the .exe file (and the rest from the exaudit dir) to a location on the network and just double click it from there. If that fails then you know it is network related.
Top

#188728 - 2008-07-14 10:45 AM Re: Simply can't seem to get a RUN command to work. [Re: Glenn Barnas]
Richard H. Richard H. Administrator Registered: 2000-01-24 Posts: 4946 Loc: Leatherhead, Surrey, UK	I second Glenns comment about where the program is running. Make sure that you change to a real drive letter (local or mapped) before starting the program (use the GO command in KiXtart). It doesn't have to be the drive that the software is installed on, the local hard drive will be fine. The reason is that some software simply does not like being started by a process whose locale is not a device - some give a reasonable message (like UNC being invalid) and some will just fail silently.
Top

#188742 - 2008-07-14 07:55 PM Re: Simply can't seem to get a RUN command to work. [Re: Glenn Barnas]
Kdyer Kdyer KiX Supporter Registered: 2001-01-03 Posts: 6241 Loc: Tigard, OR	Originally Posted By: Glenn Barnas Your initial command was "\\server\ezaudit\ezstart.exe". Then you say you mapped the drive to "Y:", and then ran "\ezaudit\ezstart.exe". Isn't "ezaudit" the share name? If it is, all you need to do is go to the ROOT of Y: and run "ezatart.exe" with your args. However, if "ezaudit" is not shared, it would explain why none of the UNC paths work. What is the server name? What is the share name? If you map the drive to that share manually, what do you see when you run DIR? (post the actual command output, please) One thing that comes to mind with Glenn's comments - Are you using the Z: Drive at all? The reason I ask is that there are some programs that use the Z: drive.. Kent _________________________ Utilize these resources: UDFs (Full List) KiXtart FAQ & How to's
Top

#188936 - 2008-07-30 09:39 PM Re: Simply can't seem to get a RUN command to work. [Re: Kdyer]
cwick cwick Fresh Scripter Registered: 2003-08-25 Posts: 10 Loc: Ohio	We actually use EZAudit here. This is the command from our login script RUN "%COMSPEC% /c o:\ezaudit\ezscan.exe auto" The O drive is mapped to a share on our server using the USE command. Hope this helps. Chad
Top

#188937 - 2008-07-30 10:07 PM Re: Simply can't seem to get a RUN command to work. [Re: cwick]
Allen Allen KiX Supporter Registered: 2003-04-19 Posts: 4562 Loc: USA	No slash. Ahh. It's always the simple stuff everyone overlooks, but I guess in this case, unless you used that software, you wouldn't know it. Thanks for clearing that up.
Top

Page 2 of 2

2

Previous Topic

Previous Topic View All Topics

View All Topics

Index Next Topic

Next Topic

Moderator: Jochen, Allen, Radimus, Glenn Barnas, ShaneEP, Ruud van Velsen, Arend_, Mart

Hop to:

Shout Box

Who's Online

0 registered and 493 anonymous users online.

Newest Members

BeeEm, min_seow, Audio, Hoschi, Comet
17882 Registered Users

Generated in 0.232 seconds in which 0.213 seconds were spent on a total of 13 queries. Zlib compression enabled.

click tracking