a killer poke is a method

In PC language, an executioner jab is a strategy for instigating physical equipment harm on a machine or its peripherals by the addition of invalid qualities, through, for instance, Essential's Jab order, into a memory-mapped control enlist. The term is normally used to depict a group of genuinely surely understood traps that can over-burden the simple gadgets in the CRT screens of PCs lacking equipment rational soundness checking (outstanding illustrations being the IBM Portable[1] and Commodore PET.The PET-particular executioner jab is associated with the engineering of that machine's video rasterizer circuits. In early PETs, written work a specific incentive to the memory address of a specific I/O enlist (Jab 59458,62[2]) made the machine ready to show message on the screen considerably speedier. At the point when the PET range was redone with refreshed equipment, it was found that playing out the old trap on the new equipment prompted interesting conduct by the new video chip, which could harm the PET's coordinated CRT monitor.[3]

Commodore 1541 Plate Drive[edit]

The Commodore 64 had a discretionary outside 5-1/4" floppy drive. The Commodore 1541 contained a 6502 microchip which was utilized to run Commodore DOS and furthermore to deal with the drive instrument. The drives put away information on 40 tracks (#0–39), and the stepper engine could be physically controlled through Essential by PRINT#-ing "MEMORY-State" summons to the drive (which compare to the Jab charge of Fundamental, yet keep in touch with the drive's inward memory and I/O registers, not those of the PC itself). On the off chance that the drive was at either end of its range (track 0 or track 39) and it was charged to keep moving, there was no product or firmware technique to forestall drive harm. Kept "thumping" of the drive head against the stop would toss the system askew. The issue was exacerbated by duplicate insurance systems that utilized non-standard plate positions with strange track checks. The Commodore 1571 had an optical head stop rather than a mechanical one.

TRS-80 Display III[edit]

The TRS-80 Show III had the capacity to switch between a 32 far reaching show and a 64-character show. Doing as such impelled a transfer in the video equipment, fulfilled by keeping in touch with a particular memory-mapped control register.[4] Projects that more than once exchanged in the vicinity of 32-and 64-character modes at rapid (either intentionally or unintentionally) could for all time harm the video hardware.[citation needed] While this is not a solitary "executioner jab", it shows a product disappointment mode that could for all time harm the equipment.

Tape relay[edit]

The TRS-80 Shading PC, IBM PC, IBM PCjr, Nascom, MSX, Amstrad CPC, and BBC Small scale from Oak seed PCs all contained an inherent transfer for controlling an outer tape recorder.[5] Flipping the engine control hand-off in a tight circle would diminish the hand-off's life span.

Commodore Amiga[edit]

The floppy drive of the Commodore Amiga PC could be made to create commotions of different pitches by making the drive heads move forward and backward. A program existed which could play El Cóndor Pasa, pretty much accurately, on the Amiga's floppy drive.[6] As a few sounds depended on the head gathering hitting the stop, this slowly sent the take off of arrangement.

LG Album ROM drives[edit]

Certain models of LG Album ROM drives with particular firmware utilized an anomalous summon for "refresh firmware": the "unmistakable support" order normally utilized on Cd RW drives. Linux utilizes this summon to differentiate between Disc ROM and Cd RW drives. Most Disc ROM drives constantly give back a blunder for the unsupported Album RW charge, yet the broken drives translated it as "refresh firmware", making them stop helpful working (frequently calmly referenced as the gadget having been "bricked").[7]

iPhone 5s and 6[edit]

On variants of iOS more established than v9.3, setting the date to January 1, 1970 (the Unix Age) will make the telephone stop working until the gadget's firmware is refreshed utilizing a computer.[8]

MSi Tablets UEFI[edit]

Systemd mounts factors utilized by Bound together Extensible Firmware Interface on Linux framework's sysfs as writable by the root client of a framework. Accordingly, it is workable for the root client of a framework to totally block a framework with a non-adjusting UEFI execution (particularly some MSi portable workstations) by utilizing the rm charge to erase the/sys/firmware/efi/efivars/index, or recursively erase the root registry.

No comments :

Post a Comment