![]() |
Quote:
|
aswadd the thing me curious but I have no other ideas or advice to give here.
|
Quote:
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 ?? |
1 Attachment(s)
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.
|
| All times are GMT -7. The time now is 21:56. |
Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2026, vBulletin Solutions Inc.
FileForums @ https://fileforums.com