Again! 10-14 distro tried to delete itself (basedir=targetdir)

I have been using updated 9-11 build for a while as it became stable with 10/1/15 Updates and didn't self destruct since. However, networking never works in that I cannot connect to an old Buffalo TeraStaion NAS that works with every other Windows OS I have. But, I digress. I wanted to try the latest distro to see if networking would work.

SO,

To keep what I have done so far ...

   BACKUP:  renamed c:\winbuilder to BACKUP5j.

   Created new c:\winbuilder and copied 10-14 distro to it. Mainly want to see if networking works or not. Builds up to this point are stable.

    added:  minimal additions. AdditionalFiles, VC++, WriteMedia to usbstick to nonexistent L:.  forgot to uncheck CreateISO.
            forgot to create logfile

   burned:  nonexistent L: usbstick in 50 stages. It stopped as expected when L: was not found. Stick not plugged in.
            During network.script running, I saw "ndiscap.inf.reg not found. The driver will not be registered" in Network.script.
            Hmmm. Is that why networking doesn't work?
 
    added:  Told it to create logfile.   Standard filecopy.
    added:  removed/Unchecked 'Create ISO' in Finals.
   burned:  to SANDBLUE1 as E: replacing WPEX38 in 49 stages. No format; LOTS of extra files from prev builds on stick.
            Saw "ndiscap.inf.reg not found. The driver will not be registered" in Network.script  27/49 stage

   tested:  unnamed SANDBLUE1 build in PAV17. SAW different initial screen after I picked sandisk usbstick. Waiting it out and
            it booted from the stick. Have to get picture with cellph. Tried to map raid5 as Z: letter but even adding UID and PW
            credentials, still get same "The specified network name is no longer available" although NAS is running.

   tested:  unnamed SANDBLUE1 build in PAV17. Took picture. Seems to be a grub4dos menu; normally I don't use grub4dos.
            Aha! I forgot to pick CopyToUSBDeviceBCD.

    added:  Changed WriteMedia destination to CopyToUSBDeviceBCD and disabled CopyToUSBDevice.

            Cannot find ndiscap.inf.reg on computer using Windows Search.

    added:  Ran Util\ExtractWimFolders despite warning that it already existed. ChrisR said this might be needed when others have
            had networking issues. I don't think it will mess up my previous winbuilder setups and might help.  Very long process.
            I did see warning that the Extracted folders were going to be deleted. Went ahead. After a while, I realized that
            Windows Defender was ON; turned off realtime antimalware checking about halfway through ExtractWimFiles. Finished no errors.

 reburned:  unnamed to SANDBLUE1 replacing unnamed in 49 stages, with refreshed ExtractWimFiles.  Almost immediately HALTED: targetdir=basedir
            I had gotten one of the possible popups when Win10PESE is about to delete itself.

==============
So this was a basic build, but RIGHT AFTER using my old SOURCE with Extracted WIM files, and refreshing those same files. I am posting the logfile and screenshot.

I will try again without adding VC++ and AdditionalFiles scripts to see if networking will work.

One thing I see I did wrong.  Running Util ExtractWimFolders was set to x86 instead of amd64. duh.

Reset to amd64 and trying another Extraction with 10-14 distro (saved from Deletion by Lancelot's placement of several HALT statements in 0-Preconfig).

Hi Tony4219,

nice instruction but too mixed  not reproducable to me on my low free time....

still you seem to figure out network trouble....

It is nice to hear nothing deleted with halts 


Things noticed:
* be sure about disabled AV etc.

* no need to use extracted wim folder if you extracted before (which you did)

* always have PostConfig + CreateISO enabled
this maybe important for WriteMedia plugins, ex: Copy To USB etc...

shortly:
do not enable WriteMedia plugins,
after you build with last 2 PostConfig, CreateISO

go to the WriteMedia plugin, use "small green" button.


my personal advice:
using Copy to USB-Device plugin,
get normal drive letter for your usb flash disk,
normal I mean:
you have 4 drive letters for your disks, G: is the usb flash disk
C:
D:
E:
F:
G: --> usb flash disk


***
when you test next time, follow steps.
1) Disable AV *****
2) try using other than C: (other than drive where windows is)
ex: D:\Oven
3) Extract zip to new folder D:\Oven
4) Use Utils\Update XXX (Exact and Secure) --> Download and Copy ==> get latest files from server
==> this also re assures, with Disabled AV, you have all files from exactly same with project server.
5) only point your source folder
6) do not change anything, just build :)

than changes "step by step" until you find the "step" where halt occurs

keep in mind: you are the only one who report such thing, since we create this forum 
 many development in some weeks, many plugins updated, no such halt from other users,
  it will be nice when figure out your unique condition 

my bet is the %TargetDir% has been modified

and,
when you click "source"
and pick your source directory,

be sure you do not click "x" near "Target Directory"

it is a bad design of current builder, nobody yet accidentally change this settings ;)

*
and
next time, better also provide some (2-3) previous logs ;)
your log is
log_20151016_131600_Win10PESE_Support.html
there are other logs with lower date on your basedir (D:\Oven)
or under Logs folder (D:\Oven\Logs)
2 or 3 of them would be enough ;)

**
Good luck on your next tests 

my bet is the script.project file has been modified

but what did it, why, how .....

remove from the "Source" tab -
%TargetDir%
%baseDir%\Target\Win10PESE

And make a perment variable (%baseDir%\Target\%projectname%) in  script.project


But that variable just gave me a faster way to create tests..

no copy to usb or postconfig

I will test in following days ..... 
I have to speed down.....

But that variable just gave me a faster way to create tests..

no copy to usb or postconfig

I don't understand that (my bad english)..

only a note:
after adding
%baseDir%\Target\%projectname%
restart builder ;)
 (another bug workaround ;) )

Time to sleep

I could possibility boot directly to target\Windows

Hi  KYHI,

later I remember why we did not do that in past,
 there is permanent variable bug of current builder.....
  it is not noticable by adding removing 1 2 variables, but when number increase it becomes very noticable ;)
    long story to short, we re-organised permanent variables and lowered total # in very past...
At that times, I also thought adding TargetDir or TargetDirV (ISOFile ISOFileV)
 but since main goal was lowering number, we did not.....

since this is a special case only with Tony4219, better first figure out what cause this..... 
 After figure out, we can follow your suggested way   

One thing I see I did wrong.  Running Util ExtractWimFolders was set to x86 instead of amd64. duh.

Hi Tony4219,

that setting is only for "Waik Source" ,

since SE projects use Windows source, that setting effect nothing...

shortly:
You don't need to change anything on "Extract Wim Sources" before using 

One must assume - the target Directory is being changes to C:\Winbuilder (in his case)

That is the only way %BaseDir%=%TargetDir%

As the %TargetDir% (in his case) should be = C:\winbuilder\target\Win10PESE

Which we know is the same as = %BaseDir%\Target\Win10PESE

So must assume the default value for Target Directory are being manually changed..



One only needs to select the SOURCE and leave all other values at their Default settings..

YES IT COULD BE 'PILOT ERROR' I hope this works!  I am setting up another Win10 machine to try a new build on, hopefully tomorrow or Monday early (Midwest USA time) 

 I don't think I ever clicked the red X but I have set up the new builds so often I could have done it wrong. Unfortunately, I deleted all the bad builds as they occurred, and only have the recent successful build backups (at around 5GB each)

The picking of SOURCE  PATHS is the possible place for manual (on my part) setting BaseDir=TargetDir. Looking forward to trying this on a different computer ...

[on the 'haunted' computer, I just did a successful build, restoring my previous working Winbuilder (9-11 distro with 10/1/15 updates that does not connect to NAS), but I did not use the pre-extracted WIM nor autodetect WIM options in ImagesConfiguration, only the time-consuming mounting of WIM each build. The PATHS appear correct for TargetDir and ISOdir.  The 'haunted computer' was set up with TechBench ISO as the host Win10 OS, after the Win81-to-Win10 upgrade failed after a few weeks.

Again, THANKS FOR ALL YOUR HELP AND SUGGESTIONS. I will very carefully set up PATHS on next 10-14 distro

Well, for now I added warning to FAQ
http://theoven.org/index.php?topic=834
reply 22 http://theoven.org/index.php?topic=834.msg17158#msg17158

Saw "ndiscap.inf.reg not found. The driver will not be registered"

ndiscap.inf.reg was added to the Network plugin. It's on server.

Networking never works in that I cannot connect to an old Buffalo TeraStaion NAS that works with every other Windows OS I have.

It seems that Ms does not allow, by default, to connect to unsecured network shares, Samba server, Nas... on Windows 10 now
Probably better in "Can't access my NAS (mount)" thread http://theoven.org/index.php?topic=1468.0

I should have replied to this thread sooner, but NO MORE PROBLEMS OF SELF-DELETING !!

since I now carefully ONLY set the SOURCE PATH and did not touch anything else on the PATHS page.

Definitely Pilot Error.

Again, many thanks. It has been so long since I set up my Win7PESE x64 (trouble free), I was setting Target also, which is a no-no I was unaware.

Right, now don't do it again...
https://www.youtube.com/watch?v=hdIAEpSyYTw

Of course, we all know where that came from:
https://www.youtube.com/watch?v=IIAdHEwiAy8

Thanks for the updates Tony4219 

Some tips to get your life easier :

*
Utils\Plugin Manager --> you can save settings of plugins ;)
--> you can use "Restore" button to restore your personal settings after updating 

*
Utils\Update XXX (Exact and Secure) --> Restore button get all project folder re-created (back to default ;) )

http://theoven.org/index.php?topic=1210.0


See You

Just want to point out - that even though this turned out to be pilot error..

The target directory is deleted in 3 different plugins..
And temp files are deleted in two plugins..

Main Configuration
0-PreConfig (where protections added)
1-Copy Files

Hi KYHI,

Win10PESE - Also added protection to:
Main Configuration
1-Copy Files