I'm not sure the resolution would be too good - TV resolution is much lowerQuote:> The other day I was thinking how one might go about combining a Linux box
> with another running Windows with a single monitor in the most convenient
> way. I know there are a lot of emulators, network methods, etc. but I
was
> thinking of something a little simpler, where one would not have to deal
> with an extra layer of software, or slow network connections. The best
> idea I could come up with, although it might be a little expensive, is to
> equip the linux box with a graphics card with a "TV IN" like as found on
> some ATI cards. Then arrange for the windows video out to be routed
> somehow to the ATI card like it was from a TV, only it's from a computer.
> If this could be done, then you could display the output from the windows
> box concurrently in a separate window on your desktop that you could
> resize, minimize, etc. Very convenient, and nothing to slow things down.
> I wonder if anyone's tried this?
> --
> _________________________________________________________________________
> George Bell/ | "Doug, you're suffering from a schizoid embolism."
> Arlington/ VA | <Coffee && Doughnuts
One thing you could do would be to run a VNC server on the Windows boc, VNC
client on the Linux box. Clearly you're concerned about slowing the network
down so why not install an extra NIC in each machine, connect with a
crossover cable, and have a dedicated bandwidth just for the VNC data
transfer? Probably cheaper than buying a TV card and coax cable, and
certainly better resolution.
james.
Yes, I see your point. Why have two video cards for one monitor? And I'veQuote:> I'm not sure the resolution would be too good - TV resolution is much
> lower than the standard 1024x768 you get with computers. Depending on your
> location, PAL gives you 625 lines (ie vertical resolution) and NTSC 525
> lines.
> One thing you could do would be to run a VNC server on the Windows boc,
> VNC client on the Linux box. Clearly you're concerned about slowing the
> network down so why not install an extra NIC in each machine, connect with
> a crossover cable, and have a dedicated bandwidth just for the VNC data
> transfer? Probably cheaper than buying a TV card and coax cable, and
> certainly better resolution.
> james.
Although, since distance is not an issue here, perhaps an even simpler
solution is possible. If the computers are close together, then why not
connect them with an ECP Parallel Ports instead? This would also eliminate
the overhead and delays involved with packageing data for sending and
recieving over NICS, and parallel ports are already standard come with most
computers anyway. Wouldn't the parallel port give as much or more bandwidth
in this situation? (If not, I guess one could also try to equip both
computers with SCSI ports - which may be expensive, I don't know.) Then a
daemon in the windows box could (theoretically) route/buffer the video data
out the pp and recieve mouse clicks/keyboard commands through the pp. On
the linux side there's more flexibility. I imagine you could hack the
kernal so that input from a given parallel port could always be written to
say, /dev/tty3, and all mouse clicks and keyboard punches would be written
to the pp from tty3. Otherwise, I suppose a daemon could be written to do
the same job. Maybe the VNC or other existing software could be used or
modified.
--
_________________________________________________________________________
George Bell/ | "Doug, you're suffering from a schizoid embolism."
Arlington/ VA | <Coffee && Doughnuts
> > I'm not sure the resolution would be too good - TV resolution is much
> > lower than the standard 1024x768 you get with computers. Depending on your
> > location, PAL gives you 625 lines (ie vertical resolution) and NTSC 525
> > lines.
> > One thing you could do would be to run a VNC server on the Windows boc,
> > VNC client on the Linux box. Clearly you're concerned about slowing the
> > network down so why not install an extra NIC in each machine, connect with
> > a crossover cable, and have a dedicated bandwidth just for the VNC data
> > transfer? Probably cheaper than buying a TV card and coax cable, and
> > certainly better resolution.
> > james.
> Yes, I see your point. Why have two video cards for one monitor? And I've
> also left out the communication with the keyboard and mouse.
> Although, since distance is not an issue here, perhaps an even simpler
> solution is possible. If the computers are close together, then why not
> connect them with an ECP Parallel Ports instead?
You'd then have the overhead of packaging it for theQuote:> This would also eliminate
> the overhead and delays involved with packageing data for sending and
> recieving over NICS, and parallel ports are already standard come with most
> computers anyway.
I don't think so. An ECP parallel port might come close toQuote:> Wouldn't the parallel port give as much or more bandwidth
> in this situation?
Much, much more expensive. 10/100 ethernet cards are underQuote:> (If not, I guess one could also try to equip both
> computers with SCSI ports - which may be expensive, I don't know.)
VNC should run unmodified on PLIP, SLIP (serial), or anyQuote:> Then a
> daemon in the windows box could (theoretically) route/buffer the video data
> out the pp and recieve mouse clicks/keyboard commands through the pp. On
> the linux side there's more flexibility. I imagine you could hack the
> kernal so that input from a given parallel port could always be written to
> say, /dev/tty3, and all mouse clicks and keyboard punches would be written
> to the pp from tty3. Otherwise, I suppose a daemon could be written to do
> the same job. Maybe the VNC or other existing software could be used or
> modified.
OK! So I guess it's already been done! All I have to do then is get thisQuote:> VNC should run unmodified on PLIP, SLIP (serial), or any
> other TCP/IP network.
OK! So I guess it's already been done! All I have to do then is get thisQuote:> VNC should run unmodified on PLIP, SLIP (serial), or any
> other TCP/IP network.
Pt
> > Although, since distance is not an issue here, perhaps an even simpler
> > solution is possible. If the computers are close together, then why not
> > connect them with an ECP Parallel Ports instead? This would also eliminate
> > the overhead and delays involved with packageing data for sending and
> > recieving over NICS, and parallel ports are already standard come with most
> > computers anyway. Wouldn't the parallel port give as much or more bandwidth
> > in this situation?
> I think dedicated 100 BT cards would be faster than ECP.
> Pt
moonie ;)
1. GETSERVBYNAME()????????????????????"""""""""""""
Hi,
Does anyone know why
struct servent *serv;
serv=getservbyname("exec","tcp");
gives a warning err of incomparible pointer type?
I also can't get rexec to function. It compiles ok....
Thanks
Kirk
2. 1.1.86 dep compile problem. genksyms?
3. "Box", "line drawing", "special graphics" characters in aixterm
4. Is a UNIX process running ? getprocs ?
5. """"""""My SoundBlast 16 pnp isn't up yet""""""""""""
6. ftape complains: Device not configured
7. Unix/linux "installation user" vs MS Windows "installation user".
8. Why should malloc() SIGSEGV on me?
9. Type "(", ")" and "{", "}" in X...
10. " No CDDB Entry" "Error Getting CDDB Entry" ???
11. Getting Sendmail to Read "Reply-To" and "Subject" from file
12. OPTUSHOME LINUX LAN SERV WITH 2 WINDOW BOXES "HELP"
13. xterm crashes X-window after "xset fp+ /xfont_path" on my Linux box