Cougar Mountain Software Support-cms2TS NovellHelp

Over the last few years network operating systems and applications have increased a greatly in size and complexity while striving to meet the demands of the modern business world. Very often installers and administrators are so busy assembling and integrating operating systems and application software to meet these demands and answering questions concerning the capability of the hardware and software that they make errors in the basic set-up or neglect it altogether assuming that it is running so it should be ok. These seemingly minor omissions can later manifest themselves in the form of minor glitches to major server crashes. If you are experiencing problems with your network the very first thing you should do is to recheck the basic set-up. We have found the best way is to use the following outline to create a check list for each part of your network.

I.	All hardware specifications are adequate for the application.
	A.	Servers and workstations.
		1.	Sufficient memory installed.
		2.	Correct interface hardware.
		3.	Correct peripherals and attachments.
		4.	New software may not respond properly on older hardware.
	B.	NICs, Repeaters, Cabling.
		1.	Connected correctly.
		2.	Latest and compatible drivers installed.
II.	All hardware and software configured properly.
	A.	Memory configurations correct for operating system and applications.
	B.	Conflicts with IRQ, DMA, and memory addresses.
		1.	Verify IRQ for every device.
			a.	Video and sound cards may use IRQs normally used elsewhere.
			b.	Check any other add-on devices (scanners etc.).
		2.	Verify no conflicting DMA usage.
			a.	Sound cards and scanners may use DMA.
		3.	Verify memory address and size for each device.
			a.	Be especially wary of any dynamic memory managers or other devices which allocate memory overlapping memory address already set by other means.
III.	Config.sys, Config.dos, Autoexec.bat, Autoexec.dos.
	A.	Verify each statement and its position in the file.
		1.	Check for errors on boot-up using F8 to step through.
		2.	Double check memory management commands.
IV.	Registry, Win.ini, System.ini.
	A.	These are very difficult to check and best done only by an expert. If you feel that you have the knowledge proceed very cautiously, make a backup, and change only one command before re-booting & re-checking everything.
	B.	Verify each statement and its position in the file.
V.	Software drivers.
	A.	Check that each and every driver is current and compatible with operating system and application software.
VI.	Work Habits of the users.
	A.	Many users trying to launch the same application at the same time.
	B.	A user locking a login file open while answering the phone.

The commands in the config.sys, config.dos, autoexec.bat, autoexec.dos and registry files are probably the most difficult place to spot problems. In the case of the first four the only way to isolate a problem here is to "rem out" the commands (Screen Saver(?), CD-ROM, sound cards, etc.) that are not absolutely necessary for basic operation. Then test each command by adding it back in one line at a time (re-booting after each addition) until the problem is discovered. The registry is quite another matter. In the case of the registry it controls everything in the system and if you change anything at all your system may not re-boot correctly. I cannot stress it too highly that is is a task best left to experts. One change could make reinstallation necessary.

Sound cards and screen savers(?) are a major source of conflicts. In these hints I say screen savers(?) because at this point in technology they are not that necessary for preserving newer monitors and have been proven to cause many, many intermittent problems such as locking a workstation, locking the server and even slowing a server to a standstill when someone made an especially cute complex program available over the network.

As you add more capability and upgrades to your system you multiply the chance of conflicts and errors. Modern systems have so much more capability and so many more applications that we tend to forget that many of these combinations of hardware and software have never been used together on a daily basis. There are virtually thousands of combinations of hardware and software so it is impossible for manufacturers to test their products (especially upgrades that have added new functions) under all conditions. Even if your system has been running smoothly adding or upgrading one application may create a whole new set of problems when your hardware or existing drivers are not completely compatible with the new additions.

1.	Be certain that you really need the new capability. Analyze the functionality of what you have compared to what you will be gaining. If possible get a demonstartion of the new additions using your data. Do not upgrade for the sake of having something newer or because a salesman needs to make a quota.
2.	I cannot emphasize strongly enough that when adding a new application be sure to question everyone, especially the manufacturer of the application, if the combination you are going to use has been thoroughly tested under everyday usage.
3.	Set up a test bed and test every change before actually installing it on your main system. I realize that setting up a test bed takes time, effort and resources but it is time well spent. Once set up it is easily maintained because users aren't constantly changing it and you have a controlled environment to test any changes, new hardware, new applications, new drivers or upgrades. Sometimes even just the installation is not as straight forward as it is supposed to be. It may change some existing configuration and even though it makes a back-up, the ramifications of operating until a problem makes itself apparent can sometimes be very detrimental to daily data collection.
4.	Never, never do more than one major change at a time. Be certain that you have all the necessary driver upgrades for that change and they are correctly installed and configured at that time. Be certain that everything is tested and working correctly before adding the next change. This applies to your test bed as well as your system. After all, trouble-shooting is just isolating the problem.

We sincerely hope this has been helpful to you. We will continue to add to these pages from time to time. We would appreciate any suggestions or comments you may have. If you have a problem you cannot solve and you located in the Long Beach - Los angeles area we would be happy to be of direct assistance. If you are out of the area we have telephone support available.

IConnect NetworX Windows NT & 95 Tips

email us at sales@CougarMtnSupport.com // phone (714) 228-5444.