problem with srep ?
 

Hi , I have a serious problem with srep // srep64
I used srep64+LZMA to compress red alert 3 & it was successful & decompression was successfull
But
Using srep64+LZMA or srep+LZMA to compress [ red alert 3 UPRISING ] it was successful
but decompression always Failed :confused::confused::confused:
Sometimes it gave me Disk is full Error however there are over 60GB Free disk space
Sometimes it gave me this error
-------------------------------
ERROR: write error (disk full?) in compression algorithm sreparc: read: invalid
argument (Bad file descriptor)
arc: CompressionLib_dbHm: interrupted
------------------------------
RA3 compression & decompression was successful
RA3 UPRISING compression was successful but decompression failed
the same problem with Command & Conquer 4

check if harddrive is not failing.also run a program called memtestx86.it run in dos but it the best to check faulty memory modules.do a full scan of the memory modules.should take a few hours any errors then you have you answer.

the problem is only when i try on Red Alert 3 Uprising & C&C 4 :confused::confused:
it doesn't happen with other games :\ so anyone try on C&C4 or RA3 UPRISING ??

try fazip
it gives good results
near SREP

I'm using Fazip :D But i'm wondering why srep won't work with red alert 3 uprising ?? is it because EA some protected files ?? or something Else

More than anything else you should check which file/s cannot be compressed with SREP in the game Red Alert III, much for be more precise.

all files compressed successfully but the decompression always failed :confused::confused: & RA3 Is working fine but the Uprising Red Alert 3 chapter is not working :\ Could you tell me how to know the file that cause this problem ... how to detect it ??

Then it in summary, did you try to decompress from the command line, and not with the installation used to verify the problem.
Post the arc.ini configuration that uses either for compression or decompress.
the information that you have given are few, we are not soothsayers the problem can be any.
You disable the antivirus during decompression / installation?
KS srep3.93b he sees it as a false positive.

That's right. Is the RAM!. Try to limit the ram usage in arc.exe.

http://i.imgur.com/35mwISG.png
It's not about antivirus because i compressed many games without errors but this one I can't understand why she is refusing to be decompressed with srep
I also tried many versions of srep but nothing changed & the same error

I limited it & again the same error
-ld2048

checked c: drive as well ?

Have you tried to test the archive "Arc t -i2" get the same error.

C: has 30 GB Free Disk space

D:\test>Arc t -i2 RA3UP.arc
FreeArc 0.67 (December 12 2012) testing archive: RA3UP.arc
Testing 548 files, 6,492,788,509 bytes
Testing clownBold.ttg
Testing dialoglogo128x128.jpg
Testing grass.tga
Testing LauncherSupport.dat
Testing lib_art.map
Testing patchw32.dll
Testing RA3EP1.exe
Testing ra3ep1.ico
Testing RA3EP1_english_1.0.SkuDef
Testing Red Alert 3 Uprising Trainer.exe
Testing VistaShellSupport.dll
Testing Data\Apt.big
Testing Data\clownBold.ttg
Testing Data\dbghelp.dll
Testing Data\dfe
Testing Data\en-us_eula.rtf
Testing Data\English.big
Testing Data\EnglishAudio.big 5.0%
ERROR: write error (disk full?) in compression algorithm srep


I'll try on other OS & maybe EA has some additional security with their files as i noticed during the setup

"Data\EnglishAudio.big 5.0%" .... compress and decompress only that

compression & decompression success on this file

aswadd the thing me curious but I have no other ideas or advice to give here.

try to change configuration srep arc.ini

pack:

[External compressor:srep]
header = 0
packcmd = srep -m3f -a1 $$arcdatafile$$.tmp $$arcpackedfile$$.tmp
unpackcmd = srep -d -s -- <stdin> <stdout>

[External compressor:srep64]
header = 0
packcmd = srep64 -m3f -d1g -a2 $$arcdatafile$$.tmp $$arcpackedfile$$.tmp
unpackcmd = srep64 -d -s -- <stdin> <stdout>


unpack:

[External compressor:srep64]
header = 0
packcmd = srep64 {options} -m3f -d1g -a2 $$arcdatafile$$.tmp $$arcpackedfile$$.tmp
unpackcmd = srep64 -d -s -- <stdin> <stdout>

[External compressor:srep]
header = 0
unpackcmd = srep {options} -d -s - - <stdin> <stdout>

Just limit the RAM usage -mem200mb, though I don't think it's going to fix the issue.

Make sure you're running a stable CPU and RAM clock. Programs crash on my side if I'm not running a stable clock instead of getting BSOD.

another pic O.o From Command & conquer 4 extraction
http://i.imgur.com/2MqkiOT.png
it gave me this things + strange sound like the one when opening the computer
But when i try to extract it again it extract without errors & without this strange things
what is going on ??

Freearc bug, if you have everything piped, you get that. Sometimes, it's just idiotic usage of pipe programs. This happens when stdout is redirected to stderr.