#545 SECDEV creates bootloop

[Jacques Belin]

I am trying to use SECDEV ( http://hp200lx.net/cgi-bin/modsearch.cgi?Query=secdev )
under dosemu.

In a 64 bit context (debian sid - dosemu 1.4.0.8+20130105 - kernel 3.14-2), the driver reports to be loaded, but the boot process enters a loop displaying :

DOSEMU 1.4.0.8 (2013-01-05), configured: 2013-01-05 15:35:04 -0800
Please test against a recent version before reporting bugs and problems.
Submit Bugs & Patches to linux-msdos@vger.kernel.org or via http://dosemu.org.
FreeDOS kernel build 2036 cvs [version Aug 18 2006 compiled Aug 18 2006]
Kernel compatibility 7.10 - WATCOMC - 80386 CPU required - FAT32 support

(C) Copyright 1995-2006 Pasquale J. Villani and The FreeDOS Project.
All Rights Reserved. This is free software and comes with ABSOLUTELY NO
WARRANTY; you can redistribute it and/or modify it under the terms of the
GNU General Public License as published by the Free Software Foundation;
either version 2, or (at your option) any later version.
C: HD1, Pri[ 1], CHS=    0-1-1, start=     0 MB, size=   392 MB
D: HD2, Pri[ 1], CHS=    0-1-1, start=     0 MB, size=   392 MB
E: HD3, Pri[ 1], CHS=    0-1-1, start=     0 MB, size=   392 MB
dosemu XMS 3.0 driver installed.
dosemu EMS driver rev 0.5 installed.
SecureDevice 1.4's SECDEV.SYS 1.10
Written by Max Loewenthal & Arthur Helwig
A:\SECDEV.DSK added acting as drive F.
Kernel: allocated 41 Diskbuffers = 21812 Bytes in HMA

There is no errors in boot.log (see boot.log.64).

In a 32 bit context (ubuntu 10.10 - dosemu 1.4.0+svn.1999 - kernel:2.6.35), the boot process crashes with a General Protection error (see boot.log.32).

The Secdev.dsk container I use is an existing one, created on anoher setup. Anyway, it is not involved during the driver loading.

Note : The SECDEV source files (ASM + C) are also included in the archive.

[Stas Sergeev]

This seems to use DPBs to access local FAT
volumes, but dosemu only provides a read-only
access for emulated local volumes. This is
needed only on early boot.
The read-write access happens when DOS makes
a network redirector calls, which is a file-level
access, not a volume-level access.
So I don't think dosemu should support this.
Instead you can set up crypto on host FS.

Still, if you set up dosemu to work with
hd image (see mkfatimage16 tool), then this
will probably work. But hd image is an unsupported
functionality currently, so it may as well not
work either. :)

[Stas Sergeev]

And if it crashes right at boot, it
may be because of something else.
Try MS-DOS instead of FreeDOS first.
It will not work because of the aforementioned
reasons, but it of course should not
just crash at boot.