Toshiba recovery image to USB
#1
Posted 25 February 2010 - 04:37 PM
I humbly ask for help, or some pointers in the right direction, for assistance with a problem I am finding a bit of a challenge.
I have a Toshiba netbook running XP that allows me to create a recovery DVD. I have made an ISO of the recovery disk and have been fumbling around for some time now trying to get this to boot from a flash drive. The fumbling part of this statement should give you an indication of the level of progress I have made
I have tried using uunetboot to load the image, but didn't have any success (booted with a default option and would go no further). I have also tried extracting the boot sector with BBIE in the hope that maybe I could figure out what to do with it a reload it to the flash drive with mkbt then copy the ISO files over, but I was out of my depth here and had no idea if this would work, so I bottled out. I am not even sure if the flash drive is supposed to FAT or NTFS formatted
In case it may be useful, the visible structure of the ISO is reproduced (rougly) below:
It has a bootmgr file and a setinv.ini at its root and a bunch of folders;
A Boot folder containing a bcd file, boot.sdi and etfsboot.com
An EFI\microsoft\boot folder containing another bcd file
A HDDPrep folder containing a bootmgr file and a boot directory the same as the first, but also a sources directory with a boot.wim
A Sources folder with another boot.wim
A Tools folder containing imagex and some other bits
And a ZZImg folder with a few .swm files and a .crc (which I gather is just a multipart .wim)
My thanks in advance,
Tony
#2
Posted 25 February 2010 - 04:52 PM
install grub4dos to your usb.( you can use BOOTICE(gui tool) to install grub4dos)
copy the iso file to root of your usb.
use this code for booting iso file.
(assuming name of iso file is recoverydvd.iso)
title recoverydvd find --set-root /recoverydvd.iso map /recoverydvd.iso (0xFF) || map --mem /recoverydvd.iso (0xFF) map --hook root (0xFF) chainloader (0xFF)
tell me if this work or if you want to ask in detail.
#3
Posted 25 February 2010 - 04:55 PM
In case it may be useful, the visible structure of the ISO is reproduced (rougly) below:
Maybe if you could run a:
DIR D: /S>C:\DVDdir.txtthen compress DVDdir.txt in a .zip file and post it as an attachment, we would have a less rough idea of the DVD structure .
Generally speaking .SWM files are tricky business, a special app may be needed to get something out of them.
Here an user started playing the game and soon abandoned it :
http://www.msfn.org/...-recovery-disc/
If your DVD is like that one no need for the DIR, of course.
Wonko
#4
Posted 25 February 2010 - 09:04 PM
I didn't expect such a rapid response
@shamurshamur
I'll give grub4dos a try and let you know how I get on... thanks for the usage instructions, will save me lots of reading.
@Wonko
Heh... yes, maybe outputting the structure to a text file would have been more sensible. You even managed to suggest it without sarcasm, for which I thank you
The structure is very similar to the post you reference, with some very minor differences. I have attaached a zip anyway, as it is only 1kb. It looks to me like the OP of the thread was trying to strip out some of the bloatware from his images... I want to copy the entire lot to a bootable USB otherwise unmolested, so I hope this makes the task a little less tricky!
I'll let you know how I get on after having a go with grub.
Cheers,
Tony
Attached Files
#5
Posted 26 February 2010 - 12:41 AM
I've made some progress, by using BOOTICE to create an UltraISO USB-HDD MBR and a PBR that points to BOOTMGR.
The ISO has a BOOTMGR file, so I copied this onto the flash drive with the rest of the files and booted the netbook. It seemed to load up OK, as I got the Windows is loading files... progress bar and then the black boot window with the Windows style progress bar like you get when you boot Vista.
Next I get a DOS box with a title x:\windows\system32\cmd.exe - startnet.cmd. The text in the DOS box says 'Waiting for ODD to become available ... ' and does not progress.
I created the original recovery disk by jerry rigging a DVDRW through a 3.5" caddy I have, as the recovery software will only run with an optical drive attached and will only output to said optical drive.
I am now stumped again, as the waiting for ODD message must mean that the recovery software is not looking for the image on the flash drive and is seeking an optical drive to restore the image from. Any ideas please?
Thanks,
Tony
EDIT: shamurshamur, could you tell me what file I am supposed to edit for grub with the code you specify please. Thanks
#6
Posted 26 February 2010 - 01:32 AM
for installing grub4dos on pen drive by bootice:
1) choose option "process MBR"
2) then choose "grub 4 dos 0.4.5a"
3) press "install/config" button
4) now manually copy files "grldr" and "menu.lst" to root of the pendrive. ( get these 2 file from here grub4dos)
The code which i have given , should be copied in to file menu.lst ( use any text editor) .
The iso file(recoverydvd.iso) you are copying to the pen drive should be contiguous ( it should be defragmented after copying)
PS:
i am not guranteeing that this method will work , and after seeing the freakishly large size of the iso file i am less hopeful.
read the threads mentioned by @wankothesane in previous post.
cheers!!
#7
Posted 26 February 2010 - 01:47 AM
I've just tried loading manually with grub, by booting into grub and entering those commands from the command line (I've just seen your post) and I got the following message after executing the chainloader (0xFF) command:
Load segment: 0x0 System Type: 0x0 Sector Count: 0X4
Load RBA: 0x37 Boot Type: 0 = No Emulation
Not sure if that would be the expected outcome from entering the commands into menu.lst, I assume that is a sort of batch file for grub and would have the same effect?
Thanks for your help so far... even if I get nothing more than the headache this has given me, at least I have learnt a thing or two today
#8
Posted 26 February 2010 - 01:52 AM
I can see why you may be concerned about the iso size. Is it likely that an image of that size would remain in contiguous sectors, even if the disk was defragmented after copy??
Ta,
Tony
#9
Posted 26 February 2010 - 02:19 AM
Unfortunately, I got exactly as far as the other method I tried in my post #5
I think that is the proverbial fat lady I hear singing, so time to abandon this particular cause for one that has better possibility of a successful outcome.
Thanks to both yourself and Wonko for the guidance.
Tony
#10
Posted 26 February 2010 - 08:53 AM
I mean, nice try but it was likely that it wouldn't have worked, the grub4dos emulation of a CD/DVD is only "partial", and the stoopid guys at Toshiba (not that they are worse than those at Sony or HP, BTW ) like to have things done in a complex way.
I would try the manual imagex approach:
http://www.msfn.org/...showtopic=89955
http://www.msfn.org/...howtopic=109293
Wonko
#11
Posted 26 February 2010 - 12:47 PM
teebee, I guess that both you and shamurshamur were a bit too optimistic.
Yeah, I haven't had enough gotcha's for my optimism to wear off yet!
I would try the manual imagex approach:
http://www.msfn.org/...showtopic=89955
http://www.msfn.org/...howtopic=109293
Those look very interesting, thanks. I think I understand the process using imagex discussed in the second post, though I am not sure how I could automate this through a bootloader on a flash drive.
I don't understand the bootloading process to start my own experimentation. I get that the boot partition calls a loader, but am not sure what is contained in the loader and how it is edited and whether there are further scripts after this or the loader manages the calls to something like imagex to write the image to the drive?
Is there any chance of a couple of pointers to set me off in the right direction?
Cheers,
Tony
#12
Posted 26 February 2010 - 12:54 PM
The idea is to *somehow* get from the stoopid .swm image a "good" .wim image, if needed modify the .wim, then throw away the .swm's and use the .wim.
In other words, you now have a set of files of which we do not have any idea of the contents, first step is transforming them in a way that the content is viewable/inspectable, if needed change the content and then hopefully have something working.
Now that you've learned the DIR /S >C:\dir.txt you need to find a way to dir the contents of the .wim.
Wonko
#13
Posted 14 March 2010 - 03:10 PM
I'm not sure why I would need to modify the WIM, as the image would be applied to the machine that the image was created for. The problem seems to be that the image loader is waiting for the CD drive to become available to present the image, which I assume is something to do with the ImageX config files that were set when the image was originally sent to a CD drive.
Of course, I may be misunderstanding the process and the information is being fetched from the WIM, which would be why you say I need to be able to inspect the WIM
Thanks for your input anyway, if I make any further progress if and when I come back to this I will let you know.
Tony
#14
Posted 10 May 2010 - 01:40 PM
So recover CD is useless for me.
#15
Posted 10 May 2010 - 01:47 PM
I usually do not use recover CD, I always reinstall my system completely, this makes me feel better. And to recover data, I use recovery software like Diskgetor, it helps me a lot.
So recover CD is useless for me.
Quite frankly, unless you are a spammer for Diskgetor (which is probable), I've rarely seen a more pointless and out of topic post in my experience.
http://en.wikipedia....9;t_give_a_damn
Wonko
#16
Posted 12 May 2010 - 04:11 PM
Two suggestions:
1. Use RMPrepUSB and format the USB pen for WinPE/Bootmgr and copy the entire contents of the DVD over (not the ISO file but ALL the files inside it).
2. If you REALLY want to use an ISO - make a folder called \ZZImg on your USB flash drive and copy all the files from the ISO folder \ZZImg to the USB folder \ZZImg. Then when WinPE boots from the ISO (as you have it now) it should be able to find the \ZZImg\ swm files on the USB drive. If this works, you could always remove the \zzImg files from the ISO file as you no longer need them. Though looking at the folder structure, other bits may not work either (e.g. may not find tools or the recovery files, etc.).
HTH
S
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users