X-Recipient: archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status: No, hits=-1.9 required=5.0 	tests=AWL,BAYES_00,SARE_MSGID_LONG40,SPF_PASS
X-Spam-Check-By: sourceware.org
MIME-Version: 1.0
In-Reply-To: <4B074F7A.4060303@tlinx.org>
References: <4B061292 DOT 1060301 AT tlinx DOT org> 	 <416096c60911192258xd6b36ecy6b212f10b18eb153 AT mail DOT gmail DOT com> 	 <4B074F7A DOT 4060303 AT tlinx DOT org>
Date: Sat, 21 Nov 2009 06:12:41 +0000
Message-ID: <416096c60911202212q4cedba83pe06f61f5c12490e@mail.gmail.com>
Subject: Re: win7 specific probs; examples; and poor solutions
From: Andy Koppe <andy DOT koppe AT gmail DOT com>
To: cygwin AT cygwin DOT com
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
List-Id: <cygwin.cygwin.com>
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

2009/11/21 Linda Walsh:
>>> I still haven't figured out why -- but the values for cygdrive prefix
>>> won't stay stored.
>>
>> That's because you now have to set it in /etc/fstab to make it
>> permanent, e.g.:
>>
>> none /mnt cygdrive binary 0 0
>
> =C2=A0I did THAT, as part of my debugging. =C2=A0I copied over the line f=
rom my
> working XP config:
>
> =C2=A0none / cygdrive binary,posix=3D0,user 0 0
>
> onto my non working Win7 config -- and it had no effect on newly started
> copies of a shell (either using minTTY or console2).

So what happened instead? Did the prefix remain /cygdrive?

Please attach cygcheck output as described at
http://cygwin.com/problems.html so people can have a look at what's
wrong with that install.


> I saw a section for "The Cygdrive Path Prefix", but didn't see any option
> to reset it. =C2=A0So I copied the working line (that I didn't create. =
=C2=A0Maybe
> "mount -c" created it, but that's a guess

I think that line would have been created by setup-1.7.exe when
converting your 1.5 install. In 1.5, the cygdrive prefix was stored in
the registry.


>>> This is related to my initial complaint about the full-screen effect on
>>> setup.
>>>
>>> Setup WASN'T storing my choice -- it was blowing up to full each time.
>>>
>>> Then, ... it didn't. =C2=A0Guess it decided to store it.
>>
>> cgf recently implemented that.
>
> =C2=A0I read that he did that -- but that doesn't explain why it worked o=
n my
> XP machine, but not on my Win7 machine that was installed from the same
> install base.

FWIW, it's fine working on Win7 here. Any chance you're using an older
version of setup-1.7.exe?


> =C2=A0No waiving of hands was necessary. =C2=A0But a concrete example (us=
ing
> find+file to look text files under /prog/vim (/Program Files (x86)/Vim)
> and running dos2unix on each did run -- and 'vi' at cmd prompt worked.
> But later (yesterday, vi and cmd prompt gave CRLF related errors again. =
=C2=A0I
> reran the conversion, differently, and it worked again.
> =C2=A0I use VIMRUNDIR=3D"C:/Prog/Vim", in my environment. =C2=A0This stem=
s to a need
> for 'GVim' to know it's RUNTIME dir regardless of how it is invoked.
> =C2=A0In order for 'GVim' to effectively replace 'notepad' for all things
> text, it needs to have a link in /Windows/system32/. =C2=A0Unfortunately,=
 when
> invoked from there, it can't find it's RUNTIMEDIR. =C2=A0So I set the glo=
bal
> var.
>
> =C2=A0BUT, that created a problem for 'vim' under cygwin when I did edits=
 in
> a cmd window -- as it would pickup the runtime dir in C:/Prog/Vim.
> Fortunately, the Win-version of Gvim is advanced enough to handle
> line-endings of CRLF OR LF -- so I convert all of the text files in the
> Win-version of 'Vim/Gvim' from "CRLF" to "LF". =C2=A0Then all I need to d=
o is
> keep the versions syncronized in major point release, and the cygwin-vim
> and Win-Gvim, can share config files.
>
> =C2=A0They also share my home dir's .vimrc, .gvimrc, and .vimdir.
>
> =C2=A0In order to not have interference with cygwin's gvim, I rename it to
> "xvim" as it uses "X". =C2=A0I sometimes use it for it's better internati=
onal
> character support. =C2=A0the Windows Gvim is broken when it comes to hand=
ling
> non-monospaced character fonts (unicode) while the Cygwin X version
> handles them.
>
>
>>> unfortunately, it looks like I had part of my registry disappear as
>>> well -- the part having to do with HARDWARE appears to be missing --
>>> can't find the file it maps and going to the key gives a file-not found
>>> message.
>>
>> /proc/registry/HKEY_LOCAL_MACHINE/HARDWARE looks fine here.
>
> ---
>
> =C2=A0 Yes. =C2=A0I'm happy for you. =C2=A0And when did you first use som=
ething above
> 'XP'? =C2=A0(vista or Win7?) =C2=A0I'm still in the 'oh frack, I did what=
?!' stage.

About three years ago I guess.

$ uname -a
CYGWIN_NT-6.1-WOW64 Tobermory 1.7.0(0.218/5/3) 2009-11-19 10:07 i686 Cygwin


> =C2=A0Some suggest using the bogus string =C2=A0"C.utf-8", but that isn't=
 a valid
> locale (yet). =C2=A0I could use that, but it would cause compatibility wi=
th
> many non-broken apps that expect *valid* language strings.

And what's stopping you from setting it to "en_US.UTF-8" or whatever?

Andy

--
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