Why no trailing colon or backslash?

[daos]

Why is it that WSUS OU refuses to accept a temp variable that points to the root of a drive? I use a RAMdisk and creating a pointless directory just seems like a waste to me. I assume that there's a reason for this and it isn't just arbitrary but I'd like to know.

[boco]

If you want to use the root of a drive, use only the drive letter, e. g. TEMP=X:

My experiences (back to DOS) are that most software will add the slash itself, and TEMP variables must never end with a slash. There may be some programs designed to tolerate it (using X:\\ as X:\), though.

[daos]

Thanks for the reply. There's only one problem with that answer. It doesn't actually work that way. I tried putting in just T: and I got the same error. It specifically says that you can't have either a trailing colon or backslash. It's still not making sense to me.

[boco]

I found that passage in the UpdateGenerator.au3 code file. So the WSOSOU author would have to enlighten us as to why it is not possible to use a drive root as TEMP. Maybe it's an AutoIt limitation.

[WSUSUpdateAdmin]

Hi!

No, it's not an AutoIt limitation, it's my decision.
A trailing backslash is impossible because of path concatenation.
A trailing colon (without concatenation) does not mean root, but the drive's current path.
That's why I also prevented the colon.

Regards
Torsten Wittrock

[WSUSUpdateAdmin]

Hi again,

I just went through the code and saw that the "colon" restriction isn't needed any longer for the download part: http://trac.wsusoffline.net/browser/trunk (r400).

Thanks & regards
Torsten Wittrock

[daos]

That's good news. I appreciate you looking into that. Thank you.