Message-ID: <351832F1.2828@CGSTE.MQ>
Date: Tue, 24 Mar 1998 16:25:53 -0600
From: HANRIGOU Philippe <HANRIGOU AT cgste DOT mq>
Reply-To: HANRIGOU AT cgste DOT mq
Organization: CONSEIL GENERAL DE LA MARTINIQUE / DGA2
MIME-Version: 1.0
To: "Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>; Nate Eldredge <eldredge AT ap DOT net>; Martin DOT Stromberg AT lu DOT erisoft DOT se; Mitchell Spector" <spector AT EnchantedLearning DOT com>
CC: djgpp AT delorie DOT com
Subject: Re: Problem with bash
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
Precedence: bulk

Hi,                
                 
Sorry for not having responded before, but I was taking a few
holidays... without bash! ;-)

Mitchell Spector wrote:
> What I noticed was that if I type 16 characters
> (getting no apparent response at all), the system then starts to beep
> at each character typed, as if I had exceeded the length of an
> input buffer.

I've got exactly the same behaviour.

Eli Zaretskii wrote:
> Since you are running Windows 95, the version of COMMAND.COM which
> comes with Windows is C:\WINDOWS\COMMAND.COM.  Please see if changing
> the above directive to the following helps:
> 
>   SHELL=C:\WINDOWS\COMMAND.COM C:\WINDOWS /E:1024 /P
> 
> > DEVICEHIGH=C:\WINDOWS\COMMAND\ANSI.SYS
> > device=C:\WINDOWS\COMMAND\display.sys con=(ega,,1)
> > Country=033,850,C:\WINDOWS\COMMAND\country.sys 
> Try not to load these and see if that helps.
> 
> > mode con codepage prepare=((850) C:\WINDOWS\COMMAND\ega.cpi)
> > mode con codepage select=850
> > keyb fr,,C:\WINDOWS\COMMAND\keyboard.sys
> Also try not loading these.
> [strip]
> I would also remove the HOME variable and see if that helps.
> [strip]
> That's an *extremely* long PATH!  Could you please try making it
> shorter than 127 characters and see whether that helps?
> [strip]
> Try making this a Unix-style path name, like so:
> 
>     TMPDIR=c:/tmp

I've tried all these modifications (see below new config.sys and 
autoxec.bat files). Unfortunately, everything's the same !!!

============= File CONFIG.SYS =============

DEVICE=C:\WINDOWS\HIMEM.SYS
DEVICE=C:\WINDOWS\EMM386.EXE NOEMS X=CC00-CFFF
DOS=HIGH,UMB
SHELL=C:\WINDOWS\COMMAND.COM C:\WINDOWS /E:1024 /P

========= End of file CONFIG.SYS ==========


============ File AUTOEXEC.BAT ============

SET TZ=cst6cdt
@ECHO OFF
PROMPT $p$g
PATH C:\WINDOWS;C:\WINDOWS\COMMAND;C:\;C:\DOS
SET TEMP=c:\temp
SET PATH=%PATH%;C:\IEXPLORE\mail
SET PATH=%PATH%;C:\IEXPLORE
set ieppp=C:\IEXPLORE
set pctcp=C:\IEXPLORE\pctcp.shv

rem ----------- DJGPP ----------
set PATH=%path%;d:\ph\bin\bin\djgpp\bin
set DJGPP=d:\ph\bin\bin\djgpp\djgpp.env
set INFOPATH=d:\ph\bin\bin\djgpp\info
set TMPDIR=c:/tmp
set LFN=Y

======== End of file AUTOEXEC.BAT =========

Eli Zaretskii wrote:
> > makefiles were developped under Unix (or Linux) as some "littles things"
> > do not work: for instance main makefile try to create a ".notified" file
> > using "touch .notified" which do not seam to work under windows95
> 
> It *should* work on Windows 95, unless you disabled the long file
> names support.  Try setting LFN=y in the environement.
> 
Nate Eldredge wrote:
> 
> I think setting `LFN=Y' in your environment will let this work. Try that.

Yes, It solves the ".notified" problem. Thank you to both of you for
this
piece of advice. Nevertheless, a few other problems still remain when
I try to compile bash.

Martin Stromberg wrote:
> I have a bash compiled with -g. If you want I can mail it to you. So you
> can run symify on the tracebacks (which have to be redone, of course).
> 
> But bevare, it's big: ~1.4Mb. Mail me if you want it.
> 
> Your mailbox'll go "Groink!!",
> 
Great, I need that! Thank you very much wasting your time for me.
I haven't succeeded yet in compiling this ?%*$# code, and I guess it's
just because it's too difficult for me... I learn a lot of things but
I've got the bad feeling that I'm still far from any result!!!
But why not putting your bash compiled with -g, your modified makefiles,
newversion.c and sed scripts in some ftp site? That way we could easily
download them, compile bash and add a few "strategic printf" to try to 
localize the problem without "Groinking" our mailbox. Nevertheless, if 
you've got no access to a ftp site, just mail me everything you can to
make bash compile... 

That's all. Thank you again to all of you for your help.

Regards,
Philippe.

-- 
_______________________________________________________________________
  
     Philippe HANRIGOU           Conseil Général de la Martinique
  Ingénieur informatique              D.D.S.T. - service I.T.S.
                                Immeuble Concorde, route de la Folie
   Tél: (0596) 59-84-63                  97200 Fort de France
  E-mail: hanrigou AT cgste DOT mq                      FRANCE
_______________________________________________________________________