home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!munnari.oz.au!sgiblab!swrinde!gatech!udel!bogus.sura.net!howland.reston.ans.net!sol.ctr.columbia.edu!emory!ogicse!flop.ENGR.ORST.EDU!xanth.CS.ORST.EDU!villalj
- From: villalj@xanth.CS.ORST.EDU (John Villalovos)
- Newsgroups: comp.sys.novell
- Subject: Re: Windows & Novell 3.11 (getting it working)
- Message-ID: <1k4keuINN10i@flop.ENGR.ORST.EDU>
- Date: 27 Jan 93 00:19:42 GMT
- Article-I.D.: flop.1k4keuINN10i
- References: <1993Jan26.200307.18587@black.ox.ac.uk>
- Organization: Oregon State University
- Lines: 27
- NNTP-Posting-Host: xanth.cs.orst.edu
-
- In article <1993Jan26.200307.18587@black.ox.ac.uk> wa95003@oxford.ac.uk (Martin J Bligh) writes:
- >I am trying to get windows running under Novell 3.11
- >
- >(1) Different machines on the net have different video cards, etc. I
- >thus need to autodetect the chipset (which I will probably write a
- >small program in C to do), and then autoconfigure the .ini files
- >apropriately. Any user should be able to use any workstation, and I
- >don't want to end up having about 3 sets of windows files for each
- >user, one for each chipset.
- >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:
-
- Just thought I'd let you know. The information on the video cards is kept
- in the system.ini file. The SYSTEM.INI file holds all the information about
- the hardware. So you will need to have a separate SYSTEM.INI file for each
- unique configuration of computers that you have. You could either keep a copy
- of this file on the local hard drive or put it in a network directory. I use
- the second method. To do that you will need to be able to uniquely identify
- your computer. If you can't figure out that part feel free to write me back.
-
- Later,
- --
- John Villalovos
- Certified Netware Engineer
- villalj@xanth.cs.orst.edu
- (503) 753-7883
-