Custom Query (16363 matches)
Results (1507 - 1509 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #7312 | duplicate | jumbled audio | ||
| Description |
All audio output is jumbled since virtualbox 3.2.8 release As a example I've recorded windows startup sound(sorry for poor volume). it seems that people are experiencing the same problem on mac http://forums.virtualbox.org/viewtopic.php?f=8&t=33537&p=150625#p150625 |
|||
| #2703 | fixed | javaws (JVM) does not function properly / hangs (winxp guest, fedora linux host) | ||
| Description |
Attempting to use SUN's EBS (Enterprise Backup) console - a javaws/jvm interface, does not run properly (or at all) under Windows XP as a guest host in Virtualbox. The console "login" screen appears, but the console itself does not. The only sign of any activity is a stuck "javaw" process in Windows - trying the EBS console again creates ANOTHER "javaw" process, and so on. No error messages, nothing logged in the windows event viewer under any category. Behavior is consistent regardless of java version (1.4, 1.5, 1.6). (Editor note, this ought to be interesting, seeing as Sun EBS console, Virtualbox, AND Java are *all* sun products...). This lack of functionality is a deal killer that will not allow me to permanently retire my Windows XP workstation. Seeing as there were other similar java issues under other operating systems, I am betting this could affect many other applications..... |
|||
| #11078 | obsolete | java write IOException on windows to VBoxSharedFolderFS | ||
| Description |
I was using an existing java application that writes data to a file. The host is linux and the guest is windows XP. If the destination file is on the guest's C: partition, the write is sucessful. If the destination file is on the guest's VBoxSharedFolderFS, the write fails. Caused by: java.io.IOException: The parameter is incorrect
There is nothing in Java anywhere that explains, references, or describes the error "The parameter is incorrect". The file gets created, but it is only the write that fails. Investigation showed that the write was not even attempted to the native OS system call. I wrote a small groovy program to find the error. OutputStream output = null
If the bbuffer size is 123K or smaller, the write succeeds. If the bbuffer size is 124K or larger, the write fails. invoked with "groovy jwrite.groovy 124 sample.txt" Caught: java.io.IOException: The parameter is incorrect java.io.IOException: The parameter is incorrect
|
|||

