This is Our
Archive Section
Click Here to
Read or Make a New Post.
Notepad doesn't require START or CMD /C but START gets it to terminate...by (Login The-Universe)Admin The ohter two ways hang until Notepad is colsed, in and screen. I think your SCREN 12 troubles are memory related. I find changing back to SCREEN 0 via SCREEN 9 solves that issue...
CLS SCREEN 12 PRINT "Execute: SHELL " + CHR$(34) + "cmd /c start notepad" + CHR$(34) SHELL "cmd /c start notepad" PRINT "Execute: SHELL " + CHR$(34) + "cmd /c start notepad" + CHR$(34) + " Completed." GOTO 100 PRINT "Execute: SHELL " + CHR$(34) + "cmd /c notepad" + CHR$(34) SHELL "cmd /c notepad" PRINT "Execute: SHELL " + CHR$(34) + "cmd /c notepad" + CHR$(34) + " Completed." PRINT "Execute: SHELL " + CHR$(34) + "notepad" + CHR$(34) SHELL "notepad" PRINT "Execute: SHELL " + CHR$(34) + "notepad" + CHR$(34) + " Completed." 100 SCREEN 9 SCREEN 0 END --------------------------- Get rid of SCREEN 9 and SCREEN 0 and all hell breaks loose. I inckuded the other two ways to get Notepad just to demonstrate how they hang. YOu can get rid of the GOTO statement to test them. Remember to close Notepad each time to ge it to move to the next non-START SHELL statement. Pete
|
| Response Title | Author and Date |
| Thanks. This worked without Screen 9 | on Jul 4 |
| Just another day in this Goth-am City... or as the Caped Crusader would put it... | SCREEN ZERO HERO on Jul 4 |