home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.os.os2.apps
- Path: sparky!uunet!paladin.american.edu!darwin.sura.net!wupost!gumby!destroyer!ubc-cs!newsserver.sfu.ca!sfu.ca!weinkam
- From: weinkam@fraser.sfu.ca (James Lawrence Weinkam)
- Subject: Re: Windows 3.1 virus attacks OS/2 2.0!
- Message-ID: <weinkam.713755112@sfu.ca>
- Sender: news@sfu.ca
- Organization: Simon Fraser University, Burnaby, B.C., Canada
- References: <16712uINN2om@agate.berkeley.edu> <Bsxpx5.Mq9@watserv1.uwaterloo.ca>
- Date: Fri, 14 Aug 1992 01:18:32 GMT
- Lines: 27
-
- dp35@mc1adm.UWaterloo.ca (Greg Moore) writes:
-
- >In article <16712uINN2om@agate.berkeley.edu> boss@soda.berkeley.edu (Brion "Imp" Moss) writes:
- >>
- >> [ not being able to print... ]
-
- >>(oh, and just to prove it farther, I had just printed something out of OS/2
- >>before I shut it down, and installed Windows 3.1. Nothing else could have calused
- >>the problem....)
-
- >I would bet that if he had his path in an order that it would find the
- >SYSTEM.INI file for OS/2 first, that would cause a big problem. Not that
- >I mean he did, but he might have had his OS/2 directory before his Windows
- >Directory in his path statement.
-
- This would not help any. Windows install searchs the whole tree of every
- drive for previous versions of windows. It makes changes to all .ini
- files it finds that belong to a version of windows. Thus even if he
- removed the winos2 directory from his path, windows 3.1 install would
- still find the winos2 .ini files and modify them.
-
- It is simply a case of a stupid install program. It should ask the user
- for permission to change the .ini files in other directories.
-
- Sorry for the flame.
-
- James
-