... a step further, the file only disappears if you open the volume again.
if you connect controller, it makes file system protocol available again.
If you just stop there, the file is good, if you open the simple file
system protocol then open the volume, it's gone.
On Mon, Sep 23, 2013 at 12:35 PM, David F. <df7...@gmail.com> wrote:
> Hi,
>
> So while I tested in OVMF and VirtualBox with no issues, on the Intel
> board (AMI) if you look for the simple file systems, disconnect it, then
> write your own file to the file system, then connectcontroller based on
> locating the old device path (using device path), and open the volume, it
> wipes out the new file in the root directory (chkdsk will then find the
> lost file)., If I don't connectcontroller and just leave it, then the
> file is there safely.
>
> Is there something else I should be doing or is this another example of
> implementation issues?
>
> TIA!!
>
>
>
------------------------------------------------------------------------------
October Webinars: Code for Performance
Free Intel webinars can help you accelerate application performance.
Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from
the latest Intel processors and coprocessors. See abstracts and register >
http://pubads.g.doubleclick.net/gampad/clk?id=60133471&iu=/4140/ostg.clktrk
_______________________________________________
edk2-devel mailing list
edk2-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/edk2-devel
