public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Andrey Repin <anrdaemon@yandex.ru>
To: Sridhar Ayengar <ploopster@gmail.com>, cygwin@cygwin.com
Subject: Re: setup-x86_64 Can't Download to Mapped Drive
Date: Mon, 26 Nov 2018 14:50:00 -0000	[thread overview]
Message-ID: <41253716.20181126173800@yandex.ru> (raw)
In-Reply-To: <CAFx2bNJX_fBf9M1TG1KVKz0a4YPqvZjWbW_VvGwyy-bdDYzTwg@mail.gmail.com>

Greetings, Sridhar Ayengar!

> I'm trying to use setup-x86_64.exe to update Cygwin.  The directory into
> which Cygwin is installed is C:\cygwin.  I am trying to use a network
> shared drive mapped to I: for the download directory, I:\cygwindownload.
> setup-x86_64 shows a dialog box with "Directory I:\cygwindownload does not
> exist, would you like me to create it?".  If I click "Yes", I get a dialog
> box with "Could not create directory I:\cygwindownload, sorry.  (Is drive
> full or read-only?)".  I get the same behavior even if I remove
> I:\cygwindownload and have setup-x86_64.exe try to create it.

Get off the habit of using mapped drives. Use UNC paths directly.
But for your specific issue, the drive mapped in your user session, but you
start setup within administrative session, where the drive is not mapped.
So, back to the previous statement, get off the bad habits. Or map the disk
inside adm session.


-- 
With best regards,
Andrey Repin
Monday, November 26, 2018 17:36:29

Sorry for my terrible english...


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

  reply	other threads:[~2018-11-26 14:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-26 14:18 Sridhar Ayengar
2018-11-26 14:50 ` Andrey Repin [this message]
2018-11-26 19:12   ` L A Walsh
2018-11-27 16:17   ` Sridhar Ayengar

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=41253716.20181126173800@yandex.ru \
    --to=anrdaemon@yandex.ru \
    --cc=cygwin@cygwin.com \
    --cc=ploopster@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).