Re: read volume

2016-05-11 Thread JB
When I read your reply it said there was a recent thread opened about that and gave a link. Now it does not say that and talks about walking a directory. Walking a directory for a large volume is too slow. I already tried it and I was happy with the time it takes. What I want to do is read the

Re: read volume

2016-05-11 Thread JB
Thanks for the info. I will read it. JB > On May 10, 2016, at 7:16 PM, Scott Rossi wrote: > > I think what you're looking for is directory walking (files & folders, not > file contents). > > You're part of a fairly recent thread that explains this: >

Re: read volume

2016-05-10 Thread Scott Rossi
I think what you're looking for is directory walking (files & folders, not file contents). You're part of a fairly recent thread that explains this: http://runtime-revolution.278305.n4.nabble.com/recursion-limit-when-creatin g-file-list-of-harddrive-td4697952i20.html Regards, Scott Rossi

read volume

2016-05-10 Thread JB
I thought I had read you could read a volume like you read a file but it can not be the startup volume. I tried to read using the volume name shown from the volumes function and open file and it did not work so I used open driver and it did not return any data either. Is there a way to read a