From: "da Silva, Joe" 

I guess it's case sensitive because it's _not_ a DOS thing.
AFAIK, this ANSI sequence stuff originated as a terminal
(from the time before personal computers were available or
at least readily available) control "language", I think from the
DEC VT100 terminal or one of its relatives. The DOS ANSI
driver simply emulates this, so the original terminal must
have been case sensitive.

BTW, when using ANSI sequences in batch files, it may be
useful to check that the ANSI driver is actually loaded. So,
you may like to try my CHKANSI utility, available from :
http://jds-freeware.hypermart.net/

Joe.

> -----Original Message-----
> From:	DONALD PEDDER [SMTP:jims_son{at}jedi.apana.org.au]
> Sent:	Wednesday, December 03, 2003 11:51 PM
> To:	opendos{at}delorie.com
> Subject:	Re: ANSI.SYS
> 
> > unless you want to be called spammer again ;->)
> 
>    Yes, not very helpful that the output of technical system info gets
> regarded as spam. :-(
> 
> 
> > Maybe you just mistyped the escape sequences?
> 
>    I actually just solved it myself after a quick look around the web. It
> turns out it's case-sensitive (not a very DOS-like thing to do, though I
> guess it's because we're talking binaries here, not plain text).
> Paradoxically (i.e. someone needs to proof-read this stuff) the doco
> showed a lower-case "m", whereas the example given at the end was in
> upper-case (which is what I originally had and wasn't working). It works
> now that I have changed the case (although the cursor is going back to
> white again after I've called an app).
> 
>    I'll get back to you guys about the other stuff later (just a few
> further comments to make, for future reference), but for now know that I
> have resolved all my issues. :-)
> 
> thanks,
>   dp.


--- Internet Rex 2.29