HydrogenAudio

I've decided to discontinue development of this component. Please see this post (http://www.hydrogenaudio.org/forums/index.php?showtopic=78708&view=findpost&p=694581) for the reason why. Thank you to all of those who have downloaded and used the component previously

Updated to version 0.1.6.2. Download here (http://www.hydrogenaudio.org/forums/index.php?showtopic=78707).

Changelist:
0.1.6.2 (2010-03-02)
- Handle multiple components in one dll with name changes between versions (uses <oldname> tag) (thanks to kode54)
- Fixed listbox scrolling

0.1.6.1 (2010-03-02)
- REALLY fixed crash when downloading non-existent link
- More version comparison tweaks
- Use SHCreateDirectoryEx instead of CreateDirectory

0.1.6 (2010-02-24)
- Fixed security attributes on copied files (no more lock icon). Re-downloading a component that has the lock icon will remove it and replace it with a file that has the correct security attributes.
- Don't ask for elevation unless required
- Added support for files needing to be installed to foobar2000 profile folder (eg foo_httpcontrol)

0.1.5.3 (2010-02-22)
- Added link dialog for developers who want traffic redirected to their webpage. The respective component is not downloaded.

0.1.5.2 (2010-02-21)
- Fixed support for compressed xml component list. Set the XML download location to http://58.108.209.133/foo_component_manager.7z (http://58.108.209.133/foo_component_manager.7z) to make use of it. Both plain xml and compressed xml files will continue to be updated.

0.1.5 (2010-02-20)
- Added support for compressed xml component list.
- Handle differently formatted version strings

See download link for complete changelist.

If you're a developer and don't want your component included as part of the auto update (due to bandwidth usage, lost webpage traffic, etc) please let me know. I can host the files myself, direct users to your homepage instead, or not include it at all.

-----------------------------------------
Hi all,

I'm pleased to release my second foobar2000 component, foo_component_manager. This component is intended to help manage the installation and updating of 3rd party foobar2000 components.

At the moment foo_component_manager only updates currently installed components, but this will expand to include adding of new components and removal of installed components. I just wanted to gauge foobar2000 users' feedback on this initial release before implementing those features.

The update procedure works by downloading an xml file containing a list of known components. This list includes the component's name, version, description, release date, author, download link and so on. The actual xml schema for a component is shown below. Items in bold are required, while items in italics can appear one of more times. I'll set up a HA wiki page on editing the xml file, as well as putting the xml file up on the wiki so people can edit it as new component versions are released. For now I'll maintain the xml file myself which is by no means complete, so if you want to see a component in there just PM me with the relevant details.

[b][i]<plugin>[/i][/b]
[b]<module></module>[/b]
<desc></desc>
<category></category>
<author></author>
<email></email>
<homepage></homepage>
<thread></thread>
<redirect></redirect> (only included if component is to redirect to developer's homepage)

[b][i]<release>[/i][/b]
[b][i]<component>
<name></name>
[i]<oldname></oldname>[/i]
<version></version>
</component>[/i][/b]
<date></date>
<foobar2000version></foobar2000version>
<requirements></requirements>
[b]<download></download>[/b]
<changelist></changelist>
[i]<installpath>
<src></src>
<dest></dest>
</installpath>[/i]
[i][b]</release>
</plugin>[/b][/i]

So basically the xml file contains one or more plugins, which itself contains one or more releases. Each release can have one or more component versions (because a single dll can contain multiple components, such as foo_unpack). There can also be zero or more install paths per release, depending on how many files are included in the zip/7z/rar file.

This component includes the expat xml parsing library (http://expat.sourceforge.net/) to parse the xml file, and the command line version of 7zip (http://www.7-zip.org/) to handle downloaded archives.

Download:
foo_component_manager 0.1.6.2 (http://www.hydrogenaudio.org/forums/index.php?showtopic=78707)

Installation:
- Unzip the downloaded file to your foobar2000 folder
- foo_component_manager should be in the components folder, while libexpatw.dll, 7z.exe and 7z.dll should be in the same folder as foobar2000.exe

Usage:
- To update installed components, go to Help->Check for component updates
- A dialog will appear displaying your currently installed components and their versions. By default any component with available updates will be checked.
- You can select a component from the list to view its details in the bottom half of the dialog.
- After checking the components you want to update, click either Download Only or Download & Install.
- Components will be downloaded to an updates folder within the foobar2000 folder, along with a batch file which performs the installation.
- If you clicked Download & Install, foobar2000 must be restarted for the updated components to be installed.

Known Problems:
- The update won't work if foobar2000 is installed to Program Files on Windows Vista or Window 7. Downloads can be performed if foobar2000 is run as an administrator, but the update batch file will fail. I will change this to use %APPDATA% asap. - FIXED
- Downloading a component from a link that no longer exists will cause foobar2000 to crash. - FIXED
- The auto check for updates and silent install options in the preferences page are placeholders at the moment as they haven't been implemented yet, so are greyed out.
- If component contains date as part of its version, it may be reported that the XML file is out of date - FIXED
- Keyboard navigation in dialogs isn't complete (tabbing, etc). Need to handle keyboard accelerators in modeless dialogs.
- Can't sort columns by status
- There's an issue with handling dlls that declare multiple components where component names have changes between versions (eg foo_adpcm.dll). - FIXED
- There are two different components both named foo_cuefilter. Will need to cross check their declared names and modules to determine which one is the correct one to update.

Future changes:
- Add a dialog to allow easy installation of new components and removal of old components. The dialog will allow searching by component types (UI, DSP, etc), name etc.
- Perhaps being able to parse webpages like the HA wiki in addition to/instead of a manually edited xml file.
- Ability to update to an older version of a component listed in the xml file (if the newest version is broken, or doesn't support the installed foobar2000 version).
- Handle compressed xml files (suggested by cerAmik) - DONE
- Configurable download location (suggested by cerAmik)
- Activate/deactivate components (suggested by cerAmik)
- Add option to search for and overwrite existing component paths (suggested by watercolor)
- Add path to 7zip if it is already installed (suggested by 2E7AH)
- Add "Restart fooobar2000" button to download completed message box (suggested by Hitchhiker427)

Please download it and let me know what you think

Thank you! I use many component and it has already helped me to keep them up to date.

Bug report:
The download works well, but install doesn't. I find the file in my temporary internet files, a command prompt is launched when closing foobar, but no update. The command prompt window is too fast to see what append...

Suggestions:
- Handle compressed xml files. They are many components, and if you keep all version for each, the list will be very big
- Option to choose where the files are downloaded
- Component deactivate option

Thanks for your suggestions, I'll add them to the list of to-dos.

Try downloading some components by clicking the Download Only button. Then look in the foobar2000/updates folder. Are there any files there?

What OS are you using? If it's Vista or 7, I'm guessing that you've installed foobar to the Program Files folder, but the component doesn't have write permissions to save the components or update them. You could try running foobar2000 as an admin and do a Download & Install to see if that makes a difference.

To see the output of the batch file, open up a command prompt (start->run and type cmd). Then type "cd <foobar2000 folder>\updates" (without the double quotes) and hit enter. Then type "update.bat" and hit enter. What text is displayed?

I'm using windows 7, and foobar is installed in program files, but i have taken ownership of the directory...
The files are in the foobar2000/updates

C:\Program Files\foobar2000\updates>update
foobar2000 component update in progress...

7-Zip 4.65  Copyright © 1999-2009 Igor Pavlov  2009-02-03


Error:
7-Zip cannot find the code that works with archives.
Un sous-répertoire ou un fichier ..\components existe déjà.
Le fichier spécifié est introuvable.
Le fichier spécifié est introuvable.

Update complete.

Maybe it's the foo_dop archive (the only update I have try, murphy law)

Thanks for that. It sounds like 7zip is missing a dependency.

Edit: Yep, it's missing a dll file. I'll include it in the zip file and re-upload the component.

Edit 2: OK, the missing dll is now included with the zip. Please re-download it and let me know how it goes.

Works fine now  Thanks

There is a request. I install component in sub component folder(e.g. foobar2000/component/ui/foo_ui_console.dll).
that is mean if I use update funciton of foo_component_manager, it will duplicate component file.(this component download to directly under component folder.)
so,I hope changing this component's downloading place to same as preexisting component's folder.

Sorry my poor english. Thank you.

Thanks for making this.  I've wished for this kind of functionality ever since I started using foobar, and now it's a reality.  Good job.

It looks very good, thanks

What does "XML file out of date" means?
More than 80% of my components are "Not found in XML list" and I wouldn't say I have exotic components
Can we use sort by clicking the column title?
I already have 7zip, can I just point component to it folder instead adding it to my foobar folder
Maybe list can be saved per foobar instance and not loaded each time user selects the command as there are certainly not changes to components if foobar isn't restarted

The update won't work if foobar2000 is installed to Program Files on Windows Vista or Window 7

You mean directly in Program Files? I haven't had a change to try downloading as my components are up to date

There is a request. I install component in sub component folder(e.g. foobar2000/component/ui/foo_ui_console.dll).
that is mean if I use update funciton of foo_component_manager, it will duplicate component file.(this component download to directly under component folder.)
so,I hope changing this component's downloading place to same as preexisting component's folder.

Sorry my poor english. Thank you.

Your English is perfectly understandable, so don't apologise

Thanks for the suggestion, I'll see what can be done.

Foobar seems to crash everytime I try to update, though I've got no idea what's wrong as the crash bypasses failure logs. Trying to download three components, foo_bpm 0.2.3 to 0.2.4), foo_dumb (0.9.9 to 0.9.9.12) and foo_uie_lyrics2 (0.4.2 to 0.4.6.5). I've tried both Download & Install, then Download Only, but the problem persists with both.

EDIT: Downloading each file individually seems to work. As far as I could tell, it crapped out every time I tried to download foo_uie_lyrics2.

Core (2010-01-09 12:47:00)
    foobar2000 core 1.0
foo_abx.dll (2009-06-07 13:25:26)
    ABX Comparator 1.3.4
foo_albumlist.dll (2010-01-09 12:44:46)
    Album List 4.4
foo_audioscrobbler.dll (2009-08-30 23:27:42)
    Audioscrobbler 1.4.2
foo_biometric.dll (2009-03-14 20:42:36)
    Fingerprint tools 0.3
foo_bpm.dll (2010-01-11 06:26:17)
    BPM Analyser 0.2.3
foo_cdda.dll (2010-01-09 12:44:42)
    CD Audio Decoder 3.0
foo_component_manager.dll (2010-02-15 03:24:04)
    Component Manager 0.1.0
foo_converter.dll (2010-01-09 12:44:32)
    Converter 1.4
foo_dop.dll (2009-12-27 16:06:53)
    iPod manager 0.6.6.4
foo_dsp_bs2b.dll (2009-06-29 19:28:12)
    bs2b 3.1.0
foo_dsp_loudspeakereq.dll (2009-07-02 07:52:58)
    Loudspeaker Equalizer 1.0.1
foo_dsp_std.dll (2010-01-09 12:44:48)
    Standard DSP Array 1.0
foo_dumb.dll (2009-09-06 16:34:42)
    DUMB module decoder 0.9.9
foo_fileops.dll (2010-01-09 12:43:32)
    File Operations 2.1.2
foo_input_monkey.dll (2009-05-01 13:40:52)
    Monkey's Audio Decoder 2.1.4
foo_input_std.dll (2010-01-09 12:44:24)
    Standard Input Array 1.0
foo_jesus.dll (2009-04-05 20:12:46)
    Autosave 0.0.3
foo_lyricsdb.dll (2009-09-21 22:06:04)
    foo_lyricsdb 0.0.8 alpha 1
foo_lyricsgrabber.dll (2008-12-11 19:27:08)
    Lyrics Grabber 0.2.6.2 Beta
foo_masstag.dll (2009-10-23 14:40:56)
    Masstagger 1.8.4
foo_np_simple.dll (2009-01-10 18:11:52)
    Now Playing Simple 1.8
foo_playcount.dll (2009-04-29 19:09:32)
    Playback Statistics 2.1.9
foo_playcount_sql.dll (2009-06-18 22:12:48)
    Playback statistics SQL 1.5.4.236
foo_pqview.dll (2008-03-11 18:02:54)
    Playback Queue Viewer 0.2
foo_rgscan.dll (2010-01-09 12:44:24)
    ReplayGain Scanner 2.0.9
foo_run.dll (2009-06-07 14:15:18)
    Run services 0.3.7
foo_softplaylists.dll (2010-01-09 04:47:02)
    Soft Playlists 2009-12-30.2
foo_texttools.dll (2009-12-13 00:46:02)
    Text Tools 1.0.3
foo_ui_columns.dll (2010-01-09 15:40:28)
    Columns UI 0.3.8.3
foo_ui_std.dll (2010-01-09 12:44:52)
    Default User Interface 0.9.5
foo_uie_biography.dll (2009-12-19 11:25:46)
    Biography View 0.3.4.4
foo_uie_lyrics2.dll (2009-12-16 18:33:08)
    Lyric Show Panel 0.4.2
foo_verifier.dll (2009-10-06 20:49:20)
    File Integrity Verifier 1.1
foo_wave_seekbar.dll (2010-01-17 00:11:28)
    Waveform seekbar 0.1.10
foo_whatsnew.dll (2008-08-30 14:45:00)
    Feature Watcher 1.0.6

What does "XML file out of date" means?

That means you have a component installed that is newer than what's listed in the xml file. What's the component that says XML file out of date?

More than 80% of my components are "Not found in XML list" and I wouldn't say I have exotic components

I've been adding each of the components by hand to the xml file which can be a bit tedious and time consuming. In the coming days and weeks the list will become more complete.

Can we use sort by clicking the column title?

Not yet, but it's on the cards.

I already have 7zip, can I just point component to it folder instead adding it to my foobar folder

Good idea, I'll add it to the to-do list. For now, you can modify your %PATH% environment variable to include the 7zip installation folder.

Maybe list can be saved per foobar instance and not loaded each time user selects the command as there are certainly not changes to components if foobar isn't restarted

That's true, though the list itself might have been updated even though foobar hasn't been restarted. Perhaps I'll make it a configurable option.

You mean directly in Program Files? I haven't had a change to try downloading as my components are up to date

You can force a component download/update by checking its box and clicking Download Only. If you run the batch file from the command-line, you'll see 7zip complains that it can't extract the files.

Foobar seems to crash everytime I try to update, though I've got no idea what's wrong as the crash bypasses failure logs. Trying to download three components, foo_bpm 0.2.3 to 0.2.4), foo_dumb (0.9.9 to 0.9.9.12) and foo_uie_lyrics2 (0.4.2 to 0.4.6.5). I've tried both Download & Install, then Download Only, but the problem persists with both.

EDIT: Downloading each file individually seems to work. As far as I could tell, it crapped out every time I tried to download foo_uie_lyrics2.

The link to foo_uie_lyrics2 0.4.6.5 seems to no longer exist. The component development has moved really rapidly (http://code.google.com/p/foo-display-lyrics/downloads/list) since I created the xml file, and is now up to 0.4.6.12, with the oldest available being 0.4.6.7. I've updated the xml file to show the latest version. Try doing an update again, hopefully it will work.

That said, the component should handle non-existent links so there's definitely a bug there.

That means you have a component installed that is newer than what's listed in the xml file. What's the component that says XML file out of date?

foo_ac3: Mine 0.9.4; Reported 0.9.3
foo_osd: Mine 1.52; Reported 1.6

You can force a component download/update by checking its box and clicking Download Only. If you run the batch file from the command-line, you'll see 7zip complains that it can't extract the files.

OK, it wasn't clear to me what you meant with Program Files. I updated successfully foo_bpm to it's current version

I tried some months ago (latest add on June 2009) collecting links to foobar components (like many others I guess) and thou it's not up to date or complete maybe it can save you some time: (CSV) http://pastebin.ca/1797059 (http://pastebin.ca/1797059)
It's before foobar component page existed or your foo_bpm (so it isn't there)

foo_ac3: Mine 0.9.4; Reported 0.9.3
foo_osd: Mine 1.52; Reported 1.6

Thanks, I'll update the xml file for foo_ac3.
Looking at the versions for foo_osd, 1.6 is the newest (just downloaded from kode54's site) although my version comparison function sees .52 being newer than .6 so it complains the xml file is out of date. I'll add it to the list of bugs  In the mean time you can safely update foo_osd to 1.6.

I tried some months ago (latest add on June 2009) collecting links to foobar components (like many others I guess) and thou it's not up to date or complete maybe it can save you some time: (CSV) http://pastebin.ca/1797059 (http://pastebin.ca/1797059)
It's before foobar component page existed or your foo_bpm (so it isn't there)

Awesome work, this'll give a big head start to filling in the xml file

I don't know if 1.6 is GDI+ or GDI, as GDI version renders fonts better on my display so I'll keep what I have right now

About csv, glad if it's helpful, thou many of them are now on foobar components page as you know

foo_osd 1.6 reports its name as On-Screen Display GDI+, so it seems to use GDI+ rather than GDI. If that's the case, you can add foo_osd to the list of components to ignore when checking for updates under the Component Manager Preferences.

thanks for this fraganator, this really has the potential to be one of the greats.

Vista x64 here, fb2k installed in "Program files (x86)": running the update from the normal instance of fb2k doesn't have any effect as expected, but "download & install" succeed when running as administrator. Maybe it's because I have the components folder shared.
Anyway, nice component!

Fantastic component, worked for doing a few updates on first try with no issues.  This has some serious potential!

Great component!!!!!!!! I hardly can't wait for broader component support

Version 0.1.1 has been uploaded. It now requests UAC permission when running the update script, so should work on default installations in Vista and 7.

- Activate/deactivate components (suggested by cerAmik)

This is what I am waiting for. Without the need of delete the plugin from component's folder and when you want it back you have to search for it again.

Thank you for this long awaited component.

can't wait for more components to be added!

This old version (http://bubbleguuum.free.fr/foo_adpcm.dll) of foo_adpcm crashes the plugin just after "Status: Downloading XML data", probably when you enumerates plugins.
This is probably related to the fact this component declare several components. The latest foo_adpcm available on the components page do not crash your plugin.
Also what was strange is that when crashing I direclty got the Microsoft submit crash dialog instead of foobar2000's one.

I had to disable plugins one by one to find the offender .

I just wanted to say thanks! It's already come in handy. I'm good about keeping components up to date. Yet, I had 3 I never kept track of. Updating is such a breeze now.

Great work!

Thanks you! This is a great plugin!

It would be nice if one could submit a list of components that one has and that aren't on the XML list. Although I guess that could lead to quite a load of redundant submissions.

Version 0.1.2 is out. There's just a couple of minor changes, the main one being core components aren't marked as missing from the xml file.

I did a reasonable sized update to the xml update list, so it's probably worth re-running the check for updates.

This old version (http://bubbleguuum.free.fr/foo_adpcm.dll) of foo_adpcm crashes the plugin just after "Status: Downloading XML data", probably when you enumerates plugins.
This is probably related to the fact this component declare several components. The latest foo_adpcm available on the components page do not crash your plugin.
Also what was strange is that when crashing I direclty got the Microsoft submit crash dialog instead of foobar2000's one.

I had to disable plugins one by one to find the offender .

Thanks for doing that bit of investigation. It looks like the names of the components within the dll have changed between versions, which I haven't accounted for. I've removed foo_adpcm from the xml update list until it's resolved.

Works as expected here! Thanks! This is a new entry on my must-download list.

Update process worked smoothely and as expected. Thank you very much!

Hm, just tried it on my home PC and though it downloads the components just fine, it fails to successfully extract them and so fails to update.

What OS are you using and where abouts is foobar2000 installed to on your home PC? Are 7z.exe and 7z.dll in the foobar2000 folder? Could you please post the update.bat file? (found under either foobar2000\updates for a portable installation, or under c:\Users\<username>\AppData\Roaming\foobar2000\updates on Vista/7 or C:\Documents and Settings\<username>\Application Data\foobar2000\updates on XP for a standard install).

Win7. foobar2000 is installed to k:\foobar2000. 7z.* are where they should be. My install is not portable, but my config files are stored in the application folder, and this does not seem to confuse the component.

@echo off
echo foobar2000 component update in progress...

ping -n 2 127.0.0.1 >NUL

"K:\foobar2000\7z" x -y -o"K:\foobar2000\updates\foo_ac3" "K:\foobar2000\updates\foo_ac3.zip"
md "K:\foobar2000\components"
move /Y "K:\foobar2000\updates\foo_ac3\foo_ac3.dll" "K:\foobar2000\components\foo_ac3.dll"
rd /S /Q "K:\foobar2000\updates\foo_ac3"
del /Q "K:\foobar2000\updates\foo_ac3.zip"

"K:\foobar2000\7z" x -y -o"K:\foobar2000\updates\foo_audioscrobbler" "K:\foobar2000\updates\foo_audioscrobbler-1.4.6.zip"
md "K:\foobar2000\components"
move /Y "K:\foobar2000\updates\foo_audioscrobbler\foo_audioscrobbler.dll" "K:\foobar2000\components\foo_audioscrobbler.dll"
rd /S /Q "K:\foobar2000\updates\foo_audioscrobbler"
del /Q "K:\foobar2000\updates\foo_audioscrobbler-1.4.6.zip"

"K:\foobar2000\7z" x -y -o"K:\foobar2000\updates\foo_burninate" "K:\foobar2000\updates\foo_burninate_3.0.2.zip"
md "K:\foobar2000\components"
move /Y "K:\foobar2000\updates\foo_burninate\foo_burninate.dll" "K:\foobar2000\components\foo_burninate.dll"
rd /S /Q "K:\foobar2000\updates\foo_burninate"
del /Q "K:\foobar2000\updates\foo_burninate_3.0.2.zip"

move /Y "K:\foobar2000\updates\foo_discogs.dll" "K:\foobar2000\components\foo_discogs.dll"
del /Q "K:\foobar2000\updates\foo_discogs.dll"

"K:\foobar2000\7z" x -y -o"K:\foobar2000\updates\foo_dop" "K:\foobar2000\updates\foo_dop-0.6.6.5.7z"
md "K:\foobar2000\components"
move /Y "K:\foobar2000\updates\foo_dop\foo_dop.dll" "K:\foobar2000\components\foo_dop.dll"
rd /S /Q "K:\foobar2000\updates\foo_dop"
del /Q "K:\foobar2000\updates\foo_dop-0.6.6.5.7z"

"K:\foobar2000\7z" x -y -o"K:\foobar2000\updates\foo_dumb" "K:\foobar2000\updates\foo_dumb.zip"
md "K:\foobar2000\components"
move /Y "K:\foobar2000\updates\foo_dumb\foo_dumb.dll" "K:\foobar2000\components\foo_dumb.dll"
md "K:\foobar2000\components"
move /Y "K:\foobar2000\updates\foo_dumb\unmo3.dll" "K:\foobar2000\components\unmo3.dll"
rd /S /Q "K:\foobar2000\updates\foo_dumb"
del /Q "K:\foobar2000\updates\foo_dumb.zip"

"K:\foobar2000\7z" x -y -o"K:\foobar2000\updates\foo_gep" "K:\foobar2000\updates\foo_gep.zip"
md "K:\foobar2000\components"
move /Y "K:\foobar2000\updates\foo_gep\foo_gep.dll" "K:\foobar2000\components\foo_gep.dll"
rd /S /Q "K:\foobar2000\updates\foo_gep"
del /Q "K:\foobar2000\updates\foo_gep.zip"

"K:\foobar2000\7z" x -y -o"K:\foobar2000\updates\foo_input_alac" "K:\foobar2000\updates\foo_input_alac_1.0.5.zip"
md "K:\foobar2000\components"
move /Y "K:\foobar2000\updates\foo_input_alac\foo_input_alac.dll" "K:\foobar2000\components\foo_input_alac.dll"
rd /S /Q "K:\foobar2000\updates\foo_input_alac"
del /Q "K:\foobar2000\updates\foo_input_alac_1.0.5.zip"

"K:\foobar2000\7z" x -y -o"K:\foobar2000\updates\foo_input_hvl" "K:\foobar2000\updates\foo_input_hvl.zip"
md "K:\foobar2000\components"
move /Y "K:\foobar2000\updates\foo_input_hvl\foo_input_hvl.dll" "K:\foobar2000\components\foo_input_hvl.dll"
rd /S /Q "K:\foobar2000\updates\foo_input_hvl"
del /Q "K:\foobar2000\updates\foo_input_hvl.zip"

"K:\foobar2000\7z" x -y -o"K:\foobar2000\updates\foo_input_monkey" "K:\foobar2000\updates\foo_input_monkey_2.1.4.zip"
md "K:\foobar2000\components"
move /Y "K:\foobar2000\updates\foo_input_monkey\foo_input_monkey.dll" "K:\foobar2000\components\foo_input_monkey.dll"
rd /S /Q "K:\foobar2000\updates\foo_input_monkey"
del /Q "K:\foobar2000\updates\foo_input_monkey_2.1.4.zip"

"K:\foobar2000\7z" x -y -o"K:\foobar2000\updates\foo_jesus" "K:\foobar2000\updates\foo_jesus-v8.zip"
md "K:\foobar2000\components"
move /Y "K:\foobar2000\updates\foo_jesus\foo_jesus.dll" "K:\foobar2000\components\foo_jesus.dll"
rd /S /Q "K:\foobar2000\updates\foo_jesus"
del /Q "K:\foobar2000\updates\foo_jesus-v8.zip"

"K:\foobar2000\7z" x -y -o"K:\foobar2000\updates\foo_masstag" "K:\foobar2000\updates\foo_masstag_1.8.4.zip"
md "K:\foobar2000\components"
move /Y "K:\foobar2000\updates\foo_masstag\foo_masstag.dll" "K:\foobar2000\components\foo_masstag.dll"
rd /S /Q "K:\foobar2000\updates\foo_masstag"
del /Q "K:\foobar2000\updates\foo_masstag_1.8.4.zip"

"K:\foobar2000\7z" x -y -o"K:\foobar2000\updates\foo_midi" "K:\foobar2000\updates\foo_midi.zip"
md "K:\foobar2000\components"
move /Y "K:\foobar2000\updates\foo_midi\foo_midi.dll" "K:\foobar2000\components\foo_midi.dll"
rd /S /Q "K:\foobar2000\updates\foo_midi"
del /Q "K:\foobar2000\updates\foo_midi.zip"

"K:\foobar2000\7z" x -y -o"K:\foobar2000\updates\foo_musicbrainz" "K:\foobar2000\updates\foo_musicbrainz-0.2-20090410.7z"
md "K:\foobar2000\components"
move /Y "K:\foobar2000\updates\foo_musicbrainz\foo_musicbrainz.dll" "K:\foobar2000\components\foo_musicbrainz.dll"
rd /S /Q "K:\foobar2000\updates\foo_musicbrainz"
del /Q "K:\foobar2000\updates\foo_musicbrainz-0.2-20090410.7z"

"K:\foobar2000\7z" x -y -o"K:\foobar2000\updates\foo_out_wasapi" "K:\foobar2000\updates\foo_out_wasapi_2.1.zip"
md "K:\foobar2000\components"
move /Y "K:\foobar2000\updates\foo_out_wasapi\foo_out_wasapi.dll" "K:\foobar2000\components\foo_out_wasapi.dll"
rd /S /Q "K:\foobar2000\updates\foo_out_wasapi"
del /Q "K:\foobar2000\updates\foo_out_wasapi_2.1.zip"

"K:\foobar2000\7z" x -y -o"K:\foobar2000\updates\foo_quicktag" "K:\foobar2000\updates\foo_quicktag_1.0.2.zip"
md "K:\foobar2000\components"
move /Y "K:\foobar2000\updates\foo_quicktag\foo_quicktag.dll" "K:\foobar2000\components\foo_quicktag.dll"
rd /S /Q "K:\foobar2000\updates\foo_quicktag"
del /Q "K:\foobar2000\updates\foo_quicktag_1.0.2.zip"

"K:\foobar2000\7z" x -y -o"K:\foobar2000\updates\foo_ui_columns" "K:\foobar2000\updates\foo_ui_columns-0.3.8.3.7z"
md "K:\foobar2000\components"
move /Y "K:\foobar2000\updates\foo_ui_columns\foo_ui_columns.dll" "K:\foobar2000\components\foo_ui_columns.dll"
rd /S /Q "K:\foobar2000\updates\foo_ui_columns"
del /Q "K:\foobar2000\updates\foo_ui_columns-0.3.8.3.7z"

"K:\foobar2000\7z" x -y -o"K:\foobar2000\updates\foo_uie_albumlist" "K:\foobar2000\updates\foo_uie_albumlist-0.3.5.7z"
md "K:\foobar2000\components"
move /Y "K:\foobar2000\updates\foo_uie_albumlist\foo_uie_albumlist.dll" "K:\foobar2000\components\foo_uie_albumlist.dll"
rd /S /Q "K:\foobar2000\updates\foo_uie_albumlist"
del /Q "K:\foobar2000\updates\foo_uie_albumlist-0.3.5.7z"

move /Y "K:\foobar2000\updates\foo_upnp.dll" "K:\foobar2000\components\foo_upnp.dll"
del /Q "K:\foobar2000\updates\foo_upnp.dll"

"K:\foobar2000\7z" x -y -o"K:\foobar2000\updates\foo_vis_shpeck" "K:\foobar2000\updates\foo_vis_shpeck-0.3.7.zip"
md "K:\foobar2000\components"
move /Y "K:\foobar2000\updates\foo_vis_shpeck\foo_vis_shpeck.dll" "K:\foobar2000\components\foo_vis_shpeck.dll"
rd /S /Q "K:\foobar2000\updates\foo_vis_shpeck"
del /Q "K:\foobar2000\updates\foo_vis_shpeck-0.3.7.zip"

"K:\foobar2000\7z" x -y -o"K:\foobar2000\updates\foo_wave_seekbar" "K:\foobar2000\updates\foo_wave_seekbar_0.1.10.7z"
md "K:\foobar2000\components"
move /Y "K:\foobar2000\updates\foo_wave_seekbar\components\foo_wave_seekbar.dll" "K:\foobar2000\components\foo_wave_seekbar.dll"
md "K:\foobar2000\effects"
move /Y "K:\foobar2000\updates\foo_wave_seekbar\effects\seekbar.fx" "K:\foobar2000\effects\seekbar.fx"
rd /S /Q "K:\foobar2000\updates\foo_wave_seekbar"
del /Q "K:\foobar2000\updates\foo_wave_seekbar_0.1.10.7z"

"K:\foobar2000\7z" x -y -o"K:\foobar2000\updates\foo_wlm" "K:\foobar2000\updates\foo_wlm_1.1.3.zip"
md "K:\foobar2000\components"
move /Y "K:\foobar2000\updates\foo_wlm\foo_wlm.dll" "K:\foobar2000\components\foo_wlm.dll"
rd /S /Q "K:\foobar2000\updates\foo_wlm"
del /Q "K:\foobar2000\updates\foo_wlm_1.1.3.zip"

echo.
echo Update complete.

If you open up a command prompt and run the update.bat file, what does it output?

Could you also please try downloading and installing a single component to see if the same issue is occurring?

foobar2000 was not closed when the batch-file ran, which prevented it from replacing the .DLLs.

I closed the window and the batch-file ran before foobar2000 shut down.

Thanks for the feedback. I was thinking that may have been the case. I'll add a longer delay between foobar2000 shutting down and the batch file executing.

Thanks for the feedback. I was thinking that may have been the case. I'll add a longer delay between foobar2000 shutting down and the batch file executing.

You may check if the foobar2000 is running in the batch file in this way:

tasklist /nh /fi "IMAGENAME eq foobar2000.exe" 2>nul | findstr /i /b foobar2000.exe >nul 2>&1
if not ERRORLEVEL 1 echo foobar2000 is running

Thanks for that  Heheh I was just looking at using tasklist to do such a thing.

I assume I can't update update.bat myself manually by adding one extra line of code that checks if foobar2000 is running? It's generated automatically, right?

Wouldn't it be better to use PID? I hear people run more than one instance of foobar2000.exe at the time.

You could manually edit it after the updates have been downloaded (which is when the batch file is generated), but before closing foobar2000. Or you can just download the components and run the batch file manually after closing foobar2000.

You raise a good point Yirkha. PID does make more sense to use.

Version 0.1.4 is out and fixes a few more things. The next priority is to handle compressed xml files, as the xml file is getting a bit chubby with all the components being added to it.

On that note, I've searched all of the main component websites and developer pages for components and have been studiously adding them to the update list. If you have any exotic/lesser known components that aren't in the xml file, let me know and I'll be sure to add them.

1: thanks for this component
components: foo_dsp_fsurround, foo_channel_mixer, foo_7taskbar, foo_msnalt

foo_customdb (http://blog.99ravens.net/index.php?e=283), foo_dsp_continuator, foo_new_file_stamper (http://www.hydrogenaudio.org/forums/index.php?showtopic=68139), foo_playlist_attributes (http://www.hydrogenaudio.org/forums/index.php?showtopic=73783), foo_preview (http://74.125.77.132/search?q=cache:http://skipyrich.com/wiki/), foo_preview_custom (http://kitahei.cocolog-nifty.com/youyou/2009/09/foo_preview_cus.html), foo_skip is special - I don't have the official one (http://www.hydrogenaudio.org/forums/index.php?showtopic=30361&view=findpost&p=264060), but a modified version implemented as DSP by Case (http://www.hydrogenaudio.org/forums/index.php?showtopic=77818&view=findpost&p=680561).

Then there are components which becomes obsolete, like foo_uie_vis_peakmeter.

bug: foobar crashes because the downloader cannot find http://www.skipyrich.com/store/foo_channel_mixer.7z (http://www.skipyrich.com/store/foo_channel_mixer.7z) (link doesn't resolve)

foo_queuecontents
http://www.hydrogenaudio.org/forums/index....showtopic=73648 (http://www.hydrogenaudio.org/forums/index.php?showtopic=73648)
http://sites.google.com/site/salskisite/foo_queuecontents (http://sites.google.com/site/salskisite/foo_queuecontents)

foo_uie_trackinfo_mod
http://www.hydrogenaudio.org/forums/index....showtopic=47044 (http://www.hydrogenaudio.org/forums/index.php?showtopic=47044)

foo_uie_quicksearch
http://www.hydrogenaudio.org/forums/index....showtopic=44012 (http://www.hydrogenaudio.org/forums/index.php?showtopic=44012)
http://thx538.free.fr/Foobar/Quicksearch%20V2.x/ (http://thx538.free.fr/Foobar/Quicksearch%20V2.x/)

foo_dsp_vlevel
http://www.hydrogenaudio.org/forums/index....showtopic=22057 (http://www.hydrogenaudio.org/forums/index.php?showtopic=22057)
http://vlevel.sourceforge.net/about/ (http://vlevel.sourceforge.net/about/)

foo_dsp_vstwrap (George Yohng's VST Wrapper)
http://www.hydrogenaudio.org/forums/index....showtopic=59206 (http://www.hydrogenaudio.org/forums/index.php?showtopic=59206)

foo_uie_tabs
http://www.hydrogenaudio.org/forums/index....showtopic=28869 (http://www.hydrogenaudio.org/forums/index.php?showtopic=28869)

The remaining ones in my "Not found in XML list"

Thanks for a great component fraganator.

When I first tried this I shed a tear... for all the update orgies done manually done in the past years. Really a great component. Thanks.

Bug: when trying to update foo_uie_vis_channel_spectrum from 0.14 to 0.17.2, the new dll erroneously replaces foo_abx

Thanks for the feedback. I was thinking that may have been the case. I'll add a longer delay between foobar2000 shutting down and the batch file executing.

can't "running" file help?

depending of foobar installation:

goto exec
:wait
ping 127.0.0.1 -n 1 -w 1000 > nul
:exec
if exist "%appdata%\foobar2000\running" goto wait

bug: foobar crashes because the downloader cannot find http://www.skipyrich.com/store/foo_channel_mixer.7z (http://www.skipyrich.com/store/foo_channel_mixer.7z) (link doesn't resolve)

Which version of foo_component_manager did this happen with? It should have been fixed with 0.1.4. I did notice that link was very flaky when I tried to access it, so I might just host the file myself for the time being.

Bug: when trying to update foo_uie_vis_channel_spectrum from 0.14 to 0.17.2, the new dll erroneously replaces foo_abx

Fixed. That's what happens when you don't pay close attention when copying and pasting!

Quote from: boombaard on 2010-02-17 18:14:37

bug: foobar crashes because the downloader cannot find http://www.skipyrich.com/store/foo_channel_mixer.7z (http://www.skipyrich.com/store/foo_channel_mixer.7z) (link doesn't resolve)

Which version of foo_component_manager did this happen with? It should have been fixed with 0.1.4. I did notice that link was very flaky when I tried to access it, so I might just host the file myself for the time being.

Quote from: novembre on 2010-02-17 22:47:51

Bug: when trying to update foo_uie_vis_channel_spectrum from 0.14 to 0.17.2, the new dll erroneously replaces foo_abx

Fixed. That's what happens when you don't pay close attention when copying and pasting!

Ah, correct. I didn't think to update it manually because I was trying to update channelmixer and this component at the same time.

pls add
foo_cuefilter
foo_taskbar_gestures
foo_ui_hacks

foo_DeleteCurrent (http://www.hydrogenaudio.org/forums/index.php?showtopic=53305) is the only component still missing in my case.

You know, there are the unofficial repository here (http://pelit.koillismaa.fi/plugins/), right? Updating every single component manually must be quite trivial... Maybe an open common repository would force developers to put more attention to components and possible problems?

Another thing that would be cool, is notification of new components and possible a list of all available components. This could create a larger user base for many interesting components.

I get "XML file out of date" for some components... foo_osd, foo_playlist_attributes, foo_random_pools ...???

I'm still missing the following components.

foo_dsp_bs2b, foo_exvar, foo_playback_custom, foo_twitter_post, foo_uie_explorer, foo_uie_graphical_browser

Some might be out of development though.

I get "XML file out of date" for some components... foo_osd, foo_playlist_attributes, foo_random_pools ...???

What version numbers are displayed for each of those (installed/available)? As far as I can tell the latest versions are in the xml file:
foo_osd (http://www.foobar2000.org/components/view/foo_osd) - 1.6
foo_playlist_attributes (http://www.hydrogenaudio.org/forums/index.php?showtopic=73783) - 0.2.2
foo_random_pools (http://www.hydrogenaudio.org/forums/index.php?showtopic=77460) - 0.0.1
It's been difficult to track down the latest versions of some components as their download links are scattered across posts/threads/developers (foo_winamp_spam for example), but the above ones should be pretty accurate.

I've come across a number of component repositories online (for example here (http://chron.visiondesigns.de/scripts/fb-components/list-lua.php5) and here (http://wiki.hydrogenaudio.org/index.php?title=Foobar2000:Component_Repository)), and although quite complete, unfortunately don't seem to be updated on a regular basis. The wiki at http://foobar2000.xrea.jp/ (http://foobar2000.xrea.jp/) seems to be maintained daily, but doesn't cover all components. I've found visiting developer's homepages the best way to stay up to date, and then update the xml data accordingly. I've been building up a list of developer/component pages for which I'll write a basic parser to automatically download and check them for changes, which will let me know if they've been updated at all. I'll still manually add the data to the xml file though.

I'm hoping one day foobar2000 will offer a centralised component repository, and make it simple for developers to add to it through the SDK. This is something I think Apple did really well with the iPhone and AppStore (limitations and restrictions aside). I'm not saying I want foobar2000 to go down that exact path, but making finding new components and maintaining current components should be much simpler for users than sifting through numerous forums and webpages. Until then though, this is how things are being done

New version works as expected. Thank you.

foo_osd (http://www.foobar2000.org/components/view/foo_osd) - Installed: 1.52, Latest: 1.6
foo_playlist_attributes (http://www.hydrogenaudio.org/forums/index.php?showtopic=73783) - Installed: 0.2.2 [Nov 16 2009 - 20:33:31], Latest: 0.2.2
foo_random_pools (http://www.hydrogenaudio.org/forums/index.php?showtopic=77460) - Installed: 0.0.1 [Dec 27 2009 - 18:22:23], Latest: 0.0.1

I wonder if the date is causing trouble?

You're welcome Canar

Yep, it is the dates. The version comparison function is seeing those extra numbers and reports it as being newer (so 0.0.1 [Dec 27 2009 - 18:22:23] is greater than 0.0.1). I'll need to strip out the dates (which a surprising number of components seem to have) before doing the comparison. As for foo_osd, version 1.52 is seen as newer than 1.6 because 52 is larger than 6. Really the numbering is more like 1.5.2, but it's impossible to derive that from the number alone. I guess I could try doing some other checks, like if the two versions are within some threshold of each other, but that's just guess work. Another reason for a standardised repository SDK!

but it's impossible to derive that from the number alone.

How about dates, then?  You could probably keep a pseudo-date if you don't know the real release date?

I noticed that you require elevation on update even when my user has full write access to foobar directory (running Windows 7). Also the extracted files had Administrator as the owner instead of me.

foo_uie_vis_peakmeter_spectrum (http://www.hydrogenaudio.org/forums/index.php?showtopic=61145&st=0&p=546448&#entry546448)

Seeing as how you're keeping an index of all the components anyhow, perhaps you could keep an index of all the versions as well? If you keep the list ordered, it should be simple to determine which version is newer.

Seeing as how you're keeping an index of all the components anyhow, perhaps you could keep an index of all the versions as well? If you keep the list ordered, it should be simple to determine which version is newer.

Doesn't it already do that? I noticed for continuator, that multiple versions were listed in the dropdown.

Would be nice to be able to enforce a certain version to be installed.

For better testing i used an old portable foobar installation (after updating 1.0) that contains much outdated components. That looks very good and impressive! Thanks!

However, here some results:

1. After pressing "download and install" and downloading all the new components i restarted foobar by main menu -< restart.  I saw a command prompt window for a few seconds and foobar restarted but no component was updated. I repeated the procedure but now i closed foobar. That seemed to help: Almost all was updated.

2. There are three components i can't update although they seemed to be downloaded. I tried it several times.
[blockquote]foo_tradersfriend 0.7 -> 0.7.1
foo_podcatcher 0.0.2 (alpha) -> 0.1.5f
foo_lastfm_radio 0.5 -> 0.5.7e[/blockquote]

(http://img705.imageshack.us/img705/9074/foobar2.png)

An official central repository and an official naming/versioning convention would make things much easier. But if they go through that much trouble then they might just as well put the updater into fb2k itself

2. There are three components i can't update although they seemed to be downloaded. I tried it several times.
foo_podcatcher 0.0.2 (alpha) -> 0.1.5f

foo_podcatcher is downloading the html file linking to the seperate components for foobar 1.0 and 0.9.6 instead of the actual component.

I'm hoping one day foobar2000 will offer a centralised component repository, and make it simple for developers to add to it through the SDK. This is something I think Apple did really well with the iPhone and AppStore (limitations and restrictions aside). I'm not saying I want foobar2000 to go down that exact path, but making finding new components and maintaining current components should be much simpler for users than sifting through numerous forums and webpages. Until then though, this is how things are being done

Or just how it works for firefox. The update mechanism is from the end user point of view simple to use and the system is always up-to-date + quick search capabilities for new components.

These are the ones that are reported (I don't necessarily know if these are latest versions)

Not found in the xml list:
foo_comserver2 (http://www.hydrogenaudio.org/forums/index.php?showtopic=39946&pid=358355&mode=threaded&show=&st=0) 0.7 alpha 6
foo_covers2 (http://www.hydrogenaudio.org/forums/index.php?showtopic=71446) 0.06
foo_dockable_panels 1.9.7b no official link
foo_lyricsdb (http://lyrics.mirkforce.net/) 0.0.8 beta 0
foo_input_flv (http://foo2k.chottu.net/) 0.1
foo_playback_custom (http://kitahei.cocolog-nifty.com/youyou/2007/04/foo_custominfo__6ab8.html) 1.5.1
foo_prettypop (http://www.maroonspoon.com/foo_prettypop/) 1.2.4
foo_stopaftercuralbum (http://www.hydrogenaudio.org/forums/index.php?showtopic=72420) 0.2
foo_twitterpost (http://kitahei.cocolog-nifty.com/youyou/2007/04/foo_custominfo__6ab8.html) 1.8.1
foo_ui_graphical_browser rev015 (http://www.hydrogenaudio.org/forums/index.php?showtopic=61412)

XML File out of date:
foo_osd (http://kode54.foobar2000.org/) 1.6

Cheers,

Chris

not found in xml list:

foo_lyricsgrabber

http://www.hydrogenaudio.org/forums/index....showtopic=62821 (http://www.hydrogenaudio.org/forums/index.php?showtopic=62821)
http://code.google.com/p/lyricsgrabber/downloads/list (http://code.google.com/p/lyricsgrabber/downloads/list)

foo_playlist_revive
http://www.hydrogenaudio.org/forums/index....showtopic=73910 (http://www.hydrogenaudio.org/forums/index.php?showtopic=73910)

Thank you to everyone who has reported issues and missing components

Some components are reporting versions differently to what their webpage shows, which is what I was using for the xml info. I'm now making sure to install every component and grabbing the version from there instead.

foo_tradersfriend 0.7 -> 0.7.1
foo_podcatcher 0.0.2 (alpha) -> 0.1.5f
foo_lastfm_radio 0.5 -> 0.5.7e

foo_trandersfriend is labelled as version 0.7.1 on the website, but reports 0.7 when installed (even though it's the 0.7.1 download). I've modified the xml so it matches the reported version.
foo_podcatcher and foo_lastfm_radio were only downloading the html of the homepage (as reported by ledge) and hence not updating, so I'm hosting the files myself.

An official central repository and an official naming/versioning convention would make things much easier. But if they go through that much trouble then they might just as well put the updater into fb2k itself

Or just how it works for firefox. The update mechanism is from the end user point of view simple to use and the system is always up-to-date + quick search capabilities for new components.

Agreed on both counts

(http://img269.imageshack.us/img269/6025/20100219102439.th.png) (http://img269.imageshack.us/i/20100219102439.png/)

A newer version was found, though not recognized as new.

First of all, thanks for this awesome component !!!

I want to report a bug:
While/after downloading of an update (foo_dop) foobar2000 crashes.
The next file would have been foo_dsp_bs2b.

My missing components:

foo_dsp_centercut (http://www.hydrogenaudio.org/forums/index.php?showtopic=46611)
foo_grabber_python (http://code.google.com/p/lyricsgrabber/)
foo_imgburner (http://www.hydrogenaudio.org/forums/index.php?showtopic=66681)
foo_lyricsdb (http://www.hydrogenaudio.org/forums/index.php?showtopic=36598)
foo_lyricsgrabber (http://code.google.com/p/lyricsgrabber/)
foo_prettypop (http://www.hydrogenaudio.org/forums/index.php?showtopic=33236)

Thanks!

Just wanted to say that this is an outstanding component. Thank you very much.

This component is absolutely fantastic, it really adds to the usability of foobar2000 .

Missing:
foo_lyricsdb (http://lyrics.mirkforce.net/)

[edit]
Ok, I'm blind, it was already reported.

missing components:

foo_dsp_crossfeed
foo_dsp_noise
foo_dsp_loudspeakereq
foo_dsp_ssrcX
foo_dsp_upmix
foo_dsp_xover
foo_input_tta
foo_normalprev
foo_playlists_sort
foo_version

I'm getting fb2k crashing when trying to update foo_input_tta

Try again now, it should be working.

Edit: Released version 0.1.5. Please see the first post on updating your settings to use the compressed xml file download. The changes to the version number handling should handle most versioning schemes, including alpha/beta/experimental/RC status, and mixtures of numbers and letters. Things like date and "(SSE)" are ignored.

Please keep the missing component requests coming in  I've added most of the requests, though a few are proving hard to find working versions/links for:
foo_input_flv
foo_dsp_ssrcX
foo_version

There are two different versions of CUE filter, under same filename:

foo_cuefilter: Cue sheet filter (http://yirkha.fud.cz/progs/foobar2000/foo_cuefilter.dll)
foo_cuefilter: CUE playlist filter (http://wintense.com/download/foo_cuefilter_017.zip)

which component doesn't recognize as separate, so i.e. reports I should update "Cue sheet filter" with "CUE playlist filter"

+ using foobar restart always fails with updating (as expected), instead exit should be used then start manually

I got almost all my components covered - great
except:
foo_dsp_winamp
foo_biometric
foo_dbsearch_api_demo (comes together with foo_dbsearch)
and the ones from user pro_optimizer

nevermind this request for something that is already there .

There are two different versions of CUE filter, under same filename:

Hmm, that's an interesting one. I'll have to change the way components are cross matched.

+ using foobar restart always fails with updating (as expected), instead exit should be used then start manually

This might be a silly question, but where is the Restart command? I don't seem to have it under the File menu:
[attachment=5741:foobar20...ile_menu.jpg]

Edit: Thanks Keesface

Shift-click the menu and you'll see it .

That was a quickfix! All fine now

When I use the component manager I got this error

Status: Error parsing XML due to unknown error.

I installed the 0.1.5 version, it's the first version I use

Status: Error parsing XML due to unknown error.

I get the same error with the latest version.

Cheers and thanks for the component

Alex

Thanks, the last version works pretty well. The only thing that bugs me is that it tells you to "restart" foobar, but if you use the restart command from the main menu (which I do a lot), it doesn't work because foobar restarts too fast. I don't know if it's possible, but maybe you can block the foobar2000.exe process to start before you update the component ? (edit : oops, it's already been said. )

I also have 2 obscure components not present in the XML :
- foo_7taskbar (http://www.foobar2000.com.cn/showtopic-7096.html)
- foo_textfile (http://blog.99ravens.net/index.php?e=282)

PS: Wow, and I learned that I wasn't even using the last version of my own component... ^^;

Quote

Status: Error parsing XML due to unknown error.

I get the same error with the latest version.

Cheers and thanks for the component

Alex

I get the same error. I'm using Windows 7 64-bit.

Great component!

I don't know if it's possible, but maybe you can block the foobar2000.exe process to start before you update the component ?

That seems brutal to me. I guess the most simple would be to tell the user to close foobar2000. Maybe it would be nice  if foobar would be started again automatically at the end of installing process. Something like: "close foobar and wait till it gets started"

I keep getting an error with this component: "Error parsing XML due to unknown error". What could be causing this ?

My apologies to everyone with the XML parsing error. It's due to the zipped xml file not decompressing fully before it is being parsed, which is causing the error. Please change the XML download location in the preferences to the uncompressed xml file: http://58.108.209.133/foo_auto_update.xml (http://58.108.209.133/foo_auto_update.xml)
I will work on a fix in the mean time. If you don't have any problems with the compressed xml, feel free to continue using it.

Changed to new URL; still getting parse error.

Could you post the error code that's printed in the console? I'm trying to reproduce the issue here but with no luck.

Edit: I was just updating the xml file, and you may have been downloading it as I replaced it. Please try updating again to see if that was the problem.

Edit 2: Is anyone not having problems with the compressed xml?

If URL is http://58.108.209.133/foo_component_manager.7z (http://58.108.209.133/foo_component_manager.7z) in error console

,e8W

If URL is http://58.108.209.133/foo_auto_update.xml (http://58.108.209.133/foo_auto_update.xml)

>
</installpath>
</release>

<release>
<component>
<name>Component Manager</name>
<version>0.1.0</version>
</component>
<date>2010-02-15</date>
<foobar2000version>1.0</foobar2000version>
<requirements>libexpatw.dll, 7z.exe, 7z.dll (included)</requirements>
<download>http://www.hydrogenaudio.org/forums/index.php?act=attach&amp;type=post&amp;id=5725</download>
<changelist>- Initial release</changelist>
<installpath>
<src>components\foo_component_manager.dll</src>
<dest>components\foo_component_manager.dll</dest>
</installpath>
<installpath>
<src>7z.exe</src>
<dest>7z.exe</dest>
</installpath>
<installpath>
<src>7z.dll</src>
<dest>7z.dll</dest>
</installpath>
<installpath>
<src>libexpatw.dll</src>
<dest>libexpatw.dll</dest>
</installpath>
</release>

</plugin>




</foo_component_manager>dest>
</installpath>
<installpath>
<src>libexpatw.dll</src>
<dest>libexpatw.dll</dest>
</installpath>
</release>

<release>
<component>
<name>Component Manager</name>
<version>0.1.4</version>
</component>
<date>2010-02-17</date>
<foobar2000version>1.0</foobar2000version>
<requirements>libexpatw.dll, 7z.exe, 7z.dll (included)</requirements>
<download>http://www.hydrogenaudio.org/forums/index.php?act=attach&amp;type=post&amp;id=5733</download>
<changelist>- Force batch file to wait on fb2k PID while it closes
- Broken download links now handled and reported to console</changelist>
<installpath>
<src>components\foo_component_manager.dll</src>
<dest>components\foo_component_manager.dll</dest>
</installpath>
<installpath>
<src>7z.exe</src>
<dest>7z.exe</dest>
</installpath>
<installpath>
<src>7z.dll</src>
<dest>7z.dll</dest>
</installpath>
<installpath>
<src>libexpatw.dll</src>
<dest>libexpatw.dll</dest>
</installpath>
</release>

<release>
<component>
<name>Component Manager</name>
<version>0.1.3</version>
</component>
<date>2010-02-17</date>
<foobar2000version>1.0</foobar2000version>
<requirements>libexpatw.dll, 7z.exe, 7z.dll (included)</requirements>
<download>http://www.hydrogenaudio.org/forums/index.php?act=attach&amp;type=post&amp;id=5731</download>
<changelist>- Added failure output file to aid debugging</changelist>
<installpath>
<src>components\foo_component_manager.dll</src>
<dest>components\foo_component_manager.dll</dest>
</installpath>
<installpath>
<src>7z.exe</src>
<dest>7z.exe</dest>
</installpath>
<installpath>
<src>7z.dll</src>
<dest>7z.dll</dest>
</installpath>
<installpath>
<src>libexpatw.dll</src>
<dest>libexpatw.dll</dest>
</installpath>
</release>

<release>
<component>
<name>Component Manager</name>
<version>0.1.2</version>
</component>
<date>2010-02-17</date>
<foobar2000version>1.0</foobar2000version>
<requirements>libexpatw.dll, 7z.exe, 7z.dll (included)</requirements>
<download>http://www.hydrogenaudio.org/forums/index.php?act=attach&amp;type=post&amp;id=5728</download>
<changelist>- Batch file path fixes
- Don't mark core components as missing from xml</changelist>
<installpath>
<src>components\foo_component_manager.dll</src>
<dest>components\foo_component_manager.dll</dest>
</installpath>
<installpath>
<src>7z.exe</src>
<dest>7z.exe</dest>
</installpath>
<installpath>
<src>7z.dll</src>
<dest>7z.dll</dest>
</installpath>
<installpath>
<src>libexpatw.dll</src>
<dest>libexpatw.dll</dest>
</installpath>
</release>

<release>
<component>
<name>Component Manager</name>
<version>0.1.1</version>
</component>
<date>2010-02-16</date>
<foobar2000version>1.0</foobar2000version>
<requirements>libexpatw.dll, 7z.exe, 7z.dll (included)</requirements>
<download>http://www.hydrogenaudio.org/forums/index.php?act=attach&amp;type=post&amp;id=5726</download>
<changelist>- Glaringly obvious user access control fix
- Components now downloaded to fb2k profile path
- All directories in batch file are absolute</changelist>
<installpath>
<src>components\foo_component_manager.dll</src>
<dest>components\foo_component_manager.dll</dest>
</installpath>
<installpath>
<src>7z.exe</src>
<dest>7z.exe</dest>
</installpath>
<installpath>
<src>7z.dll</src>
<dest>7z.dll</dest>
</installpath>
<installpath>
<src>libexpatw.dll</src>
<dest>libexpatw.dll</deste -y -o"C:\fb2k\updates" "C:\fb2k\updates\foo_auto_update.xml"
XML error is 3

I can confirm I get the same error with both links....worked earlier today with the xml link, but got the error with the compressed one.

Can someone please grab the console output for this debug build for both 7z and xml cases and send the results to me? There's a lot of output, so you may have to set the console to write to disk log first.

[attachment=5744:foo_comp....5_debug.7z]

Edit: Sorry all, this is turning into a bit of a saga. If you're experiencing the xml issues with version 0.1.5, please download 0.1.5.1. It uses the previous xml downloading/parsing code so should work as before.

Edit 2: Thanks to traxy for pinpointing the problem.

It seems that the "parsing error" only occurs if the "updates" subfolder is missing. After manually creating that folder, the error is gone and the XML gets parsed.

Thank you traxy! I thought I was going crazy there... I'll upload the fixed version in a moment.

Edit: OK, version 0.1.5.2 has been uploaded and should address the xml parsing errors. Thanks everyone for their patience.

Glad I could help. Version 0.1.5.2 works like a charm now.
Btw, thank you for this great component!

Wow, fast fix; works great now.  Thank you for your hard work on this component!

Please keep the missing component requests coming in  I've added most of the requests, though a few are proving hard to find working versions/links for:
foo_input_flv
foo_dsp_ssrcX
foo_version

foo_version (http://www.crystalidea.com/foobar2000-plugins)
foo_dsp_ssrcX (http://audiophilesoft.ucoz.ua/load/audiophilesoftware/foobar2000/3-1-0-5#plugins)

Big thanks for that coponent. The funny thing is that about 2 weeks ago i wondered why such feature is still missing in foobar 

You can add foo_adpcm from  http://kode54.foobar2000.org/ (http://kode54.foobar2000.org/)  and it will be all for me.

I am missing an update for foo_input_ac3 and foo_cdartdisplay

foo_version (http://www.crystalidea.com/foobar2000-plugins)
foo_dsp_ssrcX (http://audiophilesoft.ucoz.ua/load/audiophilesoftware/foobar2000/3-1-0-5#plugins)

Thanks  They've now been added.

You can add foo_adpcm from  http://kode54.foobar2000.org/ (http://kode54.foobar2000.org/)  and it will be all for me.

This one's a little tricky as multiple components have been declared in the one dll file, and component names have changed between dll file versions. Once I've figured out a way to handle it, it'll be added to the list.

I am missing an update for foo_input_ac3 and foo_cdartdisplay

I've added foo_cdartdisplay, but couldn't find foo_input_ac3. You may want to check out the alternative foo_ac3 (http://kode54.foobar2000.org/) as it's still actively developed.

I've added foo_cdartdisplay, but couldn't find foo_input_ac3. You may want to check out the alternative foo_ac3 (http://kode54.foobar2000.org/) as it's still actively developed.

thanks and great work

for more complete information: his name is kitahei! 

http://kitahei.cocolog-nifty.com/youyou/20...info__6ab8.html (http://kitahei.cocolog-nifty.com/youyou/2007/04/foo_custominfo__6ab8.html)

an the discussions threads are here (http://www.hydrogenaudio.org/forums/index.php?act=Search&nav=au&CODE=show&searchid=c3200633e8ca7a7141f219bfa54fb52d&search_in=topics&result_type=topics)

Please make the component's update windows smaller, so I can use it on my 1024x600 netbook.

Hello everybody

This seems to be a wonderful component, but I can't yet get it working! Download of new components works alright, but everytime I start the update.bat, It keeps saying "waiting for foobar2000 to shutdown". Of course, I've tried everything to really shut f2k down, but the batch file just won't execute. What am I doing wrong?

Tx
Copland

The batch file will wait for the Process ID (PID) of foobar2000.exe to finish before it starts executing. So foobar2000.exe must be still running in the background somewhere, even though you've closed it.

Firstly double check foobar2000.exe isn't running using the task manager under the Processes tab. If it is, select it and click End Process, then manually run the update.bat file.

If foobar2000.exe definitely is closed, open update.bat using Notepad (right-click it and choose Edit). Find the line tasklist /nh /fi "PID eq 6004" 2>nul | findstr /i /b foobar2000.exe >nul 2>&1 near the top of the file. We're interested in the number in bold. It will be a different number for you than shown here. Make a note of the number, then open a command prompt (Start->Programs->Accessories->Command Prompt). Type in the following (including the double quotes):

tasklist /FI "PID eq 6004"

where the number in bold is the same number from your update.bat file. What is the Image Name associated with that PID? If you get a message saying something like "No tasks are running that match the criteria", then something else is going on which I can't pin-point off the top of my head.

http://www.hydrogenaudio.org/forums/index....showtopic=75813 (http://www.hydrogenaudio.org/forums/index.php?showtopic=75813)

Another update is out, 0.1.5.3.

If developers want download traffic directed to their webpage (for ad-clicks etc), their components won't be automatically downloaded. Instead, once all the other components have been downloaded, a window is displayed with a set of links to the remaining components.

When the updated components are downloaded manually they can still be saved to the updates folder, and will automatically be installed when foobar2000 is next closed.

Type in the following (including the double quotes):

tasklist /FI "PID eq 6004"

I realized that I did not have the "tasklist.exe" in my windows xp home. After I'd downloaded it and placed it in my system32 folder, I could execute the command. After this, although the response was something like "search filter not recognized", the automatic update in f2k worked alright (and it does ever since!).

So, though I don't understand why it works, thank you for your help!

Thanks, 0.1.5.3 finally works for me using Win 7 64....neat

Did notice the updated components now have a lock overlaid the icon. Not sure what its supposed to indicate.

Case picked up on that earlier with files being owned by the Administrator user. I hope to rectify this with the next version.

What wasn't working for you earlier?

Interesting error:  updated foo_component_manager (to 0.1.5.3) while logged in to Admin account (MS Windows Vista Ultimate SP2), restarted Foobar2000, then switched to User account, opened Foobar2000 and got:

Failed to load DLL: foo_component_manager.dll
Reason: Access denied

Not sure what happened; worked fine before (0.1.5.2) - any ideas?

Foobar2000 v1.0

Reproducible even after reboot and only logged in to user account.

Thanks for the feedback. I'd say it's related to the issue above, in that I'm not correctly elevating permissions. If you look at the properties of a file with the lock icon (foo_component_manager.dll) and one without the lock icon and compare the users under the security tab, you'll notice the file with the lock icon does not have the generic 'Users' account. This account provides read access for all users on your machine. Seeing as the Users account no longer has read permission, you get an error when foobar2000 tries to load the component.

To fix this, right-click foo_component_manager.dll (or any dll with the lock icon), then select the security tab. Click the Edit button, then click Add. Type "Users" (without the double quotes) into the box and hit OK. The little lock icon should now disappear.

I'll admit I'm not completely across UAC and the correct way to elevate permissions, so there's a bit of research to be done before I can fix the problem. Please bear with me.

No worries; I fully appreciate your work and am glad to help.

FYI - I went to all dll's in the foo_component_manager 7z package that are installed in "Program Files/Foobar2000", added type = "Users" and then added "Full Control" under "Permissions" for each one.

All works now.

Case picked up on that earlier with files being owned by the Administrator user. I hope to rectify this with the next version.

What wasn't working for you earlier

Of course, should have realised and no it hadn't worked at all till the last update with errors on the xml parsing. Thanks very much, it's a great component.

Version 0.1.6 is out. There's a few permissions/elevations fixes included.

Did notice the updated components now have a lock overlaid the icon. Not sure what its supposed to indicate.

Interesting error:  updated foo_component_manager (to 0.1.5.3) while logged in to Admin account (MS Windows Vista Ultimate SP2), restarted Foobar2000, then switched to User account, opened Foobar2000 and got:

Code: [Select]

Failed to load DLL: foo_component_manager.dll
Reason: Access denied

Reproducible even after reboot and only logged in to user account.

I eventually discovered that the lock icon appearing was a result of the batch file 'copy' command copying the source file's security settings over the destination's settings. The downloaded components are unzipped to the foobar2000 profile folder that lives within the user's directory (eg c:\Users\fraganator\AppData\roaming\foobar2000). Files placed within this folder by default don't have read access by the generic 'User' user. They were then being copied from there to the foobar2000 installation folder with only privileges for the current user. Hence the access denied error you received DigitalMan.

To fix the lock icons, you can simply re-download the affected components using the component manager and it will remove the offending files and replace them with files that have the correct attributes.

Small bug:  When using the arrow keys to navigate the update list, the selected item changes appropriately, but the list does not scroll.

Also, would it be possible to add a "Restart" command on the message box telling you to restart foobar?  I suppose it would just close foobar, and add a line to the end of the batch file to start foobar after the file copying is completed.  Thanks.

Hello,
I am verry sorry to bring this up again:
I am afraid both your components are flawed in this regart.
It is inpossible to use tab key or any other standart keyboard navigation command to navigate in the dialogs. It is even inpossible to activate links in the conponent links dialog using the keyboard.
Otherwise everything is great with this component. This is really very very serious accessibility problem.

And some minor discrepancies related to xml file:
Problem with the versioning...

Module: foo_seek_box; Name: Seek box; Installed Version: v0.0.1; Latest Version: 0.0.1; Status: XML file out of date

Components missing in the archive...

foo_input_ds.dll (http://haali.su/fb2k/foo_input_ds.dll)

Module: foo_input_ds; Name: DirectShow input; Installed Version: 0.1; Latest Version: -; Status: Not found in XML list

foo_amr (http://angelo.scene.pl/download,foo_amr_1_1_1.exe)

Module: foo_input_amr; Name: AMR input; Installed Version: 1.1.1; Latest Version: -; Status: Not found in XML list

Don't know if you can auto install this exe file.

This. Is. So. Awesome.

This may very well be the killer component that catapults foobar2000 popularity into the stratosphere. When I talk to people who do not use/like foobar one of the biggest complaints is there's no easy way to keep components up to date. Your component takes a process that would normally be quite time-consuming & deftly reduces it to a couple mouse clicks.

Bravo, kind sir. Bravo. Words cannot begin to describe the amount of appreciation I have for this component & your programming efforts.

You are my god. I bow before you. We're not worthy, Fraganator. I can't wait to see all the future improvements implemented and to have this merged into the foobar proper!

Probably the only thing that took me off guard when using the component was the inability to sort columns (by Status for instance).

BRAVO, GOOD SIR!

thanks for this fine component - i was just visiting the site in order to check for updates to my components, expecting to spend 30-45 minutes searching around. i saw this component, installed it, and within a minute or 3 had 8 components downloaded and updated without a hitch - thanks!

Quote from: sirDaniel on 2010-02-21 11:03:38

You can add foo_adpcm from  http://kode54.foobar2000.org/ (http://kode54.foobar2000.org/)  and it will be all for me.

This one's a little tricky as multiple components have been declared in the one dll file, and component names have changed between dll file versions. Once I've figured out a way to handle it, it'll be added to the list.

You could keep an overrides list, which contains the DLL name (no need to store the extension), the component name of the version info service we want to check, and optionally an override for the component name to match what's on the official repository or author's site:

"foo_adpcm", "kode's ADPCM decoders", "ADPCM decoders"
"foo_unpack_unix", "", "Unix archive support" <- blank, so pick the first one you see, I guess, since I keep them all in sync anyway

Oops, there, I've gone and given away one of Yirkha's trade secrets.

Also, I don't see what I did to component version info that was so bad. I changed the descriptions on a few of the components a few months ago, but I don't recall changing any of the name fields recently. Well, maybe the BRR, but I thought I changed that months ago, at least. Oh well.

I waited a long time for such a component, but sadly I can't get this to work.

It downloads the XML file, but just after that it says "Error parsing XML file due to unknown error" - console shows "foo_component_manager: XML error is 3"
Well the interesting part is that no update folder is created, neither in the foobar directory nor in the user profile / appData / ... directory. And Windows also cannot find the update xml file anywhere.
An earlier version of the component did download and parse the file fine, but then after clicking download or download and install it only got the files, but did not install any (same here: no update folder, no actual update files).
The reason behind this is probably the same as why it does not work anymore at all - It cannnot seem to find the files it downloads (if it actually does download any). I guess the earlier version did parse the XML file immediately after download without re-opening it (which the new version probably does to support zipped files).

I hope you can help me on this one, I can try provide more details or test a debug version if you like.

System:
- foobar 1.0
- foo_component_manager 0.1.6
- Windows Vista Home Premium 32bit
- UAC is disabled!

foxblock out

WSH panel mod is hosted on google code, and there are download feeds
I know some other components are hosted there or where feeds are provided, but not sure which
So maybe you can automatically update your XML list with XML response from project download page (code is simple), i.e. WSH panel has new version as of 25.02.2010 09:26

You could keep an overrides list, which contains the DLL name (no need to store the extension), the component name of the version info service we want to check, and optionally an override for the component name to match what's on the official repository or author's site.

Also, I don't see what I did to component version info that was so bad. I changed the descriptions on a few of the components a few months ago, but I don't recall changing any of the name fields recently. Well, maybe the BRR, but I thought I changed that months ago, at least. Oh well.

An override list sounds like a pretty good solution. Currently components are compared based on filename/version, but if more than one component is declared within a file, component names/versions are then compared. So an override list for older component names can easily be worked into here. Thanks for the input

I think it was the name change made to BRR (see the older version linked by bubbleguuum), though I don't see anything wrong with that. I just hadn't taken it into account when I first wrote the comparison/cross-checking method.

This old version (http://bubbleguuum.free.fr/foo_adpcm.dll) of foo_adpcm crashes the plugin just after "Status: Downloading XML data", probably when you enumerates plugins.

WSH panel mod is hosted on google code, and there are download feeds
I know some other components are hosted there or where feeds are provided, but not sure which
So maybe you can automatically update your XML list with XML response from project download page (code is simple), i.e. WSH panel has new version as of 25.02.2010 09:26

I was thinking exactly this for google code hosted components, I just hadn't got around to it. I've been keeping a list of what's hosted where and the best way to check the websites for updates. Most component sites don't provide an RSS feed, but do have a date of when the last component update was made. So I think the simplest solution there is to grab the html and parse out the dates, then check if they've been updated in the past couple of days or weeks. Or maybe even just compare cached versions of the webpages.

It downloads the XML file, but just after that it says "Error parsing XML file due to unknown error" - console shows "foo_component_manager: XML error is 3"
Well the interesting part is that no update folder is created, neither in the foobar directory nor in the user profile / appData / ... directory. And Windows also cannot find the update xml file anywhere.
An earlier version of the component did download and parse the file fine, but then after clicking download or download and install it only got the files, but did not install any (same here: no update folder, no actual update files).
The reason behind this is probably the same as why it does not work anymore at all - It cannnot seem to find the files it downloads (if it actually does download any). I guess the earlier version did parse the XML file immediately after download without re-opening it (which the new version probably does to support zipped files).

XML error 3 (XML_ERROR_NO_ELEMENTS in expat.h (http://expat.cvs.sourceforge.net/viewvc/expat/expat/lib/expat.h?revision=1.80&view=markup)) means no tags exist in the xml, which as you've discovered is due to the xml file not even existing. The older version of the component just fed the download straight into the parsing routine without the need to write to disk, so that'd be why it worked previously.

I'll create a debug build which reports the errors resulting from trying to create the updates folder, which is where I suspect things are going wrong.

Edit: Debug version attached.
Edit 2: Removed debug version

Great component.  Installed, told me foo_dop was out of date.  Updated with no problem

Two possible issues:

* How will this deal with components that wipe data?  I know foo_uie_lyrics2 had an update which wiped all previous preferences of the component.  Can you think of a way that will notify the user if their data will  be wiped in an upgrade?  I suppose having it listed in the changelog section is enough, just curious what others think.
* How is this invoked?  Does the program use any resources if not called?  (I ask since I have a huge library and things can already get slow from time to time and I'd rather not sacrifice _any_ performance for a convenience I will probably use one or twice a month.

For component updates that wipe/overwrite data, I think a flag indicating a major settings change has occurred since version x.x.x would be sufficient. If the user is then upgrading from a version older than that, they would be notified and asked for confirmation before downloading the update. What do others think?

The component code only runs when you select it from the menu. There are no hidden background threads or anything of that nature while foobar2000 is running. The only thing I will add in future is the ability to check for updates on startup, but that can be switched off and will only be a one time thing when foobar2000 first runs.

If the user is then upgrading from a version older than that, they would be notified and asked for confirmation before downloading the update. What do others think?

Just the same - dialog box

Are you reading all components release notes?
It could be difficult sometimes, I guess

Thanks for the debug version, the error is exactly as you had anticipated: It fails to create the updates directory (in the user / appData folder).
Strange enough, it also gives the "failed to create directory error" even after I already created that folder manually...
It also gives this error when trying to download the XML file: "foo_component_manager: Directory creation failed. Reason: 0"

I wonder what is causing this as I have UAC disabled, so missing admin rights should not be the problem. (I also tried "run with as admin" but this did not change anything)

Another thing I noticed:
The component crashed foobar when an invalid path to the xml file is specified.

foxblock out

EDIT: Changing configuration dir to foobar installation directory fixes this, guess it has to relate to read/write access after all.

Great component! Thanks

Missing one:

foo_filedate (http://www.hydrogenaudio.org/forums/index.php?showtopic=57384)

This works beautifully! thanks!

Hey there, I get a crash whenever I update. Here's the report on the error

<?xml version="1.0" encoding="UTF-16"?>
<DATABASE>
<EXE NAME="foobar2000.exe" FILTER="GRABMI_FILTER_PRIVACY">
	<MATCHING_FILE NAME="7z.dll" SIZE="726016" CHECKSUM="0x5F6491DE" BIN_FILE_VERSION="4.65.0.0" BIN_PRODUCT_VERSION="4.65.0.0" PRODUCT_VERSION="4.65" FILE_DESCRIPTION="7z Standalone Plugin" COMPANY_NAME="Igor Pavlov" PRODUCT_NAME="7-Zip" FILE_VERSION="4.65" ORIGINAL_FILENAME="7za.dll" INTERNAL_NAME="7za" LEGAL_COPYRIGHT="Copyright © 1999-2009 Igor Pavlov" VERFILEDATEHI="0x0" VERFILEDATELO="0x0" VERFILEOS="0x40004" VERFILETYPE="0x2" MODULE_TYPE="WIN32" PE_CHECKSUM="0x0" LINKER_VERSION="0x0" UPTO_BIN_FILE_VERSION="4.65.0.0" UPTO_BIN_PRODUCT_VERSION="4.65.0.0" LINK_DATE="02/03/2009 07:21:03" UPTO_LINK_DATE="02/03/2009 07:21:03" VER_LANGUAGE="English (United States) [0x409]" />
	<MATCHING_FILE NAME="7z.exe" SIZE="150016" CHECKSUM="0xF435BEAE" BIN_FILE_VERSION="4.65.0.0" BIN_PRODUCT_VERSION="4.65.0.0" PRODUCT_VERSION="4.65" FILE_DESCRIPTION="7-Zip Console" COMPANY_NAME="Igor Pavlov" PRODUCT_NAME="7-Zip" FILE_VERSION="4.65" ORIGINAL_FILENAME="7z.exe" INTERNAL_NAME="7z" LEGAL_COPYRIGHT="Copyright © 1999-2009 Igor Pavlov" VERFILEDATEHI="0x0" VERFILEDATELO="0x0" VERFILEOS="0x40004" VERFILETYPE="0x1" MODULE_TYPE="WIN32" PE_CHECKSUM="0x0" LINKER_VERSION="0x0" UPTO_BIN_FILE_VERSION="4.65.0.0" UPTO_BIN_PRODUCT_VERSION="4.65.0.0" LINK_DATE="02/03/2009 07:09:39" UPTO_LINK_DATE="02/03/2009 07:09:39" VER_LANGUAGE="English (United States) [0x409]" />
	<MATCHING_FILE NAME="foobar2000 Shell Associations Updater.exe" SIZE="82944" CHECKSUM="0x83E77B18" BIN_FILE_VERSION="1.0.0.0" BIN_PRODUCT_VERSION="0.9.6.0" PRODUCT_VERSION="0, 9, 6, 0" FILE_DESCRIPTION="foobar2000 Shell Associations Updater" PRODUCT_NAME="foobar2000" FILE_VERSION="1, 0, 0, 0" ORIGINAL_FILENAME="foobar2000 Shell Associations Updater.exe" INTERNAL_NAME="FileType" LEGAL_COPYRIGHT="Copyright © 2008 Peter Pawlowski" VERFILEDATEHI="0x0" VERFILEDATELO="0x0" VERFILEOS="0x4" VERFILETYPE="0x1" MODULE_TYPE="WIN32" PE_CHECKSUM="0x1B63B" LINKER_VERSION="0x0" UPTO_BIN_FILE_VERSION="1.0.0.0" UPTO_BIN_PRODUCT_VERSION="0.9.6.0" LINK_DATE="01/09/2010 11:43:00" UPTO_LINK_DATE="01/09/2010 11:43:00" VER_LANGUAGE="English (United States) [0x409]" />
	<MATCHING_FILE NAME="foobar2000.exe" SIZE="1777664" CHECKSUM="0x52778675" BIN_FILE_VERSION="1.0.0.0" BIN_PRODUCT_VERSION="1.0.0.0" PRODUCT_VERSION="1, 0, 0, 0" FILE_DESCRIPTION="foobar2000" PRODUCT_NAME="foobar2000 Application" FILE_VERSION="1, 0, 0, 0" ORIGINAL_FILENAME="foobar2000.exe" INTERNAL_NAME="foobar2000" LEGAL_COPYRIGHT="Copyright © 2001-2009 Peter Pawlowski" VERFILEDATEHI="0x0" VERFILEDATELO="0x0" VERFILEOS="0x4" VERFILETYPE="0x1" MODULE_TYPE="WIN32" PE_CHECKSUM="0x1B30D6" LINKER_VERSION="0x0" UPTO_BIN_FILE_VERSION="1.0.0.0" UPTO_BIN_PRODUCT_VERSION="1.0.0.0" LINK_DATE="01/09/2010 11:46:59" UPTO_LINK_DATE="01/09/2010 11:46:59" VER_LANGUAGE="English (United States) [0x409]" />
	<MATCHING_FILE NAME="lame.exe" SIZE="187392" CHECKSUM="0xAC5D41FE" MODULE_TYPE="WIN32" PE_CHECKSUM="0x0" LINKER_VERSION="0x0" LINK_DATE="12/22/2005 10:29:33" UPTO_LINK_DATE="12/22/2005 10:29:33" />
	<MATCHING_FILE NAME="libcurl.dll" SIZE="319488" CHECKSUM="0x3F48D406" MODULE_TYPE="WIN32" PE_CHECKSUM="0x4F319" LINKER_VERSION="0x0" LINK_DATE="03/19/2006 21:05:12" UPTO_LINK_DATE="03/19/2006 21:05:12" />
	<MATCHING_FILE NAME="libexpatw.dll" SIZE="151552" CHECKSUM="0x6AD92D54" MODULE_TYPE="WIN32" PE_CHECKSUM="0x2C083" LINKER_VERSION="0x0" LINK_DATE="06/05/2007 19:23:40" UPTO_LINK_DATE="06/05/2007 19:23:40" />
	<MATCHING_FILE NAME="libmmd.dll" SIZE="2814044" CHECKSUM="0x38345C3E" BIN_FILE_VERSION="9.1.9.2" BIN_PRODUCT_VERSION="0.0.0.0" PRODUCT_VERSION="9.1" FILE_DESCRIPTION="Math Library for Intel® Compilers (thread-safe)" COMPANY_NAME="Intel Corporation" PRODUCT_NAME="Intel® C Compiler, Intel® C++ Compiler, Intel® Fortran Compiler" FILE_VERSION="9.1.9.2" ORIGINAL_FILENAME="libmmd.dll" INTERNAL_NAME="libmmd.dll" LEGAL_COPYRIGHT="Copyright © 1985-2005 Intel Corporation" VERFILEDATEHI="0x0" VERFILEDATELO="0x0" VERFILEOS="0x0" VERFILETYPE="0x0" MODULE_TYPE="WIN32" PE_CHECKSUM="0x0" LINKER_VERSION="0x0" UPTO_BIN_FILE_VERSION="9.1.9.2" UPTO_BIN_PRODUCT_VERSION="0.0.0.0" LINK_DATE="02/16/2007 14:29:27" UPTO_LINK_DATE="02/16/2007 14:29:27" VER_LANGUAGE="English (United States) [0x409]" />
	<MATCHING_FILE NAME="libmzgc360_000.dll" SIZE="237568" CHECKSUM="0x22EC6684" MODULE_TYPE="WIN32" PE_CHECKSUM="0x3F515" LINKER_VERSION="0x0" LINK_DATE="11/20/2006 10:53:50" UPTO_LINK_DATE="11/20/2006 10:53:50" />
	<MATCHING_FILE NAME="libmzsch360_000.dll" SIZE="1757184" CHECKSUM="0xFB9B4D23" MODULE_TYPE="WIN32" PE_CHECKSUM="0x1AD82B" LINKER_VERSION="0x0" LINK_DATE="11/20/2006 10:54:53" UPTO_LINK_DATE="11/20/2006 10:54:53" />
	<MATCHING_FILE NAME="libpng13.dll" SIZE="114688" CHECKSUM="0x82473E79" BIN_FILE_VERSION="1.2.8.0" BIN_PRODUCT_VERSION="1.2.8.0" PRODUCT_VERSION="1" FILE_DESCRIPTION="PNG image compression library" PRODUCT_NAME="LibPNG" FILE_VERSION="1.2.8" ORIGINAL_FILENAME="LIBPNG13.DLL" INTERNAL_NAME="LIBPNG13 (Windows 32 bit)" LEGAL_COPYRIGHT="© 1998-2004 Glenn Randers-Pehrson et al." VERFILEDATEHI="0x0" VERFILEDATELO="0x0" VERFILEOS="0x4" VERFILETYPE="0x2" MODULE_TYPE="WIN32" PE_CHECKSUM="0x0" LINKER_VERSION="0x0" UPTO_BIN_FILE_VERSION="1.2.8.0" UPTO_BIN_PRODUCT_VERSION="1.2.8.0" LINK_DATE="12/23/2004 15:37:07" UPTO_LINK_DATE="12/23/2004 15:37:07" VER_LANGUAGE="English (United States) [0x409]" />
	<MATCHING_FILE NAME="NeroAACWrapper.exe" SIZE="106496" CHECKSUM="0x54456F6E" MODULE_TYPE="WIN32" PE_CHECKSUM="0x1E36C" LINKER_VERSION="0x0" LINK_DATE="04/22/2006 21:55:28" UPTO_LINK_DATE="04/22/2006 21:55:28" />
	<MATCHING_FILE NAME="shared.dll" SIZE="148480" CHECKSUM="0x304F3BA9" MODULE_TYPE="WIN32" PE_CHECKSUM="0x2DBEB" LINKER_VERSION="0x0" LINK_DATE="01/09/2010 11:42:56" UPTO_LINK_DATE="01/09/2010 11:42:56" />
	<MATCHING_FILE NAME="ShellExt32.dll" SIZE="108544" CHECKSUM="0x51195F19" BIN_FILE_VERSION="1.0.0.7" BIN_PRODUCT_VERSION="0.9.7.0" PRODUCT_VERSION="0.9.7" FILE_DESCRIPTION="foobar2000 shell extension" COMPANY_NAME="Peter Pawlowski" PRODUCT_NAME="foobar2000" FILE_VERSION="1.0.0.7" ORIGINAL_FILENAME="Fb2kShellExt.dll" INTERNAL_NAME="Fb2kShellExt.dll" LEGAL_COPYRIGHT="© Peter Pawlowski.  All rights reserved." VERFILEDATEHI="0x0" VERFILEDATELO="0x0" VERFILEOS="0x4" VERFILETYPE="0x2" MODULE_TYPE="WIN32" PE_CHECKSUM="0x24139" LINKER_VERSION="0x0" UPTO_BIN_FILE_VERSION="1.0.0.7" UPTO_BIN_PRODUCT_VERSION="0.9.7.0" LINK_DATE="05/27/2009 16:24:16" UPTO_LINK_DATE="05/27/2009 16:24:16" VER_LANGUAGE="English (United States) [0x409]" />
	<MATCHING_FILE NAME="uninst-audioscrobbler.exe" SIZE="47163" CHECKSUM="0x4BB19EFE" MODULE_TYPE="WIN32" PE_CHECKSUM="0x0" LINKER_VERSION="0x0" LINK_DATE="11/17/2007 14:35:28" UPTO_LINK_DATE="11/17/2007 14:35:28" />
	<MATCHING_FILE NAME="uninstall.exe" SIZE="147371" CHECKSUM="0x2A89D326" BIN_FILE_VERSION="1.0.0.0" BIN_PRODUCT_VERSION="1.0.0.0" PRODUCT_VERSION="1.0" FILE_DESCRIPTION="foobar2000 Installer" COMPANY_NAME="foobar2000.org" PRODUCT_NAME="foobar2000" FILE_VERSION="1.0" ORIGINAL_FILENAME="foobar2000_v1.0.exe" LEGAL_COPYRIGHT="� Peter Pawlowski. All rights reserved." VERFILEDATEHI="0x0" VERFILEDATELO="0x0" VERFILEOS="0x4" VERFILETYPE="0x1" MODULE_TYPE="WIN32" PE_CHECKSUM="0x0" LINKER_VERSION="0x60001" UPTO_BIN_FILE_VERSION="1.0.0.0" UPTO_BIN_PRODUCT_VERSION="1.0.0.0" LINK_DATE="09/09/2009 13:23:23" UPTO_LINK_DATE="09/09/2009 13:23:23" VER_LANGUAGE="Language Neutral [0x0]" />
	<MATCHING_FILE NAME="zlib1.dll" SIZE="73728" CHECKSUM="0x244B6C4A" BIN_FILE_VERSION="1.2.2.0" BIN_PRODUCT_VERSION="1.2.2.0" PRODUCT_VERSION="1.2.2" FILE_DESCRIPTION="zlib data compression library" PRODUCT_NAME="zlib" FILE_VERSION="1.2.2" ORIGINAL_FILENAME="zlib1.dll" INTERNAL_NAME="zlib1.dll" LEGAL_COPYRIGHT="© 1995-2004 Jean-loup Gailly &amp; Mark Adler" VERFILEDATEHI="0x0" VERFILEDATELO="0x0" VERFILEOS="0x10004" VERFILETYPE="0x2" MODULE_TYPE="WIN32" PE_CHECKSUM="0x0" LINKER_VERSION="0x0" UPTO_BIN_FILE_VERSION="1.2.2.0" UPTO_BIN_PRODUCT_VERSION="1.2.2.0" LINK_DATE="12/23/2004 15:36:24" UPTO_LINK_DATE="12/23/2004 15:36:24" VER_LANGUAGE="English (United States) [0x409]" />
	<MATCHING_FILE NAME="components\albumart.exe" SIZE="225280" CHECKSUM="0x4A23993F" BIN_FILE_VERSION="1.0.0.0" BIN_PRODUCT_VERSION="1.0.0.0" PRODUCT_VERSION="1.0.0.0" FILE_DESCRIPTION="Cover Art Downloader" COMPANY_NAME="Damage, Inc." PRODUCT_NAME="Cover Art Downloader" FILE_VERSION="1.0.0.0" ORIGINAL_FILENAME="albumart.exe" INTERNAL_NAME="albumart.exe" LEGAL_COPYRIGHT="Copyright © Damage, Inc. 2005" VERFILEDATEHI="0x0" VERFILEDATELO="0x0" VERFILEOS="0x4" VERFILETYPE="0x1" MODULE_TYPE="WIN32" PE_CHECKSUM="0x0" LINKER_VERSION="0x0" UPTO_BIN_FILE_VERSION="1.0.0.0" UPTO_BIN_PRODUCT_VERSION="1.0.0.0" LINK_DATE="09/22/2006 23:58:53" UPTO_LINK_DATE="09/22/2006 23:58:53" VER_LANGUAGE="Language Neutral [0x0]" />
	<MATCHING_FILE NAME="components\Boo.Lang.Compiler.dll" SIZE="552960" CHECKSUM="0x22FF572F" BIN_FILE_VERSION="1.0.0.0" BIN_PRODUCT_VERSION="1.0.0.0" PRODUCT_VERSION="1.0.0.0" FILE_DESCRIPTION="boo - an extensible programming language for the CLI" PRODUCT_NAME="boo - an extensible programming language for the CLI" FILE_VERSION="1.0.0.0" ORIGINAL_FILENAME="Boo.Lang.Compiler.dll" INTERNAL_NAME="Boo.Lang.Compiler.dll" LEGAL_COPYRIGHT="© 2003-2005 Rodrigo Barreto de Oliveira" VERFILEDATEHI="0x0" VERFILEDATELO="0x0" VERFILEOS="0x4" VERFILETYPE="0x2" MODULE_TYPE="WIN32" PE_CHECKSUM="0x95D58" LINKER_VERSION="0x0" UPTO_BIN_FILE_VERSION="1.0.0.0" UPTO_BIN_PRODUCT_VERSION="1.0.0.0" LINK_DATE="04/24/2006 16:08:52" UPTO_LINK_DATE="04/24/2006 16:08:52" VER_LANGUAGE="Language Neutral [0x0]" />
	<MATCHING_FILE NAME="components\Boo.Lang.dll" SIZE="69632" CHECKSUM="0xE9C8F42C" BIN_FILE_VERSION="1.0.0.0" BIN_PRODUCT_VERSION="1.0.0.0" PRODUCT_VERSION="1.0.0.0" FILE_DESCRIPTION="boo - an extensible programming language for the CLI" PRODUCT_NAME="boo - an extensible programming language for the CLI" FILE_VERSION="1.0.0.0" ORIGINAL_FILENAME="Boo.Lang.dll" INTERNAL_NAME="Boo.Lang.dll" LEGAL_COPYRIGHT="© 2003-2005 Rodrigo Barreto de Oliveira" VERFILEDATEHI="0x0" VERFILEDATELO="0x0" VERFILEOS="0x4" VERFILETYPE="0x2" MODULE_TYPE="WIN32" PE_CHECKSUM="0x1B48F" LINKER_VERSION="0x0" UPTO_BIN_FILE_VERSION="1.0.0.0" UPTO_BIN_PRODUCT_VERSION="1.0.0.0" LINK_DATE="04/24/2006 16:08:46" UPTO_LINK_DATE="04/24/2006 16:08:46" VER_LANGUAGE="Language Neutral [0x0]" />
	<MATCHING_FILE NAME="components\Boo.Lang.Parser.dll" SIZE="405504" CHECKSUM="0x2D6F1A82" BIN_FILE_VERSION="1.0.0.0" BIN_PRODUCT_VERSION="1.0.0.0" PRODUCT_VERSION="1.0.0.0" FILE_DESCRIPTION="boo antlr based parser" PRODUCT_NAME="boo - an extensible programming language for the CLI" FILE_VERSION="1.0.0.0" ORIGINAL_FILENAME="Boo.Lang.Parser.dll" INTERNAL_NAME="Boo.Lang.Parser.dll" LEGAL_COPYRIGHT="© 2003-2005 Rodrigo Barreto de Oliveira" VERFILEDATEHI="0x0" VERFILEDATELO="0x0" VERFILEOS="0x4" VERFILETYPE="0x2" MODULE_TYPE="WIN32" PE_CHECKSUM="0x6D415" LINKER_VERSION="0x0" UPTO_BIN_FILE_VERSION="1.0.0.0" UPTO_BIN_PRODUCT_VERSION="1.0.0.0" LINK_DATE="04/24/2006 16:09:01" UPTO_LINK_DATE="04/24/2006 16:09:01" VER_LANGUAGE="Language Neutral [0x0]" />
	<MATCHING_FILE NAME="components\Foobar2000DeskbandControls.dll" SIZE="32256" CHECKSUM="0x976DD48" MODULE_TYPE="WIN32" PE_CHECKSUM="0xA1AE" LINKER_VERSION="0x0" LINK_DATE="02/10/2010 20:54:10" UPTO_LINK_DATE="02/10/2010 20:54:10" />
	<MATCHING_FILE NAME="components\foo_abx.dll" SIZE="179712" CHECKSUM="0x52DBE10D" MODULE_TYPE="WIN32" PE_CHECKSUM="0x3221D" LINKER_VERSION="0x0" LINK_DATE="05/24/2008 15:23:51" UPTO_LINK_DATE="05/24/2008 15:23:51" />
	<MATCHING_FILE NAME="components\foo_ac3.dll" SIZE="169472" CHECKSUM="0x2BA1DD62" MODULE_TYPE="WIN32" PE_CHECKSUM="0x2DD9C" LINKER_VERSION="0x0" LINK_DATE="01/11/2010 19:18:38" UPTO_LINK_DATE="01/11/2010 19:18:38" />
	<MATCHING_FILE NAME="components\foo_audioscrobbler.dll" SIZE="187904" CHECKSUM="0x8D9F1EC" BIN_FILE_VERSION="1.4.6.0" BIN_PRODUCT_VERSION="1.4.6.0" PRODUCT_VERSION="1, 4, 6, 0" FILE_DESCRIPTION="foo_audioscrobbler" PRODUCT_NAME=" foo_audioscrobbler" FILE_VERSION="1, 4, 6, 0" ORIGINAL_FILENAME="foo_audioscrobbler.dll" INTERNAL_NAME="foo_audioscrobbler" LEGAL_COPYRIGHT="© 2006-2010 Florian Heidenreich" VERFILEDATEHI="0x0" VERFILEDATELO="0x0" VERFILEOS="0x4" VERFILETYPE="0x2" MODULE_TYPE="WIN32" PE_CHECKSUM="0x3914B" LINKER_VERSION="0x0" UPTO_BIN_FILE_VERSION="1.4.6.0" UPTO_BIN_PRODUCT_VERSION="1.4.6.0" LINK_DATE="02/07/2010 14:16:46" UPTO_LINK_DATE="02/07/2010 14:16:46" VER_LANGUAGE="English (United Kingdom) [0x809]" />
	<MATCHING_FILE NAME="components\foo_cdda.dll" SIZE="294400" CHECKSUM="0x755E6D6E" MODULE_TYPE="WIN32" PE_CHECKSUM="0x535E4" LINKER_VERSION="0x0" LINK_DATE="01/09/2010 11:44:41" UPTO_LINK_DATE="01/09/2010 11:44:41" />
	<MATCHING_FILE NAME="components\foo_component_manager.dll" SIZE="350720" CHECKSUM="0xFB67E782" MODULE_TYPE="WIN32" PE_CHECKSUM="0x55E62" LINKER_VERSION="0x0" LINK_DATE="02/24/2010 13:45:22" UPTO_LINK_DATE="02/24/2010 13:45:22" />
	<MATCHING_FILE NAME="components\foo_converter.dll" SIZE="438784" CHECKSUM="0xDAD673EE" MODULE_TYPE="WIN32" PE_CHECKSUM="0x713AE" LINKER_VERSION="0x0" LINK_DATE="01/09/2010 11:44:32" UPTO_LINK_DATE="01/09/2010 11:44:32" />
	<MATCHING_FILE NAME="components\foo_deskband_controls.dll" SIZE="26624" CHECKSUM="0xCF835478" MODULE_TYPE="WIN32" PE_CHECKSUM="0x8167" LINKER_VERSION="0x0" LINK_DATE="02/08/2010 19:20:30" UPTO_LINK_DATE="02/08/2010 19:20:30" />
	<MATCHING_FILE NAME="components\foo_dockable_panels.dll" SIZE="200704" CHECKSUM="0x4B0AE564" MODULE_TYPE="WIN32" PE_CHECKSUM="0x403E4" LINKER_VERSION="0x0" LINK_DATE="03/28/2007 13:19:00" UPTO_LINK_DATE="03/28/2007 13:19:00" />
	<MATCHING_FILE NAME="components\foo_dop.dll" SIZE="1691648" CHECKSUM="0x48DA7DF2" MODULE_TYPE="WIN32" PE_CHECKSUM="0x1A91F7" LINKER_VERSION="0x0" LINK_DATE="02/20/2010 19:51:11" UPTO_LINK_DATE="02/20/2010 19:51:11" />
	<MATCHING_FILE NAME="components\foo_dsp_continuator.dll" SIZE="94208" CHECKSUM="0xE58C57A9" MODULE_TYPE="WIN32" PE_CHECKSUM="0x1CA53" LINKER_VERSION="0x0" LINK_DATE="01/04/2008 19:13:13" UPTO_LINK_DATE="01/04/2008 19:13:13" />
	<MATCHING_FILE NAME="components\foo_dsp_crossfader.dll" SIZE="190464" CHECKSUM="0xAF9AB932" MODULE_TYPE="WIN32" PE_CHECKSUM="0x39F07" LINKER_VERSION="0x0" LINK_DATE="01/13/2010 13:46:08" UPTO_LINK_DATE="01/13/2010 13:46:08" />
	<MATCHING_FILE NAME="components\foo_dsp_silence.dll" SIZE="164352" CHECKSUM="0x3C8546CC" MODULE_TYPE="WIN32" PE_CHECKSUM="0x321B6" LINKER_VERSION="0x0" LINK_DATE="08/09/2009 23:32:53" UPTO_LINK_DATE="08/09/2009 23:32:53" />
	<MATCHING_FILE NAME="components\foo_dsp_std.dll" SIZE="280576" CHECKSUM="0x5B70DB19" MODULE_TYPE="WIN32" PE_CHECKSUM="0x49AAA" LINKER_VERSION="0x0" LINK_DATE="01/09/2010 11:44:47" UPTO_LINK_DATE="01/09/2010 11:44:47" />
	<MATCHING_FILE NAME="components\foo_facets.dll" SIZE="520192" CHECKSUM="0xB853ED4B" MODULE_TYPE="WIN32" PE_CHECKSUM="0x834A9" LINKER_VERSION="0x0" LINK_DATE="02/26/2008 00:56:40" UPTO_LINK_DATE="02/26/2008 00:56:40" />
	<MATCHING_FILE NAME="components\foo_filedate.dll" SIZE="131072" CHECKSUM="0xF8198C64" MODULE_TYPE="WIN32" PE_CHECKSUM="0x217AC" LINKER_VERSION="0x0" LINK_DATE="09/19/2007 11:07:14" UPTO_LINK_DATE="09/19/2007 11:07:14" />
	<MATCHING_FILE NAME="components\foo_fileops.dll" SIZE="276992" CHECKSUM="0xE44563EF" MODULE_TYPE="WIN32" PE_CHECKSUM="0x456E0" LINKER_VERSION="0x0" LINK_DATE="01/09/2010 11:43:30" UPTO_LINK_DATE="01/09/2010 11:43:30" />
	<MATCHING_FILE NAME="components\foo_freedb2.dll" SIZE="246272" CHECKSUM="0xB9476654" MODULE_TYPE="WIN32" PE_CHECKSUM="0x469E0" LINKER_VERSION="0x0" LINK_DATE="01/09/2010 11:43:34" UPTO_LINK_DATE="01/09/2010 11:43:34" />
	<MATCHING_FILE NAME="components\foo_input_monkey.dll" SIZE="272896" CHECKSUM="0xD461678B" MODULE_TYPE="WIN32" PE_CHECKSUM="0x4C9D6" LINKER_VERSION="0x0" LINK_DATE="05/01/2009 12:40:53" UPTO_LINK_DATE="05/01/2009 12:40:53" />
	<MATCHING_FILE NAME="components\foo_input_std.dll" SIZE="1337344" CHECKSUM="0x2336FBB0" MODULE_TYPE="WIN32" PE_CHECKSUM="0x152DEB" LINKER_VERSION="0x0" LINK_DATE="01/09/2010 11:44:22" UPTO_LINK_DATE="01/09/2010 11:44:22" />
	<MATCHING_FILE NAME="components\foo_jesus.dll" SIZE="138752" CHECKSUM="0x658DE157" MODULE_TYPE="WIN32" PE_CHECKSUM="0x2A467" LINKER_VERSION="0x0" LINK_DATE="01/03/2010 12:41:16" UPTO_LINK_DATE="01/03/2010 12:41:16" />
	<MATCHING_FILE NAME="components\foo_masstag.dll" SIZE="327680" CHECKSUM="0x9DEFC9F9" MODULE_TYPE="WIN32" PE_CHECKSUM="0x55187" LINKER_VERSION="0x0" LINK_DATE="09/18/2009 08:01:36" UPTO_LINK_DATE="09/18/2009 08:01:36" />
	<MATCHING_FILE NAME="components\foo_mouse_gesture.dll" SIZE="166912" CHECKSUM="0x46DF2FA8" BIN_FILE_VERSION="0.1.0.0" BIN_PRODUCT_VERSION="0.1.0.0" PRODUCT_VERSION="0, 1, 0, 0" FILE_VERSION="0, 1, 0, 0" ORIGINAL_FILENAME="foo_uie_panel_splitter.dll" VERFILEDATEHI="0x0" VERFILEDATELO="0x0" VERFILEOS="0x4" VERFILETYPE="0x2" MODULE_TYPE="WIN32" PE_CHECKSUM="0x2C4AA" LINKER_VERSION="0x0" UPTO_BIN_FILE_VERSION="0.1.0.0" UPTO_BIN_PRODUCT_VERSION="0.1.0.0" LINK_DATE="01/18/2010 12:20:00" UPTO_LINK_DATE="01/18/2010 12:20:00" VER_LANGUAGE="Japanese [0x411]" />
	<MATCHING_FILE NAME="components\foo_musicbrainz.dll" SIZE="360448" CHECKSUM="0x81116E97" MODULE_TYPE="WIN32" PE_CHECKSUM="0x5CC00" LINKER_VERSION="0x0" LINK_DATE="04/10/2009 20:27:27" UPTO_LINK_DATE="04/10/2009 20:27:27" />
	<MATCHING_FILE NAME="components\foo_navigator.dll" SIZE="195584" CHECKSUM="0xC6B29036" MODULE_TYPE="WIN32" PE_CHECKSUM="0x39165" LINKER_VERSION="0x0" LINK_DATE="02/20/2010 01:13:12" UPTO_LINK_DATE="02/20/2010 01:13:12" />
	<MATCHING_FILE NAME="components\foo_new_file_stamper_mod (2).dll" SIZE="145920" CHECKSUM="0x6F79E111" MODULE_TYPE="WIN32" PE_CHECKSUM="0x29563" LINKER_VERSION="0x0" LINK_DATE="12/21/2008 00:05:19" UPTO_LINK_DATE="12/21/2008 00:05:19" />
	<MATCHING_FILE NAME="components\foo_playlist_attributes.dll" SIZE="256000" CHECKSUM="0x9E462237" MODULE_TYPE="WIN32" PE_CHECKSUM="0x468F6" LINKER_VERSION="0x0" LINK_DATE="11/16/2009 19:33:44" UPTO_LINK_DATE="11/16/2009 19:33:44" />
	<MATCHING_FILE NAME="components\foo_prettypop.dll" SIZE="286208" CHECKSUM="0x4ED2D498" BIN_FILE_VERSION="1.2.5.0" BIN_PRODUCT_VERSION="1.2.5.0" PRODUCT_VERSION="1, 2, 5, 0" FILE_DESCRIPTION="Pretty Popup Plugin" PRODUCT_NAME="Pretty Popup" FILE_VERSION="1, 2, 5, 0" ORIGINAL_FILENAME="foo_prettypop.dll" INTERNAL_NAME="foo_prettypop.dll" LEGAL_COPYRIGHT="© 2005-9 Matt Witherspoon" VERFILEDATEHI="0x0" VERFILEDATELO="0x0" VERFILEOS="0x4" VERFILETYPE="0x2" MODULE_TYPE="WIN32" PE_CHECKSUM="0x49F3F" LINKER_VERSION="0x0" UPTO_BIN_FILE_VERSION="1.2.5.0" UPTO_BIN_PRODUCT_VERSION="1.2.5.0" LINK_DATE="12/06/2009 03:31:07" UPTO_LINK_DATE="12/06/2009 03:31:07" VER_LANGUAGE="English (United States) [0x409]" />
	<MATCHING_FILE NAME="components\foo_preview.dll" SIZE="118784" CHECKSUM="0x9FFCD1AB" MODULE_TYPE="WIN32" PE_CHECKSUM="0x0" LINKER_VERSION="0x0" LINK_DATE="12/22/2008 20:41:11" UPTO_LINK_DATE="12/22/2008 20:41:11" />
	<MATCHING_FILE NAME="components\foo_random_pools.dll" SIZE="207360" CHECKSUM="0x7DE55311" MODULE_TYPE="WIN32" PE_CHECKSUM="0x40D74" LINKER_VERSION="0x0" LINK_DATE="12/27/2009 17:22:55" UPTO_LINK_DATE="12/27/2009 17:22:55" />
	<MATCHING_FILE NAME="components\foo_rgscan.dll" SIZE="298496" CHECKSUM="0x93DCD198" MODULE_TYPE="WIN32" PE_CHECKSUM="0x56CAC" LINKER_VERSION="0x0" LINK_DATE="01/09/2010 11:44:24" UPTO_LINK_DATE="01/09/2010 11:44:24" />
	<MATCHING_FILE NAME="components\foo_run.dll" SIZE="369152" CHECKSUM="0x1F65BA37" BIN_FILE_VERSION="0.3.7.0" BIN_PRODUCT_VERSION="0.3.7.0" PRODUCT_VERSION="0, 3, 7, 0" FILE_DESCRIPTION="foo_run foobar2000 component" PRODUCT_NAME="foo_run foobar2000 component" FILE_VERSION="0, 3, 7, 0" ORIGINAL_FILENAME="foo_run.dll" INTERNAL_NAME="foo_run" LEGAL_COPYRIGHT="Copyright © 2006-2009 Florian Heidenreich" VERFILEDATEHI="0x0" VERFILEDATELO="0x0" VERFILEOS="0x4" VERFILETYPE="0x2" MODULE_TYPE="WIN32" PE_CHECKSUM="0x6199A" LINKER_VERSION="0x0" UPTO_BIN_FILE_VERSION="0.3.7.0" UPTO_BIN_PRODUCT_VERSION="0.3.7.0" LINK_DATE="06/07/2009 13:15:14" UPTO_LINK_DATE="06/07/2009 13:15:14" VER_LANGUAGE="German (Germany) [0x407]" />
	<MATCHING_FILE NAME="components\foo_scheduler.dll" SIZE="519168" CHECKSUM="0x2288E895" MODULE_TYPE="WIN32" PE_CHECKSUM="0x8C40A" LINKER_VERSION="0x0" LINK_DATE="02/09/2010 19:42:39" UPTO_LINK_DATE="02/09/2010 19:42:39" />
	<MATCHING_FILE NAME="components\foo_scrobblecharts.dll" SIZE="204800" CHECKSUM="0x52344B3" MODULE_TYPE="WIN32" PE_CHECKSUM="0x35C03" LINKER_VERSION="0x0" LINK_DATE="03/31/2007 14:36:48" UPTO_LINK_DATE="03/31/2007 14:36:48" />
	<MATCHING_FILE NAME="components\foo_softplaylists.dll" SIZE="315904" CHECKSUM="0x8B8415CC" MODULE_TYPE="WIN32" PE_CHECKSUM="0x4E225" LINKER_VERSION="0x0" LINK_DATE="12/30/2009 19:29:49" UPTO_LINK_DATE="12/30/2009 19:29:49" />
	<MATCHING_FILE NAME="components\foo_stopaftercuralbum.dll" SIZE="122880" CHECKSUM="0xAA991A40" MODULE_TYPE="WIN32" PE_CHECKSUM="0x22AA6" LINKER_VERSION="0x0" LINK_DATE="06/01/2009 08:50:40" UPTO_LINK_DATE="06/01/2009 08:50:40" />
	<MATCHING_FILE NAME="components\foo_textdisplay.dll" SIZE="240128" CHECKSUM="0x4DE184A1" MODULE_TYPE="WIN32" PE_CHECKSUM="0x43811" LINKER_VERSION="0x0" LINK_DATE="07/08/2008 17:45:15" UPTO_LINK_DATE="07/08/2008 17:45:15" />
	<MATCHING_FILE NAME="components\foo_texttools.dll" SIZE="197120" CHECKSUM="0xB16B12BF" MODULE_TYPE="WIN32" PE_CHECKSUM="0x37F02" LINKER_VERSION="0x0" LINK_DATE="12/23/2009 20:00:20" UPTO_LINK_DATE="12/23/2009 20:00:20" />
	<MATCHING_FILE NAME="components\foo_uie_biography.dll" SIZE="306688" CHECKSUM="0x174292BA" BIN_FILE_VERSION="0.1.0.0" BIN_PRODUCT_VERSION="0.1.0.0" PRODUCT_VERSION="0, 1, 0, 0" FILE_VERSION="0, 1, 0, 0" ORIGINAL_FILENAME="foo_uie_panel_splitter.dll" VERFILEDATEHI="0x0" VERFILEDATELO="0x0" VERFILEOS="0x4" VERFILETYPE="0x2" MODULE_TYPE="WIN32" PE_CHECKSUM="0x5857D" LINKER_VERSION="0x0" UPTO_BIN_FILE_VERSION="0.1.0.0" UPTO_BIN_PRODUCT_VERSION="0.1.0.0" LINK_DATE="01/21/2010 14:20:37" UPTO_LINK_DATE="01/21/2010 14:20:37" VER_LANGUAGE="Japanese [0x411]" />
	<MATCHING_FILE NAME="components\foo_uie_esplaylist.dll" SIZE="227328" CHECKSUM="0x6DFB2BD9" BIN_FILE_VERSION="0.1.0.0" BIN_PRODUCT_VERSION="0.1.0.0" PRODUCT_VERSION="0, 1, 0, 0" FILE_VERSION="0, 1, 0, 0" ORIGINAL_FILENAME="foo_uie_panel_splitter.dll" VERFILEDATEHI="0x0" VERFILEDATELO="0x0" VERFILEOS="0x4" VERFILETYPE="0x2" MODULE_TYPE="WIN32" PE_CHECKSUM="0x38D0E" LINKER_VERSION="0x0" UPTO_BIN_FILE_VERSION="0.1.0.0" UPTO_BIN_PRODUCT_VERSION="0.1.0.0" LINK_DATE="02/26/2010 18:25:02" UPTO_LINK_DATE="02/26/2010 18:25:02" VER_LANGUAGE="Japanese [0x411]" />
	<MATCHING_FILE NAME="components\foo_uie_trackinfo_mod.dll" SIZE="352256" CHECKSUM="0x6B38CA90" MODULE_TYPE="WIN32" PE_CHECKSUM="0x595D9" LINKER_VERSION="0x0" LINK_DATE="01/05/2007 19:36:21" UPTO_LINK_DATE="01/05/2007 19:36:21" />
	<MATCHING_FILE NAME="components\foo_uie_wsh_panel_mod.dll" SIZE="696832" CHECKSUM="0x17417679" MODULE_TYPE="WIN32" PE_CHECKSUM="0xB1816" LINKER_VERSION="0x0" LINK_DATE="02/23/2010 04:04:17" UPTO_LINK_DATE="02/23/2010 04:04:17" />
	<MATCHING_FILE NAME="components\foo_ui_columns.dll" SIZE="1492992" CHECKSUM="0xE2103ABC" MODULE_TYPE="WIN32" PE_CHECKSUM="0x171A77" LINKER_VERSION="0x0" LINK_DATE="01/09/2010 14:40:24" UPTO_LINK_DATE="01/09/2010 14:40:24" />
	<MATCHING_FILE NAME="components\foo_ui_std.dll" SIZE="1084416" CHECKSUM="0xFCEA4D38" MODULE_TYPE="WIN32" PE_CHECKSUM="0x1188BA" LINKER_VERSION="0x0" LINK_DATE="01/09/2010 11:44:52" UPTO_LINK_DATE="01/09/2010 11:44:52" />
	<MATCHING_FILE NAME="components\foo_unpack.dll" SIZE="171520" CHECKSUM="0x3E6A9DF" MODULE_TYPE="WIN32" PE_CHECKSUM="0x2A031" LINKER_VERSION="0x0" LINK_DATE="01/09/2010 11:43:19" UPTO_LINK_DATE="01/09/2010 11:43:19" />
	<MATCHING_FILE NAME="components\foo_vis_shpeck-beta.dll" SIZE="172032" CHECKSUM="0xAEB08753" MODULE_TYPE="WIN32" PE_CHECKSUM="0x30BA8" LINKER_VERSION="0x0" LINK_DATE="04/18/2008 22:41:49" UPTO_LINK_DATE="04/18/2008 22:41:49" />
	<MATCHING_FILE NAME="components\foo_wlm.dll" SIZE="116224" CHECKSUM="0x3C718148" MODULE_TYPE="WIN32" PE_CHECKSUM="0x2282B" LINKER_VERSION="0x0" LINK_DATE="02/09/2010 09:06:10" UPTO_LINK_DATE="02/09/2010 09:06:10" />
	<MATCHING_FILE NAME="components\ICSharpCode.SharpZipLib.dll" SIZE="139264" CHECKSUM="0x5A4FE44F" BIN_FILE_VERSION="0.84.0.0" BIN_PRODUCT_VERSION="0.84.0.0" PRODUCT_VERSION="0.84.0.0" FILE_DESCRIPTION="ICSharpCode.SharpZipLibrary" PRODUCT_NAME="#ZipLibrary" FILE_VERSION="0.84.0.0" ORIGINAL_FILENAME="ICSharpCode.SharpZipLib.dll" INTERNAL_NAME="ICSharpCode.SharpZipLib.dll" LEGAL_COPYRIGHT="Copyright 2001-2005 Mike Krueger" VERFILEDATEHI="0x0" VERFILEDATELO="0x0" VERFILEOS="0x4" VERFILETYPE="0x2" MODULE_TYPE="WIN32" PE_CHECKSUM="0x2A3B5" LINKER_VERSION="0x0" UPTO_BIN_FILE_VERSION="0.84.0.0" UPTO_BIN_PRODUCT_VERSION="0.84.0.0" LINK_DATE="09/22/2006 08:21:42" UPTO_LINK_DATE="09/22/2006 08:21:42" VER_LANGUAGE="Language Neutral [0x0]" />
	<MATCHING_FILE NAME="components\Interop.Foobar2000.dll" SIZE="49152" CHECKSUM="0x968AC15B" BIN_FILE_VERSION="1.0.0.0" BIN_PRODUCT_VERSION="1.0.0.0" PRODUCT_VERSION="1.0.0.0" FILE_DESCRIPTION=" " COMPANY_NAME=" " PRODUCT_NAME="Assembly imported from type library 'Foobar2000'." FILE_VERSION="1.0.0.0" ORIGINAL_FILENAME="Interop.Foobar2000.dll" INTERNAL_NAME="Interop.Foobar2000" LEGAL_COPYRIGHT=" " VERFILEDATEHI="0x0" VERFILEDATELO="0x0" VERFILEOS="0x4" VERFILETYPE="0x2" MODULE_TYPE="WIN32" PE_CHECKSUM="0x0" LINKER_VERSION="0x0" UPTO_BIN_FILE_VERSION="1.0.0.0" UPTO_BIN_PRODUCT_VERSION="1.0.0.0" LINK_DATE="09/22/2006 23:58:45" UPTO_LINK_DATE="09/22/2006 23:58:45" VER_LANGUAGE="Invariant Language (Invariant Country) [0x7f]" />
	<MATCHING_FILE NAME="components\Interop.Foobar2000Helper.dll" SIZE="7168" CHECKSUM="0xC82886BF" BIN_FILE_VERSION="1.0.0.0" BIN_PRODUCT_VERSION="1.0.0.0" PRODUCT_VERSION="1.0.0.0" FILE_DESCRIPTION=" " COMPANY_NAME=" " PRODUCT_NAME="Assembly imported from type library 'Foobar2000Helper'." FILE_VERSION="1.0.0.0" ORIGINAL_FILENAME="Interop.Foobar2000Helper.dll" INTERNAL_NAME="Interop.Foobar2000Helper" LEGAL_COPYRIGHT=" " VERFILEDATEHI="0x0" VERFILEDATELO="0x0" VERFILEOS="0x4" VERFILETYPE="0x2" MODULE_TYPE="WIN32" PE_CHECKSUM="0x0" LINKER_VERSION="0x0" UPTO_BIN_FILE_VERSION="1.0.0.0" UPTO_BIN_PRODUCT_VERSION="1.0.0.0" LINK_DATE="09/22/2006 23:58:45" UPTO_LINK_DATE="09/22/2006 23:58:45" VER_LANGUAGE="Invariant Language (Invariant Country) [0x7f]" />
	<MATCHING_FILE NAME="components\scripts\scriptcache.dll" SIZE="9728" CHECKSUM="0xBE8E13A8" MODULE_TYPE="WIN32" PE_CHECKSUM="0x0" LINKER_VERSION="0x0" LINK_DATE="10/27/2006 05:14:53" UPTO_LINK_DATE="10/27/2006 05:14:53" />
	<MATCHING_FILE NAME="tools\libeay32.dll" SIZE="1177600" CHECKSUM="0xADEFC887" BIN_FILE_VERSION="0.9.8.8" BIN_PRODUCT_VERSION="0.9.8.8" PRODUCT_VERSION="0.9.8h" FILE_DESCRIPTION="Libeay32: open Secure Socket Layer protocol" COMPANY_NAME="GnuWin32 &lt;http://gnuwin32.sourceforge.net&gt;" PRODUCT_NAME="OpenSSL" FILE_VERSION="0.9.8h" ORIGINAL_FILENAME="libeay32.dll" INTERNAL_NAME="libeay32" LEGAL_COPYRIGHT="© 2008 OpenSSL &lt;www.openssl.org&gt;" VERFILEDATEHI="0x0" VERFILEDATELO="0x0" VERFILEOS="0x4" VERFILETYPE="0x2" MODULE_TYPE="WIN32" PE_CHECKSUM="0x12417E" LINKER_VERSION="0x10000" UPTO_BIN_FILE_VERSION="0.9.8.8" UPTO_BIN_PRODUCT_VERSION="0.9.8.8" LINK_DATE="09/03/2008 20:49:35" UPTO_LINK_DATE="09/03/2008 20:49:35" VER_LANGUAGE="English (United States) [0x409]" />
	<MATCHING_FILE NAME="tools\libiconv2.dll" SIZE="1008128" CHECKSUM="0x63331ED0" BIN_FILE_VERSION="1.12.2872.39125" BIN_PRODUCT_VERSION="1.12.2872.39125" PRODUCT_VERSION="1.12.2872.39125" FILE_DESCRIPTION="Libiconv: convert between character encodings" COMPANY_NAME="GnuWin32 &lt;http://gnuwin32.sourceforge.net&gt;" PRODUCT_NAME="LibIconv" FILE_VERSION="1.12.2872.39125" ORIGINAL_FILENAME="iconv2.dll" INTERNAL_NAME="iconv2" LEGAL_COPYRIGHT="© 2007 Free Software Foundation &lt;www.fsf.org&gt;" VERFILEDATEHI="0x0" VERFILEDATELO="0x0" VERFILEOS="0x4" VERFILETYPE="0x2" MODULE_TYPE="WIN32" PE_CHECKSUM="0xFC3CB" LINKER_VERSION="0x10000" UPTO_BIN_FILE_VERSION="1.12.2872.39125" UPTO_BIN_PRODUCT_VERSION="1.12.2872.39125" LINK_DATE="03/14/2008 22:21:30" UPTO_LINK_DATE="03/14/2008 22:21:30" VER_LANGUAGE="English (United States) [0x409]" />
	<MATCHING_FILE NAME="tools\libintl3.dll" SIZE="103424" CHECKSUM="0x8506FBBB" BIN_FILE_VERSION="0.14.4.1952" BIN_PRODUCT_VERSION="0.14.4.1952" PRODUCT_VERSION="0.14.4.1952" FILE_DESCRIPTION="GetText: library and tools for native language support" COMPANY_NAME="GNU &lt;www.gnu.org&gt;" PRODUCT_NAME="GetText" FILE_VERSION="0.14.4.1952" ORIGINAL_FILENAME="libintl3.dll" INTERNAL_NAME="libintl3" LEGAL_COPYRIGHT="© 2005 Free Software Foundation &lt;www.fsf.org&gt;" VERFILEDATEHI="0x0" VERFILEDATELO="0x0" VERFILEOS="0x4" VERFILETYPE="0x2" MODULE_TYPE="WIN32" PE_CHECKSUM="0x1BF7B" LINKER_VERSION="0xE" UPTO_BIN_FILE_VERSION="0.14.4.1952" UPTO_BIN_PRODUCT_VERSION="0.14.4.1952" LINK_DATE="05/06/2005 19:52:42" UPTO_LINK_DATE="05/06/2005 19:52:42" VER_LANGUAGE="English (United States) [0x409]" />
	<MATCHING_FILE NAME="tools\libssl32.dll" SIZE="232960" CHECKSUM="0xAACC4C9C" BIN_FILE_VERSION="0.9.8.8" BIN_PRODUCT_VERSION="0.9.8.8" PRODUCT_VERSION="0.9.8h" FILE_DESCRIPTION="Libssl32: open Secure Socket Layer protocol" COMPANY_NAME="GnuWin32 &lt;http://gnuwin32.sourceforge.net&gt;" PRODUCT_NAME="OpenSSL" FILE_VERSION="0.9.8h" ORIGINAL_FILENAME="libssl32.dll" INTERNAL_NAME="libssl32" LEGAL_COPYRIGHT="© 2008 OpenSSL &lt;www.openssl.org&gt;" VERFILEDATEHI="0x0" VERFILEDATELO="0x0" VERFILEOS="0x4" VERFILETYPE="0x2" MODULE_TYPE="WIN32" PE_CHECKSUM="0x3A269" LINKER_VERSION="0x10000" UPTO_BIN_FILE_VERSION="0.9.8.8" UPTO_BIN_PRODUCT_VERSION="0.9.8.8" LINK_DATE="09/03/2008 20:49:36" UPTO_LINK_DATE="09/03/2008 20:49:36" VER_LANGUAGE="English (United States) [0x409]" />
	<MATCHING_FILE NAME="tools\wget.exe" SIZE="449024" CHECKSUM="0xE2D614EA" BIN_FILE_VERSION="1.11.4.3287" BIN_PRODUCT_VERSION="1.11.4.3287" PRODUCT_VERSION="1.11.4.3287" FILE_DESCRIPTION="Wget: retrieve files from the WWW" COMPANY_NAME="GnuWin32 &lt;http://gnuwin32.sourceforge.net&gt;" PRODUCT_NAME="Wget" FILE_VERSION="1.11.4.3287" ORIGINAL_FILENAME="wget.exe" INTERNAL_NAME="wget" LEGAL_COPYRIGHT="© 2008 Free Software Foundation &lt;www.fsf.org&gt;" VERFILEDATEHI="0x0" VERFILEDATELO="0x0" VERFILEOS="0x4" VERFILETYPE="0x1" MODULE_TYPE="WIN32" PE_CHECKSUM="0x729E4" LINKER_VERSION="0x10000" UPTO_BIN_FILE_VERSION="1.11.4.3287" UPTO_BIN_PRODUCT_VERSION="1.11.4.3287" LINK_DATE="12/31/2008 14:03:36" UPTO_LINK_DATE="12/31/2008 14:03:36" VER_LANGUAGE="English (United States) [0x409]" />
</EXE>
<EXE NAME="foo_component_manager.dll" FILTER="GRABMI_FILTER_THISFILEONLY">
	<MATCHING_FILE NAME="foo_component_manager.dll" SIZE="350720" CHECKSUM="0xFB67E782" MODULE_TYPE="WIN32" PE_CHECKSUM="0x55E62" LINKER_VERSION="0x0" LINK_DATE="02/24/2010 13:45:22" UPTO_LINK_DATE="02/24/2010 13:45:22" />
</EXE>
<EXE NAME="kernel32.dll" FILTER="GRABMI_FILTER_THISFILEONLY">
	<MATCHING_FILE NAME="kernel32.dll" SIZE="986112" CHECKSUM="0x359DA0B2" BIN_FILE_VERSION="5.1.2600.3541" BIN_PRODUCT_VERSION="5.1.2600.3541" PRODUCT_VERSION="5.1.2600.3541" FILE_DESCRIPTION="Windows NT BASE API Client DLL" COMPANY_NAME="Microsoft Corporation" PRODUCT_NAME="Microsoft® Windows® Operating System" FILE_VERSION="5.1.2600.3541 (xpsp_sp2_gdr.090321-1320)" ORIGINAL_FILENAME="kernel32" INTERNAL_NAME="kernel32" LEGAL_COPYRIGHT="© Microsoft Corporation. All rights reserved." VERFILEDATEHI="0x0" VERFILEDATELO="0x0" VERFILEOS="0x40004" VERFILETYPE="0x2" MODULE_TYPE="WIN32" PE_CHECKSUM="0xFEAFF" LINKER_VERSION="0x50001" UPTO_BIN_FILE_VERSION="5.1.2600.3541" UPTO_BIN_PRODUCT_VERSION="5.1.2600.3541" LINK_DATE="03/21/2009 14:18:57" UPTO_LINK_DATE="03/21/2009 14:18:57" VER_LANGUAGE="English (United States) [0x409]" />
</EXE>
</DATABASE>

[!--sizeo:1--][span style=\"font-size:8pt;line-height:100%\"][!--/sizeo--]moderation: changed code to codebox[/size]

I'm getting the crash too... it happens when it starts to download the component.  Weird since it seemed to have worked before but this just started happening.

And me, rolling back to a previous version doesn't seem to help either.

Try updating again now. I had messed up the link to foo_podcatcher.

Still getting a crash. For the record, the only components being updated are foo_abx and foo_uie_wsh_panel_mod

Thanks for the info. foo_uie_wsh_panel_mod was recently updated to 1.3.2, and all links to previous versions were removed. So the component was crashing when trying to download a non-existent link. I've really got to fix that bug.

As a side note, foo_uie_wsh_panel_mod will be reported as the XML file being out of date due to the incorrect handling of versions with beta in the name. Eg. 1.3.2 Beta 4 is seen as newer than 1.3.2

Hmm, I noticed in the changelog:

0.1.6 (2010-02-24)
- Fixed security attributes on copied files (no more lock icon). Re-downloading a component that has the lock icon will remove it and replace it with a file that has the correct security attributes.
- Don't ask for elevation unless required
- Added support for files needing to be installed to foobar2000 profile folder (eg foo_httpcontrol)

Thing is, I'm still getting elevation prompts under Windows Server 2008 even though I've recursively given full access to the users group for "C:\Program Files\foobar2000\"

component not found in xml for me:

foo_skype
http://www.hydrogenaudio.org/forums/index....showtopic=63055 (http://www.hydrogenaudio.org/forums/index.php?showtopic=63055)

* but its development is dead


foo_popupplus
http://www.hydrogenaudio.org/forums/index....showtopic=55933 (http://www.hydrogenaudio.org/forums/index.php?showtopic=55933)

* but its listed as crashware so i dont know if its suported

incorrect handling of versions with beta in the name. Eg. 1.3.2 Beta 4 is seen as newer than 1.3.2

I´m only using file attributes 'last changed' for comparing which version is newer. It works fine for me maybe also an idea for you?

So, does this component notify the server when we receive an "XML file out of date" message, or should we report those here?  I'm getting that response for 5 of my components, and I'm not sure if I should be reporting that when it happens.

I didn't receive an update for the new version of columns ui and customdb, could you check on this?

xml file out of date for installed version columns ui 0.3.8.4  latest version0.3.8.3....

This component depends on it author, and I guess he isn't available 24/7, so if you know there is update before author does, just download it by yourself 
Perhaps it could detect if user have updated version and than get informed by the info so that it could be updated ASAP
It would be nice if it could also detect new foobar version too, thou it detects core components versions but that's not enough for knowing about new foobar versions (not that it can automatically download and install torrent of course, but for informative purposes) and as we have also another autoupdate component, using both together once a week is good practice IMO
and info that it provides as homepage/discussion thread links etc are just great

Bug report:

Component crashes foobar while downloading foo_podcatcher update.

edit: after manually updating component manager to the newest version,
problem solved.

Just thought I'd mention that latest foo_queuecontents (http://sites.google.com/site/salskisite/foo_queuecontents) is version 0.2. Manager is saying 0.1.1 and that XML file is out of date.

Two more out of date:

foo_dop 0.6.6.8 vs 0.6.6.7

and

foo_scheduler 4.0 vs 3.55

Can foo_amipwrapper be included?

http://pelit.koillismaa.fi/plugins/show.php?id=40 (http://pelit.koillismaa.fi/plugins/show.php?id=40)

I don't see the foobar2000 deskband controls plugin

http://www.hydrogenaudio.org/forums/index....c=78234&hl= (http://www.hydrogenaudio.org/forums/index.php?showtopic=78234&hl=)

XML out of date for foo_wave_seekbar.
XML reports 0.1.10, latest version is 0.1.11
http://www.hydrogenaudio.org/forums/index....showtopic=77490 (http://www.hydrogenaudio.org/forums/index.php?showtopic=77490)

Component manager can't find the new HDCD decoder - need to add/include:

http://www.foobar2000.org/components/view/foo_dsp_hdcd (http://www.foobar2000.org/components/view/foo_dsp_hdcd)

I hope this component isn't dead, wonder if someone else could update the xml and then we can change the url, in case the current developer has abandoned this project.

Hi everyone,

Apologies for not updating the xml list or component for the past two weeks. I've been unable to update the component for the reason given below.

I fell ill on the 4th March with an incredibly painful headache and it was soon discovered that the headache was being caused be a brain aneurysm. I had brain surgery the past week to clamp the aneurysm and, thank God, the surgery went without a hitch (in the face of a stroke or worse). I've only just gotten out of hospital and require rest at home for the next month or so.

Given this very rapid change in my life, I've decided to take a step back from component development and focus more on my immediate family and life in general. So I'm afraid I will be taking a break from contributing to this component for the next few months, if not permanently.

The component is open source so anyone else may continue development, and anyone is free to host and update the xml file themselves.

Thank you everyone who has taken the time to use the component, report bugs, and make all of the numerous xml suggestions.

fraganator - that is terrible, but I'm glad you're doing well.  Thank you for all you've done, you will be in my prayers, take care of yourself and we look forward to your healthy return in the future.

Hi everyone,

Apologies for not updating the xml list or component for the past two weeks. I've been unable to update the component for the reason given below.

I fell ill on the 4th March with an incredibly painful headache and it was soon discovered that the headache was being caused be a brain aneurysm. I had brain surgery the past week to clamp the aneurysm and, thank God, the surgery went without a hitch (in the face of a stroke or worse). I've only just gotten out of hospital and require rest at home for the next month or so.

Given this very rapid change in my life, I've decided to take a step back from component development and focus more on my immediate family and life in general. So I'm afraid I will be taking a break from contributing to this component for the next few months, if not permanently.

The component is open source so anyone else may continue development, and anyone is free to host and update the xml file themselves.

Thank you everyone who has taken the time to use the component, report bugs, and make all of the numerous xml suggestions.

That is awful man... Rest easy, and have a stable, swift recovery.

I'm sad to hear that. Hope you get better soon and recover fully.

terribly sad to hear about that fraganator, but glad all has gone well for you given the circumstances.

hope you make a full recovery soon

I'm sorry for you. I hope you'll be fine

Fraganator, hope you make a full recovery.

Will pray for your wellness.

Thank you for your work.

We should probably upload the source to a code hoster. I suggest Launchpad or Github, any objections/preferences?

google code or sourceforge?

I wish you all the best, frag!

You take care  and  get bad to full health, thanks for all your effort but concentrate on what is important  for you and your family.

all the best wishes to fraganator. take care of you man and i hope for you full recovery.

even thought one of the most promising attempt for auto update probably died

anyone want to take over this plugin? would be ashamed if it died, if anything someone could run the xml stuff maybe.

(http://s003.radikal.ru/i204/1003/15/b050140dc626.png) (http://www.radikal.ru)

fraganator - Get well soon! That is terrible news, I hope you'll be alright!

A big thank you to everyone for their support and well wishes. It really does mean a lot  Headaches have completely gone, it's just a matter of waiting for energy levels to slowly return.

By the sounds of things this component will be superseded by foobar2000 core at some point in the near future. To quote Peter on foo_component_manager (on the day of its release):

Not to discourage anything, but I think this idea sucks, this task needs to be implemented by core and without idiotic limitations like requiring foobar2000 to be running as admin.
If you choose to continue developing this, you'll be in for a serious disappointment a few foobar2000 versions later when your work becomes completely obsolete.

A big thank you to everyone for their support and well wishes. It really does mean a lot  Headaches have completely gone, it's just a matter of waiting for energy levels to slowly return.

By the sounds of things this component will be superseded by foobar2000 core at some point in the near future. To quote Peter on foo_component_manager (on the day of its release):

Quote from: Peter link=msg=0 date=

Not to discourage anything, but I think this idea sucks, this task needs to be implemented by core and without idiotic limitations like requiring foobar2000 to be running as admin.
If you choose to continue developing this, you'll be in for a serious disappointment a few foobar2000 versions later when your work becomes completely obsolete.

thats a good thing to hear that youre doing better... considering peters quote... good to hear that stuff and looking forward to next releases with renewed hope

A big thank you to everyone for their support and well wishes. It really does mean a lot  Headaches have completely gone, it's just a matter of waiting for energy levels to slowly return.

Awesome!

By the sounds of things this component will be superseded by foobar2000 core at some point in the near future. To quote Peter on foo_component_manager (on the day of its release):

Quote from: Peter link=msg=0 date=

Not to discourage anything, but I think this idea sucks, this task needs to be implemented by core and without idiotic limitations like requiring foobar2000 to be running as admin.
If you choose to continue developing this, you'll be in for a serious disappointment a few foobar2000 versions later when your work becomes completely obsolete.

A few foobar versions later, huh? Looking forward to that! No reason why a solution that works right now (without requiring foobar to run as admin, I might add) is an idea that "sucks", though...

Here is interim links.....
http://mudlord.hcs64.com/files (http://mudlord.hcs64.com/files)

I want to take over this plugin.
but i have no enough time to maintain the xml on time.
so.... first i will open a website as soon as possible, that user can maintain the xml themself.
but i need some advise, that should we let anyone to maintain the xml? or just the plugin developer? or somebody that in allowed list?

Why don't you ask these (http://foobar2000.xrea.jp/index.php?%E6%9B%B4%E6%96%B0%E7%8A%B6%E6%B3%81) guys for corporation? They react very fast to any update.

but i need some advise, that should we let anyone to maintain the xml? or just the plugin developer? or somebody that in allowed list?

A closed & trusted group of maintainers is best. Making it entirely open makes it a support nightmare.

thanks,
now i'm working on it.
first
it's a simple list of components make xml more user friendly.
and then i will add more features, such as maintain the xml nodes

http://www.vteam.org.cn/foobar2000 (http://www.vteam.org.cn/foobar2000)

but i need some advise, that should we let anyone to maintain the xml? or just the plugin developer? or somebody that in allowed list?

For obvious security reasons (as well as organization) you need to have it relatively closed.  There is one way (conceptually) to make this easier.  Take foo_dop.  If you make the base URL only changeable by a few trusted users "http://yuo.be/download/" then you can have a broader array of people add that the newest version is "DB7C5040-928A-4a17-84DF-16A58E25BEDE/foo_dop-0.6.7.4.7z".  That way the worst that happens is a broken link and not a malicious component.  This would run into a few more problems with components hosted on this forum since they'd have the base URL of "http://www.hydrogenaudio.org/forums/index.php?act=attach&type=post&id=" which wouldn't really stop much.

Just throwing that out there.

(Big thanks to fraganator (hope things go well for you) and everyone trying to keep this alive.)

Zelphar, have you been able to make any further progress on this? 

You noticed the new auto-update features in the latest fooobar2000 betas?
If your favorite components are not on the official components site so ask the author why he doesn't add his components to it.

You noticed the new auto-update features in the latest fooobar2000 betas?

Oops, I haven't tried the latest beta versions yet. Great news!