Jim, Thank you for trying this... and also for sharing your article on running FreeDOS on QEMU under Linux; I had missed that one.
Your report that everything was working fine in Fedora 29 got me curious, so I downloaded a Live CD of the same and tried it. Sure enough, no problems. To summarize my findings, I tried calling QEMU from a variety of systems utilizing the same disk images and command line call as quoted in my original message; and CD access in FreeDOS is either okay or fails as follows: QEMU 2.12.0 on MacOS 10.13.6 --> ok QEMU 3.0.0 on MacOS 10.13.6 --> FAIL QEMU 3.0.0 on Windows 10 --> FAIL QEMU 3.0.0 on Fedora 29 --> ok I think it's time for a bug report to the QEMU folks. Hopefully this will save some headaches for new FreeDOS users following this pathway on the affected OS's. John Date: Sat, 10 Nov 2018 17:09:17 -0600 > From: Jim Hall <jh...@freedos.org> > > I'm running QEMU 3.0.0 on Fedora 29. Works fine over here. > > This is the command line I use to launch QEMU: > > qemu-system-i386 -m 32 -k en-us -rtc base=localtime -soundhw > sb16,adlib,pcspk -device cirrus-vga -display gtk -hda > /home/jhall/lib/qemu/drive_c.img -cdrom > /home/jhall/lib/qemu/FD12CD.iso -drive file=fat:rw:/home/jhall/dos > -boot order=c > > > I can run FDIMPLES from that, even though my FD12CD.iso is recognized > as the E: drive, instead of D: (my D: drive is my /home/jhall/dos > folder). > > I wrote an article about running FreeDOS under Linux using QEMU. I > know you're running MacOS, but the QEMU command line should transfer > just the same. > https://opensource.com/article/17/10/run-dos-applications-linux > > Jim > On Wed, Nov 7, 2018 at 12:48 PM John Haynes <johnh...@gmail.com> wrote: > > > > Hello all, > > > > I'm wondering if anyone who uses FreeDOS on QEMU would be interested > willing to help me track down a new issue I'm seeing. (I run QEMU on MacOS > 10.13.6, which may or may not matter...) > > > > Here's a demo of the problem. Suppose I want to use FDIMPLES to install > some software, and I start FreeDOS with this command: > > > > > qemu-system-i386 -rtc base=localtime -soundhw pcspk -drive > format=raw,file=freedos.img -cdrom FD12CD.iso > > > > where freedos.img is an image containing a working FreeDOS installation, > and FD12CD.iso is of course the installation CD image. > > > > With QEMU version 2.12.0, this works fine... for example, once FreeDOS > loads, I can do a DIR D: to see the files on the CD, and start FDIMPLES to > install the packages I want. > > > > In the recent QEMU 3.0.0 release, however, the same qemu startup command > no longer results in the CD being loaded in FreeDOS. For example, once > inside FreeDOS: > > C:> DIR D: > > Volume in drive D Error reading from drive D: data area: drive not ready > > (A)bort, (R)etry, (F)ail? > > > > My first question is: can anyone else reproduce this? If so, then I'd > appreciate any ideas on how to go about tackling it (besides reverting to > QEMU 2.12.0, which incidentally is exactly what I'm doing... but if there > is an fact a bug at play here, hopefully we can at the least report it, and > maybe even make some headway on eliminating it). > > > > Thanks much, > > John > > > > --- > > > > Some additional info: > > I just noticed that during the FreeDOS boot sequence (with either > version of QEMU... even the working one...), the autoexec.bat: > > DEVLOAD /H /Q %dosdir%\BIN\UDVD2.SYS /D:FDCD0001 > > > > results in this: > > UDVD2, 4-30-3013. CD/DVD name is FDCD0001. > > BAD Controller at I-O address C040h, Chip I.D. 80867010h. > > CD0; IDE0 Secondary-master, QEMU DVD-ROM, PIO. >
_______________________________________________ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
