Electronics > Projects, Designs, and Technical Stuff

Codewarrior V4.7 can no longer load projects

<< < (3/4) > >>

AndersJ:

--- Quote from: donotdespisethesnake on January 07, 2020, 10:49:03 pm --- the NXP forums or support are the place to look.

--- End quote ---

No response from NXP forums.
The NXP support responds that V4.7 is no longer supported.
No attempt to understand, discuss or resolve the problem.

donotdespisethesnake:

--- Quote from: AndersJ on January 08, 2020, 07:33:42 am ---
--- Quote from: donotdespisethesnake on January 07, 2020, 10:49:03 pm --- the NXP forums or support are the place to look.

--- End quote ---

No response from NXP forums.
The NXP support responds that V4.7 is no longer supported.
No attempt to understand, discuss or resolve the problem.

--- End quote ---

I was thinking more of peer support. I did get some useful help with running CW on Windows 7, a user provided patches and instructions.

For official support, raise a ticket. Though, since the age of the product and the NXP takeover, there may simply be no one at NXP who knows anything. Maybe now is the time to migrate to a newer tool? Sure that takes some effort, but everything has a lifetime, and waiting until it no longer works can result in nasty surprises.

And it is still nothing to do with Java!

RoGeorge:
To keep old software working over long time (years or decades), I use virtual machines (offline, and with clock not synchronized with the host machine).  HDD space is too cheap nowadays, and life is too short to waste time with countless software updates or toolchains migrations.  Keeping backups, installation kits, or using containerization won't cut it over many years.

Sometimes we even used dedicated laptops (with only the OS and the configuration software of some industrial equipment for power plants) kept off, locked in a storage room (and never online when powered).

Also, I avoid at all costs online services/tools, or any other form of 3rd party dependency.  This is impossible to do in a large company, but for very small companies (or for individual work) is the only way to go.

AndersJ:
I found the problem, sort of.

Microsoft updated Windows twice in mid december.
I removed the two updates and Codewarrior worked again.

I then asked Windows to reinstall all available updates.
After that, Codewarrior continues to work.

Thanks for your feedback.

filssavi:
Glad you sorted it out  ;D

However if I can just give you an advice as a friend, if you are not in deadline pending mode really try to update to a newer version of the tool.
It might seem a waste of time (re-learning the UI and workflow) however the software you are using is a ticking timebomb, it is just matter of time until it will stop
working for good. You will not get any support from nxp (probably not even if you want to pay for it), since i suspect would rather loose a customer rather than continue supporting a legacy software
from 10 years ago. Since surely no one remembers how the thing worked internally, the build systems are no more and they might even have lost/thrown out the source code in the acquisitions.

You can probably keep the thing running in a VM on an old unpatched OS etc but seriously evaluate how much time you will need to set up and constantly mantain such a fragile system

Bottomline if you are forced to mantain such a legacy system ( if you work in aerospace for example) I feel your pain, otherwise consider updating to a slightly less obsolete software

Navigation

[0] Message Index

[#] Next page

[*] Previous page

There was an error while thanking
Thanking...
Go to full version
Powered by SMFPacks Advanced Attachments Uploader Mod