View Full Version : Boot sector virus
I'm trying to install windows xp on my comp and getting this message.
BootSector Write
Virus: Continue [Y/N]?
Originally, I have been attempting to upgrade from windows 2k to xp pro using oem xp install software. It wouldn't install as upgrade so I did it as new installation. Ever since then my computer just wouldn't behave. I know there is nothing wrong with the install cd itself, because I was able to successfully install in my laptop.
The problem occured when I tried to boot after installing xp. It would just freeze up when it came to the xp logo on the screen. I then reformatted the hard drive and re-installed the xp. Now I am getting the message above. I made a mess of thing and I can't clean it up.
Specs:
Asus p4c800
p4 3.2
geforce 6800
maxtor 7200 200gb
2gb ram
It sounds like that motherboard has a feature to prevent anything from altering the boot sector of the HD to prevent getting a boot sector virus. If this is occuring during the Windows XP install process I would just let it write to the boot sector as it is part of the install process. You could also temporarily disable the feature from BIOS until the install has finished.
If this is occuring after the install has competed, and you have been using Windows XP then you have a virus you need to take care of.
Sylvander
03-20-2006, 10:57 AM
"It sounds like that motherboard has a feature to prevent anything from altering the boot sector of the HD to prevent getting a boot sector virus"
I think Erik is correct there. My older BIOS has...
"Virus Warning : Disabled"
I remember reading how much of a nuicance this can be when enabled.
It should at least be disabled when installing an OS, since the boot sector will be modified during that.
I've tried diabling the virus warning, but still the windows' having trouble starting up. Not sure if it's hardware or software issue that I'm having difficulties with.
So should there be any difference between oem software and retail version when installing on hard drive that has pre-existing data?
Paul Komski
03-23-2006, 02:29 AM
but still the windows' having trouble starting up
Will windows boot without this warning if you boot into safe mode; (F8 during startup) or do you only get this message when attempting to install/reinstall/upgrade ??
If you never finished performing an installation properly due to the motherboards virus warning you might still have the old Win2K boot sector, which would cause problems loading Windows XP as they are different.
Try booting from the Windows XP CD, and choosing recovery consule when given the option by pressing R. Once at the command prompt interface type in fixmbr and hit enter. This should copy a fresh Windows XP standard boot sector information to where it needs to be. As long as you did a plain and simple installation this should work without problem. If you tried dual boot, or installing to different drives or partitions then it might not help you.
Paul Komski
03-23-2006, 04:42 PM
fixmbr does not replace a win2k (or any other) partition boot sector with the one for winxp; for that you need to run fixboot.
fixmbr does however replace the bootstrap code in the mbr and may thus directly replace any boot sector virus code with normal code.
I don't know about that. I have used fixmbr to write over non Windows XP boot sectors after problems with a multi boot system. It gives a warning saying that the boot sector isn't a standard Windows XP version, and asks if you want to continue anyway.
Paul Komski
03-24-2006, 05:49 PM
http://support.microsoft.com/?kbid=314058
FIXBOOT
fixboot drive name:
Use this command to write the new Windows boot sector code on the system partition. In the command syntax, drive name is the drive letter where the boot sector will be written. This command fixes damage in the Windows boot sector. This command overrides the default setting, which writes to the system boot partition. The fixboot command is supported only on x86-based computers.
FIXMBR
fixmbr device name
Use this command to repair the MBR of the boot partition. In the command syntax, device name is an optional device name that specifies the device that requires a new MBR. Use this command if a virus has damaged the MBR and Windows cannot start.
The MBR is not involved with any specific OS; it being outside any individual partition's metadata.
In my case, neither fixboot or fixmbr have worked. I may have whole another problem with the computer. I did try to install another hard drive as slave to the existing primary drive. Now I have two drives that is not working.
This has turned out to be big headache. I gived up trying to fix it on my own and turned it in to tech service today to see if they can make it come alive. I should get it back within in a week.
Are you guys sure this has nothing to do with this being an oem software?
If it is like OEM for a Dell and you try to install on an HP for example you might encounter problems with activation, or it might tell you it is not a compatible computer during install. Nothing about a boot sector virus. This is defenitely related to a feature on your motherboard.
Paul Komski
03-25-2006, 12:06 PM
Having disabled the virus warning in the BIOS it could have been an idea to have written zeroes to the drive and then started over. An alternative, once again after diabling the virus warning, would be to try a repair installation of WinXP: http://www.michaelstevenstech.com/XPrepairinstall.htm
Are you guys sure this has nothing to do with this being an oem software
An oem winxp installation CD should perform just as well as a full retail installation CD since the only difference is that the oem software should only be distributed along with hardware and not as standalone software.
If you buy a mobo and parts to build a pc you would certainly be eligible to receive the oem software at the same time. In that case you become the OEM. The term is also used for the big name proprietary "builders" of computers such as Dell, Compaq and so on.
I just got my computer back from repair service. However, they were unable to fix the problem of installing xp. I was told there were something wrong with the mobo. They didn't specifically tell me what was the nature of problem; just "think it's hardware issue". I thought I would try something before deciding to get a new mobo.
I tried to install win 2000 again after reformatting the hard drive. It successfully installed win2k. I couldn't believe my eyes. So now I don't think there is anything wrong with the mobo. I don't even know if those guys at the tech service knows what they are doing. Anyways, after fully installing windows, I popped in the window xp install cd into the computer, and checked for compatibility. I get this warning message:
Windows xp setup does not support upgrading from Microsoft Windows 2000
Which was the messege I got the first time trying to install xp before all this mess. So now I still don't know why it wouldn't install xp, and just what is it that I need in order to upgrade to xp.
Paul Komski
04-05-2006, 02:01 AM
That warning isn't a hardware compatibility issue. It seems you need the full retail version to do the upgrade and not the oem edition: see http://www.mcse.ms/message1009948.html p.s. Sorry that I was wrong about that but I suppose it stands to reason since the oem edition is designed for "new hardware".
You should maybe make a backup image of your current installation onto CD(s)/DVD(s) or onto another HDD partition using software such as BootIt-NG or Image for DOS from http://www.terabyteunlimited.com or from an older image program running from an EBCD from http://ebcd.pcministry.com/ or from any other imaging software of your choice. That way you should be able to restore to your current setup with little risk if you run into problems clean installing WinXP. Suggest that after you have an image that you zero the drive or at least fully delete the Win2K partition from the installation CD or by using a utility such as fdisk or bootitng from www.bootitng.com beforehand.
Disable the virus warning in the BIOS if you dont want it to freak you out.
So much for tech support!! ;)
Sylvander
04-05-2006, 03:55 AM
KILLDISK (http://www.killdisk.com/downloadfree.htm) is a really good zero-fill utility.
1. How to make a free “Smart Boot Manager” floppy
http://www.pcguide.com/vb/showthread.php?t=41498
This makes it easier to boot a chosen drive [particularly the one holding the EBCD].
2. How to make a free EBCD bootable CD
http://www.pcguide.com/vb/showthread.php?t=41485
This has a number of useful utilities included including "Image" [for DOS, by Terabyte], "File Manager", fdisk.exe for partitioning & format.com.
This free trial version of Image needs a FAT32 partition [other than those being backed up] to which to save the backup files. Really easy to use once you've provided a home for the files and become accustomed to typing in the address and name of the file.
I save at "g:\image\c\060405".
g is the drive.
image is the folder for holding my image files.
c is the folder where I hold the backups of the C: partition.
060405 is the file name.
06 is the year.
04 is the month.
05 is the day.
Thanks guys, for all the info. I will give it a try with a spare drive I don't use just in case I foul up again. Should of tried making ebcd in the first place. I came across the info before, but I just skimmed through it not knowing if what it was.
vBulletin v3.6.1, Copyright ©2000-2012, Jelsoft Enterprises Ltd.