it's possible, but I don't think that's the problem.
it sounds more like the batch file is unable to find the source files, rather than the being unable to find the destination. if the batch-file starts in a different folder than it will no longer be near the source and thus will not be able to find them.
the problem is that the driver letters change and are unknown before hand... I can try replacing it with static destination and see if that fixes the problem.
if that doesn't work I can try giving it a static source like the C drive and keep the %HOMEDRIVE% see if that fixes the problem.
The %HOMEDRIVE% is 100% not the problem. that works just fine.
For some reason the batch-file is being loaded from somewhere other than under %SOURCE%\MksTweaks\ and therefore using the ./ relative path for the source folders doesn't work because the batch-file and the folders being copied are not in the same directory.
a partial fix for this is going through an alternate operating system and copying the folders to a known absolute path such as C:/ or D:/ before beginning the installation process and then changing the batch-file to copy the folders from there. However I would very much like to keep all dependent files on the on the installation disk as I will not always have this option and I would really like to figure out how to make the path relative since I want to make this installation portable the machines that will have different drive letter assignments..
also my .reg files are not being Merged into the registry which is strange because they are in the same place as the batch-file which nlite is clearly able to find...
any idea's on how I can fix these issues?
Edited by KapnJackSparrow, 21 November 2012 - 09:33 PM.