[MiNT] CT2b and MiNT1.16 alpha Memory Protect
Martin Tarenskeen
I have noticed that when I boot MiNT 1.16 on my Falcon030/CT2b, Memory
Protect is automatically disabled by default, unless I use left-shift to
select the startup menu and re-enable it (if I want to). With MiNT 1.15.12
I can't enable Memory Protect at all.
If I boot with my CT2b turbo switched off, Memory Protect is enabled
automatically.
I'm sure there is a good reason for this, is there ?
--
Martin Tarenskeen
Frank Naumann
> If I boot with my CT2b turbo switched off, Memory Protect is enabled
> automatically.
>
> I'm sure there is a good reason for this, is there ?
Yes. As far as I know in turbo mode the MMU is marked as used and
therefore MP can't be enabled. Enabling MP is the default behaviour in
1.16.
Tschuess
...Frank
--
ATARI FALCON 040 // MILAN 060
-----------------------------------------
http://www.cs.uni-magdeburg.de/~fnaumann/
e-Mail: fnau...@freemint.de
Martin Tarenskeen
> Hello!
>
> > If I boot with my CT2b turbo switched off, Memory Protect is enabled
> > automatically.
> >
> > I'm sure there is a good reason for this, is there ?
>
> Yes. As far as I know in turbo mode the MMU is marked as used and
> therefore MP can't be enabled. Enabling MP is the default behaviour in
> 1.16.
>
I see.
If I enable Memory Protect by force using the startup menu (left-shift),
am I doing something illegal/dangerous ? It seems to be working though ?
The reason I do this is because until now it is the only way I have
managed to get SPIN working in combination with my Falcon030/CT2b in
Turbomode.
--
Martin Tarenskeen
Sean Kelley
I just installed freemint using the Easymint distribution. I chose
the login install but also put the Xaaes software on the drive.
Can anyone tell me how to enable the launch of Xaaes after
I did the Easymint install?
Thanks,
Sean
Martin Tarenskeen
Simply type on your commandline:
xaaes
And, if everything was installed by easymint, there you go.
How does it work:
Easymint installs a symbolic link from XAAES.TOS to /usr/bin/xaaes.
When typing xaaes, /usr/bin/xaaes will be found in the PATH, and XAAES.TOS
will be started.
If you did not choose the XaAES installation in your EasyMiNT setup you
can make such a symbolic link by yourself, or start XAAES.TOS directly.
In that case type for example the following:
cd /c/xaaes/
./xaaes.tos
--
Martin Tarenskeen
Sean Kelley
I now have xaaes running along with teradesk as my desktop. Are
there any xterm like applications that give me access to the CLI? If
I boot into console I can access the command line utilities, but
now that I'm booting into xaaes+teradesk, I was wondering if there
exists an xterm like app?
Sean
Martin Tarenskeen
TosWin2 is part of the EasyMiNT distribution. It should be in
/opt/toswin2/ where you will find toswin2.prg and tw-call.prg. But due to
an error in the rpm package (when will this be fixed ?) , you'll have to
make these files executable first:
cd /opt/toswin2
chmod 755 toswin2.prg (or was it toswin2.app ?)
chmod 755 tw-call.prg
After that you'll be able to start it on your desktop by clicking on
U:\opt\toswin2\toswin2.prg. A better idea might be to let it start
automatically from the xa_exec.scl file.
Some programs, like the excellent mail/newsreader pine, will run happily
in TosWin2, but not on the login screen. Others ,like the lynx browser,
can run without GEM, but will look much better in a TosWin2 window.
Martin Tarenskeen
Sean Kelley
As it turns out, the permissions are correct with the latest
Easymint distribution. I was able to directly launch a Bash shell
and compile and execute a simple C hello world application.
Once I went to the directory you suggested, I could launch it
directly.
This is great, I now have functional Easymint distribution.
Thanks for the help!
Sean
Konrad Kokoszkiewicz
> happily in TosWin2, but not on the login screen. Others ,like the
> lynx browser, can run without GEM, but will look much better in a
> TosWin2 window.
If I understand the problem correctly: pine will work too, but the
environment variable TERM must be set correctly by rc scripts (or mint.cnf).
`export TERM=st52' somewhere in the rc scripts or `setenv TERM st52' in
mint.cnf should do for the console, provided there is /etc/termcap file with
the st52 terminal definition.
CVV
--
Konrad M.Kokoszkiewicz
http://draco.atari.org
** Ea natura multitudinis est,
** aut seruit humiliter, aut superbe dominatur (Liv. XXIV,25)
*************************************************************
** Taka to juz natura pospólstwa, albo sluzalczo sie plaszczy,
** albo bezczelnie sie panoszy.
Martin Tarenskeen
> > Some programs, like the excellent mail/newsreader pine, will run
> environment variable TERM must be set correctly by rc scripts (or mint.cnf).
> `export TERM=st52' somewhere in the rc scripts or `setenv TERM st52' in
> mint.cnf should do for the console, provided there is /etc/termcap file with
> the st52 terminal definition.
>
That's great! It works, but something strange is happening on my system.
I have to set `export TERM=st52' by hand everytime after that I have
logged in. Even if I have set this variable in mint.cnf or in one of the
rc scripts, if I log in and type
echo $TERM
I'm still getting "vt52" as an answer. I can't find which file or script
is responsible for that. Anyone ?
Martin Tarenskeen
Adam Klobukowski
> system. I have to set `export TERM=st52' by hand everytime after
> that I have logged in. Even if I have set this variable in mint.cnf
> or in one of the rc scripts, if I log in and type
> echo $TERM
> I'm still getting "vt52" as an answer. I can't find which file or
> script is responsible for that. Anyone ?
You mean for vconsoles or Toswin?
Toswin sets it dor its windowy by his own. I do not know what
vconsoles do, but I set TERM in .bashrs like this:
if [ -n "$LOGIN_SHELL" ]; then
export TERM=stv52
fi
--
Semper Fidelis
Adam Klobukowski
at...@gabo.pl
Maurits van de Kamp
> Toswin sets it dor its windowy by his own. I do not know what
> vconsoles do, but I set TERM in .bashrs like this:
>
> if [ -n "$LOGIN_SHELL" ]; then
> export TERM=stv52
> fi
KGMD has a bit of scripting that checks whether the login is occurring on
a vconsole or the main console, and sets TERM to st52 or stv52.
But since my last KGMD installation was trashed, I don't have it at hand.
:)
Maurits.
Martin Tarenskeen
>
> Hi,
>
> What do you use as a login shell? If you use bash or csh you have to edit
> the .bash_profile or corresponding file for csh in your home directory.
> There is also an /etc/profile you could look at.
I have now set
export TERM=st52
in /etc/profile and this works. Thank you for your help. Maybe this is
something that should be added to the base rpm package ?
--
Martin Tarenskeen
Martin Tarenskeen
> I have now set
>
> export TERM=st52
>
> in /etc/profile and this works. Thank you for your help.
I have removed that line again, because I have found a better solution.
The problem with my TERM settings was somewhere else. I had to edit a line
in /etc/ttytab:
console "/usr/sbin/getty console" st52 on secure
In the original easymint distribution there was "vt52" instead of "st52",
which was why pine (among others) wouldn't work on my login screen. Now,
when I start XaAES, I still have TERM=tw52 in my TosWin2 window. And
without GEM, on my login screen, TERM=st52 is automatically set.
After that I went on and have now succeeded to get vconsoles installed and
running. For these (ttyv1..ttyv9) I have chosen stv52 as TERM type. I
tried stv52c, but got messages that this term type doesn't exist ? Unless
someone can tell me what I'm doing wrong, I'll do some more studying to
get color on my console screen(s). But in mono it's working great.
Besides having 10 virtual full screen console screens - which is cool
already - there is another small but nice side effect: The vconsoles don't
suffer from the bug, caused by NVDI, that the cursor is invisible before
XaAES/N_AES is started. Did you know that ?
--
Martin Tarenskeen
Falcon030/CT2b, MiNT 1.16a, XaAES 0.962, vconsoles 0.9b, etcetera.