FULLSCREEN CONTENTS Project Home Page
.WINDOWS_USE.: Problem - /V Does Not Work Under NT
.ALIAS.......: v_does_not_work
.DISCUSSION..:
There are two problems that people commonly report when attempting to run Fdate under Windows NT. One is that they run out of environment space. The other is that the /V parm does not work, and Fdate's output is not be put into an environment variable

/V DOES NOT WORK
=====================================================

Early in 1996, reports began trickling in of users having difficulty with Fdate's /V feature (setting the value of an environment variable) when running under Windows NT. To make a long story short, in many cases, Fdate's /V feature doesn't work under Windows NT. Unfortunately, this situation cannot be corrected. Microsoft has never made it easy to access the environment programmatically, and the situation has become worse in Windows 95 and Windows NT. The situation has become so difficult that TurboPower Software, which markets add-on utilities, has withdrawn support for utilities that change environment variables. Since Fdate uses these utiltities, it is virtually certain that I will never be able to make Fdate's /V feature work under NT, in cases where it does not now work.

This does not mean, however, that Fdate can't be used with NT. What it means is that, when running Fdate under NT, we have to fall back on a more basic method of setting an environment variable. This involves creating a temporary batch file that sets the variable, then running and deleting the batch file. It's primitive, but it works.

CALL A BATCH FILE
=================

The most basic way to put Fdate's output into an environment variable, is to:

In this example, the result will be that the Fdate environment variable is set to today's date, in ccyymmdd format.

You might also want to investigate a utility called XSET. Try:
http://members.tripod.com/~marcstern/xset.htm
or http://www.bigfoot.com/~xset