EMULAB Forum

Please login or register.

Login with username, password and session length
Advanced search  

News:

The new forum is online, hope you enjoy it!

Pages: [1]   Go Down

Author Topic: Problems rebuilding files starting with @ into 7z archives under Windows 7  (Read 9010 times)

Carl0s_H

  • Member
  • *
  • Karma: 0
  • Offline Offline
  • Posts: 6
  • Operating System:
  • Windows 7 Windows 7
  • Browser:
  • Firefox 3.6.13 Firefox 3.6.13
    • View Profile

As per the subject, I have found a few sets containing files starting with @ symbols. These fail to build/rebuild into 7z archives under Windows 7 Ultimate 64 bit, and produce the following error:



If I select Yes, the destination archive becomes corrupted. Selecting No, however, skips the problematic files without corrupting the destination archive.

Has anybody else had this problem? I searched the forums but couldn't find anything similar (unless I missed it).

Any replies appreciated.

Many thanks

Carlos
Logged


Roman

  • Global Moderator
  • Member
  • ***
  • Karma: 113
  • Offline Offline
  • Posts: 3292
  • Operating System:
  • Windows XP Windows XP
  • Browser:
  • Chrome 9.0.597.94 Chrome 9.0.597.94
    • View Profile

well, since cmpro simply calls the external 7z binary to add/remove files it seems that 7z got a problem with @ in filenames...

I can check this next week.



...or it's just you trying to add a file to a solid or locked archive...which fails since 7z can't do that with the given commandline options....and the @ doesn't play a role...
« Last Edit: 11 February 2011, 07:41 by Roman »
Logged

Carl0s_H

  • Member
  • *
  • Karma: 0
  • Offline Offline
  • Posts: 6
  • Operating System:
  • Windows 7 Windows 7
  • Browser:
  • Firefox 3.6.13 Firefox 3.6.13
    • View Profile

Hello Roman,

I think that might be the case.

I've checked, and 7z uses the @ symbol as a parameter to add a list of files to an archive, e.g. @filelist.txt

Maybe it's getting confused and thinking the input file is supposed to be a list...

I have checked the archive to which it is writing, and it is neither solid nor locked.

BTW, I never had this problem under XP. Worked perfectly with the same version of clrmamepro (3.137b), the same DATs and the same ROM input / 7z output files.

It's probably just Windows 7... I've noticed a few strange things.

Thanks for taking the time to look into this though, and thanks for writing such a fantastic tool :)

If you need any other information, please let me know.

Cheers

Carlos
« Last Edit: 11 February 2011, 19:58 by Carl0s_H »
Logged

Roman

  • Global Moderator
  • Member
  • ***
  • Karma: 113
  • Offline Offline
  • Posts: 3292
  • Operating System:
  • Windows 7 Windows 7
  • Browser:
  • Chrome 9.0.597.98 Chrome 9.0.597.98
    • View Profile

yep...it's looking for a filelist when the file is in the current folder and starts with @ (which is the normal case during working with 7z...it changes to the belonging folder).

Hmm....wonder if you can use quotes or any other escaping for such a case....
Logged

Roman

  • Global Moderator
  • Member
  • ***
  • Karma: 113
  • Offline Offline
  • Posts: 3292
  • Operating System:
  • Windows 7 Windows 7
  • Browser:
  • Chrome 9.0.597.98 Chrome 9.0.597.98
    • View Profile

Hmm...theoretically it should work if you change your 7z settings to:

a -y -r -ms=off -mx9 %1 .\%2


not tested yet....guess I can 'fix' it for a future release



....'Fixed' for the next version already...
« Last Edit: 15 February 2011, 20:46 by Roman »
Logged

Carl0s_H

  • Member
  • *
  • Karma: 0
  • Offline Offline
  • Posts: 6
  • Operating System:
  • Windows 7 Windows 7
  • Browser:
  • Firefox 3.6.13 Firefox 3.6.13
    • View Profile

Awesome, I'll give it a try and see what happens.  ;D

Update: Yes, that works perfectly now. Thanks for the help Roman :)
« Last Edit: 15 February 2011, 21:39 by Carl0s_H »
Logged

Roman

  • Global Moderator
  • Member
  • ***
  • Karma: 113
  • Offline Offline
  • Posts: 3292
  • Operating System:
  • Windows XP Windows XP
  • Browser:
  • Chrome 9.0.597.98 Chrome 9.0.597.98
    • View Profile

Well, the internal fix will work the same...if the filename starts with a @, it will internally use .\@...

guess it shouldn't make a difference if you keep the .\ ....then it will be .\.\@ ....shouldn't matter
Logged
Pages: [1]   Go Up
 

Page created in 0.198 seconds with 19 queries.

anything