Both my cdrw and cdrom are up and readable now. I think that's ok, as I can't see any way I'd be burning under dosemu instead of linux. Here's what I did for anybody who needs it:
dosemu.conf: $_cdrom = "/dev/cdrom" $_cdrom2 = "/dev/cdrecord" config.emu (config.sys): devicehigh=c:\cdrom.sys devicehigh=c:\cdrom.sys 2 autoexec.emb (autoexec.bat): MSCDEX /D:MSCD0001 /D:MSCD0002 /L:E Also had to check the permissions on scd0 and scd1 (since i'm using scsi emulation in linux) to make sure an ordinary user had access. The second one refused to load and when I ran with debugging I found that the complaint was that there was no /dev/cdrom2, so I created a link from /dev/scd0 (which is already linked to /dev/cdrecord) to /dev/cdrom2. Now both the cdrom and the cdrw are recognized (as e: and f:) and can be used. I can't get the second drive to eject though with eject.com; still working on that. I didn't use any aspi. In actuality, my cdrw is scd0 and my cdrom is scd1 while the order is reversed in dOS the way I've set it up; this could be reversed if I really wanted to, but I don't see any problem with things as they are. For just one cdrom, the entries in your config.emu and autoexec.emb should be enough. If your cdrom doesn't come up then, I'd suggest running with debugging; I found out a lot that way. - To unsubscribe from this list: send the line "unsubscribe linux-msdos" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
