Screen savers

[JERRY WHITMIRE]

Hi my screen savers will not work like they should some not all.

i am using Fedora core 3 and Fedora core 3 test 3 I have XP2200 chip set to 
266 mhz and  256 mb of 2700/333 mhz ram set to 333 mhz

I have a video card with 16 mb of ram. the cpu and video card has worked 
with the screen savers before i did a mother board change to an asus  
a7v8x-x. and did a fresh install and up2date on the Fedora core 3 on the 
Fedora core 3 test 3 was a pick the rpm i wanted to use on it.
When it is set to come on the screen just goes black it does not go to the 
sleep mode  .namely the ones in the [ open gl or if it has a lot of movement 
to it ]  but if it comes on set in random they seem to work right or if i 
put them on the test mode they work but use a lot of my cpu power up to 
about 60%
is this because i only have 256mb of ram ?  i had 512 mb of pc 2100/266 mhz 
ram before. Am not sure what is going on here.[ have second email to follow 
this one]
Any help would be welcomed.  Thanks

_________________________________________________________________
On the road to retirement? Check out MSN Life Events for advice on how to 
get there! http://lifeevents.msn.com/category.aspx?cid=Retirement

[Edward Dekkers]

JERRY WHITMIRE wrote:
>  Hi my screen savers will not work like they should some not all.
>  
>  i am using Fedora core 3 and Fedora core 3 test 3 I have XP2200 chip set 
>  to 266 mhz and  256 mb of 2700/333 mhz ram set to 333 mhz
>  
>  I have a video card with 16 mb of ram. the cpu and video card has worked 
>  with the screen savers before i did a mother board change to an asus  
>  a7v8x-x. and did a fresh install and up2date on the Fedora core 3 on the 
>  Fedora core 3 test 3 was a pick the rpm i wanted to use on it.
>  When it is set to come on the screen just goes black it does not go to 
>  the sleep mode  .namely the ones in the [ open gl or if it has a lot of 
>  movement to it ]  but if it comes on set in random they seem to work 
>  right or if i put them on the test mode they work but use a lot of my 
>  cpu power up to about 60%
>  is this because i only have 256mb of ram ?  i had 512 mb of pc 2100/266 
>  mhz ram before. Am not sure what is going on here.[ have second email to 
>  follow this one]
>  Any help would be welcomed.  Thanks
>   
If your CPU goes that high, undoubtably you're doing software rendering 
on GL screensavers, not using the hardware.

Make sure you're using the correct drivers for your video card or chip.

Regards,
Ed.

Date/Time setting

[Alan McDonald]

I synchronise some files across an ftp connection. The files comes from a
computer with the current date/time set, and my PC is also set with correct
time (both clock and hwclock return the correct time). But the files which
are writtin into the ftp directory are 13 hours ascew.. How can I correct
this? Where is the magic setting for making files writen to disk obey the
curret clock?
thanks
Alan

Date/Time setting

[Fritz Whittington]

On or about 2005-03-02 06:14, Alan McDonald whipped out a trusty #2 
pencil and scribbled:

> I synchronise some files across an ftp connection. The files comes
> from a
> computer with the current date/time set, and my PC is also set with correct
> time (both clock and hwclock return the correct time). But the files which
> are writtin into the ftp directory are 13 hours ascew.. How can I correct
> this? Where is the magic setting for making files writen to disk obey the
> curret clock?
> thanks
> Alan
>   
>  
I'm presuming that this involves moving files from a Windows machine to 
Linux, or vv.  Both Windows and Linux use UTC for timestamps.  The 
difference is, in Windows you set the hardware clock to your local time, 
tell it which timezone you're in, and it converts to UTC when stamping 
file times.  Likewise, it converts timestamps back to local time for 
DISPLAY purposes when you list the directory. 

Linux/Unix do it the other way.  The hardware clock is usually set to 
UTC, you tell it what time zone you're in, and the DISPLAY of times will 
be in local, but timestamps on files will be in UTC.

As a convenience to those who have one machine with a dual-boot of 
Windows/Linux, most distros allow you to declare that the hardware clock 
is actually not UTC, but local.  Then when Linux boots, it reads the 
hardware clock, applies the TZ correction, then sets the system clock to 
UTC.  If you tell Linux the hardware clock is UTC, then it doesn't apply 
the correction on boot, just sets the system clock to the hardware 
clock, and goes on as usual.

Windows of course, has no facility to be told that the hardware clock is 
on UTC, and to correct for local time zone on booting.  So for Windows 
you must set local time on the hardware clock. 

Another problem is that you can have your Windows time zone set 
incorrectly, and someone has set the hardware clock to compensate.  So 
if I in the US Central TZ set my Windows system to the Greenwich time 
zone, then fiddle with the clock setting so that the time "looks 
correct", then Windows will think it does not need to apply any 
correction to get UTC, but all it's timestamps will then be off by 6 
hours.  (A file created at 8:00 am local time would actually be stamped 
as 0800 UTC, when it really should be stamped as 0200 UTC.)

Similar things of course can happen in Linux, in the opposite direction, 
if you don't have your TZ data set correctly and just force the clock to 
look like correct local time. 

-- 
Fritz Whittington
It is the duty of every citizen according to his best capacities to give validity to his
convictions in political affairs. (Albert Einstein, 'Treasury for the Free World,'
1946)

Date/Time setting

[Fritz Whittington]

On or about 2005-03-02 14:40, Fritz Whittington whipped out a trusty #2 pencil 
and scribbled:
>  On or about 2005-03-02 06:14, Alan McDonald whipped out a trusty #2 
>  pencil and scribbled:
>  
> > I synchronise some files across an ftp connection. The files comes from a
> > computer with the current date/time set, and my PC is also set with 
> > correct
> > time (both clock and hwclock return the correct time). But the files 
> > which
> > are writtin into the ftp directory are 13 hours ascew.. How can I correct
> > this? Where is the magic setting for making files writen to disk obey the
> > curret clock?
> > thanks
> > Alan
> >  
> >
>  I'm presuming that this involves moving files from a Windows machine to 
>  Linux, or vv.  Both Windows and Linux use UTC for timestamps.  The 
>  difference is, in Windows you set the hardware clock to your local time, 
>  tell it which timezone you're in, and it converts to UTC when stamping 
>  file times.  Likewise, it converts timestamps back to local time for 
>  DISPLAY purposes when you list the directory.
>  Linux/Unix do it the other way.  The hardware clock is usually set to 
>  UTC, you tell it what time zone you're in, and the DISPLAY of times will 
>  be in local, but timestamps on files will be in UTC.
>  
>  As a convenience to those who have one machine with a dual-boot of 
>  Windows/Linux, most distros allow you to declare that the hardware clock 
>  is actually not UTC, but local.  Then when Linux boots, it reads the 
>  hardware clock, applies the TZ correction, then sets the system clock to 
>  UTC.  If you tell Linux the hardware clock is UTC, then it doesn't apply 
>  the correction on boot, just sets the system clock to the hardware 
>  clock, and goes on as usual.
>  
>  Windows of course, has no facility to be told that the hardware clock is 
>  on UTC, and to correct for local time zone on booting.  So for Windows 
>  you must set local time on the hardware clock.
>  Another problem is that you can have your Windows time zone set 
>  incorrectly, and someone has set the hardware clock to compensate.  So 
>  if I in the US Central TZ set my Windows system to the Greenwich time 
>  zone, then fiddle with the clock setting so that the time "looks 
>  correct", then Windows will think it does not need to apply any 
>  correction to get UTC, but all it's timestamps will then be off by 6 
>  hours.  (A file created at 8:00 am local time would actually be stamped 
>  as 0800 UTC, when it really should be stamped as 0200 UTC.) 
Oooops!  That should be 1400 UTC, not 0200 UTC.  Sorry if the example caused 
even more confusion...

>  Similar things of course can happen in Linux, in the opposite
> direction, 
>  if you don't have your TZ data set correctly and just force the clock to 
>  look like correct local time.
>   

-- 
Fritz Whittington
Man is by nature a political animal. (Aristotle, Politics)