I'm making an Opera plugin, which requires copying
the whole Opera folder and files' structure to RAMdisc.
My Bart is build on Windows 2003 Server.
To copy files, I want to use XCOPY because simple
COPY requires a lot of lines in the script that does
the copying.
XCOPY doesn't function in BartPE because there is no
VSSAPI.DLL in I386\system32 folder.

How to enrich the Windows 2003 Server (functioning
as BartPE's system) with the VSSAPI.DLL file ?

In other words how to place the VSSAPI.DLL in I386\system32
and if I manage to do it, will it be enough for XCOPY to work ?

Thanks in advance !

Review the PEBuilder help folder's files.


I don't know but XCOPY works on my BartPE system. Next time I have the machine with PEBuilder up I will check my plugin folders to see what I have for it.

XCOPY now works fine.
Here's how I managed to do it ...

Before building BartPE iso file, I looked into the MyCustom folder
and found there the I386 folder { C:\pebuilder\MyCustom\I386 }.
Inside it I created the SYSTEM32 subfolder in which I placed
the VSSAPI.DLL file .
I compiled a new pebuilder.iso and when I burned the BartPE CD
and booted it, I saw that VSSAPI.DLL was present in I386\SYSTEM32 folder.
I went into the command line window and tried to use XCOPY.
It worked fine.
Thanks for your readiness to help.

Happy to hear you got your problem resolved. I found that the 911exp-MMC plugin adds the VSSAPI.DLL file to BartPE.


I've never heard of this folder. What uses it?

Easiest way would have been to create a simple plugin:

[Version]
Signature="$Windows NT$"

[PEBuilder]
Name="xcopy dll plugin"
Enable=1

[SourceDisksFiles]
vssapi.dll=2

Ed_P ,
From the beginning my "C:\pebuilder" folder had the subfolder "MyCustom",
which was placed parallel ( on the same level ) as the "plugins" folder.
I don't remember whether it was created automatically with the first
installation of PEBuilder, or I created it myself.
If I created it myself I had to have read a suggestion in the help files
that creating "MyCustom" would be convenient for keeping any
of my files there.
I have created a subfolder "Programs" in "MyCustom" and anything
I put in "Programs" ( i.e. "C:\pebuilder\MyCustom\Programs" ),
during the compilation process goes to the BartPE CD's "Programs"
folder where all the plugins land too.
For the same reason ( i.e. for the reason of this specific Bart's PEBuilder's
functionality ) anything I put in "C:\pebuilder\MyCustom\I386\System32"
goes to BartPE CD's folder "I386\System32".
For me, putting a file in a folder is a simpler way of making a file
go to the BartPE CD's chosen folder, than writing a plugin, as ParaGlider
suggests. I'm not an experienced plugin creator. I rather use existing
plugins as suggestions in the process of creating my own plugins.
Saying it otherwise, I modify a copy of an existing plugin until
I get a functioning plugin of my own.
In this way, by modifying a Firefox plugin and using some suggestions
from the Adaware plugin I managed to create the "Opera Portable" plugin.



I would be glad if ParaGlider could explain to me the meaning of
a specific element of the INF file from inside a typical plugin folder.

Namely, what is the meaning of the digits at the end of a line like ...

[SourceDisksFiles]
files\operaportable\OperaPortable.exe=a,,1

Specifically what is the meaning of "a,,1" ?

I presume it is a directive for the compiler to know where
to place files on BartPE CD.
Numbers like 1, 2 or 3 mean perhaps some system folders
like I386 or I386\System32 or still another, but I'm not sure.

Could ParaGlider or anybody here explain this convention
of the INF file ?

... or could you read the docs about plugin files format and syntax?
http://www.nu2.nu/pebuilder/help/english/pluginformat.htm

http://www.nu2.nu/pebuilder/help/english/p...ourceDisksFiles



jaclaz

I have not looked into the documents
you gave link to. I didn't look for them,
because I thought finding them would be
difficult.
Lazy me.

Thanks !

;-)

And if you're offline you can read the same files on your hdd here:

c:/pebuilder/help/english/pluginformat.htm

--why not just run OperaPortable from a usb pendrive instead of adding it to your build? I use FirefoxPortable from my pendrive and it works fine [I'm using sherpya's XPE, I don't really know if it would work in pure BartPE] Why not save that space for something else such as for drivers?--just a suggestion

Easiest way for me to copy files to a Ramdrive is to create a self extracting archive.