Weird startup file on fresh install

I've recently re-installed XP home on my workstation and have the following startup file - desktop.ini.

So whenever I reboot, notepad automatically opens and displays the info in the desktop.ini file which contains:

[.ShellClassInfo]
LocalizedResourceName=@%SystemRoot%\system32\shell32.dll,-21787


Anyone know what is going on here?

Marty

 

I suggest you do either one of the following:

1. Open the desktop.ini file and edit out the space between shell and 32.

2. Delete the desktop.ini file.

Either may cure the problem and neither will cause any harm so take your choice. I suspect the desktop.ini file in question is referencing the shell32.dll file to obtain an icon for the folder that it resides in.

EDIT Testing reveals that the code string LocalizedResourceName=@%SystemRoot%\system32\shell32.dll,-21787 will not be refering to an icon but rather to the folder name and function. It causes the folder name to be Startup on my test folder. That would explain why you witness the error on startup. Do the #1 editing and it should fix you up.

 

I have no idea why that space showed up on my posting - it is not on the file. I'm going to delete it instead. Thanks.

 

The space is thanks to the line wrap feature on this BB. Since it isn't relevant to your problem, and before deleting, check your startup folder listed under your profile and see if it contains anything strange. If not, go ahead and delete the desktop.ini file therein.

There are also several other Startup folders but the one under your profile is likely at the heart of this glitch.

FYI, the line wrap can be defeated if you ever have occasion to need such a trick. If you post a string that gets changed by the BB software and has a space character inserted that is not proper, just edit the string and format one of the words in it to the color black. Voila!

See:

[.ShellClassInfo]
LocalizedResourceName=@%SystemRoot%\system32\shell32.dll,-21787

 

Makes sense about the line wrap thing, thanks for pointing that out. No the folder was empty beside the desktop.ini file so I've rem'd it and all seems ok now.

Always an adventure.

Marty