jaclaz

OT but not much this may be of use/related : http://reboot.pro/topic/16755-offline-event-viewer/ jaclaz

See this Forum: http://www.msfn.org/board/forum/157-install-windows-from-usb/ (what you want to do is not necessarily Windows 8 related, but it is about "installing Windows from USB" ). jaclaz

That's entirely up to you. If you value the DATA on it between US$500 and US$1,000, go for the pro's (possibly even MUCH more if the issue is damaged heads ). If you don't, or simply do not have that amount of money available, you have no choices but try yourself. Since we have no validated experiences with that model (and we completely fail to know the "reason why" or the actual cause of the LBA0 situation you are in) I would suggest you anyway to invest a few more bucks - besides the ones needed to buy the TTL adapter - to buy an used (but fully working) similar 5400.6 disk drive and try the commands/routines on this second "expendable" drive. The commands *should* be the same as the 7200.11 ones, but possibly only some of them need to be issued and the order in which they are issued may be different. IF they work, they shouldn't make any "damage" (if they are correct and correctly executed they are not "destructive" commands) and you could attempt the unbricking of the "real" drive with at least some more confidence. In any case be ready to have a larger drive ready and the tool/OS tested to make an image of the unbricked drive as soon as you (hopefully) manage to revive it. These may be of help/reference: http://forum.hddguru.com/viewtopic.php?t=18819 http://forum.hddguru.com/viewtopic.php?t=18645 jaclaz

Let me doubt (with all due respect ) that you can have a WinFLP license (as those were issued only as part of the Software Assurance contract). http://en.wikipedia.org/wiki/Windows_Fundamentals_for_Legacy_PCs But the issue is not IMHO the actual OS, which anyway will need at least 512 Mb to run decently, it may be if you plan to run on it *any* real-time antivirus, they tend to peak well over 256 Mb and use in "normal" operation 100 Mb or more. The original specs for XP were: http://support.microsoft.com/kb/314865/en-us jaclaz

Yes, and : http://xkcd.com/327/ jaclaz

That's actually good, as you shouldn't use WAREZ. The disk is either in LBA0 status or it is not in it. You can check this status in the BIOS, when booting go to BIOS setup and try autodetecting the disk, when it is connected through a direct SATA connection. It will either show the right capacity (or a reduced ones n some cases) or a 0 one. This said, the SD15 firmware issues and corresponding remedies are specific to the 7200.11 model (and the same kind of "generic" reset has been with alternate success, used with the 7200.12 series too). There is unfortunately no "known-to-be-working" method (if applicable) for the 5400.6 model, only info we have is here: http://www.msfn.org/board/topic/158397-invalid-partition-table-on-my-500gb-hdd/ http://www.msfn.org/board/topic/155638-seagate-momentus-54006-st9500325as-freeagent-go/ http://www.msfn.org/board/topic/150293-unlock-seagate-54006/ The only "vague" report of the method having worked is "very" vague and here: http://www.msfn.org/board/topic/145751-seagate-freeagent-go-momentus-54006-solution/ If you value the data on it, you shouldn't even think of attempting recovery with this method, as we simply have NO previous validated experience. jaclaz

OT SCOOP! Apple considers running a bunch of queries against their financial database to create detailed reports "a herculean effort": http://www.ediscoverylaw.com/2013/09/articles/case-summaries/citing-proportionality-court-concludes-it-would-be-senseless-to-require-plaintiff-to-go-to-great-lengths-to-produce-evidence-defendants-are-able-to-do-without/ There must be some gaps in current technology, on one side there are peeps capable of looking at you every time you breath, listen to anything you say and read everything you write, and on the other someone considering extracting data from their own financial databases an ordeal. jaclaz

JFYI, it is not a matter of simply "burn-ISO-to-flash", there are a number of issues to take care of, a lot of users use multi-boot flash sticks and AFAIK the Win2flash approach is very similar to the original "how to install XP from USB" approach ( i would dare to say "replicating" it ), which has been found being not fully compatible with *every* setup/machine, and the more current approaches tend to use the install .iso "as is", see: http://www.msfn.org/board/forum/157-install-windows-from-usb/ jaclaz

Yes , but - specifically - it's not really "news" (from a technical standpoint), the comment by user twilightomni is accurate: http://en.wikipedia.org/wiki/Dual_EC_DRBG#Controversy Anyone using the algorithm after the paper by Shumow and Ferguson was published at the CRYPTO 2007: http://rump2007.cr.yp.to/15-shumow.pdf and after the article by Bruce Schneier posted: https://www.schneier.com/blog/archives/2007/11/the_strange_sto.html was eidently doing that intentionally or because of unexcusable ignorance. As Matthew Green puts it in this excellent article: http://blog.cryptographyengineering.com/2013/09/the-many-flaws-of-dualecdrbg.html About the live finger vs. cut out finger, it is the good ol' same bull$hit.A US$ 5 wrench:has traditionally proved to work alright for ol'passwords, no matter the algorithm used, elliptic curves or whatever, this time you will have the additional issue that if you forget your phone at the office you will not anymore be able to instruct your secretary to access it to retrieve that address or phone number that is only stored there and you will have to drive back some 300 miles instead .The only good thing that can come out of it is that if you accidentally break your finger or hand and need to have it bandaged/put in a cast, you are cut out of the rest of the world for the time needed for it to heal.Of course this will never happen, as there will be surely an "alternate" way (password) to access the phone (unless the good Apple guys are completely crazy).http://www.macworld.com/article/2048514/the-iphone-5s-fingerprint-reader-what-you-need-to-know.html Since you won' t be using it for months (as you would normally use the fingerprint) you'll risk forgetting it, so you will jolt it down on a post-it stored in a handy place, and access to the device will be as-easy-as-it-was-before (or even easier) for the "bad guys". jaclaz

Another good reason (IMHO) for closing a thread would be that of having in there people repeatedly and insistently whining about the way the board is managed. You may well get over it (still IMHO). jaclaz

The US$ 99 vs. US$ 550 sounds like the only good argument (though I don't see all these people giving away lumia 520's unlocked for US$ 99) , more like US$180-200, which still may have some merits. jaclaz

No, maybe you could do a "full" dump and then trick one of the few guys capable of analyzing it into having a look at it. http://www.msfn.org/board/topic/130005-creating-memory-dumps/ jaclaz

Are you somehow trying to say that Child Pornography should be covered by the 1st Amendment or similar provision? There are better places to discuss this kind of topics, be aware of Rule #2.b Back to topic. I am pretty sure some of our Apple firends won't like what will be said on Octoper 17th: http://conference.hitb.org/hitbsecconf2013kul/agenda-conference-day-2-17th-october-2013/ http://conference.hitb.org/hitbsecconf2013kul/cyril-gg-quarkslab/ jaclaz

JFYI, RTM means "Release To Manufacturers", it only applies to the edition given to (large) OEM's before the official launch of the product. The fact that the good MS guys (as hinted before) released it before it was "ready" (and senselessly induced everyone to install it on underpowered hardware) only means that in this case (not the only one) they behaved as "perfect morons", making the Vista OS getting the "bad name" it bears till today, making it a huge Commercial fiasco and somehow "forcing" for an earlier release of 7. Namely, in the case of Vista, RTM is November 8, 2006 and the end-customer version was released January 30, 2007, which would have allowed almost three months to fix (if they wanted) the most obvious issues. Not that after one year, when the SP1 was released February 4, 2008, it didn't have it's big share of issues: http://4sysops.com/archives/list-of-vista-sp1-problems-be-careful-with-service-pack-1/ Remember that it took more than 2 months to have the mess up with Windows Updates fixed for those that had the issue... So, you couldn't even rely on SP1, one year later, but had to wait for the "fixed" SP1. Of course the OS itself has no faults for the mis-management the good Microsoft guys did, but it is obvious that the "bad name" will always remain attached to the poor innocent OS. And the SP2, while containing good things, was of little use, as it came out on April 28, 2009, when all the media was already trumpeting about Windows 7 and how good it would be (soon available). Of course this has affected the most the less-technical savvy people, the "common" end customers which would just buy a HP, a Dell or any "big brand" OEM laptop or desktop with the pre-installed system, and later found out that the thing they bought was outperformed by the older XP machine their neighbour or friend had. Initially no info (or proper, or enough info) was given about the all new (also mostly senseless IMHO) BOOTMGR+\boot\BCD "shift" from good ol' NTLDR+BOOT.INI+NTDETECT.COM, and in such cases when the average Joe would have a booting issue the "procedure" adopted at the time by "highly specialized technicians" was to wipe and reinstall or use the recovery partition to reset to factory status. The initial common issues with drivers, UAC, Aero not running, and what not completed the scenario. No, it has not been a "lucky" OS. jaclaz

@ROTS The actual issue in most Western countries is only with child pornography (good ol' p0rn between consenting adults is not a problem at all AFAIK). Of course there have been (and there will be) exceptions, like this known case: http://web.archive.org/web/20111225024328/http://www.opposingviews.com/i/porn-star-lupe-fuentes-saves-man-from-bogus-child-porn-charges (but that was a mistake and the guy was proclaimed innocent) Before I forget: https://windowssecrets.com/top-story/touring-through-the-final-windows-8-1/ jaclaz

No. http://homepage.ntlworld.com./jonathan.deboynepollard/FGA/questions-with-yes-or-no-answers.html The WinsetupfromUSB page not working on Google Code is "queer" I just uploaded a copy of WinSetupFromUSB_1-0-beta9_rc4.7z I had around, here: WinSetupFromUSB_1-0-beta9_rc4.7z - 20.2 Mb See if it works for you . jaclaz

Well, NTFS.SYS (in itself) it is a "stable enough" driver. It is more likely that it reflects - under stress - a misbehaviour of the hardware (RAM or hard disk or it's controller, or even just the SATA cable or of the network, though the latter is less probable). Try to not use hibernation for a few days and see if the behaviour remains. jaclaz

I think it's just Charlotte having some form of allergy to it. jaclaz

Yep: http://www.wired.com/threatlevel/2013/09/freedom-hosting-fbi/ The internet expert was will be right, after all : http://www.msfn.org/board/topic/157597-win-xp-past-apr-2014-was-will-xp-be-supported-until-2019/?p=1047341 jaclaz

Chromium is the actual "engine" on which also Chrome is based. http://code.google.com/p/chromium/wiki/ChromiumBrowserVsGoogleChrome As said: Let's see possible reasons to use a (non-local, and possibly anonymous) proxy: to have some speed advantage in the transfer of data (unlikely, but possible in certain parts of the world) to reach an address that your ISP, firewall, IT guy, etc. has blocked (for whatever reasons) to reach an address which the provider has linked access according to IP geo-localization to reach an address in particular emergencies of failed DNS/internet section/whatever to reach an address in such a way that the other end cannot have your IP address (or geo-localization) to reach an address whose site administrator has listed your IP in a non-allowed or "black" list to make a second or nth registration/subscription to a service that links IP to accounts to reach an address that allows not concurrent connections from the same IP, when needing to make multiple connections to trick NSA (or other three or more letters agencies) into believing you are the devil and do not exist As I see it, #1 to #8 are all possible uses, while #9, while entirely possible, may NOT give the results expected . If you prefer I believe that NO proxy is "safe" (for the scope of #9), if "they" are after you , "they" will get you. jaclaz

I would say "interesting but not surprising" . In my dinosaurish view, something that is not there (if not really-really needed) and/or it is smaller, will result in faster operations ..... http://www.msfn.org/board/topic/145209-the-smallest-possible-size-of-bootsdi/?p=933421 jaclaz

The good news are that most probably it is a re-branded Logik-100/hipshing IR608: http://reciva-users.wikispot.org/Summary_information_on_Reciva_radios http://www.hipshingelectronics.com/Prod.asp?ID=39 IF this is the case, this page may be of use: http://logikir100.tripod.com/Logik.htm The bad news are that latest firmware is was seemingly available online from Reciva.com but needs/needed registering. . The generic gpl page is out of reach until end of september (at least): More generically, that thingy seems "Barracuda" based (whatever it means) which leads us right here: http://www.sharpfin.org/index.php?title=Main_Page As expected a JTAG access and some tinkering may be needed, but it seems like everything is well documented :thumbsup: Particularly, getting a login in order to change firmware seems doable without particular hardware, only with the GREATEST care and attention. http://www.sharpfin.org/index.php?title=Changing_Firmware http://www.sharpfin.org/index.php?title=Enabling_Login Still, unless you have as a hobby this kind of mods, it is not something I would suggest, as there is a concrete risk of "bricking" the radio. http://www.sharpfin.org/index.php?title=10_Sure-Fire_Ways_to_Trash_Your_Radio jaclaz

Good :, that is a sign that you have likely bought a "fake" USB stick (or anyway that a "wrap-around kind of issue happened because of some error of the controller/settings) and what you got is "just" the "wrap-around" issue. The second image you posted is identical to first one, which confirms how the error you got initially with DSFO could be ignored, but also that filesystem oriented recovery is impossible on that stick. Remember that Photorec cannot find the "original" filenames, and often it may mistake a file type for another (just as an example Office .xlsx and .docx files may be retrieved/recognized as .zip (mainly because they actually ARE ZIP files ). It is recommended to "post-process" the results from PhotoRec: http://www.cgsecurity.org/wiki/After_Using_PhotoRec http://builtbackwards.com/projects/photorec-sorter/ to first group recovered files, then, if you have issues, you may want to use TriD on the files that have not been identified properly: http://mark0.net/soft-trid-e.html You are welcome, I am sure . Normally the last file(s) that you saved won't be recoverable, BUT if what happened is a "pure" wrap-around issue, you may want to try re-sequencing the image. Translation/example: Imagine that you have what the OS/filesystem thinks to be a (very, very small) 10 sector device: 0123456789 and you want to write on it the words hello and world, if the device actually has 10 sectors you would have something like: 0123456789 helloworld BUT if it has, say, only seven sectors you would get something *like*: 0123456 rldlowo By appending a second copy of the image, like: 01234560123456 rldloworldlowo It is sometimes possible that also the "world" can be retrieved. In your case, the "queer" fact is that the image is larger that the original device, so it is possible that this wrapping around happened at "controller" level and you are actually have already a re-sequenced image. jaclaz

I will throw this one on the table also (just to keep things as together as possible): http://reboot.pro/topic/18573-hideandprotect-ntfs/ jaclaz

Are we going on a spin-off of the usual "RAM is there to be used and Windows knows how to use it alright" vs. "RAM is there to be kept free and just absorb some (little) power" flamewar? jaclaz