INT15's are typically a result of unexpected interrupts or a printer
acknowledge IRQ; ignore them. INT16's are video requests; function 1 in
this case sets the cursor type. The video requests are done to draw the
boot menu that (probably) lets you pick whether to boot w/ or w/o certain
device support (e.g. SCSI or CD-ROM). When I hit this I got further by
running doscmd w/ the -x option; sounds like that's not an option for you
(though beware I was running on BSD/OS 4.0 and not FreeBSD).
If you want to learn about this sort of stuff get a copy of The Undocumented
PC.
I'd be interested in talking to anyone that's successfully using doscmd to
do anything. I want to use it to run a DOS app that communicates with a
Panasonic KSU but can't seem to get keyboard input to work when using an X
window.
Sam
----- Original Message -----
From: "Alexey N. Dokuchaev" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, March 08, 2000 12:44 AM
Subject: doscmd under FreeBSD 4.0 20000214-SNAP
> Hi!
>
> There's a problem. I'm trying to run ${SUBJ} unsing MSDOS 6.22 bootable
> diskette, with .doscmdrc file from man doscmd(1). That's what I get:
>
> Unknown interrupt 15 function 4101
> Unknown interrupt 15 function 8796
> doscmd: fatal error int16 func 0x1 only supported in X mode
>
> If I try to run 'doscmd -r', I get:
>
> mmap: Invalid argument
>
> Any ideas? I have no X installed, btw. I'll try MSDOS 6.0, but I don't
> think version really matters at this early stage :-(
>
> P.S. and what happened to that "VM86" option in kernel?
>
>
>
> To Unsubscribe: send mail to [EMAIL PROTECTED]
> with "unsubscribe freebsd-hackers" in the body of the message
>
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
