[SOLVED] Windows XP Catastrophic Failure?

Post a reply

Smilies
:D :) :( :o :-? 8) :lol: :x :P :oops: :cry: :evil: :roll: :wink:

BBCode is ON
[img] is ON
[url] is ON
Smilies are ON

Topic review
   

Expand view Topic review: [SOLVED] Windows XP Catastrophic Failure?

Re: [SOLVED] Windows XP Catastrophic Failure?

by Peke » Mon Apr 03, 2017 6:09 pm

The things are getting worse further as many many many apps drop x86 architecture and focus on x64. It is not just Windows trend, same thing goes with MAC OS X and even my NAS refuse to update software as they require x64 firmware.

Re: [SOLVED] Windows XP Catastrophic Failure?

by Lowlander » Sun Apr 02, 2017 4:06 pm

Complete programs have already dropped support for Windows XP. Microsoft also no longer supports it. However unfortunate this is, as XP was a good OS for many and hardware running it often still runs, it often becomes impossible to run the same code base on newer and older versions of Windows.

Re: [SOLVED] Windows XP Catastrophic Failure?

by MMFrLife » Sun Apr 02, 2017 2:41 pm

yarguy wrote:The previous version of DIscogs Tagger simply wouldn't work with Discogs anymore.
That's a great point, as sites change how things are done over time. Also, XP has long been unsupported and a security risk if using it for net purposes.

Re: [SOLVED] Windows XP Catastrophic Failure?

by yarguy » Sun Apr 02, 2017 2:25 pm

It's not Discogs Tagger that is incompatible, it is the way Discogs itself interacts with other programs that won't work with XP. The previous version of DIscogs Tagger simply wouldn't work with Discogs anymore. And I have to tell you that anyone who wants to keep their program up to date, especially in ways that enhance security is going to end up with their program incapable of running under XP. XP simply is not capable of running some of the newer software security enhancements. I don't want the programs I use to be kept dumbed down and less secure just to keep them compatible with an outmoded operating system.
charmingnathan wrote:This maybe a stupid question, but I shall ask it anyway.

If Discogs Tagger has,in effect, made itself incompatible with XP, is there anyway to downgrade the tagger, i.e. to download the previous version that did and was compatible with XP?

I don't want this to sound like I'm being 'anti' Media Monkey, I would say the same about any piece of software, but it seems a quite over the top requirement that in order to use a piece of software, one has to upgrade their entire O.S.!

Just a thought...

Re: [SOLVED] Windows XP Catastrophic Failure?

by MMFrLife » Sun Apr 02, 2017 12:07 pm

Add-Ons are third party and not MM. If keeping it compatible could be done, MM wouldn't do it, anyway. It would be up to the author. Also,
you should ask the author if he knows of a way to obtain an earlier version if you don't still have a copy of yours.

Re: [SOLVED] Windows XP Catastrophic Failure?

by charmingnathan » Sun Apr 02, 2017 10:52 am

This maybe a stupid question, but I shall ask it anyway.

If Discogs Tagger has,in effect, made itself incompatible with XP, is there anyway to downgrade the tagger, i.e. to download the previous version that did and was compatible with XP?

I don't want this to sound like I'm being 'anti' Media Monkey, I would say the same about any piece of software, but it seems a quite over the top requirement that in order to use a piece of software, one has to upgrade their entire O.S.!

Just a thought...

Re: [SOLVED] Windows XP Catastrophic Failure?

by Peke » Sun Mar 26, 2017 5:28 pm

That should be able to override with hacks. Is investing in dying product worth time and effort?

Re: Catastrophic Failure?

by yarguy » Sun Mar 26, 2017 8:26 am

Peke wrote: Most likely the problem with Discogs is that uses newer components not available in XP even updated in order to work and access data. I'm keeping fingers crossed you will make things working.
This is in fact the case with Discogs. It now uses a version of TLS for SSL that is incompatible with XP and never will be now that XP is unsupported. Sorry. Time to upgrade to a supported version of windows or live with the limitations (which I imagine will only increase over time).

Re: [SOLVED] Windows XP Catastrophic Failure?

by Peke » Sat Mar 25, 2017 6:52 pm

Hi,

I updated list of needed installs here http://forum.mediamonkey.com/viewtopic. ... 60#p434160

Maybe it will help you with MSXML issues, but looks like Win XP usability and of life is very very near. Unfortunately it is a fact we can't escape from.

Re: Catastrophic Failure?

by Peke » Sat Mar 25, 2017 6:19 pm

THX for update.

Well at least we figured out it is not the MMW issue. This time, try your best next time :wink: :roll: 8) :)

Most likely the problem with Discogs is that uses newer components not available in XP even updated in order to work and access data. I'm keeping fingers crossed you will make things working.

Re: Catastrophic Failure?

by charmingnathan » Thu Mar 23, 2017 10:14 am

Thanks MMFrLife, yes some progress indeed! :D

Looks like I.E. has been largely at fault - what a surprise!

At your suggestion, I have created a thread within the Addons section of the forum, but will leave the question open here also, in case anyone has potential solutions for it.

Cheers.

Re: Catastrophic Failure?

by MMFrLife » Thu Mar 23, 2017 8:27 am

Sounds like you are making great progress. :)
Since it seems to be down to the script, you need to ask questions about it in the Discogs Tagger thread.

Re: Catastrophic Failure?

by charmingnathan » Thu Mar 23, 2017 8:21 am

Peke wrote:As you are on Win XP in order to make MM and many other apps using IE and scripting so so working a must installs are.

- Internet Explorer 8 http://download.microsoft.com/download/ ... 86-ENU.exe
- VBscript 5.7 https://www.microsoft.com/en-us/downloa ... px?id=8247
- Windows Media Player 11 and in some rare cases WMF codec updates https://www.microsoft.com/en-us/downloa ... tails.aspx
- DirectX 9.0c http://download.microsoft.com/download/ ... redist.exe

If you have any issues let me know I'll check my backups.
Peke,

Thanks for those links. You will, I hope, be delighted to hear that at last there has been some positive progress, though "not a lot"!

The VBscript refused to install advising that the system was already sufficiently updated.

DirectX installed with no problem, but I.E. 8 has, without doubt, made the most difference.

The situation now is:

Media Monkey opens without any error messages at all;

The Amazon Tagger works, and the blank white window now has visible data and graphics in it, BUT...Discogs Tagger is still screwed.

I have tried with three different artists and bands and get the same error messages, firstly : http://imgur.com/a/VTXua I click on okay, then receive: http://imgur.com/a/pC6NF

Any thoughts please?

Re: Catastrophic Failure?

by Peke » Wed Mar 22, 2017 7:41 pm

As you are on Win XP in order to make MM and many other apps using IE and scripting so so working a must installs are.

- Internet Explorer 8 http://download.microsoft.com/download/ ... 86-ENU.exe
- VBscript 5.7 https://www.microsoft.com/en-us/downloa ... px?id=8247
- Windows Media Player 11 and in some rare cases WMF codec updates https://www.microsoft.com/en-us/downloa ... tails.aspx
- DirectX 9.0c http://download.microsoft.com/download/ ... redist.exe

If you have any issues let me know I'll check my backups.

EDIT: Looks like some .NET Framework ( http://dailypctricks.com/download-micro ... rsion.html ) and MSXML ( https://www.microsoft.com/en-us/downloa ... px?id=3988 ) needs to be installed along with some dependencies like Windows Installer 3.1 Redistributable (v2) ( https://www.microsoft.com/en-us/downloa ... aspx?id=25 )

Re: Catastrophic Failure?

by charmingnathan » Wed Mar 22, 2017 11:24 am

Thanks for your replies Lowlander and MMFrLife, and what have turned out to be very useful references to I.E.

Before attempting to carry out the debug, or download the latest version of Media Monkey, I uninstalled both versions of it, and tested I.E., and received that horrible error message that one sees "Internet Exploiter has encountered a problem and needs to close" over and over again upon launching, so I...

1. Un-installed I.E. from Windows Components via Add/Remove Programs and re-installed;

2. Ran chkdsk c:/ f from the Command Prompt;

3. Right clicked "Install" from the hidden "Ie.inf" file.

With the exception of making I.E. slightly slower to open and crash with exactly the same message mentioned above, the above three points of action made no difference to anything.

As far as I am aware, I am using the version of I.E. that XP is shipped with; I very rarely use it.

Could the I.E. issue be involved in the 'whiteness' issue I am experiencing, as per those pictures?

I assume it is responsible for the other errors?

Your suggestions would be welcome of what to do next please?

Thank you.

Top