From: Roger L. <rog...@ho...> - 2003-03-05 10:11:45
|
> >Earnie wrote: > >Well now, that was interesting. I have a new P4 Compaq Laptop that I've >been setting up with software for use here at work. I ran into a situation >similar to yours Roger where Msys, Cygwin and cmd.exe would not work. So I >used depends and found that shlwapi.dll contains a reference to >WNetRestoreConnectionA which doesn't exist. I'm not sure what caused cmd >to start using shlwapi and having this problem but MS has a bug in shlwapi >as there documentation doesn't mention anything about >WNetRestoreConnectionA but it does mention WNetRestoreConnectionW. I >binary edited shlwapi.dll modifying WNetRestoreConnectionA to >WNetRestoreConnectionW which I believe to still be wrong. I can now run >cmd.exe, msys and cygwin again. I found two different versions of shlwapi.dll on my system. One in the system32 directory and one that came with McAfee Netshield. The Microsoft one only had references to WNetRestoreConnectionW but the McAfee one had references to both. I renamed the McAfee dll and rebooted. Unfortunatelly it didn't solve the problem. >Well we've narrowed down the offending sections of code. Now why >doesn't >it work for you? What access do you have to USER32.DLL? Or >do you >possibly have more than one USER32.DLL in PATH? When it comes to user32.dll I have admin rights, incl both read, execute and write. Only one version (provided by M$) on the system. >I'll have to review the MSYS coding more to determine what's going on. > >This is strange. Please let me know if there is some info I can provide you with that might help. Best regards // Roger _________________________________________________________________ Skaffa fler messengerkontakter - Vinn 10.000 i resecheckar! http://messenger.msn.se/promo |