Please Help me!! Prob in building

+
Wait someone interested in adding vss feature ( maybe better say: wait someone interested in developing current vss plugin further)


one of 3 would happen 

JFX like to focus on how things works and feedback Chris on core related things

Lucky shot on JFX interest 

Still I wonder:
 Why people do not inform (email/post whatever) application developers about offline (ex: pe) usage
 And why use vss, even xcopy would do backup task 

Ya got it chief. Now it's running. I was trying to run the software shadow copy which as you know let's you copy files which are in use via VSS service. But now too it shows could not initialise windows shadow service. But I checked in the task manger and service.msc it's up and running. What to do?

In vss.script patching is now optional?

If,Not,%ProjectName%%BuildType%,Equal,Win8.1SEOS,Run,%ScriptFile%,Patch_Vss

No matter if it's call RAMOS, is actually still a WinPE and so have the MiniNT key,
that cause VSS to refuse work.

Thanks JFX  always here for the critical cases and more

Before putting the  If,Not,%ProjectName%%BuildType%,Equal,Win8.1SEOS,
I Successfully tested with Drive Snapshot --ForceVSS without the patching files in Win8.1 RamOS. I have missed a trick ?

@Xennet
The other previous fixes, seen with Lancelot, are on the server.

Good to here from you chris. Thumbs up for updating the server in your busy schedule.

Thank you but at the same time, the work was already done by the best script coder, Lancelot 

Vss with the patched files (when building), even for Win8.1 Ramos is on the server 

Following Lancelot Reply #14, I added a note on the interface:

Code: [Select]

(*) Vss is NOT vital for Windows and is definately NOT required by
    All application on PE or portable windows.
Ex: DriveImage XML normally requires Vss, but not on PE ;)and it is with Selected=False by default now

Thanks 

Still I wonder:
 Why people do not inform (email/post whatever) application developers about offline (ex: pe) usage

As far I remember, i did inform some developers about that.
But only respond was that they give my "idea" to the programming team.
And nothing have happend 

I Successfully tested with Drive Snapshot --ForceVSS without the patching files in Win8.1 RamOS. I have missed a trick ?

Hmm, maybe it's related to the SystemSetupInProgress status.
Maybe this one is enough for the way drive image uses vss.

But only respond was that they give my "idea" to the programming team.
And nothing have happend 

I well understand lazyness of developers on such case, little demand low interest,

 My point is, more people with such demand would eventually force developers to add such usage,
and when some of them start to add such feature, other softwares will follow.

Instead people like Xennet and many others try to get vss work as junk only to fool such applications,
 if they had demand on these software developers (since bartpe) they would get rid of vss requirement junk.

Well, one day
vss will not work on one version in future  and they will start to complain to software developers 
or
ms would let vss work on pe as default.

Till one happen, vss will remain as a stupid pain in pass, only self proving lazyness.

ps:
another example is "DriveSnapshot" , it has hot-backup feature (with or without vss, I don't know) besides it is also very pe aware   

ps2:
on my personal side, I would already prefer free applications that can hot-backup on windows, and restore on any pe,
 It is only big lazyness to pay some big money for some applications that can do half, and even not demand other half from developer...
   Well, life sometimes (very often  ) not works logical , people are simply lazy  , this vss story for years is a good proof. 

When I tried to add packages to my build i get the following error as attached in the screen shot. The packages and the dism seem to be of the same version and build. Yet it says that the specified package is not applicable to this image. Elsewhere as Chris mentioned the dism has been run from the target directory target/windows/system32/dism/dism.exe and of the same build as the package and build. The package is from WAIK 8.1. Do help me. I had tried to use the install package script by Chris but it too doesnt seem to work. Think the script has not been written for win 8.1 se?

Here is dism log file that is generated. I searched for long. Couldnt find any valid reason as to why the build gets failed even when they are of the same version. The build is of Win 8.1 x86 Pro RTM Build 6.3.9600.16384 and the package is x86 from WAIK 8.1 version 6.3.9600.16384. It is clear from the screen shot. I just dont get it. Now one thing to check is whether any of the winbuilder scripts have added a different version number in any of the registry keys??

Hi Xennet

To add a WinPE package, full Boot.Wim is needed. Make sure full file copy is selected in Build --> Copy Files script.

Thanks anshad,

added to FAQ http://theoven.org/index.php?topic=834 

Hai Anshad,

There is only option for file copy "standard" in copy file script???

Yes I checked it. In WIN8SE the file copy script has choices "standard", "small full"  and "full".
But in WIN81SE the script has only option for "standard"???????

Moreover install package script is not there in Winbuilder package 81se

maybe better not jump from subject to subject on same topic,
so looking some topic titles on some pages may give you and others a clue to figure out in future....

Well that is what I did 

I feel this is the reason (with some solution...) :
http://theoven.org/index.php?topic=803

Sorry for that lancelot. But as you knows problems and doubts are like chains. They come in bunches one after the other. But anyways they just do better in increasing our knowledge finally.

I fully understand you 
 Only I feel we come to a point to break chain 

I finally got it done. Installed all packages. I tweaked and rewrote the win81se copy file script by seeing the win8se copy script. Now can select option to full copy. Thanks for anshad on the tip of full copy. Hope ChrisR is not annoyed at me on tampering the script.

It is better you provide more info about how you tamper the plugin 
or attach the tampered plugin 
Keep in mind we are not magicians that can see what you did 

ps: my guess is you add full to CopyMode_ScrollBox but maybe more....

I thought you people would be annoyed if i attached the new script. Thats why didnt tell how. I just rewrote the win8se script which had option to select full copy to include the changes chris has made in his latest version  of win81se copy script. I Have attached the modified script.