jaclaz

The "right" one: http://www.tronisoft.com/prod.php?id=4205 does 3.3V and 5V, you know, like: the "wrong" one: http://www.tronisoft.com/prod.php?id=4202 ONLY 5 V, you know, like: Sometimes I have the feeling that noone actually READs what I write, just like it happens with the "read-me-first". jaclaz

You want to solder a pin (or directly a wire) to: Tx (out) Rx (In) GND (-) VCC (+) DO NOT EVEN THINK of soldering on the hard disk side! Read here: WHERE did you get that adapter from? It should have come with instructions about the use (if any) of the jumper, as well as the actual Voltage needed to power it up, and the actual TTL level it is compatible with. I can read "TRONIX" on it. If you are going to use an USB port, why did you go through the extra long path of USB->RS232->TTL? This would have been simpler: http://www.tronisoft.com/prod.php?id=2468 and IT IS a 3.3 V TTL level cable. If the one you get is this one: http://www.tronisoft.com/prod.php?id=4205 it's ok. If it's this one: http://www.tronisoft.com/prod.php?id=4202 it won't work for the Seagate drive. Anyway the above page should contain links to the respective user manuals (or contact TRONIX to have them). jaclaz

Just to highlight how the idea that for using grub4dos is in any way "much more work necessary" is not actually true (for the very simple chore of hiding one or more paritions) here is a sample menu.lst that covers an hypothetical system with a single disk with three primary partitions on it, each with an operating system that is supposed to NOT see the other two partitions: title First partition hide (hd0,1) hide (hd0,2) unhide (hd0,0) root (hd0,0) chainloader +1 title Second partition hide (hd0,0) hide (hd0,2) unhide (hd0,1) root (hd0,1) chainloader +1 title Third partition hide (hd0,0) hide (hd0,1) unhide (hd0,2) root (hd0,2) chainloader +1 Last command: chainloader +1 can be replaced by chainloader /bootmgr in the case of a Vista or Windows 7 And, though I personally recommend to always establish root, it is not strictly *needed* (at least not for a NT based system) , so the two commands: can be replaced by either: or: Maybe it's because I do know a bit about grub4dos syntax, but it does seem to me like rather intuitive. jaclaz

A DE13 version is available on Dell's Site: http://search.dell.com/results.aspx?s=gen&c=us&l=en&cs=&k=DE13&cat=sup&x=0&y=0 jaclaz

There is a very good English word for it, word that we are not allowed to write on the forum but that is related to what comes out of a crack in the back of a male large mammal sporting huge horns. Tell your friend that the real problem is if the partition ends at cylinder 666 , but that's about 5 Gb..... jaclaz

Let's hope you didn't fry the board by connecting a RS-232 "straight" (a RS-232 can have output at more than 4 times the TTL 3.3v level). Pay GREAT attention! READ the read-me-first: It recommends to use THIS guide: http://www.mapleleafmountain.com/seagatebrick.html READ IT (again and again). You may find a bit like: jaclaz

We can remove the guesses, BTW all or most of them plainly wrong from the equation. Several months ago I contacted the nice guy that runs multibooters.co.uk and pointed him to grub4dos which is NOT GRUB (legacy) and is NOT GRUB 2. but he had no time to test himself the grub4dos . (and AGAIN what I pointed you to is grub4dos AND NOT GRUB) US$ 0 (as in zero, nil) seems to me a better deal, but of course if you like uneedingly spending 40 bucks for the Terabyte thingy (which BTW I can confirm it is a very good bootmanager ) it's your choice. JFYI: http://www.winimage.info/forum/viewtopic.php?f=1&t=3231 jaclaz

Sure , and you have a wise approach with the separation of data from OS. Problem might be the use of a "main" C: partition hosting your "main" OS. You cannot "hide" it unless you install grub4dos to the MBR. (actually I am lying, there may be ways, but they are rather advanced, but more than that prone to errors as they need "looping") A much better way would be that of having a slightly different setup. Ideally you should have (on first disk) a very small partition dedicated to just the bootmgr and the \boo\BCD (optionally plus the grub4dos files), i.e. recreate the situation of a "standard on pristine disk" Windows 7 install (the INfamous 100 Mb "hidden" partition). This would allow to leave the MBR code the "standard" Windows 7 one. And yes, you need some time to get the basics of grub4dos, and (if you don't already have them) some knowledge of the "standard" way Windows 7 boots. Find it here (just imagine to read Windows 7 instead of Vista ): http://www.multibooters.co.uk/ Particularly: http://www.multibooters.co.uk/system.html http://www.multibooters.co.uk/articles/windows_seven.html Take some time on the grub4dos guide and on the above pages, and when you feel like ready, post again, and I'll try to fill the gaps (if any). jaclaz

Yes. READ the first post on this thread. Get the tool. READ the docs, then just try it. There are suitable tools included to do the partitioning and formatting and writing of MBR, etc., if we are talking of a USB stick. The adviced tool is RMPREPUSB: http://reboot.pro/7739/ (already included) On steve6375's site there are tutorials to do the same (and more) manually, should you need some feature not available in the tool: http://sites.google.com/site/rmprepusb/ 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