Custom Query (16363 matches)
Results (1075 - 1077 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #13606 | invalid | problem mavericks guru meditation | ||
| Description |
hi my problem is that the system mac mavericks seneva in meditation gurus said my program to send the logs of the machine then here is the link with all the folder please let https://mega.co.nz/#F!zRknAIyI!lCUGrffyyAz4n3Bxv835Fw tell me what is the problem please let !!!! |
|||
| #989 | worksforme | problem in build: zlib is referenced but absent in the trunk | ||
| Description |
In the latest revision (6140) there are references to zlib. But zlib itself is missing.
When compiling there were errors (zlib.h missing).
I tried to copy zlib from zlib.org to vbox\src\libs\ (and renaming it from 1.2.3 to 1.2.1). The result is: compilation successful, but when linking, error:
kmk.exe[3]: * No rule to make target |
|||
| #8532 | fixed | problem in 4.0.4 with VHD image - image will not boot => Fixed in SVN | ||
| Description |
I was on 3.2.12 and happlily running a VM with W2K3 which was originally created as a VHD with Virtual PC for Windows7. All was good. I then upgraded to 4.0.4 and now when I try to start the VM I just get a black screen. I do not get any disk activity at all. I tried all of the usual tweaking of the settings just in case 4.0.4 had a default setting that was different to 3.2.12 but nothing worked. I then used CloneVDI to migrate the VHD file to a VDI file. Set all of the settings back to the way they were before I upgraded (i.e. virtualization, CPU's, IO APIC etc) and it booted first time - no problem. Just to be sure I detached the VDI and reattached the VHD and got the black screen again with no activity whatsoever on the disk. I think there is an issue with the upgrade to 4.0.4 or a compatability issue with VHD that is not there in 3.x. Something gets screwed when its a VHD of a certain type. |
|||

