none
Dongle problems in windows 7

    Question

  • Hello,

    I am trying windows 7 on my new computer wich specs are: i7 920, 6 gig ram, asus p6t v2 motherboard
    Everything works fine but only one program fails, its easysign pro, wich is a dutch program to use a cutting-plotter.
    The program won't run in windows 7, it gives the message "no supported os", i've called the manufacturer and they admit that and will fix it in a next version.
    BUT we also have the xp modus, and here it goes wrong.
    The program uses a usb dongle from aladdin, windows 7 recognizes it and calls it HASP 2.17.
    Well this is what happens in xp modus: i install the program in xp, then i insert the dongle in a usbport... windows 7 recognizes it and finds the driver.
    In xp modus, in the top of the screen you have to attach the usb device to the virtual machine. 
    When i do that, the dongle no more flashes (it flashes when its connected).
    In windows 7 the drivers changes to "virtualization stub driver" and in windows xp you get the driver "aladding usb key".
    But when i start the program in windows xp it keeps saying: can't find the dongle.

    Sorry for my bad english, i hope everyone can understand it.
    I hope someone haves a answer for me because i want to use windows 7, but without that program my computer is useless.
    Greetings, Bart from the Netherlands 
    Monday, June 22, 2009 8:56 PM

Answers

  • Thanks for sharing the logs. We have had a similar issue reported by other users for Aladdin USB dongle. We are working on addressing the issue.

    Regards,
    Devdeep
    Thursday, June 25, 2009 1:35 PM
    Moderator

All replies

  • Thanks for reporting the issue. Can you capture some logs and share them with us? This will help us in debugging the issue.

    1. On the host machine, from the command line (elevated) run the following command.
    logman start trace vpcusb -ets -o vpcusb.etl -nb 16 256 -bs 64 -max 256 -f bincirc -p {6692c45b-c0fb-4786-bc5c-33638678f709} 0xffff 0x05

    2. In the guest virtual machine (xp mode) run the command (again run it elevated)
    logman start trace vpcuhub -ets -o vpcuhub.etl -nb 16 256 -bs 64 -max 256 -f bincirc -p {9c38ca1e-b30e-4051-8762-ae492b35d1a6} 0xffff 0x05

    3. Attach the device to the guest virtual machine (xp mode) and repro the issue.

    4. Run the following commands on host and guest respectively
    logman stop vpcusb  -ets
    logman stop vpcuhub -ets

    Please share the vpcusb.etl and vpcuhub.etl (created in xp mode) files. You can mail these files to wcvdata@microsoft.com. Please mention this thread url, your screen name and mail id while sending these logs.

    Regards,
    Devdeep

    Tuesday, June 23, 2009 5:06 AM
    Moderator
  • Updating the steps (step 2) to capture the logs

    1. On the host machine, from the command line (elevated) run the following command.
    logman start trace vpcusb -ets -o vpcusb.etl -nb 16 256 -bs 64 -max 256 -f bincirc -p {6692c45b-c0fb-4786-bc5c-33638678f709} 0xffff 0x05

    2. In the guest virtual machine (xp mode) run the command (again run it elevated)
    logman start trace vpcuhub -ets -o vpcuhub.etl -nb 16 256 -bs 64 -max 256 -f bincirc -p {9c38ca1e-b30e-4051-8762-ae492b35d1a6} 0xffff 5

    3. Attach the device to the guest virtual machine (xp mode) and repro the issue.

    4. Run the following commands on host and guest respectively
    logman stop vpcusb  -ets
    logman stop vpcuhub -ets

    Tuesday, June 23, 2009 6:09 AM
    Moderator
  • Thank you very much, i have just send the two files to the mail adress.
    Hope to hear soon from you, maybe even with an answer :D
    greetings, Bart
    Tuesday, June 23, 2009 8:40 AM
  • Hello,
    I have a problem, i have send the mail and receive the message that it is undeliverable.
    Do you have a other mail adress or a other way how to send the files to you?
    This is the message i get:

    Diagnostic information for administrators:

    Generating server: microsoft.com

    wcvdata@microsoft.com
    #550 5.7.1 RESOLVER.RST.NotAuthorized; not authorized ##

    Original message headers:

    Received: from SVC-EXGWY-E801.partners.extranet.microsoft.com (10.251.24.242)
     by TK5EX14MLTC104.redmond.corp.microsoft.com (157.54.79.159) with Microsoft
     SMTP Server (TLS) id 14.0.601.1; Tue, 23 Jun 2009 01:43:04 -0700
    Received: from mail93-tx2-R.bigfish.com (65.55.88.112) by mail04.microsoft.com
     (10.253.160.184) with Microsoft SMTP Server (TLS) id 8.2.99.4; Tue, 23 Jun
     2009 01:43:01 -0700
    Received: from mail93-tx2 (localhost.localdomain [127.0.0.1])	by
     mail93-tx2-R.bigfish.com (Postfix) with ESMTP id 63249AC0290	for
     <wcvdata@microsoft.com>; Tue, 23 Jun 2009 08:43:00 +0000 (UTC)
    X-SpamScore: 13
    X-BigFish: ps13(zz9e12ne37lzz1202h1082k631jzz186Mz2fh6bh17ch180h21k34h62h)
    X-Spam-TCS-SCL: 1:0
    X-FB-SS: 5,5,5,
    Received: by mail93-tx2 (MessageSwitch) id 1245746578210096_1180; Tue, 23 Jun
     2009 08:42:58 +0000 (UCT)
    Received: from snt0-omc3-s2.snt0.hotmail.com (snt0-omc3-s2.snt0.hotmail.com
     [65.55.90.141])	by mail93-tx2.bigfish.com (Postfix) with ESMTP id
     20BD71A10055	for <wcvdata@microsoft.com>; Tue, 23 Jun 2009 08:42:58 +0000
     (UTC)
    Received: from SNT104-W57 ([65.55.90.136]) by snt0-omc3-s2.snt0.hotmail.com
     with Microsoft SMTPSVC(6.0.3790.3959);	 Tue, 23 Jun 2009 01:42:58 -0700
    Message-ID: <SNT104-W5787F0E43B576FF29FCB8C9E360@phx.gbl>
    Content-Type: multipart/mixed;
    	boundary="_cdc836a2-2d68-4761-8f2c-7f9421fbc024_"
    X-Originating-IP: [94.214.33.9]
    From: Bart Verhoeven <death_slasher@hotmail.com>
    To: <wcvdata@microsoft.com>
    Subject: Proplem with dongle in windows 7
    Date: Tue, 23 Jun 2009 08:42:57 +0000
    Importance: Normal
    MIME-Version: 1.0
    X-OriginalArrivalTime: 23 Jun 2009 08:42:58.0547 (UTC) FILETIME=[9C304C30:01C9F3DE]
    Return-Path: death_slasher@hotmail.com
    













    greetings, Bart
    • Proposed as answer by sharjgavhane Thursday, August 27, 2009 5:26 AM
    Tuesday, June 23, 2009 8:51 AM
  • Hello,

    Hopefully this helps, i have uploaded the two files to my webspace.
    so here's a link to the files, hope you can work with that:
    http://members.home.nl/twinsport/vpcuhub.etl

    http://members.home.nl/twinsport/vpcusb.etl

    hope to hear soon from you,
    greetings Bart
    • Edited by DutchUser Tuesday, June 23, 2009 9:16 AM
    Tuesday, June 23, 2009 9:12 AM
  • Thanks for sharing the logs. We have had a similar issue reported by other users for Aladdin USB dongle. We are working on addressing the issue.

    Regards,
    Devdeep
    Thursday, June 25, 2009 1:35 PM
    Moderator
  • Allright, hopefully this issue will be solved in the final version of 7.
    thanks for the replies.
    greetings Bart
    Thursday, June 25, 2009 8:12 PM
  • Hello Bart

    Thanks for the feedback. Could you please try the latest RC bits and let us know that your issue is resolved?


    Thanks, -Rahul -- "This posting is provided "AS IS" with no warranties, and confers no rights. You assume all risk for your use."
    Friday, August 07, 2009 4:40 AM
  • Hi ,
    I am having the same problem with my Aladin USB dongle. Even though it lights up and I have apparently installed the latest driver when I try to open my HOMPATH software it says that Hompath Classic MD usb key not found. My os is Windows 7 Home Premium 64 bit. It worked fine on Windows XP service pack 3 .
    Sunday, November 22, 2009 7:33 AM
  • If you are running a USB3 controller, I think that is your problem.  I had a similar issue with XP Mode not allowing me to attach a recognized HASP 2.17 dongle.  I went into my laptop's Hardware Setup Utility and simply disabled the Internal USB 3.0 Controller.  That reverted my USB ports back to USB 2.0 which XP Mode will recognize.  I re-booted my laptop, re-launched my XP Mode and was able to attach my dongle as well as a Serial-to-USB converter cable to run my old plotter and get to work!

    My laptop is a Toshiba with an i7 processor and USB3

    Hope this helps!

    Wednesday, November 14, 2012 8:13 PM