Jump to content

Recommended Posts

Posted

Discovered an application's (PMI) tails left over from long ago when

supposedly it had been deleted.

 

I'm hesitant to play here because they aren't concise yet I'm fairly

certain they're all together. Know what happens with "assume" also.

 

Originally, the application was geared to start on boot up.

 

If I wanted to gamble, how would I edit the ini file? Only reason to is if

it's being read. If it's being ignored, eh, so what. Thinking it might be

part of other ills here I'm hunting.

 

Windows XP SP2

  • Replies 5
  • Created
  • Last Reply
Guest David H. Lipman
Posted

Re: Win.ini

 

From: "Mist" <pequod@spam.com>

 

| Discovered an application's (PMI) tails left over from long ago when

| supposedly it had been deleted.

 

| I'm hesitant to play here because they aren't concise yet I'm fairly

| certain they're all together. Know what happens with "assume" also.

 

| Originally, the application was geared to start on boot up.

 

| If I wanted to gamble, how would I edit the ini file? Only reason to is if

| it's being read. If it's being ignored, eh, so what. Thinking it might be

| part of other ills here I'm hunting.

 

| Windows XP SP2

 

 

WIN.INI is a legacy of old applications and WinXP does not interpret it.

 

Only old games for Win95 (and maybe Win98) may interpret it.

 

--

Dave

http://www.claymania.com/removal-trojan-adware.html

Multi-AV - http://www.pctipp.ch/downloads/dl/35905.asp

Guest John John (MVP)
Posted

Re: Win.ini

 

The file is only there for backward compatibility for old 16-bit legacy

applications, you could remove all the entries in the file and it

wouldn't bother Windows at all. You can use Msconfig to disable entries

in the file or you can use Sysedit to edit and completely remove entries

in the file.

 

John

 

Mist wrote:

> Discovered an application's (PMI) tails left over from long ago when

> supposedly it had been deleted.

>

> I'm hesitant to play here because they aren't concise yet I'm fairly

> certain they're all together. Know what happens with "assume" also.

>

> Originally, the application was geared to start on boot up.

>

> If I wanted to gamble, how would I edit the ini file? Only reason to is if

> it's being read. If it's being ignored, eh, so what. Thinking it might be

> part of other ills here I'm hunting.

>

> Windows XP SP2

>

Posted

Re: Win.ini

 

"David H. Lipman" <DLipman~nospam~@Verizon.Net> wrote in

news:OB45BjkCJHA.1228@TK2MSFTNGP02.phx.gbl:

> WIN.INI is a legacy of old applications and WinXP does not interpret

> it.

> Only old games for Win95 (and maybe Win98) may interpret it.

 

No games just an ancient PIM now replaced.

 

Thanks.

Posted

Re: Win.ini

 

"John John (MVP)" <audetweld@nbnet.nb.ca> wrote in

news:O1osAnkCJHA.1628@TK2MSFTNGP03.phx.gbl:

> The file is only there for backward compatibility for old 16-bit

> legacy applications, you could remove all the entries in the file and

> it wouldn't bother Windows at all. You can use Msconfig to disable

> entries in the file or you can use Sysedit to edit and completely

> remove entries in the file.

 

Ahh, the things I learn here - very good thing.

 

Think that Sysedit is the choice.

 

Thanks.

Posted

Re: Win.ini

 

Mist wrote:

>

> If I wanted to gamble, how would I edit the ini file? Only reason to is if

 

win.ini is just a txt file. Edit with notepad.

 

--

http://www.bootdisk.com/


×
×
  • Create New...