You could open Locate32.exe, go to settings and databases tab. It might clear few things out. All databases that are setup there have name. You can update those with that -D argument.
On the otherhand, you can create also databases which are not setup in Locate32 using updtdb32.exe, but then you have to specify the file name (-d argument) and also what is included to databases (-L argumentd etc).
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
-
2013-06-20
I basically want locate32 to cover 2 drives : C: and a NAS.
Updatedb32:
To index C: I used updatedb32 with the switches -LC: and -d C:\Users...\files-C.dbs . During the indexing I noticed the NAS being scanned also !!! Strange.
The timestamps of the files confirmed that both databases, the one relating to the NAS as well as the one relating to drive C had been created/updated.
The strange thing: the file relating to drive C is supposed to be the bigger file, the one relating to the NAS should be smaller. But it was the other way around.
This means 'files-C' does relate to the NAS, not drive C .
Take a look at Locate32-file-menu:
In the menu item 'Find used databases' only ONE database is listed and it is called 'files' . And the files found are on drive C.
So updatedb32 / locate32 seem to refer to only one usable database called 'files'.
The other file - 'files-C' - was updated but is not accessible.
The locate32 Database-Tab - even more confusing:
The settings in the database tab also show one single item 'files' . And according to these settings the 'files'-database relates to drive C:, D:, E: and H: !
But when I searched for "*" on H:, nothing was found.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I'm not sure why both databases where updated if you used updtdb32 with -d and -L. Anyway, if you want to use Locate32, you should setup your databases in the Setup dialog. updtdb32 just creates/updates the database files and does not add or change anything to Locate32. I would suggest you to concentrate to Locate32 and setup your databases there.
Last edit: jmj 2013-06-21
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
-
2013-06-21
Well, I have different troubles with the regular Locate32 , that's why I turned to the portable version.
Here is a resume what updatedb32 does:
if one uses a database-path X:, switch -LX:, and no file, then the database is written into files.dbs.
if one uses a database-path X:, switch -LX: and a file X-dbase.dbs per -d switch
then updatedb32 writes the data still into the file 'files.dbs'
AND
then it applies the -L1 switch to the file X-dbase.dbs
-L1 means: 'check all local hard drives'
in my case it throws the data of drives C: D. E: H: into the file X-dabase .
HOWEVER: the X-dbase.dbs just sits there, locate32 ignores this database, it doesn't show on any menu item.
This concerns Win7, 64 bit; locate32 64bit
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Please note that -d should come first, otherwise all -L arguments are given for the default database. If you still have problems, can you give exact commend lines you are using?
Yes, as I said, updtdb32 does not change anything in Locate32. You should setup the databases in Locate32 if you want to use those. Or give databases using command line arguments when you open locate32.exe.
Portable support for Locate32 is very experimental at the best, so please skip those unless you really need those.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
How to create databese from first run with command line and update database with command line ? am trynig to make this software work portable and by using command line
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
You can specify the database (-d), directories (-L etc), and other scanning setting using the command line argument of updtdb32. Then you can call locate.exe using same -d argument. But you need to specify those always, which can be laborous.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
when i create database it seems working , when i run that way - updatedb32.exe -d C:\locate\test.dbs it creates databse at end (it finished with error message about reg files located in C:\locate ) ... but when i trying to update it - locate.exe -d C:\locate\test.dbs after it finished the test.dbs files did not shown that his modification date a changed ! and when i trying to find new files which i add after databse was created but before it updated ..it found nothing ...updates did not added in specefied .dbs file .... maybe i understand you wrong ? in this case may you please provide right command to update databse in case all locate32 programm files and databse located in C:\locate and the name of database is test.dbs .. it is really pity that this magnificent software aren´t ready and easy for portable ...... thanks in advance
Last edit: seatrophy 2018-04-23
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Yes, that's how the program is designed to work. There is no "live update" implemented and therefore you should update the database to see the changed files. You can setup automatic updated. Locate32 quite has settings for that, but you can also setup a scheduled tasks in Windows.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
i knew about it, and i mean did manual update via cmd like that locate.exe -d C:\locate\test.dbs but no updates no database modification time changed... maybe because i use wrong commnad line or maybe not prepare properly locate32 files for work like portable , but i did exaclty same as recomended to make it work as portable
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
locate.exe shuold not update database, updtdb32 is used for that. To update the database, you can use the same command line as you used when you created the database at first place (there is actually no difference between "creating" or "updating", update does not use any information from existing database).
Which recommendations you follow?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
" -d file uses database from file 'file' and
-D name uses database named 'name' (the properties of "
Hi,
what is the difference between 'file' and 'name' ?
Does 'name' refer to a certain directory ? I could not make sense out of it.
I am exploring the command line options and the portable version,
because of troubles in Windows 7 64bit.
What I noticed: locate32 basically allows only one database file 'file.dbs' which covers ALL local drives, NETWORK drives are ignored.
Only if I update per 'updtdb32 -LM:' then I can force file.dbs to cover the network drive M: . But only until I restart windows.
Hi!
You could open Locate32.exe, go to settings and databases tab. It might clear few things out. All databases that are setup there have name. You can update those with that -D argument.
On the otherhand, you can create also databases which are not setup in Locate32 using updtdb32.exe, but then you have to specify the file name (-d argument) and also what is included to databases (-L argumentd etc).
I basically want locate32 to cover 2 drives : C: and a NAS.
Updatedb32:
To index C: I used updatedb32 with the switches -LC: and -d C:\Users...\files-C.dbs . During the indexing I noticed the NAS being scanned also !!! Strange.
The timestamps of the files confirmed that both databases, the one relating to the NAS as well as the one relating to drive C had been created/updated.
The strange thing: the file relating to drive C is supposed to be the bigger file, the one relating to the NAS should be smaller. But it was the other way around.
This means 'files-C' does relate to the NAS, not drive C .
Take a look at Locate32-file-menu:
In the menu item 'Find used databases' only ONE database is listed and it is called 'files' . And the files found are on drive C.
So updatedb32 / locate32 seem to refer to only one usable database called 'files'.
The other file - 'files-C' - was updated but is not accessible.
The locate32 Database-Tab - even more confusing:
The settings in the database tab also show one single item 'files' . And according to these settings the 'files'-database relates to drive C:, D:, E: and H: !
But when I searched for "*" on H:, nothing was found.
I'm not sure why both databases where updated if you used updtdb32 with -d and -L. Anyway, if you want to use Locate32, you should setup your databases in the Setup dialog. updtdb32 just creates/updates the database files and does not add or change anything to Locate32. I would suggest you to concentrate to Locate32 and setup your databases there.
Last edit: jmj 2013-06-21
Well, I have different troubles with the regular Locate32 , that's why I turned to the portable version.
Here is a resume what updatedb32 does:
if one uses a database-path X:, switch -LX:, and no file, then the database is written into files.dbs.
if one uses a database-path X:, switch -LX: and a file X-dbase.dbs per -d switch
then updatedb32 writes the data still into the file 'files.dbs'
AND
then it applies the -L1 switch to the file X-dbase.dbs
-L1 means: 'check all local hard drives'
in my case it throws the data of drives C: D. E: H: into the file X-dabase .
HOWEVER: the X-dbase.dbs just sits there, locate32 ignores this database, it doesn't show on any menu item.
This concerns Win7, 64 bit; locate32 64bit
Please note that -d should come first, otherwise all -L arguments are given for the default database. If you still have problems, can you give exact commend lines you are using?
Yes, as I said, updtdb32 does not change anything in Locate32. You should setup the databases in Locate32 if you want to use those. Or give databases using command line arguments when you open locate32.exe.
Portable support for Locate32 is very experimental at the best, so please skip those unless you really need those.
How to create databese from first run with command line and update database with command line ? am trynig to make this software work portable and by using command line
You can specify the database (-d), directories (-L etc), and other scanning setting using the command line argument of updtdb32. Then you can call locate.exe using same -d argument. But you need to specify those always, which can be laborous.
when i create database it seems working , when i run that way - updatedb32.exe -d C:\locate\test.dbs it creates databse at end (it finished with error message about reg files located in C:\locate ) ... but when i trying to update it - locate.exe -d C:\locate\test.dbs after it finished the test.dbs files did not shown that his modification date a changed ! and when i trying to find new files which i add after databse was created but before it updated ..it found nothing ...updates did not added in specefied .dbs file .... maybe i understand you wrong ? in this case may you please provide right command to update databse in case all locate32 programm files and databse located in C:\locate and the name of database is test.dbs .. it is really pity that this magnificent software aren´t ready and easy for portable ...... thanks in advance
Last edit: seatrophy 2018-04-23
Yes, that's how the program is designed to work. There is no "live update" implemented and therefore you should update the database to see the changed files. You can setup automatic updated. Locate32 quite has settings for that, but you can also setup a scheduled tasks in Windows.
i knew about it, and i mean did manual update via cmd like that locate.exe -d C:\locate\test.dbs but no updates no database modification time changed... maybe because i use wrong commnad line or maybe not prepare properly locate32 files for work like portable , but i did exaclty same as recomended to make it work as portable
locate.exe shuold not update database, updtdb32 is used for that. To update the database, you can use the same command line as you used when you created the database at first place (there is actually no difference between "creating" or "updating", update does not use any information from existing database).
Which recommendations you follow?