Opened 16 years ago
Last modified 8 years ago
#2141 closed defect
VB crashes when installing drivers for HASP SRM (Copyright protection USB dongle) — at Version 7
| Reported by: | Kristian Karl | Owned by: | |
|---|---|---|---|
| Component: | VMM | Version: | VirtualBox 1.6.4 |
| Keywords: | HASP crash | Cc: | |
| Guest type: | Windows | Host type: | Linux |
Description (last modified by )
I get a bluescreen when installing drivers for HASP SRM (Copyright protection USB dongle). The crash occurs always. I have repeated the crash on a XP, and Windows 2000 guests.
Test instructions:
- Start the guest OS (in this case XP)
- When guest OS is up running, fetch the latest driver from Aladdin from here
- Unzip the file, and run "HASP SRM Run-time GUI Installation"
Expected results:
- The installation of the drivers should ends successfully.
Actual results:
- During the istallation of the drivers, VirtualBox crashes
Change History (8)
by , 16 years ago
| Attachment: | VBox.log.gz added |
|---|
comment:1 by , 16 years ago
Sorry for the bad formatting above... I'll repost the description beneath:
VirtualBox crashes when installing drivers for HASP SRM (Copyright protection USB dongle). The crash occurs always.
I have repeated the crash on a XP, and Windows 2000 guests.
Test instructions:
============
1) Start the guest OS (in this case Windows XP)
2) When guest OS is up running, fetch the latest driver from Aladdin at: ftp://ftp.aladdin.com/pub/hasp/srm/Runtime_%28Drivers%29/HASP_SRM_Runtime_setup.zip
3) Unzip the file, and run "HASP SRM Run-time GUI Installation"
Expected results:
============
The installation of the drivers should end successfully.
Actual results:
==========
During the istallation of the drivers, VirtualBox crashes
comment:2 by , 16 years ago
Please note, that the actual hardware (the USB HASP dongle) is not necessary to repeat the crash.
comment:4 by , 16 years ago
| Component: | other → USB |
|---|
follow-up: 6 comment:5 by , 16 years ago
The problem is not related to USB. The problem appears to be in the instruction decoder of VirtualBox; the aksfridge.sys driver contains obfuscated code, which VirtualBox does not handle correctly.
comment:7 by , 16 years ago
| Component: | USB → VMM |
|---|---|
| Description: | modified (diff) |
Right. Please could you activate VT-x for that VM session? Note that VT-x seems to be disabled in your BIOS (according to the log you added) so please check your BIOS settings. And after doing so, please make sure that VT-x is indeed enabled for the VM by checking the session information window (HostKey+N).
VBox log file