VOGONS


.PIF problem

Topic actions

First post, by Nintendork

User metadata

Hey, whenever I try opening a certain program with VDMSound, I get thie message:

C:\DOCUME~1\Owner\LOCALS~1\Temp\~xxxxxxx.PIF
Invalid program file name, please check your pif file. Choose 'Close' to terminate the application.

Pif file? What the HELL is a pif file? Anyway, the reason there are a lot of xs is because it's always some random letter/number combination when I open it. I've tried many things, but I just can't get it to work! đŸ˜” Can someone please help me?

Reply 1 of 8, by Nintendork

User metadata

Sorry for the double-post, but in the part with all the xs, replace the first four with "VLP6".

Reply 2 of 8, by collector

User metadata
Rank l33t
Rank
l33t

This used to happen with an earlier version of Launchpad. What version of VDMS and Lunchpad are you using? If you haven't installed the latest version, install the 2.1.0 PUBLIC BETA: VDMSound 2.1.0 PUBLIC BETA

The Sierra Help Pages -- New Sierra Game Installers -- Sierra Game Patches -- New Non-Sierra Game Installers

Reply 3 of 8, by Guest

User metadata

I knew this was going to be the first assumption. YES, I DO HAVE THE NEWEST VERSION!!!

Reply 5 of 8, by Nintendork

User metadata

Well, the program is actually MIDI2BAM (if you mean game.exe as in Hamster Republic) and I'd like to be able to test them instead of adding a music and going all the way into my game just to see if it works/got the right file. Would simplifying it be the only way? 😱

Reply 7 of 8, by Guest

User metadata

I have exactly the same problem. I'm using 2.1.0 and moved games to c:\gamename, still the program calls for some unknown .pif file.
The exact patch to file in question is c:\documents and settings\administrator\local settings\temp\
filename itself varies everytime and generally looks like ~vlp####.pif, where #### is some numbers and letters.
I have XP professional SP1.
Previous versions of VDMSound (i.e. w/o launchpad) worked fine.

Reply 8 of 8, by vladr

User metadata
Rank Oldbie
Rank
Oldbie

If you're running WInXP then it (Windows) fucked up during installation of VDMSound. Not in a persistent way thankfully, reboot will normally bring everything back to... normal. 😜