Thomas Stewart writes:
>
> hi
>
> >ftp://microwindows.censoft.com/pub/microwindows/microwindows-0.83.tar.gz
> >
> >Greg
> >
>
> Would it be a good idea to put a link to this on the main ELKS web site?
> Greg you must be getting board telling eveyone where it is?
>
Hmm, good idea. Wish I had
Thomas Stewart writes:
>
> hi
> This many be a stupid idea,
>
> As far as I know consoles on linux are seperate, ie each can run diffrent
> proceses independent of each other?
> Is this the same for ELKS? (using the f keys)
>
> In my elks machine I have a vga card and a herc card, how can I us
Ha! ive been trying to get OFF this list for eons and havent had any luck so
far...
Alistair Riddoch <[EMAIL PROTECTED]> on 09/28/99 02:22:00 PM
To: [EMAIL PROTECTED] (Thomas Stewart)
cc: [EMAIL PROTECTED] (bcc: Habib Ahmed/PK/ABNAMRO/NL)
Subject: Re: your mail
> Or is there a bette
: > Or is there a better way to use the two cards together? DOS does not do this
: > very well (appart from a few utills that switch the screen, and a few apps
: > that support it (tcc).)
:
: There is no current support for this in the ELKS code, but it does appeal
: to me. Any idea how it can
On Monday, September 27, 1999 7:40 PM, Michael G Hughes [SMTP:[EMAIL PROTECTED]]
wrote:
: >Currently, the biggest
: >problem with shared libraries on 8086 and bcc is that the compiler can't
: >produce position-independent code (ala -fPIC) so that even the code segment
: >requires data relocations
> : for task switching), can bcc handle that? Or create something like an
> : indirect jump and glue code in the library.
>
> The indirect jump and glue code is exactly what is needed out of bcc.
> currently, it doesn't generate any of that kind of code.
It also cant do that on an 8086 w
On Tuesday, September 28, 1999 11:56 AM, Alan Cox [SMTP:[EMAIL PROTECTED]]
wrote:
: > : for task switching), can bcc handle that? Or create something like an
: > : indirect jump and glue code in the library.
: >
: > The indirect jump and glue code is exactly what is needed out of bcc.
: >
> As I mentioned before, if this were performed with code segments
> only, then they could still be shared with the resulting memory decrease benefit.
But is outweighed by the cost of no swapping or defragmentation
> In fact, with a ridiculous increase in code size, all absolute
> lo
On Tue, 28 Sep 1999, Greg Haerr wrote:
>
> : > Or is there a better way to use the two cards together? DOS does not do this
> : > very well (appart from a few utills that switch the screen, and a few apps
> : > that support it (tcc).)
> :
> : There is no current support for this in the ELK
On Tue, Sep 28, 1999 at 10:22:00AM +0100, Alistair Riddoch wrote:
> Thomas Stewart writes:
> > Or is there a better way to use the two cards together? DOS does not do this
> > very well (appart from a few utills that switch the screen, and a few apps
> > that support it (tcc).)
>
> There is no
On Tuesday, September 28, 1999 12:26 PM, Alan Cox [SMTP:[EMAIL PROTECTED]]
wrote:
: > As I mentioned before, if this were performed with code segments
: > only, then they could still be shared with the resulting memory decrease benefit.
:
: But is outweighed by the cost of no swapping or def
Just thought I'd see if there was anybody here, since I'm brand new to this.
I'm hoping to get ELKS on my Toshiba T1200 notebook (8086-10, 640K ram, dual
720K floppies) and use it as a serial console for all of my nifty serial
devices (hubs, routers, sun boxen, etc.) Anybody tried anything simila
Hi
>Why not just have a /dev/2tty driver set for the new monitor and
>have init asign logins to /dev/tty and /dev/2tty?
>
>Luke(Boo) Farrar.
I thought of making a different set of tty drivers, but how would you do
that? Could you use mknod?
How would you tell init to use them, would it be as s
13 matches
Mail list logo
