During the course of my post about a NAS/attached storage I said I had
managed to maintain the drive letters on my external drive.

I could scrap drive letters and just use URLs in Win 10 apparently by
mounting each drive in an NTFS directory.

I know Linux and Mac OS does that anyway. Anybody actually used it in
Windows? Any pros/cons? Would it work with drives on my attached storage?

--
Jeff Gaines Dorset UK
Indecision is the key to flexibility

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Jeff Gaines wrote:

During the course of my post about a NAS/attached storage I said I had managed to maintain the drive letters on my external drive.

I could scrap drive letters and just use URLs

you might mean UNC paths to your NAS?

in Win 10 apparently by
mounting each drive in an NTFS directory.

That's been "a thing" since NT4, and probably NT3.5x as well
I've used it without any problems, might confuse some people when a
directory, rather than a drive gives errors about having no free space.

I know Linux and Mac OS does that anyway. Anybody actually used it in Windows? Any pros/cons? Would it work with drives on my attached storage?

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On 28/02/2024 in message <l48qrlFtn8nU3@mid.individual.net> Andy Burns
wrote:

Jeff Gaines wrote:

During the course of my post about a NAS/attached storage I said I had >>managed to maintain the drive letters on my external drive.

I could scrap drive letters and just use URLs

you might mean UNC paths to your NAS?

Indeed, that might explain why Google wasn't really my friend!

in Win 10 apparently by mounting each drive in an NTFS directory.

That's been "a thing" since NT4, and probably NT3.5x as well
I've used it without any problems, might confuse some people when a >directory, rather than a drive gives errors about having no free space.

OK, thanks :-}

I'll have a go on a spare machine and see how it feels.

--
Jeff Gaines Dorset UK
All those who believe in psychokinesis raise my hand.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Jeff Gaines <jgnewsid@outlook.com> wrote:

During the course of my post about a NAS/attached storage I said I had managed to maintain the drive letters on my external drive.

I could scrap drive letters and just use URLs in Win 10 apparently by mounting each drive in an NTFS directory.

I know Linux and Mac OS does that anyway. Anybody actually used it in Windows? Any pros/cons? Would it work with drives on my attached storage?

I believe some Windows APIs don't work with UNC paths, so some apps don't accept them.

Theo

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On 28/02/2024 19:48, Theo wrote:

I believe some Windows APIs don't work with UNC paths, so some apps don't accept them.

There are certainly programs that aren't aware of UNC paths, and so
reject perfectly valid names. Whether that's the programs trying to do
strict checking of pathnames and getting it wrong or failure of the APIs
I'm not sure.

--
Cheers,
Daniel.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

In article <urofgf$4q4s$1@dont-email.me>, Daniel James wrote...

On 28/02/2024 19:48, Theo wrote:

I believe some Windows APIs don't work with UNC paths, so some apps don't accept them.

There are certainly programs that aren't aware of UNC paths, and so
reject perfectly valid names. Whether that's the programs trying to do
strict checking of pathnames and getting it wrong or failure of the APIs
I'm not sure.

You may be able to get round this by generating a 'virtual' drive letter using the SUBST command-line operation.

--

Phil, London

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On 28 Feb 2024 at 08:23:42 GMT, ""Jeff Gaines"" <jgnewsid@outlook.com>
wrote:

During the course of my post about a NAS/attached storage I said I had managed to maintain the drive letters on my external drive.

I could scrap drive letters and just use URLs in Win 10 apparently by mounting each drive in an NTFS directory.

I know Linux and Mac OS does that anyway. Anybody actually used it in Windows? Any pros/cons? Would it work with drives on my attached storage?

Seems to me that the better idea would be to put the NAS/DAS drives into
some sort of redundant array where they appear as one volume to the
OS...

Cheers - Jaimie
--
Sent from my VAX 11/780

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On 28/02/2024 19:48, Theo wrote:

Jeff Gaines <jgnewsid@outlook.com> wrote:

During the course of my post about a NAS/attached storage I said I had
managed to maintain the drive letters on my external drive.

I could scrap drive letters and just use URLs in Win 10 apparently by
mounting each drive in an NTFS directory.

I know Linux and Mac OS does that anyway. Anybody actually used it in
Windows? Any pros/cons? Would it work with drives on my attached storage?

I believe some Windows APIs don't work with UNC paths, so some apps don't accept them.

Theo

yes you are correct but you can map a UNC to a drive letter....

Be aware that if you click on the "reconnect at Logon" option, and you
reboot with the external drive disconnected, Windows takes a longer time
to start up and also windows explorer takes longer to load as its trying desperately to reconnect to a now disconnected external drive!

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On 29/02/2024 12:39, Philip Herlihy wrote:

In article <urofgf$4q4s$1@dont-email.me>, Daniel James wrote...

On 28/02/2024 19:48, Theo wrote:

I believe some Windows APIs don't work with UNC paths, so some apps don't >>> accept them.

There are certainly programs that aren't aware of UNC paths, and so
reject perfectly valid names. Whether that's the programs trying to do
strict checking of pathnames and getting it wrong or failure of the APIs
I'm not sure.

You may be able to get round this by generating a 'virtual' drive letter using
the SUBST command-line operation.

SUBST? thats a MS DOS command surely... thats certainly a blast from the past....

Didn't think it still existed in Windows 11?

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On 29/02/2024 in message <l4bf8fFbo7rU1@mid.individual.net> Jaimie
Vandenbergh wrote:

On 28 Feb 2024 at 08:23:42 GMT, ""Jeff Gaines"" <jgnewsid@outlook.com>
wrote:

During the course of my post about a NAS/attached storage I said I had >>managed to maintain the drive letters on my external drive.

I could scrap drive letters and just use URLs in Win 10 apparently by >>mounting each drive in an NTFS directory.

I know Linux and Mac OS does that anyway. Anybody actually used it in >>Windows? Any pros/cons? Would it work with drives on my attached storage?

Seems to me that the better idea would be to put the NAS/DAS drives into
some sort of redundant array where they appear as one volume to the
OS...

Cheers - Jaimie

I don't want to close the circle so soon! I took a NAS out of service to
do this because it was impossible to tell what might be lost if the wrong drive(s) went down.

--
Jeff Gaines Dorset UK
Remember, the Flat Earth Society has members all around the globe.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Daniel James <daniel@me.invalid> writes:

On 28/02/2024 19:48, Theo wrote:

I believe some Windows APIs don't work with UNC paths, so some apps don't
accept them.

There are certainly programs that aren't aware of UNC paths, and so
reject perfectly valid names. Whether that's the programs trying to do
strict checking of pathnames and getting it wrong or failure of the
APIs I'm not sure.

I found that Lightroom[1] misbehaved in some way I can’t remember when
using a UNC path. It was easily solved by making Z: point to the same
place and telling Lightroom to use that. (Curiously Lightroom then
displays the corresponding UNC path as well.)

[1] the ancient pay-once version which is still shambling on just about
well enough for me to use.

--
https://www.greenend.org.uk/rjk/

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)