Terrible confusion with time variables

I keep getting through the debugger and my output that according to the _timeb struct the time in seconds from January 1, 1970 is around 8.44456*10^16. However, some simple calculation shows that it is in fact around 1.2173*10^9. This is off by 7 orders of magnitude and doesn't look anything like the correct value. Is there something that I'm missing? Can someone clear up my confusion?

Exactly what are you inspecting to see your timeb value?

--
Mats

Quote:

---

Originally Posted by matsp

Exactly what are you inspecting to see your timeb value?

--
Mats

---

I'm sorry, but I don't understand what you mean by "what are you inspecting to see."

Well, lets put it another way: Your calculations are good, you should end up with approximately 1.1E9. So I'm trying to find out if, for example, you have got the wrong data output, so you are looking at, perhaps, the address of the value, rather than the value itself.

By the way, I'm not entirely sure that time HAS to be stored as seconds from 1 jan 1970 - it conventionally is, but I'm not quite sure nit's guaranteed.

--
Mats

Nevermind, I found a different time function to use that is much more reliable/easier. Thanks anyways!

Care to share your new insight with the rest of us?

Well, I found this way to do it:

Code:

---

time_t rawtime;
struct tm* timeinfo;

time ( &rawtime );
timeinfo = localtime ( &rawtime );

f_Start_Time = (timeinfo->tm_hour + (timeinfo->tm_min)/60. + (timeinfo->tm_sec)/3600.);

---

However, I have now been informed that I need to also implement milliseconds into my code and this can only go down to seconds. Now I'm really in need of some help. I've searched everywhere and tried a few different techniques to no avail. SYSTEMTIME crashes my program on runtime just by declaring the object. And Date objects just don't seem to want to instantiate.

Now, I readily admit that both of those problems could possibly be solved by just declaring them correctly (most of my training has been in Java, so the transition can prove tricky at times).

This is how I've tried SYSTEMTIME

Code:

---

#include "ATLComTime.h"

SYSTEMTIME SystemTime;

getSystemTime(&SystemTime);

---

and for Date

Code:

---

dateObj d;

d = new Date();

---

Any help on either of those or new suggestions would be greatly appreciated.

I can find no documentation that suggests SYSTEMTIME is defined in ATLComTime.h (MSDN says windows.h). That may help.

I tried including windows.h and also stdio.h but it stills crashes.

Quote:

---

Originally Posted by LowlyIntern

I tried including windows.h and also stdio.h but it stills crashes.

---

I would help a whole lot if you post a more complete piece of code [ideally something that is complete enough to both compile and show the actual problem].

--
Mats

That's actually quite difficult as there was no main function in the program as it was given to me (don't ask, nobody here knows why) and it doesn't output in a command window (it won't even let me output in the command window), but out through a port to an RS 422 card in hex. Plus, there's some 5 to 6 thousand lines of code to run the whole thing to show the problem. Basically, when I click "Apply" on my dialog box and this message comes up "OS Attitude MFC Application has encountered a problem and needs to close. We are sorry for the inconvenience."

However, this comes up if all im doing is simply declaring: SYSTEMTIME systime; (with windows.h and stdio.h included, of course) if that helps. Also, I don't know if this has to do with anything, but I'm also using timeb.h (was in the program when it was given to me) and time.h (because it does everything but milliseconds and works for now).

Unfortunately, it would be hard to figure out what the problem is - however, I expect that you could trap it in WinDBG in that case, and look at the call-stack to figure out what is going on.

--
Mats

The issue has (hopefully) been resolved. Turns out SYSEMTIME doesn't like to be declared in a header file, go figure.