Incorrect version of dos with win95B

Server: Netware 3.12
Clients:
  Windows 95
  Windows 95b
  WFW 3.11
  DOS

Hi! I have a small network, 25 users.  8 users use dos, 2 users use Windows 3.11, 15 users using Windows 95.  The last computer that I added has Windows 95b, the second release of Windows 95.  In all the previous cases I created a directory in the 'sys:public' directory and copied the command.com from which ever dos version the user had.
        (IE V5.00, V6.00, V6.21, V6.22)
When I started using Windows 95 I copied the command.com to 'SYS: root directory' and all my dos window sessions worked.  Now with the Windows 95b, when I run dos applications or the dos windows, all return "Incorrect version of dos."  I put the first version command.com of Windows 95 in a directory called 'sys:\public\V7.00'.  But the 'b' version also looks here as '%OS_VERSION' returns V7.00 from both the
first and second release of Windows 95. In the login script I added an IF-Then-Else to check for the one LOGIN_NAME with the Win95B version.  What is the right way to handle this problem?
Ron
rontaylorAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

cwilliCommented:
There really isn't a need to change your comspec to point to the 3.12 server.  As long as all of your MAP commands are MAP INS in the Netware login script, the original Win95 path (without an autoexec.bat path statement) will point you to the local command.com.  
We're running over 200 Windows 95 this way with no problems.  We do use the %OS_VERSION in the login script (with IF-THEN-ELSE logic) to split the way the script is run based on the workstation OS.

Let me know if this helps.

Curtis
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
netkinexCommented:
The way you seem to want to handle this is rather sweeping and
I could see possible problems for some involved login scripts
and besides the fact is the information is slightly incorect
if you test for "OS_VERSION"=400.950 AND\OR 400.950a with the
early versions of 95 {look at the results 'ver' at the dos
prompt returns} and for "OS_VERSION"=400.1111 for the OSRX
family [WIN95B] you can enter info as per mfgr spec* [the right way instead of a work around!

*ie: place the appropriate command.com in the appropriate subdirectory and the if-then test done as above will allow
comspec to work just fine the RIGHT way!  

0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Novell Netware

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.