Once you have debugged ALL your batch files you can place `CTTY NUL' before
the command(s) and `CTTY CON' after to avoid output to screen.
See below to find how to chain/call another batch file.
Place the 'CTTY CON' first so you don't forget!
You need to be sure there are no interactive
This may sound odd, but is there any way I can use Git on FreeDOS, either
natively (from COMMAND.COM) or from some third-party command interpreter (e.g.
bash)?
Brandon Taylor
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
Hi Travis,
> I don't know if paragon still offers PTS dos for sale or not, but since
> it is one of the few commercial dos clones that comes with source, it
> may be worth asking them if you're interested. I've had my version for
> many years, and I'm always paranoid of loosing my source
Hi,
some more information from this afternoon.
I've made a floppy set of the floppy version, with an P4 with freedos
1.2 with USB und floppy installed.
Booting from bootfloppy is verry slow, but okay.
Fdisk and format works perfect, installing allways stops after the
installer tries to copy
On 26 Feb 2022, 02:54, Bret Johnson wrote:
I've tried creating an ECHO environment variable. With older versions of DOS:
SET ECHO=ECHO OFF
and with newer versions of DOS:
SET ECHO=@ECHO OFF
then at the beginning of all batch files I put a:
%ECHO%
That works with older versions of
It seems trying to redirect the echo off command (at least under windows
in a cmd prompt) does indeed create the echoed test on the screen
because of the STDERR being directed to the screen as stated above.
Regular echo commands however do redirect just fine
I'm fairly certain though that
Hello
Have you tested with a command with @ ex:. @dir ?
On Sat, Feb 26, 2022 at 1:57 AM Bret Johnson wrote:
> This question is more about DOS in general than specifically about
> FreeDOS. But, there are enough experienced and creative users around
> FreeDOS that someone may be able to help
Oh, one more thing...
It could also possibly be a one-liner, like so:
echo off | vgotoxy up | vecho /n /e
But, it will display all of that before erasure. Also, I have no idea if there
would be compatibility issues under some DOS platforms or their different
versions. But, it works fine in
On 2/26/2022 9:14 AM, Mateusz Viste wrote:
On 26/02/2022 15:09, Travis Siegel wrote:
Barring those solutions, you could always redirect the @echo off line
to null, which would prevent it from displaying on the screen.
It would not, since the error message is output to stderr.
That's not
Well, I guess I’ll put in two cents worth of a non-standard solution…
If you don’t want to have the “echo off” on the screen and don’t want to clear
the screen either, you can do it using two utilities in V8Power tools
(available and provided with FreeDOS).
It would look something this…
——
On 26/02/2022 15:09, Travis Siegel wrote:
Barring those solutions, you could always redirect the @echo off line to
null, which would prevent it from displaying on the screen.
It would not, since the error message is output to stderr.
Mateusz
___
Why not use the @echo off syntax, then simply use the cls command to
clear the screen before moving on to the later pieces of the autoexec.
It then won't show the @echo off command onthe screen.
The caveat of course is that all driver messages also get erased, but
that may or may not be an
Hi Bret
The simplest solution is to use ECHO OFF without the @ at the start of your
BAT file. That will work everywhere. If you don't like seeing this line on
the screen at boot, you could run CLS after that.
I suppose another way to solve this is with a simple tool that detects the
DOS version.
Hallo Herr Mercury Thirteen via Freedos-user,
am Samstag, 26. Februar 2022 um 03:47 schrieben Sie:
> Would it be feasible to throw together an "@ECHO.COM" application
> which would manually execute a normal "ECHO OFF" line if the DOS
> version is below 3.3 and simply terminate otherwise? The
14 matches
Mail list logo
