Any workaround for Tunercat OBD-II editior from not crashing ?

[teamzr1]

I'm not sure I have much to offer but what I've seen. Reading/writing/editing ecm's and pcm's I only use WinXP 32bit and have never had an issue with TC on multiple laptops through the years. Shoot, I still have some software that I have to keep a Win98 laptop around for. I've never had an XP 64bit system. My programming laptops rarely ever see the internet and when I need to transfer files I use a thumb drive. Now that some software requires Win7 or newer(Holley for example), we have no choice but to have another laptop. I see nothing but problems with my Win7 64bit, screens flashing on and off for no reason, complete freeze of computer but my mouse still moves around and more crap than I care to remember.
Now that the later .net framework and Visual Studio stuff doesn't work on XP we have a lot of problems with older software and compatibility mode is useless.
The good news is refurbished XP laptops on ebay are very reasonable as long as you check the seller. Local computer refurbish guys on craigslist has worked for me too.

I wish I had a better answer for you.

Hi Carl
Thanks for the reply, I think your correct about if MSwindows is 32 or 64 bit, most P/C and laptops are 64 bit and crashes for the editor seems to crash very easy then if using a older P/C using a 32 bit XP version

I have tried to install earlier versions of .NET, VS and Vbasic runtimes but news MSwindows do not support older versions

I assume people who are using older versions of the Tunercat OBD-II editor have less problems, I use whatever newest updates found on
Tunercat website is at V 3.55

I used to have problems also with the Winflash but John had come out with a Winflash for the dealers kit which was written few years back and
is coded to work on newer MSwindows, version 4.25 and zero issues with that version but for whatever the reason Tunercat says they cannot find
the problem as for the editor crashing in different ways :-(

I have to assume as you did that when the editor was first written it was complied for older .NET and VB which does not work correctly with newer versions of those 2 MS programs.

This is really bad as if I do not keep saving as I make tune changes and editor crashes then I loss all the changes and time I had done and have to start over again so was hoping some other Tunercat owners have found some workaround or band-aid to solve this :-(

Yet as I mentioned sometimes the editor crashes saying no free memory when task manager shows 10 gigs free or crashing saying the client has disconnected
and when I am custom tuning my P/Cs or laptops are set to have minimum programs or DLLs, etc running in background and they are set for best performance which limits 40 or less MSwindows processes running :-(
I see no reason if CPU is 3 Ghz or more and multi processors should crash when using a small program like the editor


Problem is I use other programs like a professional OBD I/II scanner and it will not work on Win XP and older laptops do not support newer windows and caps off with maximum 3 Gig of memory or do not have enough USB ports

Thanks

[NISANDA]

i have same problem, gets even worst with new car\truck .Cal files.

[teamzr1]

i have same problem, gets even worst with new car\truck .Cal files.

When Tunercat OBD-II tuner came out around 2002 GM flashes in most cases were only 512K bytes and that was for PCM and auto tranny
Now GM calibrations are like 4 mg bytes and that is each for PCM and TCM

I suspect early on they coded software for a much smaller free working memory space and now runs out of that memory space

Another problem I do not know if it is the runtime for VB or .Netframe used in 2002 but editor program is not compatible with either them for newer versions
of those MSwindows programs

Cannot get anyone to get involved to at least get some workaround and I have lots of money spent in all the VDFs I have bought since 2002 :-(

So was hoping others here find ways to resolve these hard crashes.

[steveo]

if you run software that doesn't work on newer computers, virtualization is what you're looking for. install windows XP 32 bit in a virtual machine and install the software there. the software to do that is free (google virtualbox). you can run operating systems within operating systems, and your 'guest' operating systems are pretty much isolated from your real computer. modern processors have virtualization instructions that make this type of emulation very fast.