Custom Query (16363 matches)
Results (2011 - 2013 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #7410 | obsolete | FrontRange enteo Agent crashes on Virtual Box clients | ||
| Description |
Currently it's not possible to manage Virtual Box Clients with FrontRange enteo v6. The related agent (niagnt32.exe) crashes during network access. Several attempts to fix this problem failed :-( For further details see http://forum.enteo.com/showthread.php?t=6656. This bug is sad because it makes people switch back to VMware or any other Virtualization platform - FRS enteo is working fine on each of these platforms! To shorten processing time of this bug please contact FrontRange Germany directly (located in Filderstadt) for any testing scenario. |
|||
| #14650 | invalid | Cannot install Windows 8.1 or Windows 10 as guest virtual machines | ||
| Description |
I have a Windows 7 host system that is used for testing deployments of our application on numerous target OS's. These include XP x86 and x64, Vista x86 and x64, Win 7 x86 and x64. These all installed fine and are running. Win 8.1 and Win 10 will not install. I have tried multiple solutions on the web with no luck. I temporarily put another hard drive in the computer and verified that Win 8.1 and 10 will install properly. The processor is an AMD Athlon II X2 B26 which supports AMD-V as well as SSE2. It's supposed to support NX but there is no place in the BIOS to set this. The BIOS only allows virtualization to be enabled/disabled. Line 550 in the log may be a clue because it seems to be misidentifying the CPU: 00:00:02.449392 CPUM: Matched host CPU AMD 0x10/0x6/0x3 AMD_K10 with CPU DB entry 'AMD Phenom II X6 1100T' (AMD 0x10/0xa/0x0 AMD_K10) Line 663 reports that NX/XD cannot be turned on so maybe that's another clue: 00:00:15.067232 CPUM: WARNING! Can't turn on NX/XD when the host doesn't support it! I've attached the log file. Thanks in advance... |
|||
| #5521 | obsolete | Pause/Freeze on y key-press | ||
| Description |
I'm pretty sure no one is going to take this seriously, but I have to try - I have enough anecdotal evidence. Running Ubuntu 9.04, VirtualBox 3.0.10 (though to be honest it was in the previous version too - 3.06). Windows XP is the guest. Not every time, but at least 4 out of 5 times, I type a 'y' in the guest (email, skype, etc) there is a short pause. Sometimes up to 3 seconds before the application responds.. The y is then not displayed and the subsequent keypresses (quite a lot if I'm typing quickly), all appear at once after some lag. This means when I type "you" I more often than not end up with "ou". I don't know what you need to pin this down - I'm using the host browser to create this ticket and haven't had a single issue with all the y's in this post. The key is seated properly and functions fine in the host session. |
|||

