Quantcast
Channel: File Metadata
Viewing all 919 articles
Browse latest View live
↧

New Post: Error using version 1.3 in windows 10

January 17, 2016, 4:56 pm
$
0
0
Thanks for the instructions. Did exactly as instructed.

No log file was created, However results as seen on the cmd prompt screen are as follows:

G:>PropertyTest.exe test.pdf

File: test.pdf
Property Handler: {D06391EE-2FEB-419B-9667-AD160D0849F3}

Instantiated Property Handler
Found IID_IInitializeWithFile
Initialized for test.pdf

System.Keywords : GetCount failed with HRESULT=0x80030002

System.Keywords : GetValue failed with HRESULT=0x80030002

System.Keywords : SetValue failed with 0x80030002


Btw, I ran this test on my flash drive.

I observed that I can add tags to the file if they reside on my HDD, the "Error 0x80030003: The path %1 could not be found. " appears only when tagging files on the flash drive.

hiwire03
↧
Search

New Post: Error using version 1.3 in windows 10

January 18, 2016, 3:17 am
$
0
0
Excellent, this certainly clarifies things greatly.

File Meta depends on an NTFS feature to store metadata. How is your flash drive formatted? Many of them ship formatted using FAT, which won’t work.

Dijji
↧
↧

New Post: Error using version 1.3 in windows 10

January 18, 2016, 6:47 am
$
0
0
Right on !!

I checked with the Flash Drive's File format. It was indeed FAT.

This I think solves the mystery!

Thanks,

hiwire03
↧

Updated Wiki: Errors and their causes

January 19, 2016, 2:42 am
$
0
0

Errors and their causes

Errors, when they occur, usually seem to show up at the first attempt to save a metadata property that has been edited in Windows Explorer. This page describes the errors that have been reported, and what turned out to be their causes.

0x80030003

0x80030003 is STGEPATHNOTFOUND, which typically produces the message “The path %1 could not be found.”. The ‘%1’ is a placeholder for the path that couldn't be found, but, unfortunately it’s often not filled in.

This error can occur when an attempt is made to set a metadata property on a file which is stored on a drive formatted using FAT. File Meta depends on an NTFS feature to store metadata.

0x80004005

0x80004005 is the most vague of error messages. Its technical name is E_FAIL, the E being for error. It may be reported as ‘Unspecified error’, and it tends to be used as the default error for anything that goes wrong.

These are usually caused by the fact that Explorer caches information that it has read from the registry, and hasn’t yet caught up with some recent change made in the File Association Manager. It can be fixed by killing and restarting Explorer.exe, or at the worst, rebooting the system. The File Association Manager in Version 1.3 proposes and will perform the required restart of Explorer when changes are made that might require it.

0x800700C1

0x800700C1 is ERROR_BAD_EXE_FORMAT, and may be reported as ‘xxx is not a valid Win32 application’.

This is caused by a failure to load the File Meta property handler, or one of the DLLs on which it depends. It indicates either a disk problem, or that one of the executable files is corrupt. To check for disk problems, use the Microsoft supplied chkdsk utility. The only executable files involved are the property handler itself, and the C++ runtime on which it depends. To make sure that your copies are clean, take the following steps:
  1. uninstall File Meta
  2. uninstall any Microsoft Visual C++ 10.0 runtimes or redistributables that are currently installed, then
  3. check to see that msvcr100.dll no longer appears in Windows\System32 (this is the most important component of the C++ runtime)
  4. if msvcr100.dll still appears, then further investigation is required. Its presence will prevent the C++ runtime installation from succeeding. I have seen this occur when a 32-bit version of msvcr100.dll had been manually copied to the System32 folder, which on a 64-bit system is reserved for 64-bit files, despite the name.
  5. otherwise, reinstall File Meta. This will automatically install the correct version of the C++ runtime.
↧

Updated Release: Property Tester (Jan 16, 2016)

January 19, 2016, 3:04 am
$
0
0
A tool to help diagnose problems writing metadata properties.

PropertyTest64.zip and PropertyTest32.zip each contain a single executable, PropertyTest.exe. if you have a 64-bit system, download PropertyTest64.zip, otherwise download PropertyTest32.zip .To run the test, first extract the executable from the downloaded zip file to a convenient folder.

The tool needs to be run from the command line, so next you need to open a command prompt by typing cmd in the search box and choosing ‘Command Prompt’. Then you need to change to a directory containing a test file on which we're going to set a metadata property. For instance, ‘cd Documents’ will take you to your normal documents folder.

Then you can say ‘\wherever\PropertyTester.exe test.pdf’ to run the tool against the chosen target file, or if you unzip PropertyTester.exe to the same directory as the target file, just ‘PropertyTester.exe test.pdf’. Note that the target file must be of a type configured to use the File Meta property handler. The output will appear in the command window, or you can route it to a log file by saying ‘\wherever\PropertyTester.exe test.pdf > log.txt’.

The test basically performs the same actions as Windows Explorer does when setting metadata properties, but reports back in detail on any errors that it encounters. On my machine, for a successful run, I get: 
File: empty.txt
Property Handler: {D06391EE-2FEB-419B-9667-AD160D0849F3} 

Instantiated Property Handler
Found IID_IInitializeWithFile
Initialized for empty.txt 

System.Keywords : Property is in the property store. 

System.Keywords : Value = atag 

System.Keywords : SetValue succeeded
System.Keywords : Commit succeeded
↧
↧

Updated Release: Property Tester (Jan 16, 2016)

January 19, 2016, 3:08 am
$
0
0
A tool to help diagnose problems writing metadata properties.

PropertyTest64.zip and PropertyTest32.zip each contain a single executable, PropertyTest.exe. if you have a 64-bit system, download PropertyTest64.zip, otherwise download PropertyTest32.zip .To run the test, first extract the executable from the downloaded zip file to a convenient folder.

The tool needs to be run from the command line, so next you need to open a command prompt by typing cmd in the search box and choosing ‘Command Prompt’. Then you need to change to a directory containing a test file on which we're going to set a metadata property. For instance, ‘cd Documents’ will take you to your normal documents folder.

Then you can say ‘\wherever\PropertyTester.exe test.pdf’ to run the tool against the chosen target file (here, test.pdf is the target file, and \wherever\ is the path to the unzipped executable), or if you unzip PropertyTester.exe to the same directory as the target file, just ‘PropertyTester.exe test.pdf’. Note that the target file must be of a type configured to use the File Meta property handler. The output will appear in the command window, or you can route it to a log file by saying ‘\wherever\PropertyTester.exe test.pdf > log.txt’.

The test basically performs the same actions as Windows Explorer does when setting metadata properties, but reports back in detail on any errors that it encounters. On my machine, for a successful run, I get: 
File: empty.txt
Property Handler: {D06391EE-2FEB-419B-9667-AD160D0849F3} 

Instantiated Property Handler
Found IID_IInitializeWithFile
Initialized for empty.txt 

System.Keywords : Property is in the property store. 

System.Keywords : Value = atag 

System.Keywords : SetValue succeeded
System.Keywords : Commit succeeded
↧

New Post: Error using version 1.3 in windows 10

January 19, 2016, 2:48 am
$
0
0
Great. It’s always good to pin one of these down. Thank you for all your help in doing so.

I’ve added this error code to the Documentation page about errors and their causes, to help the next person that bumps into this.

Dijji
↧

Released: Property Tester (Jan 16, 2016)

January 19, 2016, 3:08 am
$
0
0
A tool to help diagnose problems writing metadata properties.

PropertyTest64.zip and PropertyTest32.zip each contain a single executable, PropertyTest.exe. if you have a 64-bit system, download PropertyTest64.zip, otherwise download PropertyTest32.zip .To run the test, first extract the executable from the downloaded zip file to a convenient folder.

The tool needs to be run from the command line, so next you need to open a command prompt by typing cmd in the search box and choosing ‘Command Prompt’. Then you need to change to a directory containing a test file on which we're going to set a metadata property. For instance, ‘cd Documents’ will take you to your normal documents folder.

Then you can say ‘\wherever\PropertyTester.exe test.pdf’ to run the tool against the chosen target file (here, test.pdf is the target file, and \wherever\ is the path to the unzipped executable), or if you unzip PropertyTester.exe to the same directory as the target file, just ‘PropertyTester.exe test.pdf’. Note that the target file must be of a type configured to use the File Meta property handler. The output will appear in the command window, or you can route it to a log file by saying ‘\wherever\PropertyTester.exe test.pdf > log.txt’.

The test basically performs the same actions as Windows Explorer does when setting metadata properties, but reports back in detail on any errors that it encounters. On my machine, for a successful run, I get:
File: empty.txt
Property Handler: {D06391EE-2FEB-419B-9667-AD160D0849F3} 

Instantiated Property Handler
Found IID_IInitializeWithFile
Initialized for empty.txt 

System.Keywords : Property is in the property store. 

System.Keywords : Value = atag 

System.Keywords : SetValue succeeded
System.Keywords : Commit succeeded
↧
Search

New Post: Don not show File-Size on StatusBar on Windows 10

January 21, 2016, 8:54 am
$
0
0
I've checked with EXE, FLV, MP4 file-type, I think other file-types too. I prefer to look at FileSize in the status bar rather than detailed mode. Pls fix this. Please view my following images:

Image

Image

OS: Windows 10 - x64

Again, thank you for your great soft :)
↧
↧

New Post: Don not show File-Size on StatusBar on Windows 10

January 21, 2016, 12:08 pm
$
0
0
Hi Xikul

In Windows 10, EXE, FLV and MP4 file types are all configured with Windows supplied property handlers, so it is not possible to add the File Meta property handler to these types using the Association Manager. So what types are you adding the File Meta property handler to?

On my Windows 10 x64 system, I have the File Meta property handler configured for.txt and.pdf files, and I do not see the same symptom: file sizes are displayed in the status bar as you would expect, for txt, pdf , EXE, FLV and MP4 file types

Do you find that the problem goes away if you uninstall File Meta?

Dijji
↧

New Post: Don not show File-Size on StatusBar on Windows 10

January 21, 2016, 6:12 pm
$
0
0
To be able to add the File Meta property handler to these types using the your File Association Manager, I'd deleted keys in Regedit, ex. for MP4, path:
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\
Windows\CurrentVersion\PropertySystem\
PropertyHandlers\.mp4]
@="{f81b1b56-7613-4ee4-bc05-1fab5de5c07e}"
And then, just click on "Add File Meta Handler"
So, that's all.

FileTypes I'm adding FM:

Image
↧

New Post: Don not show File-Size on StatusBar on Windows 10

January 22, 2016, 2:43 am
$
0
0
Thank you, that makes sense now. I’ve done the same thing on my own machine, but I cannot reproduce the problem. Whatever I do, Explorer stubbornly shows the total size of the current selection.

So I’m wondering if you can give me some help. What do you have to do to get the size shown again? Does restoring the Windows property handler do the trick?

Dijji
↧

New Post: Don not show File-Size on StatusBar on Windows 10

January 22, 2016, 4:36 am
$
0
0
Dijji wrote:
So I’m wondering if you can give me some help. What do you have to do to get the size shown again? Does restoring the Windows property handler do the trick?

Dijji
Yes, I restored Windows property handler. Pls view my image:

Image

Sorry for my bad Eng :(
↧
↧

New Post: Don not show File-Size on StatusBar on Windows 10

January 22, 2016, 5:37 am
$
0
0
Sorry for my missing Tittle, maybe: Error does not display the FileSize in the StatusBar after "Add File Meta Handler" to the EXE, FLV, MP4.... Please fix this.

Finally, I'd like to show Filetype on the StatusBar after using your FileMeta software.
↧

New Post: Don not show File-Size on StatusBar on Windows 10

January 22, 2016, 6:56 am
$
0
0
So, to confirm what you’re saying, when you removed the File Meta property handler using the Association Manager, size information started appearing in the status bar again?

Note that doing this will not restore the Windows property handler, but leave the file type without any property handler registered at all. To restore the Windows property handler, you would need to restore the deleted property handler registry key manually.

I can’t add the file type to the status bar. I don’t directly display anything in Explorer, all I do is to set registry keys to list the properties that should be shown in the details pane, and the details tab in the properties dialog. I have recently discovered that I could also be setting a registry key to list the properties that should be shown in the infotip you see when you hover over a file, but I don’t currently set it. I don’t know of anything that I could do within my current scope to influence what is shown in the status bar.

Some Explorer extensions do modify what the status bar shows, so this is a possible factor. Do you have any other extensions installed?

Dijji
↧
Search

New Post: Don not show File-Size on StatusBar on Windows 10

January 22, 2016, 10:43 am
$
0
0
Dijji wrote:
So, to confirm what you’re saying, when you removed the File Meta property handler using the Association Manager, size information started appearing in the status bar again? Yes, That's right.

Note that doing this will not restore the Windows property handler, but leave the file type without any property handler registered at all. To restore the Windows property handler, you would need to restore the deleted property handler registry key manually. OK, I've backed up before delete any RegistryKey.

I can’t add the file type to the status bar. I don’t directly display anything in Explorer, all I do is to set registry keys to list the properties that should be shown in the details pane, and the details tab in the properties dialog. I have recently discovered that I could also be setting a registry key to list the properties that should be shown in the infotip you see when you hover over a file, but I don’t currently set it. I don’t know of anything that I could do within my current scope to influence what is shown in the status bar. Oh sorry sorry, I mean it's FileSize, not FileType. So, can you fix to show FileSize after add File Meta property handler using the Association Manager?

Some Explorer extensions do modify what the status bar shows, so this is a possible factor. Do you have any other extensions installed? No, install your MetaFile only.

Dijji
↧

New Post: Don not show File-Size on StatusBar on Windows 10

January 22, 2016, 11:39 am
$
0
0
Okay, so we are just talking about file size. I would be happy to fix this if we can figure it out. However, at the moment, I can’t reproduce the problem on my system, so I don’t know what is causing it on yours.

Can we try looking at file type for which Windows does not define a property handler? Let’s go for .txt. First, confirm that the size of the txt file is shown when selected. Then use the Association Manager to add the File Meta property handler for .txt files, and restart Explorer. Does the size of the txt file still show in Explorer? If not, when you remove the File Meta property handler and restart Explorer, does it come back?

Dijji
↧
↧

New Post: Don not show File-Size on StatusBar on Windows 10

January 22, 2016, 12:03 pm
$
0
0
Let’s go for .txt. First, confirm that the size of the txt file is shown when selected. Then use the Association Manager to add the File Meta property handler for .txt files, and restart Explorer. Does the size of the txt file still show in Explorer? No, it doesn't show filesize in Explorer.

If not, when you remove the File Meta property handler and restart Explorer, does it come back? Yes, it come back (show in Explorer).
↧

New Post: Don not show File-Size on StatusBar on Windows 10

January 22, 2016, 12:29 pm
↧

New Post: Don not show File-Size on StatusBar on Windows 10

January 23, 2016, 12:06 pm
$
0
0
It couldn’t be clearer than that! I will keep scratching my head, and try to come up with something that will let us make progress.

One thing, what language is your machine set to? I could make one of mine the same, in case that is relevant.

Dijji
↧
Viewing all 919 articles
Browse latest View live
Search
<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>