Re: 'NET' is not recognized as a command

[Bill Stewart]

I have seen a few cases where it all looks OK, but the valuname PATH has
mysteriously become Tpye REG_SZ (and therefore the vars. are not expanded
correctly). I have no idea how it happens exactly though. Possibly a
bad installer that reads, deletes, re-creates the value (incorrectly).

Mark,

Thanks for the information. That's what I appreciate about our community--
although this hasn't happened to me, it is helpful to pass along. I will
update my web page with this, with instructions to change the registry
entry to a REG_EXPAND_SZ. I bet you're right about the cause, though.

<side story>At my last job, a sys admin was convinced that a installation
routine was writing binary data to a certain registry key. The problem was
that the tracking utility he was using wasn't capable of discerning that
what was really happening was that the installer was adding a string to a
REG_MULTI_SZ registry value. There's no point to this story, really, other
than it has to do with differing registry value types.</side story>