Hi, I used this article: http://www.devx.com/security/Article/21522/0/page/1 to create a
password filter for Windows XP. I added the dll to the registry key
NotificationPackages under
HKLM\SYSTEM\CurrentControlSet\ControlSet\Lsa. I have also enabled the
local policy "Password must meet complexity requirements" and copied
the dll to the %SYSTEMROOT%\system32 folder. When I reboot the
computer LSA calls the initialization function. However when I change
my password through CTRL-ALT-DEL Windows Security dialogue box, LSA
doesn't seem to call the other functions to check the user password.
I also tried debugging LSA by setting PolicyDebugLevel in
HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\SecEdit to 2 but this
did not seem to work on Windows XP. The article from microsoft under
KB277675 applied to Windows 2000 so this may no longer apply.
Re: .Net packaging/wrapper application? ... it just didn't work well in reality due to DLL...Windows works is to look in the executable's directory for a needed DLL ... the way apps used to work when they developed Windows. ... Looks to me like Jim is looking for the .NET equivalent of compiling... (microsoft.public.dotnet.framework.aspnet)
Re: Unnown process... 5eplorer.exe ... do not remove the cause (a "super"-hidden .dll program) but only remove ... symptom files and registry settings.... It has all permissions but 'copy' denied to everyone, ... then by using the Windows XP Recovery Console. ... (microsoft.public.win2000.general)
Re: WinSxS, functional under 2k ? ... The newSide-by-Side Assembly technology was introduced with Windows XP to help reduce or eliminate DLL Hell.... If you recall earlier Windows versions, like Windows 95, when you installed an application you were warned if the installer tried to replace a DLL from the system folder with an older version and you were asked if you wanted to accept the change. ... Until Windows XP it wasn't so easy to use different versions of shared system DLLs, that is what the new Side-by-Side assemblies attempts to resolve. ... (microsoft.public.win2000.general)
Re: Determine name and path of dropped object? ... MDE I would really suggest the use of external DLL to hold the subclassing...windows after loading the Microsoft Office Visual Basic Editor, ...Public Declare Sub DragAcceptFiles Lib "shell32.dll" _ ... (microsoft.public.access.modulesdaovba)
Re: .Net packaging/wrapper application? ... the simple answer to DLL Hell for Visual Basic apps was simply to place a copy of the needed DLLs in the same directory as your executable. ... The way Windows works is to look in the executable's directory for a needed DLL BEFORE using the registry to find one EVEN IF THE REFERENCED DLL IS REGISTERED ON THE PC RUNNING THE APPLICATION THAT NEED IT. ... Perhaps I'm getting old and but what really bothers me is nobody seems to notice this--maybe the 80s was before they got into programming.... Looks to me like Jim is looking for the .NET equivalent of compiling with static libraries to produce a single executable. ... (microsoft.public.dotnet.framework.aspnet)
