The problem is not usually AnzioWin in this case. The problem is the handling of backslashes by the shell you are running under for your operating system. Since backslashes have special meaning in most all shell strings, they have to be either escaped or handled special on input and output. Try something like the following (this may vary depending on your shell and scripting environment):
/usr/bin/printf "\034%s\035" "dir/s c: "
read -r file
printf "%s\n" "$file"
file="${file//\\/\\\\}"
/usr/bin/printf "%s\n" "$file"
The "-r" is necessary on the read to not strip the backslashes and if you need to redisplay the file name with just an echo or use it within other variables, the "file=..." string will escape the backslashes for you.
There are a couple of commands that will help in situations where you continue to have problems with backslashes.
First, you can set the default directory separator character (a backslash) to be something other than the Windows default with the "dir-separator" command.
/usr/bin/printf "\034%s\035" "dir-separator | "
You will then get back a file name with that character separating the path directories, i.e. c:|myfolder|myfile.pdf.
Additionally, when a dir/s, findfirst/s, findnext/s or other directory commands fail or are completed, they return, by default, a double-backslash, i.e. \\. This too can be difficult to work with on some hosts. So we have a command to adjust this as well, the "dir-terminator" command.
/usr/bin/printf "\034%s\035" "dir-terminator DONE "
In this example, instead of a double-backslash being returned when a directory command is complete (or fails), the word DONE will be returned.
More information can be found in the AnzioWin manual and whitepapers, as well as in the readme.txt file shipped with each version of AnzioWin.