Action when terminating the VM . . . . . . . . . . . . . . . . . . . . . . 188 9.19.9 Action for handling a Guru Meditation . . . . . . . . . . . . . . . . . . 189 9.19.10 Configuring automatic mouse capturing 24 VirtualBox expert storage management . . . . . . . . . . . . . . . . . . . . . . . 196 9.25 Handling of host power management events . . . . . . . . . . . . . . . . . . . . 196 9.26 Experimental support host floppy not found . . . . . . . . . . . . . . . . . . . . . . . . 222 12.7.5 Strange guest IDE error messages when writing to CD/DVD . . . . . . . 222 12.7.6 VBoxSVC IPC issues . . . . . . . . . .

Action when terminating the VM . . . . . . . . . . . . . . . . . . . . . . 188 9.19.9 Action for handling a Guru Meditation . . . . . . . . . . . . . . . . . . 189 9.19.10 Configuring automatic mouse capturing 9.24 VirtualBox expert storage management . . . . . . . . . . . . . . . . . . . . . . . 196 9.25 Handling of host power management events . . . . . . . . . . . . . . . . . . . . 196 9.26 Experimental support host floppy not found . . . . . . . . . . . . . . . . . . . . . . . . 223 12.7.5 Strange guest IDE error messages when writing to CD/DVD . . . . . . . 223 12.7.6 VBoxSVC IPC issues . . . . . . . . . . .

Among many other generally useful code sequences it contains a function which shows how to retrieve error details in C code if they are available from the API call. The sample program tstCAPIGlue can be built revision; /* * VBoxCGlueInit() loads the necessary dynamic library, handles errors * (producing an error message hinting what went wrong) and gives you * the pointer to the function table (g_pVBoxFuncs) functions in worker threads created by COM/XPCOM (which you might observe if your code uses active event handling), everything is initialized correctly already. On Windows the C bindings create a marshaller which

Among many other generally useful code sequences it contains a function which shows how to retrieve error details in C code if they are available from the API call. The sample program tstCAPIGlue can be built revision; /* * VBoxCGlueInit() loads the necessary dynamic library, handles errors * (producing an error message hinting what went wrong) and gives you * the pointer to the function table (g_pVBoxFuncs) functions in worker threads created by COM/XPCOM (which you might observe if your code uses active event handling), everything is initialized correctly already. On Windows the C bindings create a marshaller which

Action when terminating the VM . . . . . . . . . . . . . . . . . . . . . . 188 9.19.9 Action for handling a Guru Meditation . . . . . . . . . . . . . . . . . . 189 9.19.10 Configuring automatic mouse capturing 24 VirtualBox expert storage management . . . . . . . . . . . . . . . . . . . . . . . 196 9.25 Handling of host power management events . . . . . . . . . . . . . . . . . . . . 196 9.26 Experimental support host floppy not found . . . . . . . . . . . . . . . . . . . . . . . . 222 12.7.5 Strange guest IDE error messages when writing to CD/DVD . . . . . . . 222 12.7.6 VBoxSVC IPC issues . . . . . . . . . .

Among many other generally useful code sequences it contains a function which shows how to retrieve error details in C code if they are available from the API call. The sample program tstCAPIGlue can be built revision; /* * VBoxCGlueInit() loads the necessary dynamic library, handles errors * (producing an error message hinting what went wrong) and gives you * the pointer to the function table (g_pVBoxFuncs) functions in worker threads created by COM/XPCOM (which you might observe if your code uses active event handling), everything is initialized correctly already. On Windows the C bindings create a marshaller which

Among many other generally useful code sequences it contains a function which shows how to retrieve error details in C code if they are available from the API call. The sample program tstCAPIGlue can be built revision; /* * VBoxCGlueInit() loads the necessary dynamic library, handles errors * (producing an error message hinting what went wrong) and gives you * the pointer to the function table (g_pVBoxFuncs) functions in worker threads created by COM/XPCOM (which you might observe if your code uses active event handling), everything is initialized correctly already. On Windows the C bindings create a marshaller which

Among many other generally useful code sequences it contains a function which shows how to retrieve error details in C code if they are available from the API call. The sample program tstCAPIGlue can be built revision; /* * VBoxCGlueInit() loads the necessary dynamic library, handles errors * (producing an error message hinting what went wrong) and gives you * the pointer to the function table (g_pVBoxFuncs) functions in worker threads created by COM/XPCOM (which you might observe if your code uses active event handling), everything is initialized correctly already. On Windows the C bindings create a marshaller which

Among many other generally useful code sequences it contains a function which shows how to retrieve error details in C code if they are available from the API call. The sample program tstCAPIGlue can be built revision; /* * VBoxCGlueInit() loads the necessary dynamic library, handles errors * (producing an error message hinting what went wrong) and gives you * the pointer to the function table (g_pVBoxFuncs) functions in worker threads created by COM/XPCOM (which you might observe if your code uses active event handling), everything is initialized correctly already. On Windows the C bindings create a marshaller which

Among many other generally useful code sequences it contains a function which shows how to retrieve error details in C code if they are available from the API call. The sample program tstCAPIGlue can be built revision; /* * VBoxCGlueInit() loads the necessary dynamic library, handles errors * (producing an error message hinting what went wrong) and gives you * the pointer to the function table (g_pVBoxFuncs) functions in worker threads created by COM/XPCOM (which you might observe if your code uses active event handling), everything is initialized correctly already. On Windows the C bindings create a marshaller which