search

CobaltFusion / DebugViewPP

DebugView++, collects, views, filters your application logs, and highlights information that is important to you!
Boost Software License 1.0
1.02k stars 150 forks source link

Can't save Log file in negative time zones #226

Closed BillSTP closed 8 years ago

BillSTP commented 8 years ago

Attempting to save log file gives a "FileTimeToSystemTime: The parameter is incorrect" error message. A "dblog" file is created but it's empty. Getting this on several systems (PC, tablet). Noticed this behavior after latest Windows 10 update. Running version 1.4. Tried using version 1.6 but same error situation.

janwilmans commented 8 years ago

Thanks for reporting, I have had more windows 10 issues reported, I hoped they would go away with new windows 10 updates but it seems like that is not going to happen :) I'll install windows 10 in a virtual machine and see what I can do.

BillSTP commented 8 years ago

I'm testing some software on a Win 10 tablet and then sending the debug log file over to my Win 10 PC.

My workaround for now is to run version 1.2 on the tablet (which does let me save the log correctly) and then view it on the PC (using version 1.4).

On Thu, Feb 25, 2016 at 1:20 PM, Jan Wilmans notifications@github.com wrote:

Thanks for reporting, I have had more windows 10 issues reported, I hoped they would go away with new windows 10 updates but it seems like that is not going to happen :) I'll install windows 10 in a virtual machine and see what I can do.

— Reply to this email directly or view it on GitHub https://github.com/djeedjay/DebugViewPP/issues/226#issuecomment-188993776 .

janwilmans commented 8 years ago

Ok, I've tested on Windows 10 Professional, and it does not reproduce for me, I'm guessing it has something to do with a change I made in the way timestamps are saved. Can you give me more details? Does the error occur on the PC side as well, or only one the tablet. what are the regional settings of the tablet?

Also, are you aware that you run dbgview-agent on it the tablet (it is available from microsoft) and debugview++ can connect to it, just like dbgview. That way, you can have 'runtime / live' view the messages instead of load/saving.

BillSTP commented 8 years ago

I've tested on Windows 10 Professional...

I'm running Windows Home on the PC and the tablet (both have latest Win 10 update).

Same problem on PC and tablet. Same error message. And on both, an empty log file is created.

what are the regional settings of the tablet...

​

Also, are you aware that you run dbgview-agent on it the tablet...

Yup but I've never been able to get them to connect. DebugView puts up its "Waiting To Connect" messagebox on the tablet and when I try use the "Connect Debug View Agent" option on DebugView++, on the remote PC, it logs a "connection refused by target machine" error message. Tried tweaking the firewall on the tablet to no avail.

Seems like a nice feature. But, in for the sake of expediency, I ended doing the "save log on the remote from the tablet" procedure. not as elegant but it gets the job done.

By the way, nice job on DebugView++. The colorized processes and the filtering options are a pleasure to use.

Bill :-)

On Thu, Feb 25, 2016 at 4:53 PM, Jan Wilmans notifications@github.com wrote:

Ok, I've tested on Windows 10 Professional, and it does not reproduce for me, I'm guessing it has something to do with a change I made in the way timestamps are saved. Can you give me more details? Does the error occur on the PC side as well, or only one the tablet. what are the regional settings of the tablet?

Also, are you aware that you run dbgview-agent on it the tablet (it is available from microsoft) and debugview++ can connect to it, just like dbgview. That way, you can have 'runtime / live' view the messages instead of load/saving.

— Reply to this email directly or view it on GitHub https://github.com/djeedjay/DebugViewPP/issues/226#issuecomment-189058178 .

janwilmans commented 8 years ago

Bill, would you be willing to help solve the problem? I have a test-version I can share to debug the problem, please email me directly ( janwilmans at gmail dot com)

janwilmans commented 8 years ago

Thanks for the info bill, I have found the issue and will create a patch shortly

janwilmans commented 8 years ago

Actually, it turns out this is not windows 10 related at all. Any save attempt in a negative timezone (UTC-N) will fail because the header line is trying to save the FILETIME "0" which translates into a systemtime before 1601/01/01, which is not acceptable.