News:

MASM32 SDK Description, downloads and other helpful links
MASM32.com New Forum Link
masmforum WebSite

about enviroment

Started by Rockphorr, June 13, 2006, 10:19:21 AM

Previous topic - Next topic

Rockphorr

Which envirvars are case censitive??

I create enviroment for child command.com with 'prompt=$p$g',0
This was no effect.
The effect was after convertion to upper case:  'PROMPT=$p$g',0
Strike while the iron is hot - Бей утюгом, пока он горячий

MichaelW

Either case, or mixed case, works for me under Windows 2000 and Windows 98SE. Environment variables were not case sensitive under MS-DOS, and I thought Windows continued this convention.

eschew obfuscation

Rockphorr

Quote from: MichaelW on June 13, 2006, 11:49:19 AM
Either case, or mixed case, works for me under Windows 2000 and Windows 98SE. Environment variables were not case sensitive under MS-DOS, and I thought Windows continued this convention.

I was agree with you until yesterday. This BUG with prompt var was found under Windows 95.
Set command always converts to upper case.
Strike while the iron is hot - Бей утюгом, пока он горячий