Viktor Szakáts wrote: > Hi Maurilio, > >> Viktor, >> >> .bat files are executed by OS/2 command.com (that is they start the dos >> emulator) and as such they have the same limits/capabilities of a real >> dos >> batch file. > > Is this done in smooth way? so that I may integrate postinst.cmd > functionality into postinst.bat for OS/2? We don't need special > capabilities there (just echo, copy, cd, if, calling zip). In fact > dos mode would be better, since dos is already supported in this > file, so we wouldn't have to maintain the same code for 3 different > cmd processors, just 2. >
I think you should integrate NT/XP .cmd batch files with OS/2 ones, this way they are executed by the native shell on both platforms. Anyway, if you call a .bat file, a dos window gets opened and it executes its autoexec.bat and then the .bat you passed it. BUT, the environment of the cmd.exe process is NOT inherited by the command.com one, so all variables like HB_... or the ones created by make are not visible inside command.exe environment. AND, you cannot start a .bat file from a path which is not fully 8.3 (for example I have my svn copy on \repository\harbour and from such a path no .bat file can be executed). > Second question: > Can you force execution of .bat file to be executed by OS/2 shell, > by issuing: 'CMD.EXE /C hello.bat' ? > Yes, but with the limits I wrote above. Maurilio. -- __________ | | | |__| Maurilio Longo |_|_|_|____| farmaconsult s.r.l. _______________________________________________ Harbour mailing list [email protected] http://lists.harbour-project.org/mailman/listinfo/harbour
