• 0

[MS-DOS batch] 7zip Duplicate file error in different directories


Question

Hi,

I need to use some ms-dos batch files to run 7zip for making compressed backup. However, it treats it as duplicate file name error when there are files with same name but in different directories :cry: .

Error:

Duplicate filename:

abc.txt

abc.txt

The list file looks like:

d:\test\backup\abc.txt

d:\test\backup\sub\abc.txt

The batch file looks like:

dir /B /S d:\test\*.* >> fileList.lst

"c:\programe files\7-zip\7z" a -tzip test.zip @fileList.lst

Any idea to solve the problem?

Thanks,

petal

4 answers to this question

Recommended Posts

  • 0

well.. what you are doing there is just listing out the file names and adding them to a zip file..

you need to zip the root directory instead of adding individual files

i don't have 7zip to hand but perhaps try something like..

"c:\programe files\7-zip\7z" a -tzip test.zip "d:\test"

not 100% sure though ;)

  • 0

I am also receiving a duplicate file error -

Originally, an archive was created with these syntax parameters to archive my documents and settings folder each day and update any files that have changed to a slaved D drive:

7z u -tzip D:\DocumentsAndSettings.zip "C:\Documents and Settings"

The archive was created. I then wanted to clean the archive file using an exclusion list of file types and directories. This is the syntax I used:

7z d D:\DocumentsAndSettings.zip -ir@C:\exclude\exclude.txt

This was the contents of my exclusion list:

"Documents and Settings\*\Local Settings\Temp\*"

"Documents and Settings\*\Local Settings\Temporary Internet Files\*"

*.bak

*.tmp

*.mp3

*.wav

*.mov

*.avi

*.mpg

*.url

After attempting to clean the archive file using my exclusion list, I get the duplicate file name error. The error reports back with 2 file names with the same names and identical creation dates placed in the same directories in the archive file. There is only 1 file on disk. How did 7zip place identical files in the same directory?

Any help would be greatly appreciated!

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • And this is why I always wait at least a week after a Patch Tuesday before updating the servers. No headaches over here.
    • Windows is a scam for many decades, it's good if some people are realizing it now
    • Latest Patch Tuesday has broken DHCP Server in all Windows Server editions by Usama Jawad Microsoft released Patch Tuesday updates for Windows and Windows Server releases roughly a week ago, on June 10. In the latter, the release contained new functions for Narrator scan mode, along with tons of fixes for File Explorer, GDI+, Hyper-V, and more. At that time, Microsoft noted a known issue for Noto fonts, where Chinese, Japanese, and Korean text appears blurry or unclear under certain conditions. Now, it has highlighted another known issue following user reports. For the past couple of days, users on Reddit have been reporting issues with the DHCP service after applying the latest Patch Tuesday update. Apparently, rebooting the system fixes the issue, which can be understandably annoying. Now, Microsoft has updated the documentation for the June 10 release notes across Windows Server 2016, 2019, 2022, and 2025, to mention that the DHCP Server service may "intermittently" stop working after installing Patch Tuesday's update, which will impact IP renewal processes on client machines. Redmond has assured customers that it is working on a fix, which will likely be rolled out within the next few days. Of course, this problem is rather frustrating for IT admins, and that annoyance is reflected in the Reddit thread where customers are blaming Microsoft's software quality assurance practices. The fact that it's currently unclear when a fix will be rolled out may further add to customer grievances. For those unaware, the DHCP Server service in Windows is responsible for network management such as allocation and configuration of IP addresses in a centralized environment with robust logging and monitoring mechanisms. And for those keeping track, this is not the only Windows Server issue that has cropped up in recent memory. Last month, Microsoft pushed an out-of-band (OOB) hotfix to patch a Hyper-V bug that was plaguing the platform. Of course, one can argue that problems like these are happening because of incomplete testing, but it is also important to remember that Windows is running on hundreds of millions of devices all over the globe, so comprehensive test case coverage is very difficult, if not impossible.
    • And still, no Windows Hello support for protected "tabs" in the "old"/Win32 OneNote app, a feature that was available for a long time in the UWP version. Please, Microsoft, get back to feature parity...
    • Like jupe, for me, the most exciting news from Windows for a few weeks ( / months ?) now is the return of the clock in the taskbar calendar. I filed a feedback hub post so long ago about this. Finally!
  • Recent Achievements

    • Week One Done
      patrickft456 earned a badge
      Week One Done
    • One Month Later
      patrickft456 earned a badge
      One Month Later
    • One Month Later
      Jdoe25 earned a badge
      One Month Later
    • Explorer
      Legend20 went up a rank
      Explorer
    • One Month Later
      jezzzy earned a badge
      One Month Later
  • Popular Contributors

    1. 1
      +primortal
      617
    2. 2
      ATLien_0
      281
    3. 3
      +FloatingFatMan
      174
    4. 4
      Michael Scrip
      153
    5. 5
      Steven P.
      124
  • Tell a friend

    Love Neowin? Tell a friend!