jaclaz

You see, that's the WHOLE point . You are perfectly free to post that, it is your opinion, and though you provide NO backing for it, and it is clearly completely WRONG , we do respect that (somewhat ) This is freedom . jaclaz

Yes. http://homepage.ntlworld.com./jonathan.deboynepollard/FGA/questions-with-yes-or-no-answers.html Now, should the question actually be: The quick answer is "it depends". The long answer being "it depends", there are quite a lot of possible "quirks" in the way BIOSes handle the USB booting, my increasingly OUTdated pages reports some of them (FAQ#10): http://jaclaz.altervista.org/Projects/USB/USBfaqs.html The way the device has been paritioned/formatted and the Size of the primary partition, besides the size of the whole device may play a role in booting or completely fail to. The most "comprehensive" solution nowadays is usually the "NON-standard" partitioning through FBINST: http://reboot.pro/9460/ http://reboot.pro/7932/ http://reboot.pro/11753/ but there are more (bad) BIOSes then stars in the sky, and DELL's are re-known to be normally a PITA, so YMMV . BTW, if you use a USB 3.0 port, unless the PE has USB 3.0 drivers "integrated", you will get a BSOD 0x0000007b anyway. jaclaz

Nothing. I.e. in this cases, you need to buy TWO items: a dust bin a new disk drive Quick instructions: throw the old disk in the dustbin use the new disk instead You have to live with the fact that sometimes you win, sometimes you lose, and it is NOT worth the time and effort (EVER) to "repair" a disk drive if not for the sheer recovering of data (if any) on it. A "botched" drive is - strangely enough - "botched". (last character in the above is a "full stop" or "period") Try to see it this way: when you get a brand new disk drive you expect that it will "live forever" (and this WON'T happen) before or later you will loose some (often important) data because you didn't have a sound backup strategy exactly because that new disk drive will fail if - by sheer luck - you manage to revive the disk to recover data, you are in a different situation from #1 above, you now KNOW that that particular disk drive failed at least once and actually using it further would be "pure folly", the first time you didn't imagine that this could happen, after, you KNOW that it can happen now, a disk drive that suffered ONLY from a minor issue - like the original "botched firmware" of the 7200.11 and that after the repair passes BOTH the short and long "manufacturer test" AND it appears to work normally may be re-used - with all the cautions and as a redundant storage media, BUT if you experience *any* quirk of *any* kind, even if it passes the tests, should go in the dustbin in NO time jaclaz

You need some "basics" before anything else . The MBR (Master Boot Record) is part of the DISK (WHOLE disk) i.e. there is one (and ONLY one) MBR for each disk drive device. The PBR (Partition Boot Record) or VBR (Volume Boot Record) or bootsector is part of the Partition or Volume, i.e. there are as many VBR's as there are Volumes on the disk drive device. The HP hardware normally comes with a "specific", "proprietary" MBR CODE, that allows to press F11 to get to the Recovery partition. If you change the MBR code (as an example by installing *any* MBR based bootmanager and or simply run a MBRFIX or on Windows 7 a bootsect with the /mbr switch) that original MBR code is gone for good and restoring it (unless you have a copy/backup of it) is/will be - to say the least a nightmare. See: Unless you have re-formatted the partition/volume, there is a copy of the PBR/VBR strating on sector 6, so that wouldn't be a problem to restore it, just in case: http://thestarman.narod.ru/asm/mbr/index.html http://thestarman.narod.ru/asm/mbr/ntFAT32BR.htm You will need to restore not only the first sector, but also the other two (a FAT32 VBR is actually three sectors long, the "main" one being sectors 0, 1 and 12, while backup ones are sector 6, 7 and 8. (please be aware that the "third sector" is #12 only on NT based systems, in DOS/Win9x it is #2 and in ReactOS it is #14 ): http://www.911cd.net/forums//index.php?showtopic=23382 http://www.911cd.net/forums//index.php?showtopic=23382&st=12 The "flashing" cursor - however - is traditionally connected to a botched BPB, namely disk geometry, but not only. If you can get the MBR, (first sector of PhysicalDrive) and the PBR (first sector of the LogicalDrive), through an hex editor or a tool like HDhacker: http://dimio.altervista.org/eng/ zip the two files together and attach the .zip to your next post, I may be able to have a look at them and tell you if anything looks "strange" to me. An only seemingly unrelated thread: http://www.911cd.net/forums//index.php?showtopic=23408&hl= jaclaz

There is a possibility, though of course with rants but not actual info and different approaches/all things mixed together just a guess, but there is a distinct case where any of these methods won't work, and that is if the PC has USB 3 ports (and needs USB 3 drivers). Another likely possibility, since several methods failed is an issue with the actual source, possibly (badly or "too much") nlited and/or (badly) integrated with SP's or later KB's or simply, for *whatever* reason, "botched". There may also be issues (maybe) with some of the less common "eastern languages" source, but I doubt it. @TheEditor If you would be so nice to choose one method (the given manual way being the easiest to correct/fix/modify) and post the standard litany: http://homepage.ntlworld.com./jonathan.deboynepollard/FGA/problem-report-standard-litany.html Maybe we could go forward, until you continue saying "this didn't work" or "this other didn't work" we will remain in the "I'm ill, doctor. Help!" stage, actually in the "I'm ill, doctor, and you suck as a doctor. Help!" one. jaclaz

WHO knows? The warning: applies here like everywhere else . Edit: @submix8c Your first link is strangely similar to the one I originally posted, you were not paying attention enough jaclaz

If it helps , it is confirmed as a problem in Windows 98: http://support.microsoft.com/kb/187188/en-us jaclaz

No you haven't. No Toshiba hard disk locks itself if a log gets to 320 or multiple thereof. Possibly you have a similar symptom (i.e. the disk drive in EITHER of BSY or LBA0 state). Yes , this is "normal". If the disk drive is under warranty, they will replace it, if it is outside warranty they will do nothing, in both cases your (lost) data is not their problem. Maybe yes, maybe no. But you see, the real question should not be if anyone else has had this or a similar problem, but rather if a way to recover your data (or disk) exists and is "public" and it applies to the particular symptoms (and cause of them) you are experiencing. Well, at least you will need to provide a description of the symptoms. Standard litany: http://homepage.ntlworld.com./jonathan.deboynepollard/FGA/problem-report-standard-litany.html Right now we are in the "I'm ill, doctor. Help!" stage, worsened by "My cousin has had something similar last year" jaclaz

There is an issue, at least a "philosophical" one . According to MS (but we all know how in some cases the info available is somewhat inaccurate, often at least partially misleading or - in a few occasions - plainly wrong ) the 22 Gb does not "sound right", see here: http://support.microsoft.com/kb/191824/en-us Disk Size Threshold Threshold Percentage Space ---------------------------------------- <= 512 MB 10.0 25.6 - 51.2 MB <= 1 GB 5.0 25.6 - 51.2 MB <= 2 GB 2.5 25.6 - 51.2 MB <= 4 GB 1.2 24.6 - 49.15 MB <= 8 GB 0.6 24.6 - 49.15 MB <= 16 GB 0.3 24.6 - 49.15 MB <= 32 GB 0.2 32.8 - 65.5 MB > 32 GB 0.1 32.8 - ???? MB for a drive larger than 32 Gb the threashold is (even on drives for which the cleanup thingy has not been disabled through the Registry) 0.1%. . So in theory the thingy should be triggered around 750,000,000 bytes, i.e. around 715 Mb, much less than the 22 Gb! Since the "threasholds table" has as last entry 32 Gb, it is possible that some miscalculation occurs, but it is "queer". Personally, running Windows 98 with a single volume 700 Gb in size is what I would use as an example of "pure folly", for a number of other reasons, but maybe, as often is, it is just me . jaclaz

Additionally, no information was given about how the 700 GB was partitioned formatted, nor whether the 22 Gb free were on a single partition, etc.... And of course though it may be "common knowledge" that SiL 3512 contollers allow "native SATA" mode on Windows 98 , this wasn't specified and not necessarily it represents a solution to the varios "big sized drives" under Windows 98. You might want to appreciate the dubitative form of my maybe in my reply to the OP. jaclaz

There was no actually helpful suggestion implied in my post, only a "generic": and a hinting that maybe, since one or the other of the mentioned utilities has been proved to work for several (many) people, then it is possible that you have *something else*, be it the source, the actual USB device or your understandng of the use of the tool that *somehow* is "not standard". At it's very minimum, please read here: there is no actual need of a dedicated tool, you could try the manual steps outlined in the above. The mentioned thread is about an user (BTW using Windows 7 as "building" environment) that detailed how exactly to make a USB install stick manually (there are anyway a limited number of steps in it, ten in total) self-imposing the use of NO third-party tools. jaclaz

Maybe it is because you are using a tool outside it's intended usage paradigm. This tool has helped surely thoudands, likely tens of thousands, possibly hundreds of thousands people in installing XP from USB device. (people that were running XP) Some other tools, including he one wimb pointed you to or the "other app": have been developed since, some may work "better", some may NOT work, some may be working AND more convenient. Try looking at the half full glass , if you had this *need* before 2007 you would have had NO possibilities whatsoever . jaclaz

Yes/maybe. See here: http://www.annoyances.org/exec/show/article03-102 Using the DisableLowDiskSpaceBroadcast Registry entry should do: http://support.microsoft.com/?ID=KB;EN-US;q188074 jaclaz

It could be something completely UNrelated to the "main issue" described in this thread. Is the disk LBA0 or BSY? What I personally would do would be: clean the contacts (BOTH heads and motor one) THOROUGHFULLY try, following it to the letter, this guide: http://www.mapleleafmountain.com/seagatebrick.html try at first with the head contacts insulated, if it doesn't work, try again with the motor contacts insulated. jaclaz

Well, there is no real *need* to use a "gadget" and to connect to the terminal commands, it depends on WHAT/HOW/WHO set the password. You need to unlock exactly WHAT model? Coming from WHAT? (I mean standard PC, X-box, etc.)? Is security set to "high" (good) or "maximum" (bad)? Usually googling gives some results: http://www.seagateunlock.com/ http://ipv5.wordpress.com/2008/04/10/4/ http://forums.seagate.com/t5/Barracuda-XT-Barracuda-Barracuda/HDD-locked-enter-password-5-left/td-p/47233 http://forum.hddguru.com/seagate-non-standard-ata-master-password-t12920.html jaclaz

That would be very nice . Well, I don't think that anyone is pretending to deliver (or get) the "ultimate solution to all virus/malware problems", but having both the concepts and some practical examples may help to put some corks in the bigger holes, the boat would not become "perfect", but still it would ship less water . jaclaz

Probably this one: AND links in it. jaclaz

Dencorso, you should tune your grammar : http://en.wikipedia.org/wiki/All_your_base_are_belong_to_us jaclaz

With all due respect you didn't specify anything, you vaguely cited ACL's, temp folders, alternate credentials, sensitive areas of the system, services that do not actually require NT Authority\Local System or other unusual priveleges and GPO's. I do like the approach , but it would be interesting if you could provide some examples, lists of the services, etc. jaclaz

On behalf of IACDUIAL, the International Association of Children Designing User Interfaces After Lunch , I want to signify how your statement is higly offensive of the professionality of the Members that have designed in the past and will design in the future MUCH BETTER interfaces than Metro. jaclaz

You must be joking . The intended procedure is: buy a Microsoft digital camera (the thingy will be presented soon, it runs Windows 8 ARM ) take a snapshot of the screen upload the picture to the cloud (MS cloud) through a paid for subscription (the MS camera doesn't save anything locally you must upload it to the cloud) buy an OCR app at the MS online store (including the needed framework it is only around 3 Gb in size) run it (in a Virtual Machine) and have it process the online image (that you have re-downloaded in the meantime, and that goes in a special folder that you cannot access, only the TrustedOCRService can) the ouput will be an .xml file that will be, once stored on the cloud, re-downloaded and automagically converted to plain text using the MSXML2TXT TrustedConverter (another few bucks on the MS cloud store) at this point you hit Ctrl+V, a small window popup will appear asking if you really want to paste plain text in an Excel cell (since the content is different from the cells immediately before and after) and you have to fill a form to guarantee that you won't sue MS if the result is not what you expect, digitally sign it and send it to the cloud, which depending on the speed of your connection and the status of the servers may shortly authorize the paste operation, log it both on your PC and on your MS account, and finally issue the OK to the TrustedKeyboardFilter to let the command go through jaclaz

Don't tell me that you are still using BLUE? I went GREEN a long time ago.... This should work since Windows 3.x and up to XP/2003: http://www.kevinscrate.com/blog/2007/12/22/change-the-bsod-or-blue-screen-of-death-to-a-different-color/ http://www.petri.co.il/change_bsod_color.htm Please do appreciate the high level technology used , nowadays the good MS guys would need at least ActveX, .NET, 1 zillion entries in the Registry, setting file written in a XML file , two interdependent running services, a performance monitor, an event log connection and a few digital signatures here and there (and to change the setting you would need to impersonate Super-Hyper-Mega-TrustedInstaller ). JFYI, the good Mark Russinovich - after an intiial hiccup - came out with a nice thingy (with help from Alex Ionescu ): http://blogs.technet.com/b/markrussinovich/archive/2010/12/14/3374820.aspx http://blogs.technet.com/b/markrussinovich/archive/2011/01/11/3379158.aspx So you can have your PPSOD even now . jaclaz

Well, no . (meaning that you would have had exactly the same issue if you attempted to install from CD, the test on the virtual machine went OK because the virtual machine on which you tested needs NOT a Mass Storage driver - i.e. the needed one is already in your source). If you prefer, if you have not an adequate mass-storage driver, no-matter from which device you attempt the install, you will have issues. There is a FAQ sticky: which is was originated for the "other" app, but Q3 is "common" between all "install from USB" thingies, and relatively to the (SATA) Mass Storage device drivers. On most machines you can get around a missing SATA driver by changing the settings in the BIOS to "IDE emulation mode" or similar, but you will have later to install the driver and often it is not very easy. On laptops (where BTW it is more likely that you will install from USB because you miss the CD/DVD drive), such option in the BIOS is very often not present, so you need the integrated driver (or use one of the available "F6 floppy" workarounds). This is the part that is not clear (to me at least) . The idea is to have the Source integrated with the needed drivers and then create the stick through WinsetupfromUSB from this integrated source, if you did this, then it should have worked. Yes, but remember to start from a non-nlited source. No, the issue is not when you format (I mean unless you format it 100,000 to 1,000,000 times ) it is more an issue when using NTFS (or any journaled or semi-journaled filesystems). From the first /actually very vague) data about lifetime of USB sticks (actually of the memory in them) a lot of betterings have been introduced, besides changes in the actual flash memory, modern sticks use "wear leveling" algorithms, so right now, though I personally recommend - unless there is a "real" *need* for NTFS - to use FAT16 or FAT32, the reports of sticks wearing out have lessened or completely disappear, with a recent USB stick I would rate probabilities of a failure as follows: 55% lost//stolen/forgot on another site 25% factory defect/bad solder/poor components 12% my dog ate it 5% zapped due to static electricity/desktop not properly grounded/with 120 or 240 V AC connected accidntally to the chassis 2.5% worn by using a journaled or semi-journaled filesystem (please read as NTFS) 0.45% other reasons 0.05% worn by repeatedly formatting it Please take note that when you format under XP, very little writes are performed, while when formatting under Vista or 7 without the /q switch the whole drive will be wiped (00 written): jaclaz

Allow me a carpenter's comparison . jaclaz

UNfortunately you are correct : the Warranty (where applicable) only refers to a replacement of the defective disk drive (though there have been exceptions made for "largely failing" disks/series).. I don't hink there is anything that can be done DIY to "repair" that disk, but is it only (very) slow? I mean, does it have read errors or - though over a long period of time - data read from it is OK? If the latter it should be just a matter of "keeping it cool" and have patience while imaging to a new disk. jaclaz