I know that there is NOT a portable version per se but, I used the zip version and unpack it then carry it around on a SD chip (along with USBDLM, which can be configured to make drives use the same letter). The other thing I can do is place it on 'C:\' in the same location [eg. C:\progfile\tools\locate\locate32.exe]
So, my question [shrug request] is "What would it take to reconfigure locate32.exe to start using the dbs files relative paths verses using absolute paths?"
Unfortunetly I never really learned C and have not really used svn / git or I would try to take this request on. I still may try to take it on, but I don't seem to see the option to request to be added to the project.
Also seeing that the codebase seems to be spread out. Which is the real or recomended codebase to use, the website, sourceforge or git?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
You can use relative path with respect to installation directory using %locatedir% in the path name.
But the thing I guess is to use such paths in a new computers without too much reconfiguring. Maybe storing settings in a reg file using regedit when a proper setup is made.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I tried using 'import' with the "%locatedir%\dbs\HDD-38.dbs" as a file name but locate32 would just die off. But when I used the absolute path it would work normally.
I was able to export a registry file using one db and then modified it to use "ArchiveName"="%locatedir%\dbs\HDD-38.dbs" then added that to the registry. Opened up locate32 and was successfully able to navigate the db. So that did work but that was a lot to do just to add the dbs file. I think that the import file process dialog box was having trouble using the "%locatedir%".
Any other ideas ?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
It is an arbitrary ID used internally. It's better keep as is. I guess changing it does not do any harm either (unless there are several databases with same id), but there is no really reason to change it.
Last edit: jmj 2017-07-30
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Well duh, it ocurrs to me now that it would be best to do a 'import' then go into the file name box and replace the absolute path with the relative path.
Last edit: Chris Smith 2017-07-30
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I do not have access to any windows computers in 1.5 weeks, so I cannot try it myself. I am not sure that why you are using Import here (It will just load settings from the database). Can you write %locatedir% to "Path:" field when you configure the database? If you want to use Import, you can first use it to import settings and then change Path.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I know that there is NOT a portable version per se but, I used the zip version and unpack it then carry it around on a SD chip (along with USBDLM, which can be configured to make drives use the same letter). The other thing I can do is place it on 'C:\' in the same location [eg. C:\progfile\tools\locate\locate32.exe]
So, my question [shrug request] is
"What would it take to reconfigure locate32.exe to start using the dbs files relative paths verses using absolute paths?"
Unfortunetly I never really learned C and have not really used svn / git or I would try to take this request on. I still may try to take it on, but I don't seem to see the option to request to be added to the project.
Also seeing that the codebase seems to be spread out. Which is the real or recomended codebase to use, the website, sourceforge or git?
You can use relative path with respect to installation directory using %locatedir% in the path name.
But the thing I guess is to use such paths in a new computers without too much reconfiguring. Maybe storing settings in a reg file using regedit when a proper setup is made.
I tried using 'import' with the "%locatedir%\dbs\HDD-38.dbs" as a file name but locate32 would just die off. But when I used the absolute path it would work normally.
I was able to export a registry file using one db and then modified it to use "ArchiveName"="%locatedir%\dbs\HDD-38.dbs" then added that to the registry. Opened up locate32 and was successfully able to navigate the db. So that did work but that was a lot to do just to add the dbs file. I think that the import file process dialog box was having trouble using the "%locatedir%".
Any other ideas ?
also what is the "ID"=dword:0000ebaa reg entry? Is that an arbitrary id number that we can change to anything? or is it derived from the dbs file?
It is an arbitrary ID used internally. It's better keep as is. I guess changing it does not do any harm either (unless there are several databases with same id), but there is no really reason to change it.
Last edit: jmj 2017-07-30
Well duh, it ocurrs to me now that it would be best to do a 'import' then go into the file name box and replace the absolute path with the relative path.
Last edit: Chris Smith 2017-07-30
I do not have access to any windows computers in 1.5 weeks, so I cannot try it myself. I am not sure that why you are using Import here (It will just load settings from the database). Can you write %locatedir% to "Path:" field when you configure the database? If you want to use Import, you can first use it to import settings and then change Path.