| Author | Message | ||
     Pánczél, Levente Username: panczel_levente Registered: N/A |
In Options|General I'm trying to set "Folder for images and backup files" to ".." (the parent folder of the current launch-location) but XWF rejects it with this message: The file or directory ".." does not exist. The same stands for "Folder for internal hash database" which I want to set to ".\HashDB" or simply "HashDB". I'm pretty sure that the launch location is correct and that I'm right about where "." is pointing, because clicking the [...] button opens the Select Folder dialog on exactly those places that I wanted to enter in the box. BTW: "." is always accepted. (The key is that I'd like to have _relative_ paths, some pointing to parent folders and some to children; because I plan to move this copy along with other data.) If these restrictions are by design then what should I make different? | ||
| Stefan Fleischmann Username: admin Registered: 1-2001 |
"." is a specially defined placeholder for the directory from where X-Ways Forensics is executed. Other than that, only actual paths are accepted. > If these restrictions are by design There are no restrictions. That "." has a special meaning, is a special feature. > then what should I make different? Nothing. Relative paths are not supported. | ||
| Pánczél, Levente Username: panczel_levente Registered: N/A |
Thank you! Then my original approach was obviously wrong. We need to work in a system, where we can put a case on a HDD and mobilize it. That means we store the version of XWF we used with all settings and case data on the same volume as the images. Then we simply move such case HDDs from workstation to workstation. This implies that we cannot assume case drive letters, so absolute paths are not an option. I know others already copy XWF along with case data to maintain version coherence; so can that be done somehow easy, or do they have to reconfigure paths when the drive letters change? I see that as a last resort "." is sufficient (by setting images to "." and always steppnig into an "images" folder when adding new images) to keep files in separate folders (to a certain degree). A suggestion: I assume that "." is the only special case because it's crucial that the folders exist; but if so, then I would suggest adding any levels of ".." as special case, since these are also guaranteed to exist, and would help in organising a cleaner case-data structure (e.g. we could place images right outside the XWF folder). |