286 xterm?

286 xterm?

[Bardelli Luigi]

Dear all,

     I'm totally new to the world of 286 & Linux, and I would like to ask
you something:
it is possible to use a 286 machine as a normal X-term?
I'd like to use it together with a "normal" linux-box: every application
will run one the 
remote machine.

Thank you
      Luigi

PS: Beg pardon if it is not the right place to post...

Re: 286 xterm?

[Stefan de Konink]

Yeah it is possible to make a 286 a terminal, pretty easy with telnet and
a slip connection.

Have Fun here :)


Greetings,

Stefan de Konink

On Sun, 25 Aug 2002, Bardelli Luigi wrote:

> Dear all,
>
>      I'm totally new to the world of 286 & Linux, and I would like to ask
> you something:
> it is possible to use a 286 machine as a normal X-term?
> I'd like to use it together with a "normal" linux-box: every application
> will run one the
> remote machine.
>
> Thank you
>       Luigi
>
> PS: Beg pardon if it is not the right place to post...
>
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-8086" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>

Re: 286 xterm?

[Riley Williams]

Hi Stefan, Luigi.

>> it is possible to use a 286 machine as a normal X-term? I'd like
>> to use it together with a "normal" linux-box: every application
>> will run one the remote machine.

> Yeah it is possible to make a 286 a terminal, pretty easy with
> telnet and a slip connection.

Stefan: whilst it's easy to use a 286 as a TEXT terminal (implied by
"telnet" in your comment), I'm not so sure regarding using it as an
XTERM as Luigi asked.

If you can clarify that, it'd be appreciated here as well.

Best wishes from Riley.

Re: 286 xterm?

[Stefan de Konink]

If Luigi wants to run X on his 286... are there any plans for XFree8086?
;)

On Sun, 25 Aug 2002, Riley Williams wrote:

> Hi Stefan, Luigi.
>
> >> it is possible to use a 286 machine as a normal X-term? I'd like
> >> to use it together with a "normal" linux-box: every application
> >> will run one the remote machine.
>
> > Yeah it is possible to make a 286 a terminal, pretty easy with
> > telnet and a slip connection.
>
> Stefan: whilst it's easy to use a 286 as a TEXT terminal (implied by
> "telnet" in your comment), I'm not so sure regarding using it as an
> XTERM as Luigi asked.
>
> If you can clarify that, it'd be appreciated here as well.
>
> Best wishes from Riley.
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-8086" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>

Re: 286 xterm?

[Dan Olson]

This is a little late, so maybe someone already commented, but a text
terminal and an Xterm are two different things.  There is supposedly a
program, DesqView-X that allows a 286 to be used as an Xterm, but I've
never found it.  I finally gave up and just started using a 386 running
Linux with a minimal amount of packages installed.  I can just boot Linux,
run X, and then redirect my display to that machine over the ethernet.
Maybe someone else has some ideas on the Xterm question, there was some
work on a GUI for ELKS but I don't think it's to the point of doing what
you want.

	Dan


On Sun, 25 Aug 2002, Stefan de Konink wrote:

> Yeah it is possible to make a 286 a terminal, pretty easy with telnet and
> a slip connection.
>
> Have Fun here :)
>
>
> Greetings,
>
> Stefan de Konink
>
> On Sun, 25 Aug 2002, Bardelli Luigi wrote:
>
> > Dear all,
> >
> >      I'm totally new to the world of 286 & Linux, and I would like to ask
> > you something:
> > it is possible to use a 286 machine as a normal X-term?
> > I'd like to use it together with a "normal" linux-box: every application
> > will run one the
> > remote machine.
> >
> > Thank you
> >       Luigi
> >
> > PS: Beg pardon if it is not the right place to post...
> >
> >
> > -
> > To unsubscribe from this list: send the line "unsubscribe linux-8086" in
> > the body of a message to majordomo@vger.kernel.org
> > More majordomo info at  http://vger.kernel.org/majordomo-info.html
> >
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-8086" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>

Re: 286 xterm?

[Luigi Bardelli]

Dear all,
	thank you for your replies. Dan, i'd like to do it with a *2*86, not
a 386...
Any new suggestion?
Thanks
	Luigi

-------------------
> This is a little late, so maybe someone already commented, but a
text
> terminal and an Xterm are two different things.  There is supposedly
a
> program, DesqView-X that allows a 286 to be used as an Xterm, but
I've
> never found it.  I finally gave up and just started using a 386
running
> Linux with a minimal amount of packages installed.  I can just boot
Linux,
> run X, and then redirect my display to that machine over the
ethernet.
> Maybe someone else has some ideas on the Xterm question, there was
some
> work on a GUI for ELKS but I don't think it's to the point of doing
what
> you want.
> 
> 	Dan

Re: 286 xterm?

[Rob Helmer]

Hello,


You can't currently do this on a 286 with Linux, although there are some X
servers for DOS available.

I used "X Appeal" for DOS a long time ago, it may run under 
FreeDOS also -

http://www.xtreme.it/xappeal.html

"X Appeal" is based on XFree86, but it is proprietary software. There
is a trial version available.



HTH,
Rob Helmer


On Sun, Sep 01, 2002 at 12:48:58PM +0300, Luigi Bardelli wrote:
> Dear all,
> 	thank you for your replies. Dan, i'd like to do it with a *2*86, not
> a 386...
> Any new suggestion?
> Thanks
> 	Luigi
> 
> -------------------
> > This is a little late, so maybe someone already commented, but a
> text
> > terminal and an Xterm are two different things.  There is supposedly
> a
> > program, DesqView-X that allows a 286 to be used as an Xterm, but
> I've
> > never found it.  I finally gave up and just started using a 386
> running
> > Linux with a minimal amount of packages installed.  I can just boot
> Linux,
> > run X, and then redirect my display to that machine over the
> ethernet.
> > Maybe someone else has some ideas on the Xterm question, there was
> some
> > work on a GUI for ELKS but I don't think it's to the point of doing
> what
> > you want.
> > 
> > 	Dan
> -
> To unsubscribe from this list: send the line "unsubscribe linux-8086" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 

Re: 286 xterm?

[Stefan de Konink]

http://www.google.nl/search?q=cache:-_HbJwRoGhMC:www.ait.iastate.edu/olc/services/xwindows/X.PC.txt.html+286+x+appeal+for+dos&hl=nl&ie=UTF-8

see above list... its in googles cache

On Sun, 1 Sep 2002, Rob Helmer wrote:

> Hello,
>
>
> You can't currently do this on a 286 with Linux, although there are some X
> servers for DOS available.
>
> I used "X Appeal" for DOS a long time ago, it may run under
> FreeDOS also -
>
> http://www.xtreme.it/xappeal.html
>
> "X Appeal" is based on XFree86, but it is proprietary software. There
> is a trial version available.
>
>
>
> HTH,
> Rob Helmer
>
>
> On Sun, Sep 01, 2002 at 12:48:58PM +0300, Luigi Bardelli wrote:
> > Dear all,
> > 	thank you for your replies. Dan, i'd like to do it with a *2*86, not
> > a 386...
> > Any new suggestion?
> > Thanks
> > 	Luigi
> >
> > -------------------
> > > This is a little late, so maybe someone already commented, but a
> > text
> > > terminal and an Xterm are two different things.  There is supposedly
> > a
> > > program, DesqView-X that allows a 286 to be used as an Xterm, but
> > I've
> > > never found it.  I finally gave up and just started using a 386
> > running
> > > Linux with a minimal amount of packages installed.  I can just boot
> > Linux,
> > > run X, and then redirect my display to that machine over the
> > ethernet.
> > > Maybe someone else has some ideas on the Xterm question, there was
> > some
> > > work on a GUI for ELKS but I don't think it's to the point of doing
> > what
> > > you want.
> > >
> > > 	Dan
> > -
> > To unsubscribe from this list: send the line "unsubscribe linux-8086" in
> > the body of a message to majordomo@vger.kernel.org
> > More majordomo info at  http://vger.kernel.org/majordomo-info.html
> >
> -
> To unsubscribe from this list: send the line "unsubscribe linux-8086" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>

Re: 286 xterm?

[Paul Nasrat]

On Sat, Aug 31, 2002 at 11:28:24PM -0700, Dan Olson wrote:

> Maybe someone else has some ideas on the Xterm question, there was some
> work on a GUI for ELKS but I don't think it's to the point of doing what
> you want.

For those who don't know this already - Dan is talking about

http://www.microwindows.org/

However I'm unsure of it's current state with elks.

Paul

Re: 286 xterm?

[Feher Tamas]

>This is a little late, so maybe someone already commented, but a text
>terminal and an Xterm are two different things.  There is supposedly a
>program, DesqView-X that allows a 286 to be used as an Xterm, but I've
>never found it.

www.chsoft.com/dv.html
version 2.0 and 2.1 available for download

Sincerely: Tamas feher.

Re: 286 xterm?

[Gavin]

Sorry Tamas.... This time to the list. 

Can you also confirm the desqview-x will actually make an x-term, and if so is 
there any info/howtos on this ??? 

As I have a ibmps1 here that wont boot into elks, an x-term alternative would 
be worth looking into.  ( I am presenting a demo on x-terms at the local lug 
soon and a few "unique demos will be good" an elks telnet via slip will be 
running too :-)


On Monday 02 September 2002 9:44 pm, Feher Tamas wrote:
> >This is a little late, so maybe someone already commented, but a text
> >terminal and an Xterm are two different things.  There is supposedly a
> >program, DesqView-X that allows a 286 to be used as an Xterm, but I've
> >never found it.
>
> www.chsoft.com/dv.html
> version 2.0 and 2.1 available for download
>
> Sincerely: Tamas feher.
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-8086" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: 286 xterm?

[Gregg C Levine]

Hello from Gregg C Levine
Basically, and as I remember discussing the issue with a representative from
Quaterdeck, Desqview/X is, or was, a compilation of X, that ran with the
standard Desqview windows managing system. It supplied certain functions,
and I believe an xterm was part of the collection, but that wasn't
discussed. I have stored someplace, two versions of Desqview/X, but
according to the notes, it is aimed for the 386, and better market. There
was a version that did run on AT class machines, but I don't have that
version, that'd be all of the earlier versions.
Gregg C Levine obiwanthejediknight@att.net
<This signature will be replaced, pending an approval from the Jedi Council.
>
----- Original Message -----
From: "Gavin" <redhat@ihug.co.nz>
To: "Linux-8086 - ELKS" <Linux-8086@vger.kernel.org>
Sent: Monday, September 02, 2002 7:31 PM
Subject: Re: 286 xterm?


> Sorry Tamas.... This time to the list.
>
> Can you also confirm the desqview-x will actually make an x-term, and if
so is
> there any info/howtos on this ???
>
> As I have a ibmps1 here that wont boot into elks, an x-term alternative
would
> be worth looking into.  ( I am presenting a demo on x-terms at the local
lug
> soon and a few "unique demos will be good" an elks telnet via slip will be
> running too :-)
>
>
> On Monday 02 September 2002 9:44 pm, Feher Tamas wrote:
> > >This is a little late, so maybe someone already commented, but a text
> > >terminal and an Xterm are two different things.  There is supposedly a
> > >program, DesqView-X that allows a 286 to be used as an Xterm, but I've
> > >never found it.
> >
> > www.chsoft.com/dv.html
> > version 2.0 and 2.1 available for download
> >
> > Sincerely: Tamas feher.
> >
> > -
> > To unsubscribe from this list: send the line "unsubscribe linux-8086" in
> > the body of a message to majordomo@vger.kernel.org
> > More majordomo info at  http://vger.kernel.org/majordomo-info.html
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-8086" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>

Re: 286 xterm?

[Feher Tamas]

Hello,

>Can you also confirm the desqviewx will actually make an
>x-term, and if so is  there any info/howtos on this ???

I don't know anything about these software, just found the files with Google.

BTW, the BBC reports the red chinese govt has just banned Google access. Maybe
G. W. Bush should first nuke the engine that spins the Axis of Evil, before
moving onto Saddam?

>I'd love to hear about that too; there are absolutely no docs on how to
>make Desqview/X run with TCP/IP capabilities in Desqview/X (v2.1, the
>latest) package. It did recognize IPX (if proper drivers were installed)
>but that's not it.

Install v2.0 first, then upgrade to v2.1. Visit the webpage I provided for more
info:
www.chsoft.com/dv.html

Sincerely: Tamas Feher.

Re: 286 xterm?

[Blaz Antonic]

This is getting slightly off-topic but anyway ... 

> Can you also confirm the desqview-x will actually make an x-term, and if so is
> there any info/howtos on this ???

I'd love to hear about that too; there are absolutely no docs on how to
make Desqview/X run with TCP/IP capabilities in Desqview/X (v2.1, the
latest) package. It did recognize IPX (if proper drivers were installed)
but that's not it.
 
> As I have a ibmps1 here that wont boot into elks, an x-term alternative would
> be worth looking into.  ( I am presenting a demo on x-terms at the local lug
> soon and a few "unique demos will be good" an elks telnet via slip will be
> running too :-)

PS1 = AT class machine. As people pointed out Desqview/X won't (well,
shouldn't according to docs) run on sub-386 processors. Older version
Gregg was referring to (namely Desqview) don't have X capabilities.

Blaz Antonic

Re: 286 xterm?

[Gavin]

Actually this brings us back to a gui for ELKS Since even the desqview option 
is 386 onwards, and for this I would use a cut down linux, if there's enough 
memory in the graphics card even a 386 is pretty acceptable x-term. 

I wonder now as to the nano-x option. So for me, this has gone full circle, 
and back to seeing what it would take to get a gui onto an AT class machine.

Thanks to all who contributed. Now can we get a solution ????? 


On Wednesday 04 September 2002 4:59 am, Blaz Antonic wrote:
> This is getting slightly off-topic but anyway ...
>
>
> > As I have a ibmps1 here that wont boot into elks, an x-term alternative
> > would be worth looking into.  ( I am presenting a demo on x-terms at the
> > local lug soon and a few "unique demos will be good" an elks telnet via
> > slip will be running too :-)
>
> PS1 = AT class machine. As people pointed out Desqview/X won't (well,
> shouldn't according to docs) run on sub-386 processors. Older version
> Gregg was referring to (namely Desqview) don't have X capabilities.

Re: 286 xterm?

[Chad Page]

	Unfortunatly nano-X does not, AFAIK, use the X wire protocol.  If
it were hacked to do so, or a wrapper was made around it, it could be made
to work.  For it to be more useful elksnet would also need ethernet
support which is quite a bit of reworking too.

	In theory it's possible, although I'm not sure how practical it
would be as most video systems which could handle X at an acceptable speed
with >=8bit color are on systems can run regular Linux and XFree86 given
enough memory (8MB).  I could see 800x600 in monochrome using an SVGA card
working decently on a 286 however, since that mode fits into a 64K
segment.  If someone was interested in trying this it could probably be
written first under regular Linux.

	Also there are many different versions of PS/1 boxes - they
continued through the 486 era and then were renamed Aptiva.  Most of the
later ones were made by Acer.

	- Chad


On Tue, 3 Sep 2002, Gavin wrote:

> Actually this brings us back to a gui for ELKS Since even the desqview option 
> is 386 onwards, and for this I would use a cut down linux, if there's enough 
> memory in the graphics card even a 386 is pretty acceptable x-term. 
> 
> I wonder now as to the nano-x option. So for me, this has gone full circle, 
> and back to seeing what it would take to get a gui onto an AT class machine.
> 
> Thanks to all who contributed. Now can we get a solution ????? 
> 
> 
> On Wednesday 04 September 2002 4:59 am, Blaz Antonic wrote:
> > This is getting slightly off-topic but anyway ...
> >
> >
> > > As I have a ibmps1 here that wont boot into elks, an x-term alternative
> > > would be worth looking into.  ( I am presenting a demo on x-terms at the
> > > local lug soon and a few "unique demos will be good" an elks telnet via
> > > slip will be running too :-)
> >
> > PS1 = AT class machine. As people pointed out Desqview/X won't (well,
> > shouldn't according to docs) run on sub-386 processors. Older version
> > Gregg was referring to (namely Desqview) don't have X capabilities.
> 
> 
> -
> To unsubscribe from this list: send the line "unsubscribe linux-8086" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 

Re: 286 xterm?

[Robert de Bath]

I suppose one solution to this might be to use the VNC protocol to display
an X-terminal screen on an ELKS machine. You really wouldn't want to
run X at 800x600 though 'cause it's been designed for megapixel displays
(1024x768x1) from day one. Also 'cause VNC prefers truecolour displays
the minimum depth is probably 8-bit; as I remember the 1Mb (1024x768x8)
graphic cards were around at about the time of 286 but I don't suppose
they're gonna be that fast ...

NB: http://www.uk.research.att.com/vnc/

Of course VNC needs ethernet too and I would expect that to be rather
rare on a machine of that age.

-- 
Rob.                          (Robert de Bath <robert$ @ debath.co.uk>)
                                       <http://www.cix.co.uk/~mayday>

Re: 286 xterm?

[Francois Gurin]

On Thu, Sep 05, 2002 at 08:45:39PM +0100, Robert de Bath wrote:
> 
> I suppose one solution to this might be to use the VNC protocol to display
> an X-terminal screen on an ELKS machine. You really wouldn't want to
> run X at 800x600 though 'cause it's been designed for megapixel displays
> (1024x768x1) from day one. Also 'cause VNC prefers truecolour displays
> the minimum depth is probably 8-bit; as I remember the 1Mb (1024x768x8)
> graphic cards were around at about the time of 286 but I don't suppose
> they're gonna be that fast ...
> 
> NB: http://www.uk.research.att.com/vnc/
> 
> Of course VNC needs ethernet too and I would expect that to be rather
> rare on a machine of that age.

is there a vnc version supporting <=386?  i seem to recall the dosvnc port
came precompiled 32bit but it's been a while.  as for bit depths, that can
be easily modified, i know some clients will dither down to 4-bit usefully.
(the palmos client comes to mind, it also had a server optimized for palm, 
but the client itself works fine with stock vncserver)

--francois

Re: 286 xterm?

[Dan Olson]

> Of course VNC needs ethernet too and I would expect that to be rather
> rare on a machine of that age.

8 and 16 bit ISA ethernet cards are very common, actually.


	Dan

Re: 286 xterm?

[Gregg C Levine]

Hello from Gregg C Levine
Indeed! In fact whenever I had to work on a system that was a bona-fide
PC/XT type, it wore a 3c509, or something along those lines. You can pick up
a 3c509 for price that's so low, you'd swear that the card was a clone.
Gregg C Levine obiwanthejediknight@att.net
<This signature will be replaced, pending an approval from the Jedi Council.
>
----- Original Message -----
From: "Dan Olson" <dano@agora.rdrop.com>
To: "Linux-8086 - ELKS" <Linux-8086@vger.kernel.org>
Sent: Thursday, September 05, 2002 4:18 PM
Subject: Re: 286 xterm?


>
> > Of course VNC needs ethernet too and I would expect that to be rather
> > rare on a machine of that age.
>
> 8 and 16 bit ISA ethernet cards are very common, actually.
>
>
> Dan
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-8086" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>

Re: 286 xterm?

[Robert de Bath]

On Fri, 6 Sep 2002, Gregg C Levine wrote:

> Hello from Gregg C Levine
> Indeed! In fact whenever I had to work on a system that was a bona-fide
> PC/XT type, it wore a 3c509, or something along those lines. You can pick up
> a 3c509 for price that's so low, you'd swear that the card was a clone.
> Gregg C Levine obiwanthejediknight@att.net
> <This signature will be replaced, pending an approval from the Jedi Council.
> >
> ----- Original Message -----
> From: "Dan Olson" <dano@agora.rdrop.com>
> To: "Linux-8086 - ELKS" <Linux-8086@vger.kernel.org>
> Sent: Thursday, September 05, 2002 4:18 PM
> Subject: Re: 286 xterm?
>
>
> >
> > > Of course VNC needs ethernet too and I would expect that to be rather
> > > rare on a machine of that age.
> >
> > 8 and 16 bit ISA ethernet cards are very common, actually.

AFAICR Ethernet only became popular with the arrival of Win 3.11 on 386s.
All those loose 10Mb ethernet cards are much later vintage, I suspect from
the switch between 10Mb/s and 100Mb/s.

I don't know how many <=286s were retro-fitted with ethernet though and
as 10Mb cards are now seen as worthless I don't suppose it matters.

-- 
Rob.                          (Robert de Bath <robert$ @ debath.co.uk>)
                                       <http://www.cix.co.uk/~mayday>

Re: 286 xterm?

[Dan Olson]

> AFAICR Ethernet only became popular with the arrival of Win 3.11 on 386s.
> All those loose 10Mb ethernet cards are much later vintage, I suspect from
> the switch between 10Mb/s and 100Mb/s.
>
> I don't know how many <=286s were retro-fitted with ethernet though and
> as 10Mb cards are now seen as worthless I don't suppose it matters.

I guess a little of this stuff is somewhat before my time, but I seem to
recall ethernet being popular with Novell Netware for drive sharing and
printer sharing with MS DOS.  For example, my high school had a netware
server with all the applications on it, and many of the school's computers
just booted off a floppy, loaded the network drivers, then ran everything
from the server.  The network included everything from origional PCs and
Tandy 1000s to newer (at that time) 386s and 486s.  I have a few 3 Com
etherlink cards (not etherlink II) that are full length 8 bit cards that
required a manual jumper to select thicknet (DB15) or ten-base-2 (coax).

	Dan

Re: 286 xterm?

[Jacek Lipkowski]

On Tue, 10 Sep 2002, Dan Olson wrote:

> I guess a little of this stuff is somewhat before my time, but I seem to
> recall ethernet being popular with Novell Netware for drive sharing and
> printer sharing with MS DOS.  For example, my high school had a netware

and don't forget all of the packet driver based software for the pc. in
some environments this was really used alot (and NCSA telnet is still one
of the best telnet clients i've seen). there was even an nfs server for
the pc (sos) and a graphics based web client (i think it was called
Arachne). also don't forget ka9q NET and all derivatives of it (we had a
nice 286 based router working for several years). check the simtel msdos
archives for lots of useful software.

jacek

Re: 286 xterm?

[Seemanta Dutta]

greetings to all linux gurus.....

i am an ELKS newbie though i have been using linux for quite some time now..
i have the recent images of ELKS and i can boot from an ELKS floppy..but the
problem that i am facing is this:

				i want to access the PC parllel port from 
ELKS..
i can do that from normal linux...the necessary function calls ie. ioperm() 
and
outb() are defined in /asm/io.h and unistd.h respectively....

my program is just a simple one to control the lighting of a 8 LEDs
connected to data pins of the parallel interface...as long as i use 'gcc' 
its absolutely
fine....but i am not being able to compile my program using 'bcc'..the 
program i
am using is given below..albeit a very short and simple one...

#include<sys/io.h>
#include<unistd.h>
int main()
{
        ioperm(0x378,3,1);  //to enable access to the parallel port..
        for(;;)
          outb(0x88,0x378);  //writing 0x88 or 10001000b to the data 
pins..thereby lighting the LEDs....
        return 0;
}			

now when i compile it using bcc as :
					 bcc testport.c -o testport
the error reported is this:
				testport.c:1.18: error: cannot find include 
file sys/io.h
OK..i get it then i try out this..using the '-I' option of bcc:
				bcc testport.c -I/usr/include/sys -o 
testport
the output i get is this....
			
			testport.c:1.18: error: cannot find include file 
sys/io.h
/usr/include/sys/unistd.h:1.19 (from /usr/include/sys/unistd.h:1) 
(from /usr/include/sys/unistd.h:1) 
(from /usr/include/sys/unistd.h:1) (from/usr/include/sys/unistd.h:1) 
(from /usr/include/sys/unistd.h:1) 
(from /usr/include/sys/unistd.h:1) (from /usr/include/sys/unistd.h:1) 
(from /usr/include/sys/unistd.h:1) 
(from /usr/include/sys/unistd.h:1)  .....like this for several pages...and 
in the end i get this line..)
(from testport.c:2): error: cannot find include file unistd.h

i am not able to make anything out of this.....is there any other option of 
nasm that i might be missing??any libraries that i might be
mising??
kindly help....i shall ever be grateful

there is another trivial  question that i would like to ask....

whenever i am running the above program after compiling thru gcc...i get 
the LEDs lighted, alright...but the other LEDs that are not supposed
to light up..also light up and then light off..although very fast...for 
example if i write hex F8 on the data port...
what i should get is this: on on on on on off off off  in my LEDs...
but the last three LEDs switch between on and off states very fast..thus 
what i get actually is a series of alternating F8 and FF in my
LEDs...can u suggest any thing???

one last query....whenver i am not running my program even then some random 
bytes are displayed on the data pins of the parallel port....
what process will be doing this? i have my 'lpd' disabled too....
what i want is that when i am writing to my port..no one should....so that 
the output i get from my LEDs is always constant.....
so my question now is: how can i know what process is accessing my port 
even when i am writing to it??
can i disable it from doing it?
kindly help this newbie out of these problems....
i hope i did not waste ur precious time with such trivial and boring 
questions...;-)
regards...
thanks in advance....
seemanta

newbie...please help.....

[Seemanta Dutta]

greetings to all linux gurus.....

i am an ELKS newbie though i have been using linux for quite some time now..
i have the recent images of ELKS and i can boot from an ELKS floppy..but the
problem that i am facing is this:

				i want to access the PC parllel port from 
ELKS..
i can do that from normal linux...the necessary function calls ie. ioperm() 
and
outb() are defined in /asm/io.h and unistd.h respectively....

my program is just a simple one to control the lighting of a 8 LEDs
connected to data pins of the parallel interface...as long as i use 'gcc' 
its absolutely
fine....but i am not being able to compile my program using 'bcc'..the 
program i
am using is given below..albeit a very short and simple one...

#include<sys/io.h>
#include<unistd.h>
int main()
{
        ioperm(0x378,3,1);  //to enable access to the parallel port..
        for(;;)
          outb(0x88,0x378);  //writing 0x88 or 10001000b to the data 
pins..thereby lighting the LEDs....
        return 0;
}			

now when i compile it using bcc as :
					 bcc testport.c -o testport
the error reported is this:
				testport.c:1.18: error: cannot find include 
file sys/io.h
OK..i get it then i try out this..using the '-I' option of bcc:
				bcc testport.c -I/usr/include/sys -o 
testport
the output i get is this....
			
			testport.c:1.18: error: cannot find include file 
sys/io.h
/usr/include/sys/unistd.h:1.19 (from /usr/include/sys/unistd.h:1) 
(from /usr/include/sys/unistd.h:1) 
(from /usr/include/sys/unistd.h:1) (from/usr/include/sys/unistd.h:1) 
(from /usr/include/sys/unistd.h:1) 
(from /usr/include/sys/unistd.h:1) (from /usr/include/sys/unistd.h:1) 
(from /usr/include/sys/unistd.h:1) 
(from /usr/include/sys/unistd.h:1)  .....like this for several pages...and 
in the end i get this line..)
(from testport.c:2): error: cannot find include file unistd.h

i am not able to make anything out of this.....is there any other option of 
nasm that i might be missing??any libraries that i might be
mising??
kindly help....i shall ever be grateful

there is another trivial  question that i would like to ask....

whenever i am running the above program after compiling thru gcc...i get 
the LEDs lighted, alright...but the other LEDs that are not supposed
to light up..also light up and then light off..although very fast...for 
example if i write hex F8 on the data port...
what i should get is this: on on on on on off off off  in my LEDs...
but the last three LEDs switch between on and off states very fast..thus 
what i get actually is a series of alternating F8 and FF in my
LEDs...can u suggest any thing???

one last query....whenver i am not running my program even then some random 
bytes are displayed on the data pins of the parallel port....
what process will be doing this? i have my 'lpd' disabled too....
what i want is that when i am writing to my port..no one should....so that 
the output i get from my LEDs is always constant.....
so my question now is: how can i know what process is accessing my port 
even when i am writing to it??
can i disable it from doing it?
kindly help this newbie out of these problems....
i hope i did not waste ur precious time with such trivial and boring 
questions...;-)
regards...
thanks in advance....
seemanta

Re: 286 xterm?

[kees]

Hi,

Unisys had nice units with 286, 1 MB, NE1000 type ethernet interface, ps2
mous and keyboard, extension up to 4 MB, VGA, serial and parallel port.
This unit probabely was fitted on rear of monitor and had power from it.

Kees


On Tue, 10 Sep 2002, Robert de Bath wrote:

> On Fri, 6 Sep 2002, Gregg C Levine wrote:
>
> > Hello from Gregg C Levine
> > Indeed! In fact whenever I had to work on a system that was a bona-fide
> > PC/XT type, it wore a 3c509, or something along those lines. You can pick up
> > a 3c509 for price that's so low, you'd swear that the card was a clone.
> > Gregg C Levine obiwanthejediknight@att.net
> > <This signature will be replaced, pending an approval from the Jedi Council.
> > >
> > ----- Original Message -----
> > From: "Dan Olson" <dano@agora.rdrop.com>
> > To: "Linux-8086 - ELKS" <Linux-8086@vger.kernel.org>
> > Sent: Thursday, September 05, 2002 4:18 PM
> > Subject: Re: 286 xterm?
> >
> >
> > >
> > > > Of course VNC needs ethernet too and I would expect that to be rather
> > > > rare on a machine of that age.
> > >
> > > 8 and 16 bit ISA ethernet cards are very common, actually.
>
> AFAICR Ethernet only became popular with the arrival of Win 3.11 on 386s.
> All those loose 10Mb ethernet cards are much later vintage, I suspect from
> the switch between 10Mb/s and 100Mb/s.
>
> I don't know how many <=286s were retro-fitted with ethernet though and
> as 10Mb cards are now seen as worthless I don't suppose it matters.
>
> --
> Rob.                          (Robert de Bath <robert$ @ debath.co.uk>)
>                                        <http://www.cix.co.uk/~mayday>
>
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-8086" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>

Re: 286 xterm?

[Chad Page]

	VNC would be a good solution if it has a 1-bit mode... as for why
I mentioned 800x600x2 - that's what fits on 1 64K page and is going to be
optimal on a 16-bit card with almost all non-accelerated SVGA cards.  Some
cards had good bank selection IIRC, so they would do well in higher
resolutions.

	- Chad


On Thu, 5 Sep 2002, Robert de Bath wrote:

> 
> I suppose one solution to this might be to use the VNC protocol to display
> an X-terminal screen on an ELKS machine. You really wouldn't want to
> run X at 800x600 though 'cause it's been designed for megapixel displays
> (1024x768x1) from day one. Also 'cause VNC prefers truecolour displays
> the minimum depth is probably 8-bit; as I remember the 1Mb (1024x768x8)
> graphic cards were around at about the time of 286 but I don't suppose
> they're gonna be that fast ...
> 
> NB: http://www.uk.research.att.com/vnc/
> 
> Of course VNC needs ethernet too and I would expect that to be rather
> rare on a machine of that age.
> 
> -- 
> Rob.                          (Robert de Bath <robert$ @ debath.co.uk>)
>                                        <http://www.cix.co.uk/~mayday>
> 
> 
> 

Re: 286 xterm?

[Bardelli Luigi]

On Tue, 3 Sep 2002, Blaz Antonic wrote:

> This is getting slightly off-topic but anyway ... 
> 
> > Can you also confirm the desqview-x will actually make an x-term, and if so is
> > there any info/howtos on this ???
> 
> I'd love to hear about that too; there are absolutely no docs on how to
> make Desqview/X run with TCP/IP capabilities in Desqview/X (v2.1, the
> latest) package. It did recognize IPX (if proper drivers were installed)
> but that's not it.

I'd like also to have a (small) howto on it!
Luigi

Re: newbie...please help.....

[teo_icKs]

hi, 

if you want to make bin in ELKS (and you haven't its libc)you must use
its include file with bcc and then statically link file object in your
app;
First of all install ELKS source files (for ex. /usr/src/elks) in your
linux
environment; instead use bcc in this way:

bcc -0 -ansi -I/usr/bcc/include/ -I/usr/src/elks/include/ -o
Parallela  	          parallela.c /usr/src/elks/arch/i86/lib/outportb.o

the modified source code of your app...

#include<arch/io.h>   /* is the correct position of io.h in ELKS */
#include<unistd.h> 
int main() 
{ 
       /*- ioperm(0x378,3,1);  to enable access to the parallel port.. 
				not implement				*/
	
       for(;;){ 
       		outb(0x88,0x378); /* writing 0x88 or 10001000b to the data 
            	                     pins..thereby lighting the LEDs.... */
       } 
} 

before this you must compile the implementation of outb function; this
is an assembly file in the source code of ELKS kernel. 
If have you compiled the Kernel ..... good 
(you can link directly the object file> outportb.o)
else learn to make it!!!! :-)

If you have the small version of libc, don't you need to statically link
it in your app.

> whenever i am running the above program after compiling thru gcc...i get 
> the LEDs lighted, alright...but the other LEDs that are not supposed 
> to light up..also light up and then light off..although very fast...for 
> example if i write hex F8 on the data port... 
> what i should get is this: on on on on on off off off in my LEDs... 
> but the last three LEDs switch between on and off states very fast..thus 
> what i get actually is a series of alternating F8 and FF in my 
> LEDs...can u suggest any thing??? 

THis effect is probably caused by another process who use this port;
Kill all suspected process and try it again! ....:-0
With ELKS kernel and the code that I have fixed, this problem there
isn't.

Now I don't know what process could uses your parallel port...  

however in Linux kernel, use this port with read, write, open and the
other syscall! It's safer then the direct access to register.

teo_icKs    ....    ....     ....    .....    ....
______________________________________________________________________
Scarica il nuovo Yahoo! Messenger: con webcam, nuove faccine e tante altre novità.
http://it.yahoo.com/mail_it/foot/?http://it.messenger.yahoo.com/