Jump to content


Ability to run apup from network location

Started by moorsey, Oct 06 2010 05:26 PM

8 replies to this topic

#1 moorsey

    Newbie

  • Members
  • Pip
  • 6 posts

Posted 06 October 2010 - 05:26 PM

Can't see this requested in here, so thought I would add it. I think a lot of people are likely to store Autopatcher and it's files on a server or NAS box, so being able to run apup to download updates would be smashing!

It currently fails as it can't seem to handle network addresses, this is the case even if the network location is mapped to a drive letter

Currently, the only way I see of getting around this is to copy autopatcher and everything to a local PC, run apup to get updates and then copy it all back.

#2 Cristiano

    Super Helpful Guy

  • Veterans
  • PipPipPipPipPipPip
  • 3,851 posts
  • Gender:Male
  • Location:Brazil (Santa Maria - RS)

Posted 06 October 2010 - 06:44 PM

you are right about that issue. currently, nor autopatcher or apup can run from network locations. i will ask to our developer explain why this happen and if this can be fixed.

thanks

[]s

#3 moorsey

    Newbie

  • Members
  • Pip
  • 6 posts

Posted 07 October 2010 - 06:47 AM

many thanks for the reply!

#4 Antony

    Member

  • Members
  • PipPip
  • 30 posts
  • Gender:Male

Posted 11 October 2010 - 10:36 AM

can you give to me more detailed description of your actions which lead to autopatchers' fail?
because I've tried to run AP from network resource mapped to a drive letter Z - and all was fine..
About pure network paths like: \\my_pc_share\APvault\binaries - yes it will fail - and the reason is that looks like curl(out internal subtool=URLdownloader) does not support saving file with a network paths...

#5 moorsey

    Newbie

  • Members
  • Pip
  • 6 posts

Posted 11 October 2010 - 08:39 PM

View PostAntony, on 11 October 2010 - 10:36 AM, said:

can you give to me more detailed description of your actions which lead to autopatchers' fail?
because I've tried to run AP from network resource mapped to a drive letter Z - and all was fine..
About pure network paths like: \\my_pc_share\APvault\binaries - yes it will fail - and the reason is that looks like curl(out internal subtool=URLdownloader) does not support saving file with a network paths...


Hi Anthony,

I am on Windows 7, Autopatcher is running from a Samba share on my Ubuntu server machine, mapped to drive letter Z on my windows machine.

Autopatcher itself runs fine from a drive letter, or network path.

But apup doesn't seem to run from either on my Windows 7 machine.

UPDATE: As I was writing this, I had a thought that it may be a Windows 7 issue and it does seem that is the case. I just mapped my server to a drive letter on my XP VM and ran apup.exe, it worked without error.

Below is a full log of running apup on my Windows 7 machine, it seems to ignore the drive letter and just interpret it to the actual server name, very odd. It then behaves the same as if you ran apup from a network share path on XP

Spoiler

Will try some things now and post back if I find anything, any ideas?

Cheers

Edited by Antony, 13 October 2010 - 09:15 AM.
spoiler

#6 Antony

    Member

  • Members
  • PipPip
  • 30 posts
  • Gender:Male

Posted 13 October 2010 - 09:20 AM

as you can see from your log initial interpreting of working path is correct:

Quote

Starting APUP From: \\server1\local\Software\Windows Updates\apup

but after that something is breaking, because this correct path is converting in:

Quote

Executing shell command: del "\server1\local\Software\Windows Updates\apup\apup_bin\uz.exe"

as you see we lost here one underlined symbol:

Quote

\\server1
in the second case.

Only one symbol and all is going crazy ((((
I will take a look on this code ...

#7 moorsey

    Newbie

  • Members
  • Pip
  • 6 posts

Posted 14 October 2010 - 07:52 AM

View PostAntony, on 13 October 2010 - 09:20 AM, said:

as you can see from your log initial interpreting of working path is correct:


but after that something is breaking, because this correct path is converting in:


as you see we lost here one underlined symbol: in the second case.

Only one symbol and all is going crazy ((((
I will take a look on this code ...


ahh I see, never noticed that it did have "\\" to start with, just saw the single "\" later on!

If there is anything I can test on Windows 7 here, just let me know!

#8 moorsey

    Newbie

  • Members
  • Pip
  • 6 posts

Posted 29 October 2010 - 11:59 AM

Hi Antony, just wondering if you had had any luck with getting to the bottom of this? Again, happy to test anything out

Cheers

#9 moorsey

    Newbie

  • Members
  • Pip
  • 6 posts

Posted 08 December 2010 - 12:04 PM

bump......
Back to AutoPatcher Feature Requests


1 user(s) are reading this topic

0 members, 1 guests, 0 anonymous users

  1. AutoPatcher Forum
  2. → Development
  3. → AutoPatcher Feature Requests