We help IT Professionals succeed at work.

We've partnered with Certified Experts, Carl Webster and Richard Faulkner, to bring you two Citrix podcasts. Learn about 2020 trends and get answers to your biggest Citrix questions!Listen Now

x

DOS/Win Client32, VLM 1.21, and Shared WfWG 3.11?

SMPaulsen
SMPaulsen asked
on
Medium Priority
421 Views
Last Modified: 2009-12-16
I manage an installation where a majority of the users start
Windows for Workgroups 3.11 from a shared copy on the network server (SETUP /A, SETUP /N).  All stations on the network were upgraded to use VLM version 1.21, and the shared directory for Windows had been updated with the VLM 1.21 divers.

I began experimenting with Client 32 for DOS/Windows for some stations (Btter memory management, more stable...).  The Client32 install updated drivers in the shared Windows directory again.  Now, I'm having trouble with the stations that are still VLM 1.21.  Everything works perfectly st these stations until the user tries to exit Windows.  After clicking "Ok" to end windows, the station goes into the Black Screen of Death.  A Ctrl-Alt-Del brings up the "Windows has become unstable" Blue Screen of Death, but I can never get back to DOS.

Shouldn't the new client32 drivers be backwards compatible?  Is it possible to run both VLM 1.21 and Client32 DOS/Win in a shared Windows environment?

Thank you in advance ...

Steve Paulsen
Roundabout Theatre Company
Comment
Watch Question

Commented:
How do you have the users windows directories set up? The problem sounds like the client32 over wrote some dlls in the shared windows directory that are the same name but different. There is a way to put all the client files in the users windows directory but you have to manualy copy them there.

Author

Commented:
In response to a question about my setup:

The user's windows directories are installed as a subdir to their home dir:

map root f: sys:\users\<username>
map root w: sys:\users\<username>\win31

The shared install is installed off the root of sys:

map root z: sys:\wfwg311

Yes.  It looks like Client32 for DOS/Win overwrote DLLs that are named the same, but are different enough to be incompatible.  I had expected better behavior from Novell.

I will try to copy the appropriate Client32 files to the user's W: drive, and restore the Z: files to the VLM 1.21 state.  Any further suggestions?

Commented:
You will need to move all client files to all the users windows directories and remove them from the shared directory because you have the shared directory shearch mapped. This way a client of one type won't load the files of the wrong type from the shared directory no matter how hard they try. Yes the files should load first from the default directory but stanger things have happened. <grin>
Commented:
On one of my networks I have installed the 32bit  client for win, and I am running shared windows with the user's bits of windows in their own user directories with no problems. ( except that everyone must be out of windows when you do the install for the client32),  However the 'black screen of death' can be cured sometimes by applying 'WINUPx' from the novell web site.  It has all the updated VLM and NETX drivers for windows 3.x.  I am using WINUP9 which I think is the current version.

Not the solution you were looking for? Getting a personalized solution is easy.

Ask the Experts

Author

Commented:
I've not yet had a chance to implement paulmew's answer, but it sounds right.  Thanks!

Author

Commented:
I've not yet had a chance to implement paulmew's answer, but it sounds right.  Thanks!
Access more of Experts Exchange with a free account
Thanks for using Experts Exchange.

Create a free account to continue.

Limited access with a free account allows you to:

  • View three pieces of content (articles, solutions, posts, and videos)
  • Ask the experts questions (counted toward content limit)
  • Customize your dashboard and profile

*This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

OR

Please enter a first name

Please enter a last name

8+ characters (letters, numbers, and a symbol)

By clicking, you agree to the Terms of Use and Privacy Policy.