DOS Client Click Here in the middle of this page
Top I have been in correspondence with Rick Klemetson concerning networking the Vernal, Utah FHC. I was the computer technician for the Uintah School District and have extensive background in networking. Since he had assisted several other FHCs in setting up their networks, I asked him if there was anything special I needed to be aware of. After receiving his reply, I believe I have partial solutions to the problems faced by the networked FHC. He suggested I post this information and some other correspondence to the list so here goes.....
I asked Rick:
What pitfalls should I be watching out for in this project?
My biggest problem is people turning the workstations on before the server and telling it not to attach to the server drives in the future. Let me know if you have a way to force it to attach like a Novell workstation would.
These solutions work for Windows 95/98 - I'm looking for a DOS solution now...
You can use policy editor to force the user to login to a network. They have no local access if they have no network access. This way if the server is not running, the user cannot use the local system. Next, we use Tweakui to automate the login process. Now the user doesn't have the chance to make changes to the login. This is exactly what we want. Both of these programs are free from Microsoft.
Installing Policy Editor:
System Policy Editor
Use this tool to create or edit system policies to standardize the appearance and capabilities of Windows 95 for a single user, a group of users, or the entire network.
You can create new policy files, or use the sample policy files included in the ADMIN\RESKIT\SAMPLES\POLICIES folder on the Windows 95 CD.
To install this tool on your local hard disk, or to install support for group policies, use the Add/Remove Programs option in Control Panel, select the Windows Setup tab, click the Have Disk button, and install from the ADMIN\APPTOOLS\POLEDIT directory on the Windows 95 CD.
For more information about system policies and System Policy Editor, see those topics in the Windows 95 Resource Kit (WIN95RK.HLP).
Running System Policy Editor:
The site below explains exactly how to do what we want:
BTW-Policy editor will allow you to remove the desktop icons, keep users from changing the backgrounds, etc. After using it for a time, you will see what I mean.
To download and install Tweakui follow the directions on the link below:
Once installed, open control panels- double click on Tweakui - click on the network tab. enter the user name and password, check automatic login. Now your set.
Next step is to convince the FHC staff that the server should _never_ be turned off unless it is totally frozen (preferably by the Computer Specialist - threats of being smitten with fire and brimstone might be of help here).
Many computer specialists are not aware that you can include older DOS machines in a Windows 95 network environment. Microsoft offers free client software for doing this. (Who says Bill's not a nice guy!)
Below is some information that can explain better than I ever could.
The information below is from the Windows 95-- Easy Networking FAQ by Alan Zisman (c) 1997
Can I connect to other operating systems?
Simple Windows 95 networks as described can easily include
machines running the following networks:
-- Windows NT
-- Windows for Workgroups
-- OS/2 Warp Connect 3.0 or Warp 4.0 (Merlin)
Microsoft has also made available a free DOS-level add-on, allowing machines running DOS or Win 3.1 to connect to such networks. To install this add on, you need to get files from Microsoft's FTP site (unfortunately, these are not readily identified on Microsoft's Web site).
According to Bruce Feuchuk:
Get the DOS Workgroup Client from ftp.microsoft.com, in directory /bussys/clients/MSCLIENT - (this path works fine - gwc). Get both files. They're self-extractors. Extract all the files (to a temporary folder-gwc), run SETUP. Now your DOS machine is a client on your Windows P-t-P (peer-to-peer) network.
(This is now on our site - Click Here for WG1049.EXE)
Go back to ftp.microsoft.com, and get WG1049.EXE, from /softlib/mslfiles. It's another self-extractor. Run it in your /NET directory, and let it overwrite whatever it wants to. (This enables your DOS machine to share its files -- az) - (I don't see this as necessary in our situation...gwc)
Make the obvious changes to /NET/SYSTEM.INI. Some fine tuning is required (like "Computer Name"; "Network Name"; IO Base and Interrupt). And make sure you set the 'filesharing' and 'printsharing' "YES". Also I've always used NO passwords (simplier this way).
Now you have a DOS based client/server that can work on a Win95 network.
One bit of info I would like to share - at the school district where I worked we had about 1500 networked machines. I have used every network card on the market. I have found the easiest to get going with a variety of applications is the most basic, plain-vanilla, el-cheapo, generic, ISA network card. I have had nothing but problems running "premium" cards - Intel, 3com, etc. They seem to work fine if the whole network uses the company's hardware, but fail miserably when used with anything else. This is especially true of software applications. If it's from Microsoft, the cards will probably work. Any other kind of program though and you likely will not see the card or the network. PCI cards are often especially troublesome. If an Intel or 3com installation fails on the first try, many times you will have to delete the Windows directory, reinstall Windows with the card in place.
Again, I stick with inexpensive generic ISA cards - cheaper by a factor of 8 and far fewer headaches.
BTW - off topic, I am seeking employment as computer tech. If anyone knows of anything...
I hope these solutions are of some help. If I can answer any questions, please do not hesitate to contact me.
Gary W. Clark | Researching the Following Surnames:
100 N 1350 APT 4 | CLARK - O'KELLEY - DRAPER - WOOLLEY
VERNAL UT 84078-3177 | SOWARDS - HILDERBRANDT - BERNER
(435) 789-7951 | WALKER - KIMES - CHILDS - BEHRMANN
email@example.com | http://familytree.ourfamily.com