| Forum |
|
|||||||
| Tutorials This section offers tutorials and How to's on just about anything related to computers and IT. Note: All tutorials are courtesy the posters and not verified by Digit |
![]() |
|
|
LinkBack (1) | Thread Tools | Display Modes |
|
|
#1 (permalink)
|
|
Alpha Geek
Join Date: May 2005
Posts: 687
|
Bug in the download manager. Bad proxy server. Bad web server. Problems with your own computer. Re-downloading corrupted files, specially those sized over 500 MB are really painful for most of us. And there is no guarantee that the re-downloaded file will be free of corruption as far as you are using the same configuration. In such cases, its best to fix them manually instead of downloading again. The whole process is very simple, but requries enough concentration. Once you have mastered it, you will never have to worry about corrupted files. Tools Required: WinHex _http://www.winhex.com/winhex.zip CURL _http://curl.haxx.se/latest.cgi?curl=win32-nossl-sspi CommonSenseâ„¢ (I don't have any link for this one) Steps required in brief: Make a backup copy of the corrupted file and open it with WinHex. Identify corrupted segments. Large sequences of zeros are all we have to search for in most cases. Re-download the corrupted segments with CURL. Write the retrieved data on appropiate offsets. Step-by-step example: Let us assume that we have a corrupted file named corrupted.rar. We open it WinHex, and do the following things: Switch the offset representation from hex to decimal by clicking once on the offset area. ![]() Now we search for corrupted segments. Most of the time they will be sequences of zeros. As we can see from the first bytes of the opened file, it's a rar file. Files we download over the Internet are mostly compressed formats. By design, a fresh file should not contain sequences of zeros or other repeating bytes after the header part. So, we scroll a few pages down. ![]() Now we start searching for such sequences with CTRL+ALT+F. ![]() The search takes us to a place where we can see some zeros and repeating bytes. Surely this is one of the corrupted segments. ![]() So, now we have to download the missing data using CURL. It's always a good idea to retrieve the data with some margin. In our case, we get the bytes from 01094304 to 01094512 in order to cover the screenshot size. In real case it should be even higher. So, we start command prompt and issue the command "curl -r 1094304-1094512 _http://badserver.com/mygoodfile.rar -o 01094304.bin" to download the mentioned segment of the original file, and save it to a file named 01094304.bin. For details, curl manual can help. After it's done, curl will terminate and we will have our file 01094304.bin right inside CURL's folder. ![]() Now we open the downloaded segment 01094304.bin with WinHex. Copy the whole file with CTRL+A -> CTRL+C. ![]() Switch back to our corrupted file and go to the starting offset of our retrieved segment. CTRL+G -> 01094304 ![]() Now press CTRL+B to write the copied data over this offset. It is very important to determine correct offset. One offset left or right can ruin everything. Our retrieved segment starts with 18 1E BD 3D, and the offset we are going to write here also starts with 18 1E BD 3D. ![]() After we are done, we save the file using CTRL+S. For larger files, it is better to switch the edit mode to in-place mode. F6 -> In-place mode. Now we can see that the corrupted part has been filled with original data, and it's fixed. In this example we had only of such segment. But in real cases, there might be several segments like this. In that case the whole procedure is to be repeated for each corrupted segment. Also note that, the length of zero sequences to find for can be chosen to be smaller or larger than the length used here. TRY IT....
__________________
Any use of the collective descriptions and shared knowledge from any of my posts are at the sole discretion of the reader.I am not responsible for what you do with it. |
|
|
| Advertisements. Register and be a member of the community to get rid of them. | |
|
Advertisement
|
|
|
|
#2 (permalink) |
|
Broken In
Join Date: Nov 2004
Location: Latitude:13.083 Longitude:80.283
Posts: 137
|
Great tut man!...
P.S. : A small software can be made for the steps you mentioned using vb or any such. It will be much more easier to fix them. I too willl try on it. |
|
|
|
|
#9 (permalink) |
|
Alpha Geek
Join Date: Jan 2005
Location: earth
Posts: 801
|
thnx rajas700
this is da best tut i have ever seen here is da workin link 4 CURL http://curl.haxx.se/download/curl-7.15.1.zip
__________________
signature??? |
|
|
|
|
#13 (permalink) | |
|
GUNNING DOWN TEAMS
Join Date: Mar 2005
Location: MUMBAI
Posts: 1,724
|
Quote:
PS- this rajas700 has 600 od posts to his name means had been member for long time and also knows the rule sof forum......he has a banned tagged.....may be broken rules.....but y do old members do break the rules? :roll:
__________________
The moment U stop learning ......u stop improving |
|
|
|
|
|
#17 (permalink) |
|
In The Zone
Join Date: Jan 2005
Location: Mushroom KiNGDOME!
Posts: 425
|
this TUT rox!
thanks m_p :mann.. i hate this limit
__________________
The name is Mario, "Mario Pant"! mario = avatar; pant = पतलून and i'm NOT some mountain KiD! |
|
|
|
|
#19 (permalink) |
|
Right Off the Assembly Line
Join Date: Jan 2006
Posts: 8
|
Works great for my 100 mb download file
Just some instructions : After you have downloaded curl from the link extract it to windows\system32 and in start=> run=> curl -r 1094304-1094512 http://badserver.com/mygoodfile.rar -o 01094304.bin . In orginial post there is underscore (_) here : 1094512 _http but it works without underscore Last edited by Dharmil; 09-07-2006 at 10:12 PM. |
|
|
![]() |
| Bookmarks |
| Thread Tools | |
| Display Modes | |
|
|
LinkBacks (?)
LinkBack to this Thread: http://www.thinkdigit.com/forum/tutorials/17841-do-not-download-large-corrupted-files-again-fix-them.html
|
||||
| Posted By | For | Type | Date | |
| Can we repair corrupt .exe file | This thread | Refback | 07-02-2011 03:27 PM | |