Back to home page

DOS ain't dead

Forum index page

Log in | Register

Search:  
Back to the forum
Board view  Mix view

The Doszip Commander version 3.08 available (Announce)

posted by nidud E-mail, Norway, 11.10.2013, 00:40

> > The problem with executing old .EXE?s (BC/BCC/... is now solved by using
> a
> > .BAT file to execute these .EXE?s. There is however now an issue with
> > redirection like JWASM -? > jwasm.txt, so this may also need some
> > special handling.
>
> Besides CMD or 4DOS, I don't think most true DOS shells (e.g. FreeCOM)
> allow you to redirect .BAT output directly, so you have to do "%COMSPEC% /c
> blah.bat > blah.out".
>
> But I assume you already knew that, so I dunno, just trying to be helpful
> anyways. :-P
It's only a valid .EXE that is executed directly (like JWASM), so all other commands uses %COMSPEC%.

There are some exceptions to this as mention above, but the redirecting thing is also a problem, and in this case "blah.bat" should be:
@echo off
JWASM > JWASM.TXT

The command executed will then be %COMSPEC% /c blah.bat
Instead of JWASM > JWASM.TXT which will result in:
Fatal error A1106: Cannot open file: "." [6]
Fatal error A1106: Cannot open file: ".." [6]
Error A2106: Cannot open file: "jwasm.txt" [ENOENT]

So you may argue that this is a weakness in JWASM which is unable to handle the '>' argument. :-P

The problem is that some .EXE's creates problems executed directly (depending on what %COMSPEC% actually is), and to fix this a .BAT extension should be used for this (not .CMD). But in addition to this, redirected commands should also have the same handling.

This may be the reason the command above and the .EXE-thing fails in FM.

Post reply
 

Complete thread:

Back to the forum
Board view  Mix view
22632 Postings in 2109 Threads, 402 registered users, 365 users online (0 registered, 365 guests)
DOS ain't dead | Admin contact
RSS Feed
powered by my little forum