Page 1 of 2 12 LastLast
Results 1 to 10 of 14

Thread: Verse List Organizer Discussion

  1. #1
    Join Date
    Apr 2004
    Posts
    185

    Default Verse List Organizer Discussion

    At the author's request, the discussion regarding Scott Jone's Verse List Organizer was to be in the non-BibleWorks forum. For the original announcement see: https://www.bibleworks.com/forums/showthread.php?t=3914

  2. #2
    Join Date
    Apr 2004
    Posts
    185

    Default VLO ini files

    I having configuration problems-no ini file.
    --There is no vlo_ini.ini file that I see in my Windows directory.
    --In VLO, Configure/Find ASE file I get the error "Unable To Read VLS INI File"
    --In VLO, Configure/Set VLV Folder I get the error "Unable To Read VLO INI File"

    Perhaps an antivirus or Vista issue, but any ideas how to get around this.

    I even tried to use Notepad to create an empty vlo_ini.ini file in the Windows directory. When I go to save it, the error says contact an administrator. So I saved it to a different directory and copied the file to Windows. Still the same errors in VLO. Any ideas?

  3. #3

    Thumbs up Thanks!

    This looks impressive, Scott. I think I'll just have to start using the VLM so I can use the VLO! There's always more to learn in BWks!

    One question though: is there a BWks minimum version requirement? I'm running BW7, not 8. (I already have .NET 3.5 .) Hopefully nothing changed between versions ...

    (Maybe you could add this info beside the link at the top of your first post in the original thread? It could be a "FAQ"!)

    Thanks!
    David.

  4. #4
    Join Date
    Apr 2004
    Posts
    2,088

    Default

    Quote Originally Posted by Greg Ward View Post
    I having configuration problems-no ini file.
    ... Perhaps an antivirus or Vista issue, but any ideas how to get around this.
    I wouldn't think it's an antivirus issue. It's possible, I suppose.

    If there IS "vlo_ini.ini" file in your Windows folder, try deleting it. If there is not, this is the very first thing VLO creates when it starts for the first time.

    Are you sure you are actually selecting the apppropriate folders by navigating to them and then clicking on the "Okay" button?

  5. #5
    Join Date
    Apr 2004
    Posts
    2,088

    Default

    Quote Originally Posted by doc_dave View Post
    One question though: is there a BWks minimum version requirement? I'm running BW7, not 8. (I already have .NET 3.5 .) Hopefully nothing changed between versions ...
    David,

    You are correct, I should have stated the BW platforms. The problem is, I don't know what they might be, as I have only tested VLO on BW8.

    It should work without any problems on BW7, perhaps even BW6, except for the ParaText feature, which means you won't be able to double-click on verses in VLO and have them directed to BW because the ParaText feature is not in the earilier BW versions.

  6. #6
    Join Date
    Apr 2004
    Posts
    2,088

    Default

    Quote Originally Posted by Greg Ward View Post
    When I go to save it, the error says contact an administrator. So I saved it to a different directory and copied the file to Windows. Still the same errors in VLO. Any ideas?
    Greg

    It sounds like you might be having a problem with your administrator privileges. Also, when you installed, did you check the button for "everyone" or the button "just me" in the installation module?

    You can go to control panel and uninstall Verse List Organizer, then do a clean install. You do NOT have to reboot your computer. Just uninstall and reinstall and make sure the "everybody" button is checked in the install screen.

  7. #7
    Join Date
    Apr 2004
    Posts
    2,088

    Default

    Quote Originally Posted by Greg Ward View Post
    I having configuration problems-no ini file.
    --There is no vlo_ini.ini file that I see in my Windows directory.
    Also, Greg, if you have a corrupt .VLO file in your specified VLO folder, you will get this message. You need to delete your .VLO file if reconfiguring doesn't solve it. I'm working on changing this so VLO will skp to the next file if you have a corrupt .VLO file, but for now the solution is to delete your .VLO file. You also should not edit these files outside of VLO.

  8. #8
    Join Date
    Apr 2004
    Posts
    185

    Default ini file missing

    Scott,
    Thanks for your replies. So far VLO has been unable to create an ini file. Probably a Vista permissions thing. I'll keep poking around.

    (Is there a way to put the ini file in the program's directory similar to BW? If I remember there are several people who carry the whole BW program around on their USB Drive.)

    Thanks,
    Greg

  9. #9
    Join Date
    Apr 2004
    Posts
    2,088

    Default

    Quote Originally Posted by Greg Ward View Post
    (Is there a way to put the ini file in the program's directory similar to BW? If I remember there are several people who carry the whole BW program around on their USB Drive.)
    Greg,

    I think you need to run as an admin... I don't have Vista, I have XP, but I know Mike has run it on several of his Vista computers without any problem.

    Yes, I will be making a change so that the INI file can be placed in the same folder as VLO itself. Right now I'm trying to make everything as stable as possible and to implement some better error handling.

    Also, I have just spent the last four hours converting the entire project over to multibyte instead of Unicode (same as BW), so there won't be any potential conversion problems down the road. This will also make for some future increased functionality. That doesn't mean VLO won't recognize Unicode; it will, but the whole project fares better under multibyte.

    You should not try to create an INI file on your own. VLO will run without the INI file.

    Unlike most programs, however, VLO opens and reads TWO different files on startup, i.e., the first VLS file in your ASE folder and the first VLO file in your VLO folder. Most programs, as you know, don't open any files on startup.

    So I've got to get in there and make this bulletproof. The trouble you are having is NOT the fact that there is no INI file. I don't know why you're not allowed to create it, but that is the very FIRST thing VLO does when it starts, assuming there is no INI file to begin with. If there is an INI file, it reads it. If it can't read the INI file, program execution continues anyway.

    So your problem, in addition to privilege issues, could be with a corrupt VLS file or a corrupt VLO file.

    You might try renaming the first VLS file to a different extension, for example, "myfile.vvv" instead of "myfile.vls" and do the same thing if you have a VLO file created.

    Also, instead of reinstalling, grab the "vlo_exe_only.zip" from my download site and just try to run that. Be sure and unzip it and overwrite your current VLO.EXE.

  10. #10
    Join Date
    Apr 2004
    Posts
    185

    Default VLO startup

    Scott,
    Thanks for sharing the program. I was able to get the program to run and create the ini(s) by changing the vlo.exe properties to run it as an administrator in Vista.

    My help file now just has the index but no pages--probably again Vista priviledges.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •