jaclaz

That's good, if it was possible to do that, then it would become a non secure solution. Seriously, WHY (the heck) do you want to have a tool (BTW of very dubious reputation) that automatically runs? jaclaz

No, nothing that you can do yourself, and head failures are basically of two kinds: head failure (simply) head failure because of head(s) sticking to a platter (or platters) if #1 a professional with the appropriate tools/methods should be able to recover data (all of them) after having performed a head transplant. if #2 the amount of data that can be recovered by the same method above might be very little or none at all. jaclaz

@ehsantlk Are you insulating Head or Motor contacts? Try CLEANING/VERIFY contacts. If they are good, then unfortunately it is likely to be a broken/dead head. jaclaz

Sure, there is a whole family of Virus/Malware that arbitrarily change Office related keys in the Registry if the user is so reckless as to change the permission of a specific Office related key. Seriously, make a backup of the Registry, try setting that key to "Everyone", and see IF that is the cause (it is one of the possibilities, not necessarily the real reason). IF that is NOT the cause, THEN you restore the backup and have NOT to worry about the altered permissions. jaclaz

Is there a difficult part in: http://support.microsoft.com/kb/838687/en-us jaclaz

You don' t have the word "greed" in your dictionary? Just in case : http://www.thefreedictionary.com/greed It can be even worse than that. While most firms are obviously (even if somehow "greedy") "professional", I was reported in a few occasions of "ransom like" approaches. Basically you pay a "flat fee" for the exam of the drive, the firm would recover the contents, but provide you only with a DIR of the files found, asking for some money (the usual range between US$ 500 and 1,200) to recover the files. If you accept and pay the money you get your files back, if you don't and ask the drive back they give you back another drive (always photocopy the label of the disk AND mark in a corner the PCB and the aluminum case with a couple little scratch and take a picture of them before handing a disk to any external firm) or give you back your drive, BUT with the data wiped/mingled and re-bricked. You then try yourself (and fail) and or find another firm that (in perfect good faith) cannot recover anything so you go back to the "first" one. This time however the cost for the recovery (which they can still do ) is doubled or tripled.... Well, JFYI, that is another nice urban myth. The number of actual clean rooms in data recovery shops in a mid-sized industrial country can usually be counted on fingers without taking your shoes off. What is written on the site/advertisement is "clean room", what actually exists/is used is generally a laminar flow workbench. JFYI: jaclaz

Yeah, sure, I also had a couple experience with cars, one bad, one good. Many years ago I had an Alfetta (gasoline, automatic gearbox) which engine decided to blow up at a mere 250.000 Kms. More recently I passed the 350,000 km landmark on my Toyota Hilux (diesel, manual gearbox) without a hitch. I am pretty sure that a lot of people have experienced something similar with wives/husbands/partners (one bad, one good). Just in case: http://en.wikipedia.org/wiki/Anecdotal_evidence Seriously, Windows 98 Scandisk (obviously on a FAT filesystem, and specifically on a overheating disk drive) and CHKDSK (most probably on a NTFS filesystem on a normally working disk drive) are two such different thiings that you can hardly compare them (the only similarity is that both have d,s and k in their name ). jaclaz

Have you checked permissions for the Registry? From the KB you found: http://support.microsoft.com/kb/838687/en-us Those are "generic" kind of possible issues. The "full path" to the key (UNLIKE what stated in you post) should be: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\11.0\Common There may be another key: HKEY_CURRENT_USER\Software\Microsoft\Office\11.0\Common which should be the one you found /but that is not seemingly the one creating the 1406 error) jaclaz

I personally find the whole idea of BYOD (Bring Your Own Device) as being second in stupidity only to the cloud (when it comes to security, privacy, integrity of data). But I would like to understand what other members think of the idea/approach, if they have any experience (poositive/negative/neutral) about it, etc. Some "introductory" reference: http://www.cio.com/article/703511/BYOD_If_You_Think_You_re_Saving_Money_Think_Again?page=1 http://www.cio.com/article/721478/2013_Prediction_BYOD_on_the_Decline_ http://www.cultofmac.com/156511/byod-failure-five-big-reasons-why-employees-dont-want-to-use-their-iphones-ipads-at-work/ http://www.infosecurity-magazine.com/view/31062/companies-failing-to-get-a-grip-on-byod/ http://www.theregister.co.uk/2012/11/09/sec_security_snafu/ http://www.darkreading.com/advanced-threats/researcher-to-demo-spy-phone-at-black-ha/240157439 And some personal ideas on the matter: http://www.forensicfocus.com/Forums/viewtopic/t=10567/ jaclaz

Who knows? Try and see. Each motherboard manufacturer (exactly like it happened with BIOS) may have provided (or completely failed to provide) *everything* (and the contrary of it) and may have provided it (or completely failed to provide it) in either UEFI only mode, BIOS only mode or mixed mode and additionally Windows 7 or Windows 8 (and Windows XP) may "react" to these in different ways. It is "vague", I would say "extremely vague", that is essentially the point about UEFI being a non-standard and knowing from experience how BOTH the motherboard manufacturers (or BIOS programmers or both) and Microsoft have failed to deliver over the years full, integral, fail-proof adherence to actual standards (but took them more or less as "general advice" and largely ignored them or managed to develop deviating, "custom" standards or "proprietary dialects" of them) you can understand what you can expect from this mess. As an OT example, see what the XP Disk management can do when simply changing the active status of a partition on a disk partitioned by a later MS OS (and still within the MBR "standard"): http://reboot.pro/topic/9897-vistawin7-versus-xp-partitioning-issue/ to me this establishes that you normally cannot believe anyone (and particularly the good MS guys and their programs and docs) on anything. In other words, your mileage may (and will) vary. jaclaz

http://gigaom.com/2013/06/28/if-prism-doesnt-freak-you-out-about-cloud-computing-maybe-it-should-says-privacy-expert/ And, just for the record : http://www.montereyherald.com/local/ci_23554739/restricted-web-access-guardian-is-army-wide-officials jaclaz

In my simplicity, once booted to the recovery console, I would run a CHKDSK from there first thing. Please consider how the CHKDSK in recovery console has a slightly different syntax from the "real thing". http://best-windows.vlaurie.com/chkdsk.html http://commandwindows.com/recovery.htm The worst that can happen is that the thingy will take some time to execute. jaclaz

Already provided link: http://www.techsupportforum.com/forums/f217/solved-win7-64bits-uefi-mbr-need-infos-592835.html And link within: http://support.microsoft.com/kb/2481490 And initial suggestion: http://www.rodsbooks.com/gdisk/hybrid.html Whatever you do, do the right thing http://www.imdb.com/title/tt0097216/quotes?item=qt0362962 jaclaz

Yes and no. The EFI thingy was more or less "invented" by Intel. The real reason (originally and IMHO) being that of stopping giving away money to Award, Ami and similar BIOS making companies, officially to provide servers with a "more adequate to more powerful hardware base hardware interpreter". It failed miserably. Then Apple (more or less for the same reasons) started making Macintosh EFI based. TIll now, all that made sense (either proprietary hardware on Mac's or hardware - servers - limited to a niche of machines managed by IT guys). Then the good linux guys (possibly in perfect good faith) started supporting EFI/UEFI (thus contributing to it's success). And only "finally" the good MS guys had the brilliant idea (with the usual arrogance) to leverage on the capabilities of UEFI to make it "compulsory" for Windows 8 (coherently with the senseless push towards 64 bit OS) the "secure boot". Of course the "Secure boot" Microsoft made "compulsory" is not "secure" and in some cases it is not even "boot". http://en.wikipedia.org/wiki/Unified_Extensible_Firmware_Interface#Criticism The real issue is that the thingy is senselessly complex, and since everyone can read the specifications "the way he/she likes" all the issues over the years with BIOS ( badly programmed BIOS code, senseless features added/removed, possibility to brick for good a motherboard, etc., etc. ) have not been particularly mitigated, let alone removed. BTW; if we are talking of "freedom" (about which the proprietary BIOS was largely criticized over the years), the first step you have to do to get the specifications is to give away your personal data in order to get to read the specs: http://www.uefi.org/specs/agreement And guess who are the members of the UEFI org? http://www.uefi.org/about/ Of course the request for providing data can be easily bypassed by simply using google and get directly to the download page. Just for the record, the simple current 2.3.1 specifications consists in a .pdf made of only 2180 pages . jaclaz

You are seemingly not familiar with "directional hmmmming" , it was aimed @submix8c . jaclaz

Hmmm. jaclaz

OT , but as always not much : http://blogs.msdn.com/b/larryosterman/archive/2010/01/04/what-s-up-with-the-beep-driver-in-windows-7.aspx And (in case of need), thanks to the "enhancements" above detailed: http://www.waldbauer.com/tmp/reference.php jaclaz

--JorgeA Unless you actually access/mount (through a Virtual Disk Driver) the Virtual Disk it is simply a file (or if you prefer a container). Does (say) a .zip file (a common form of compressed container) infect you machine only because it exists on your hard disk drive? On the other hand, once the Virtual Disk Image has been mounted to a drive or mountpoint, it behaves EXACTLY as it was a "real" Disk drive, let's say (but there is not "autorun" provision for these) like if you insert in your machine a SD card or a USB stick. Again - provided that you have not any of the stupid autorun settings - are the contents of the device "dangerous" because they exist? But since this Virtual Disk Drive behaves like it was a "real" one, you can scan it with the same anti-virus/anti-malware solution you use for the real disks. Of course if you are affected by dementia and start executing (double clicking) "random" .exe's, .bat's, .cmd's etc from the mounted image, and do this with the OS in the VM having no anti-virus protection and you do it before scanning the device contents fron the "Host" OS, then you have the SAME lack of security you would have if you do the same on your Real Machine. Conversely, if you never access/mount the Virtual Disk Drive, it is like an infected SD card or USB stick that you NEVER connect to your machine (pretty much safe ). http://www.theanswerbank.co.uk/Media-and-TV/Question69979.html jaclaz

Yes, you are evidently NOT familiar with the concept. A Virtual Machine resides on a Real Machine (Host). A Virtual Machine (normally) uses a Virtual Disk Drive. A Virtual Disk Drive (normally) resides on the Real Machine (usually in the form of a disk image, i.e. of a file, saved on the Real Machine, that represents a disk contents). The Virtual Disk Drive Image (the file) can be accessed - through a Virtual Disk Driver - exactly if it was a Real Disk Drive from the Real Machine. jaclaz

As a matter of fact that one is one among the many (pointless/lacking info) ones on it. This one actually has some "contents" : The real issue being that in the last 5 (five) years nothing much has changed . jaclaz

I additionally doubt that UEFI booting is faster in any way (3 seconds - if true/achievable is meaningless time save, unless your main occupation is booting/rebooting the system). A number of motherboards have however both BIOS and UEFI, or are however capable of using MBR disks alright. http://www.techsupportforum.com/forums/f217/solved-win7-64bits-uefi-mbr-need-infos-592835.html BIOS based tools, like - as an example - grub4dos, won't work on EFI/UEFI mode, obviously. Personal opinions: All in all GPT disks are a senseless new standard that has no real world advantage if not on extremely large storage devices. EFI/UEFI is instead a senseless new non-standard (meaning that the standard is so mindboggingly complex that noone can possibly make one actually fully respecting the set standard). jaclaz

What happens when you click on the "Disable" button in the center of the window you posted a screenshot? It vanishes in thin air The text in it changes by sheer magic into "Enable" Something else (please specify) What happens when right clicking on the connection entry? http://www.cavsi.com/questionsanswers/how-to-enable-or-disable-a-network-adapter/ jaclaz

I guess your ONLY chance is to make a Hybrid partitioning: http://www.rodsbooks.com/gdisk/ http://www.rodsbooks.com/gdisk/hybrid.html jaclaz

You don't normally make a "backup" of a CD, you make an image of it. Recent thread (only seemingly OT -contains links to commonly used programs to create .iso images): If you need to modify it, then a "backup" AND a suitable .iso making tool (mkisofs or OSCDIMG) AND a correct command line for any of them is the way to go. Possibly you could make use of : jaclaz

Naah, you missed the orignal reference: http://www.911cd.net/forums//index.php?showtopic=21827&st=23 http://www.911cd.net/forums//index.php?s=&showtopic=21827&view=findpost&p=148472 AND the image attached. jaclaz ones.bmp