Logos on USB flash iii
would it be an idea to run logos on something like this http://www.bestbuy.com/site/sandisk-ultra-fit-128gb-usb-3-0-type-a-flash-drive-black-silver/9208221.p?skuId=9208221
Note: best I can tell, i have 60 gig in my Logos library
Comments
-
I run logos on my Surface Pro from a Lexar 128g. It isn't super fast but it works.
0 -
Josh Hunt said:
would it be an idea to run logos on something like this ...
Logos wiki => Install in different folder or drive includes
- Unsupported and NOT recommended by Faithlife, see Relocate your Resources folder for relocating ~ 80 % of storage used while minimizing external drive interface issues
Caveat: personally am using USB on a MacBook Air for Resources folder storage, which recently included USB drive replacement as previous USB became unusable (from too many hard knocks during various travels).
Keep Smiling [:)]
0 -
If you are going to run Logos from an USB memory stick, at least get a fast one.
The typical USB flash memory uses what is called Multi-Level Cell (or sometimes Triple-Level Cell) flash memory, but there is also Single-Level Cell flash memory. MLC/TLC memory is much slower compared to SLC. MLC/TLC also has a shorter lifespan than SLC by a factor of up to 10x. There are lots of articles out there describing the differences in more detail - Google "slc vs. mlc" or equivalent.
The downside to SLC USB memory sticks is 1) they are not readily available in the US (you have to hunt for them - the one shown below comes from Taiwan), and 2) they are more expensive than MLC/TLC.
Although I am not running Logos from it, I have one of these (in a 32GB size, not 64GB) and I can confirm my speeds exceed what they have published as measured by ATTO (USB 3.0 port). For comparison I have also shown speeds for a typical Lexar 32GB USB memory stick.
Instead of Artificial Intelligence, I prefer to continue to rely on Divine Intelligence instructing my Natural Dullness (Ps 32:8, John 16:13a)
0 -
If you have USB 3 or 3.1, your fastest option would be something like this:
https://www.amazon.com/ADATA-SV620-240GB-External-ASV620-240GU3-CTI/dp/B01IP6STJY/
0 -
I'm sure everyone that has commented already knows this, but in case anyone that comes across this thread doesn't, we do not support installations to removable media like SD cards, flash drives, or externally connected disk drives (spinning drives or solid state).
0 -
Tommy Ball said:
I'm sure everyone that has commented already knows this, but in case anyone that comes across this thread doesn't, we do not support installations to removable media like SD cards, flash drives, or externally connected disk drives (spinning drives or solid state).
I didn't know that; thanks
0 -
-
Tommy Ball said:
I'm sure everyone that has commented already knows this, but in case anyone that comes across this thread doesn't, we do not support installations to removable media like SD cards, flash drives, or externally connected disk drives (spinning drives or solid state).
I run Logos from a 64 GB microSD card in my Dell Venue 8 Pro tablet because the design decision Faithlife made requires all resources to be downloaded into your Logos installation. I would love to run Logos from the internal eMMC of this tablet, but my Logos installation is about 33 GB and there is no room left (I have tried, trust me). So, Tommy, a better solution for the future is to allow users of the Windows desktop app to select on a per-device basis which resources to include in the installation. Then, I could run Logos from my internal drive and also have Logos offer support for my installation. Then we'd both be happy [:)].
0 -
Bill Anderson said:
I run Logos from a 64 GB microSD card in my Dell Venue 8 Pro tablet because the design decision Faithlife made requires all resources to be downloaded into your Logos installation. I would love to run Logos from the internal eMMC of this tablet, but my Logos installation is about 33 GB and there is no room left (I have tried, trust me). So, Tommy, a better solution for the future is to allow users of the Windows desktop app to select on a per-device basis which resources to include in the installation. Then, I could run Logos from my internal drive and also have Logos offer support for my installation. Then we'd both be happy
.so, is it slow running on the sd?
0 -
Josh Hunt said:
so, is it slow running on the sd?
It is slower running Logos off of the microSD than the internal eMMC. When it is indexing, I often cannot use it until it has finished. I try to manage those times so that updates install and index when I am not using it. But aside from that, the system runs OK off of the microSD.
0 -
Bill Anderson said:Tommy Ball said:
I'm sure everyone that has commented already knows this, but in case anyone that comes across this thread doesn't, we do not support installations to removable media like SD cards, flash drives, or externally connected disk drives (spinning drives or solid state).
I run Logos from a 64 GB microSD card in my Dell Venue 8 Pro tablet because the design decision Faithlife made requires all resources to be downloaded into your Logos installation. I would love to run Logos from the internal eMMC of this tablet, but my Logos installation is about 33 GB and there is no room left (I have tried, trust me).
Personally have a MacBook Air (MBA) that does not have enough internal space on 120 GB Solid State Disk (SSD) for my library so am using an unsupported configuration of fast USB 3 drive (128 GB) for resource file storage, which is symbolically linked into my Logos installation. Internal SSD uses 24.4 GB for my Logos application files while USB drive has 72.7 GB of resource files. Using internal SSD for most of my Logos files avoids known USB and SD issues when writing to application database files (including indexes).
Caveat: carrying around MBA with external USB provides opportunity for USB drive to be bumped so am learning to handle carefully. Thankful for USB working after MBA quick exit from car to ground a couple times, including one where USB drive cover split up into several pieces. After more trips around town, that fast USB became unrecognizable to MBA so replaced 245 MB/sec USB with one up to 115 MB/sec that works with similar performance on 2011 MBA (while physically being a bit smaller). Thankful for scan command copying of resource files from my Logos installation on another computer.
Keep Smiling [:)]
0 -
Have you considered a portable SSD? Generally, they're much faster than USB. Go for something like a Samsung T3.
This is my personal Faithlife account. On 1 March 2022, I started working for Faithlife, and have a new 'official' user account. Posts on this account shouldn't be taken as official Faithlife views!
0 -
Personally have a MacBook Air (MBA) that does not have enough internal space on 120 GB Solid State Disk (SSD) for my library so am using an unsupported configuration of fast USB 3 drive (128 GB) for resource file storage, which is symbolically linked into my Logos installation. Internal SSD uses 24.4 GB for my Logos application files while USB drive has 72.7 GB of resource files. Using internal SSD for most of my Logos files avoids known USB and SD issues when writing to application database files (including indexes).
Caveat: carrying around MBA with external USB provides opportunity for USB drive to be bumped so am learning to handle carefully. Thankful for USB working after MBA quick exit from car to ground a couple times, including one where USB drive cover split up into several pieces. After more trips around town, that fast USB became unrecognizable to MBA so replaced 245 MB/sec USB with one up to 115 MB/sec that works with similar performance on 2011 MBA (while physically being a bit smaller). Thankful for scan command copying of resource files from my Logos installation on another computer.
Keep Smiling
How would I do something like you are doing on a Windows installation?
0 -
Bill Anderson said:
How would I do something like you are doing on a Windows installation?
Logos Wiki => Install in different folder or drive includes Move to a different drive for Windows with Resources folder example using junction command.
Keep Smiling [:)]
0 -
Logos Wiki => Install in different folder or drive includes Move to a different drive for Windows with Resources folder example using junction command.
Keep Smiling
I saw this in the wiki. So, if I currently have my complete Logos installation on my microSD card, then would I be moving all of my Logos folder and subfolders EXCEPT for the Resources folder to my C: drive and then using junction to create a symbolic link to that?
0 -
Bill Anderson said:
Logos Wiki => Install in different folder or drive includes Move to a different drive for Windows with Resources folder example using junction command.
Keep Smiling
I saw this in the wiki. So, if I currently have my complete Logos installation on my microSD card, then would I be moving all of my Logos folder and subfolders EXCEPT for the Resources folder to my C: drive and then using junction to create a symbolic link to that?
Yes. Recommend verifying C: drive has adequate space first.
- How much space does Logos folder use ?
- How much space does Resources folder use ?
- How much space does LibraryIndex folder use ?
Does C: Drive have 1 GB or more free space greater than <Logos folder size> - <Resources folder size> + <LibraryIndex folder size> ?
FYI: Library indexing needs enough space to duplicate LibraryIndex folder contents plus 1 GB while merging.
If C: drive has adequate disk space, one option is a variation of => Quick Installation onto multiple computers for new C: installation.
- Move Resources folder out of Logos folder on MicroSD
- Copy Logos folder and subfolders to new C: installation (per wiki quick installation method)
- Use Junction command to symbolically link Resources folder on MicroSD into ResourceManager folder on C: drive (then proceed with remaining method steps)
Note: thought about different steps using registry edit, but found Logos folder path is in many registry keys so new installation would be quicker and safer.
Keep Smiling [:)]
0 -
If C: drive has adequate disk space, one option is a variation of => Quick Installation onto multiple computers for new C: installation.
- Move Resources folder out of Logos folder on MicroSD
- Copy Logos folder and subfolders to new C: installation (per wiki quick installation method)
- Use Junction command to symbolically link Resources folder on MicroSD into ResourceManager folder on C: drive (then proceed with remaining method steps)
This procedure is incomplete and error-prone:
- which "quick installation" method? ---> I assume Method 2
- the current Logos has to be uninstalled before you can have a new installation on C: drive
- Step 2 is technically unsound ---> executables in Logos folder will be different to Registry details.
- Step 3 is misleading ---> it should provide details of the command format for the symbolic link
- What are the remaining "method steps"?
A variation of Method 3 is much safer provided there is enough space on drive C: as stated above.
Dave
===Windows 11 & Android 13
0 -
So, I am at the place of wanting to do this installation. The goal is to run Logos off of the main eMMC but have my Resources folder on the microSD. I have enough space on my internal eMMC to do this.
I have started the Logos installation and chose custom. The first part of the installation was successful. When the login screen appeared, I closed it down.
I have done a method 2 installation numerous times, so I am familiar with those steps.
My microSC card has my previous Logos installation on it when I was running Logos completely off of the microSD.
0 -
Bill Anderson said:
I have done a method 2 installation numerous times, so I am familiar with those steps.
My microSD card has my previous Logos installation on it when I was running Logos completely off of the microSD.
Method 2 (Saves resource downloading and indexing) step 3 becomes: (copy Logos folders without Resources and create a junction for Resources)
- Move Resources folder out of Logos folder on MicroSD: e.g. move to E:\Resources
- Replace E: with your MicroSD drive letter
- If they exist delete the following folders from the new installation and replace them from your backup (on MicroSD)
- \Logos\Data
- \Logos\Documents
- \Logos\Users
- these are the only folders that you need from backup
- Download junction.exe from http://technet.microsoft.com/en-us/sysinternals/bb896768 and save it in C:\Users
- Open a Command prompt e.g. Start > Run > cmd.exe or type cmd in the Windows Search box
- Change directory (cd) to the new installation: cd “C:\Users\John Doe\AppData\Local\Logos\Data\*\ResourceManager”
- Replace John Doe with your Windows user
- If you specified a custom path, then change directory to your customized location of ResourceManager
- Use junction command to create a link to the new location: C:\Users\junction.exe Resources E:\Resources
- Replace E:\Resources folder with your MicroSD path to Resources folder
- Exit (or close) command prompt
Proceed with step 4 of Method 2 (Saves resource downloading and indexing)
After Logos is working, have option to delete Logos folder on MicroSD to free up space.
Keep Smiling [:)]
0 -
Download junction.exe from http://technet.microsoft.com/en-us/sysinternals/bb896768 and save it in C:\Users
The junction.zip download has two executables:
- junction.exe
- junction64.exe
Microsoft Developer Network has more information about NTFS Junction or Directory Symbolic Link => https://blogs.msdn.microsoft.com/aaron_margosis/2012/12/09/using-ntfs-junctions-to-fix-application-compatibility-issues-on-64-bit-editions-of-windows/
Windows 7 and newer include mklink command.
Keep Smiling [:)]
0 -
I completed the installation with the pointer to my Resources folder on my microSD card. The resources were discovered. Now my tablet is indexing and that likely will take a while.
0 -
I just wanted to report back that I have successfully completed this installation with the symbolic link to the Resources folder on my microSD card. I have been running this installation for a week now and there have been no issues. Thanks for your help, KS4J!
Seriously, if Faithlife will not allow us to select which resources to run on an installation with a small internal drive, they should formally support this type of an installation that allows those of us with small Windows tablets to use the desktop app on them.
0 -
Bill Anderson said:
Faithlife... should formally support this type of an installation that allows those of us with small Windows tablets to use the desktop app on them.
There is too much risk e.g. "I just lost my resources", "Junction didn't work". Provided you understand the variables of a non-standard installation format and an SD card it should continue to work.
Dave
===Windows 11 & Android 13
0 -
Bill Anderson said:
Seriously, if Faithlife will not allow us to select which resources to run on an installation with a small internal drive, they should formally support this type of an installation that allows those of us with small Windows tablets to use the desktop app on them.
This would have saved me over $1000 dollars when I had to upgrade my Surface Pro I to a SP4--only because of SSD space.
Making Disciples! Logos Ecosystem = LogosMax on Microsoft Surface Pro 7 (Win11), Android app on tablet, FSB on iPhone & iPad mini, Proclaim (Proclaim Remote on Fire Tablet).
0 -
Bill & KS4J
Many many thanks to both of you. I had a similar problem and this has solved it. Not ideal but what is ideal in this world anyway!
Yep I am smiling as well. [:)]0 -
You need a very fast USB-Stick like the Corsair Flash Voyager GTX 128GB
For fast USB-Sticks see this site: https://ssd-tester.de/usb_stick_test.php
0 -
You need a very fast USB-Stick
This wasn't recommended in 2017 when the thread was created, and it still isn't recommended. Additionally, FL has added the ability to have a "skinny" installation, so users should be encouraged in that route.
macOS, iOS & iPadOS |Logs| Install
Choose Truth Over Tribe | Become a Joyful Outsider!0
said:
