rontaylor
asked on
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
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
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
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!