When I did so, all I get during boot is "Launching init: gem ... error -33" and I get MiS, the FreeMiNT internal shell

What to do to start it?
Moderators: Mug UK, moondog/.tSCc., lp, [ProToS], Moderator Team
BlankVector wrote:I love GEM=ROM, unfortunately there is a big drawback... The keyboard does not work anymore
mikro wrote:Damn it, this is ridiculous. Forcing user to install a dumb acc which can be easily simulated within the kernel. The saddest part of this is the fact that the ACC is not even a part of the freemint source tree, not even as a binary.
BlankVector wrote:I love GEM=ROM, unfortunately there is a big drawback... The keyboard does not work anymore
jury wrote:What do you mean "keyboard does not work anymore" ?
Code: Select all
/*
no_hog2.acc
Very simple accessory that just calls Syield every
20ms.
Purpose: Use it when using the ROM AES with MiNT to
allow multitasking (and keyboard) to work.
Jo Even Skarstein, 2017
*/
#include <tos.h>
#include <mint.h>
#include <aes.h>
void main(void)
{
short exit = false;
EVENT event = { MU_TIMER|MU_MESAG, // Types
0, 0, 0, // Button
0, 0, 0, 0, 0, // m1
0, 0, 0, 0, 0, // m2
20, 0, // Timer
0, 0, 0, 0, 0, 0, 0,
{0, 0, 0, 0, 0, 0, 0, 0}
};
short apid = appl_init();
menu_register(apid, " NoHog2");
while (!exit)
{
unsigned short e = EvntMulti(&event);
if (e & MU_MESAG)
{
switch (event.mgpbuf[0])
{
case AC_OPEN:
form_alert(0, "[1][ NoHog2 ][ Ok ]");
break;
case AC_CLOSE:
break;
case AP_TERM:
exit = true;
break;
default:
break;
}
}
if (e & MU_TIMER)
{
Syield();
}
}
appl_exit();
}
mikro wrote:We could include this into the "tools" directory, where it had once resided.
helmut wrote:Just in case you didn't know: Keyboard works with GEM=ROM in my kernel since ages.
joska wrote:Here's a quick workaround. Run this accessory and the keyboard works fine. I could not get GEM=ROM to work on my Milan, but I tested this on my Mega and it worked fine.
joska wrote:Well, this was just a quick hack. It doesn't even check if MiNT is running so it might cause problems if started under TOS. But if there is a need for it I could fix it up.
helmut wrote:Just in case you didn't know: Keyboard works with GEM=ROM in my kernel since ages.
helmut wrote:Just in case you didn't know: Keyboard works with GEM=ROM in my kernel since ages.
BlankVector wrote:And I don't mention the fact that a BIOS feature (low-level keyboard handling) relies on an upper layer feature (MiNT's GEMDOS multitasking) is a complete nonsense.
mikro wrote:Why have you never provided a patch? What purpose it has to stay in your branch, to amuse yourself?
mikro wrote:Ideally, the ACC could check if the AES is the ROM one and if not, then exit else provide the yield functionality. This would be pretty awesome.
BlankVector wrote:I made quick test long ago (probably the same as Helmut fix): instead of delaying the keystroke, handle it immediately, like TOS. Then keyboard works like a charm with GEM=ROM. What needs to be proven is if there are really stack issues as I suspect.
helmut wrote:Any process called GEM runs in single-task-mode (that would also affect N.AES, probably myAES, etc.).
Users browsing this forum: Bing [Bot] and 6 guests