Just curious: hub.c: connect-debounce failed

Discussion in 'Acronis True Image Product Line' started by FanJ, Feb 25, 2005.

Thread Status:
Not open for further replies.
  1. FanJ

    FanJ Guest

    Hi,

    Just only being curious about this message from Ti-8-796:

    hub.c: connect-debounce failed, port 1 disabled.

    I got this message when booting from the TI floppies.

    Everything went fine.
    I could make full backup-image to external USB-2 HDD.
    I checked the image with TI: OK.
    I did a test:
    I restored the image and tested with two file integrity checkers:
    1- NIS File Check on partition D checking several thousands of files with strong HASH: all OK (see the archived forum at the bottom of the forum for this checker);
    2- ADinf32 Pro on C, checking ALL files; saved its previous log; it was as usual run just before making the backup; rebooted etc and run ADinf32 Pro.
    Nothing unusual was found (meaning: for example of course the newer NIS File Check databases were found, the saved last log of ADinf32 Pro was found, IEClean took care of INDEX.dat etc).

    So, as I said, absolutely nothing unusual was found.
    (Note: in the past I compared also the Registry before and after; I didn't do that this time).

    So, only for my curiosity:
    What does that message from TI means?

    Many thanks in advance !
    Best regards, Jan.

    =====
    System:
    W 98 SE
    Mobo: Asus P2b
    P3 600 ; 512 MB RAM
    Internal HDD: WD with partitions C, D, E, F, G
    External HDD: Maxtor OneTouch USB-2 connected to Sitecom ComboCard USB-2/Firewire.
    Very old SCSI card connected to internal Plextors CD-ROM Reader and Writer.
    HP Printer (off) connected to Printer-port.
    Internet connection temporarily disconnected.
    External USB-1 hub, connected to peripherals as mouse, scanner, wingman.
    TI : running from its bootable floppies; backup-image on the external Maxtor USB-2 HDD.
     
  2. beenthereb4

    beenthereb4 Registered Member

    Joined:
    Jun 29, 2004
    Posts:
    568
    This was a failed (in my opinion) attempt to make build 796 more compatable with USB devices. The next build should do away with this and at least restore the previous level of compatability -- new build coming coming soon. As always YMMV.
     
Thread Status:
Not open for further replies.
  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.