VirtualBox

Custom Query (16363 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (2407 - 2409 of 16363)

Ticket Resolution Summary Owner Reporter
#15504 wontfix VirtualBox Mac OS X Installer Issue Enclle
Description

Hello,

I tried to update VirtualBox for Mac OS X to the latest version, but it stops on the screen "Verifying 'VirtualBox.pkg'...".

I downloaded these DMG images http://download.virtualbox.org/virtualbox/5.0.20/VirtualBox-5.0.20-106931-OSX.dmg (from VirtualBox.Org Downloads page) and https://www.virtualbox.org/download/testcase/VirtualBox-5.0.21-107994-OSX.dmg (from TestBuilds VirtualBox.Org wiki page). With the two installers I had the same problem: I got stook in the "Verifying..." dialog. The steps are: After downloading the dmg images, open/mount it, then double click on the "VirtualBox.pkg", then it starts the Installer with the 'Verifying "VirtualBox.pkg"..." dialog and then stops.

Apparently it isn't using too much memory or processor (processor usage less than 5% all time and memory usage way less than the maximum physical memory).

I am using Mac OS X El Capitan 10.11.5

It's the first (i.e., the only) installer that I have problem with.

I let it "verifying" for more than half an hour and nothing happened.

#15503 invalid Floppy driver reads junk instead of real data (int 13h/0x2) eider
Description

To begin with, here's the example code:

  mov ax, 0x2000 ; 0x2000:0x0000 
  mov es, ax
  xor bx, bx ; bx == 0
  mov ah, 2 ; read sectors into memory
  mov al, 0xCC ; magic value for build process
  nop
  nop
  mov ch, 0
  mov cl, 2
  mov dh, 0

  int 13h

The code is supposed to read number of sectors starting from 0x2 using head 0 from floppy drive using floppy image file. Magic value (0xCC, nop, nop) is replaced by 0x26 in this example.

Before i go further i want to stress this out: it works on VMware and on real device!

http://i32.pl/osdev/img/Screenshot_4.jpg This image shows that stage2 of bootloader was loaded correctly (0x20000)

http://i32.pl/osdev/img/Screenshot_1.jpg This image shows that beginning of PE kernel file was loaded correctly (MZ header and stub). (0x24*)

http://i32.pl/osdev/img/Screenshot_2.jpg This image shows that loaded data from this point is garbage. (0x24600)

http://i32.pl/osdev/img/Screenshot_3.jpg This image shows rest of data that was supposed to be kernel code - somehow loaded data is stage1 (visible on previous image) and stage2 (visible on this image) of bootloader.

http://i32.pl/osdev/img/Screenshot_5.jpg And finally this image compares data at 0x24600 with data from beginning of floppy disk - how the hell data from sector 0 found its way onto 0x24600 when BIOS was asked to load data starting from sector 2 into 0x20000?

I'm attaching VBox.log and ZIP archive containing floppy.flp image file i used and compressed memory dump of virtual machine you can examine.

#15501 fixed Drag&Drop guest->host fails if unicode ligature character is in file-name (VERR_FILE_NOT_FOUND) -> fixed in 5.2.20 pentagonik virtual_rob
Description

I just noticed that copying a file from guest to host (both Windows) fails always if the file-name contains a unicode character like "œ" 'LATIN SMALL LIGATURE OE' (U+0153).

Renaming the file, replacing the mentioned character with ASCII characters solves the problem.

Error message:

Die Drag-und-Drop-Operation vom Gast zum Host ist fehlgeschlagen.

Drag and drop error from guest (VERR_FILE_NOT_FOUND).

Fehlercode:VBOX_E_IPRT_ERROR (0x80BB0005)
Komponente:GuestWrap
Interface:IGuest {13a11514-402e-022e-6180-c3944de3f9c8}
Batch Modify
Note: See TracBatchModify for help on using batch modify.
Note: See TracQuery for help on using queries.

© 2024 Oracle Support Privacy / Do Not Sell My Info Terms of Use Trademark Policy