X-Spam-Check-By:	sourceware.org
To:	cygwin AT cygwin DOT com
From:	mwoehlke <mwoehlke AT tibco DOT com>
Subject:	Re: Unable to automatically map a drive letter at login
Date:	Tue, 29 Aug 2006 16:25:28 -0500
Lines:	29
Message-ID:	<ed2bc8$29b$2@sea.gmane.org>
References:	<c0a19ddd0608290838s50df9729m8e808aa0852c46b8 AT mail DOT gmail DOT com> <44F46A25 DOT 2070500 AT cygwin DOT com> <c0a19ddd0608291021t1d3dc2bbi2d843757b48b78c8 AT mail DOT gmail DOT com> <ed1v90$l9q$1 AT sea DOT gmane DOT org> <c0a19ddd0608291343h409694c1u3255253ccce89bbe AT mail DOT gmail DOT com>
Mime-Version:	1.0
User-Agent:	Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.0.5) Gecko/20060719 Thunderbird/1.5.0.5 Mnenhy/0.7.4.0
In-Reply-To:	<c0a19ddd0608291343h409694c1u3255253ccce89bbe@mail.gmail.com>
X-IsSubscribed:	yes
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Unsubscribe:	<mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com

Grant Miller wrote:
> On 8/29/06, mwoehlke <mwoehlke AT tibco DOT com> wrote:
>> Grant Miller wrote:
>>> I just rebooted one of the Windows systems and tried to SSH in to a
>>> now clean system (nobody else logged in since booting) with ssh keys
>>> and a script in my .bash_profile to attach to a drive letter and I got
>>> the same error (System error 85 has occurred).
>>>
>>> I also changed the drive letter the script was trying to map from h:
>>> to q: (a random drive letter that I haven't used before) and I still
>>> got the same error.
>>>
>>> Omitting the drive letter and using UNC paths works, but it's not
>>> going to be pretty.
>>
>> Are you using a 64-bit Windows by any chance?
> 
> I'm testing and troubleshooting on Windows Server 2003 (regular 32-bit).
> 
> My other systems are running Windows XP Pro (32-bit) and XP Pro x64,
> but we're probably going to dump the 64-bit system and stick with
> 32-bit systems (for application reasons).

Ok, because I've noticed that the 32-bit 'net.exe' on 64-bit systems 
seems to be Just Plain Broken. Sorry that wasn't it... :-)

-- 
Matthew
Ncurses. Blessing console programs since 1993.


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

- Raw text -