Logos 4 on a netbook: need more flexibility in indexing process

While I have been happy with Logos 3 on my Netbook for quite a while, the time is coming when no new books will be available for Logos 3 so the time is ripe to move to Logos 4.

Problem is, the indexing process is just not flexible enough to cope with my netbook. There is just so much "stuff" these days that programmers insist on pushing onto drive C: that I only have 6GB if free space on drive C: and I would have to delete a lot of software to get much more. I am trying to install Logos 4 to an external hard drive U: which has most of its 500GB I can devote to Logos 4. But the indexer cannot get past 30% in first time indexing without running out of space on drive C:

If only the user had teh choice offered by some software companies (such as Corel) as to which drive should be used for temporary work space, I could tell it to use the vast expanse of drive U:

If it cannot get past 30% with 6GB free of the 30GB drive C: there seems to be no way do a first time index (or to ever re-index) unless I reconfigure the entire computer to expand drive C:

There would seem to be two possible solutions to avoid spending a week or so manually reconfiguring the entire system (for any of us with similar issues):

Provide a software option to use the drive with the most free space on which to do the indexing (user controlled ?)
Provide an option to avoid doing indexing altogether on a netbook and instead to copy the latest completed index from a (latest and greatest fast multicore) desktop having the same books and license.

Until then Logos 4 seems like it is not going to work for those of us with a large library and other uses than just Logos for the netbook.... [:(]

Anyone have any other solutions ?

Find more posts tagged with

Comments

Tom

Problem is, the indexing process is just not flexible enough to cope with my netbook

Sorry to say that I too had to delete a lot of programs to install Logos 4, I then reinstalled them after the very long indexing process. But I have large Lib and I just use the Netbook for Logos4, and sermon prep using MS Office. [:D]

Don´t have room for many more. [:'(]

A solution like you suggested might be worth looking into. [Y]

Bradley Grainger (Logos)

I am trying to install Logos 4 to an external hard drive U: which has most of its 500GB I can devote to Logos 4. But the indexer cannot get past 30% in first time indexing without running out of space on drive C:

If you install Logos 4 to U: (by changing the install path when first installing the app), it should store all of its files and create all of its working data on U:. (There may be small amounts of temp space on C: used for some operations, but this would be a few megabytes at most.)

If your drives are formatted with NTFS, you can move (parts of) an existing installation by using the mklink command; see here for details: http://community.logos.com/forums/p/24948/185112.aspx#185112

David Wilson

https://community.logos.com/discussion/comment/334143#Comment_334143

Hi Bradley: What you describe is how I had hoped it would work.

Can you help me understand the attached logs so that I can make some progress on the Netbook ?

My external U: drive is a WD 500GB still formatted as it came as FAT32. Drive C: is NTFS

Many thanks [:)]

3060.Logos4IndexerError.log

8750.Logos4IndexerCrash.txt

Bradley Grainger (Logos)

https://community.logos.com/discussion/comment/334167#Comment_334167

Can you help me understand the attached logs so that I can make some progress on the Netbook ?

On the face of it, these logs don't make sense. The crash dump says there's >280GB free (on the U: drive, which is where Logos 4 is storing its data) at the time that the "There is not enough space on the disk." error occurs.

Furthermore, the Logos 4 Indexer is designed to avoid this kind of fatal error. It constantly checks for <1GB of free space and shuts down gracefully (with an error message dialog) if that is detected.

However, at the top of Logos4IndexerError.log, there is the curious line "Free disk space: 0 MB". This makes me wonder if your external drive has an intermittent error where it reports to Windows that it's completely full. If that's the case, it's likely to fail to write data (at arbitrary times) and cause the "There is not enough space on the disk" error that's crashing the indexer. Unfortunately, I don't know how you could work around such a problem; it seems like a hardware failure with the drive itself.

Bradley Grainger (Logos)

https://community.logos.com/discussion/comment/334167#Comment_334167

My external U: drive is a WD 500GB still formatted as it came as FAT32.

I just remembered: FAT32 is not supported as a drive format for Logos 4 data storage, because Logos 4 needs to create individual files that are larger than 4GB (unless your library is very small). You will have to reformat or convert the drive to NTFS in order to use it with Logos 4.

David Wilson

https://community.logos.com/discussion/comment/334803#Comment_334803

The FAT32 limit makes sense. This is a new external HD and I suspected the drive hardware problem with an older drive earlier in the process of trying to get set up this way. When the new one had indexer crashes for the same reason at pretty much teh same % completed, I came back to a software issue being the problem. [:S] Will reformat to NTFS and see how we go with that. Thanks Bradley. [:)]

David Wilson

https://community.logos.com/discussion/comment/334803#Comment_334803

You will have to reformat or convert the drive to NTFS in order to use it with Logos 4.

SUCCESS [:D]: took all weekend and part of Monday to do the indexing, but with the external hard drive reformatted to NTFS no more indexer crashing and it is indexed successfully !! Thanks Bradley. The netbook may be slow but it is useable !! [:)]