Ok, I fixed my typo's in my last mediocre post about the use of the 2 cmd's the use of the IF EXIST etc...
I seen that I could fix the cmd myself, but I thought no I need to find out why the issue was happenin in the first place, hope he understands it and can do a fix that will not have the issue with bit space, then I think he will have a universal cmd for the SAD2 tool
----------------------
The 'DP_Install_Tool.cmd' is not the problem, just the extra ')' in the cmd was a legit issue tho please make sure to pass that on, as I found out the nature of the error and it was a mind bogglin one too
Well that is wat you would think, but no ..
here is the layout I just ran into last night.
1 Dual arch AutoUnattend.xml with both amd64 and x86 architectures, ok now we are goin to get a little confusin maybe, just follow along
you have this 1 XML file dual arch, and you have in it to RunAsynchronous or RunSynchronous commands ..
having the exact same run for a cmd or .exe ( or ANYTHING at this point ) in each amd64 and x86 and install a x64 OS will run BOTH the amd64 and x86 components in the pass
So wat I was gettin was that, the amd64 section of the XML file was gettin ran first ( and was fine on the x64 OS ) then the x86 section was gettin ran right after the amd64, witch would throw the windows error up, witch is legit, but to the fact that I didnt even know that BOTH comopnents ( amd64 & x86 ) would get ran if install a x64 OS .. if this has made since, that is the gist of that, lets go on ..
Now for the x86 OS install, this is just plain simple, it ignores the amd64 sections of the XML file .. thats all there is too the x86 side, it runs just the x86 components listed in the XML file ..
So using a dual arch XML file ( you have to beeee very careful to wat ya have in BOTH amd64 and x86 sections of the components pass or you may end up flubbin a x64 install, the critical areas I see that are visible to this is the RunAsynchronous or RunSynchronous commands listed in amd64 and the x86 parts
Ok, 1 final notation is that: When usin the above setup of a XML file and RunAsynchronous or RunSynchronous commands, they will run in 1 of 2 bit spaces = if amd64 the execution is from the 64 bit space, IF it runs the x86 it is ran from 32 bit space, and thus in the DP install tool.cmd this is wat was ACTUALLY happenin, is that the amd64 RunAsynchronous was the correct run cause the line was executed on a x64 OS, witch the DP Install tool.cmd finished as intended. Now the x86 RunAsynchronous command runs right after the amd64 and it would be in task manager as running in 'DP_Install_Tool.cmd *' ( witch means 32 bit run on x64 OS ) ok, fine, BUT it would pull the %PROCESSOR_ARCHITECTURE% == x86 ... and that is were I get the cross error in the DP_Install_Tool.cmd being ran.
SO to correct the bit space run on a x64 OS install, I created 2 cmd's - 1 for the x86 pass and 1 for the amd64 pass in the XML file, the x86 has in it, this is the very first thing that gets lookd at - 'IF EXIST "%HOMEDRIVE%\Program Files (x86)" GOTO EXIT' - the exit is at the bootom of the cmd so it doesnt hurt it to just simply exit out so this way it is truly ran on the correct OS Arch x86 , now the amd64 pass runs the cmd runs but does not have the check if "%HOMEDRIVE%\Program Files (x86)" exists, so that will run in 64 bit space and the %PROCESSOR_ARCHITECTURE% == amd64 when ran, so now I have this fixed more or less the correct way cause of the bit space run time for both arch's .. nifty I know LOL.
now that must sound a little better