WinXP msgina.dll & shlwapi.dll problem...

[stefan099]

its been i while since i had this problem but it was quite easy to fix, if you have the original windows disk that is.


i just changed the boot up options to boot from the cd-rom drive and then booted using the windows disk. via the interface that then appears you just select to repair and let it do its thing. it takes a while but when finished it back to normal with all the same files intact.


however i'm not so sure what to do if you dont have the disk, i'm affraid i'm not that technically minded. hope you find a solution, dont worry its fixable

[jsecr]

Hey the solution of Patrick also serves to solve the problem:

AssocGetPerceived Type with SHLWAPI.dll

thanks to all

Good it is to learn but better to share

[jsecr]

this really save my

[ComputerAid]

Originally Posted by pturner

Hey guys-


1. Boot to Recovery Console.

2 . type the following commands
cd system32 [enter]

ren winlogon.exe winlogon.old
ren msgina.dll msgina.old
ren shell32.dll shell32.old
ren shlwapi.dll shlwapi.old

cd.. [enter]
cd servicepackfiles\i386 [enter]
copy MSGINA.DLL c:\windows\system32
copy SHELL32.DLL c:\windows\system32
copy WINLOGON.EXE c:\windows\system32
copy shlwapi.dll c:\windows\system32

if not there, expand from the cd

3 Type EXIT and hit enter

Worked Like a charm - and five years later too - MS is still a pain in the ****
Thanks!!

[grace88]

Thank you guys!
I still have a question, i alreday finished changes on system23. I found my i386 files in the c:\.
but when i typed c:\>cd i386 ,it shows "Access is denied", How can i fix this?

[ShyguyXPC]

Originally Posted by nowayinthe

you are going to have to insist on getting support from MS for the problem, because MS typically attempts to refer you back to the computer manufacturer who is contractually obligated to provide support for all preloaded software,
------------------------------
Removed spam link

jesus, this spammer hasn't been removed yet? reported them a while ago early this morning... still here with 9 posts?

[Johnpcook]

Originally Posted by pturner
Hey guys-


1. Boot to Recovery Console.

2 . type the following commands
cd system32 [enter]

ren winlogon.exe winlogon.old
ren msgina.dll msgina.old
ren shell32.dll shell32.old
ren shlwapi.dll shlwapi.old

cd.. [enter]
cd servicepackfiles\i386 [enter]
copy MSGINA.DLL c:\windows\system32
copy SHELL32.DLL c:\windows\system32
copy WINLOGON.EXE c:\windows\system32
copy shlwapi.dll c:\windows\system32

if not there, expand from the cd

3 Type EXIT and hit enter


Running XP pro
My problem seems to have come with SP3. I was trying to set up users and could not get them to show in the logon screen. I tried playig with administrator settings etc. and around that time I did the windows updates hoping to fix prob. so, no boot and me and msgina are old buddies.

Did the above and got the mesage:

"this app failed to start because ODBC32.Dll was not found. Re-installing the application may fix the problem"

So, I got to the repair prompt off the XP install CD as described in earlier posts, and typed the following:

cd system32 [enter]
dir

by hitting the space bar repeatedly, I got to where the OBDC file should have been and indeed it was not there. It was not in the \servicepackfiles\i386 directory either.

Sol I went to another XP computer and found the file in the windows/system32 folder, copied it to the desktop, and dragged it onto a floppy

Next I put the floppy into the machine still stewing in its msgina juices, and and where I left it in the system32 directory in recovery mode.

I typed the following:

A: [ENTER] That's where the floppy should be
DIR [ENTER] (This let me see that the file could be read on the floppy)
copy odbc.dll c:\windows\system32 [ENTER]
exit [ENTER]


What can I say? with your help I stumbled to success!

Problem solved.

So, here's what I'm thinking. The process related to solving this problem is to get working files back to where they should be. In the case of files already there, as in the errant winlogon.exe in pturner's fix (thank you very much!) , the idea is to rename those files in case you later need to back out of your mess. You can just rename them back to their old names, in essence reversing the porcedure and be back where you were.

But, in the case of files which are not there in the first place, you need to get them where they belong.

In my case, when I tried to Ren (ame) the msgina.dll in the original fix, I got a message that the file could not be found. At that point I didn't care, because I could see that in the second step, I would be copying the msgina file from the windowsupdates.i386 directory.

When I found that the OBDC.dll was not a file in the update, I guessed it probably was not a part of the service pak and ... well at that point it was any ship in a storm, so I copied it from a known working source using the old copy to floppy.

I also could have burned it onto a CD to get it there. In this case, I would have had to remove the XP cd from the still running sick PC, pt in the CD and then type :

d: [enter} -- or whatever drive letter the CD ROM is on. I could do the dir , and hit the space bar to locate the file, or I could just do the same copy command as above.

copy <the name of the missing file> (to) c:\windows\ <the name of the directory where the file belongs>

as in:

D: [enter]
copy OBDC.dll c:\windows\system32 [enter]

Hope this helps

By the way There is one little gotcha with system files. which is XP does not like you to see them, or mess with them. You'll have to ask someone else how to reveal hidden files in case that becomes a problem, 'cause I'm relly on the edge of what I know.

If somebody could explain how to "expand from CD" and get the above all in one post, we'd have this all but dummy proof.

But I'm very happy , all the same.

Thanks again