confguration problems?

[avionbay]

Lately I (1) installed for evaluation the 6.01 version and (2) experience terrible slowdown waiting for applications to "start doing something" (i.e., it's like they are waiting for something before they start doing what they should, but once they start - they do it on normal speed).

I ran Symantec Win Doctor to check my system and found a lot of shortcut problems. Now, what's interesting is that some of them are with Total Commander helpers PIFs (e.g. pkunzip, rar, lha etc.) and are invalid. For example, the error message would read: "The shortcut C:\Windows\\PKUNZIP.PIF is invalid. Reason: The pathname PKUNZIP.EXE used by this shortcut is wrong". Notice the double backslash between Widnows and PKUNZIP. Also, when going to the C:\Windows, there are no such pif files there!

[Clo]

Lately I (1) installed for evaluation the 6.01 version and (2) experience terrible slowdown waiting for applications to "start doing something" (i.e., it's like they are waiting for something before they start doing what they should, but once they start - they do it on normal speed).

I ran Symantec Win Doctor to check my system and found a lot of shortcut problems. Now, what's interesting is that some of them are with Total Commander helpers PIFs (e.g. pkunzip, rar, lha etc.) and are invalid. For example, the error message would read: "The shortcut C:\Windows\\PKUNZIP.PIF is invalid. Reason: The pathname PKUNZIP.EXE used by this shortcut is wrong". Notice the double backslash between Widnows and PKUNZIP. Also, when going to the C:\Windows, there are no such pif files there!

Hi!
That has a virus flavour!
You might scan the whole HD with a good AV...
The *.pif files must really exist, TC installs them in <windows>
I never noticed any problem about these *.pif files under Win9x...
Glad to hear more,
best regards,
Clo

[avionbay]

Thank you for the answer.

I'm reasonably sure there is no virus.

I'm also reasonaby sure there are no PIF files. When searching fro *.pif under c:\windows, tc onlyfound NOCLOSE.PIF and _default.pif. Also, I'm very suspicious because the message is "The shortcut C:\Windows\\PKUNZIP.PIF is invalid." - notice the double slash - it's not "Windows\PKUNZIP.PIF" but "Windows\\PKUNZIP.PIF".

This both says to me that someone has tried to install into an incorrect path P, and has written somewhere a "notice" like : "there is a pif file named pkunzip in P". Then WinDoctor finds this notice, tries to locate the PIF, can't find it (as P is invalid) and complains.

Now, possibly TC succeeds in installing the PIFs to most user's directories, but fails with MY file system. Why?

[Clo]

Thank you for the answer.

I'm reasonably sure there is no virus.

I'm also reasonaby sure there are no PIF files. When searching fro *.pif under c:\windows, tc onlyfound NOCLOSE.PIF and _default.pif. Also, I'm very suspicious because the message is "The shortcut C:\Windows\\PKUNZIP.PIF is invalid." - notice the double slash - it's not "Windows\PKUNZIP.PIF" but "Windows\\PKUNZIP.PIF".

This both says to me that someone has tried to install into an incorrect path P, and has written somewhere a "notice" like : "there is a pif file named pkunzip in P". Then WinDoctor finds this notice, tries to locate the PIF, can't find it (as P is invalid) and complains.

Now, possibly TC succeeds in installing the PIFs to most user's directories, but fails with MY file system. Why?

Hello!
¤ Please, watch this:
http://perso.wanadoo.fr/charries/relais/PIFs-in-win.png
¤ I've the PIFs files under Win98SE... They are in the TC archive, and normally copied into <windows> dir.
¤ You can verify your archive, open it by Ctrl+Page Down, then 2-click on the Install.cab inside. it contains a sub-dir <Windows> where are these awful PIFs!
Did you download this TC archive from the TC site? Sometimes, certain archives from mirror-servers (or CDs...) are "patched" or damaged.
Glad to hear more about this,
Friendly,
Claude
Clo

[Premium]

Avionbay is right. Norton WinDoctor is saying that there is a problem with these .pif files. And this problem exists since the first version of Norton WinDoctor years ago. Could it be a bug in Norton WinDoctor?

[avionbay]

Download size 1,473,856, December 24 2003.

Windows XP

[ghisler(Author)]

These PIF files cause these packers to close after packing. No path is stored in the PIF files, so they work with the packers installed anywhere on the system - or not yet installed at all. WinDoctor complains because it doesn't find the programs mentioned in the PIFs, but these are really only necessary when you want to pack with them...