[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
interrupt 001E
|
From: |
Tomas By |
|
Subject: |
interrupt 001E |
|
Date: |
Sun, 17 Jan 2021 13:13:07 +0100 |
|
User-agent: |
Wanderlust/2.15.9 (Almost Unreal) SEMI-EPG/1.14.7 (Harue) FLIM/1.14.9 (Gojō) APEL/10.8 EasyPG/1.0.0 Emacs/26 (x86_64-pc-linux-gnu) MULE/6.0 (HANACHIRUSATO) |
Hi,
On Sun, 17 Jan 2021 02:43:05 +0100, Berto Furth wrote:
> Interrupt 0x1E seems to be related to "SYSTEM DATA - DISKETTE
> PARAMETERS" according to Ralf Brown's interrupt list. Could a disk
> drive be misconfigured?
On Sun, 17 Jan 2021 11:52:19 +0100, Berto Furth wrote:
> I'm afraid I don't really know what's happening (hopefully someone
> else will!).
If I were to guess, I would say it probably has to do with file
locking, or whatever is the equivalent concept in DOS.
/Tomas
- Re: Re: When qemu starts kernel image (given by -kernel option), d eos it initialize CPU registers like firmwares and bootloaders do before kernel loading?, Tomas By, 2021/01/16
- Re: When qemu starts kernel image (given by -kernel option), d eos it initialize CPU registers like firmwares and bootloaders do before kernel loading?, Berto Furth, 2021/01/16
- Re: Re: When qemu starts kernel image (given by -kernel option), d eos it initialize CPU registers like firmwares and bootloaders do before kernel loading?, Tomas By, 2021/01/17
- interrupt 001E, Tomas By, 2021/01/17
- Re: When qemu starts kernel image (given by -kernel option), d eos it initialize CPU registers like firmwares and bootloaders do before kernel loading?, Berto Furth, 2021/01/17
- interrupt 001E, Tomas By, 2021/01/17
- interrupt 001E,
Tomas By <=
- Re: interrupt 001E, Jakob Bohm, 2021/01/18
- Re: interrupt 001E, Tomas By, 2021/01/19