I have a problem with extraction of files from a rar file. The rar is 92MB big and when I estract files have errors on random files. Sometimes happen also that all goes right. First I think that this was a windows xp fault (because I have 120G s-ata hd) but I try the extraction also on an p-ata hd and errors (crc errors and file not found) also appear. If I extract directly from cd-rom there is no erros.
Any help?
damjang
Problem with rar extraction
Moderators: Hacker, petermad, Stefan2, white
Is your system overclocked?
The thihg is that RAR archiving algorothm is very intolerant to errors. If your system is unstable for any reason (for example, because of overclocking), it will produce errors while archiving and unarchiving files. There is even a test for system stability - to create large RAR-archive on stable system and then test this archive on the new system for many times: if new system is unstable, it will be seen from CRC-errors while testing archive.
BTW, what version of WinRAR do you use?
The thihg is that RAR archiving algorothm is very intolerant to errors. If your system is unstable for any reason (for example, because of overclocking), it will produce errors while archiving and unarchiving files. There is even a test for system stability - to create large RAR-archive on stable system and then test this archive on the new system for many times: if new system is unstable, it will be seen from CRC-errors while testing archive.
BTW, what version of WinRAR do you use?
Flint's Homepage: Full TC Russification Package, VirtualDisk, NTFS Links, NoClose Replacer, and other stuff!
Using TC 11.03 / Win10 x64
Using TC 11.03 / Win10 x64
No, my system is not overclocked. I have a rar file a friend of mine burn on cd and I want to extract. I use only internal tc rar plugin. I do a lot of test and my conclusion is that this is a system error (I randomly have read erros also in other applications!). If someone can help I have MSI KT6 mb with XP2800+ cpu, 512MB PC400 ram, winXP SP1, HD Sata 120GB maxtor...
damjang
damjang
Maybe just a ribbon connecting HDD to MB is damaged, or HDD may be out of order (does it work louder/slower than before?).
Check if you do not have a virus. And maybe disable DMA mode of HDD.
Eventually it might be a RAM error (memory module is broken). If you can, try to replace memory module. Or maybe it is a mainboard error.
I recommend replacing HDD or memory modules and then test how it works.
The similiar and weird problem I had was with some MSI Intel mainboard (but only one specific model with chipset 805 or something like that and it occured on three computers) that worked correctly with 64MB of memory, and when you added 128MB or more than such errors occured.
TC helped a lot to detect such problem and to perform tests:
Select a directory that has at least 200MB of data. Do not perform any writings in this directory - so it should not be Windows or Program Files directory). Compress it to the zip archive (with TC internal packer) and Set the compression level to 0 (store, no compression). Then after compressing is done, enter into the archive an use the function "menu Command / Synchronize Dirs" , select "Subdirs" and "compare by content" then start comparing. TC will check every single bit of these file and inform you if any files differ. Normally all files should be the same (=).
If you have a problem with hardware then comparison will randomly show errors. If you compare again - there may be no difference, as read errors occur only sometimes.
Another thing is to compare two copies of large file (>90MB or more - the bigger the better - or you can copy that created ZIP file and compare just two files, not ZIP content) with "menu File / Compare by content" - it may show what is wrong. In my case the difference was only in the highest bit of random bytes. Error occured once per circa 10MB of data. It changed e.g. 00h to 80h or 7F to FF or 37 to B7 or reverse (80h to 00h) - just the highest bit was sometimes lost. Weird, isn't it?
Check if you do not have a virus. And maybe disable DMA mode of HDD.
Eventually it might be a RAM error (memory module is broken). If you can, try to replace memory module. Or maybe it is a mainboard error.
I recommend replacing HDD or memory modules and then test how it works.
The similiar and weird problem I had was with some MSI Intel mainboard (but only one specific model with chipset 805 or something like that and it occured on three computers) that worked correctly with 64MB of memory, and when you added 128MB or more than such errors occured.
TC helped a lot to detect such problem and to perform tests:
Select a directory that has at least 200MB of data. Do not perform any writings in this directory - so it should not be Windows or Program Files directory). Compress it to the zip archive (with TC internal packer) and Set the compression level to 0 (store, no compression). Then after compressing is done, enter into the archive an use the function "menu Command / Synchronize Dirs" , select "Subdirs" and "compare by content" then start comparing. TC will check every single bit of these file and inform you if any files differ. Normally all files should be the same (=).
If you have a problem with hardware then comparison will randomly show errors. If you compare again - there may be no difference, as read errors occur only sometimes.
Another thing is to compare two copies of large file (>90MB or more - the bigger the better - or you can copy that created ZIP file and compare just two files, not ZIP content) with "menu File / Compare by content" - it may show what is wrong. In my case the difference was only in the highest bit of random bytes. Error occured once per circa 10MB of data. It changed e.g. 00h to 80h or 7F to FF or 37 to B7 or reverse (80h to 00h) - just the highest bit was sometimes lost. Weird, isn't it?
Is the rar file on CD the same as the rar file you try to extract on your hd?
The included unrar.dll does not work on rar archives having newer packing method than unrar.dll. So before doing any more speculations try to extract the file with WinRAR. If it works, it's unrar.dll incompatibility, maybe there's a newer version on WinRAR website.
If the file on CD is the same as that on hd:
Clean your temp folder.
Free up some space on the drive containing your temp folder, these errors can occur when space gets too low to unpack all files contained in archive.
Best is, post a screenshot of the occuring errors and have a look in the log file (when WinRAR gives the same errors...).
Icfu
The included unrar.dll does not work on rar archives having newer packing method than unrar.dll. So before doing any more speculations try to extract the file with WinRAR. If it works, it's unrar.dll incompatibility, maybe there's a newer version on WinRAR website.
If the file on CD is the same as that on hd:
Clean your temp folder.
Free up some space on the drive containing your temp folder, these errors can occur when space gets too low to unpack all files contained in archive.
Best is, post a screenshot of the occuring errors and have a look in the log file (when WinRAR gives the same errors...).
Icfu