Message-Id:	<4.3.2.7.0.20000806034311.00b0a360@pop5.inter.nl.net>
X-Sender:	fvdbogaa AT pop5 DOT inter DOT nl DOT net
X-Mailer:	QUALCOMM Windows Eudora Version 4.3.2
Date:	Sun, 06 Aug 2000 03:43:49 +0200
To:	opendos AT delorie DOT com
From:	Frans van den Bogaard <F DOT vandenBogaard AT inter DOT NL DOT net>
Subject:	DR-DOS 7.03: bug in Install-procedure??
Mime-Version:	1.0
Reply-To:	opendos AT delorie DOT com

--=====================_18653480==_
Content-Type: text/plain; charset="us-ascii"; format=flowed

To my surprise I found this List Server, indicating a live DR-DOS community.

I add a small article concerning a supposed bug in the Install-procedure.
Can anybody confirm this? 
--=====================_18653480==_
Content-Type: text/plain; charset="us-ascii"

#DRDOS-1.BUG dd. 03.08'2000 / FvdB.

It looks like a bug in Install/Setup DRDOS 7.03.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
but... finally I found it.

I installed DRDOS 7.03 on a Windows 95-OSR2 machine, with 4DOS 6.02b as
command-processor.
Working with my PC it looks like the system is functioning correctly.
Checking - and playing with - AutoDOS7.bat vs Autoexec.bat and DConfig.sys vs
Config.sys I found that the boot-procedure of DRDOS 7.03 does not read the
correct files.

The DRDOS boot-procedure should read first DConfig.sys followed by AutoDOS7.bat.
I marked the 4 files with: "Echo 'Reading Config.sys' or Echo 'Reading
DConfig.sys' " in the [D]Config.sys files and
in the batch-file Autoexec.bat: 'Set STRT=Win95' and in AutoDOS7.bat: 'Set
STRT=DRDOS7'.
That makes it easy to follow the used files -  with C:>SET you can see which
batch-file was read.

I found that the DRDOS boot-procedure starts by reading DConfig.sys but was
_always_ followed by reading the Win95 Autoexec.bat-file; so the DRDOS-specific
commands were not executed or installed.

This behaviour was independent of the used command-processor: DRDOS Command.com
or 4DOS.com.

I UnInstalled DRDOS, cleared carefully all used directories and installed DRDOS
again, with exact the same results.

I tried to find the program that called the Autoexec.bat file.
Finally - using a hex-editor - I found this entry in the command-processors
[drdos]Command.com, respectively [4dos6]4Dos.com.
The first 'Autoexec'-entry in both files is the one to be changed to
'AutoDOS7'.

Testing both command-processors I found that the correct procedure was used now:
it starts by reading 'DConfig.sys', then the used (changed) commandprocessor is
loaded, which reads 'AutoDOS7.bat'.

Some details:
In d:\drdos\ I added a changed copy of Command.com: CommandDOS7.com.
In C:\ I deleted the original Command.com and renamed a copy of CommandDOS7.com
to Command.com.

In d:\4dos6\ I added a changed copy of 4Dos.com: 4DosDOS7.com.
In the Win95 Config.sys file I used the shell-command:

SHELL=D:\4DOS6\4DOS.COM D:\4DOS6\ /P

but in the DRDOS DConfig.sys I used as the shell-command:

SHELL=d:\4dos6\4dosDOS7.com d:\4dos6 /P.

COMMENT:
I expected the DRDOS-installation procedure - that checks on the availability of
Win95 - to change the command-file accordingly, but in both installations this
failed.
I don't know if this is a bug or if I did something wrong!
Can somebody confirm this possible bug?



Frans van den Bogaard
Amsterdam / The Netherlands.
F DOT vandenBogaard AT inter DOT nl DOT net


--=====================_18653480==_
Content-Type: text/plain; charset="us-ascii"; format=flowed

Frans van den Bogaard
    Amsterdam             Fax : (31) (0)20 646 25 26 (via Reprohouse)
    The Netherlands     E-Mail: F DOT vandenBogaard AT inter DOT nl DOT net

--=====================_18653480==_--

- Raw text -