Re: [UUG/MLUG] Fixed the time problem!

[Jay Buffington <EMAIL:PROTECTED>]

Well.. I have ONE reason remaining to run windows.  I bought a $200
PCMCIA 'CaptureVision Card' it came with a camera that clips on the side
of my laptop and it has Composite inputs.  this thing is really cool, I
can plug a VCR into my laptop and have a full screen television! (okay,
yeah I don't really need this thing, but its still cool).  However, the
specific reason I bought it was for video confercing with the girlfriend
(She lives in Kansas, phone calls are expensive).  Anyway, to get to the
point I cannot get the card working in linux.  So I've been booting
windows talking to her... this is very frustrating.  

So I started playing with VMware. I just got windows installed on it
(which took forever).  Getting the card to be recognized in the 'vmware
windows' has proved to be much more than trival.  Would it be easier to
use my existing windows partition (the one that the capture card works
in) in vmware?  

Sure running vmware will allow me to stay in linux and use my camera. 
but it takes sooo much over head (my laptop is a PII300, 64 ram) and it
takes a long time for windows to boot.  My ultimate goal would be for my
girlfriend (or whoever) to get on the internet and "call" me.  This
would make my laptop make a sound and I could "answer" the call by
popping up a box that allows us to begin video conferencing. 

So, then, does anyone have any comments on my situation?  The url for
the pcmcia card I have is http://www.nogatech.com/capturevison.htm

I suppose my only option is to learn how to write device drivers for
PCMCIA cards? :)  Does anyone know of video conferencing hardware that
will work with linux on laptop?  

Please help me eliminate my last existing need to use windows!
Any help/comments/ideas are appreciated.

Jay


EMAIL:PROTECTED wrote:
> 
> Now your only problem comes if you run that "other" OS on the same
> computer...
> 
> ;)
> Nimrod
> 
> On Fri, 8 Oct 1999, Jay Buffington wrote:
> 
> > Thanks for the advice, Chris.  After running `rdate time.nist.gov` I ran
> > `hwclock --systohc --utc` and my problem was totally gone.  hwclock set
> > the hardware clock to the same time as the system clock, but corrected
> > for for greenwich time.
> >
> > Glad to have that working :)
> >
> >
> > Jay