Activity log for bug #52857

Date Who What changed Old value New value Message
2006-07-16 13:58:20 Jeff Buchbinder dosemu: status Unconfirmed Confirmed
2006-07-16 13:58:20 Jeff Buchbinder dosemu: statusexplanation Also gives error: ERROR: Unable to open console to evaluate the keyboard map. Please specify your keyboard map explicitly via the $_layout option This is still present in Dapper (6.06).
2006-08-03 06:53:09 Mantas Kriaučiūnas bug assigned to Baltix
2006-08-03 15:55:46 Mantas Kriaučiūnas bug added subscriber Mykolas OK
2006-08-03 15:59:33 Mantas Kriaučiūnas None: status Unconfirmed Confirmed
2006-08-03 15:59:33 Mantas Kriaučiūnas None: importance Untriaged Medium
2006-08-03 15:59:33 Mantas Kriaučiūnas None: statusexplanation It seems bug is in dosemu-freedos package, not in dosemu - when I installed dosemu-freedos version 1:0.0.b9r5a-3 (from Debian testing) then this problem dissapears :) AFAIK in mailing list, that you told us before (http://www.gatago.com/linux/kernel/14721949.html ) also is mentioned, that problem is in command.com from older freedos versions.
2006-08-03 15:59:33 Mantas Kriaučiūnas None: assignee mantas
2006-08-03 19:54:55 Adrian R Goalby dosemu: statusexplanation Also gives error: ERROR: Unable to open console to evaluate the keyboard map. Please specify your keyboard map explicitly via the $_layout option This is still present in Dapper (6.06).
2008-11-26 21:54:13 Adam Buchbinder dosemu-freedos: status Confirmed Incomplete
2008-11-26 21:54:13 Adam Buchbinder dosemu-freedos: statusexplanation dosemu seems to work on Intrepid; the dosemu-freedos has been rolled into it, and it pops up a DOS prompt without issue so far as I can tell if I execute "dosemu". (dosemu 1.4.0+svn.1828-2ubuntu1, kernel 2.6.27-7-generic.) What exactly are you doing on Hardy to trigger the problem? Is anyone still getting the "ERROR: cpu exception in dosemu code outside of VM86()!" error?
2009-01-02 16:34:45 Adam Buchbinder None: status Confirmed Incomplete
2009-01-02 16:34:45 Adam Buchbinder None: statusexplanation It seems bug is in dosemu-freedos package, not in dosemu - when I installed dosemu-freedos version 1:0.0.b9r5a-3 (from Debian testing) then this problem dissapears :) AFAIK in mailing list, that you told us before (http://www.gatago.com/linux/kernel/14721949.html ) also is mentioned, that problem is in command.com from older freedos versions. Is there still a reason for a Baltix task to be open on this bug?
2009-05-04 20:15:32 levien bug watch added http://sourceforge.net/support/tracker.php?aid=2760088
2009-05-04 20:18:44 levien bug task added dosemu
2010-09-16 11:17:44 Matthias Mailänder dosemu: importance Unknown Undecided
2010-09-16 11:17:44 Matthias Mailänder dosemu: status Unknown New
2010-09-16 11:17:44 Matthias Mailänder dosemu: remote watch SourceForge.net Tracker #2760088
2010-09-16 11:18:05 Matthias Mailänder removed subscriber Matthias Mailänder
2010-09-16 11:18:24 Matthias Mailänder dosemu: status New Fix Released
2010-09-16 11:18:40 Matthias Mailänder dosemu-freedos (Ubuntu): status Incomplete Fix Released
2010-09-16 11:53:34 Stéphane Marguet removed subscriber Stéphane Marguet
2012-02-14 07:45:30 Kai Kasurinen removed subscriber Kai Kasurinen