It has been a year (almost) since the thread concerning the strange symbols in the Alias tree; they seem to come about with W98SE and IE5. Has anyone discovered the facts or a fix or are you all just living with this frustrating situation? I have to rename all my symbols write them down and then change them back and compare the list in order to use the right ones - AAAgggh! I can't believe you really smart people have not "made the fix" so come on, let me in on it!
Ric

This was solved a long time ago, as you would have discovered by reading the FAQ.

You need to upgrade from IE5.0 to IE5.01.

However, beware of IE5.5 as the problem has resurfaced (and is actually worse). There is no problem with IE5.5 and Windows 2000.

Ric,
Go to this thread:

[Link: remotecentral.com]

The COMCTL32.dll file for IE5.01 is necessary to fix the font problem. Follow my instructions that are found within the thread for replacing the file properly.

It is THE fix for the problem.

Luke

First off Peter, thanks for the response but I not only read the FAQ but downloaded them from this site as well. I didn't see the answer to my qestion there. I did a search on the site and came up with the older '99 thread - thus my question.

People come to Pronto new every day and it is hard to absorb all of the collective wisdom of the community in a short time - so thanks for the attitude.

Secondly, Luke thanks for the solution your thread provided, I wouldn't have asked had it come up in the search. Also it was dated if I read it correctly "O8/00" which would be last month so I don't think the "long ago" rap of Peter's was fair. It seems your most excellent solution was not only correct but rather recent.
Thanks Ric

Sorry, Ric. Your original post sounded as though you were an 'oldie' who came across the problem a year ago and was now looking again for an answer. Your later post suggests the opposite, and that you did the right thing by searching the site first and also reading the FAQ.

Luke was referring to the IE5.5 problem which is recent (last month).

You were originally referring to the IE5.0 problem which is quite old and covered in section B11.05 of the FAQ.

Peter,
The problem with the FAQ was that it never actually solved the problem. It suggested that IE 5.01 was the fix, however, to the unfortunate few like myself who had already installed a beta version of IE 5.5, going back to 5.01 was not an option. Without knowing which particular file within IE was the culprit, we were left without a true cure.

Brandon B and I tried to determine what .dll files were common between prontoedit and IE. We found that COMCTL32.dll was the weak link. Some people may even have IE5.01 on their machines and still exhibit the problem if another program had loaded an updated version of COMCTL32.dll. Therefore, IE may not always be the cause and the old FAQ is rendered worthless.

However, I am always glad to see people like yourself take the time to answer the questions in this forum. Sometimes our writing styles make us come across with a bad attitude, but I believe your intent was to help and not belittle.

Luke

Has anyone figured out if replacing the "new" file with an "old" version does anything else? I mean they must have changed it for a reason (not the bug, but other things).

I had only used it for one month before upgrading to Windows ME (which BTW causes the problem again, argh). During that time, I experienced no ill side effects.

I've had this problem also for over a year and none of the solutions have fixed it, including the most recent comctl32.dll fix. I was really hopeful about that one, but no dice. The comctl32 that I had was the exact same size and the "fixed" one. Hum.
I suspect there's something really subtle going on that causes the "fixes" to work for some and not others. BTW I run pontoedit on Win98.

Jeff,
If you haven't already, just for grins, download the COMCTL32.dll listed in the thread: [Link: remotecentral.com]

While booted to DOS, Copy the file to both C:\Windows\System and C:\Windows\Sysbckup. Also, make sure there are no other versions lying around in other directories which could possible cause problems.

Since you've already checked that the files are the same, its a long shot. But the problem is annoying enough to take desperate measures. :^)

Let us know how you make out, I really feel as though COMCTL32.dll is the only culprit.

Luke

Peter,
I would like to agree with Luke. After going thru a lot of threads where you were helpful, I feel I may have misunderstood. The very fact that people who are more experirenced will give time and effort to help others really says something about the pronto community and especially this site! [Thanks Dan]

Luke's fix worked like magic for me - but I was a little surprised that I couldn't find a 'copy' of the offending file in 'sysbckup.' It appears that I only had one copy.

I have always tried to download the updates to windows and IE as soon as they become available - guess I'll have to think twice about it
Ric