home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!cs.utexas.edu!qt.cs.utexas.edu!yale.edu!jvnc.net!rutgers!njitgw.njit.edu!hertz.njit.edu!dic5340
- From: dic5340@hertz.njit.edu (David Charlap)
- Newsgroups: comp.os.os2.misc
- Subject: Re: Problems "running" a *.INF file...
- Message-ID: <1993Jan5.205938.28925@njitgw.njit.edu>
- Date: 5 Jan 93 20:59:38 GMT
- References: <1993Jan4.062712.14698@midway.uchicago.edu>
- Sender: news@njit.edu
- Organization: New Jersey Institute of Technology, Newark, N.J.
- Lines: 35
- Nntp-Posting-Host: hertz.njit.edu
-
- In article <1993Jan4.062712.14698@midway.uchicago.edu> pynq@midway.uchicago.edu writes:
- >I d/l'd the OS2YOU.INF file from OS2YOU.ZIP - when I double click on the
- >icon for the file, I get a VIEW.EXE error message, saying "Topic not found."
- >
- >However, when I go to an OS/2 window, and say "view os2you.inf", it
- >seems to work fine - starts up a thread reading the file. Why is this?
-
- A bug in the install program. *.INF files are not associated with
- VIEW.EXE. Instead, they're associated with the "Command Reference"
- icon. So the effective command line becomes:
-
- VIEW CMDREF.INF OS2YOU.INF
-
- Since OS2YOU.INF isn't a topic in CMDREF.INF, you get the error.
-
- Do this to correct the problem:
-
- 1) Open the Command Reference settings. Go to the associations page
- and remove the association with *.INF files.
-
- 2) Go to OS/2 System -> System -> Migrate applications. Choose OS/2
- programs. Migrate VIEW.EXE (it's in C:\OS2). Put the VIEW.EXE
- icon anywhere you want. Rename it anything you want.
-
- 3) Open the VIEW.EXE's settings. Create an association with *.INF
- files.
-
- Now, your info files should be associated with VIEW.EXE instead of
- with the command reference. All should be well now.
-
- --
- |) David Charlap | .signature confiscated by FBI due to
- /|_ dic5340@hertz.njit.edu | an ongoing investigation into the
- ((|,) | source of these .signature virusses
- ~|~
-