Hitachi(IBM) HDD Firmware Download

Here you can download Hitachi(IBM) firmware collections, you can make use of them as donor for your damaged hard drives or your Hitachi(IBM) harddisk firmware update!

Hitachi(IBM) firmware:
4212,4240,5410,5412,5416,5425,5480,7260,atmo

,atmr,aver,avv2,avvn,dara,dbca,dcya,djsa,dkla,dla3,dtca,dtla,dyla,pla3 series

firmware free download!

Hitachi Deskstar 180GXP Family (20,30,40,60,80,120GB) Hard Drives
FW update for HTS5480xxM9AT00 mobile hdd(20->80Gb)
FW update : IBM IC25T060ATCS05 (60GB) Mobile Hard Disk Drive
firmware update Travelstar 14GS/10GT/6GN ATA Mobile 2.5
PLA3-PF2OA6FA-HDS728080PLA38040Y9028LEN
PLA3-P21OABEA-HitachiHDS721680PLA380
IC35L090AVV207-0-V23OA66A-VNVC02G3DT1DZT
IC35L060AVVA07-VA3OA50K
IC35L060AVV207-0-V22OA66A
IC35L060AVV207-0-V22OA63A-VNVB03G2GGPSRJ
IC35L060AVER07-ER6FA46A
IC35L060AVER07-ER60A46A
IC35L060AVER07-ER60A44A
IC35L040AVVN07-0-VA2OAF0C-VNP210B2G86DTB
IC35L040AVVN07-0-VA2OAF0C-VNP210B2G7YYBB
IC35L040AVVA07-0-VA2OA52A-VNC212A2GXY2UB
IC35L040AVVA07-0-VA2OA52A-VNC202A2L6AERA
IC35L040AVER07-ER40A46A
IC35L040AVER07-ER40A45A
IC35L040AVER07-ER40A44A
IC35L040AVER07-0-ER4OA46A-SXNSX199624
IC35L040AVER07-0-ER4OA44A-SXPTXP43070
IC35L040AVER07-0-ER4OA44A-SXNSX199624
IC35L040AVER07-0-ER4OA44A-SX0SX042770
IC35L030AVER07-ER30A45A
IC35L030AVER07-ER30A44A
IC35L020AVER07-ER2FA44A
IC35L020AVER07-ER20A46A,IC35L020AVER07-ER20A45A
IC35L020AVER07-ER20A44A,IC35L010AVER07-ER1FA44A
IC35L010AVER07-ER10A44A,IC25N080ATMR04-0-MO4OAD4A-MRG405K4H0AS9H
IC25N080ATMR04-0-MO4OAD4A,IC25N040ATMR04-0-MO2OAD4A-MRG257KBEV9DGH
IC25N040ATMR04-0-MO2OAD4A,IC25N030ATDA04-0-DA4OA70A
ic25n010atda04,IBM-DTLA-307045-TX6OA50C-YMDYMH34857,IBM-DJSA-210

Hitachi(IBM) Firmware Download

Read More

JPEG Files

JPEG FilesNext we will look at carving JPEG graphic files, as specified in the document “Description of Exif file format.” For complete details of the file format specification, please refer to the hyperlink to the document, listed on page 1 of this paper.

The JPEG graphic file starts with a Start of Image (SOI) signature of “FF D8”.  Following the SOI are a series of “Marker” blocks of data used for file information.  Each of these “Markers” begin with a signature “FF XX”, where “XX” identifies the type of marker.  The 2 bytes following each  marker header is the size of the marker data.  The marker data immediately follows the size and then the next marker header “FF XX” immediately follows the previous marker data.  There is no standard as to how many markers will exist, but following the markers, the signature “FF DA” indicates the “Start of Stream” marker.  The SOS marker is followed by a 2-byte value of the size of the SOS data and is immediately followed by the Image stream that makes up the graphic. The end of the image stream is marked by the signature “FF D9”.

In the event that a thumbnail graphic exists within the file, the thumbnail graphic will have the exact same components as the full-size graphic, with “FF D8” indicating the start of the thumbnail and “FF D9”, indicating the end of the thumbnail.  Since thumbnails are significantly smaller and less likely to experience fragmentation than their larger parent full-size graphic, they can be used as a comparison tool for evaluating what the entire jpeg graphic is supposed to look like, in the event you must do a manual visual review of the carved graphic.

By searching first for all locations of the “FF D8 FF” signature, you identify the beginning of each jpeg graphic. The reason for searching for “FF D8 FF” is that there are different versions of jpeg  files, some that start with “FF D8 FF E0” and some with “FF D8 FF E1”, and leaving off the 4th byte in your signature will catch all instances, but may result in some false hits.

Rather than carve a specific length of data, in this case we will start at the beginning signatureand carve until we find “FF D9”.  In the event of a non-fragmented jpeg graphic, without a thumbnail, this will carve the whole file.  If we slightly modify our logic, by including a “if  “FF D8” occurs again before “FF D9”, then carve to the 2nd instance of “FF D9″” statement in our search for jpegs, then we will carve entire files including their thumbnail as long as they are not fragmented.  Without this “if” logic, the first search would stop carving at the end of the thumbnail and result in an invalid jpeg.  In the event of a fragmented jpeg file, the above carving method results in either a partial jpeg file or a complete jpeg file that contains extraneous data in the middle of it.

After carving all jpeg files based on these rules, we next quickly review which carved jpeg files are complete, versus which ones are fragmented and need further analysis.  By carving all jpeg files to a folder, you next add that folder to your forensic tool that has partial graphic file viewing capabilities, such as the “Outside In” viewer that is built into many existing forensic tools.  Using a gallery view, you can quickly identify which files are not displaying properly, only showing a partial file, and require further analysis.

Once all fragmented or partial jpegs are identified, manual visual inspection of each of these files was used to determine at what point the fragmentation occurred.  This was done by approximating the percentage of the file that displayed correctly in the viewer before displaying  corruptly.  The raw data of the carved file was then reviewed at the data at that percentage of the file to attempt to identify where the valid graphic data ended.  For this process it was assumed that the extraneous data started at an offset that was a multiple of 512-bytes from the beginning of the file.  Once the extraneous data was identified, it was then removed from the partial jpeg and re-evaluated as possible sector data for other fragmented files that had previously been identified

Read More

Top 10 worst computer viruses (Part Two)

10. Elk Cloner
Iain Thomson: Elk Cloner was written by a 15-year old high school student called Rich Skrenta as a practical joke. Unfortunately for him the joke turned bad very quickly.

The virus was developed for the Apple II system and was a boot sector virus that spread via floppy discs. Apparently Skrenta was a fan of pirated games and would swap them with his friends, sometimes with little messages added. After one too many of these infected discs, he devised a way to alter discs automatically and the Elk Cloner virus was invented.

It had little in the way of a payload. Every 50th time a person booted an infected disc the software ran a little program on the computer screen, and that was it. Nevertheless it was a serious annoyance and was a harbinger of things to come.

Shaun Nichols: And they say Apple computers don’t get viruses. What Skrenta did not realise was that he was helping to popularise what would later become standard practice for spreading viruses.

Elk Cloner spread through what is now known as a ‘boot sector’ infection. The virus copied itself into the boot sector of a floppy disk and then spread into all future disks. This became a popular attack method for Apple and PC computers, taking over as the preferred method of infection until the internet came along and email attacks emerged.

9. Klez
Iain Thomson: Klez is a persistent little devil, and variants are still doing the rounds today, seven years after it first turned up.

The most common varient, Klez H, spoofs email addresses by randomly picking one from an infected machine before sending itself on to other users. This makes backtracing the identity of the infected machine particularly difficult, since any email stored for any reason can be used.

It exploits a vulnerability in Outlook that allows it to boot up automatically on unpatched systems. It’s a cunning little devil but for all its ingenuity I still want to strangle the writer.

Shaun Nichols: The late 1990s and early 2000s were not only the golden age of the internet, they seemed to be the golden age for malware. Over that time period, few viruses were able to match the reign of Klez.

Like many other viruses of its time, Klez spread through email. Users were duped into opening infected files and, once the malware was installed, the victim’s address book was opened and copies of the attack were sent to contacts.

Klez, however, took this a step further. Not only did the virus send itself to people in your address book, it pretended to be from other people. Later, the worm wreaked further havoc by pretending to be its own removal tool.

Read More