[Freedos-kernel] config.sys problems with 2.0.34 and 2.0.35

[Patrick J. L. <pa...@us...>]

A while ago I reported a problem I had with FreeDOS kernel 2.0.34 and
PXELINUX+memdisk:

  http://www.mail-archive.com/fre...@li.../msg00761.html

Well, I have some more information.

First, the problem only happens on certain machines.  Right now, I can
only reproduce it on a Dell Dimension 450.

Second, and more interestingly, the problem has changed with the
release of 2.0.35.  It still only happens on my Dimenstion 450.  But
instead of not reading config.sys at all, I receive an error whenever
config.sys processes a DEVICE= or DEVICEHIGH= line.  For instance:

  CONFIG.SYS error in line 4
  DEVICE=himem64.exe
        ^

...and so on, one for each DEVICE= or DEVICEHIGH= line.

I tried using "DEVICE=A:\himem64.exe" and the same thing happened.

Once I get to a DOS prompt, "dir himem64.exe" shows that file is
present.  But I suspect something about the way files are read during
processing of CONFIG.SYS is different than how they are read once I
get to the command prompt.

Again, this only happens on one machine.  So I know the problem is not
in my config.sys file, although I am appending it below anyway.

Since the behavor improved between 2.0.34 and 2.0.35, I am hoping this
will ring a bell with someone and make this easy to fix.  This is
blocking me from upgrading beyond 2.0.33.

As always, I am ready to do whatever testing you need.  Thanks!

 - Pat


============================== config.sys ==============================
LASTDRIVE=Z
DOS=HIGH,UMB

;; Pick exactly one of these XMS providers
DEVICE=himem64.exe
;DEVICE=A:\fdxxms.sys bios ps
;DEVICE=himem.sys /testmem:off

;; UMB provider
;DEVICE=umbpci.sys
DEVICE=emm386.exe NOEMS

;; MSCLIENT networking gadget
DEVICEHIGH=\net\ifshlp.sys

;; Required for installing XP under VMware.  Thanks to Scott Card for
;; figuring this out.
FILES=30