PCWH Version 4.041 Crashes during install

dyeatman · Joined: 06 Sep 2003 Posts: 1934 Location: Norman, OK

I just downloaded (three times) and tried to install PCWH 4.041 and it crashes during install every time in windows XP. Version 4.040 installs/re-installs with no problem. Anyone else seeing this? I reported it to CCS.

rdburghard · Joined: 01 May 2007 Posts: 5 Location: Jackson, MS

Yes, I have done the same thing today. I have also left an email with CCS support. I am trying to update from version 4.039. The utility file will install but the pcwhupd.exe file crashes. I was thinking that the problem was because I just recently renewed my yearly subscription and this is the first time I've tried to install since then, but that might not have anything to do with it. If I figure it out or they tell me something, I'll leave a post.

picport · Joined: 01 Jun 2007 Posts: 7

Exactly the same problem with me this morning. I also tried to download it a couple of times, but it still crashes when the blue install screen opens. Reported also to CCD Support.

Bill Havins · Joined: 20 Nov 2006 Posts: 14 Location: Texas

Same experience here.

Cheers!

Bill

Darren Rook · Joined: 06 Sep 2003 Posts: 287 Location: Milwaukee, WI

Try it now.
_________________
I came, I saw, I compiled.

dyeatman · Joined: 06 Sep 2003 Posts: 1934 Location: Norman, OK

That seems to have fixed it.

Darren:
Version 4.041 copied over my reg files during the install then told me my reg files were too old when I started 4.041. Good thing I learned a long time ago to keep backups! I copied them back to the PICC directory and 4.041 is now working properly.

A warning to everyone... be sure you have backups of your reg files before installing 4.041!!!

Thanks for the help Darren.

Darren Rook · Joined: 06 Sep 2003 Posts: 287 Location: Milwaukee, WI

That's odd about your REG files, I could not recreate that. However I believe the install process generally copies CRG files from certain directories during an install and I don't think's any different in 4.041.
_________________
I came, I saw, I compiled.

dyeatman · Joined: 06 Sep 2003 Posts: 1934 Location: Norman, OK

Which directories would that be? That may be what is happening here. If I can find out which one(s) I might be able to avoid this in the future.

Dave

JIMA · Guest

Like a good engineer I keep backups of ALL of my machines.

But I to have had a 4.041 install problem.

I will as suggested, try again today (SAT).

I hope they fixed the ICD-U40 issue in this version.

It seams to me that CCS has had some version testing problems in the last four months, I wonder if a key person has left the company or if they have had too much on the engineers plates lately?

Jim Ashby, TX, USA, Texas · Guest

It appears as the 4.041 install is up and running, but the ICD-U40 issue is not fixed. UGH!

Not a happy camper.

Katsuhiro · Guest

I haven´t that problem, probably it´s a register failure thing. I´m a new costumer from Japan and my regfiles are new. I hope CCS have not to many bugs ... My reference number is in this format: XXXXX-2-XXXXX yours is like that??

best regards.

Argentum · Guest

Hi Katsuhiro!

I´m a recent user too, well my teacher at the universtity and he has a reference number like you: *****-2-***** , I supose it´s a rule from CCS to name his recent costumers dont you think??

I was wondering what i have to do to be a beta tester from PCD, my user and reference number can´t access to beta tester section in CCS webpage.

best regards from Argentina.

Ttelmah · Guest

If you are running the latest version, you _are_ a 'beta tester'.
Unfortunately, CCS, do not have any idea of what a 'beta' is. They ran a 'beta' program for a while at the launch of V4, but put the product onto the market, while the 'beta testers', were still telling them it didn't work (it would not even make 'alpha' status in any normal company...).
It took about 30 releases (and another 6 months or so), before the product became a useable 'release candidate'.
It has only been the last couple of months, where the new compiler has been really 'useable', and though now, many of the new features ae working, as has been common in the past, they tend to fix one bug, and create another.
'Long time' CCS users, always consider the latest version to be a 'beta', till it has been used for a few weeks.

Best Wishes

inservi · Joined: 13 May 2007 Posts: 128

Hello Ttelmah,
You are right ! unfortunately 'CCS technical support' dont like that someone expose this kind of problem as you can see in this topic (at the end)
Razz

http://www.ccsinfo.com/forum/viewtopic.php?t=30961

dro.
_________________
in médio virtus

PCM programmer · Joined: 06 Sep 2003 Posts: 21708

But in that specific case, the person says he is losing thousands of
dollars, but he doesn't even have one spare debugger unit.

We're a small company and we have two ICD2 units, plus I have another
one at home that I own. We will never have a problem in which all
development is shutdown and we're "losing thousands of dollars" due
to a bad debugger. We have spare units.

It's just almost unbelievable that he let himself get into that situation.

At a minimum, if he's going to use CCS tools, he should own two
ICD-U40 units, and only upgrade the firmware on one unit at a time.
If the new firmware fails, then he has his other unit that still works,
and he can keep going. If you're just doing development as a hobby
then having one debugger is fine. But for a professional, you must
have backup units.