Image For Windows

Discussion in 'backup, imaging & disk mgmt' started by Stigg, Apr 15, 2014.

  1. Brian K

    Brian K Imaging Specialist

    Joined:
    Jan 28, 2005
    Posts:
    12,179
    Location:
    NSW, Australia
    OK. Add /min to the "Add arguments". Put it in front of /b

    Does it work?

    /min
     
  2. Hadron

    Hadron Registered Member

    Joined:
    Apr 1, 2014
    Posts:
    2,145
    I have worse problems now.
    I just tried to run the task the IFW created, and it won't even run.
     
  3. Hadron

    Hadron Registered Member

    Joined:
    Apr 1, 2014
    Posts:
    2,145
    I tried that. It should work, but prior to adding that I tested it and IFW won't even run at all with or without the /min argument.
     
  4. Brian K

    Brian K Imaging Specialist

    Joined:
    Jan 28, 2005
    Posts:
    12,179
    Location:
    NSW, Australia
    I just tried it and it worked. Did you have a space before /min? And a space after /min?

    Sounds like your line is corrupted. Delete the task and create another.

    Better still, post your Add arguments line. Copy/Paste here.
     
  5. Hadron

    Hadron Registered Member

    Joined:
    Apr 1, 2014
    Posts:
    2,145
    /min /wait /b /uy /um /d:w0 /f:"D:\SystemBackup\Image_for_Windows\Backup-w0-$~YYYY$-$~MM$-$~DD$-$~HHMM$"


    Everything above is what IFW created except for /min.
    But it doesn't run with or without it.
     
  6. Brian K

    Brian K Imaging Specialist

    Joined:
    Jan 28, 2005
    Posts:
    12,179
    Location:
    NSW, Australia
    Is that the whole line? Mine started with the TeraByte path. Or it did after adding /min.
     
  7. Hadron

    Hadron Registered Member

    Joined:
    Apr 1, 2014
    Posts:
    2,145
    This is in the Program Script line:
    "C:\Program Files (x86)\TeraByte Drive Image Backup and Restore Suite\imagew64.exe"

    This is in the Add Arguments line:
    /min /wait /b /uy /um /d:w0 /f:"D:\SystemBackup\Image_for_Windows\Backup-w0-$~YYYY$-$~MM$-$~DD$-$~HHMM$"

    The arguments contain the image destination, which is: D:\SystemBackup\Image_for_Windows
     
  8. Brian K

    Brian K Imaging Specialist

    Joined:
    Jan 28, 2005
    Posts:
    12,179
    Location:
    NSW, Australia
    Weird. Mine is now like yours.

    Try changing to

    /wait /min /b ............

    Does that work?
     
  9. Hadron

    Hadron Registered Member

    Joined:
    Apr 1, 2014
    Posts:
    2,145
    Here is the full thing all together in Task Scheduler.

    IFW Line.jpg
     
  10. Hadron

    Hadron Registered Member

    Joined:
    Apr 1, 2014
    Posts:
    2,145
    No.
     
  11. Hadron

    Hadron Registered Member

    Joined:
    Apr 1, 2014
    Posts:
    2,145
    I'm going to try a reboot.
    Be back soon.
     
  12. Hadron

    Hadron Registered Member

    Joined:
    Apr 1, 2014
    Posts:
    2,145
    No.
    It refuses to run even after a reboot.
     
  13. Brian K

    Brian K Imaging Specialist

    Joined:
    Jan 28, 2005
    Posts:
    12,179
    Location:
    NSW, Australia
    Delete it and create another. While you are creating the Task, put /min in the Run field.

    /wait /min /b ......

    I assume you will put a tick in "Run only if logged on". If you don't the running task will be invisible. Maybe that's what was happening?
     
  14. Hadron

    Hadron Registered Member

    Joined:
    Apr 1, 2014
    Posts:
    2,145
    This is the task copied from IFW Scheduled Tasks.

    "C:\Program Files (x86)\TeraByte Drive Image Backup and Restore Suite\imagew64.exe" /min /wait /b /uy /um /d:w0 /f:"D:\SystemBackup\Image_for_Windows\Backup-w0-$~YYYY$-$~MM$-$~DD$-$~HHMM$"
     
  15. Brian K

    Brian K Imaging Specialist

    Joined:
    Jan 28, 2005
    Posts:
    12,179
    Location:
    NSW, Australia
    Looks OK. Delete it.
     
  16. Hadron

    Hadron Registered Member

    Joined:
    Apr 1, 2014
    Posts:
    2,145
    OK.
    By the way. I am also having trouble with PHYLock.
    I have Use VSS when available, ticked, but it still wants to use PHYLock.

    No problems at all using V2 last night.
     
  17. Brian K

    Brian K Imaging Specialist

    Joined:
    Jan 28, 2005
    Posts:
    12,179
    Location:
    NSW, Australia
    In PHYLock Settings did you Disable Usage?
     
  18. Hadron

    Hadron Registered Member

    Joined:
    Apr 1, 2014
    Posts:
    2,145
    OK. I hadn't, but now it's done.
     
  19. Hadron

    Hadron Registered Member

    Joined:
    Apr 1, 2014
    Posts:
    2,145
    Back to Task Scheduler.
    Still no good.
     
  20. Brian K

    Brian K Imaging Specialist

    Joined:
    Jan 28, 2005
    Posts:
    12,179
    Location:
    NSW, Australia
    In Task Scheduler, General tab for that IFW Task, do you have...

    Run with highest privileges
    Configure for Windows 10
    Run only when user is logged on
     
  21. Hadron

    Hadron Registered Member

    Joined:
    Apr 1, 2014
    Posts:
    2,145
    I thought I might try a manual backup. I thought it may help to get it working.
    Disabling PHYLock causes other problems.

    IFW_Lock.jpg
     
  22. Brian K

    Brian K Imaging Specialist

    Joined:
    Jan 28, 2005
    Posts:
    12,179
    Location:
    NSW, Australia
    Good thinking. Install Ver3 again using the PHYlock setting. Over the top of your current install. Restart and try a manual PHYLock backup.
     
  23. Hadron

    Hadron Registered Member

    Joined:
    Apr 1, 2014
    Posts:
    2,145
    Configure for Windows 10 got the Task Scheduler working. Strange that IFW can't configure that correctly.
    But I can't see IFW running although it is running in Task Manager. It must have an invisible setting somewhere.

    Edit: It's not working.
    The file it is trying to create is stuck on 70 MB.
     
  24. Brian K

    Brian K Imaging Specialist

    Joined:
    Jan 28, 2005
    Posts:
    12,179
    Location:
    NSW, Australia
    Mine runs invisible if I have "Run whether the user is logged on or not".
     
  25. Hadron

    Hadron Registered Member

    Joined:
    Apr 1, 2014
    Posts:
    2,145
    That's the setting I have. Do you also have Windows 10 selected? Mine was Windows Server, Windows XP or Windows 2000.

    The trouble with invisible is that I can't see if there is an error, which there probably is.
     
  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.