I use Netbsd in 16M on a 386, it takes a few mins for X to get settled as
far as what's going to be swapped out and what'll stay in active memory,
at which point 3.3.6 behaves well considering the lack of acceleration and
that it's on a 386.

Sound support shouldn't chew up all that much active memory/resources, and
would probalbly be just as easily implimented directly.

X may take some work, but it would be nice to have an X-server I can
direct my big workstation to with decent TV out. : )

Joshua Coombs

On Tue, 13 Feb 2001, Rob Healey wrote:

>
> 	Would it make sense to try and get one of the open source JAVA VM's
> 	to do graphics/audio on the DC rather than using an X server and
> 	audio server?
>
> 	Since cell phones and such use JAVA VM's for their graphic system I
> 	was thinking it might be better suited to the DC's 16M memory
> 	footprint than an X server.
>
> 	Maybe code up the VM to use wsdisplay, wsmouse, wsjoy(?) and then
> 	drive graphics/audio via JAVA apps rather than X apps?
>
> 	I've used X on one of my 16M NetBSD/Amiga's and it ain't what I would
> 	call "snappy" although the X clients themselves work well when
> 	displayed elsewhere...
>
> 	So, any opinions on using a JAVA engine for DC graphics/audio apps?
>
> 		-Rob
>