Help with DST jet 14005

I searched for this before posting hopefully it's not a repost.

Just purchased the DST package for tuning a 96 Corvette LT1 turbo car. I'm using Windows 7. Followed the setup instructions installing as an administrator in Windows Service Pack 2 compatibility mode. Everything installed properly. After the drivers had installed I connected the device in it properly set up the drivers. Selected com1. The device I have is usb only. It does not require a hardware serial converter. Once setup it was able to clear dtc without trouble. So, after charging the battery in car for an hour to make sure it's stable I attempted a read. It went about a quarter of the way into the process and asked me to create a file name for the new calibration. They continue for a few more moments only to tell me there was a communication error. Now the vehicle won't start. So now I have no base calibration to even work with or reflash. Having a spare PCM for this car I decided to experiment by downloading the original calibration from this forum. I was able to properly open it up in the jet software. But experience the same communication failure when trying to Flash. Any advice would be great as I'm reading there is very little support from jet.

After resetting the PCM and lowering data transfer rates to lowest setting was able to read calibration from PCM. Nervous at this point about flashing with all the trouble from just a read. :/

if you were reading the calibration and it failed, and now your car wont start, usually disconnecting power from the ecm for a while will bring it back to life

Yes. This is what brought the car back to life. After a reset it would start. Testing every possible transfer rate selection finally got the system working.

Only issue dealing with now is ignition timing is inverted. Asking for say 30* and actually getting -30* reported on my Snap on OBD2 scanner.
The engine struggles to idle. And is very weak on throttle. This car was tuned by another shop and this is the only tune file available.
I've searched every switch, constant, table, etc and cannot find why it would do this. Any advice would be appreciated.

I've resolved the issue. My scanner shows ignition values as negative and positive for advance and retard. All is working well.

I always use a battery charger on those cars. They are old and the connectors rusted, the PCM gets very low voltage because of this.
When you flash it, a low voltage can brick the PCM beyonda recovery by software means.
Make sure battery voltage is high, scan it before flashing to make sure the PCM sees at least 13.0 V
It's very very easy to brick the PCM in those cars and very difficult to recover them.

I have both the old serial cable and USB cable version of Tuner Cat which should basically be the same thing as JET. I used the serial cable version for about 12 years on Win XP laptops and it was rock solid. In flashing probably over 3000 vehicles I think I've bricked 2 PCMs. Now with the USB version on both Win7 and Win 10 laptops it is very unstable. On the Win 10 laptop I'd say it is almost unusable. The editor constantly crashes and I won't dare try to write any PCM with the Win 10 version. When editing with either 7 or 10, I save after every change I make because you never kno when the program will just shut down and you will lose all your changes since the last save. I'v had 2 shutdowns writing with Win 7 but both were on E38 PCMs and TC was able to recover them. I know if I was going to be flashing anything older than a E38 with Tunercat I'm getting out my serial cable and XP laptop. Does anyone know if JET is keeping up with all the updates to the editor and winlash that John at TC does for TC? I know for a while it seemed JET users complained about little to no support from JET.

Jet is not updated as often as TC. They release updates every year or two.
Regardless of that, TC/JET aren't fully compatible with Win7/8/10. It sometimes works, most of the time doesn't.
I was told by TC to use a XP laptop or a XP virtual machine, that TC/JET aren't coded to work with current operating systems and probably never will.

I installed XP to an old dell I had in a drawer and never had an issue again. I also have it running in my Win10 laptop with a XP virtual machine in Virtualbox and works great.

I'll be looking for an older laptop with windows xp to dedicate for tuning with the dst. The editor crashes just like mentioned in 2xls1's post as this PC is windows 7. I'm constantly saving after each change out of fear it will crash. Using a battery charger on the car and only running the flash application during the process seems to work well. Thanks for the tips with this. I've spent lots of time with Hondata and this JET software is like going back to the past.

TC OBD2 aka "JET DST" is fully compatible with 32 BIT VERSIONS OF WINDOWS XP or 7

64 bit = brick city