> I missed the solution to the problem where floppy access locks dosemu
> v0.98.6, which I desperately need. Could someone please resend this
> information or provide a url to get it?
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
> 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
