jaclaz

Well, there are more "real" problems IMHO.... Meanwhile in England.... http://www.nottinghampost.com/Warning-student-pays-pound-450-photo-Xbox/story-20263203-detail/story.html jaclaz

IF the issue is related to "security zones", the thingy is an ADS (Alternate Data Stream) so all is needed is to rip it off through a tool *like* http://www.nirsoft.net/utils/alternate_data_streams.html http://www.heysoft.de/en/software/lads.php http://technet.microsoft.com/en-us/sysinternals/bb897440.aspx or save/copy the file on a non-NTFS filesystem and/or use Opera to download files. jaclaz

Bad drivers having less chances to drive again after an accident? jaclaz

Hmmm. I doubt that you can update the firmware of a drive in LBA0 state. (or even if it is *possible* is one of - no offence intended to the guy that surely did this in perfect good faith - the most absurd attempts I ever heard of ). And allow me to also doubt that "Seagate software" can analyze a LBA0 disk drive and "suggest" a firmware upgrade. jaclaz

Probably it won't help you much, but something similar (but not quite) happened to me some time ago. I had a good ol' (and that has always worked) PC with a Via Epia board (one of those mini-Itx ones). After a huge storm, with blackout and n times power going out and coming back, the thingy that ran Windows 2000 just fine started BSODing without a real reason (but it worked in DOS alright). At the time it was a spare-spare machine so I did not put much importance to the issue, and when I happened to find a similar board on e-bay for a few bucks, replaced the board. The machine with the new motherboard worked alright (I tested it with a CRT monitor), and set it back as spare-spare/for random tests only. When it came the time to put into service (still with the CRT monitor) it worked alright. At a given point I was gifted with one of those el-cheapo 16" (of a never heard before make/model) LCD TV's (that are mainly TV's but that do have a VGA input) and I decided to replace the CRT with it. Problem: I could not anymore access the BIOS setup (the LCD TV could not "hook" the video signal) but once Windows 2000 booted, it was fine. Tested again with the CRT, no issues whatsoever. I concluded that the stupid LCD TV was "below standard" for *some* reasons. It was a PITA, but since you don't really have to enter BIOS every day, I was fine with swapping the LCD with a CRT in th erare case I had to change something in BIOS setup. The machine worked fine and was connected through the network to a printer, and had no issues whatsoever. Once I needed to test a good ol' HP 1100 connecting it directly to the parallel port. Everything started to act "queer", in Device Manager a "phantom" Parallel port and a "phantom" Serial appeared, IRQ assigning got garbled, etc. Without the printer (which worked fine on another PC connected) everything was fine. Out of cannot say what kind of inspiration (or desperation) I replaced the PSU, and suddenly the printer started working alright, IRQ's were fine, no "phantom" devices, everything OK. The surprise came when I tried again to access the BIOS with the LCD TV connected, and it also worked fine! I had blamed wrongly the good Chinese guys who manufactured the el-cheapo TV! The only logical explanation in my case was that *some* defect in the PSU *somehow* introduced some sort of *queer* frequence, and that *somehow* once the 2K drivers set the video to a higher resolution rate disappeared. I thought that it was one of those extremely rare cases that only Murphy's Law could actually explain, but your issue seems to have some common points with it. Safe mode should be the same "standard" video output as the BIOS setup page. Does this latter work for you? jaclaz

Strictly speaking, even if you can, it doesn't really mean that you should. Can you provide the background (reasons, requisites, requirements, whatever) that made you design that partitioning scheme? Particularly the 2.629 Tb partition FAT32 is perplexing. The "recommended" max size of a FAT32 filesystem is 32 Gb (which while making sense, can be extended within limits, like the 50 Gb of your volumes L: and M:, using a third party formatting tool) but the issue here is that: http://technet.microsoft.com/en-us/library/cc938432.aspx Approximately 2,629,000,000,000/4,177,918=629260,794 would imply 1024 Kb clusters, which - even if they would be supported :unsure. - are HUGE! Compare with common cluster sizes in use: http://support.microsoft.com/kb/140365/en-us Maybe you could consider to make that large volume exFAT should NTFS (which would be a senceful choice), for whatever reasons, doesn't suit you. jaclaz

Yep , and specifically to MS, we have the know "This is by design" statement , which I personally read as "Ok, you just got us with our hands in the marmalade, and since we are too d@mn smart to admit anything, and we don't care enough for the user and we are not going to fix this which is evidently a (possibly serious) malfunctioning, we will state that it was done on purpose". JFYI: http://reboot.pro/topic/3541-how-many-microsoft-programmers-does-it-take-to-screw-in-a-light-bulb/ Specific example : http://support.microsoft.com/kb/252135/en-us jaclaz

Hmmm. The F712 is only a "diagnostic" kind of command that simply reads some data and outputs the status. What happens if you issue directly the F,,22? I guess your last chance, if even the above fails, is to try again with the PCB completely disconnected, see (Italian): http://www.gamesnet.it/f1093/seagate-barracuda-7200-11-sblocco-errore-bios-672580/ jaclaz

... he might point you to the immortal words of user NogginBoink on anandtech : http://forums.anandtech.com/showthread.php?t=1305319 Basically that error is caused by a driver. Whether the problem is caused by the driver itself or by a malfunctioning of the underlying device is impossible to say. Maybe with a full dump people like Cluberti or MagicAndre1981 may be able to pinpoint something. jaclaz

That is assuming that any decision made in the development of Windows 8 was backed by some logic. I would first like to ask the question : "Was any form of logic involved in what clearly results as very similar to the work of a bunch of headless chickens running in circle?" I mean, I can understand if - for any reason (that may or may not be judged logical or intelligent) you decide to completely remove a tool, service or utility, but simply hiding it? If you remove it, do remove it. If you want to keep it, keep it. Be a man, keep up to your decisions. If you instead decide to keep it but hide it to the "normal" user, OK, then document a way through Group Policy, Registry editing, Control Panel (or whatever) the "power" user can re-enable it. Good . jaclaz

That is not an issue at all if you start using a good searching tool that parses the $MFT, such as : http://reboot.pro/topic/18855-windows-file-search-utility-that-is-fast/ http://sourceforge.net/projects/swiftsearch/ jaclaz

In order to disambiguate, there are at least 3 (three) different methods to access a XP for which you have lost a password: the editing of the (offline) Registry removing (or changing) the password of an existing user (which in this case may not be indicated, or not as much as #2 below, as the issue may be exactly with the SAM or with some connected authentication mechanism) the msv1_0.dll patching (which in this case may provide better results as it simply "skips" authentication) the cmd.exe -> utilman.exe/osk.exe renaming trick in order to create a new user (which may also be suited to this case, but that is IMHO the most complex to do)jaclaz

Do you know which firmware the disk has? You could try issuing a F712 AND a F,,22 (or just the latter) as in these posts: http://www.msfn.org/board/topic/128807-the-solution-for-seagate-720011-hdds/?p=832794 http://www.msfn.org/board/topic/128807-the-solution-for-seagate-720011-hdds/?p=832876 BTW were you trying with the motor or with the head contacts insulated? jaclaz

I am starting to think that you don't really want help/suggestions . This makes NO SENSE whatsoever: the PassPass WILL allow logging in to a Windows system without providing a password. <- the last character is a full stop or period. Did you try SPECIFICALLY that, not "those" or "other similar", that program grub4dos batch? And you cannot login without providing a password? Just for the record you can use to the same effect on Windows XP also WindowsGate or any other tool that similarly patches msv1_0.dll, but you were suggested to try that specific tool, NOT other ones. jaclaz

@bhplt An exceptionally good and interesting breakdown of the reasons , BUT you will need to properly define "people" in this sentence : AND you omitted mentioning Wirth's Law : http://en.wikipedia.org/wiki/Wirth's_Law jaclaz

What happens if you simply map the .vhdx with imdisk (making use of discutils and of the imdisk toolkit)? http://reboot.pro/topic/18324-imdisk-toolkit/ The issue here is that it is not clear if .vhdx format is supported by discutils (it is but not all variations of it are, seemingly). NOT useful for the current issue, but generically related to Shadow Copies (maybe useful for *something* else. and/or, since source is available possibly of inspiration): http://vscsc.sourceforge.net/ This, instead, may be of use: http://dfstream.blogspot.ch/p/vsc-toolset.html jaclaz P.S.: This seems like a "full" alternative to ShadowExplorer, see if it fits: Previous Version File Recoverer http://sourceforge.net/projects/vistaprevrsrcvr/ http://sourceforge.net/projects/vistaprevrsrcvr/files/ This: may mean that if you use something like a loopback device, or anyway find a way to fake you are accessing the PC "not from itself" the missing TAB may be restored?

Yep. More exactly it was the "passive" form, "You had already been told so", implying "What did you think, that it was instead doable with a partition conversion and that it was easy?" I would additionally state how I believe that though XXCOPY, among all the tools, is the only one that may be able to do the copy, it won't probably work nonetheless . What the method Dietmar used consists of, essentially, was not to copy from the NTFS to the FAT32 the "tricky" files/folders, but rather to create the empty files/folders structure and then use the Vista "Repair" feature to "fill the gaps". I suspect that in this process Vista is somehow "tricked", finding an already installed operating system, into bypassing the (perverted) logic that was inserted in order to prevent the installing of it on a FAT32 and "unbundles" the complex "net" of hard and soft links, making a "plainer" install. In other words, I think that when a method for achieving something similar (32 bit instead of 64 bit) exists, attempting to use the same documented method has bigger probabilities to work - at least partially - than "re-inventing" the method. If and when a success is obtained with the the known method, then it is the time to experiment with new, strange ways to replicate. As a matter of fact, IF I was interested (and had the time and source OS) in the matter, I would first try re-doing EXACTLY what Dietmar documented (with the 32 bit OS), then try the same method if successful with 64 bit and only later attempt to find whether are there any better, easier, ways to replicate. jaclaz

No problem I was asking that to see if I could suggest you a replacement/alternative to ShadowExplorer, but if you are already in contact with the Author I presume that the corruption issues will be soon solved. However in the meantime you can try this thingy here: http://redrocktx.blogspot.it/p/shadowkit.html jaclaz

Yes, but first try again from start including the N1 command (and verify that contacts are clean/that you re-tightened the screws "enough"). jaclaz

Start by inventing, and building an engine running on water, then we'll talk about making a flying thing powered by it. jaclaz

Nothing of much relevance but since the very first reply to your original question, on post #2 user Ffin, and later yours truly on post #5 tried to convey you essentially two things: a partition conversion won't work it would be a difficult process - and if possible at all - ridden with problemsthis is strangely similar to the result of Tripredacus attempt to deploy directy to a FAT32 filesystem on post #13, which got a very similar comment from me on post #14. jaclaz

Well, you can try again from the beginning but skip the SMART erase command, and or simply try again, sometimes there are timing problems. jaclaz

You also forgot to insert "unexpectedly" or "surprisingly". jaclaz

You don't need to bold anything I am pretty sure that you verified that the command can be trusted alright. I was asking if the output is a .vhdx file and it seems that - while avoiding to answer my question - you indirectly confirmed that it is a .vhdx and actually a series of incremental/differential .vhdx's. jaclaz

The "WHICH" about the clicking was about the fact that you did not describe it in the "symptoms" earlier. A clicking (like 10 or eleven or twelve times) plainly means "the issue is outside the scope of the present thread AND it is unfortunately something that ONLY a professional using professional tools may be able to fix/recover from", that is IF the contacts to the motor/heads are good. (have you checked them, cleaned them and properly tightened the PCB screws?). Try again after having cleaned/checked the contacts between disk and PCB, if still it clicks the 8/10/11/12 times it is gone for good (as long as the possibilities of a DIY job are). jaclaz