| Download WOW32.DLL | WOW32.DLL Download |
Microsoft Corporation's - Wow32 v , 0.2.0.0, 4.0.0.950, 4.0.1381.141, 4.0.1381.4, 4.00, 4.00.950, 4.10.0.1998, 4.10.1998, 4.90.0.3000, 4.90.3000, 5.0.2164.1, 5.00.2164.1, 5.1.2600.0, 5.1.2600.0 (xpclient.010817-1148), 5.1.2600.1106, 5.1.2600.1106 (xpsp1.020828-1920), 5.1.2600.2096, 5.1.2600.2096 (xpsp_sp2_rc1.040311-2315), 5.1.2600.2180, 5.1.2600.2180 (xpsp_sp2_rtm.040803-2158), 5.1.3590.0, 5.1.3590.0 (main.011110-1652), 5.2.3790.0, 5.2.3790.0 (srv03_rtm.030324-2048), 5.2.3790.1069 (srv03_spbeta.030905-1850), 6.0.3683.0, 6.0.3683.0 (Lab06_N.020923-1821), 6.0.6000.16386, 6.0.6000.16386 (vista_rtm.061101-2205) |
Monday, August 31, 2009
Finally a solution(Can't load SmartUI Library (code 126) error, ), Samsung ML-1710 printer won't work
This is a follow-up to a to a question I posed quite a while ago re: my Samsung ML-1710 printer not working.
This is the error message I kept getting (Can't load SmartUI Library (code 126) error, ) when I tried printing. I never got around to making another nlited WinXP with less options removed trying to find exactly what was causing the problem. Nobody else seemed to have any ideas either, because after nearly two months I only got one reply to my post (Mar.25th) with a possible solution. Well guess what, that was enough.
The solution offered by member ( DIGERATIPRIME ) was to put the WOW32.DLL file into my system32 directory. I didn't have the file so I downloaded a couple of versions from the internet. The first version did not work and I thought, should I bother with the second WOW32.DLL ver. 4.0.0.950 or not but I did and to my amazement it worked. I fired up the printer and it worked perfectly.
Thanks again to DIGERATIPRIME, for taking the time,
Dhedges
Sunday, August 30, 2009
Unable to logon to Windows (Tidak bisa masuk / logon ke Windows XP)
Unable to logon to Windows after removing BlazeFind using a spyware removal utility?
Logon - Logoff loop, also caused by BlazeFind
Another critical symptom caused by this malware: This malware modifies the Userinit area in the registry (replacing the userinit.exe with wsaupdater.exe) and Ad-Aware (with a particular definition update) removes the wsaupdater.exe file from the system, thus causing the Logon - Logoff loop. That is, when you login to Windows, the 'loading personal settings" verbose will appear, but suddenly it will logoff. This issue was documented clearly by Lavasoftusa in it's Lavahelp Knowledgebase.
Here is the solution to the logon - logoff issue in Windows XP.
Enter the Recovery Console
Boot the system using the Windows XP CD-ROM. In the first screen when the Setup begins, read the instructions press "R" (in the first screen) enter the Recovery Console. Type-in the built-in Administrator password to enter the Console. You'll see the prompt reading C:\Windows (Or any other drive-letter where you've installed XP)
Type the following command and press Enter.
CD SYSTEM32
(If that does not work, try CHDIR SYSTEM32)
COPY USERINIT.EXE WSAUPDATER.EXE
Quit Recovery Console by typing EXIT and restart Windows.
You'll be able to login successfully as you've created the wsaupdater.exe file (now, a copy of userinit.exe)
Now, change the USERINIT value in the registry (see Phase II in this page) and change it accordingly.
|
References & Additional Reading:
Subscribe to:
Posts (Atom)