Custom Query (45 matches)
Results (28 - 30 of 45)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #66 | invalid | RC Error: VirtualBox.res at end of compile | ||
| Description |
kBuild: Installing tstVBoxAPI => F:/5.0.6Netlabs-143/out/os2.x86/release/bin/test case/tstVBoxAPI.exe Reading binary resource file F:\5.0.6Netlabs-143\out\os2.x86\release\obj\VirtualB ox\src\platform\os2\VirtualBox?.res (0) RC: error - Only integer TYPE allowed (). RC: 1 error detected kmk: * [F:/5.0.6Netlabs-143/out/os2.x86/release/obj/VirtualBox/VirtualBox.exe] Error 1 The failing command: @g++.exe @F:/5.0.6Netlabs-143/out/os2.x86/release/obj/VirtualBox/VirtualBox.rsp kmk: * Deleting file `F:/5.0.6Netlabs-143/out/os2.x86/release/obj/VirtualBox/V rtualBox.exe' kmk: * [F:/5.0.6Netlabs-143/out/os2.x86/release/obj/VirtualBox/VirtualBox.exe] Deleting file `F:/5.0.6Netlabs-143/out/os2.x86/release/obj/VirtualBox/VirtualBox map' kmk: * [F:/5.0.6Netlabs-143/out/os2.x86/release/obj/VirtualBox/VirtualBox.exe] Deleting file `F:/5.0.6Netlabs-143/out/os2.x86/release/obj/VirtualBox/VirtualBox rsp' # |
|||
| #56 | fixed | Repair the NAT network | ||
| Description |
Internal network, working via NAT does not work. We can see that the NIC driver seems to work, the OS driver installs ok and windows device manager shows that the device works ok. But we also can see that packets go to nowhere and nothing gets received. Windows shows a yellow warning sign. It also looks that NAT loop in DrvNAT.cpp is blocked. So, we need to solve this problem. |
|||
| #13 | fixed | The VBox 'Main' server app. won't start with NS_ERROR_FACTORY_NOT_REGISTERED | ||
| Description |
When trying to start the VBox 'Main' server (VBoxSVC.exe), the VBoxXPCOMIPCD.exe (the XPCOM IPC daemon) won't spawn, an error from this ticket title is returned. But if I start VBoxXPCOMIPCD.exe daemon manually, then it starts successfully. But if I then try starting an appilcation, using the VBox XPCOM API (a user interface app, or a tstVBoxAPIXPCOM.exe testcase), then the next error in ticket #14 occurs. |
|||
