> After exhausting all other avenues I'm asking for help on dosemu. It
> seems that when I try to boot from a floppy disk the system hangs eg:
> dosemu -A. I end up having to kill the process and trying again.
There is a mailing list archive you can find from http://www.dosemu.org
which answers your question:
>From vger.rutgers.edu!owner-linux-msdos-outgoing Fri May 21 07:20:57 1999
Return-Path: <vger.rutgers.edu!owner-linux-msdos-outgoing>
Received: by erewhon
id m10kYNE-000AFra
(Debian Smail-3.2 1996-Jul-4 #2); Fri, 21 May 1999 07:20:56 +1200 (NZST)
Sender: vger.rutgers.edu!owner-linux-msdos-outgoing
Received: from mx1.ix.net.nz ([EMAIL PROTECTED] [203.97.100.27])
by planet.ak.planet.gen.nz (8.8.8/8.8.8) with ESMTP id TAA06981
for <[EMAIL PROTECTED]>; Thu, 20 May 1999 19:31:39 +1200 (NZST)
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
by mx1.ix.net.nz (8.8.8/8.8.5) with ESMTP id TAA27586;
Thu, 20 May 1999 19:36:08 +1200
Received: by vger.rutgers.edu via listexpand id <S.rEkzJ160959>; Wed, 19 May 1999
15:24:05 -0400
Received: by vger.rutgers.edu id <S.rEa.M160343>; Wed, 19 May 1999 02:54:16 -0400
Received: from Cantor.suse.de ([194.112.123.193]:10839 "HELO Cantor.suse.de") by
vger.rutgers.edu with SMTP id <S.rEM43184478>; Tue, 18 May 1999 11:04:37 -0400
Received: from Galois.suse.de (Galois.suse.de [194.112.123.130])
by Cantor.suse.de (Postfix) with ESMTP id E802732D03
for <[EMAIL PROTECTED]>; Tue, 18 May 1999 17:53:26 +0200 (MEST)
Received: from metcalf.suse.de (Metcalf.suse.de [10.0.0.10])
by Galois.suse.de (Postfix) with ESMTP id DDB2F9411
for <[EMAIL PROTECTED]>; Tue, 18 May 1999 17:53:26 +0200 (MEST)
Received: from localhost (localhost [[UNIX: localhost]])
by metcalf.suse.de (8.9.3/8.9.3) id RAA00427
for [EMAIL PROTECTED]; Tue, 18 May 1999 17:53:26 +0200
From: Steffen Winterfeldt <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: Re: floppy A: B:, vbootfloppy and 0.98.6
Date: Tue, 18 May 1999 17:40:00 +0200
X-Mailer: KMail [version 1.0.17]
Content-Type: text/plain
MIME-Version: 1.0
Message-Id: <99051817532600.00394@metcalf>
Content-Transfer-Encoding: 8bit
Sender: [EMAIL PROTECTED]
Precedence: bulk
X-Loop: [EMAIL PROTECTED]
X-Orcpt: rfc822;linux-msdos-outgoing-dig
Status: RO
> I have spent hours and hours working with my dosemu setup because
> no matter how I configure it, I could not access floppy A: This
> is version 0.98.6
>
> If I used _vbootfloppy the BOOTOFF.COM program was
> non-functional. I could never see anything but the boot image.
>
> So yesterday I made a hard drive image to boot from instead.
> When I use that, then everytime I try to read or write from the
> floppy drive it spins for just a moment and locks up. (Just
> dosemu, of course, not the whole machine).
>
> So I tried the new "boot directory" option. Unfortunately it was
> just as with the hard drive image. The floppy spins for a moment
> and locks the emulator.
Actually, you describe *two* problems. :-(
> I finally found an answer tucked in the mail archives (where I
> must have missed it before). It was the following patch to
> 0.98.6
Below is the �official� fix for this that will go into 0.98.7:
--- dosemu-0.98.6.2/src/base/misc/utilities.c Fri Mar 26 20:02:54 1999
+++ dosemu-0.98.6.3/src/base/misc/utilities.c Mon May 17 22:29:35 1999
@@ -506,15 +506,16 @@
void sigalarm_onoff(int on)
{
- static struct itimerval itv_old_;
- static struct itimerval *itv_old = &itv_old_;
+ static struct itimerval itv_old;
static struct itimerval itv;
- if (on) setitimer(TIMER_TIME, &itv_old_, NULL);
- else {
+ static int is_off = 0;
+ if (on) {
+ if (is_off--) setitimer(TIMER_TIME, &itv_old, NULL);
+ }
+ else if (!is_off++) {
itv.it_interval.tv_sec = itv.it_interval.tv_usec = 0;
itv.it_value = itv.it_interval;
- setitimer(TIMER_TIME, &itv, itv_old);
- itv_old = NULL;
+ setitimer(TIMER_TIME, &itv, &itv_old);
}
}
> I applied the patch and it worked for me. I am still booting
> from a "boot directory" now.
So this was for problem #1. :-)
> I tried switching back to _vbootfloppy, but still I find that
> BOOTOFF.COM is non-functional. But I can at least write to the
> floppy drive now with the "boot directory" approach. If you are
> having problems with your floppy and happen to be running the
> most recent "stable" version you might consider the patch and use
> some other boot method than _vbootfloppy.
This (problem #2) is actually a known problem. It�s basically the main reason I
developed the boot_dir stuff in the first place for.
At the moment booton/-off simply does not work. I�ll fix this in the near
future (unless someone else does, that is :-) ).
Bye,
Steffen
