Image For Windows

If you're referring to the OSD scripts they can be installed with IFW, at OSD/scripts. This of course depends on if and where OSD is installed

 

That works! Thanks. I guess I'll need to do that every time I need them. I'm not sure why using OSD is not a simple button that works inside any PE though. I mean, why is it included in the IFW installer at all since it cannot be used in Windows? I wish IFW wasn't so Frankensteined together and had a more unified GUI; TBIView is a separate app, OSD is separate, the WinRE builder is separate, BootIT is separate, etc. There's no unity in its parts.

 

Now that you already know how the workaround works, don't forget to insert your license for TBOSD tools before anything. Click on TeraByte OS Deployment Tool Command Prompt, it should ask for your licence:



Although I don't really know if it is really necessary for the scripts to do their job because I have never made use of tbosd tools ever, to be honest. Am I missing something good?

 

OSD scripts might not ever be needed. But in my case, I guess I'm just trying to be prepared to restore to different hardware. My system is about 7 years old and is acting hinky, so it's time to start thinking about replacing it. I'd rather have things squared away now then to have to worry about not being able to use it when I need to.

 

I use the TeraByte Explorer script most frequently. To copy files to hidden partitions. For example, I have hidden IFL and TBWinPE partitions.

OSDTool script to remove drivers when restoring to dissimilar hardware.

Configure Boot to create booting files in UEFI systems. Microsoft.xxx.

TBOSDT to analyse partitions.

Change Disk Type occasionally.

Assign Drive Letters with MBR systems. Rarely.

 

hi and @Brian K
about "change disk type" and "restore windows registry" scripts
do they need to perfom a backup and a restore ?
or just partition work and will perform actions without create an image and restore them
thanks , and for the link

 

I think @n8chavez , @Mr.X & @Brian K (maybe even better with @pandlouk but haven't seen him in a while) can better answer those questions... I am not a script user when using IFW.

 

mantra, those scripts don't use a backup image or a restore.

 

hi
nice , i have never used
they work with image for windows and dos and BIBM , but not with image for linux right?
thanks Brian

 

They work from IFL too.

 

It was a while since i used IFW and when using it now, restoring works differently. I backup as usual and then create a Bat file for Reboot restores, but when getting into the restore environment, it is not automatic anymore, i have to start the restore from a screen that warns about erasing everything and, confirm for reboot when done.

Am i missing something or has it changed? Before the restore was fully automatic.


Just installed and tried.3.62, no problems. 3.64 is as former described

 

No one?!?
The automatic restores are in this way neutered and the program has somewhat lost its attractiveness

 

I'm sorry, I don't use scripts.

 

Dont be, it is solved.
How, dont really know but a total reinstall and cleaning of the registry before a new install of 3.64 seems to have fixed it.

 

I wanted to do a full backup just now, but I have noticed that a parameter has changed when comparing the past with today. Not sure what it means going forward, and if it affects any newly created backup.

 

I'm pretty sure we're going to need more information about what's actually going on if you want anyone to help you. It looks like you have a mounted virtual drive. Why does that matter?

 

Greetings. Just built a new PC and running Win10. I have an old version of IFW, ver 2.8 I believe. I want to clone (copy) the current drive to another for backup. I have been doing this for the last 12 years. Luckily never had to use it.

Do you suggest I upgrade my IFW version to the current one? My current boot drive is an M.2 device and I want to clone it to a USB 2.5" SSD drive and have it bootable. I think I read in a post above someone recently tried this and it did not work. Hmm....

 

tyee,

I haven't used ver 2.8 for years. You could try it.

I'd create an Entire Drive image of the M.2 drive. I never create bootable copies of drives for backup purposes. I know some people do this but it's the minority.

 

Thanks for the info Brian. I have another technical question about making the copy viewable while the original source drive is still installed.

When I copy my c: and make the clone, windows will not mount it because the disk signature is the same as the c: boot drive. That's normal and fine. If I go into disk management, right click the cloned drive and select "Online", windows gives it a new disk signature. It is now able to be viewed, but of course it will not boot anymore because the BCD store has the original disk signature of my c drive. To make bootable I believe all I have to do is run this command assuming D drive is the drive in question - "bcdboot c:\Windows /s D: /f ALL". I think it's as simple as this. Now both the original c: and the cloned d: are identical with no disk signature collision as they call it. Have you ever tried this or read about it before? Now if my c drive fails, I just reboot and select my d drive to boot from and I'm back in windows in a couple of minutes!

 

Update - Just found out that Macrium Reflect automatically changes the disk signature so no collisions occur in windows. I wonder if all the other cloning apps do the same nowadays?

 

For IFW you can do this...

 

Yes, that's what I needed to know thanks!

 

tyee,

Have you been cloning the OS to a HD/SSD in a USB enclosure?
MBR or UEFI system?
Any problems with booting the cloned OS? You mentioned, "never had to use it".

 

I cloned to ssd with one of those 1 ft sata to usb3 cables. Typically 5 mins for Win7. I would remove it from the cable and install it where the original drive was if there was a failure. A few days ago i built a new win10 PC. I want to clone it too and have it available at any time by just plugging into a usb port and reboot to it. I recently updated to the current version of IFW suite and did the copy/clone to another ssd using one of those short cables. After cloning I checked disk manager to see if it was online and it was, meaning no disk signature collision. So now ive been reading how to add this drive to my system so if I want I can dual boot and to see if it is indeed bootable. But there is a problem . When my new PC boots I get no POST display until I get to the Win10 login screen . If I add this drive to my boot manager I probably won't see the choice select screen to choose the OS to boot into. So at this point I don't know if my clone is Bootable. Any tips to get my POST screen to show?

 

Your System should have an F<key> that takes you to the UEFI BOOT menu, if not there'll be another F<key> that takes you to a System Menu which should offer a way to the BOOT menu.