XYplorer Beta Club

serendipity wrote:btw, I guess you already ruled out this which Filehero encountered:
http://www.xyplorer.com/xyfc/viewtopic. ... 093#p80093

Have you already checked "my" fix?


Cheers,
Filehero

Re FileHero: I did try
"- adding C:\Windows\System32 to the env variable Path will solve the issue"
previously and that didn't help...

Not sure about the others.
I'll try more things if Marcos of Seren want me to.... Otherwise I'm not too worried about making it work.

Update on being connected to my network at work:
Is strange, I was just reviewing my first reply on this thread,
http://www.xyplorer.com/xyfc/viewtopic. ... =45#p80054
and it does appear that my first attempts to use the script WERE when my laptop was plugged in to the network at work. The different things I then tried were done on my Win 7 laptop while it was not attached to the network, but was online via wifi at my house. But I was also trying the suggestions on my Vista home desktop computer, plugged in at home, that is never networked (just plain old Comcast cable internet).

So... After Xmas break, I plugged in at work, and the script DID work. Today, I am at home again and the script is not working on my laptop. And it continues to not work on my plugged-in home desktop.

The fact is that you're experiencing a problem when the script gives all the control to the operating system. XY simply calls an exe shipped with every Windows version and tells it to run a specific VBS script. Everything is up to the OS now. And honestly I can't figure out what's not working on your computer(s):
-firewall: you say it's not the cause
-antivirus: idem
-hips: idem
-command line syntax: checked, no problem
-NTFS permissions of the folder you're trying to writing the txt file to: highly unlikely
-overlong paths: nope
I don't know

Marco wrote:...I don't know

Yea, beats me... I can't help but think it's just some dumb setting that I've put in place and forgotten about. An id10t error

Edit: Ha! Just to muddy things up more.... See video:
http://screencast.com/t/EUvsQjVw
Notice how the first part of the script works, even though the second file in the folder (i.e. the text file) is never created.
(this is on my laptop, from home)

kunkel321 wrote:Edit: Ha! Just to muddy things up more.... See video:
http://screencast.com/t/EUvsQjVw
Notice how the first part of the script works, even though the second file in the folder (i.e. the text file) is never created.
(this is on my laptop, from home)

Yes, pretty weird.
i guess you also tried all this from new install in a non-system drive like D:\ or from usb.
Sometimes access to files in folder such as appdata\roaming can be blocked.

serendipity wrote:Sometimes access to files in folder such as appdata\roaming can be blocked.

I'm starting to think that this is the only explanation possible...

Anyway, I'd like to point out how today's XY beta had a small problem (refer http://www.xyplorer.com/xyfc/viewtopic.php?f=2&t=9089 ). Don fixed the archive on the server without releasing a new version. Well, the script handled this situation smoothly, performing the update again. Other scripts relying on parsing the HTML code wouldn't be able to do so.

Marco wrote:Well, the script handled this situation smoothly, performing the update again. Other scripts relying on parsing the HTML code wouldn't be able to do so.

Yep, both of you have done an awesome job.

Every time I see a developer has obviously done some careful thinking into his design/code it puts a huge smile on my face. To much crappy stuff out there....


Cheers,
Filehero

Hi Marco and serendipity, This issue may be more in Don's hands than yours. I wasn't able to use your Simple Updater for this last beta v12.10.0005 as listed, but it shows up as v12.10.0006. This Beta put in to affect "For current user", "For all users" in Shell integration. I received an error message stating I didn't have administrative rights. Well, I'm the sole user and I am the administrator so something is messed up. I was able to update manually...it brought back memories.
Thanks
Ken

It was my mistake. The change log showed v12.10.0006 instead of v12.10.0005.

klownboy wrote:Hi Marco and serendipity, This issue may be more in Don's hands than yours. I wasn't able to use your Simple Updater for this last beta v12.10.0005 as listed, but it shows up as v12.10.0006. This Beta put in to affect "For current user", "For all users" in Shell integration. I received an error message stating I didn't have administrative rights. Well, I'm the sole user and I am the administrator so something is messed up. I was able to update manually...it brought back memories.
Thanks
Ken

Do you use shell integration? Can you repro, maybe going from to 12.10.0000 to 12.10.0006?

Note that v12.10.0006 does not change anything about shell integration unless you actively change the ticks in Configuration | Shell Integration.

Hey Marco,
What I mentioned earlier occured on a laptop running Windows 7, x64 and no I did not have shell integration. A couple of hours later now at home, I did the update to v12.10.0006 on my desktop with the same operating system with no shell integration and I didn't receive any errors. Go figure! In both systems, users accounts - my name is assigned as administrator with no other users. However, I was at my girlfriends home when I updated the laptop and had the problem, but I don't know why being on her network would affect it - though it is an Apple network

I just accomplished the update on my other desktop which is running Windows 8 x64 with the same user name (Ken) as administrator...no problems. That one was behind a little at v12.00.0013 when I did the update.

So maybe it was the Apple network, but then again I've done so many updates using Simple Updater from her place in the past without issues. That's why it strikes me as being unusual. I wouldn't do anything at this point unless someone else reports something.

Thanks,
Ken

I think it worked because I corrected my typo.

admin wrote:I think it worked because I corrected my typo.

No, SU doesn't read the number version. Sometimes if files are still locked by a process UAC can ask for permissions and stuff like that. But that's beyond SU and XY.

Hey again Marco and Don,

I just received the same error message concerning admin permission that I mentioned a few posts ago going from v12.10.0011 to v12.10.0012. This time it occurred on a desktop that I didn't have a problem with before. However, I noticed I had XY's help file up and running when I received the message (it was running when I started Simple Updater). This time I closed the help file and hit "Retry" in the message box and the update proceeded and completed. It's very possible the help file was up and running the last time as well. I've been using highends help script quite a lot so I hadn't noticed that the help was running in the background.

Update: I ran Simple Updater on my laptop also with the help file purposely running in the background and received the same the message about admin rights. I closed it and updater completed. So try it yourself. Maybe you'd want to put something in that checks if the help file is running and shut it down if it is? Note: In all my cases the help was run through highends new Help script, but I doubt that makes any difference in how the Help was initiated.
Ken