Solved

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

Posted on 1997-02-28
6
373 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
0
Comment
Question by:SMPaulsen
  • 3
  • 2
6 Comments
 
LVL 1

Expert Comment

by:garyh
ID: 1589347
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.
0
 

Author Comment

by:SMPaulsen
ID: 1589348
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?
0
 
LVL 1

Expert Comment

by:garyh
ID: 1589349
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>
0
3 Use Cases for Connected Systems

Our Dev teams are like yours. They’re continually cranking out code for new features/bugs fixes, testing, deploying, testing some more, responding to production monitoring events and more. It’s complex. So, we thought you’d like to see what’s working for us.

 

Accepted Solution

by:
paulmew earned 100 total points
ID: 1589350
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.
0
 

Author Comment

by:SMPaulsen
ID: 1589351
I've not yet had a chance to implement paulmew's answer, but it sounds right.  Thanks!
0
 

Author Comment

by:SMPaulsen
ID: 1589352
I've not yet had a chance to implement paulmew's answer, but it sounds right.  Thanks!
0

Featured Post

Complete VMware vSphere® ESX(i) & Hyper-V Backup

Capture your entire system, including the host, with patented disk imaging integrated with VMware VADP / Microsoft VSS and RCT. RTOs is as low as 15 seconds with Acronis Active Restore™. You can enjoy unlimited P2V/V2V migrations from any source (even from a different hypervisor)

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

Title # Comments Views Activity
iFolder NetDrive with iFolder 3.8 4 966
Imanager Workstation On Windows 7 - Works Partially 7 815
Novell 4.1 data 6 321
Novell Netware time zone 7 687
This problem is more common than not and I will show you some things to check to solve this problem.
As a business owner, there are many things that keep you up at night. Profit margins, employee retention, human resource protocols, whether your product or service will remain competitive. When you own or manage a technology company that operates la…
Microsoft Active Directory, the widely used IT infrastructure, is known for its high risk of credential theft. The best way to test your Active Directory’s vulnerabilities to pass-the-ticket, pass-the-hash, privilege escalation, and malware attacks …
A short tutorial showing how to set up an email signature in Outlook on the Web (previously known as OWA). For free email signatures designs, visit https://www.mail-signatures.com/articles/signature-templates/?sts=6651 If you want to manage em…

803 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question