jaclaz

There are some paths and filenames that are hardcoded. You simply cannot do "what you want". See here: http://reboot.pro/8043/ but there are however ways, though not *exactly* what you asked for one of these may fit (or however give you a hint in the "right" direction): http://sites.google.com/site/rmprepusb/tutorials/how-to-create-a-usb-drive-that-will-install-vista-win7-and-server-2008 http://sites.google.com/site/rmprepusb/tutorials/multi_boot-wim http://sites.google.com/site/rmprepusb/tutorials/winiso http://sites.google.com/site/rmprepusb/tutorials/multiisoimdiskautounattend (first one is the "evolution" of the method involving different BCD's) The easiest, as said on the other thread, is using .iso mapping, nowadays memdisk can also map .iso's, see here: http://reboot.pro/8258/ Another possible approach : http://reboot.pro/12292/ jaclaz

Hmmm. http://www.zdnet.com/blog/microsoft/microsofts-ballmer-says-next-gen-windows-systems-due-in-2012/9515 jaclaz

grub4dos. http://reboot.pro/forum/66/ http://reboot.pro/14/page__st__1 http://reboot.pro/5187/ For the simple reason that (unless you want to) needs not to be installed to the MBR or PBR, but it can be chainloaded by either the NTLDR/BOOT.INI or BOOTMGR/\boot\BCD. Without a DETAILED report on how you plan to setup your system (partitions, their type, size and filesystems used) it is difficult to give you a senceful advice about how it would be more handy to set it up. jaclaz

No, there is nothing "flawed" in the "lift". It simply: may apply to head contacts OR to motor contacts it does NOT apply (without the "short circuit" trick) to ES2 drives (according to the reports we had) I have no actual "answers", for you unfortunately , only my common sense tellng me that: since everyone in an actual BSY or LBA0 on a ES2 drive HAD to short circuit the two pins to get access to terminal since you did not need the above, then the situation of your dirves is NOT the one for which we do know a remedy It is very possible that since your drives are 250 Gb we simply miss the "right" procedure or, if you prefer, there is for that model an additional "trick" we know nothing about. I know that it may sound "queer" and/or "harsh" but all we know (which is very little) is a procedure to revive a given model (actually two of them) of drives suffering from two common problems due to a known firmware fault. As hinted in the Read-me-first, point #1: the known-to-be-working procedure is NOT a "solve-any-problem-you-might-have-with-an-HD", but, since it represents a sort of "reset" it may help also in solving problems due to "other" causes. The "buzz-buzz" sound you hear may be caused by something else, like a stuck motor (quite common on modern drives), but it may also mean that somehow drive cannot read anymore "calibration data" or whatever. Are you sure you didn't - by mistake - exchange the PCB's? Can you "feel" the hard disk spinning? See here: Did you cycle power? Can you now connect through terminal? Can you try with the PCB fully connected to issue a "spin up" command? Please do understand that you are - with all due respect - a blindman guided by (at the most) a short sighted one-eyed-man Though: I may be blessed what I suggest is not "real" knowledge but rather "some past experience" and may well lead you astray. jaclaz

Discussioni on ES2 drives goes on here: Please DO NOT double post. jaclaz

Please DO NOT EVER double post. I just replied to your post on the other (WRONG) thread. I am re-posting the contents of that here: What you report is "queer". "Spin down" is a "normal" and NOT even potentially "destructive" one. If you: power off the drive completely remove the PCB from it. verify contacs between PCB and drive (which means visually inspecting BOTH contacts on the PCB and the "springy" ones on the HD - checking that no "springy thingy" is bent or "flattened", and clean them thoroughfully with an eraser -the one on a pencil will do - and clean them thoroughfully with isopropyl alcohol or similar solvent, acetone is OK, as long as you do use it carefully, parsimoniously and quickly) re-assemple fully hard disk and PCB try powering it again (without any connection BUT the actual power supply) What happens? Since your disks are ES2 you had to do the "short circuit" trick. Is it possible that you short circuited "something else" or "also something else"? jaclaz PLEASE, let's continue here. jaclaz

Sorry, removed post, see below. jaclaz

Yep , this is corresponding to the settings of --iso-level in mkisofs (and as well those of -relaxed-filenames -allow-lowercase -allow-multidot -no-iso-translate and -U http://en.wikipedia.org/wiki/ISO_9660 http://linux.about.com/library/cmd/blcmdl8_mkisofs.htm See also (just for the record): page__st__39 MSCDEX wants "upper case" filenames only, SHSUCDX allows for lowercase too. jaclaz

See if this applies to you: http://forums.techarena.in/portable-devices/1405707.htm jaclaz

I meant, WHEN you post on the Fedora Forum, also post the actual brand/model, sorry if I caused a misunderstanding, that problem is NOT related to "Hardware hangout" and I doubt you will find here on MSFN many people capable of solving the Linux related problem. jaclaz

Yes, it comes from Fedora. It's a known problem on older versions and it revolves around ACPI on notebooks. "Full error" should be: example: http://forum.soft32.com/linux/Bug-571251-base-hp-pavillon-start-30-success-ftopict507686.html This is a problem you need to address to a Linux (possibly Fedora ) Forum http://www.fedoraforum.org/ post also exact brand/model of actual Notebook. jaclaz

See if this fits (to find current links): http://www.coderforlife.com/projects/utilities/#FindLinks Then you can use either mklink: http://technet.microsoft.com/en-us/library/cc753194(WS.10).aspx or ln or it's GUI Link Shell: http://schinagl.priv.at/ http://schinagl.priv.at/nt/ln/ln.html http://schinagl.priv.at/nt/hardlinkshellext/hardlinkshellext.html ln also can find links. jaclaz

Use another mounting tool (better if on a COPY of that image) that allows R/W operations. Since you are going on a file-based recovery, you can use IMDISK allright: http://www.ltr-data.se/opencode.html/ An alternative method should be that of using TESTDISK on the image to just copy the files: http://www.cgsecurity.org/wiki/TestDisk jaclaz

Sure , it's a deal. That's why I said "normal" use, like temporary internet files, etc. Since you have not enough RAM, then you create a pagefile, i.e. a (very slow) extension of physical memory residing on a disk. Then you make a Ramdisk (that uses RAM) to put the pagefile on it instead. Of course if you have more than 3 ( or 3.2 or whatever is the exact limit) Gb of RAM, AND use a 32 bit OS, then the Gavotte's Ramdisk is a way to use the extra (otherwise unusable) when (and only when) you "saturate" the "lower" 3 Gb (or whatever) of RAM. In my book this is not "normal", but rather an "exceptional" case, where you BOTH have a need for lots of RAM AND you don't have a 64 bit OS. AND there are reports of stability with /PAE: http://reboot.pro/4064/ And yes, in this case IMDISK is NOT the "right" tool: http://reboot.pro/7973/ Beware of "doctors" agreeing : http://reboot.pro/13601/page__st__89 jaclaz

120 V 5 A is quite a bit of power consumption, 600 VA= around 600 W. If the circuits are efficient, it is likely to produce a flux of up to 2500 or 3000 gauss. The 3+3 seconds IMHO can be "replaced" by 5 to 10 seconds on 1 side only. Compare with data from the V94 or V92 models you find here (professional tools): http://www.veritysystems.com/degaussers/tape-degaussing.asp And with those of the hand held unit here: http://www.degaussers.net/degausser.asp?id=1242 From "common sense" I would try with two or three floppy max, if the field works similar to the latter above, you have 2400 gauss on surface and 700 at 1/2" inch distance. jaclaz

@dencorso NO. The "best" (of course IMHO) for normal use is IMDISK, for TWO reasons: it is faster than Firadisk and WinVblock (and Gavotte's) it works at a "higher level" than other ones mentioned (i.e. doesn't create a Physicaldrive, doesn't interact with Disk Management) There is in practice no or very little difference in the capabilities of Firadisk and in those of WinVblock, the two projects are developed "in parallel" and features that become available in one are usually quickly added to the other also. In this exact moment (but tomorrow I could be able to say the opposite ) WinVblock is one little step ahead because of the experimental "delay load" mechanism that helps in booting on some ICHx moitherboards. jaclaz

It's good, but there are better choices if you only need a ramdisk for storing "temporary INternet or the like. See here: http://reboot.pro/11252/ jaclaz

You are missing a few points (BIG ones). We are NOT talking about "Windows XP", but rather of "Windows XP setup/install". NO "Windows XP setup/install" version is "USB bootable". ALL "Windows XP setup/install" versions can be made "USB bootable". Whether a given app to do the latter: exists works with a given version is another question. You used an app (WintoFlash) that we: don't use do not know do not recommend (which BTW and just for the record, produced a botched result, most probably because you used a 5th partition) So your question can be either: Which versions of "Windows XP setup/install" does application x make bootable? or: Does does application x make bootable version y of "Windows XP setup/install"? And if x is not any of the ones you can find here, you'd better ask that question on the forum dedicated to application x After all the trouble in helping you out of the situation you ended up in, we get to know that you used a WAREZ release! Don't event THINK to ask here about version y if it is a WAREZ you downloaded from somewhere. We DO NOT support WAREZ. Topic closed before you manage to get banned. jaclaz

Well, that's quite a strange coincidence. One of the most "illustrative" guys on AeroStudio is Shirin Zaban which actually is Iranian. Have you checked his mini-guide in .chm format here ?: http://reboot.pro/8008/ A "step by step" guide, and expecially one for "all XP versions (Home, Pro, MCE), my Vista/7 AIO (all x86 & x64 discs in one), seatools, memtest, bit defender, ophcrack boot cds, etc." does not exist AFAIK. Guides like the flyakite ones are "easier" to do since they are more "targeted" (only XP's) What you want to do is very ambitious, and you need to grasp the concepts and get familiar with the apps, and then develop yourself the missing "solutions" or "assemble" yourself the bits and pieces. For grub4dos it's easier because there is a good guide (actually written in English , though by an Australian ): http://reboot.pro/forum/66/ http://reboot.pro/5187/ http://diddy.boot-land.net/grub4dos/Grub4dos.htm and by searching on the reboot.pro forum you actually have a "database" of a great number of things that can be booted with grub4dos (and how to boot them). And yes, I'm happy to know it was unintentional , but your innuendo did sound a lot like whining jaclaz

Very nice and descriptive! I often happen to provoke that, and didn't know how to call it! jaclaz

You are welcome , maybe if you hadn't mentioned it, you wouldn't have got the snotty reply at all. You see, a lot of people are not native English speaking or know it very well and they may have difficulties in speaking/writing in it, but since they are nice guys, they do try to share what they know in the way they can. IMNSHO, they should be admired and thanked for their efforts... notwithstanding the fact that their English is "not decent" or "broken", and, to be quite frank, from time to time even people that is supposed to know the idiom natively write in a "not-really-Oxford" English: jaclaz

Sorry, my crystal ball is out of tune and in the workshop for tuning , didn't see through it that you were running a 64 bit OS. Is also the XP (booted temporarily through the initial use of the USB stick) also x64? (hint, hint ) jaclaz

I don't get it , if you want a "multi-boot manager" you can use either grub4dos or syslinux. If you want a "multi-boot manager" with nice graphical effects you can use grub4dos with gfxboot/gfxmenu. See: I don't see how "your boss" would have an easier experience with the second than with the first, it's about choosing what to boot, not "rocket science" or "brain surgery": you choose/highlight something and press [ENTER] In any case, anyone actually capable of using: won't have a problem with them. Just for the record, the kind of "broken English" you can find here: http://reboot.pro/forum/72/ has been anyway "good enough" AFAIK to let a few thousands (non-Chinese and non-Turkish) people be able to use AeroStudio.... If you want something "better" you can also try @DED-LEGO@ http://reboot.pro/13437/ But still you will find some not-easy parts and "broken English".... jaclaz

Good. Open Disk Management, and check that Drive C:\ is the ACTIVE partition on first disk (it will probably be so from what you have posted till now). What happens NOW when you boot is the following (compare with the given links and posted images): BIOS-> First Disk-> MBR (of first disk) ->chainload PBR (or bootsector) of First Active Partition on FIrst disk PBR (of Active partition on first disk) -> calls BOOTMGR (inside Active partition, i.e. the one that gets letter C:\ in your case) BOOTMGR-> parses \boot\BCD (still inside Active partition filesystem) and finds ONLY one entry to boot Windows 7, so it calls WINLOAD.EXE WINLOAD.EXE -> loads Windows 7 What should happen: BIOS-> First Disk-> MBR (of first disk) ->chainload PBR (or bootsector) of First Active Partition on FIrst disk PBR (of Active partition on first disk) -> calls BOOTMGR (inside Active partition, i.e. the one that gets letter C:\ in your case) BOOTMGR-> parses \boot\BCD (still inside Active partition filesystem) and finds TWO entries, one to boot Windows 7, and one to boot XP, IF user chooses to load Windows 7, it calls WINLOAD.EXE AND: WINLOAD.EXE -> loads Windows 7 BUT: BOOTMGR-> parses \boot\BCD (still inside Active partition filesystem) and finds TWO entries, one to boot Windows 7, and one to boot XP, IF user chooses to load Windows XP, it calls NTLDR NTLDR (still inside Active partition filesystem) -> NTLDR parses BOOT.INI (still inside Active partition filesystem) and depending on the choices in there, you continue booting the XP on one or the other disk or partition NTDETECT.COM (still inside Active partition filesystem) is called to detect hardware and then the kernel of XP is loaded You have ALREADY all the needed files in the Active partition on first disk (drive C:\): BOOTMGR \boot\BCD\ (even if it's not listed in the screenshot you posted, you do have it, otherwise 7 wouldn't boot) NTLDR BOOT.INI NTDETECT.COM so, you now need to: add an option to the \boot\BCD in order to load NTLDR. (you must think as \boot\BCD as the corresponding of BOOT.INI, only in a "strange" format - actually it is a Registry hive - instead of a plain TXT file) verify that the options in BOOT.INI are correct Use any of the mentioned tool to add the entry in \boot\BCD, simplest would be to use BCDtool: http://reboot.pro/10003/ http://filebeam.com/fe6603a102cbd28393bda4bb553c9c56 Start the app, then: Boot Config->Open -> C:\boot\BCD Edit-> Create Windows Legacy OS loader (NT4 winXP win2003) It should get: identifier => {ntldr} device=> partition=C: path=> \ntldr description=> Windows XP [*]Close the app Replace contents the BOOT.INI file in C: with these: Most probably the #5 or #5 one is the right one, i.e.: multi(0)disk(0)rdisk(0)partition(1)=First disk first partition= C:\ multi(0)disk(0)rdisk(0)partition(2)=First disk second partition= D:\ multi(0)disk(0)rdisk(0)partition(3)=First disk third partition= E:\ Then : multi(0)disk(0)rdisk(0)partition(4)=First disk fourth partition= F:\ multi(0)disk(0)rdisk(0)partition(5)=First disk fifth partition= G:\ OR multi(0)disk(0)rdisk(0)partition(4)=First disk fourth partition= G:\ multi(0)disk(0)rdisk(0)partition(5)=First disk fifth partition= F:\ No way to know unless you post a screenshot of Disk Management. Please, when replying avoid quoting WHOLE posts, expecially if they are longish/contain images. jaclaz

Forget the windows "Search". Open explorer (make sure you have settings so that it shows system and hidden files and file extensions). Look in the ROOT of your drive when booted in Windows 7. (the actual drive corresponding to active partition, normally C:\, which will have a file named BOOTMGR in it's root). Can you see files: NTLDR NTDETECT.COM BOOT.INI If not, as first step copy them from the root of the USB stick to the root of the internal disk. Then you will need to get a GUI BCD editor, (there are several ones, just examples): http://reboot.pro/10003/ http://www.zezula.net/en/fstools/bellavista.html and learn to use them to add to the BCD store an entry for the NTLDR. You can also use the Win 7 built-in command line BCDedit, but it's a tadbit more complex. Take some time reading here (simply read "Windows 7" instead of "Vista "): http://www.multibooters.co.uk/ particularly this page: http://www.multibooters.co.uk/bootmgr.html and this one: http://www.multibooters.co.uk/multiboot.html you are in situation: and you need to get to situation: It is also possible (it depends on the way your Windows 7 was originally installed) that you have a partition with no drive letter attached to it, that you can only see in disk management, and that will be around 100 Mb in size. Report if this is the case. jaclaz