Jump to content

falco

Members
  • Posts

    126
  • Joined

  • Last visited

  • Speed Test

    My Results

Posts posted by falco

  1. I had an old computer my son was using for general surfing, etc. For about a week now the CPU fan was making noise.I was out of town for a few days and when I got back, the computer wasn't running. If the fan went, would it stop the computer from operating? I'm pretty sure it isn't the power supply as it tries to fire up for about 2 seconds, and then shuts down. Usually, if a power supply is hooped, you get no response(dead). Anyone got any ideas? Is there a way to test to see if it is the fan?

  2. Bad graphics card? Also while I am not real crazy about recomending this. Type in start, run, msconfig. See what programs are starting with your computer. I assume you can still get on the net? IF you can that instead of msconfig use this free program, http://www.windowsstartup.com/download.php. Its called startup inspector, Run it, click on consult button at the top and disable anything not necessary, If unsure google it see what it is.

    I was hoping it was the graphics card also but I swapped it out but that wasn't my problem.

  3. I can't access the net because I can only run in safe mode(I'm using my old athlon comp. I had networked). The interesting thing is I did both anti-virus and spyware scans in safe mode and my AVG reports that both my shell32.dll and ntoskrnl.exe files have been changed. Anyone know about these two files? I'm thinking my next course of action may be to rebuild my boot.ini file. Anyone have any other suggestions?

  4. If the above doesn't work, try the following steps:

    <p align="left"><b><font face="Verdana" size="2" color="#008000">Logon - Logoff

    loop, also caused by BlazeFind</font></b></p>

    <p align="left"><font face="Verdana" size="2">Another <b><font color="#FF0000">critical</font></b>

    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. <i>That is, when you login to Windows,

    the 'loading personal settings" verbose will appear, but suddenly it will

    logoff.</i> This issue was documented clearly by Lavasoftusa in it's

    Lavahelp Knowledgebase. </font></p>

    <p align="center"><font face="Verdana" size="2" color="#0000FF"><b>Here is the

    solution to the logon - logoff issue in Windows XP.</b></font></p>

    <p align="left"><font face="Verdana" size="2"><b>Enter the Recovery Console</b></font></p>

    <p style="text-align: left"><font face="Verdana" size="2">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 <b>C:Windows</b> (Or any other drive-letter where you've installed

    XP) </font></p>

    <p style="text-align: left"><font face="Verdana" size="2">Type the following command and press Enter.</font></p>

    <p style="text-align: left"><font face="Verdana" size="2"><b>CD SYSTEM32</b>

    (If that does not work, try <b>CHDIR SYSTEM32</b>)</font></p>

    <p style="text-align: left"><b><font face="Verdana" size="2">COPY USERINIT.EXE WSAUPDATER.EXE</font></b></p>

    <p style="text-align: left"><font face="Verdana" size="2">Quit Recovery Console by typing <b>EXIT </b>and

    restart Windows.</font></p>

    <p style="text-align: left"><font face="Verdana" size="2">You'll be able to login successfully as you've

    created the wsaupdater.exe file (now, a copy of userinit.exe)</font></p>

    <p style="text-align: left"><font face="Verdana" size="2">Now, change the <b>USERINIT</b> value in the

    registry (see Phase II in this page) and change it accordingly.</font></p>


    <p align="left"><b><font face="Verdana" size="2" color="#2932D6">

    </font><font face="Verdana" size="2" color="#008000">Phase II  - 

    Fixing a registry entry which causes the Quick Launch issue (not retaining the

    settings)</font></b></p>

    <p align="left"><font face="Verdana" size="2">Click Start, Run and type REGEDIT.

    Navigate to:</font></p>

    <p><b><font face="Verdana" size="2">HKEY_LOCAL_MACHINE  SOFTWARE  Microsoft  WindowsNT  CurrentVersion  Winlogon</font></b></p>

    <p align="left"><font face="Verdana" size="2">In the right-pane, change the value of Userinit to

    "<b><font color="#2932D6">C:WINDOWSsystem32userinit.exe,</font></b>"

    Type the above value exactly as given, including the comma  - exclude the quotes.

    <font color="#2932D6"><b> Also, change the path to userinit.exe appropriately if Windows is installed in a different

    drive</b>.</font>

    Close Registry Editor and restart Windows. The Quick Launch settings should be retained now.</font></p>


    Read the full page here: WinXPTutor.com

    Thanks for the reply. I tried everything you listed, but to no avail. I forgot to mention before that I tried using"the last known good configuration" and that didn't work either.

  5. I went to use my computer and the graphics were all funny. I re-booted and it shows the blue screen with the profiles showing. I click on a profile and it says logging on and the theres a flicker and I just briefly see my desktop, then it says"logging off, saving your settings.. and then I'm back to the profile screen again. I can get in using safe mode and did spy and virus scans with no problem. I tried system restore but that didn't help. Anyone have any other ideas?

  6. As a side note... I went to the Comodo site and decided to try their anti-spam program. I installed it, and then the problems began. It re-configures your network and knocked mine out-internet and everything. It also made my machine take about 2 min. to fully re-boot and I have a dual core processor. From what I can tell, it changes some winsock settings. I finally had to restore to yesterdays restore point and all is well again. I'm not saying the program is bad, but BEWARE!!

×
×
  • Create New...