czdc++ 0.666i running 2 times (1 hashing), windows clock racing ahead
 

News:

29 December 2022 - PtokaX 0.5.3.0 (20th anniversary edition) released...
11 April 2017 - PtokaX 0.5.2.2 released...
8 April 2015 Anti child and anti pedo pr0n scripts are not allowed anymore on this board!
28 September 2015 - PtokaX 0.5.2.1 for Windows 10 IoT released...
3 September 2015 - PtokaX 0.5.2.1 released...
16 August 2015 - PtokaX 0.5.2.0 released...
1 August 2015 - Crowdfunding for ADC protocol support in PtokaX ended. Clearly nobody want ADC support...
30 June 2015 - PtokaX 0.5.1.0 released...
30 April 2015 Crowdfunding for ADC protocol support in PtokaX
26 April 2015 New support hub!
20 February 2015 - PtokaX 0.5.0.3 released...
13 April 2014 - PtokaX 0.5.0.2 released...
23 March 2014 - PtokaX testing version 0.5.0.1 build 454 is available.
04 March 2014 - PtokaX.org sites were temporary down because of DDOS attacks and issues with hosting service provider.

Main Menu

czdc++ 0.666i running 2 times (1 hashing), windows clock racing ahead

Started by Motivations, 11 April, 2005, 04:40:57

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

Motivations

Hello PPK,

(sorry admin for posting it here, if you have a better place for it let me know....

I placed it here because PPK is as far as I know also involved with czdc++, and the czdc++ forum has been down for a couple of weeks now...so this might be a good location for him to catch the following...)


I have the following strange and very annoying problem when I do the following.

I have setup a 2 dir configuration with 2 identical versions of czdc++ (0.666i), in order to have 2 different shares for 2 different hubs (with different sharing rules...)

When I tried to set this up I discovered that while the one was running fine and had (at first) no problems, and the second hashing about 900 GB of files, the windows system clock raced ahead compared to normal time at variable rates (last test I did was 1,5 hours over a 9 hours hashing period).
So my pc windows time was 10.30 pm  and real time was 9.00 pm....

When I tried to reset this to normal time, both configurations disconnected from the hubs I was connected to, and a quick reconnect (using the menubar icon) did nothing for me...

The only thing I could do was restart czdc++....and next the hubs connected fine again...

I believe it has to do with the hashing process, because next I did the following:  copied the hashindex files (both of them) to the second configuration dir, next started and restarted the second configuration a couple of times, to change the folders shared and to recreate the files.xml.bz2 file.....

....and you guessed it already perhaps, the windows time stayed the same as real time....

(note with windows time I mean the clock in the lower right corner).

Hope I have described it well enough for you to do something with, because I find it very strange when software changes my windows system time.....first time in my more than 10 years of windows use.

My system is running on windows 2003 server, 512MB memory...and during the hashing period I only had the 2 czdc++'s open....and was hashing at 5MB/s.

gr. Frank

jiten

Hi there.
Well, in the last week, something related happened to me while I was running PtokaX 16.09 debug.
At night, I saw that the windows date wasn't correct. So, I just changed it back to the original (less one day).
At that moment, I lost connection to every hub where I was and the same happened to all users that were hosted by my server, although I was able to open webpages and other normal stuff.
I had to restart the computer to be able to serve again.
Maybe it had something to do with timers... I'm not really sure about that.
Just to mention, it also happened to another guy that changed the windows clock time (backwards).

Cheers

PPK

Yes here is something broken in windows, i have reported problems in both PtokaX and CZDC++ (everything start with reports only from win 2003) and both use winapi GetTickCount() function :(
I don't have fix for this now...
"Most of you are familiar with the virtues of a programmer. There are three, of course: laziness, impatience, and hubris." - Larry Wall

plop

check in the local security policy from windows.
it's a feature 2 use the clock syncronisation as a security feature.
for example if my workstation has a different time then my fileserver i can't acces the shares from the fileserver.
somewhere in the policy you can set the max difference on the time which is considered safe.

plop
http://www.plop.nl lua scripts/howto\'s.
http://www.thegoldenangel.net
http://www.vikingshub.com
http://www.lua.org

>>----> he who fights hatred with hatred, drives the spreading of hatred <----<<

bastya_elvtars

This is a part of windows that should not be secure, while other parts are not secure. :D Billy boy!

BTW with some service packs installed you cannot update your XP, which I consider very secure. :P
Everything could have been anything else and it would have just as much meaning.

plop

QuoteOriginally posted by bastya_elvtars
This is a part of windows that should not be secure, while other parts are not secure. :D Billy boy!

BTW with some service packs installed you cannot update your XP, which I consider very secure. :P
with a alpha from M$ anti spyware app you can remove the source from spyware.
internet explorer itself.
now this is secure.

plop
http://www.plop.nl lua scripts/howto\'s.
http://www.thegoldenangel.net
http://www.vikingshub.com
http://www.lua.org

>>----> he who fights hatred with hatred, drives the spreading of hatred <----<<

bastya_elvtars

QuoteOriginally posted by plop with a alpha from M$ anti spyware app you can remove the source from spyware.
internet explorer itself.
now this is secure.

plop

Most important part of health care is prevention... it was M$ to apply it accureately. :)
Everything could have been anything else and it would have just as much meaning.

SMF spam blocked by CleanTalk