Subj : Calling OS/2 CMD from DOS BAT To : Mike Powell From : Peter Knapper Date : Mon Apr 11 2005 08:45 pm Hi Mike, MP> Is it possible to call an OS/2 CMD file from a DOS batch file? Well... it all depends, but first I must ask, is it absolutely necessary to run a .BAT file or a DOS app?. No, a DOS .BAT file cannot NATIVELY start a ..CMD file, BUT there are ways to actually do this as long as the methodologies don't cause issues. As I see it, your options are - 1. Turn your .BAT files into .CMD files and run them anyway. A Dos executable within the .CMD file will cause a DOS windwo to open and run the DOS app, which ends and control returns to the OS/2 .CMD file, BUT passing return values can prevent this from being much use. 2. Use a 3rd party utility called HSTART. I have never used this because everything I use has a native OS/2 version. 3. Be a bit inventive and manage the activity from an OS/2 .CMD file... By this I mean that you use a master control script that uses FLAG files to control the processing sequence. That way you can start DOS sessions as and when desired, and as long as the FLAG files are managed correctly, everything should flow as expected. I have been using this type of methodology for running all the Background BBS tasks completely external to all Mailer and BBS events, since OS/2 v2.0 hit the streets. It the BBS had been running under OS/2 v1.3 then I would have done it there, it has worked extremely well for me. I can go away for weeks and everything runs automatically, even through power failures (baring major issues). MP> I have moved my board over to the OS/2 system. The one MP> problem I am having is that I cannot run the os/2 version MP> of IREX, unless I do it manually. Ok, I will bite, WHY can this not be done? Any .BAT or .CMD fie can be started in AUTOEXEC.BAT or in the Startup folder, so I fail to see why it has to be manual... MP> I can't call it from the BAT file, and I can't call the CMD MP> file from the BAT file. I am still puzzeled why you need a DOS .BAT file??? MP> I tried START, but that obviously only works in an OS/2 window. ;-) It also work in an OS/2 Full screen session.....;-) However we need to understand WHY you have to run a .BAT file and connot start a .CMD file... Cheers.................pk. --- Maximus/2 3.01 * Origin: Another Good Point About OS/2 (3:772/1.10) .