Kill Boot Sector Script?


Recommended Posts

I had a script about a year ago, but lost it. It was a debug script that ran from a boot floppy to delete the master boot record of the first drive.

The script was in a test file and then I ran it like "debug killbs.txt" from the command line.

Anyone have this script or can make one for me?

Any way to go further than that. Like is there a way to copy the boot sector to the floppy and then delete the master boot record and then later if need be, have the floppy restore the master boot record to get everything back?

That would be a great security script.

Link to comment
https://www.neowin.net/forum/topic/135642-kill-boot-sector-script/
Share on other sites

No, it's something else. I remember it, let me pull it off...

At least you have the necessary commands right there...

  Quote
Run the Debug Script

The following debug script removes DOS and non-DOS partitions on the hard drive. This debug script allows you to convert a drive from an incompatible partition structure to one that will work with FDISK.EXE such as converting Linux partitions to MS-DOS partitions.

Insert the boot disk that contains the Debug command into the floppy disk drive.

Restart the computer.

A black screen with the Microsoft Windows? 95 Startup Menu appears.

Press the <5> key, and then press the <Enter> key.

The boot process concludes with an A:\> prompt followed by a blinking cursor (underline).

From the A:\> prompt, type the following commands, and then press the <Enter> key after each command:

NOTE: Type the bolded text only (the debug prompt is a dash). You may receive an error if you type anything other than the bold text. The non-bolded text represents the system response that will appear after typing each command and pressing the <Enter> key.

debug

-F 200 L1000 0

-A CS:100

xxxx:0100 MOV AX,301

xxxx:0103 MOV BX,200

xxxx:0106 MOV CX,1

xxxx:0109 MOV DX,80

NOTE: Type 80 for the primary hard drive - HD 0, or type 81 for the secondary hard drive - HD 1.

In most cases, the primary hard drive is required 80.

xxxx:010C INT 13

xxxx:010E INT 20

xxxx:0110 (Leave this line blank. Press the <Enter> key to continue.)

-G

The message Program terminated normally appears.

Press the power button to turn off your computer.

On the ensuing startup, the hard drive must be partitioned and formatted. Refer to the Additional Information section for further instructions.

Return to Overview

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • PC manufacturers used to trick BIOS copyright strings to get full editions of trial software by Usama Jawad You may have noticed that when you purchase a new PC, it comes with certain software pre-installed. Sometimes, when you open this software, it activates, and you receive the full version of it without paying any additional cost. This is because that PC's manufacturer is a licensee of that software and the fact that a customer gets the full version of a trial software for free serves as a perk for potential buyers. However, many PC manufacturers tried to trick this process in its infancy. During the days of Windows 95, when the Plug and Play specification was still in development, the OS' engineering team was trying to figure out ways through which it could identify PCs that existed prior to the inception of this specification. To that end, one of the methods they tried was searching for copyright strings and firmware dates in the BIOS. Through the course of this investigation, they discovered a rather oddly named copyright string "Not Copyright Fabrikam Computer" in a PC that was actually manufactured by Contoso. In this case, both Fabrikam and Contoso are fictional names that are used to describe this scenario without revealing the actual identity of the OEMs involved. Microsoft engineer Raymond Chen explains in a blog post that these odd copyright strings were actually appearing because Contoso PCs contained a trial version of a software and the company wanted the full version to be activated for customers even though it was not an official licensee. In order to bypass the costly licensing process, what the firm did was that it added the following text to its copyright string: "Copyright Contoso Not Copyright Fabrikam Computer". The trial version of said software would search for the string "Copyright Fabrikam Computer" and end up finding it within the substring of the convoluted copyright string mentioned above, accidentally activating the software's full version. While more robust ways were adopted later to avoid this problem, it's certainly interesting to see that OEMs would go to this length in order to distribute software that they are not officially allowed to. Well, as they say, the past stays in the past.
    • Uhm... a couple of issues with this. First, you're engaging in revisionist history. People weren't dragged from Win 7 to Win 10. You've kind of glossed over a whole cycle there: Win 8/8.1. People stayed on 7 because they hated 8/8.1 and held on until 10 showed up. THEN they actually started to switch voluntarily. Second, it's not about the OS, it's about the workflow. OS fans consistently miss this, People have work to do and they've invested a lot of time, effort and even money building their workflows. It's expensive to change so, that change has to offer real benefits and sorry, Win 11 just doesn't. That's the same reason they won't just jump to an entirely new OS - which has an even bigger workflow cost - until there's just no other option. And now there IS another option, stay on Win 10 for another year and pray for Win 12 (much as Win 7 users did with Win 8 - which happened when Win 10 came out).
    • Microsoft has some PC VR games that could be played with it.
    • As such, many developers will start dropping Windows 10 support in their products Hi! Actual developer here. No we won't. It really doesn't work that way simply because most Windows devs don't target to a specific release of Windows unless we're using a feature that only exists IN a specific version, and that's pretty unusual. The biggest example would be MSFT killing off Windows Mixed Reality in Win 11, but most stuff we write for Win 10 will just work fine in Win 11 and vice versa. The vast majority of software doesn't rely on these things and will continue working on any recent version of Windows. Heck some of my software still runs on WinXP. Where Win 10 users will be left behind is software that relies on new features in Win 11 but again, we tend not to use those unless we're writing specific apps that need those features. In fact, the biggest danger area isn't apps, it's drivers as hardware makers focus on new machines more than supporting legacy devices.
  • Recent Achievements

    • Week One Done
      DrRonSr earned a badge
      Week One Done
    • Week One Done
      Sharon dixon earned a badge
      Week One Done
    • Dedicated
      Parallax Abstraction earned a badge
      Dedicated
    • First Post
      956400 earned a badge
      First Post
    • Week One Done
      davidfegan earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      616
    2. 2
      ATLien_0
      227
    3. 3
      +FloatingFatMan
      170
    4. 4
      Michael Scrip
      166
    5. 5
      Som
      148
  • Tell a friend

    Love Neowin? Tell a friend!