3.3.0.9 locks up
Moderator: mikel
-
- Posts: 39
- Joined: Fri Jan 25, 2008 10:37 am
- Location: Davie, Fl
- Contact:
3.3.0.9 locks up
Why, Can I not open a file to view an old log without connecting a tool first. It just locks up half way through opening any old datalog file.
- mikel
- Posts: 57794
- Joined: Tue Jan 16, 2007 1:17 pm
- Location: DiabloSport World Headquarters
- Contact:
Re: 3.3.0.9 locks up
can you post one of those logs here?
I have not seen such an issue....
I have not seen such an issue....
Mike Litsch
DiabloSport Brand Manager
Diablo Tech support by phone:
561-908-0040
M-F 8:00 AM to 5:00 PM EST
tech@diablosport.com
DiabloSport Brand Manager
Diablo Tech support by phone:
561-908-0040
M-F 8:00 AM to 5:00 PM EST
tech@diablosport.com
-
- Posts: 39
- Joined: Fri Jan 25, 2008 10:37 am
- Location: Davie, Fl
- Contact:
- mikel
- Posts: 57794
- Joined: Tue Jan 16, 2007 1:17 pm
- Location: DiabloSport World Headquarters
- Contact:
Re: 3.3.0.9 locks up
yeah, that log is fubard.
Mike Litsch
DiabloSport Brand Manager
Diablo Tech support by phone:
561-908-0040
M-F 8:00 AM to 5:00 PM EST
tech@diablosport.com
DiabloSport Brand Manager
Diablo Tech support by phone:
561-908-0040
M-F 8:00 AM to 5:00 PM EST
tech@diablosport.com
-
- Posts: 2
- Joined: Wed Nov 10, 2010 12:26 am
Re: 3.3.0.9 locks up
Same version locking up for me as well
Re: 3.3.0.9 locks up
Rage-tek.com wrote:Why, Can I not open a file to view an old log without connecting a tool first. It just locks up half way through opening any old datalog file.
I having the same issue with most of my logs. I've found a couple that will open but most lock up DV.
Needless Torque Calibrations
www.needlesstorque.com
www.needlesstorque.com
Re: 3.3.0.9 locks up
Not necessarily corrupt file. I had the same thing happen on my primary computer whenever I tried to load a Ford log file. I installed DataViewer on another computer (and after fixing an annoying SideBySide dependency issue), the same log file opened perfectly fine. I figured out the C++ redistribution dependency issue but this one has me stumped. BTW, I'm using DV v3.3.0.10 and this happened with log files recorded using both v3.3.0.8 and v3.3.0.10.