TeraByte Product Release Thread

Discussion in 'backup, imaging & disk mgmt' started by TheKid7, Aug 19, 2011.

  1. Brian K

    Brian K Imaging Specialist

    Joined:
    Jan 28, 2005
    Posts:
    12,175
    Location:
    NSW, Australia
    Mohamed,

    That is great news. Thanks.

    You now have PHYLock ver 11. The previous one was ver 10. It will be interesting to see if it works better than ver 10 in your computer.
     
  2. aladdin

    aladdin Registered Member

    Joined:
    Jan 9, 2006
    Posts:
    2,986
    Location:
    Oman
    Thanks Brain, would test PHYLock ver 11 in a day or two and post the results.

    Best regards,

    Mohamed
     
  3. puff-m-d

    puff-m-d Registered Member

    Joined:
    Feb 13, 2002
    Posts:
    5,703
    Location:
    North Carolina, USA
    Hello,

    First off I am on Windows 8.1 Pro with Media Center (MBR not UEFI) using the new release of IFW 2.84. I run the TBWinRE script and get an "One or more files may be missing and the media may not boot" as the script finishes. I proceed on to MakeDisk in order to create an ISO but that option is no longer there. Instead I proceed to make a bootable UFD (even though I got the above error). I test the bootable UFD and it works fine so the supposed missing files do not affect it.

    Now here is my issue. I use a software called YUMI which allows you to boot into multiple ISO's instead of having to have a separate UFD for each. This has worked fine with IFW 2.83 and Windows 8, but the upgrade to IFW 2.84 and/or the upgrade to Windows 8.1 seems to have broken the option to create an ISO and your only option now is to create bootable media. Have I missed something in trying to create the ISO or is it no longer possible? I only have one UFD as my funds are extremely limited being on a fixed income and really like the convenience of keeping all of my bootable software on just the one UFD. Can anyone help me as to what I may be doing wrong or is ISO creation indeed not possible now?
     
  4. aladdin

    aladdin Registered Member

    Joined:
    Jan 9, 2006
    Posts:
    2,986
    Location:
    Oman
    Hi puff-m-d,

    Please read my above posts having trouble installing v2.84 with AVAST being on. I had to turn off AVAST to install v2.84

    After the installation, I checked and found that during my installs when AVAST was on, it quarantined a file as a virus. Maybe, a false negative.

    Check your AV. Turn off your AV and then try to reinstall v2.84 and see if you are still having problems.

    Best regards,

    Mohamed
     
  5. MudCrab

    MudCrab Imaging Specialist

    Joined:
    Nov 3, 2006
    Posts:
    6,483
    Location:
    California
    puff-m-d,

    Windows 8.1 removes the files for creating a bootable ISO/CD.

    If you have Windows 8.0 you can copy the etfsboot.com file from the C:\Windows\Boot\DVD\PCAT into your TBWinRE folder. Then run MakeDisk again.

    You can also get the file from a backup of your Windows 8.0 system (TBIView/TBIMount) or from an existing TBWinRE folder on Windows 8.0 (TBWinRE must have been created at least once for the file to have been copied there).
     
  6. valnar

    valnar Registered Member

    Joined:
    Sep 30, 2006
    Posts:
    137
    I also was having a problem with Avast installing this latest 2.84, but I blame Avast. About a month ago it wiped out my video drivers because it thought it was a virus and turned my PC back to the dark ages at 16 colors. I could also not figure out how to tell Avast to ignore the file without submitting it to Avast, and even that did not work.

    As much as I liked Avast for the past several years, these things are unacceptable. I have removed it and paid for Avira instead.
     
  7. Brian K

    Brian K Imaging Specialist

    Joined:
    Jan 28, 2005
    Posts:
    12,175
    Location:
    NSW, Australia
    MudCrab,

    I have Win8.1 and etfsboot.com is present in my tbwinre folder. I assume it must have been there before I upgraded Win8 to Win8.1. I haven't uninstalled IFW at any time.

    An ISO was created from 2.84.

    Interesting.
     
  8. puff-m-d

    puff-m-d Registered Member

    Joined:
    Feb 13, 2002
    Posts:
    5,703
    Location:
    North Carolina, USA
    Hello,

    I did a clean install of Windows 8.1 as I had difficulties upgrading from 8. I imagine that the clean install is why I do not have that file present in the TBWinRE folder whereas you upgraded and the file was retained.

    I have the WinPE (ADK for 8.1) installed as I needed it to make an ISO for my antivirus. I just went ahead and created an IFW 2.84 ISO using WinPE instead of WinRE a and that works fine...
     
  9. Brian K

    Brian K Imaging Specialist

    Joined:
    Jan 28, 2005
    Posts:
    12,175
    Location:
    NSW, Australia
    MudCrab and Kent,

    I tested a clean Win8.1 install. After running TBWinRE.cmd I saw the Missing Files message and couldn't see any target drives (CD/UFD). I copied etfsboot.com to the tbwinre folder, ran TBWinRE.cmd and again saw the Missing Files message but I could see target drives (CD/UFD).

    I checked my old tbwinre folder and it also contained efisys.bin. This file was copied to the tbwinre folder in the clean Win8.1 system. TBWinRE.cmd then ran without a Missing Files message.
     
  10. puff-m-d

    puff-m-d Registered Member

    Joined:
    Feb 13, 2002
    Posts:
    5,703
    Location:
    North Carolina, USA
    Hello,

    Since I did the clean install of Windows 8.1, I then transferred all backups of my files and then started my backup routines fresh. Because of this, I did not have copies of those two files that I could copy. I checked my TBWinPE folder and those two files were present, so I copied them over to my TBWinRE folder and ran the TBWinRE script. I had no errors this time and now had the option to create an ISO when MakeDisk was ran. I created the ISO and it tests good. The strange thing is the difference in the size of the ISO's, 223 MB for the TBWinPE ISO and 298 MB for the TBWinRE ISO. They both seem to have the same features and function the same, so I wonder why the difference in size?
     
  11. MudCrab

    MudCrab Imaging Specialist

    Joined:
    Nov 3, 2006
    Posts:
    6,483
    Location:
    California
    Brian,

    On your clean 8.1 install were you using TBWinRE v1.6? It shouldn't have had a problem with the missing file and you should still have seen any UFD devices in MakeDisk.

    ------------------
    puff-m-d,

    The WinRE has WinRE-specific files in it (based on WinPE). Also, when you created the builds were they the same architecture (x86 or x64)? The WinRE is probably x64, which is larger than the x86 file.
     
  12. puff-m-d

    puff-m-d Registered Member

    Joined:
    Feb 13, 2002
    Posts:
    5,703
    Location:
    North Carolina, USA
    Hello,

    My system is 64 bit so I assume the WinRE was 64 bit also. With the WinPE script you can choose either 32 bit or 64 bit, and I choose the 64 bit. So as far as I know, both versions are 64 bit. I was looking at both ISO's and the main difference in size was the boot.wim file, 179 MB for the WinPE and 263 MB for the WinRE.
     
  13. Brian K

    Brian K Imaging Specialist

    Joined:
    Jan 28, 2005
    Posts:
    12,175
    Location:
    NSW, Australia
    MudCrab,

    IFW hadn't been installed in that OS until today. IFW 2.84. I used the tbwinre folder in V2 folder. TBWinRE.cmd says ver 1.6.

    I can restore that OS to "yesterday" if you would like me to try something.
     
  14. HAN

    HAN Registered Member

    Joined:
    Feb 24, 2005
    Posts:
    2,098
    Location:
    USA
    So does this mean the only bootable WinRE that we can make is for USB?

    I've read the posts above that the missing files can be inserted and things seem to work. But IMO, that misses the point. Most users won't have access to the missing files. Right?

    I still like booting from a CD. Or at least having the option...
     
  15. MudCrab

    MudCrab Imaging Specialist

    Joined:
    Nov 3, 2006
    Posts:
    6,483
    Location:
    California
    I also still like being able to create ISO files and CD/DVD discs (I use them all the time). For now, you'll need to copy the files in. There may be a better fix later.

    Users that had Windows 8.0 and upgrade could hopefully get them from a backup. Users with a clean 8.1 install wouldn't have them on their system. It's possible the Windows 7 versions may work also, but I haven't tried them.

    TBWinPE is also an option, though it requires large download.
     
  16. TheKid7

    TheKid7 Registered Member

    Joined:
    Jul 22, 2006
    Posts:
    3,576
    Image for UEFI 2.84 (ifu-en.zip) was released on November 5, 2013:

    Image for UEFI 2.84 (ifu-en.zip) Changes:
     
  17. aladdin

    aladdin Registered Member

    Joined:
    Jan 9, 2006
    Posts:
    2,986
    Location:
    Oman
    Hi Brian,

    As promised you, I tried the PHYLock ver 11. Please see the attached image:

    1. It stopped working after 45 minutes, very frustrating.

    2. The imaging with IFW is very, very slow in comparison to other imaging programs.

    Best regards,

    Mohamed
     

    Attached Files:

  18. Brian K

    Brian K Imaging Specialist

    Joined:
    Jan 28, 2005
    Posts:
    12,175
    Location:
    NSW, Australia
    I can backup my Win8.1 partition in 2 minutes.

    Sorry, I don't know the answer to your problem. I hope MudCrab can offer more insight.
     
  19. aladdin

    aladdin Registered Member

    Joined:
    Jan 9, 2006
    Posts:
    2,986
    Location:
    Oman
    Dearest Brian,

    Many thanks. I will wait to see what recommendations/help MudCrab will come out with.

    Best regards,

    Mohamed
     
  20. aladdin

    aladdin Registered Member

    Joined:
    Jan 9, 2006
    Posts:
    2,986
    Location:
    Oman
    Here is an image of my PHYLock settings:

    Best regards,

    Mohamed
     

    Attached Files:

  21. valnar

    valnar Registered Member

    Joined:
    Sep 30, 2006
    Posts:
    137
    aladdin,
    Why would you bump up the RAM cache to 128MB then keep it in disk cache? Turn off disk storage.
     
  22. The Seeker

    The Seeker Registered Member

    Joined:
    Oct 24, 2005
    Posts:
    1,339
    Location:
    Adelaide
    Image for Windows: Upgrade History

    Image for DOS: Upgrade History

    Image for Linux: Upgrade History

    BootIt® Bare Metal: Upgrade History

    OSD Tool Suite: Upgrade History

     
  23. mantra

    mantra Registered Member

    Joined:
    Jan 25, 2005
    Posts:
    6,194
    hi
    is there a way to copy my w7 to a new solid disk without unplug the source solid disk?

    i mean a i have 2 solid disk , in 1 solid disk i have w7 plugged , a second solid disk empty plugged too
    i want to copy (or create an image of my w7 and restore) to the second solid disk

    now at the reboot i have 2 solid disks with both the same os

    does the old trick
    Code:
    HKEY_LOCAL_MACHINE\SYSTEM\MountedDevices
    and delete all the key like
    Code:
    \??\Volume{.....
    work to boot without unplug the 1 solid disk

    at the boot w7 should re-create the registry key partition ,and doesn't mess up


    thanks
     
  24. MudCrab

    MudCrab Imaging Specialist

    Joined:
    Nov 3, 2006
    Posts:
    6,483
    Location:
    California
    Just use the Change Disk ID and GUIDs option when copying/restoring the disk. IFW will make the necessary changes.
     
  25. mantra

    mantra Registered Member

    Joined:
    Jan 25, 2005
    Posts:
    6,194
    Hi
    for the winpe i create an iso and usb stick v2.83 , haven't found time to update , can i use this version ? or should i update ? i found not so easy creating a winpe

    are Change Disk ID and GUIDs options in the restore dialog options?

    does these option the same trick of deleting the keys \??\Volume{..... in HKEY_LOCAL_MACHINE\SYSTEM\MountedDevices before create the image or copy the disk?
     
  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.