home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.sys.novell
- Path: sparky!uunet!digex.com!intercon!udel!news.udel.edu!bach.udel.edu!mulford
- From: mulford@bach.udel.edu (George Mulford)
- Subject: Re: Windows & Novell 3.11 (getting it working)
- Message-ID: <C1Iy0M.5rq@news.udel.edu>
- Sender: usenet@news.udel.edu
- Nntp-Posting-Host: bach.udel.edu
- Organization: University of Delaware
- References: <1993Jan26.200307.18587@black.ox.ac.uk>
- Date: Wed, 27 Jan 1993 18:00:21 GMT
- Lines: 33
-
- In article <1993Jan26.200307.18587@black.ox.ac.uk> wa95003@oxford.ac.uk (Martin J Bligh) writes:
- ;
- ; The only solution that I can think of is to automatically build
- ; win.ini, etc. when the user goes into windows. This would involve
- ; assembling from 3 bits:
- ;
-
- Why not save the three or four configurations in three or four
- subdirectories and use an environment variable to point to them? What we
- do is something like this (I'm winging this...but you get the point):
-
- in the system login script you have a big IF statement that generates a
- station number from your ethernet card number (which is P_STATION):
-
- if "%P_STATION"="0325C3EFDA" then dos set station="01"
- ...lots more if statements here
-
- Then you do
-
- map j:=myserver/sys:wininits
- #copy j:%station%\*.* c:\windows3.1
-
- You document all this in a big spreadsheet, and if you're really cool,
- you write a spreadsheet macro to generate the "if" statements from the
- spreadsheet, and just use Novell's "include" command to bring the file so
- generated into your login file. It's not pretty, but it beats writing code
- that will be obsolete when Windows goes into a new version.
-
- Don't flame me...I didn't make this up, but I copied it.
- --
-
- George W. Mulford mulford@brahms.udel.edu
- Instructional Technology Center University of Delaware
-