Do they claim it works?  In theory, it might work.

You would have to sync first with pruning disabled and then run Armory until it is up to date.

After that pruning should be OK, unless Armory falls far enough behind.

Well yeah, that's an inherent problem with pruning.

Having said that, Armory builds up its own database, so if that is enabled, it could still be ok.  Though, that defeats a lot of the benefit of pruning.

There are ways to make pruned Core nodes work with Armory but that's not an item on the list at the moment, so no point speculating.

I tried to update my offline Armory 0.92.3 with "armory_0.93.2_winAll.exe" (32- and 64-bit) but Bitcoin Armory Setup is telling me "You cannot install this version on a 32-bit sytem". Why?

Thank you.

Yes no problem at all.

i'm on win 7 64bit. all is working well including the offline wallet.

@philipma, if you need any help or questions with offline storage & armory stuff, you can pm me.

Yes, although online Armory must be on a 64-bit system when using Ubuntu.

Hire a wretchedly expensive consultant who knows what they are doing. Maybe someone who is knowledgeable about bitcoin and gets paid insane amounts of money for endorsing bleeding-edge cryptographic hashing equipment and algorithms.

My armory breaks down every time I start it. Or better: as soon as it is connected to BitcoinQT (while organziing blockchain). I have the latest version of BitcoinQT and Armory. It was everything ok for weeks. But today it happend EVERY time (I tired at least 10 times, reboot, ...) I have a mac.

Any hint what I should do? Rebuilt blockchain? Reinstall Armory?

Those are the first lines of the error report:

rocess:               Python [822]
Path:                 Applications/Armory.app/Contents/MacOS/Python
Identifier:            com.armory.armory
Version:               
Code Type:             X86-64 (Native)
Parent Process:        [1]
Responsible:           Python [822]
User ID:               501

Date/Time:             2015-08-01 22:47:16.836 -0700
OS Version:            Mac OS X 10.10.4 (14E46)
Report Version:        11
Anonymous UUID:        0342B016-FFD5-109B-1719-DF5FD2B7FFA6

Sleep/Wake UUID:       A3F7E20C-0AA7-44AD-8CD9-7D44B0AF6A3F

Time Awake Since Boot: 2400 seconds
Time Since Wake:       1300 seconds

Crashed Thread:        8

Exception Type:        EXC_BAD_ACCESS (SIGBUS)
Exception Codes:       0x000000000000000a, 0x0000000ae461e001

VM Regions Near 0xae461e001:
    MALLOC_LARGE           0000000adde02000-0000000ade103000 [ 3076K] rw-/rwx SM=PRV 
--> mapped file            0000000ade103000-0000000ae64c9000 [131.8M] r--/rwx SM=PRV Users/USER/Library/Application Support/Armory/*
    MALLOC_LARGE           0000000ae64c9000-0000000ae67ca000 [ 3076K] rw-/rwx SM=PRV 

Thread 0:: Dispatch queue: com.apple.main-thread
0   libdispatch.dylib                0x00007fff8b59f7f8 _dispatch_queue_wakeup_with_qos_slow + 1075
1   com.apple.coreui                 0x00007fff8d155bed PerformBlockWithThemeRegistry + 102
2   com.apple.coreui                 0x00007fff8d155e7e _LookupThemeProvider + 232
3   com.apple.coreui                 0x00007fff8d1391e1 -[CUIThemeFacet _approximateRenditionForRenditionKey:] + 109
4   com.apple.coreui                 0x00007fff8d13e706 -[CUIThemeFacet imageSize] + 83