Just what PIF files do you think will be restored using SFC? For sure, I'd say there is more to this problem than has been reported, but PIF files are basically shortcuts - the actual command should still be accessible. While it may be advisable to use SFC to try and determine what the real problem is, indiscriminate use of that tool can lead to a whole new set of difficulties. Why don't they make computers that will do what we think we want them to do?

0

Thanks for your continued responses "Humbug". (And the website was a needed laugh too.) I have the latest Virus and Spyware detection/removal tools installed and current. I run them regularly as well as manually performing other "maintenance" like defrag etc. I also maintain tight security and am extremely careful while on-line. (eg. all ports are closed OR closely monitored.) Bordering on paranoia, I also have no instances on my system of my real name or location, and for any communications between unknown parties I have a third party e-mail account.(through lycos.com) I know that I am only missing the .pif files because while I was cleaning up unecessary (and dated) .log files, .txt files, .000 files, .001 files, etc. etc. I noticed that I had over 200+ of those .pif files. I deleted a few and rebooted the system to see if there were any undesirable effects of the actions. After trying out a few of my more commonly used programs (simple games, Winamp, Office apps.) and finding that they were all working I erroneously figured that I didn't need those pesky files either. So let me be the first to admit to one and all that I WAS WRONG. It seems that I deleted more than just the ones that were 0 Kb in size and unused. And now most of the slightly more complicated usages of my machine can't be done. They keep returning me the aforementioned "cannot find xxxxxxxx.pif" errors As for "mmmmmmm"'s comments... I also left my Windows CD at the previously mentioned Mother In-Law's (along with a whole host of others when doing a complete system install a while back.) so I don't have it to fall back on. My "Boot Disk" floppy is also there. I keep all my installation software in one "bag" and forgot to bring it home after a visit that went much too late. (She DL'd a virus that wiped out her partitions then she installed a new printer AND THEN she wanted me to recover lost data files and wipe the HD for a "fresh" install of everything the way it was before it was messed up. Ugh.) And as I have already worked a full day, done some last minute shopping, wrapped the gifts for family, and I'm working on dinner, I'm not sure what your abbreviation SFC stands for. "Some Fargin' Chump" comes to mind, but that probably ain't what you're saying. Although I would definitely have a hard time denying it at this time. So...any other suggestions/assistance ?

0

SFC is the System File Checker, which can be used to scan for and replace altered Windows files, or to extract individual files from the CD or its equivalent. Ok - a compromised machine was a bit of a stretch, but not impossible. I gather you deleted the files 'permanently' rather than to the Bin? Can you create a new shortcut to MS-DOS by r-clicking a blank part of the desktop and use c:\windows\command.com as the program? Can you open the 'run' dialog and enter 'command' there to launch the MS-DOS prompt? As stated, PIF files are not themselves programs. I'm still not completely clear on what you're doing to receive the error message. Also as suggested, removing those files would not gain much disk space to speak of - unless your drive is using the old FAT16 file system. Why don't they make computers that will do what we think we want them to do?

0

Does the error message take the form of: Windows cannot find MS-DOS Prompt.pif. This program is needed for opening files of type "Shortcut to MS-DOS Program". Why don't they make computers that will do what we think we want them to do?

0

When I try to use "Run" and command I get a window popping up that says : Windows cannot find command.pif. This program is needed for opening files of type `Shortcut to MS-DOS Program'. Location of command.pif: (with the entry field below it as : ) C:\ When I use the "Find" & "Files or Folders" to look for any of the files that windows can't find of course they aren't on the root drive because some num-nuts (me) deleted them. As far as removing the `little' files goes... I just don't like having hundreds af useless little files using a minimum of 4 Kb each of space. I also remove redundant short-cuts, never used web links, empty folders etc. A habit I was forced to adopt when I only had a 4GB partitioned HD and needed about 40GB to get by. (I have a LOT of music and video files that hog up HD space.) Now I'm up to a 20GB partitioned for Root Drive, Games, & Archives/Misc. AND a 40 GB split in half for Music and Video. Total available `free' space across all the `drives' is about 2.5 GB. And as I am actively participating in filesharing while attempting to DL a few movies, I am usually "shoehorning" files around to make space available for those large DL's to complete before burning to CD. I don't install or un-install software very often but I have been running this system for about 2 years since the original install of the OS and some hardware changes coupled with a few games and such have led to quite a few `artifacts' in the registry and other associated files. Then there are the temp files created automatically when using other programs or trying out new options in existing programs and the resultant log files, etc. etc. One thing I have learned over the years is how fast a Windows OS creates clutter and doesn't manage to clean up after itself. And as Microsoft doesn't want anybody to know too much about the issues of their OS's it is hard to know exactly everything that is or isn't vital to the smooth operation of an individuals system with their own unique assortment of hardware & software installations. So often while sitting here enjoying music in the evenings I take an opportunity to "check things out" and clean things up while poking around my machine inspecting for unwanted or unexpected activity. Once in a while I try out something "new" and even rarer I find out a very important lesson. (Like NOW !) So that's my story...believe it or not, in a simplified and shortened form. I still think that a simple replacement of the .pif files would go a long way to remedy my situation. At least the primary or main ones that would allow me to start making the others. Then I could start working on the next set of screw-ups I make...

0

This may or may not be premature but I do tend to agree with "still think that a simple replacement of the .pif files would go a long way to remedy my situation." c:\windows\options\cabs\win98\setup.exe will do an "over the top" install of Win98. You won't lose any settings or programs but, please understand; if you have other problems, they will also carry over to the reinstall. As long as the above directory (folder) does in fact exist, it makes no difference if you use it from a DOS prompt or from within Windows. Skip

0

"I just don't like having hundreds af useless little files" Well, if that makes you happy, fine - but the gains are negligible and the downside should be apparent. You might have a look here at Micro$oft's take on that general error message. Can you not just recreate the MS-DOS Prompt.pif, as described previously? Just as an experiment, I deleted all 4 copies from my system, and dosprmpt.pif as well. Didn't seem to hurt anything. Rebooted. Ran 'command' from the 'run' dialog, got a DOS prompt. As well, 'command.pif' was created automatically. Forgive me if I seem dense or stubborn on this, I'm just trying to make what you're reporting mesh with my understanding of things. Why don't they make computers that will do what we think we want them to do?

0

Aaahh, "Humbug" It seems you are only scratching the surface of my incompitence. I seem to have deleted ALL .pif files. That includes all the other commands as well. I have a nice folder in the Windows directory labelled PIF. Inside it is a whole lot of empty. Nothing. Nada. Zippo. Showing signs of my IQ concerning this. As far as the deleting of the 4Kb files...back when I only had .92 GB partition for my Root Drive getting rid of a few hundred of those 4Kb files freed up a remarkable portion of the available space and it's a habit that I keep...seeing how I am sitting here anyways. 400-800 Kb was a lot of document files or jpeg images that didn't need to be deleted (or backed up for the lazy of us.) And with what I've said so far, do you really think I would have kept a bunch of HUGE .cab files on the HD when I've got them on the CD anyways ? Think it through now...do I really seem to be that smart ? But getting back to it all... I guess I'm looking to get my original installation cd back (with alll the others) and copy the .pif files while at it. Seeing how I'm going to be at the In-Laws tomorrow for Dinner, it'll give me a darn good reason to be playing around on her computer while a buch of no-good so and so's strain to be friendly to each other.(Why do they do that ?!?) Thank for your input and have a happy Holiday. (if you're of that particular notion.) BTW I will be checking back here periodically for the next few hours just in case someone gets a real brainstorm.

0

Just checked the Micrsoft link you posted and the first three relate to me. When you try to start a command prompt in Windows, or restart your computer in MS-DOS mode, or start an MS-DOS-based program, you may receive one or more of the following error messages: • Windows cannot find MS-DOS Prompt.pif. This program is needed for opening files of type "Shortcut to MS-DOS Program". • The object that "C:\WINDOWS\Desktop\MS-DOS Prompt.pif" refers to has been moved or is inaccessible • Windows cannot find Command.com. This program is needed for opening files of type "MS-DOS Application". Yup. That's me all right. Alas...the proposed fix requires the install CD. Can pick it up and copy the files at the same time. Guess we got it right. So maybe I'm not a complete idiot. (Some parts are missing...) Just be forewarned to leave the cleaning up of unknown files to when your totally awake and not at the end of a 20+ hour day. Thank again everybody.

0

"Program Information Files (PIF) tell Windows how to handle non-Windows applications.) It’s been replaced by a property sheet, which describes an object’s characteristics under Win95. To set a program’s properties, right-click its icon, and the context, or pop-up menu, will appear. To set Properties for the DOS prompt, left-click the Start button and Programs, then double left-click the DOS Prompt icon. Right-click the DOS prompt window and left-click the Properties menu option to see the tabbed pages of program settings." The majority of PIF files on my machines were not created by installing Windows, but were formed automatically whenever I'd launch a DOS application from Explorer. A few were included as part of the install package for applications. I have a 'PIF' folder too - it contains 2 items, the PIF for CVT.exe (FAT32 converter), created upon installation, and one for memmaker, created when I ran an instance of that DOS program. I wouldn't miss either one, but launching the executables would (should) recreate the PIFs Whatever's going on with your machine should not, to my understanding, have anything to do with missing PIFs. As far as keeping a tidy hard drive - sure, old habits die hard, and keeping the root clean on a FAT16 drive (especially a large one) was pretty important. It's still a good idea, organization-wise, but hardly critical. 800K is barely a drop in the bucket, even on a "mere" 4Gb drive. Having the good fortune or the foresight to have the Win98 CAB files backed up on the drive has a few advantages - it's only about 130Mb (roughly 3%) and is handier than having to slap in the disc when needed (or when it's unavailable) {pauses to read new posting} Yep - if that is the case, you'll need to restore those files from the CD or else copy from another 98 machine, preferably of the same edition of Windows. Let us know how you make out. Why don't they make computers that will do what we think we want them to do?

0

Hi Shorty, Like jboy, I think something else is going on. I'm running w2k and it creates PIFs as DOS apps are used. I got a fresh copy for you out of the 98se CAB51 and put it here: http://www.Golden-Triangle.com/DOSPRMPT.PIF That's your "stocking stuffer." Let us know. M2 Mechanix2@Golden-Triangle.com

0

Well, I am curious about this one - it would have been nice if the poster had tried creating the shortcut himself. If the cause is a missing or damaged Winoa386.mod or Vgafull.3gr file, that'd be good to know for future reference - sure as heck wouldn't have thought of that on my own ; ) Why don't they make computers that will do what we think we want them to do?

0

jboy, As Dr. McCoy says to Capt. Kirk, "It's worse tahn that, Jim." I'd never heard of those files. Somebody get a toe tag ready for me. M2 Mechanix2@Golden-Triangle.com

0

Anyone thought of looking for command.com file? May be in root directory, windows, windows\command or windows\command\ebd folder(s). Search your drive for this file and make a shortcut pointing to it.

0

Rick, Good point, but it's hard to imagine it would do anything without a viable command.com; like not even boot. M2 Mechanix2@Golden-Triangle.com

0

Yep, you would assume it is using the command.com in the root directory to boot. ShortyInCanada just has to know how to find his command.com file(s) and create shortcut to point to one of them.

0

I don't think it's quite that simple - and, as you know, the system won't do much without c:\command.com It had occurred to me that maybe c:\windows\command.com is missing, since c:\windows is on the default PATH, whereas the root is not. I'm not sure if that would generate the same errors though. Why don't they make computers that will do what we think we want them to do?

0

"When I try to use "Run" and command I get a window popping up that says :" It sounds like you have either deleted your C:\Windows\Command.com or your "PATH" variable is now upset. Go to C:\Windows and locate COMMAND.com Right click on it and select Open. Type in PATH to see what it is showing. Mine shows PATH=C:\WINDOWS;C:\WINDOWS\COMMAND I just extracted all .pif files (*.pif) from the Win98SE CD (Win98 folder) and there were a total of 9 files: LMSCRIPT PIF SCANREG PIF CTLG95 PIF CTLGNT PIF CVT PIF DOSMODE PIF DOSPRMPT PIF EMS_XMS PIF EXTRACT PIF Prior to doing the above I used Find Files and Folders to locate all .pif files on my C:\ drive and in comparing that list to the above I found that only DOSPRMPT PIF was already in C:\Windows and LMSCRIPT PIF was already in C:\Windows\System but is it named "Windows NT Logon Script". So, Mechanix2Go has supplied that single .pif for you at http://www.Golden-Triangle.com/DOSPRMPT.PIF Placing it into C:\Windows will have yours the same as mine unless you also deleted Command.com. Mine is working. As noted earlier the PIF is simply the file created that stores your parameters of how you run a particular non-Windows program such as it's hot keys and window size and more. It is nothing more that that. Right click and select Properties on the one supplied to see what it contains for the "information" of that program file. It is not a program in itself. Command.com is the program or application in that case. Regards, Bryan

0

If I remember right, the comspec is set to the command processor which the OS booted from. You can specify another with the comspec= line. It's conceivable that the comspec var or the path or both got hosed. It would be useful to know these vars and the location of all command.com(s). Looks like this thread is another high miler, where we get in some shop talk and learn something. M2 Mechanix2@Golden-Triangle.com

0

Well Hello again all. I've just been going through all the postings and reviewing some of the info from the posted link to the MS database and decided to check a couple of things. Firstly, I don't have ANY of the .pif files listed by "Bryco" on my harddrive. (and I don't remember deleting those either but my memory is nothing to really depend on.) Secondly, as a check I looked for "Vgafull.3gr" and I don't have that file either. Seems I sort-of recall deleting unneeded (assumed) monitor related files as I'm on my third monitor since initial install of the OS. Guess I was pretty dumb with that one too. (Just proving you need to BE AWAKE when doing this stuff. I mean, just checking the date of the file creation would probably be a good indicator of whether it was an original install or later device install !) And thirdly, under these circumstances, I can't get the Windows install CD to work properly for a re-install over top of itself as the first step requires a drive check that needs to be done from DOS, which can't be accessed because I've erased the necessary instructions as to how to do precisely that. (Oh what a tangled web we weave...)But I'm just being lazy again and not wanting to search through and extract manually the file(s) I need. SO I think the first thing I'm going to do is to work on the "Vgafull.3gr" file. Will report back with the results.

0

Some further confirmation The PIF files shouldn't really be the issue, but I'll quit repeating that. Might be time to reassess your concept of 'unnecessary files' though. Use SFC to extract the files from the CD - no need for a song & dance, it's straightforward. Hopefully that will be it Why don't they make computers that will do what we think we want them to do?

0

Well well well. Did the extract/install, rebooted and viola ! All is well again. From what I gather I won't need to worry too much about all the .pif files as they should be automatically created as needed. I have just spent the last 20 minutes trying out some of the things that weren't working for me before and they all work again. Woohoo ! So a big thank-you to all concerned and thanks for assisting without a bunch of "you dumb so-and-so" kind of thing. The way I look at it is that it is all part of a learning process anyhow. And did I EVER learn a big lesson this time. Now to see what else I might do...I wonder if this .reg file is reeeeally necessary... ;)

0

;) It's a good discussion and I'll remember it. Good to find a solution rather than a reinstall or format. Naw, you don't really need that .reg file. See ya in the next thread. Skip

0

Glad to hear it all worked out. For sure, the fix is far from an intuitive one - so yeah, I'd say we all benefited from this one. Why don't they make computers that will do what we think we want them to do?

0