Hi Malkie,
You have to remember that VDos works with a virtualized file system,
meaning that programs running inside VDos can only access drives and
folders that you make available to them in the VDos configuration, and
that VDos can be configured to access drives or folders using drive
letters that are meaningful only within the scope of the VDos world.
Specifically, the 'autoexec.txt' file in your VDos folder controls how
your VDos apps interact with the outside world. If you want VDos apps to
be able to write to drive H:, you have to map access to that drive by
including a line in your autoexec.txt file that says:
USE H: H:\
That now lets VDos apps access any folder and file on the H: drive (as
long as the folder/file name conforms to the 8.3 specs).
If you wanted to be more limiting in the access granted to VDos apps,
you could do something like this instead:
USE Q: H:\MSWord\Docs
Then anytime DP running inside VDos needed to write to the real-world
H:\MSWord\Docs folder, you would simply tell it to output to Q:\ and the
output would automatically get directed by VDos to your mapped
real-world folder.
Tim Rude
On 9/14/2014 4:54 PM, barmag wrote:
Hi Everyone;
Can someone please help me figure this out? I'm using VDos for DP on
my Win7 64 bit and it's working beautifully, thanks a million to Gerard.
My DP is in F:\DP26F\phonebk
WP51 is in F:\WP64\docs and Word is in H:\MSWord\Docs
When I export from DP to WP or Word having entered H:\MSWord\Docs\test
at the destination filename, I get "illegal path name -- path not found".
If I enter F:\test as the filename, I'd find the file located in F:\DP26F.
What do I insert in the destination filename to get it exported to WP
or Word?
Malkie
_______________________________________________
Dataperf mailing list
[email protected]
http://lists.dataperfect.nl/cgi-bin/mailman/listinfo/dataperf
_______________________________________________
Dataperf mailing list
[email protected]
http://lists.dataperfect.nl/cgi-bin/mailman/listinfo/dataperf
