jaclaz

Yes, but "traditionally" all good (and most evil ) have come from "Server" or however "Professional/Corporate" solutions, that in the years have been forced to "innocent" end customers. Just think of the use your mom or grandmother makes of features like: NTFS quotas file permissions transactional filesystem fast user switching .... on her netbook (that she uses to read some news, find some cook recipes and write/receive e-mails to/from her friends/relatives, besides keeping a spreadsheet with home expenses). With regards to your quote: I will translate it in plain English: We conducted a market research on a non-casual sample of users representing no more than 7% of the market. Instead of realizing that any sample - if not casual - is meaningless metrics, we tried to enlarge the sample size still keeping it non-casual, i.e . having a bigger volume of meaningless data instead of attempting to have an even minimal volume of meaningful data. Then we learned that the reason why the sample was so meager in size was connected to the fact that Enterprise Servers (i.e. something designed to keep possibly sensitive data either of private or commercial nature) were on purpose shielded by firewalls and similar devices in order to prevent information from escaping them . Those correspond, respectively, to lesson #1 and #2 in statistics, and to lesson #3 in computer science (Lesson #1 being "turn on the PC", Lesson #2 being "turn the monitor on, too"), the good MS guys must have had some more interesting things to do instead of attending class . jaclaz

Yep, at it's vey basic you need to: make sure that the "right directory" is chosen make sure that the epstopdf.exe program is found translate that one-liner in a batch (basically doubling the % in the FOR loop variable Basically: @ECHO OFF CD /D %~dp0 SET Program="C:\My program directory\eps to pdf\epstopdf.exe" for %%A in (*.eps) do %Program% %%A this assumes that you copy the small batch to the directory and that you have the program in a "fixed" directory, in the example "C:\My program directory\eps to pdf\epstopdf.exe". The %~dp0 will expand to the drive and path of the item 0 of the command line (the batch file itself). jaclaz

But you should see the good guys at MS like a (BTW very gifted in their self-esteem) doctor. In their own words: http://blogs.technet.com/b/windowsserver/archive/2012/05/17/improved-server-manageability-through-customer-feedback-how-the-customer-experience-improvement-program-makes-windows-server-2012-a-better-product-for-it-professionals.aspx If you do not forfait all your data to them, NOW, you are actually holding them back from helping other people, you little selfish bastard! I do prefer the short version: jaclaz

Well, I got you exactly where I wanted you to be , also grub4dos has this feature (and many others), see here (be warned it is advanced-advanced ): http://reboot.pro/7138/ (and take into account that since the above thread, quite a few new tricks can be done with latish releases of grub4dos ) See you when you are back . jaclaz

Sure , no doubt about this, BUT BEFORE that he should see if it actually gets the LED:000000CC state (or *whatever* error) BEFORE attempting to short the two pins, THEN he must know WHICH pins to short, the picture in the thread you referenced is about a board 100617465 REV A, and NOT about the one he has (which is a 100535537 REV A), so we are back to square #1 . I may produce which pins are to be shorted (if needed) on the 100535537 REV A Board, but if I were Eurgene I wouldn't do anything so d@mn dangerous without further data: Here: http://forum.hddguru.com/st31500541as-led-error-pins-short-t23079.html ??? It was a retaliation against Eurgene's original post. What was posted: ST31500341AS http://www.newegg.com/Product/Product.aspx?Item=N82E16822148337 What it is really: ST31500541AS http://www.newegg.com/Product/Product.aspx?Item=N82E16822148412 Comparison: ST31500341AS ST31500541AS jaclaz

Well, as i see it, the LP should be part of the 7200.12 family, but of course there are NO certainties, the usage of "child" for the LP actually reinforces my impression of it belonging to the 7200.12 family..... The good guys at Seagate have of course far too few neurons connected to actually provide a senceful naming scheme, so it could be *anything*, the model "ST31500541AS" corresponds also to a "normal" 7200.11 7200 rpm disk, so you may be perfectly right, and the LP couls be any of (PSEUDO-NUMBERS): 7200.11.1 7200.12.1 7200.13 8745.42sx Mark III jaclaz

Yep , same happens on RJ connectors, if you remove the "pin", since it is the pin itself that perforates the wire insulation. Though it is usually quite difficult to remove a single "pin" from a RJ connector. Point is/was that "better be safe than sorry" unless you know that *nothing* is connected to the pin #5 of the RJ12 receptacle, and besides there is no data to know if the "N/C" wire on the RJ45 receptacle would go on which among pins #4, #5 and #8 (you should remove all three of them, but usually, if on the RJ45 socket there are all 8 contacts, the ones that find the "hole" where the "pin" shoud be won't "like it" much and will tend to bend/stuck the connector ), cutting the cable shorter on the RJ45 side is the faster and safer way. There is also another (remote) possibility, that on the RJ12 side the pin #5 is connected to a ground of some kind, in which case having a 6 wire cable with one wire connected to pin 5 on the RJ12 side and cut 2 or 3 millimeters shorter on the RJ45 side would provide a form of "shielding". jaclaz

Would you agree on a 7200.12 LP? You know, like : http://www.hdd-parts.com/barracuda-720012.html http://www.hdd-parts.com/10113001.html @Eurgene Check this also: http://www.microsofttranslator.com/bv.aspx?ref=Internal&from=ru&to=en&a=http://hddhelp.com.ua/7200-12.htm jaclaz

This is the one you want MBR Utility, file mbr.zip: page__view__findpost__p__769544 OR, forget about it and get OS-BS rectius mbldr instead: http://reboot.pro/334/ page__st__105?do=embed' frameborder='0' data-embedContent> BTW this info is in the thread you were ALREADY pointed to: (there are reasons why a link is given ) jaclaz

The "traditional" unbricking works normally by EITHER: detach the PCB from the hard disk and re-connect it while powered, after some initial commands <- the original method, now superseded for the 7200.11 by one of the following ones insulate only the Motor contacts with a slip of paper and remove it when powered, after some initial commands <- on some disks this works, on other you need the following insulate only the Head contacts with a slip of paper and remove it when powered, after some initial commands <- on some disks this works, on other you need the previous The issue at hand is that some models or only some units will produce a LED:000000CC message that prevents sending further commands. To stop the message above and have enough time to issue the commands the shorting of two pins may work. It is only logical to try FIRST if you get to the LED:000000CC state BEFORE attempting to short the two pins. I would guess that that would count as the "BOTH" in my request . Your board is a 100535537 REV. A. From the little I know then your drive is NOT a 7200.11, but a 7200.12 . From the little info we know: http://computersciencelabs.blogspot.it/2011/02/seagate-720012-sim-error-firmware-fault.html http://www.facebook.com/note.php?note_id=152456431478526 there is no need to short pins on this. jaclaz

Or a "tighter" compressor. (PAQ8 family or WinRK or nanozip) @anthoyaudi NO, there is NO magic app that does miracles , there are good compressors, better compressors and worse compressors, but that's all. There is a trade off between "compression time", "decompression time" and "compression ratio" (and memory used/needed) most common compressors (and decompressors) tend to be more or less "symmetrical" and "efficient enough", if you have "infinite time" to compress (and also to decompress) you can have "tighter" compression. From time to time someone comes out with a "miracle" compressor, that as soon as it is tested, it is found to be a joke. If you have exceptional results, it meas that your source is a very compressible one like - as -X- pointed out - something with lots of 00's or anyway repeated data, a good example is empty disk images. Go here: http://www.maximumcompression.com/index.html and take some time studying the basics . jaclaz

Here, kid , let me take your hand so that you can UN safely cross the road .... Open the .iso with 7-zip. You will see: [BOOT] Drivedetect.exe README.txt Open from within 7-zip [bOOT] You will see: Bootable_1.44M.img Open from within 7-zip Bootable_1.44M.img You will see something LIKE: AUTOEXEC.BAT COMMAND.COM CONFIG.SYS ES2SN16C.ZIP HIMEM.EXE KERNEL.SYS RDISK.EXE TDSK.EXE unzip.exe Open from within 7-zip ES2SN16C.ZIP You will see something LIKE: CHOICE.EXE FDAPM.COM fdl464.exe flash.bat LIST.COM README.TXT seaenum.exe SN16c.lod sn16ccfg.txs jaclaz

As often happens, OT , but not much : http://www.digitalwpc.com/GetInvolved/MSPartnerPerspectives/KarlNoakes/Pages/You-Spoke-We-Listened-The-New-MPN-Brand.aspx#fbid=ECa4Zu_QDFo Every comment is superfluous. jaclaz

NO, I cannot , (or not so easily , compare with http://reboot.pro/2246/#entry14607 ) but Daniel B. Sedory (aka the Starman) seemingly can and he is so nice as to publish his results. jaclaz

Yep . See here: http://thestarman.narod.ru/asm/mbr/MSWIN41.htm and here: http://thestarman.narod.ru/asm/mbr/ntFAT32BR.htm jaclaz

N/C is the conventional name for Not Connected. In this case it means that the RJ45 (that has 8 contacts) is used on a 6 wire cable of which one (the one connected to the Pin #5 on the RJ12) is cut SHORTER than the others and is NOT connected to ANY receptacle on the RJ45 side )or you can use a 5 wire cable, if you find one). The schematics is evidently drawn by one of those nice guys that like to make things more complex than actually needed . Usually it is "etiquette" to NEVER change the pin order on either side of a cable schematics. Here are a couple examples of more "clear" schematics: http://buzzdavidson.com/?p=24 http://ltxfaq.custhelp.com/app/answers/detail/a_id/328/~/cable-to-connect-a-dec-vt-terminal's-mmj-to-a-lantronix-rj45-serial-port @Tripredacus, a wire marked N/C must NOT be connected to any pin/receptacle. jaclaz

You cannot. You can type one by one all commands with the /h or -h switch, but since not all commands use this convention, doing it in a batch would be EXTREMELY dangerous/and or pointless (and there is not an easy way AFAICR to find out if a .exe is a command line app or a GUI one and if it supports a /h switch). BTW, since the issue was the bootsector, and now the Recovery is working for you, leave the \boot\BCD alone, it is unprobable that something is broken in two places (and if it now works, it means that the BCD is OK, if it is used, if I get it right you have not the "HP specific" MBR - please read as "press F11", but the "generic" Vista /7 one - please read as "press F8" ). Some info on the "generic" recovery partition feature is given here: jaclaz

WHICH .iso? (link please). jaclaz

No. You got it wrong. The bootsector of a FAT32 is three sectors long. First one contains, besides CODE the BPB (filesystem DATA). Second contains some "redundant" filesystem DATA. Third one contains just CODE. On DOS/Win9x/ME the three sectors are #0, #1 and #2 (quite logical). On NT based systems they are #0, #1 and #12 <-at least up to 2K/XP/2003 . On ReactOS they are #0, #1 and #14. The backup is always #6 and #7 (for #0 and #1) and #8 (for #2) , sector #12 (or #14) is not backed up. If i give links is because you should read THOSE links: http://thestarman.narod.ru/asm/mbr/index.html http://thestarman.narod.ru/asm/mbr/ntFAT32BR.htm and more on THAT site, like: http://thestarman.narod.ru/asm/mbr/MSWIN41.htm Wikipedia is a very nice thing but in some cases it has incomplete, partially deceiving or plainly wrong info . In this case it is simply "vague" and doesn't take into account the differences between different MS OS's: The "main entry" is correct for DOS/Win9x/Me, whilst the "some cases" represent any NT system that supports FAT32, i.e. from 2K onwards. Now, be nice, get a Virtual disk of any kind, create a disk and format it with the FAT32 filesystem, and verify that: Sector #0 = Sector #6 Sector #1 = Sector #7 Sector #12 = Sector #8 if they are not, this should mean that the Vista or 7 changed again something. See edit below.... You can leave sectors #1 and #7 alone, the data in it (them) are actually almost never used. You are falling in the "Access is denied" issue with Windows 7, right? It is one of the "nice" protection features. See: http://reboot.pro/12413/ EDIT: I take it back . The sector #12 is NOT backed up on sector #8 (actually it is NOT backed up anywhere) even on 2K/XP. This is not a real problem, as it contains only CODE, so you can re-create it copying it from any other volume formatted under the same OS. jaclaz

There are several things that come into play. First thing is that you may NOT need to short anything (have you tried with the "plain" disconnecting?) Second is that we don't know if that specifcic model will "unbrick" with the known set of commands. Third we dont' know WHY exactly your disk is bricked. ST31500341AS means "very little". Post two CLEAR photos of the PCB of your disk (BOTH sides of it) and maybe someone may be able to tell you which pins you can try shorting (read channel). jaclaz

Good . That explains the different partition start address (and the flashing cursor), the initial BPB broken diagnosis was correct. . But I wonder about the differences in sectors 7 and 12. About the Madame Tussaud's idea, the wax statues tend to be mainly of dead people , so I would gladly pass for an adequate number of years from now . jaclaz

Sure , of course at your complete risk, try with the hints given here : jaclaz

Since you are using tinyhexer, you may find my little (as always half-@§§ed ) scripts for it, handy. Here: http://reboot.pro/8734/ I can see a problem right away, the parition table states that the 0C partition is starting at LBA 1914456064 and extends for 39063552 sectors. The PBR data states that there are 1900271616 sectors before and that the volume extends for 39063552 sectors. Please note how the "previous" NTFS partition actually starts @ #1900271616 in the MBR partition table. WHY this happened (and WHICH of the two values is the right one) is another thing , if I were you I would access the PhysicalDrive with tinyhexer and save sectors #1914456064 and #1900271616 and find out which one is the actual PBR of THAT volume. jaclaz

Well, then it is likely (but not sure) that the differences in sector 7 makes you slightly NOT boot the recovery partition, whilst the difference in sector 12 may (or may not) make you largely NOT boot it. Yes. http://homepage.ntlworld.com./jonathan.deboynepollard/FGA/questions-with-yes-or-no-answers.html If you post the requested data, I might even be able to tell you the one that is more likely to apply to your case, as well it is possible that the issue is in the \boot\BCD as Tripredacus is guessing, but without data it's impossible to say. jaclaz

A strange request , I know. I have to (actually would like to) write a small set of Macro's (NO, NOT Excel VBA) to manage some textual data. I have my reasons to use Excel Macro's (and no - again - NOT Visual Basic macros), basically the intended spreadsheet will not be used in Excel, but rather in SPREAD32. I have found the "base references", i.e. the Excel Macro (for Macintosh ) docs and the help file macrofun.hlp. http://www.microsoft.com/en-us/download/details.aspx?id=19243 http://support.microsoft.com/kb/128185/en-us As always happens these show the actual command syntax but provide no or very little examples. So I am looking for some examples (already written Macro's, related tutorials with examples, etc.). Of course googling today will give as result 9999 VBA related pages an 1 (maybe) actually Macro related. So, if anyone has some "old links", Wayback Machine bookmarks, etc. I would be very interested in them. jaclaz