#1 current drive letter

[Chris Thomas]

this bug appears when you are running windows, since I
have no support for any other platform as yet.

when you create the PortableProgram executable which is
to run your child program, you customise the XML which
is then combined with the PortableProgram program
loader, because windows supports paths. Most of the
time, it is not a good idea to put drive letters inside
the XML file, because they can change and cause you
problems.

In SVK, this happens also, but there is a bug which
happens when you have your command prompt on drive c:
but you are running svk from drive e: and therefore the
PortableProgram executable is sitting on drive e: also
(a requirement of the system to work properly)

in svk, this results in the wrong drive being accessed
and the error:

Cannot create svk-config-directory at
'C:\apps\svk\.svk' : No such file or directory

where e:\apps\svk\.svk is the directory it is SUPPOSED
to access, beacause I am on drive C and the path is
treated relatively, it means it checks the wrong location.