Re: [Condor-users] Debugging with cmd.exe

["Thomas Bauer" <tombauer@xxxxxxxxxxxxxxxxxxx>]

I'm not sure, why you want to start the cmd.exe but if you just want to use
commands from the dos-box, put the desired commands into a batch file and
define that batch-file as your executable. 

Thomas

> -----Ursprüngliche Nachricht-----
> Von: condor-users-bounces@xxxxxxxxxxx 
> [mailto:condor-users-bounces@xxxxxxxxxxx] Im Auftrag von 
> mjinks@xxxxxxxxxxxx
> Gesendet: Mittwoch, 16. August 2006 01:53
> An: condor-users@xxxxxxxxxxx
> Betreff: [Condor-users] Debugging with cmd.exe
> 
> I'm still trying to get Condor and Windows to play nice together, 
> knowing next to nothing about Windows... And my latest attempt 
> involves trying to get Condor to run a copy of cmd.exe just to prove 
> that everything is working.
> 
> I have a copy of cmd.exe, and a submit file which transfers the 
> executable and then calls it.  Everything seems to work fine, except 
> that the window only pops up on the Windows machine for a split 
> second, and Condor's logs show what looks like a successful job 
> completion.
> 
> Is this expected behavior?  Shouldn't cmd.exe run interactively until 
> the user at the console dismisses it?  Or am I thinking in Unix again?
> 
> If normal behavior would be for cmd.exe to stick around, but it isn't 
> in my case, that might provide some insight into why other Windows 
> apps aren't working as expected for us, especially if we can figure 
> out why.
> _______________________________________________
> Condor-users mailing list
> To unsubscribe, send a message to
> condor-users-request@xxxxxxxxxxx with a
> subject: Unsubscribe
> You can also unsubscribe by visiting
> https://lists.cs.wisc.edu/mailman/listinfo/condor-users
> 
> The archives can be found at either
> https://lists.cs.wisc.edu/archive/condor-users/
> http://www.opencondor.org/spaces/viewmailarchive.action?key=CONDOR
>