Windows IT Pro is the leading independent community for IT professionals deploying Microsoft Windows server and client applications and technologies.
  
  
  Advanced Search 


June 2001

Replacing a Corrupted Bootsect.dos File


RSS
Subscribe to Windows IT Pro | See More Windows OSs Articles Here | Reprints | Or get the Monthly Online Pass—only $5.95 a month!

Several years ago, I migrated from Novell NetWare 3.11 to Windows NT 4.0. One of my accounting programs didn't run well in NT, so I set up a dual-boot with DOS—but DOS quit working recently. My computer consultant informs me that bootsect.dos is corrupted and can't be fixed. Can I fix this problem?

When you install NT on a machine with an existing OS, NT Setup creates a file called bootsect.dos and copies the existing OS's boot sector, which resides in sector 0 of the C drive, into that file. Then, when you run the previous OS, NT copies bootsect.dos to the boot sector. Because NT Setup creates bootsect.dos, the file can be the boot sector for any previous OS and can be difficult—but not impossible—to recreate.

First, regenerate a boot sector for the previous OS (in your case, DOS). Make a 3.5" boot disk for your version of DOS, and copy sys.com from the DOS directory onto the 3.5" disk. Boot the troubled computer from the boot disk, and run the following command:

sys c:

This procedure will restore your DOS version. However, NT won't function.

You must now ascertain whether bootsect.dos exists on your hard disk; NT Setup won't overwrite an existing bootsect.dos file. Boot to DOS, and change the directory to DOS. Run the following command:

attrib -r -s -h c:\bootsect.dos

If bootsect.dos exists, delete it. After you delete the file, or if the file doesn't exist, turn off the machine and remove the 3.5" boot disk. Insert the first NT Setup disk, and reboot the machine. At the first Setup screen, press the R key (for repair).

When Setup presents you with the list of optional repair tasks, select only the Verify boot files on your C: drive check box. When the repair process is done, you'll see a message that states Setup Repair is complete. You should then be able to boot to DOS and run your accounting program.

End of Article



Reader Comments

You must be a registered user or online subscriber to comment on this article. Please log on before posting a comment. Are you a new visitor? Register now




Top Viewed ArticlesView all articles
Command Prompt Tricks

One reader shares his tip for setting up the command prompt to reflect a remote path. ...

2009 Windows IT Pro Editors' Best and Community Choice Awards

Picking a favorite product from an impressive crowd of competitive offerings is never an easy task, and such was the case with our Editors' Best and Community Choice awards this year. ...

WinInfo Short Takes: Week of November 23, 2009

An often irreverent look at some of the week's other news, including some post-PDC some soul searching, a Google Chrome OS announcement and a Microsoft response, Windows 7 off to a supposedly strong start, the Jonas Brothers and Xbox 360, and so much more ...


Related Events Deep Dive into Windows Server 2008 R2 presented by John Savill

Check out our list of Free Email Newsletters!

Windows OSs eBooks Understanding and Leveraging Code Signing Technologies

A Guide to Windows Certification and Public Keys

SQL Server Administration for Oracle DBAs

Related Windows OSs Resources Introducing Left-Brain.com, the online IT bookstore
Looking for books, CDs, toolkits, eBooks? Prime your mind at Left-Brain.com

Discover Windows IT Pro eLearning Series!
Clear & detailed technical information and helpful how-to's, all in our trademark no-nonsense format


Windows IT Pro Home Register FAQ for Windows WinInfo News
Europe Edition About Us Contact Us/Customer Service Media Kit Affiliates / Licensing  
SQL Server Magazine Office & SharePoint Pro DevProConnections IT Job Hound
Left-Brain.com Technology Resource Directory asp.netPRO ITTV Windows SuperSite 
 
 Windows IT Pro is a Division of Penton Media Inc.
 © 2009 Penton Media, Inc. Terms of Use | Privacy Statement