X6 BUGS... List Them Here...

[Joe Carrick]

Mark,

My D:\ProgramData folder is simply where I chose to move the Data Files to. Chief still looks at C:\ProgramData\Chief Architect Premier X6 because I've set up a symbolic link to D:\ProgramData\Chief Architect Premier X6 .

[Dan Park]

I'm looking at resolving the issue and noticed I have some logging information that should show up in our Message Log.txt file.

The Message Log.txt file is located in %AppData%\Local\Chief Architect Premier X6\

I would be interested in the cases where it takes a long time to see what the diagnostic information shows right after Registering Help.
Search for Registering Help and see what the next line says.

Mine looks like this:
2/10/2014 4:41:04 PM 295.190496 Registering Help
Register Help Success!

[Joe Carrick]

Dan,

Without AntiVirus exception

2/11/2014 9:04:06 AM 60.107429 Registering Help
Register Help Success!

With AntiVirus exception

2/11/2014 9:47:20 AM 11.053837 Registering Help
Register Help Success!

Does this help you?

[MarkMc]

I have several instances- all similar different dates
2/11/2014 1:42:20 PM 813.042847 Registering Help
Register Help Success!
Joe I knew you had done the symbolic links- just don't understand why I have it from x5 and not x6- both were default installs.

[gteacher]

Same lines as Mark and Joe, Previous post was a mistake.

[Dan Park]

Awesome! Thanks for the info, at least we are not failing.

Can I confirm with those that are seeing the slowness the following:

1) Open Chief -> launch help -> Takes a long time ~8 - ~60 seconds.

2) Close help -> leave chief open -> launch help -> how long? is it faster? How fast?

[Joe Carrick]

Dan,

Since I excepted Chief Folders from my AntiVirus the Help File Loads within 1-2 seconds every time. It doesn't matter if it's the first time I launch help or not. IOW, the only time it's slow for me is if my AntiVirus is checking the Chief Files/Folders.

OTOH, the Library Files seem to always take 5-7 seconds. I'm assuming that this is due to "Building the Tree". One programming trick that could help that is to only build the top level and one level below initially and then when a branch is opened build the next level below it - if that branch doesn't already exist. While there's no real time saved by doing this way the delays are almost invisible to the user because they are spread out to each subsequent branch opening. Another way might be to simply refresh the Library Browser as soon as the first level or two have been built.

[ambrozac]

......Can I confirm with those that are seeing the slowness the following:

1) Open Chief -> launch help -> Takes a long time ~8 - ~60 seconds.

2) Close help -> leave chief open -> launch help -> how long? is it faster? How fast?

2/11/2014 1:56:08 PM 30.903121 Registering Help
Register Help Success!

1) 30 seconds
2) 18 seconds

[JL DRAFTING]

30 seconds + virtually every time. I don't use the help often, but need it from time to time for sure. I can't follow the folder search stuff you guys are discussing.

[MarkMc]

45-60 seconds, random, no noticeable improvement on second opening

[gteacher]

My behavior -- initial launch -- 35 seconds. Seceding launches - 25 seconds.
Also I am using Nortons and Excluded Chief's directory from Auto Protect -- SONAR - -- Same result

[Dan Park]

Got a repro and and a workaround!!!

We know of a potential fix in the code, we will assess and work it into a future update if it solves the problem.

In the meantime you can try one of the following:

1) run chief as Administrator,

2) install chief in a folder other than Program Files, or

3) turning of UAC for Chief or the system(not recommended).

The problem appears to be related to User Access Control and the fact that we are reading and writing our help files from a folder in the Program Files directory.

[miked56]

Dan - As an extension to this fix it would be great if CA give the users the option to install the files in default locations or in user defined ones.

[gteacher]

To mark an application to always run as an administrator, do the following:
1. On the Start menu, locate the program that you want to always run as an administrator.
2. Right-click the application’s shortcut, and then click Properties.
3. In the Properties dialog box, click the Compatibility tab.
4. Do one of the following:

To apply the setting to the currently logged-on user, select the Run This Program As An Administrator check box, and then click OK.
To apply the setting to all users on the computer and regardless of which shortcut is used to start the application, click Change Setting For All Users to display the Properties dialog box for the application’s .exe file, select the Run This Program As An Administrator check box, and then click OK twice.

You will get the standard "OK to proceed dialog" on start up of Chief -- OK after that -- Thanks Dan

[MarkMc]

1) run chief as Administrator

Woohoo- everything feels snappier-help is fine-fans don't run as often- send to layout quicker- library snaps open