set device info

[[e-mail]]

Hi.

I am getting this:

C:\>fdtest


The shell is about to be terminated, though, this is
forbidden (usually by enabling the "/P" option).
You must reboot the system or, if this shell runs in
a multitasking environment, terminate this process/task manually.

when I run this:

C:\devel\pdos\pdpclib>type fdtest.asm
.model small

.stack 1000h

.code

top:

mov ah, 044h
mov al, 01h
mov bx, 0
;mov dx, 081h
mov dx, 0h

int 021h

mov ah, 04ch
int 021h

end top


under Freedos 1.3.

I don't get that problem on a Win 95 command prompt.

Using 1 or 81h (for dx) gives the same result.

The code seems to be conforming to this:

http://www.ctyme.com/intr/rb-2821.htm
http://www.ctyme.com/intr/rb-2820.htm

Note that the original real code does a get device
info first, and has a device information word of 0,
but I may have stuffed that test up.

Is my code correct, and thus, does some component
of Freedos (or some other part of my system) have a bug?

Compilation is as below.

Thanks. Paul.



C:\devel\pdos\pdpclib>wasm fdtest.asm
Open Watcom Assembler Version 1.6
Portions Copyright (c) 1992-2002 Sybase, Inc. All Rights Reserved.
Source code is available under the Sybase Open Watcom Public License.
See http://www.openwatcom.org/ for details.
fdtest.asm: 20 lines, 0 warnings, 0 errors

C:\devel\pdos\pdpclib>wcl fdtest.obj
Open Watcom C/C++16 Compile and Link Utility Version 1.6
Portions Copyright (c) 1988-2002 Sybase, Inc. All Rights Reserved.
Source code is available under the Sybase Open Watcom Public License.
See http://www.openwatcom.org/ for details.
wlink @__wcl__.lnk
Open Watcom Linker Version 1.6
Portions Copyright (c) 1985-2002 Sybase, Inc. All Rights Reserved.
Source code is available under the Sybase Open Watcom Public License.
See http://www.openwatcom.org/ for details.
loading object files
creating a DOS executable

[JJ]

Post by ***@gmail.com
Hi.
C:\>fdtest
The shell is about to be terminated, though, this is
forbidden (usually by enabling the "/P" option).
You must reboot the system or, if this shell runs in
a multitasking environment, terminate this process/task manually.
C:\devel\pdos\pdpclib>type fdtest.asm
.model small
.stack 1000h
.code
mov ah, 044h
mov al, 01h
mov bx, 0
;mov dx, 081h
mov dx, 0h
int 021h
mov ah, 04ch
int 021h
end top
under Freedos 1.3.
I don't get that problem on a Win 95 command prompt.
Using 1 or 81h (for dx) gives the same result.
http://www.ctyme.com/intr/rb-2821.htm
http://www.ctyme.com/intr/rb-2820.htm
Note that the original real code does a get device
info first, and has a device information word of 0,
but I may have stuffed that test up.
Is my code correct, and thus, does some component
of Freedos (or some other part of my system) have a bug?
Compilation is as below.

[snip]

With the same code, the only difference is the OS. So obviously the cause is
in the OS, and not the code. Either the command interpreter, or the OS
kernel itself.

FYI, no other DOS OS is trully compatible with MS-DOS - including it's
quirks. PC-DOS is excluded, since it's just a rebranded MS-DOS.