PostConfig script removing sources in Target?

So I've gone through trying to figure out why in the world this particular project would not load when I attempted to open the Win7PESE file in the ISO, and after doing some searching, I found out that the script PostConfig was deleting the source folder when it was trying to create the ISO image for it. This made things even harder to make an image, because without this script I can't compile a proper boot.wim file for the ISO. It keeps giving me this particular error message:



AND THIS error message confuses me very greatly, because I am using a x86 build source to build this file from. The worst thing is that when I try to use a x64 source to build it from, I get the same error message as well. Is there something terribly wrong with the script? Or am I just searching for the answer in all the wrong places?

So I've gone through trying to figure out why in the world this particular project would not load when I attempted to open the Win7PESE file in the ISO, and after doing some searching, I found out that the script PostConfig was deleting the source folder when it was trying to create the ISO image for it. This made things even harder to make an image, because without this script I can't compile a proper boot.wim file for the ISO. It keeps giving me this particular error message:



AND THIS error message confuses me very greatly, because I am using a x86 build source to build this file from. The worst thing is that when I try to use a x64 source to build it from, I get the same error message as well. Is there something terribly wrong with the script? Or am I just searching for the answer in all the wrong places?

I just noticed the picture size is WAY too small to even try to read. Here's a bigger one:
newbielink:http://i281.photobucket.com/albums/kk211/QuentinX5/PostConfigError_zps5ad21420.png [nonactive]

The imageX file used to make boot.wim must have the same architecture as your Host PC.
No matter if you use a win7 x86 or x64 as project source.

Did you do manual operations (eg: copy imagex from Waik or others) the wim tools are downloaded once and automatically at first building.
In a first step, use the package without touching anything, just specifies the source directory then press the Play button.

Otherwise, there are no enough information to understand what is happening to you.
Please, in the script Main Configuration, enable 'Create support Log' and after building, share the log (mediafire, zshare, ...).

I found out that the script PostConfig was deleting the source folder when it was trying to create the ISO image for it.

I do not really understand what you mean 
The source, I guess that you mean the TargetDir (result of building). It is not deleted at all in PostConfig!
The image boot.wim is built from TargetDir in a new folder ISO\WIM\sources in this script, if you are referring to this folder. It allows to takes account of all modifications done in TargetDir (play a new script, add new files, registry change...)

Is there something terribly wrong with the script? Or am I just searching for the answer in all the wrong places?

I believe  that I would have had many other messages if there were some horrible things in this script

The imageX file used to make boot.wim must have the same architecture as your Host PC.
No matter if you use a win7 x86 or x64 as project source.

Did you do manual operations (eg: copy imagex from Waik or others) the wim tools are downloaded once and automatically at first building.
In a first step, use the package without touching anything, just specifies the source directory then press the Play button.

Otherwise, there are no enough information to understand what is happening to you.
Please, in the script Main Configuration, enable 'Create support Log' and after building, share the log (mediafire, zshare, ...).

...
So I had been having this project get the tools themselves, and I had copied them over once, but I figured that the Retrieve Tools script would gather me a more up to date version of them, and what you said about copying them over worked again. :P

I found out that the script PostConfig was deleting the source folder when it was trying to create the ISO image for it.

I do not really understand what you mean 
The source, I guess that you mean the TargetDir (result of building). It is not deleted at all in PostConfig!
The image boot.wim is built from TargetDir in a new folder ISO\WIM\sources in this script, if you are referring to this folder. It allows to takes account of all modifications done in TargetDir (play a new script, add new files, registry change...)

Alright, so I was watching the directory where WinBuilder had been building the Win7PESE boot disc, and as that script ran (and I know the script is supposed to create a boot.wim file), it would just completely erase the folder instead of actually building a boot.wim file, which I think is why that error message kept coming up. :P

Is there something terribly wrong with the script? Or am I just searching for the answer in all the wrong places?

I believe  that I would have had many other messages if there were some horrible things in this script

You have quite a point. :P
My thought was that maybe somewhere in the process of retrieving this script, that some lines of code could of gotten messed up. :P
Alright, now I am running into the original error I was running into before this became a problem. XD

newbielink:http://i281.photobucket.com/albums/kk211/QuentinX5/MissingIFP_zps674cd7a3.png [nonactive]

It continues to tell me that this driver is missing (It's an Intel Driver for Windows 8 and Windows Server) or corrupt, which I can't understand for the life of me because I tried booting it on another computer and ran into the same issue. Is this an issue with the downloaded driver packs I got from driverpacks.net?

Eliminating the driver packs seems to get rid of this issue, but I wanted to use the Chipset, LAN, WLAN, and Mass Storage drivers. Any idea on how to get around this?

I FIGURED OUT MY ISSUE!
So, I thought that maybe if I deleted the excess boot drivers (the ones from Server, Vista, and Windows 8), that it might get rid of the issue. Lo and behold, it did! Boot disc acquired. :)
Thanks for pushing my thought process in the right direction. :)

So I had been having this project get the tools themselves, and I had copied them over once, but I figured that the Retrieve Tools script would gather me a more up to date version of them, and what you said about copying them over worked again. :P

If I understand, you knew about for Retrieve tools and that you had copied the wim tools manually.
But you come to ask for help nevertheless, without saying your operation and without thinking that the first error is certainly related.
Do better next time 

Is this an issue with the downloaded driver packs I got from driverpacks.net?

Eliminating the driver packs seems to get rid of this issue, but I wanted to use the Chipset, LAN, WLAN, and Mass Storage drivers. Any idea on how to get around this?

2 remarks,
Windows 8 comes with a large number of native drivers for most hardware.
You may need some additional drivers but I do not believe that Gb of drivers is really necessary.

DriverPacks.net does not seem to have Windows 8 package for now, although some drivers are Compatible, so be careful.

What are the "DriverPacks"?
They are intended to be used while creating a Windows 2000, XP, 2003, Vista or Windows 7 installation disc/image. We also provide you with the software to make that as simple as possible.