Elusive .pif files

Guest · Post by **Guest** » Mon Dec 08, 2003 3:46 pm

While trying to get a pif file that does nothing but get a command shell with custom config.sys in Win XP (to check something out asked in another thread) I ran into a little strange thing...

As I recall it, on Win9x OS, if you created a shortcut to a DOS executable, you'd end up with a pif file, or just by running the executable, you'd get the same result...
If creating a short cut to a DOS executable in XP, you get nothing but a short cut

If you run the exefile, you get nothing at all...

If you however copy an old .pif file, then change stuff in it, for examble to execute only %systemroot%\system32\cmd.exe and specfying custom version of config.sys, everything works as it should... There is no doubt that XP can handle .pif files... BUT how tf do you create them other than copying? I really dislike the idea of not being able to do so unless I already have a "stem cell file" to create new ones from

Sweetest would of course be if anyone knows how to modify the registry to get the option of making a new pif file appear on the r-click menu, submenu "new" in explorer. Any other way wouldn't hurt though

please help me out. i'm curious...

Post by **Wally** » Mon Dec 08, 2003 7:33 pm

Hi get the program

send to toys...

that should help

well maybe not....

Splodginator · Post by **Splodginator** » Tue Dec 09, 2003 12:54 am

Err... AFAIK, Windows XP automatically makes PIF's if you set the shortcut to a DOS program. CMD isn't a DOS program, so you can't make it into a PIF.

Zaphod` · Post by **Zaphod`** » Tue Dec 09, 2003 1:58 pm

Furthermore, there is no such thing as Config.sys under WinXP. I am surprised that Win98 PIFs work under XP, it probably strips out the irrelevant fields. Well, anyway, under XP, the entire subject of this post is pointless. All the "Config.sys" fields from Windows 98 are either not modifiable, or are specified in the WinXP PIF options (Such as size of memory, etc.) For sound drivers, please try VDMsound.

Guest · Post by **Guest** » Sun Dec 14, 2003 6:01 am

erm, I keep referring to config.sys when I mean whatever config file is specified in the pif file.

and you're right abot cmd.exe not being a DOS program which is why it wouldn't create the pif file for me automatically (command.com most certainly was a DOS file in win98). However, making a copy of a pif file, setting command line to cmd.exe and setting up a config file to be used. That way you can get a command shell with EMS memory for instance.