[vbox-dev] v4.0.0_BETA2 - IVFSExplorer API - Tickets 7147 & 7148 Not Fixed

Klaus Espenlaub klaus.espenlaub at oracle.com
Mon Dec 13 12:50:33 PST 2010

On 12.12.2010 19:03, Joseph Smith wrote:
> Hi All,
> Not sure if this is the right place to send this. I did add to the forum
> (VirtualBox Beta Feedback) and sent a PM to one of the moderators to
> determine if that was the correct approach. The moderator has not yet
> had a chance to respond but as I have more to send ... I am trying to
> determine the correct process. Please let me know.
> I am in the process of migrating from 3.2.12 to 4.0.0 (BETA2 at the
> moment). The ticket does show a status of fixed ... so I am assuming it
> is part of 4.x. That may be a bad assumption on my part though.

Neither is marked as fixed, just the summary points to SVN. And yes, 4.0 
has the code. No matter which BETA you're looking at.

> VirtualBox: Version 4.0.0_BETA1 r68572
> Host: Windows XP (Service Pack 2)
> I have not tested this functionality on Linux yet ... can/will update
> with results once I am able to test.
> IVFSExplorer::entryList - Ticket #7148 ->
> http://www.virtualbox.org/ticket/7148
> Testing the IVFSExplorer::entryList API, the enhancement to support
> returning permission and size in addition to file name and type is not
> working.
> Per the documentation, this API is defined as:
> void IVFSExplorer::entryList (
> out wstring[] aNames,
> out unsigned long[] aTypes,
> out unsigned long[] aSizes,
> out unsigned long[] aModes
> );
> The API is only returning the first two elements in the response (same
> as 3.2.10 and 3.2.12).

Can't confirm. The code is there for all arrays, filling it with the 
information returned by the host OS. This is so simple that it's hard to 
imagine that there's a bug in this area.

> -------------
> IVFSExplorer::cd - Ticket #7147 ->http://www.virtualbox.org/ticket/7147
> Though indicated as fixed, does not work in 4.0. The suggested
> work-around described in the ticket for 3.2.x still works in 4.0.

The operation is definitely implemented now, and also expects a URI 

I really wonder what's going wrong for you there, it cannot possibly 
return the same error code...


> _______________________________________________
> vbox-dev mailing list
> vbox-dev at virtualbox.org
> http://vbox.innotek.de/mailman/listinfo/vbox-dev

More information about the vbox-dev mailing list