>
>I'm a beginner in Windows NT, Last few months I've found out that, we are getting continuous error under Event Log, abt, Master Browser is stopped or an election is forced, as SOME computer considers it self a Master Browser. Can you pls explain me the reasons for the same. Is there any problems in our Network.
>

This, usually, isn't a problem but just an annoyance. You should be able to take care of this by going to your Win95 machines' Networking Configuration area (just by right-clicking the Network Neighborhood and then selecting Properties) and then selecting the File and Printer Sharing for Microsoft Networks (under the Configuration Tab) and then selecting Properties. There should be a tab there for Advanced and an entry for "Master Browser" or something similar. The setting (on the right side) should be either "Automatic" or "Disabled". This should let that computer know to not try and be the master browser (and the NT should be).


>Also I've faced a few problems, in one of our DOS based multi-user application , which is not behaving very well for las few months. It suddenly becomes very very slow on even computers with configuration of P200 32 MB ram, and 600K free conventional memory. It becomes slower and slower and suddenly it gives Exception error and we have to close the computer. Once this happens, this happens on all the computers and the only solution is, to turn off all the computers, running that software, and restart again, wait for sometime, and resume your work. This is very frustrating. Can you help me here.
>

I'd have to know alot more about the application in question. If it affects all the computers at the same time equally then I would first look at what that program is doing at the file server level (if that's appropriate to the application). Is it using temporary files? Are all of those files being placed in one location for all computers (like a file share on the file server)? Does the application use some kind of looping (timer or whatever) that keeps consuming memory on the clients and eventually stops everybody at about the same time? That kind of thing. Or the load on the file server (either CPU or harddrive access) might be the problem.

Hope some of this might help

- A Hilton