Mail Archives: djgpp/1998/03/17/03:06:21
Eli Zaretskii wrote:
>
> On Sun, 15 Mar 1998, Mitchell Spector wrote:
>
> > > Please post the same system information that Philippe posted. I would
> > > like to look for common peculiarities in your two configurations.
> >
> > See below. I appreciate your looking at this.
>
> Thanks, but I meant mainly the CONFIG.SYS, AUTOEXEC.BAT and the output
> of the command "set" when typed in a DOS box configured exactly as you
> do to run Bash. Please post these.
Sorry, I should have included those too. Here they are:
--------------
CONFIG.SYS
REM Tip: Put the real-mode driver for your CD-ROM in here.
REM It won't be used by Windows 95, but it will be used if you
REM choose "Restart your computer in MS-DOS mode" from
REM the Shutdown menu in Windows or if you choose F8 and select
REM one of the Startup menu options that let you enter into MS-DOS
REM instead of loading the Windows 95 GUI.
REM
REM Be sure the information following the /D switch on the CD-ROM
REM driver matches the information following the /d: parameter on
REM MSCDEX loaded in Autoexec.bat.
[COMMON]
FILES=40
BUFFERS=20
NUMLOCK=ON
DEVICE=C:\WINDOWS\HIMEM.SYS /TESTMEM:OFF
DOS=HIGH,UMB
device=c:\cddrv\d011v109.sys /D:toscd001
--------------
AUTOEXEC.BAT
@ECHO OFF
SET MSINPUT=C:\MSINPUT
REM c:\windows\command\mscdex /d:toscd001 /m:15 /l:e
SET BLASTER=A220 I5 D1 T4
REM SET WSSCFG=A530 I11 D0
SET DJGPP=C:\DJGPP\DJGPP.ENV
SET PATH=C:\DJGPP\BIN;%PATH%
SET PGPPATH=C:\PGP262
SET PATH=C:\PGP262;%PATH%
SET PATH=C:\JDK1.1.4\BIN;%PATH%
SET TZ=PST8PDT
--------------
Output of "set", as typed in a DOS box (configured exactly as when
I run bash)
TMP=C:\WINDOWS\TEMP
TEMP=C:\WINDOWS\TEMP
PROMPT=$p$g
winbootdir=C:\WINDOWS
COMSPEC=C:\WINDOWS\COMMAND.COM
MSINPUT=C:\MSINPUT
DJGPP=C:\DJGPP\DJGPP.ENV
PGPPATH=C:\PGP262
PATH=C:\JDK1.1.4\BIN;C:\PGP262;C:\DJGPP\BIN;C:\WINDOWS;C:\WINDOWS\COMMAND
TZ=PST8PDT
windir=C:\WINDOWS
BLASTER=A220 I5 D1 T4
--------------
Output of "set", as typed within bash. (You didn't ask for this,
but maybe it would be useful.)
BASH=c:/djgpp/bin/bash.exe
BASH_VERSION=1.14.7(1)
BLASTER=A220 I5 D1 T4
CMDLINE=bash
COMSPEC=C:\WINDOWS\COMMAND.COM
DJDIR=c:/djgpp
DJGPP=C:\DJGPP\DJGPP.ENV
EMU387=c:/djgpp/bin/emu387.dxe
EUID=42
HISTFILE=//.bash_history
HISTFILESIZE=500
HISTSIZE=500
HOSTTYPE=PCAT
IFS=
LFN=y
MAILCHECK=60
MSINPUT=C:\MSINPUT
OPTERR=1
OPTIND=1
OSTYPE=MSDOS
PATH=C:/JDK1.1.4/BIN;C:/PGP262;C:/DJGPP/BIN;C:/WINDOWS;C:/WINDOWS/COMMAND
PGPPATH=C:\PGP262
PPID=1
PROMPT=$p$g
PS1=bash\$
PS2=>
PS4=+
PWD=c:/windows
SHELL=C:\WINDOWS\COMMAND.COM
SHLVL=1
TEMP=C:\WINDOWS\TEMP
TMP=C:\WINDOWS\TEMP
TMPDIR=c:/djgpp/tmp
TZ=PST8PDT
UID=42
USER=dosuser
winbootdir=C:\WINDOWS
windir=C:\WINDOWS
> [Clipped.]
>
> > Within bash, I can run both built-in commands and regular DOS
> > executables (like XCOPY) without difficulty. It seems to be
> > just djgpp executables that cause bash to hang.
>
> Bash pulls out some very complicated tricks when it runs DJGPP
> programs, to make up for several blatant bugs in some commercial DPMI
> servers (resource leaks and such likes) which raise their ugly head
> when running nested DPMI programs, like when Bash invokes another
> DJGPP program. Something in your setup triggers some obscure bug in
> that part.
That is consistent with bash running correctly when I boot directly to
DOS, since Windows 95's DPMI server wouldn't be running then.
Thank you again, Eli, for looking at this.
Mitchell
--
Mitchell Spector, Enchanted Learning Software
E-mail: spector AT EnchantedLearning DOT com
Visit Little Explorers, Zoom Dinosaurs, and much more!
-- http://www.EnchantedLearning.com --
- Raw text -