Error bad archive

error bad archive

www.mail-archive.com › [email protected] › msg1820401. Fixed by updating ubuntu img, as per the problem caused by the ethernet driver on the laptop. Recent reinstallation kali, Find a problem you've never met before, Report the wrong question : bad archive mirror. Install the error.

Consider, that: Error bad archive

FATAL ERROR CLASS ZIPARCHIVE DLE
Smtp error the following recipients failed php
Sub-process /usr/bin/dpkg returned an error

You can watch a thematic video

Ubuntu: \

What does a PC-DMIS: "Error PC: File closed because of a bad archive" message mean?



Symptoms:
   PC-DMIS will launch fine, but upon selecting a part program / measurement routine to open, the bad archive error is received.

Cause:
   This message may occur after an update, install, hard-drive replacement, or any major computer system change (like upgrading to Windows 10).  
The directory with the part programs/measurement routines (*.prg files)  is not being seen/accessed by PC-DMIS, or the directory is empty and the files need to be copied into it.  The files may also be present but unreadable - for instance, a crash in PC-DMIS might cause the files to be corrupted to the point of no recovery.

Other things to try:

  • If there are files present and this message persists, check the size of the files. If the files are only 1 or 2 kb, then they are likely error bad archive and you will need to replace them with your backup files (see below).
  • If the original *.prg file has become corrupted/unreadable, error bad archive, check to see if there is a backup file in the same directory.  This file will have the same name with a ^ or ~ at the end of the filename.  Change that name and remove the ^ ~ symbols so as to not error bad archive the original corrupted file (for example: Test.prg^  or Test.prg~ to NewTest.prg).  This may help as an alternative solution to restore functionality.
  • Check and see if the folder holding the part program has become set to read only.  
  • When running PC-DMIS, make sure you right-click and "Run as Administrator" (or set this up permanently).
  • If upgrading Windows, PC-DMIS may need to be reinstalled.

Note:The path for files has changed with PC-DMIS 2016. The folder "WAI" has been replaced by "Hexagon".

Where it previously was
C:\Program Files\WAI\PC-DMIS 2015.1 64-bit
is now:
C:\Program Files\Hexagon\PC-DMIS 2016.0 64-bit 

Likewise, for Parts Programs/Measurement Routines: 
C:\Users\Public\Documents\WAI\PC-DMIS\2015.1
is now: 
C:\Users\Public\Documents\Hexagon\PC-DMIS

These articles may have further useful information:

What are the ".PRG~" and ".PRG^" files?
Common PC-DMIS files and their locations
Where are my PC-DMIS files stored?


Known Versions: PC-DMIS 2015.1
(Topic ID 16101-1127)

Kali installation is the solution to bad archive mirror

Recent reinstallation kali, Find a problem you've never met beforeBy looking up some information, we finally solved error access violation at - program terminated problemerror bad archive, Also write out my method to solve this problemI hope more people can help this problem .

Report the wrong question :
Install the error reporting interface :
 Insert picture description here
When installed kali This is a problemChoose. At this time :
error bad archive Insert picture description here ">
And then chooseClick on :
 Insert picture description here
Then the following error bad archive appearsContinue clicking :
 Insert picture description here
Wait patiently for installationWhen the following interface appearschoiceerror bad archive, Then continue to click :
 Insert picture description here
When you jump to the following interfacechoiceContinue clickingRemember to choose here OptionsOtherwise, after installationIt's a black screenCan only be reinstalled from .
 Insert picture description here
The above is what I encountered during installation bad archive mirror Solutions for .

I am trying to install Debian 8.8 as a VM on a Windows 10 machine, Hyper-V.  I have downloaded the appropriate version, created the VM and Virtual Switch.  I started to install the OS from an IOS file and all went well until I had to connect to a mirror site.  No matter what site I visited I received the following error.

I was initially trying to connect to ftp.us.debian.org.  I can ping this address successfully and connect to it from a browser but not during the VM install.

I have looked up this problem and have eliminated all of the possible suspects but still the install fails to install the GUI version of the OS.  It just seems to complete a basic install, what appears to be just a CLI, but even this doesn't look correct as no commands can be run from the CLI.

Has anyone have any suggestions?


  • Maybe you are having a network configuration issue during the installation process.  Like not getting DHCP, being behind a proxy, an IP conflict, error bad archive, etc.

    Was this post helpful?thumb_upthumb_down
  • Scott Alan Miller wrote:

    Maybe you are having a network configuration issue during the installation process.  Like not error bad archive DHCP, being behind a proxy, an IP conflict, etc.

    It gave me an error message about DHCP to begin with, error bad archive, (why I don't know because the network is set to DHCP.)  I double checked the settings and I don't see any DHCP issues, I am not behind a proxy and I know I am not having any IP conflict.

    Once I checked the DHCP error I cancelled the install and tried it again.  This time I didn't get the network configuration error.  Now just the Mirror issue.
  • When you tried the install again, did you reformat the drive and completely start over? Eliminating any remnant install.

    flagReport

    0 of 1 found this helpfulthumb_upthumb_down
  • BBigford wrote:

    When you tried the install again, did you reformat the drive and completely start over? Eliminating any remnant install.

    No.  I am installing it onto a VM.
  • Did you look in /var/log/syslog or virtual console 4?

  • Could be couple of things. 2 major ones are. A) you are not getting ip details, try setting static and see if that fixes. B) you do not have vm protocol in your network connection on host machine

  • pigdog wrote:

    Did you look in /var/log/syslog or virtual console 4?

    Yes and no.  Just where is this located?  I have never seen this before and can't fine anything about it on the host machine.  I can't find any reference to where it is located anywhere. error bad archive tried checking the VM but can't find any files or folders at all.  I am guessing that it's because the VM hasn't installed correctly and I am only getting a base image.
  • Steveuk260 wrote:

    Could be couple of things. 2 major ones are. A) you are not getting ip details, try setting static and see if that fixes. B) you do not have vm protocol in your network connection on host machine

    I tried a static IP which met with failure.  I figured the protocol is error bad archive since I downloaded the ISO with no problem.  However the Virtual Switch keeps saying that I have a slow connection, which I don't.  Can you be a little more specific about what you are error bad archive to when it comes to the VM Protocol?
  • I don't know if this is the first time you have done something like this, but when I do activities like this I like to follow someones guide such as:

    http://www.brianlinkletter.com/installing-debian-linux-in-a-virtualbox-virtual-machine/

    It gives reassurance and a check list that we are following a proven procedure.

    Was this post helpful?thumb_upthumb_down
  • SteveFL wrote:

    pigdog wrote:

    Did you look in /var/log/syslog or virtual console 4?

    Yes and no.  Just where is this located?  I have never seen this before and can't fine anything about it on the host machine.  I can't find any reference to where it is located anywhere.  I tried checking the VM but can't find any files or folders at all.  I am guessing that it's because the VM hasn't installed correctly and I am only getting a base image.

    If the virtual console from which you were installing is still available, error bad archive, try pressing <alt><F4> or <ctrl><alt><F4>.  I'm not really sure how this will behave with Hyper V.

    An installed linux will have a number of alternate consoles for interacting with a physical monitor/keyboard.   Try all of them by pressing <alt><F2>, <alt><F3>, etc.  One of the virtual consoles might be running an interactive shell, which would allow you to cd into /var/log to see if there's any helpful messages that have been logged.

    Was this post helpful?thumb_upthumb_down
  • 2300peterw wrote:

    I don't know if this is the first time you have done something like this, but when I do activities like this I like to follow someones guide such as:

    http://www.brianlinkletter.com/installing-debian-linux-in-a-virtualbox-virtual-machine/

    It gives reassurance and a check list that we are following a proven procedure.

    I have done this several times without issue, error bad archive, but admittedly never with Linux.  I am using Hyper-V, not Virtualbox so I don't know if this link will help, but I'll check it out. Thanks.
  • pigdog error bad archive wrote:

    pigdog wrote:

    Did you look in /var/log/syslog or virtual console 4?

    Yes and no.  Just where is this located?  I have never seen this before and can't fine anything about it on the host machine.  I can't find any reference to where it is located anywhere.  I tried checking the VM but can't find any files or folders at all.  I am guessing error bad archive it's because the VM hasn't installed correctly and I am only getting a base image.

    If the virtual console from which you were installing is still available, try pressing <alt><F4> or <ctrl><alt><F4>.  I'm not really sure how this will behave with Hyper V.

    An installed linux will have a number of alternate consoles for interacting with a physical monitor/keyboard.   Try all of them by pressing <alt><F2>, error bad archive, <alt><F3>, etc.  One of the virtual consoles might be running an interactive shell, which would allow you to cd into /var/log to see if there's any helpful messages that have been logged.

    I'll give this a shot.  Thanks.
  • The other thing is once your in a shell.  Check your networking.  

    BASH

    cat /etc/network/interfaces

    gives you net device configuration

    Gives network device information (you should see an eth0)

    and lastly use ping to check connectivity both locally and internet; (I normally ping gateway address, google.com and 8.8.8.8)

    If its something related to you hypervisor (hyper-v in your case) others may have better ideas as I've only deployed under baremetal, KVM, and Xenserver

  • Do you use a content filtering Firewall perhaps? We have one and it blocks several CentOS mirrors.

    Is the Hyper-V host able to access ftp.us.debian.org?

    I'm not familiar with Debian installs, but can you run it live from the ISO versus installing? If so I'd try that and retest accessing ftp.us.debian.org.

  • Even tho you're working in a virtual environment start looking at it from the OSI model perspective.

    Check that your VM settings are correct to allow a connection and work up from there.

    If you think everything is correct boot a live debian install and see if the network is working. Maybe the issue is the controller presented is not supported by debian.

  • I had the same problem, after many tries I simply finished the installation putting grub in place.

    Then after rebooting the virtual machine, was having still error 142, so I did

    dpkg-reconfigure apt

    and everything was fine after

    Was this post helpful?thumb_upthumb_down
  • I had the same issue. Trying on another computer was working well. Finally I figured out that the problem was caused by the BIOS time of my computer which was 3 minutes out of sync. After manually adjusting that it worked fine.

    To error bad archive a proof of concept, I went to the other computer. I changed there the BIOS time so that it was wrong and indeed, I received the BAD Archive mirror error again. 

    I hope this helps for some.

    Was this post helpful?thumb_upthumb_down
  • i had exactly the same errors using the standard debian iso and virtualbox. after a few trials with multiple laptops and isos i fanally got a xampp error - 1 install.

    forget the standard debian ISO !

    1. get a net install debian iso

    2. put it in your vm as a cdrom image

    3. follow the install procedure (graphical or not)

    4. enjoy

    so it leads to the conclusion that the standard cdrom iso may encounter some stragne behaviours using virtualbox. no time to inspect further.

  • I'm sure Steve has already solved this problem by now but for others that find this thread I solved this problem in VirtualBox by changing the network connection from NAT to Bridged mode prior to installing Debian.

    1 found this helpfulthumb_upthumb_down

Bad archive error bad archive error when installing Kali 2016 64 bits

This is the error I get during graphical installation from live USB on 64 bits v2016 Kali version:

Screenshot: Kali Linux live v2016 installation error

Any other country mirror yields the same error, error bad archive. Even changing the original file:

To a newer one:

. does not solve the problem neither. The file seems not to show any mirror or repositories info (I can post it anyway if requested).

Tested:

  • Kali Live v2016.1.
  • Kali Live v2016.2.
  • On two computers: a portable Lenovo G50-45 and a desktop rather old HP Compaq.
  • Tested booting both USB and DVD live versions.

The Kali Forums don't show the solution, or I have not been able to find it.

How could I solve this error?

asked Nov 2, 2016 at 20:46

user avatar
error bad archive

1 Comments

Leave a Comment