From: miffed on
par4thecourse wrote:

>miffed <nowhere(a)there> wrote
>> Yikes! I run a reg cleaner every night!
>
>That's probably what caused the program's inability to run.

Quite likely. It may have been a program I use weekly to thorougly wash
the system: NirSoft's "CleanAfterMe", which can dig quite deeply.

It raises a question about whether Xmedia portable version I installed
is truly portable. I'm still waiting to hear from the author but I don't
hold out much hope.

Whatever, the installer version is now working OK for the moment.


-miffed

From: miffed on
Yrrah:
>miffed <nowhere(a)there>:
>
>> many so-called portable
>> apps still write to the registry which makes them non-portable
>> according to most peoples' understanding the term.
>>
>> In some cases, the only benefit one gets is that they usually don't
>> have an installer process and will run out of the box, but that by
>> itself doesn't make it portable IMO.
>
>Correct. However, portable XMedia Recode does not write to the
>registry.

Assuming you've checked that out and aren't guessing, it adds weight to
the view that there was a problem with the v2.2.4.4 portable build which
the sudden new release of v2.2.4.4 may resolve.


-miffed




From: miffed on
par4thecourse wrote:

>>Whatever, the installer version is now working OK for the moment.
>>
>
>The only way you can tell is to clean your system by uninstalling the
>program, and using a program such as Regseeker or Nirsoft's scanner to
>search for all references to Xmedia Recode, and other key dll's in the
>program directory. Once again, be careful as to what's deleted and
>keep Regseeker backups or an entire Erunt backup of your registry
>before editing.
>
>Then when you think you may have deleted all references to the
>program, use Zoft's Uninstaller to monitor what happens to your
>registry after starting the portable version of Xmedia Recode. That
>would mean running Zsoft before extracting the portable zip file, and
>again after running and closing the program to finish the analysis.
>The view the zulog file.

I'll keep that advice handy thanks. Meanwhile the installer version is
still working OK and I note a sudden new release v2.2.4.4 has been
released which I speculate resolves the previous problem I reported
with the portable build.


-miffed