Ok, I'll admit I'm not well versed in Visual C and maybe there is a quick workaround, but on the surface it appears that the source in the current form has not been compiled in WIn32. Why? The includesin the source files are lower case and the filennames in most cases are upper and lower case, causing cpp to fail. Example include stdafx.h, however the file is named StdAfx.h... Am I missing something here? Ignore case on compile?
Dan
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
As far as I know, the included binary should run as is, pretty much anywhere other than 3.11 and 95. Otherwise, I had it once compiled under 98 with a borrowed copy of VC right before the initial commit.
I am a linux kinda guy so years ago I started a port onto Gnome but ran out of time and never finished it.
I'd imagine MS libraries might have changed a bit since then so it may take a little work to have it compiled with 21st century wonderful Microsoft technology.
You guys are welcome to check the code out and modify it to compile with anything you like. We can put the changes back onto the CVS tree afterwards.
good luck.
Winston
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I've made some good progress. I can now compile and execute FeeScan without crashes. One source of crashes was a unregistered control that is registered by the Windows Install. I need to get more information to close that loop. The other crash that affected me was a couple of coding errors in the 89Corvette protocol module that I'm using. Array sizes were set incorrectliy. It appears the 89Vette protocol was cloned from another GM (Camaro) protocol file, but a couple of important details were missed. I will be verifying and testing the protocol. I will also document the Win32 build file requirements as the structure that comes from CVS doesn't match the Visual C++ project/workspace structure. -Dan
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I have a 1988 Pontiac Fiero to which I installed a 1995 Corvette LT1 engine. I used Freescan to check and clear codes and monitor events. I may have some pictures of the laptop sitting next to me at the track. - http://www.FieroLT1.com
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
FreeScan now runs without crashing. I have basic 89Corvette functionality working. The next step is refining the displays to fcomplete the mapping of the 89Corvette. I should also be able to add the 86-88 TPI Corvette,Camaro Z28 and Pontiac Firebird to the list.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Ok, I'll admit I'm not well versed in Visual C and maybe there is a quick workaround, but on the surface it appears that the source in the current form has not been compiled in WIn32. Why? The includesin the source files are lower case and the filennames in most cases are upper and lower case, causing cpp to fail. Example include stdafx.h, however the file is named StdAfx.h... Am I missing something here? Ignore case on compile?
Dan
Also have found that the folder protocols is referenced as "protocols" and "Protocols". This is also providing compile time errors.
Dan
As far as I know, the included binary should run as is, pretty much anywhere other than 3.11 and 95. Otherwise, I had it once compiled under 98 with a borrowed copy of VC right before the initial commit.
I am a linux kinda guy so years ago I started a port onto Gnome but ran out of time and never finished it.
I'd imagine MS libraries might have changed a bit since then so it may take a little work to have it compiled with 21st century wonderful Microsoft technology.
You guys are welcome to check the code out and modify it to compile with anything you like. We can put the changes back onto the CVS tree afterwards.
good luck.
Winston
I put some effort into porting it over to Linux, however I am not a programmer so I'm suffering a steep learning curve, not from lack of trying.
OK, I've been massaging the case of the includes source so it compiles now under WinXP and Visual C++ 6.0. The environment I'm in is case sensitive.
Now I've got to figure out why the exe crashes when it executes!
I'm also from the linux/unix world, so this development world is a bit foreign to me.
I'll be adding a MAF based 1227165 ECU - TPI Camaros, Firebirds, and Corvettes.
Dan
I've made some good progress. I can now compile and execute FeeScan without crashes. One source of crashes was a unregistered control that is registered by the Windows Install. I need to get more information to close that loop. The other crash that affected me was a couple of coding errors in the 89Corvette protocol module that I'm using. Array sizes were set incorrectliy. It appears the 89Vette protocol was cloned from another GM (Camaro) protocol file, but a couple of important details were missed. I will be verifying and testing the protocol. I will also document the Win32 build file requirements as the structure that comes from CVS doesn't match the Visual C++ project/workspace structure. -Dan
Good deal Dan.
Keep up the good work!
I have a 1988 Pontiac Fiero to which I installed a 1995 Corvette LT1 engine. I used Freescan to check and clear codes and monitor events. I may have some pictures of the laptop sitting next to me at the track. - http://www.FieroLT1.com
FreeScan now runs without crashing. I have basic 89Corvette functionality working. The next step is refining the displays to fcomplete the mapping of the 89Corvette. I should also be able to add the 86-88 TPI Corvette,Camaro Z28 and Pontiac Firebird to the list.