default.pif

Matt Dwyer · External Since: Mar 05, 2007 Posts: 1

How do you edit the file c:\windows\_default.pif?

I see it is very well protected.

Jesper · External Since: Dec 26, 2006 Posts: 501

> How do you edit the file c:\windows\_default.pif?

You're not supposed to.

> I see it is very well protected.

All the system files are.

azquadz · Joined: Mar 21, 2007 Posts: 2

Ok so you are not supposed to....but how do you do it. How do you uncheck the box "close on exit." I can't even get windows vista to let me do this under the program tab in properties...?

azquadz · Joined: Mar 21, 2007 Posts: 2

am a student who needs to run a c compiler named miracle c for my intro to
computing class and i need to uncheck the box that says close on exit so when
my programs finish runnign i can see what they did instead of a dos window
flashing for a nano second then vanishing, when i uncheck the box and press
ok i get the error

"cannot update the properties for this program. the shortcut or .pif ma be
read-only, or another program may be modifying them.
Close all copies of this program, and then try again."

I was able to edit this option on windows xp with out any problem, any help
would be vastly appreciated

jacobwessel · External Since: Mar 14, 2009 Posts: 1

Use an elevated cmd prompt and type edit _default.pif

Thats the only way to view the file, but it is set read only even in
admin mode

--
jacobwessel

karrylogar · Joined: Oct 15, 2009 Posts: 3

The ARPANET, the predecessor to the Internet, had no distributed host name database, such as the modern Domain Name System for retrieving a host's network node address by using the web design host's name. Each network node maintained its own map of the network nodes that it needed to know about and assigned them names that were memorable to the user. There was no method for ensuring that all references to a given node on a network were using the same name, nor was there a way to read some other system's hosts file to automatically obtain their copy.

The small size of the ARPANET made the use of hosts files practical. Network nodes typically had one address and could have potentially many names. As individual TCP/IP computer networks gained popularity, however, the maintenance of the hosts file became a larger burden on system administrators as networks home insurance and network nodes were being added to the system with increasing frequency.