Hey, James.

I was unable to achieve 1st launch on my G5 dual 2 ghz. Launch gets QRecall "Quick Start" dialog and menus, but spinning cursor. Allowed 10 minutes.

2 subsequent attempts met with same result. No updating to log occurred.

OS 10.4.8

Machine Name: Power Mac G5
Machine Model: PowerMac7,2
CPU Type: PowerPC 970 (2.2)
Number Of CPUs: 2
CPU Speed: 2 GHz
L2 Cache (per CPU): 512 KB
Memory: 1.5 GB
Bus Speed: 1 GHz
Boot ROM Version: 5.1.4f0

1.5 gigs RAM

1 internal HD:
Serial-ATA Bus:

ST3160023AS:

Capacity: 149.05 GB
Model: ST3160023AS
Revision: 3.05
Serial Number: 3JS1YAK9
Removable Media: No
Detachable Drive: No
BSD Name: disk0
Protocol: ata
Unit Number: 0
Socket Type: Serial-ATA
Bay Name: "A (upper)"
OS9 Drivers: Yes
S.M.A.R.T. status: Verified
Volumes:
Macintosh G5 HD:
Capacity: 149.05 GB
Available: 8.96 GB
Writable: Yes
File System: Journaled HFS+
BSD Name: disk0s9
Mount Point: /

1 External Firewire HD:
External HDD Button & Lights:

Manufacturer: WD
Model: 0x0
GUID: 0x90A990E011379D
Maximum Speed: Up to 400 Mb/sec
Connection Speed: Up to 400 Mb/sec
Sub-units:
External HDD Button & Lights Unit:
Unit Software Version: 0xCE0002
Unit Spec ID: 0x90A9
External HDD Device Unit:
Unit Software Version: 0x10483
Unit Spec ID: 0x609E
Firmware Revision: 0x100
Product Revision Level: 106a
Sub-units:
External HDD Device SBP-LUN:
Capacity: 298.09 GB
Removable Media: Yes
BSD Name: disk2
OS9 Drivers: Yes
S.M.A.R.T. status: Not Supported
Volumes:
NapAlp Backup:
Capacity: 297.96 GB
Available: 297.88 GB
Writable: Yes
File System: Journaled HFS+
BSD Name: disk2s10
Mount Point: /Volumes/NapAlp Backup

QRecall log:

2007-03-05 11:08:38 -0500 [5522] Details Installed link to QRecallBundledHelper
2007-03-05 11:08:38 -0500 [5522] Details Installed link to QRecallScheduler
2007-03-05 11:08:38 -0500 [5522] Failure Cannot connect to scheduler
2007-03-05 11:08:38 -0500 [5522] Details Updating QRecallScheduler jobs in user crontab
2007-03-05 11:08:38 -0500 [5522] Details Installed link to QRecallMonitor.app
2007-03-05 11:08:39 -0500 [5522] Installing QRecallMonitor.app in user login items
2007-03-05 11:08:39 -0500 [5526] Failure Unable to register connection (QRecallMonitor)

Hello Steven,

A couple of questions:

- Did you first copy the application into your Applications folder or did you launch it from the disk image? (QRecall is designed so that it shouldn't matter, but maybe it does.)

- Are you using FileVault?

- Launch Activity Monitor, set it to show All Processes, then enter "QRecall" into the search field (without the quotes). Are there any processes listed?

- Are there any related messages in the system or console logs?

James Bucanek wrote:- Did you first copy the application into your Applications folder or did you launch it from the disk image? (QRecall is designed so that it shouldn't matter, but maybe it does.)

No, I copied to the Application folder as you explain to do in your notes. (I always follow the rules in Betas )

- Are you using FileVault?

No.

- Launch Activity Monitor, set it to show All Processes, then enter "QRecall" into the search field (without the quotes). Are there any processes listed?

Don't really need to enter any more than QR. Here's the result:

340 QRecallScheduler alper 0.00 1 6.55 MB 27.63 MB
643 QRecall (Not Responding) alper 0.00 7 23.76 MB 242.55 MB
645 QRecallMonitor alper 0.00 4 13.50 MB 215.07 MB

- Are there any related messages in the system or console logs?

I don't see anything different today than yesterday:

2007-03-05 11:08:38 -0500 [5522] Details Installed link to QRecallBundledHelper
2007-03-05 11:08:38 -0500 [5522] Details Installed link to QRecallScheduler
2007-03-05 11:08:38 -0500 [5522] Failure Cannot connect to scheduler
2007-03-05 11:08:38 -0500 [5522] Details Updating QRecallScheduler jobs in user crontab
2007-03-05 11:08:38 -0500 [5522] Details Installed link to QRecallMonitor.app
2007-03-05 11:08:39 -0500 [5522] Installing QRecallMonitor.app in user login items
2007-03-05 11:08:39 -0500 [5526] Failure Unable to register connection (QRecallMonitor)
2007-03-06 08:26:19 -0500 [643] Installing QRecallMonitor.app in user login items
2007-03-06 08:26:20 -0500 [645] Failure Unable to register connection (QRecallMonitor)

I can't find anything in other logs or console messages.

Best,

Steve Alper

Steven M. Alper wrote:Don't really need to enter any more than QR. Here's the result:

340 QRecallScheduler alper 0.00 1 6.55 MB 27.63 MB
643 QRecall (Not Responding) alper 0.00 7 23.76 MB 242.55 MB
645 QRecallMonitor alper 0.00 4 13.50 MB 215.07 MB

I'm pretty sure I know what the problem is, I just don't know what's causing it. I think the QRecallMonitor is hung and when QRecall goes to talk to it it gets hung up too.

In the Activity Monitor, Quit or Force Quit the QRecall Monitor process. See if this shakes the main QRecall application loose. If that works, hold down the Option+Shift keys and select QRecall > Quit and Uninstall, then relaunch QRecall.

Are you, by any chance, upgrading from an earlier version of QRecall?

Do you have any haxies or other UI goodies installed?

James Bucanek wrote:I'm pretty sure I know what the problem is, I just don't know what's causing it. I think the QRecallMonitor is hung and when QRecall goes to talk to it it gets hung up too.

I've got Activity Monitor listing process by CPU usage and I can see QRM move above QRecall after QRecall locks, which would seem to indicated that QRM is not hanging first -- although I have no idea how far behind Activity Monitor is lagging.

In the Activity Monitor, Quit or Force Quit the QRecall Monitor process. See if this shakes the main QRecall application loose. If that works, hold down the Option+Shift keys and select QRecall > Quit and Uninstall, then relaunch QRecall.

Wow, that took more speed and dexterity than I'm used to, since QRM relaunched so quickly.
Tried that and was able to get to the "Quit & Uninstall" item before QRM relaunched. However, relaunches of QRecall behaved the same as previously. (I tried it three times.)

Are you, by any chance, upgrading from an earlier version of QRecall?

Was the beta even public before this? No, I just heard about it for the first time yesterday at VersionTracker.

Do you have any haxies or other UI goodies installed?

What kind of Mac user would I be if I didn't!
I've got Application Enhancer running (for Detour and Instant Hijack Server - audio redirect applications, both from Rogue Amoeba), and the following additional panels:

ATI displays
Déja Vu (always disabled)
Diablotin (a manager along the lines of pre-OS X Extensions Manager)
Digidesign Mbox
DivX
FinderPop
Flip4Mac WMV
Growl
Mouseworks (Kensington)
StuffIt AVR

I'm going to see what happens with APE disabled. Will let you know....

Best,
Steve

Well, it seems to be APE that's the culprit. QRecall runs fine with it disabled. (And it's pretty!)

With APE running, QRecall hangs, even when the application appears in APE's exclude list.

Is there some info I can provide to help you work around this problem? I think APE has a large enough user base where it's important that you find a way to co-exist.

Unsanity asks to be notified of these kinds of conflicts and I'd be happy to do so if you'd like.

Best wishes,

Steve

Steven M. Alper wrote:Well, it seems to be APE that's the culprit. QRecall runs fine with it disabled. (And it's pretty!)

That's good news — from a debugging standpoint, at least. I'll set up a partition, install APE, and see if I can reproduce the problem here. Hopefully, there's a simple fix.

Thanks for being so patient.

James:

Many apologies for the delay, but I was out-of-town far longer than expected and wasn't set up there to test.

At least as of the current beta (39) -- along with the current version of APE -- problems seem to be resolved. I've got my first capture in process at the moment and all seems well. I even set up an Action with the capture in process.

One note: When I attempted to run the capture at first, QRecall complained that there was no valid Identity Key. I picked up a fresh ID Key at your site, but when I checked in the preference pane an Identity Key already appeared there and was grayed out. Normally grayed out text implies that a text area is off limits, so it wasn't until I flipped around the program for awhile and returned to the ID Key pane that I even tried entering the text area for the new key. Of course it worked, but you might want to rethink the gray text. (I'm guessing you're set up for the future when the keys will be more or less permanent.)

Thanks!

Steve

Steve,

No problem -- I'm just glad thinks are working now.

Beta identity keys are permanent. The beta application itself will expire, but your identity key won't.

The only thing that should cause you to lose your identity key is if you lost the preference file/folder where your identity key is stored. The self-uninstall procedure (Command+Option+Shift+Q) should not delete your key, but performing the manual uninstall instructions found in the advanced topic of the help will. If you performed the manual uninstall in an attempt to diagnose your earlier problem, that would definitely erase your key. Identity keys are also user specific, so running QRecall from another user account or from a different boot volume will require that you reenter a key. Note that if you are running QRecall from multiple accounts on the same machine you can enter the same identity key for all of those users, or use a different identity keys to keep the data captured by each user separate.

And I agree that the identity key entry screen is confusing. Apple added "default text" to text entry fields recently and I used that to display a sample identity key. However, Apple's method of displaying the default text (i.e. the value of the field if you don't enter anything) is to draw it dimmed. I've had two individuals think that there was already an identity key entered, and two more now that thought the field was disabled.

I'll probably replace this with a prompt or simply leave the field blank in the next version.

Thanks for the feedback.