Hi All,

Is there any Win32 API function can launch a process on remote machine? (I don't want to use win32 socket functions etc., just want one or two win32 system API to do it).

I did it 5 years ago on Windows 95 system, but I can't remeber it right now 'cause I worked on UNIX these years.

Thans,
Huoping.

sorry to have to ask... but what do you mean by launch a process?

an application? a window? control panel?
i don't know exactly what you mean.  
        

____________________________
Been busy trying to take a second degree <--it's not working out...

I mean "an application" such as windows calculator (calc.exe).

If windows API is impossible, Is there any other simple way I can do it such as with the help of current exisiting Windows service (I know I can do it with terminal service under windows XP)? I don't want to pre-install any piece of my code in the remote machine, that's the reason I want to use Windows API OR existing service.

Thanks,
Huoping.

q: have you tried using shell method?

____________________________
Been busy trying to take a second degree <--it's not working out...

I just heard about it, but have no much knowledge about it.

I will be grateful to u if you can provide me a piece of easy-read code and which components I need?

Many Thanks,
Huoping.
University of Arizona

I checked the shell COM objects. It seems that it can only support the some operations on local machine.

  

okay. well, i am trying to find some of my old files, and if i get to, i'm hoping that i find the source code on launching applications.

have you tried the run.dll? scrun.dll run.32.dll? i think the api's can be found there.. i'll look into it. please be patient. this may take a while, but i hope others too  will come to your aid.

____________________________
Been busy trying to take a second degree <--it's not working out...

I've never been able to run an aplication on a remote PC via Vb code without having a program already installed on that PC written in VB.

If possible, it would depend on (if on a NT based machine [XP too]) security permissions of the user on the sending machine.

As you're probably thinking, if you're on NT systems, with proper permissions, you can always "cheat" and use the AT command (for specifics enter "AT /?" at the cmd prompt).

Ex:

Private Sub RunProgram() ' Assumes that remote PC is at same time yours is ' Run Specified app 1 min from now      Shell "AT WorkstationName " & Hour(time) & ":" & Min(time)+1 & Chr(34) & "Calc.exe" & Chr(34) EndSub

[Edited by JLRodgers on 20-11-2002 at 02:03 PM GMT]

Thanks very much.

Yeah, the at.exe OR soon.exe is not bad choice. We really can do it if we comply with certain Windows security.

The limit is We need conform to the Windows Domain Secutiry mechanism such as we need admin privelege.

Anyway, it's a good idea.

Thanks again,
Huoping :-)