jaclaz

Let's separate the chores: create a bootable USB from Ubuntu <-your problem make the already bootable USB boot Windows 7 <- this topic With reference to #1 above what "linux" loader are you currently using on the USB stick (Syslinux or GRUB)? With reference to #2 above are you wanting to have a Windows 7 running from a USB stick? Or are you wanting the USB stick to boot to a Windows 7 setup (in order to install Windows 7 on an internal hard disk)? jaclaz

Yes, you do not need the BOOT.INI and NTLDR if you use grub4dos. The only entry you need in menu.lst is: Just to make sure, have you in \CMDCONS\ a file WINNT.SIF with contents: http://www.911cd.net/forums//index.php?sho...20983&st=39 [data] CmdCons="1" ? I don't think that the fact that syslinux is used as intermediate leads to the 0x000000ED error, thus it is possible that it is caused by the missing SATA driver. You can try (temporarily) disabling the internal hard disk to test this (if possible in your BIOS). Unfortunately the F6 is reserved to floppy. You need to integrate the appropriate SATA driver in the RC or you can try mapping a floppy image with grub4dos. You need your SATA driver in a floppy image and then map the image, something like: in order to use the F6. If the \I386\ on your hard disk (or from another source) already has the driver integrated, you only need to copy from it the TXTSETUP.SIF or TXTSETUP.SI_ and the files for the actual driver(s) to the CMDCONS directory on the stick, but how can you access the \I386 on your hard disk? Which exact netbook model is it? jaclaz

you mean a 0x0000007b error? Is your drive (the internal one) a SATA disk? Can you describe how you finally setup the stick (which files which directories, which menu.lst entry? jaclaz

Well, you did ANOTHER thing from what that thread explained. Most probably you have now a Syslinux bootsector. Nothing personal, rest assured , but I completely fail to see WHY people introduces (unneded) variations/complications to a method and then cannot solve the problem they themselves created. The original thread was about: "normal" NTLDR bootsector NTLDR BOOT.INI in order to chainload grub4dos. Then grub4dos was used to DIRECTLY chainload SETUPLDR.BIN. You have (again WHY? ) Syslinux bootsector Syslinux syslinux.cfg with which you chainload grub4dos, then you have: grldr (or grub.exe) menu.lst to chainload NTLDR, then you have: NTLDR BOOT.INI to chainload a bootsector that will load SETUPLDR.BIN Can't you see that you do not need last step and you can chainload directly SETUPLDR.BIN from grub4dos? jaclaz

Mike Stevens method looks rather user intensive, Acronis does 99% of that for you (if you can afford it)Dead system, not a problem for Acronis. As long as his hard drive is still working (should be), Acronis can capture the image from the HDD and the Universal Restore add-on will be able to create a hardware-independent image. It will fully preserve all settings, favorites, applications as the OP requested. The only thing that will be different is during the first boot you may need to add drivers for things on the new equipment. Mostly I just need to run the chipset drivers when I move my machines around. Well, the link is for the theory of operation. And, with all due respect , you sound a bit like an Acronis Sponsor. There are many ways to skin a cat (though the cat won't be happy anyway ): http://www.911cd.net/forums//index.php?showforum=43 http://www.911cd.net/forums//index.php?showtopic=19397 http://www.boot-land.net/forums/index.php?showtopic=9830 jaclaz

Ok, now you solved (though in an overly complex way ) the booting problem you can go on. jaclaz

Good, now you may want to start using a "good" wiping utility : http://cmrr.ucsd.edu/people/Hughes/SecureErase.shtml It is also inside the UBCD "UltimateBootCD": http://www.ultimatebootcd.com/ jaclaz

Yes. Tricky. Yes. http://michaelstevenstech.com/moving_xp.html Doing it from a "dead" system would be even trickier. jaclaz

Well, NCQ has not much sense when imaging, but it does seems like having a relevance in day-to-day usage. jaclaz

The "usual" way is to take two registry snapshots of a running system, one before the install and one after the install, then review the differences and directly apply them: http://regshot.ru/20/ http://translate.google.com/translate?u=ht...en&ie=UTF-8 jaclaz

JFYI: http://www.msfn.org/board/install-usb-wins...4-page-590.html jaclaz

No, the "flashing underscore" means that you have a problem in the bootability of that stick, it is the typical symptom of a "wrong" bootsector. If you have more than one entry in boot.ini, you will see the two choices, if you have one single entry, you should get an error message about missing hal.dll. Nowadays the HP USB formatting utility is deprecated, as it leads in a number of cases to unbootable sticks or however "wrongly" partitioned/formatted ones. Pick one among these: http://www.boot-land.net/forums/index.php?showforum=71 http://www.boot-land.net/forums/index.php?showtopic=9460 I would suggest you to try RMPREPUSB first. jaclaz

I will try again : if you cannot describe this program, it is difficult I can help you speciofically as my crystal ball is in the shop , again, for maintenance and tune-up. General way for a CD (please FORGET for the moment that page http://www.nu2.nu/bootcd/#whatis ): Create an image of the floppy. <- there are several suitable programs, but without knowing what OS you are running it is difficult to point you to one particularly, probably best option is DCOPY/DCOPYNT that will cover DOS and various Windows: http://users.telenet.be/jbosman/applications.html make an El-Torito floppy emulation Cd, again there are several suitable programs, but without knowing what OS you are running it is difficult to point you to one particularly, easiest for Windows will be IMGBURN: http://www.imgburn.com/ http://forum.imgburn.com/index.php?showtopic=6392 http://forum.imgburn.com/index.php?showtopic=6392&st=5 Which can even extract directly the image of the floppy: http://forum.imgburn.com/index.php?showtopic=1779 jaclaz

I see. Here is a good start: http://www.slipstick.com/problems/scanpst.asp http://office.microsoft.com/en-us/outlook/...0771141033.aspx If the .pst files aren't corrupt it should be just a matter of following the instructions on MS site, I don't think that anyhting has changed between 2003 and 2007, but cannot really say. jaclaz

Well that may depend also on how/what you searched for. So we are talking of: - fixing an unbootable system (on an otherwise working hard disk, spinning, seen in BIOS, etc.) - fixing a corrupted partitioning/formatting (as above) - recovering data from one of the above - recovering data from a dead drive (no spinning, no detection in BIOS) You need to post some details, OS you are running, disk size, how it was formatted/partitioned, filesystems used, and an actual description of the "symptoms" you can see, how/when it happened, etc., etc.. This way it will be possible to help you in one direction or the other. The more data/descriptions you can give, the better. jaclaz

Which old floppy program? Are we talking of making a DOS booting from CD or USb and run tha program? You can do an El-Torito floppy emulation boot CD easily. Or does the "floppy" needs write access? If yes your best bet is using grub4dos or Syslinux/memdisk and either use an image (if the shatever needs writing BUT changes can be discarded) or a "normal" multiboot install (obviously only possible on a USB stick or HD, not on CD). Any reason why you should be able to read posts "better" than "instructions"? Post some details, and we'll see what we can do. jaclaz

It is very strange, at this point I would think of an iso creating problem. Can you try creating another bootable .iso with same PC? As an example try creating this one: http://www.boot-land.net/forums/?showtopic=2254 which is fairly small/fast to download files for/create, but still uses El-Torito No-emulation bootsector. Additionally, try booting those .iso in another VM (to check if for any reason the problem is in your VMware install). Qemu Manager: http://www.davereyn.co.uk/download.htm jaclaz

As I see it the only advantage would be that of having files bigger than 4 Gb: http://www.ntfs.com/ntfs_vs_fat.htm With all due respect for the people asking for NTFS support, the only practical use of NTFS on Windows 9x is IMHO for easily exchange of files in NT/2k/Xp/2003/Vista/2008/7 multi-boot systems or as a quick recovery system, as it seems to me that all the "advanced" features of NTFS (permissions, quotas, etc.) are pretty much useless in a 9x system which is not intneded/used as "multi-user" or server. They definitely won't, but one could write new ones as well. jaclaz

If you want to boot recovery console from a USB stick, check here: http://www.boot-land.net/forums/index.php?showtopic=5316 Cannot say however if you will be able to solve that problem using RC. jaclaz

NOT what you asked, but maybe Ninja Pendisk would do as well and needs no serial/registration, being Freeware: http://www.boot-land.net/forums/index.php?showtopic=4350 http://nunobrito.eu/ninja/ jaclaz

Just a small correction. You are confusing the means with the goal. Downloading legally through torrents is perfectly possible, a number of open source projects are downloadable through torrent, just as an example: http://linuxtracker.org/index.php?page=torrents It is the goal in your case that may be illegal (this largely depends on your country and local laws). If the Copyright holder had meant to let you (or anyone else) download the files legally, he would have most probably provided a way to do so. If the original site does not allow saving locally the movies, by using a screen capture approach you are, if not doing anything illegal (which is possible), anyway doing something against the Author or Copyright holder wish. Judging from this: http://www.southparkstudios.com/about/lega...nt=terms_of_use It doesn't seem to me like they want you through any means to have those files saved. jaclaz

0x0000007b means "unaccessible boot device". In the case of a SATA device, please read as: 0x0000007b I miss the appropriate SATA drivers for this device Read FAQ #3 here: http://www.msfn.org/board/faqs-t116766.html Add the BTS driverpack (or add the specific SATA driver) to the source. jaclaz

Sometimes GROUNDING is required, but usually the problem is in "garbled characters", not "NO response" Look at this photo: and read here: http://www.msfn.org/board/solution-seagate...-page-1661.html BUT you are using this board: http://www.sparkfun.com/commerce/product_i...products_id=449 Try reading attentively this part of the description: Chack against this: http://www.msfn.org/board/solution-seagate...-page-2023.html and a few posts later. Now, you may want to try powering it with 3 V, i.e. it is very possible that you are sending "ununderstandable signals through the line", compare with this: http://www.interfacebus.com/voltage_threshold.html jaclaz

There are three possible reasons: as said, HD (or mouse - but improbable) drawing too much power the above AND a problematic motherboard/USB bus "botched" something in the Registry Since #1 is easier to test/troubleshoot, I would exclude it before "delving deeper" in #3 (for this you might need to buy or borrow a PS/2 mouse). The general idea for #3 is to uninstall ANYTHING "USB related" from the system, clean the Registry, and try re-detecting the devices. For #2 you will need some hardware and test equipment, like a number of resistors, a USB cable and a multimeter, I would leave this as last attempt. However, just for the record, something along the line of this: http://www.girr.org/mac_stuff/usb_stuff.html jaclaz

Which, if it is exactly 2048 bytes in size "seems" right. Let's go on, still in the open in 7-zip .iso, can you locate: \I386\BOOTFIX.BIN \I386\SETUPLDR.BIN \I386\TXTSETUP.SIF or \I386\TXTSETUP.SI_ ? jalcaz