Problems with using reparse points for SOURCE folder

[Ausmith1]

I had the bright idea of using reparse points (Windows retarded way of doing symlinks) for the SOURCE folder for HFSLIP, but have run into some weird issues. I was wondering if anyone else is using this method with the latest release of HFSLIP? If so are you encountering the same issues I'm seeing?

My script:

Build 2003_R2_x86_ENT_EVAL

#junction.exe D:\HFSlip\SOURCE D:\Source\2003\x86\ENT\EVAL
CALL D:\HFSlip\hfslip-1.1.0.cmd
C:\Support\SysInternals\junction.exe -d D:\HFSlip\SOURCE

What happens is only the files that are actually changed/updated/patched by HFSLIP get copied to the D:\HFSlip\SOURCESS folder, all of the unchanged files get left behind...

I tried the method mentioned by Bilou_Gateux @

http://www.msfn.org/board/index.php?showto...=368791�

but I get the same results, only the changed files in the I386 folder get copied to D:\HFSlip\SOURCESS.

I've had weird results with other applications when using reparse points, like folders getting deleted one level above where they should have been deleted so maybe it just one of those weird things with reparse points, but it sure would be nice to have it work, it would save a lot of time copying from the source folders...

[Tomcat76]

I don't know anything about that so I can't really help, but have you tried running your script from within the HFSLIP folder?

[Ausmith1]

Yes, I tried running everything manually from a command line in the D:\HFSLIP folder when the script didn't work. Same result.