Bug 3112 - dosemu hangs accessing drive "A:"
dosemu hangs accessing drive "A:"
Status: CLOSED RAWHIDE
Product: Red Hat Linux
Classification: Retired
Component: dosemu (Show other bugs)
6.0
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Bernhard Rosenkraenzer
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 1999-05-28 06:49 EDT by paolo.saggese
Modified: 2008-05-01 11:37 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2000-02-09 07:33:05 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description paolo.saggese 1999-05-28 06:49:13 EDT
Hi everybody,

	if I try to access drive A: (floppy disk drive, configured
as "treeinch" in /etc/dosemu.conf) from within dosemu, the
floppy drive LED lights up and it seems to start reading,
too, but immediately after the light goes off and dosemu
hangs.

No problems (apparently) if there is no disk in the drive:
the usual "drive not ready" message does appear. But that's
not so much useful indeed! 8-)

As a workaround, I have currently disabled dosemu internal
floppy support ($_floppy_a ="") and am accessing the floppy
disks trough LREDIR + Linux automounter (autofs).

Unfortunately, there's no way to boot dosemu from a floppy.

FYI: I'm using the same (custom built) hdimage with Caldera
Open/DR-DOS 7.2 that I was using (without any problem) with
previous versions (RH 5.2, etc), but I have tried also with
RH 6.0 supplied hdimage.freedos with the same results.


Ciao,
			Paolo.
Comment 1 Patrick W. Binning 2000-01-20 14:37:59 EST
I had this same problem with RH6.0. I then got the new binaries for dosemu,
freedos, and xdosemu for RH6.1 and the problem not longer existed for me.
Comment 2 Bernhard Rosenkraenzer 2000-02-09 07:33:59 EST
0.99.13-6 (Rawhide powertools) should definitely fix this (new freedos version).

Note You need to log in before you can comment on or make changes to this bug.