RE: Full screen capable?

Subject: RE: Full screen capable?
From: Al Koller (al.koller@spacecoastnet.com)
Date: Tue Jun 26 2001 - 23:10:45 MDT

Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Next message: Quentin Mason: "Re: Full screen capable?"
Previous message: Derrik Pates: "Re: Current MoL rsync does not build against benh's 2.4.6-pre3"
In reply to: Callahan, Tom: "RE: Full screen capable?"
Reply: Al Koller: "RE: Full screen capable?"

Thanks Tom. More memory is on its way; once it arrives, I will allocate
more RAM as you've suggested. I have another question:

Do you know whether there exist Front Page Extensions for Linux on the MAC?
The only ones I can find are for Intel chips, which means my Apache running
on MOL will not support my web pages... Bummer! Thanks.

Al Koller

-----Original Message-----
From: Callahan, Tom [mailto:TCallahan@DeepBridge.Com]
Sent: Monday, June 25, 2001 2:48 PM
To: 'mol-general@lists.maconlinux.org'
Subject: RE: Full screen capable?

Did you know that you can allocate more RAM in the molrc config file? Open
the molrc file with a text editor and scroll to the ram section to increase
the amount of RAM. This might help, having more RAM never hurts.

Tom
-----Original Message-----
From: Al Koller [mailto:al.koller@spacecoastnet.com]
Sent: Saturday, June 23, 2001 12:29 PM
To: mol-general@lists.maconlinux.org
Subject: Full screen capable?

Hi everyone. I am new to linux and am using Yellow Dog version 2.0. I have
it installed on a 350 iMac and running fine, along with MOL. I've already
sent for more RAM because I cannot get MOL to run without hanging and think
there simply is not enough memory available (I have 128Megs). Also, I
cannot get a full screen display and wondered in anyone can advise how to do
that using KDE as the graphical interface???

Thanks.

Al Koller

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML xmlns="http://www.w3.org/TR/REC-html40" xmlns:o =
"urn:schemas-microsoft-com:office:office" xmlns:w =
"urn:schemas-microsoft-com:office:word"><HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=windows-1252">

<META content=Word.Document name=ProgId>
<META content="MSHTML 5.00.3103.1000" name=GENERATOR>
<META content="Microsoft Word 9" name=Originator><LINK
href="cid:filelist.xml@01C0FBE0.04F9CDE0" rel=File-List>
<STYLE>P.MsoNormal {
COLOR: black; FONT-FAMILY: Arial; FONT-SIZE: 10pt; MARGIN: 0in 0in 0pt;
mso-bidi-font-size: 18.0pt; mso-style-parent: ""; mso-pagination:
widow-orphan; mso-fareast-font-family: "Times New Roman";
mso-bidi-font-family: "Times New Roman"; mso-bidi-font-weight: bold
}
LI.MsoNormal {
COLOR: black; FONT-FAMILY: Arial; FONT-SIZE: 10pt; MARGIN: 0in 0in 0pt;
mso-bidi-font-size: 18.0pt; mso-style-parent: ""; mso-pagination:
widow-orphan; mso-fareast-font-family: "Times New Roman";
mso-bidi-font-family: "Times New Roman"; mso-bidi-font-weight: bold
}
DIV.MsoNormal {
COLOR: black; FONT-FAMILY: Arial; FONT-SIZE: 10pt; MARGIN: 0in 0in 0pt;
mso-bidi-font-size: 18.0pt; mso-style-parent: ""; mso-pagination:
widow-orphan; mso-fareast-font-family: "Times New Roman";
mso-bidi-font-family: "Times New Roman"; mso-bidi-font-weight: bold
}
P.MsoAutoSig {
COLOR: black; FONT-FAMILY: Arial; FONT-SIZE: 10pt; MARGIN: 0in 0in 0pt;
mso-bidi-font-size: 18.0pt; mso-pagination: widow-orphan;
mso-fareast-font-family: "Times New Roman"; mso-bidi-font-family: "Times New
Roman"; mso-bidi-font-weight: bold
}
LI.MsoAutoSig {
COLOR: black; FONT-FAMILY: Arial; FONT-SIZE: 10pt; MARGIN: 0in 0in 0pt;
mso-bidi-font-size: 18.0pt; mso-pagination: widow-orphan;
mso-fareast-font-family: "Times New Roman"; mso-bidi-font-family: "Times New
Roman"; mso-bidi-font-weight: bold
}
DIV.MsoAutoSig {
COLOR: black; FONT-FAMILY: Arial; FONT-SIZE: 10pt; MARGIN: 0in 0in 0pt;
mso-bidi-font-size: 18.0pt; mso-pagination: widow-orphan;
mso-fareast-font-family: "Times New Roman"; mso-bidi-font-family: "Times New
Roman"; mso-bidi-font-weight: bold
}
SPAN.EmailStyle15 {
COLOR: black; mso-bidi-font-family: Arial; mso-style-type:
personal-compose; mso-ansi-font-size: 10.0pt; mso-ascii-font-family: Arial;
mso-hansi-font-family: Arial
}
DIV.Section1 {
page: Section1
}
</STYLE>
</HEAD>
<BODY lang=EN-US style="tab-interval: .5in">
<DIV>Did
you know that you can allocate more RAM in the molrc config file? Open the
molrc
file with a text editor and scroll to the ram section to increase the amount
of
RAM. This might help, having more RAM never hurts.</DIV>
<DIV> </DIV>
<DIV>Tom</DIV>
<BLOCKQUOTE style="MARGIN-RIGHT: 0px">
 <DIV align=left class=OutlookMessageHeader dir=ltr>-----Original Message----- From: Al Koller
 [mailto:al.koller@spacecoastnet.com] Sent: Saturday, June 23,
2001
 12:29 PM To: mol-general@lists.maconlinux.org Subject:
 Full screen capable? </DIV>
 <DIV class=Section1>
 Hi everyone.  I am new to linux and am using
Yellow
 Dog version 2.0.  I have it
 installed on a 350 iMac and running fine, along with MOL.  I've already sent for more RAM
because
 I cannot get MOL to run without hanging and think there simply is not
enough
 memory available (I have 128Megs). 
 Also, I cannot get a full screen display and wondered in anyone can
 advise how to do that using KDE as the graphical
 interface???<o:p></o:p>
 <![if
!supportEmptyParas]> <![endif]><o:p></o:p>
 Thanks.<o:p></o:p>
 <![if
!supportEmptyParas]> <![endif]><o:p></o:p>
 Al

Koller<o:p></o:p></DIV></BLOCKQUOTE></BODY><
/HTML>

Next message: Quentin Mason: "Re: Full screen capable?"
Previous message: Derrik Pates: "Re: Current MoL rsync does not build against benh's 2.4.6-pre3"
In reply to: Callahan, Tom: "RE: Full screen capable?"
Reply: Al Koller: "RE: Full screen capable?"

This archive was generated by hypermail 2a24 : Tue Jun 26 2001 - 22:29:03 MDT