Hi, > If I run either TEST1.BAT or TEST2.BAT with MS-DOS 3.0, 3.1, or 3.2, it > crashes.
That is definitely possible. Since the earliest version of DOS I really only every used was MS 3.3, I never have worried about pre-3.3 compatibility. > If I run them with MS-DOS 3.3 or 4.01 the session looks like this: > > C:\>test1 > > > C:\> ECHO Test Line 1 > Test Line 1 > > C:\> ECHO Test Line 2 > Test Line 2 > Test Line 2 > > C:\>test2 > > Test Line 1 > Test Line 2 > Test Line 2 > > C:\> Interesting, I wonder where the duplicate “Test Line 2” is coming from. vecho does not use STDOUT to display text, it uses the BIOS. Same for scrolling, etc. > If I run them in MS-DOS 5.0 thru 6.22 the session looks like this: > > C:\>test1 > > > C:\> ECHO Test Line 1 > Test Line 1 > > C:\> ECHO Test Line 2 > Test Line 2 > > C:\> > C:\>test2 > > Test Line 1 > Test Line 2 > C:\> > > If I run them in DR-DOS 6.0 thru 8.0 the session looks like this: > > C:\>test1 > > Test Line 1 > Test Line 2 > C:\>test2 > > Test Line 1 > Test Line 2 > C:\> > > If I run them in FreeDOS 1.2 or 1.3 the session looks like this: > > C:\>test1 > Test Line 1 > Test Line 2 > C:\>test2 > Test Line 1 > Test Line 2 > C:\> > It looks like the OS is forcing a CR after execution. Which is down right inconvenient. A possible remedy would at boot set a env variable for the OS (which you probably already do). The after erasure, if not running on FreeDOS, perform a additional vgotoxy up or possible or double that vgotoxy up up. echo off | vgotoxy up | vecho /n /e if not “%OS% == “FREEDOS” vgotoxy up up > As you can see, there are extra blank lines (though that problem is not a > deal-killer), extra ECHO's, and extra DOS prompts (extra <Enter> keys being > pressed) depending on the specific environment. I think FreeDOS is the only > one works the way I think it should (no extra "stuff" appearing on the screen > anywhere). There is one other thing to try via v8power tools. Instead of using vgotoxy up | vecho /n /e, there is another combination to do it as well. echo off | vgotoxy up | vdelete vdelete doesn’t display text. It literally deletes a row and feeds a blank line in from the bottom. It can be told to remove multiple lines. However, defaults to 1 line. Outside of a couple rare situations they rarely get used. So, I sometimes forget about them. Anyhow, vdelete is a far simpler program than vecho. You may even have better compatibility results. However, you may be better off writing a HUSHECHO program that does all of this. It could test the DOS Version and perform any additional stuff required. As you find exceptions, just add a little more to it. Probably only be 100-200 byte com file total even with the exceptions. :-) Jerome > > > _______________________________________________ > Freedos-user mailing list > Freedos-user@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/freedos-user _______________________________________________ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
