Jump to content
Posted 11 November 2009 - 08:47 PM
Posted 12 November 2009 - 09:24 AM
You should not be following specific instructions provided to someone else. Those instructions were most likely given under the guidance of a trained staff helper to fix that particular member's problems, NOT YOURS after careful evaluation of the malware involved. Before taking any action, the helper must investigate the nature of the infection and then formulate a fix for the victim. Although your problem may be similar, the solution could be different based on the kind of hardware, software, system requirements, etc. and the presence of other malware. Using someone else's fix instructions could lead to disastrous problems with your operating system.
i followed some steps from a reply to another poster who was having the same issue.
Using MSConfig to access (force) safe mode with the /Safe boot option when there is malware on your system could have disastrous results and render your computer unbootable. The Safeboot option modifies the Boot.ini file by adding the /safeboot:minimal argument to your operating systems startup line. Some types of malware can delete or alter the safeboot key in the registry resulting in the inability to reboot fully into safe mode or back to normal mode. When this occurs, you may be locked in a continuous reboot loop afterwards where you cannot get back to MSConfig and undo your selection until the /safeboot argument is removed from the boot.ini. See Booting into Safe Mode safely.
i then ran msconfig and checked the safe mode box under boot.ini. I then found that my computer was unable to boot properly
Problems that can occur by forcing Safe Mode
...If a situation like this has happened to you it is possible to fix this problem by renaming your boot.ini file. The first step would be to use a boot disk to start your computer. If your computer does not have a floppy disk, then you can typically boot off the Windows CD that came with your computer in order to access the Windows Recovery Console...Once booted to a command prompt, you would simply rename your C:\Boot.ini file to another name like C:\Boot.ini.bak. The command to rename the file at the command prompt is:
ren C:\Boot.ini Boot.ini.bak
Once the file is renamed, you can then remove the boot disk and reboot your computer to get back to normal mode. When booting up after the rename, do not be surprised if you see an error stating that you do not have a valid Boot.ini file. When you get back to normal Windows mode, you can then rename C:\Boot.ini.bak to C:\Boot.ini file and run Msconfig again to remove the /safeboot flag...
Posted 12 November 2009 - 06:39 PM
Posted 12 November 2009 - 07:53 PM
0 members, 0 guests, 0 anonymous users