jaclaz

Which command line options are you using with OSCDIMG? jaclaz

Well, why don't you do it? I mean WHAT is the question/problem, all you have to do is to make your USB stick bootable and copy the contents of the DVD to it, there are several tutorials available, one for all: http://technet.microsoft.com/en-us/magazin...a/dd535816.aspx More: http://tinyurl.com/yff29ku Or you can try using this app: http://www.msfn.org/board/install-usb-wins...ui-t120444.html If anything does not work, you ask for help. jaclaz

I would try seeing what happens in XP using a USB adapter and rdummy.sys. Another approach. Do a dd-like copy and mount it in IMDISK (as Removable) this should do for corrupted data: http://www.boot-land.net/forums/index.php?showtopic=7783 jaclaz

Check here : http://www.murraymoffatt.com/software-problem-0010.html From a logical point of view the needed app is more a "defragger" than anything else. http://www.smartcomputing.com/editorial/ar...6.asp&guid= defrag /sn Poorman's defragging described here: http://www.msfn.org/board/msoft-uses-diske...017-page-3.html http://kessels.biz/JkDefrag/ Now: http://www.mydefrag.com/ http://www.mydefrag.com/Manual-UsingMyDefrag.html I guess it's just a matter of adjusting the script to go on a certain volume or directory only. jaclaz

Are we talking of DOS or DOS in Windows? If the latter: http://www.computerhope.com/dirhlp.htm http://ss64.com/nt/dir.html hint: DIRCMD variable jaclaz

Are .iso hard links (duplicates-once)not working anymore? jaclaz

AFAICR a "Filter Driver" is a "Filter Driver" . cfadisk.sys is a "generic" Filter Driver. If you install it on a USB device "gendisk", see here: http://www.msfn.org/board/fixed-drive-usb-...68-page-12.html you will filter USB, if you apply it to other bus, it should filter it. But "normal" dummydisk.sys is ALREADY "targeted" to USBSTOR.SYS: http://www.codeproject.com/KB/system/sovie...ct_hooking.aspx and I presume that the same applies to reversed version rdummy.sys. I presume that some changes need to be made in the Source, of which I am not sure of the availability. Ilko_t at the time took contacts with Anton Bassov, and may be able to answer. Maybe it would be easier to modify the source of cfadisk.sys to get a "rcfadisk.sys" Definitely nothing in the .inf will do. jaclaz

Well, you can check the contents of the stick as is, I get that it is already bootable. you could have in either ROOT of the stick or in a /boot folder files like: menu.lst or syslinux.cfg or syslinux.conf First one "means" GRUB, either of the latter two "means" syslinux. The easiest in your situation would be adding if it's GRUB, grub4dos to the stick and the Windows 7 files, if it's Syslinux you may need to update to a later release. From either grub4dos or latish syslinux you can boot the Windows 7 BOOTMGR. jaclaz

Good news. Well, there is no actual need, if your Recovery console starts, as is, i.e. you can see and possibly also the progression bar and All you need is to add the SATA drivers. This thread may help you: http://www.boot-land.net/forums/index.php?showtopic=8758 If you re-start from scratch, I would rather use a PE of some kind as it is a "better" recovery environment. Should I choose one I would use the "frozen" LiveXP: http://www.boot-land.net/forums/index.php?showtopic=4111 Additional info: http://www.msfn.org/board/install-xp-usb-a...sb-t121446.html Are you able to recreate (from a recover CD/DVD or from a \I386\ on hard disk) a "source" Install CD? 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