The FreeDOS Project

>I just like to share, that I have received the following error message
when
>using fat16, latest command.com from kernel homepage and i386 16 bit
>version of the kernel.
...
>There is only one primary partition and it is setup for fat32...

@msdos622:
There is no FreeDOS 32-bit kernel (in the usual sense of 32-bit).
The "32" in the kernel name indicates that it supports FAT32, as well as
FAT12/16; a "16" indicates that FAT32 is disabled, so only FAT12/FAT16 are
supported.

From what you're saying (quote #2), it sounds like you may be using a
FAT12/16 only kernel with a FAT32 partition, in which case this behavior is
not a bug.
FDISK /STATUS (or FDISK /DUMP) should allow verifying the partition
format.

After another install I noticed the installer still installs the 32bit
kernel version even though I setup a 16bit 2gb partition. I do not know if
this will create problems in clarifing the kernel naming.

In regards to windows, I have been able to get Windows For Work Groups
working in real mode using the "win /D:T"

[CONFIG.SYS]
SET DOSDIR=C:\FDOS
LASTDRIVE=Z
BUFFERS=38
FILES=38
DOS-HIGH, LIMB
DEVICE=C:\UIN311\HIMEM.SYS
DEVICE=C:\UIN311\EMM386.EXE NBEMS
SHELL=C:\FDOS\BIN\C0MMAND.COM C:\FDOS\bin /E:1024 /P=C:\AUTOEXEC.BAT

[AUTOEXEC.BAT]
@echo off
SET LANG=EN
SET MTCPCFG=C:\FDOS\MTCP.CFG
SET WATTCP.CFG=C:\FDOS
SET PATH=%dosdir%\BIN;C:\WIN311
SET NLSPATH=%dosdir%\NLS
SET HELPPATH=%dosdir%\HELP
SET TEMP=%dosdir%\TEMP
SET TMP=%TEMP%
SET BLASTER=A220 I5 D1 H5 P330
SET DIRCMD=/P /OGN /4
SET COPYCMD=/-Y
REM LH DOSLFN
REM NLSFUNC C:\FDOS\BIN\COUNTRY.SYS
REM DISPLAY CON=(EGA),858,2)
REM MODE CON CP PREP=((858) C:\FDOS\CPI\EGA.CPX)
REM KEYB US,858,C:\FDOS\bin\keyboard.sys
REM CHCP 858
REM LH PCNTPK INT=0x60
REM MOUSE
REM DEVLOAD /H /Q %dosdir%\BIN\UIDE.SYS /H /D:FDCD0001 /S5
REM SHSUCDX /QQ /D3
REM SHSUCDHD /QQ /F:FDBOOTCD.ISO
REM SHSUCDX /QQ /~ /D:?SHSU-CDR,D /D:?SHSU-CDH,D /D:?FDCD0001,D
/D:?FDCD0002,D /D:?FDCD0003,D
REM MEM /C /N
GOTO DONE

:END
LH FDAPM APMDOS

SET AUTOFILE=%0
SET CFGFILE=C:\FDCONFIG.SYS
alias reboot=fdapm warmboot
alias reset=fdisk /reboot
alias halt=fdapm poweroff
alias shutdown=fdapm poweroff
alias cfg=edit %cfgfile%
alias auto=edit %0
GOTO DONE

:DONE
echo Done processing startup files %cfgfile% and %0
echo Type HELP to get support on commands and navigation
echo.
echo Welcome to the FreeDOS 1.1 operating system (http://www.freedos.org)

I just like to share, that I have received the following error message when
using fat16, latest command.com from kernel homepage and i386 16 bit
version of the kernel.

JeiwEx v5.75 [85/21/11] JeMMEx loaded
Kernel: allocated 55 Diskbuffers = 29268 Bytes in HMR
FreeCoM version 8.84-pre2 XMS_Swap [Jul 17 2811 21:46:461 MCB chain
corrupt, or MS-DBS incotipatible systeti. MCB chain corrupt, or MS-DBS
incompatible system. MCB chain corrupt, or MS-DBS incompatible system.
UelcoMe to the FreeDOS 1.1 operating systeM (http://NNN.freedos.org)


C:s>chkdsk
ChkDsk beta 8.9.2
Copyright 2882, 2883, 2889 Itire Leber under the GNU GPL
\CRYNUR is a directory without \TESTDISK is a directory without
The entry in \RRRCHNE is not pointing to the right directory
\D0SUSB28 is a directory without
\FDGS\SGURCE is a directory without ‘..’
\FDOS\DRIUERS is a directory without‘..’
\UIND0US\DISK1 is a directory without‘..’
\UIND0US\DISK2 is a directory without‘..’
\UINDGWS\DISK3 is a directory without‘..’
The entry in \UIND0US\DISK4 is not pointing to the right directory
\UINDGWS\DISK5 is a directory without‘..’
The entry in \UIND0US\DISK6 is not pointing to the right directory
\UINDGWS\DISK7 is a directory without‘..’
\NIND0NS\DISK8 is a directory without‘..’
\UINDGWS\SYSTEM is a directory without
SCRYNUR doesn't contain an '.' as first entry
Error accessing the voluiie
C:\>

In regards to wfw 3.11 and freedos, that it is not supported.

Yes that should be the reason - the particular kernels you were using do
not support FAT32 so although it boots fine from an unsupported partition
(as the boot loader will load the entire kernel into memory) when the
kernel goes to load the shell (command.com) it won't be able to find it
since it does not understand the file system. I believe the naming of the
kernels for selection should be made more clear to note the 32 corresponds
only to FAT32 supported.

There is only one primary partition and it is setup for fat32, running in
VMware 7.1.4. Thinking this over I believe this is the problem, since it
only can support fat16 format. I have included the following information as
requested if the above is not true. Tnx..

The Bios Reports the following.

Total Sectors: Maxinun Capacity:

LBA Fornat
- Total Sectors: 16777216
- Total Capacity: 8590MB

Multi Sector Transfers: [16 Sectors]
LBA Node Control: [Enabled]
32 Bit I/O: [Disabled]
Transfer Node: [FPIO 4 / DMA 21
Ultra DMA Mode: [Mode 2]

Could you provide some information about your partition. I assume it is
FAT16 since you are using the FAT12/16 only kernel. Are there other
partitions? would it be possible to give some indication of size and
placement on disk (ie 1st partition, last partition or CHS/LBA location)?
I appreciate any information to help ensure I can duplicate. Could you try
the FAT32 enabled kernel as well to help narrow down where to issue resides
(common code or a code path unique to the FAT12/16 kernel). Thank you.

The 8086 version of the kernel seems to experience the same problem.