|
Title: Can not write to USB when doing Armory offline transactions Post by: Sophokles on May 27, 2013, 08:32:23 PM Hi,
first of all, I think that Armory is an awesome client, especially the offline- and paper wallet features. Thanks to the developers! But I have a slight annoyance. Like the title suggests, Armory cannot write on USB sticks directly when doing offline transaction, both on online and offline machine. The transaction always has to written on the local disk, and the copied to the USB (Win7 Pro 64, Armory (v0.88.1.-beta_win64 ). I have administrator rights on the account, and I have not encpuntered this problem with any other application. So, is this maybe a bug in Armory? Or what could be done to avoid this? Thanks! Sophokles Title: Re: Can not write to USB when doing Armory offline transactions Post by: Sophokles on May 30, 2013, 12:49:53 PM So no one had this issue besides me? Some Win7 access authorizations settings wrong on my machine? I couldn't figure it out yet, also it is a fresh install of the OS...
Title: Re: Can not write to USB when doing Armory offline transactions Post by: etotheipi on June 01, 2013, 11:55:30 PM So no one had this issue besides me? Some Win7 access authorizations settings wrong on my machine? I couldn't figure it out yet, also it is a fresh install of the OS... You might try formatting the USB key to FAT32. Or NTFS. Or just any reformat. Sometimes, the way the key is formatted causes seemingly-artificial restrictions on I/O. I've seen it on Linux a dozen times. Doesn't surprise me Windows would see the same thing. Title: Re: Can not write to USB when doing Armory offline transactions Post by: Sophokles on June 02, 2013, 12:18:01 AM So no one had this issue besides me? Some Win7 access authorizations settings wrong on my machine? I couldn't figure it out yet, also it is a fresh install of the OS... You might try formatting the USB key to FAT32. Or NTFS. Or just any reformat. Sometimes, the way the key is formatted causes seemingly-artificial restrictions on I/O. I've seen it on Linux a dozen times. Doesn't surprise me Windows would see the same thing. Cool, that sorted it out. Looks like the issue only arises on NTFS formatted sticks, no problems with FAT. Thanks! |