boot to the DOS promt follow these commands at the c: attrib msdos.sys -h -r -a -s edit msdos.sys you should get a blue edit screen with some text in it. look for aline that says bootmenu=1 change it to bootmenu=0 save the file (Atl+f scroll down to save) exit the file (Atl+f scroll down to exit) At the c: type attrib msdos.sys +a +s +r +h reboot

0

Opps i put your name in there....loIf you get a error when you type the attrib command then type this and try it again. path=c:\windows\command

0

Ok John, did that. no bootmenu listed. Options bootMulti=1 bootGUI=1 doublebuffer=1 autoscan=1 winver=4.10.1998

0

Under the boot menu that you are getting does it say something about windows not being shut down proprly or does it say something else?

0

it says windows did not finishing loading on the previous attempt. choose safe mode to start Windows 98... then it tests the memory, then goes into safe mode automatially.

0

Hmmm I am guessing that the Autoscan and win ver line are all the way at the bottom of the msdos.sys file. That is where they ussually are. Does the PC run scan disk? It is odd that it keepsloading that way and doesnt give you a chance to change how you want to boot up.

0

also while doing mcafee virus scan cannot scan boot record.

0

Mandy; Let's start from the beginning: Here, from Symantec... "Discovered on: February 17, 1995" "NYB is a simple virus that infects master boot records (MBR) and DOS boot sectors (DBS). NYB spreads to a system only when there is an attempt to boot the system from an infected floppy disk. Target of infection: DOS TECHNICAL DETAILS During the boot process, NYB loads the MBR into memory and checks for infection. After determining that the MBR is not infected, the NYB stores the uninfected MBR at cylinder 0, side 0, sector 17 on the hard disk. NYB then places its virus code into the MBR and writes the infected MBR back to the hard disk at cylinder 0, side 0, sector 1. Once the boot process is complete and the NYB virus is active in memory, the virus displays its stealthing capabilities by redirecting any disk reads of the infected MBR or DBS to its clean counterpart. (On floppy disks, the original DBS is stored in the last sector of the root directory.) NYB is highly prolific." You (or somebody using your PC) may have accidentally left an floopy in it's drive on a subsequent re-boot. • Obtain a CLEAN and Write-Protected System Bootdisk on floppy. • Obtain a DOS-based virus checker (like F-Prot) • Boot from the Bootdisk • Switch floopies to the DOS a-virus floppy • Run the scan from that floppy That should lead to resolving your problem, BUT, you must now also v-scan and clean your "innocent-looking" floppies... :(

0

the files are listed in order as in previous post. Yes i've done scandisk - no errors I've defragged - no errors. I have tried fdisk /mbr with the bios virus scan both dissabled and enabled. It is a myster on how to clean that boot sector that's infected.

0

how am i gonna get f-prot on a diskette? it's too big a file to transfer.

0

f-prot /loaddef will load the def files from a second floppy. The first floppy should contain: English.tx0 f-prot.exe macro.def The second floppy will contain the two sign.def files.

0

Hello Michael Well thanks for that. However it didn't work. I loaded F-prot. Then it asked for a disk weith the two sign.def files and the macro.def file. The new def files are too big with the macro.def file for one disk. Still stuck!

0

You're quite right, that's why I listed which files go on which disk, the floppy with the sign.def and sign2.def files does not have the macro.def file on it. F-Prot should have asked for the macro.def file, at which point you would put the 1st floppy back in. Sorry, I just checked the new August def files, and you're right, sign.def and sign2.def won't fit on a single floppy anymore (1k too big). Now we'll have to use 3 diskettes for it. Or put the sign2.def file on the 1st floppy. That should work. The /loaddef switch only means to look on another floppy for the def files.

0