To set classpath or unset classpath? That is the question

Question

I notice that Sun application examples make a point of unsetting the classpath when starting rmiregistry. In Windows they suggest the command:
unset CLASSPATH
but I have found that I get the response:
Bad command or file name
Any suggestions?
However, having said this, I have found it advantageous to having the classpath set when I start the rmiregistry for the following reason:
When I try this sequence of commands, things seem to work pretty simply:
set classpath=c:\javaWork\project
start rmiregistry
java Server
However, if I try it this way, the java command line has to be more complicated:
start rmiregistry
set classpath=c:\javaWork\project
java -Djava.rmi.server.codebase=file:/c:/javaWork/project/ Server
Is there any reason I shouldn't use the first way of going about it? Or a compelling reason for going for the second approach?
Thanks, Rob

Answer 1

Yes, and to reiterate daney's post ...regarding the question in your header... if the rmiregistry can find the classes in the classpath, it will make no attempt to download the stubs to your client. Since it sounds like you are supplying permanent stubs with your client, this will be of no concern to you. However, that is the explanation as to why you keep comimg accross this information in your sources. :-}