Initializing and cygwin.bat

Initializing and cygwin.bat

[CBFalconer]

As a new user I wanted to customize cygwin.bat to my system, which
uses 4dos as the shell and only maintains command.com as an
antique.  W98 BTW.

I found that various commands wouldn't work!  The reason was that
command.com was being called in the .pif file.  I simply changed
the .pif to specify "%comspec%" in place of
"c:\windows\command.com".

Is there any reason setup shouldn't do this in the initial
creation?  Since the .pif files are of some peculiar structure I
had to use explorer and the fursluginner mouse to make this
change.

-- 
Chuck F (cbfalconer@yahoo.com) (cbfalconer@worldnet.att.net)
   Available for consulting/temporary embedded and systems.
   <http://cbfalconer.home.att.net>  USE worldnet address!



--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: Initializing and cygwin.bat

[Sven Köhler]

> As a new user I wanted to customize cygwin.bat to my system, which
> uses 4dos as the shell and only maintains command.com as an
> antique.  W98 BTW.
> 
> I found that various commands wouldn't work!  The reason was that
> command.com was being called in the .pif file.  I simply changed
> the .pif to specify "%comspec%" in place of
> "c:\windows\command.com".
> 
> Is there any reason setup shouldn't do this in the initial
> creation?  Since the .pif files are of some peculiar structure I
> had to use explorer and the fursluginner mouse to make this
> change.

i don't use the batch-file anymore.
i changed the shortcut to execute bash.exe --login diretly, which avoids 
a stupid question by cmd.exe after bash exists and Ctrl-C was pressed:
   Abort Execution (Y/N)
text may be different in englisch (using german windows)

i don't know, if this work for you, but instead of changing the 
batch-file, you could change /etc/profile which is the first script 
bash.exe executes (when run with the --login paramter)

starting bash without a batch-file also avoids the idle cmd.exe or 
commmand.com process :-)

BTW: why is cygwin installed with that batch-file, and why doesn't the 
setup create shortcuts to the command "bash.exe --login" but to cygwin.bat?
Has this been done for some reason?




--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: Initializing and cygwin.bat

[Gerrit P. Haase]

Hallo Sven,

> BTW: why is cygwin installed with that batch-file, and why doesn't
> the setup create shortcuts to the command "bash.exe --login" but
> to cygwin.bat?
> Has this been done for some reason?

Some environment settings need to be done before the first Cygwin
process starts, e.g. CYGWIN settings like 'ntsec tty binmode notitle
...'.  'ntsec' is on by default now but you still may also use
others.  You don't need to set them globally in the Windows
environment if you set them in the batch file.  There may be some more
reasons why there is this batch file?  Maybe there were no patches to
change this?


Gerrit
-- 
=^..^=


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: Initializing and cygwin.bat

[Sven Köhler]

> >BTW: why is cygwin installed with that batch-file, and why doesn't
> >the setup create shortcuts to the command "bash.exe --login" but
> >to cygwin.bat?
> >Has this been done for some reason?
>
>
> Some environment settings need to be done before the first Cygwin
> process starts, e.g. CYGWIN settings like 'ntsec tty binmode notitle
> ...'.  'ntsec' is on by default now but you still may also use
> others.  You don't need to set them globally in the Windows
> environment if you set them in the batch file.  There may be some more
> reasons why there is this batch file?  Maybe there were no patches to
> change this?

there's also a registry-entry where you can set the "default" values

[HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\Cygwin\Program Options]
"default"="ntsec tty codepage:oem"

Chris was so kind to tell me about it ;-)




--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

RE: Initializing and cygwin.bat

[Gary R. Van Sickle]

> Hallo Sven,
>
> > BTW: why is cygwin installed with that batch-file, and why doesn't
> > the setup create shortcuts to the command "bash.exe --login" but
> > to cygwin.bat?
> > Has this been done for some reason?
>
> Some environment settings need to be done before the first Cygwin
> process starts, e.g. CYGWIN settings like 'ntsec tty binmode notitle
> ...'.  'ntsec' is on by default now but you still may also use
> others.

I find it best to simply set this in your regular Windows environment.  That
way, regardless of how you end up invoking cygwin prog's you get the same
behavior.

>  You don't need to set them globally in the Windows
> environment if you set them in the batch file.  There may be some more
> reasons why there is this batch file?  Maybe there were no patches to
> change this?

I suspect it's the latter.  I personally never use the batch file anymore, and
can't think of a reason why it would still be necessary or desireable,
especially with rxvt working well these days.

--
Gary R. Van Sickle
Brewer.  Patriot.



--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/