PDS2@psuvm.psu.edu (Paul D. Shan) (07/24/90)
I the old version of Windows (2.1) If I wanted to associate an extension to a
program, I simply(?) edited the WIN.INI file. In Windows 3.0, this is partly
automated by clicking on "Associate." HOWEVER, I have noticed that it doesn't
work the same as it did in Windows 2.1. My specific example is as follows:
I have a directory called C:\TEMP. It is usually empty. When I get a new
program I put it there to test it out. I also use it for UnZipping files.
In Windows 2.1 the WIN.INI line looked like this:
ZIP=PKUNZIP.PIF -d ^.ZIP C:\TEMP
This would call the PIF file (Which ran in a background window on my 386)
and would attach the paramaters on the end of the command. As a result, all
files and any subdirectories were decompressed into the C:\TEMP directory,
no matter where the ZIP file was located on the hard drive. In Windows 3.0
I tried to set this up by using the Associate command, and it didn't work.
So I edited the WIN.INI file. The line in there looked like the one above.
When I tried to go back to Associate, the "^.ZIP C:\TEMP" portion of the
line was missing. I assume Windows "protects" the user from the inner
workings, which is why the ^.ZIP is cut off, but in the process, the
parameters following the ^.ZIP are also lost. As a result, the files are
not extracted as they should be.
Has anyone else had these problems? If so, how did you fix them?
- -----------------------------------------------------------------------------
Paul Shan | "Music is a shout of foregone conclusions,
PDS2@psuvm.psu.edu | as long as music plays its part"
| - YES, "Our Song", 90125
|---------------------------------------------------
| "Always be nice, until it's time to not be nice."
| - From the movie "Roadhouse"
- -----------------------------------------------------------------------------