The error message is very helpful, actually.

When you say "Y:\folder\file.exe", you tell the O/S to run "file.exe", which is found in the path "Y:\folder". Just because you tell the O/S where the file that you want to run is , it doesn't mean it will go there and then run the file, it just means it will run that file while sitting right where it is (in it's favorite easy chai - um - folder.

The message is most likely coming from the installer, not the OS. So - get a little more complex - Create a batch file to run the installer - EasyStart.BAT. It should look something like
 Code:
@Echo Off
Y:
CD \EasyAudit
.\EasyStart.exe (plus any needed args) >C:/temp/install.log 2>C:\Temp\error.log

This assumes that you mapped the drive to Y: in Kix before running this command via
Shell "Y:\EasyAudit\EasyStart.bat"

If that works, you can think about doing these commands in Kix if you wish, but using the bat file will let you test outside of kix. That's important when debugging and you're not sure if the problem is Kix, the environment, or the application you're launching.

I had an issue this past Tuesday where an install failed because there was a space in the path defined by %TEMP%. Spent a while looking at my Kix script before I started running the commands manually. Really tough, because no error wass generated, the process just exited silently. Basically, it pays to break your logic into managable chunks, even outside of your core process.

Glenn
_________________________
Actually I am a Rocket Scientist! \:D