Ok John it seems Windows XP SP3 is messing with the platform,
Exception EReadError in module PortableAppsMenu.exe at 00019c63
error reading trayiconMenu.visible: Cannot create shell notification icon
this is for your build and also the unofficial build by xrxca and Smithtech.
My system specs are:
Manufacturer: TOSHIBA
Processor: Intel(R) Celeron(R) CPU 550 @ 2.00GHz
Memory: 1014MB RAM
Hard Drive: 60 GB
Video Card: Mobile Intel(R) 965 Express Chipset Family
Monitor: Default Monitor
Sound Card: Realtek HD Audio output
Speakers/Headphones:
Keyboard: USB Root Hub
Mouse: USB Root Hub
Operating System: Windows XP Professional (5.1, Build 2600) Service Pack 3 (2600.xpsp.080413-2111)
if you need anything more just say the word
I have XPSP3 and it does work.
Did it stop working right after you upgraded it?
"What about Love?" - "Overrated. Biochemically no different than eating large quantities of chocolate." - Al Pacino in The Devils Advocate
To make it short, Yup
your friendly neighbourhood moderator Zach Thibeau
this problem could be just restricted to XP MCE try it on another xp pc if possible i have xp pro and it works fine
well XP MCE is Professional just with addons.
your friendly neighbourhood moderator Zach Thibeau
Windows XP SP3 works just fine. I use it daily. And so do hundreds of thousands of others. So, it's something wrong with your specific PC. And if it can't create the shell icon, I'd be willing to wager that you don't have a tray and are probably using an alternate Windows shell.
Sometimes, the impossible can become possible, if you're awesome!
sorry for the delayed response John, I do have the tray and I am not using an alternate windows shell, here is a screen shot of my desktop.
>>Preview
your friendly neighbourhood moderator Zach Thibeau
Reboot and close down everything optional (including all the cruft in the tray) and try again. Something is preventing it. Maybe a software firewall or something?
Sometimes, the impossible can become possible, if you're awesome!
Well I uninstalled a program called wefi and it started working again problem solved
your friendly neighbourhood moderator Zach Thibeau