WTF Is “Bulk Texture File Conversion” Shell-Menu-Item

The Convert to file format... context-menu item
and Bulk Texture File Conversion dialog,
are a shell-contextmenu item, added after registering TxView.dll which is a part of DirectX SDK package.

You’ll have the menu-item when you’ll right-click on the a Directory, jpegfile, Paint.Picture, pfmfile, pngfile and TxView.1 file-types classes,

Continue reading

VobSub 2.23 Installer Free

Contains The “Installer/Setup/Registry Free” Files, In A Compressed Format.
Unmodified, Original Files Of VobSub Installer.

technical stuff.
I always misplacing the installer and Windows Vista/7/8+ has problems installing it.

I’ve analysed the latest available VobSub_2.23.exe,

some exe stuff:
it has File Offset 00003264 and Overlay 000A71D0.
reverse engineering showed that it has Installer Nullsoft PiMP Stub header,

so rather than installing and collecting the files from around my PC, I’ve used my reverse Nullsoft installer script (wrote it when I was 12 years old for d2k2.ollydbg..).

you can use it for VirtualDub video editing as a “normal” (a.k.a not SSA/ASS subtitles embedded).
it is easy as placing the files in the ‘plugins’ folder and restarting VirtualDub.

You may use some of the files, or run the exe to register the DLL files,
or do it manually.

Files in the package:

|   submux.exe
|   subresync.exe
|   unrar.dll
|   vobsub.dll
|   vobsub.ini
|   vobsub_au.auf
|       ass-quickref.txt
|       ass-specs.doc
|       dvobsub.txt
|       license.txt
|       readme1st.txt
|       submux.txt
|       subresync.txt
|       supported formats.txt
|       textsub.txt
|       unicode.txt
|       vobsub-auto.txt
|       vobsub.txt


on VirtualDub:
you can essentially place this folder anywhere, but conventionally copy everything (deflate the folders) into .....path....\VirtualDub\plugins\.
afterwards, you close and open VirtualDub, and (on the top menu) go to videofilters... – click Add... – click Load..., select either textsub.vdf or vobsub_vd.vdf, and continue to load your srt subtitles, etc…

Bring Adobe Flash Back To Chromium (Solved)

ahhh… I had to figure out this one for myself from the source-code of Chromium (Chrome) project at: and… :(

New Chromium versions does not have Flash anymore!
– Chrome (regular and Canary) still does.

also, and there are no-people figuring out the solution yet, (as far as Googling around shows..)
so this post should be the first one to explain how to re-enable Adobe Flash on New Chromium installations.

it should be compatible with Windows, Mac and Linux installations.

Chromium not just disable Flash, but it does not ship with the ‘pepflashplayer.dll’,
in fact- the folder, named PepperFlash, which is the code-name for the embedded plugin for Flash, is empty:


you can look for pepflashplayer.dll in the Google-Chrome-Canary or regular versions and copy it to the folder but it won’t do anything (check using chrome://flash/)

for Chromium’s plugin-engine to identify the plugin, you’ll need to use some command-line switches,
but first let us play smart, assuming you’ll be updating Chromium somewhere in the future, the application folder will get overwritten so we’re not going to play with files and folders,
lets use the official Adobe plugin!

– download the latest Flash version from the
I currently developing some video-players with Flash fallback, so I’m using the “+Debugger” version.. but feel free to download the regular one.

its best for you to first download the uninstaller:
run it to clean the old versions (make all of the browsers are closed, even their background processes, just use task-manager and kill chrome.exe firefox.exe and iexplore.exe if any..)

then the IE version:, and install it.

then the “other” browsers version:, and install it.

and the “other other” browsers version:, and install it too.


in a second, we will be adding some command-line argument to Chromium, but first we need to find out where are the pepflashplayer{architecture}_version_ver._ver._ver.dll is located, and what is their named:

there are two folders:




one is holding the x32 version of Flash, and the other is holding the x64 version.
you can visit chrome://chrome/
to see what version you are using, I’m using the x64 version of Chromium for windows..

normally the C:\Windows\System32\Macromed\Flash holds the x32 version and the C:\Windows\SysWOW64\Macromed\Flash\ has the x64 version.

right! so the x64 version it is,

Adobe guys had a bug in the installation script, and the DLL FILES location are upside-down:

ok, so now we’ll be using two switches, one to disable the embedded-plugin (even that it is “not there”) and the other one to force load a flash-plugin from C:\Windows\System32\Macromed\Flash folder.

here is an example for the command line to load Chromium, with Flash support, (again):

C:\Users\Elad\AppData\Local\Chromium\Application\chrome.exe --disable-bundled-ppapi-flash --ppapi-flash-path="C:\Windows\System32\Macromed\Flash\pepflashplayer64_17_0_0_93.dll"

you may put it in a cmd file, or just create a shortcut for chrome.exe and after “OK”‘ing it, just re-edit it adding a --disable-bundled-ppapi-flash --ppapi-flash-path="C:\Windows\System32\Macromed\Flash\pepflashplayer64_17_0_0_93.dll" at the end.

sometimes sending arguments is hard in windows, most of the time there is a lot of inverted commas confusion and mix-ups.

you can download the exe and the ini file from my github page:

after you’ll run the exe a Chromium process will be created with the arguments passed directly to the Windows-API (so- FAST!) re-open the chrome://flash/ page, and see something like that: