Independent Restore Imaging

Okay so I have tbosdtw.exe running in a windows 7 based environment. What do I do from here?

 

TBOSDT needs scripts to run; it is not independent. I'm guessing after just running the exe file you're looking at a blank command prompt. The good thing is that these scripts are included with the pro version. You need to run osdtool.tbs. I create a run file names "tool".run that does that for me. It simply has the command "runtbs osdtool.tbs". A bat file names "Run Me.bat" has the commands "tbosdtw tool2.run". It first runs the exe and then tells the exe to run the scripts. That way all I have to do it run the bat file. Then answer the prompts as needed. PM me is you need those files. Again, they will only work with the paid version.

 

Okay so I tried creating the bat file and run file like you said, but it doesn't work for me. A command box pops up for a split second and then disappears.

I did manage to get osdtool.tbs to run from tbosdtw.exe. I used it to install the default IDE drivers, but I still get a BSOD when I try to boot to this drive.

 

Then my guess is that you did not install the right drivers, but without knowing more about this exact situation, like the BSOD message, there's not much more I can add. Try adding a new HAL, or perhaps restoring the MBR.

 

I'm trying to get an IDE drive from a desktop to boot on a laptop. It is connected via an IDE to usb2 cable directly from the back of the drive to the laptops usb ports. I thought I don't need to provide drivers for the script if its an IDE drive.

If I try to use the script to change the Hal, I have about 6 choices. How do I decide which one to use? I'll tell you what the BSOD says if I ever get enough time to look at it before it disappears.

 

Brian - I have a quick question for you. I like ready this thread, it's so packed with useful information. Kudos to the guy that started it. My question is, based on posts #79 and #83 it seems like there does not need to be any driver injection of HAL manipulation when you are restoring a Windows 7 system to older hardware (even if it is completely different). It seems, based on those posts, that is correct. And, if that's correct, then it seems logical to say that if a user has an image of a Windows 7 system then there is no need for third-party H.I.R. applications, right? If they are not needed (with Windows 7) then why is it being advertised as a component in most "top-tier" imaging applications?

I still find this topic very interesting, since it is the thing that all computer users have in common, and it is the only thing that is guaranteed to fail at some point.

 

Nate,

Good question. Win7 only has one HAL and has native support for AHCI. I haven't had the opportunity to restore an image taken from an Intel processor computer to an AMD processor computer or vice versa. Maybe HIR is needed for this but I don't know.

As we know, if you can get the computer to boot into Windows you can load other hardware drivers at your leisure.

 

XP cannot run natively from a usb.

Take a look on the following links to get started
http://www.911cd.net/forums//index.php?showtopic=14181
http://forums.ngine.de/viewtopic.php?f=4&t=1243&sid=cee74a9272bfcd6f0de734850b4ff02e
http://www.usboot.org/tiki-index.php

Panagiotis

 

nineine,

I think this is an easy method...

http://www.terabyteunlimited.com/tbosdt.htm

USBBoot 1.16 TBS script to enable booting XP from a USB drive.

 

I've had the same results with Windows 7 as Brian K. For insurance, you can also make a Sysprep-based image of your source computer while it's still working, just in case, as detailed here.