jaclaz

jaclaz

What do you mean "it fails to register"? Can you try manually registering it with regsvr32? http://ss64.com/nt/regsvr32.html jaclaz

@Click Beetle Dx There is still some difficulties in understanding the setup you have. What do you exactly mean by "Dial-up"? Do you have an actual modem inside that machine? Do you have an actual modem (external and connected through a serial cable or USB)? (either analogic or ISDN) Or, like anyone else nowadays you have a Lan card (Ethernet) with an Ethernet cable connecting the PC to a DSL router/modem ? Please let's leave alone for the moment the USB tethering to your cellphone, which is the hardest to trouble shoot usually and the Wi-Fi, since you seemingly have not a local Wi-Fi at home (or where you normally are when posting). Describe with as much detail as you can the hardware involved in what you call "dial up internet". jaclaz

It seems like you are having several "bad areas". As said your best option next is ddrescue under Linux, using a Log: http://www.gnu.org/software/ddrescue/manual/ddrescue_manual.html Usually it can recover as much as it is possible. What are the temperatures of that disk drive? It is a good idea to "keep it cool" (like by putting it under the airflow of a fan) when doing intentsive i/o (like imaging/cloning). jaclaz

Hey, kid, remember that the particularly outdated "style of computing" is what very likely allowed your dead (or mom, or both) to procure what you eat and the place where you live and that it is the thing that allowed you grow long enough to be able to express your (senseless) opinions now. Consider also how the electricity that you are using to operate your hardware gets to your home because a number of engineers used and still are using that style of computing and do it rightly. jaclaz

@kostas275 Try doing the power off by disconnecting the power cable, and waiting one minute. No matter if *needed*, it has worked fine with the power off step. @Azurlake Shouting really hard at hardware is a known technique that I personally use, when needed, but you need to be trained to use it, and often some plainer threatening works fine: http://www.msfn.org/board/topic/139328-disc-drive-unable-to-eject/?p=891753 (farting is of course a no-no for the obvious minimum level of education and dignity , and the push-ups serve no purpose whatever ) jaclaz

OT , and completely unlike useful for your actual issue , some old time wise words to ponder upon: http://en.wikipedia.org/wiki/Jumping_from_the_frying_pan_into_the_fire jaclaz

You have to consider how - among all programming chores - kernel level programming is one of the most difficult ones (if not outright the most difficult one). ones. I wouldn't advice anyone to start from it. You normally need a decent familiarity with C/ C++ and with writing programs in userland before attempting to go down to kernel level. http://en.wikibooks.org/wiki/Windows_Programming/User_Mode_vs_Kernel_Mode jaclaz

Well, when I am having difficulties to produce some nonsensical statement, I often use the Hal Berenson's site to get inspiration. By saying everything (and the opposite of it), multiple times, it can happen to get something right, on average 50 % of the times, and is rather easy, now, to acknowledge that Windows 8 is a failure (and putting all the blame on Sinofsky - whom surely has a lot of responsabilities but cannot be the only root of all evil). What is not bold (and often totally apodictic) statements is petty talk and chattering about people working at MS (and how much they failed in whatever they are/were up to or more generally badmouthing everyone else but himself). If you go through his (to be fair, once cleaned off the badmouthing of every software product on Earth , and of all the other people in the business , seemingly quite honest ) recalling of the failure of his own startup "PredictableIT": http://www.zoominfo.com/CachedPage/?archive_id=0&page_id=1902037377&page_url=//www.microsoft.com/presspass/exec/de/Berenson/default.mspx&page_last_updated=2008-02-21T10:48:11&firstName=Hal&lastName=Berenson http://hal2020.com/2012/06/06/anatomy-of-a-startup-predictableit-part-i/ http://hal2020.com/2012/06/11/anatomy-of-a-startup-predictableit-part-ii/ http://hal2020.com/2012/08/31/anatomy-of-a-startup-predictableit-part-iii/ You might see how much similarities there are (were) between his own "business model" and the ones he now widely criticizes. No, most probably he is a good guy , but not someone I would rely on for "authoritative" opinions on softwares and particularly on Microsoft ones. jaclaz

Wayback Machine to the rescue: https://web.archive.org/web/*/http://windows98.ic.cz/chipset/intelinf.zip jaclaz

I guess we will need anyway to define "lightweight". Just yesterday it was released a new version of one of the "augmented privacy" YACBBS, SRWARE Iron: http://www.srware.net/forum/viewtopic.php?f=18&t=7502 which "portable" version is in a .zip file that expands to around 132 Mb. In my dinosaurish view, if a web browser needs (besides all the rest) two dll's (namely chrome.dll and chrome_child.dll) sized 37 Mb each it is a sign of how humanity is doomed . jaclaz

Yep. And that error would explain nicely why the filesystem is not recognized. A "normal" NTFS volume has it's $MFT starting on LCN 786432 with an 8 sectors/cluster that would make 786432*8+2048=6,293,504, the $MFT plays a vital part in filesystem recognizing and access and for the error you got it seems like that sector is in a damaged/bad area. You can try to see what happens with "ignore all", or decide to "abort". The next attempt is to try making an image of the disk using a more suitable tool for damaged disks, there is a very good one for Linux (that would make the imaging procedure automatic) and also a more manual Windows one: http://www.datarescue.com/photorescue/v3/drdd.htm but then you can try imaging the disk in chunks manually with DMDE, (to get the "advanced" LOG feature in it you need the Professional edition) If you are familiar enough with Linux (and command line) you can use ddrescue using a log. A succinct "theory of operation" when imaging manually in "chunks" is provided here: http://www.msfn.org/board/topic/170288-lost-partition-and-filesystem-problem-with-adata-sh14-disk/?p=1059909 jaclaz

...provided that unticking that check box actually disables the feature.... jaclaz

Yep, 4/5 to 9/10 of this thread is to be considered obsolete. Which I cannot but tag as YACBBS (Yet Another Chromium Based Browser Spinoff). There are by now (including the senseless shift of the good Opera guys, see: http://www.msfn.org/board/topic/105936-last-versions-of-software-for-windows-98se/?p=1067020 (if you wish it would be nice if you sign the petition) tens of slightly different browsers that use the same Chromium/Webkit (or nowadays "Blink") "core" engine: http://www.chromium.org/blink http://en.wikipedia.org/wiki/Chromium_(web_browser) http://en.wikipedia.org/wiki/Comparison_of_web_browser_engines 99% of which also sport a similar "dumbified" interface. jaclaz

Possibly a stupid question, but won't a 32 bit BootIce work the same on both a 32 bit and a 64 bit OS? Or there is something that I cannot recall right now that is "bitness specfic"? In any case, if bitness specific is needed, it would make IMHO more sense to adopt a solution similar to the one gbrao used here: https://sites.google.com/site/gbrtools/home/software/bootice-portable/downloads http://reboot.pro/topic/8986-bootice-a-boot-sector-manipulation-utility-v078-released/?p=177623 where the used version is "automatically chosen". jaclaz

Good, the MBR, as expected, is fine (but is important to check it anyway).There is a single entry in it: Entry Type Boot bCyl bHead bSect eCyl eHead eSec StartSector NumSectors #0 07 80 0 32 33 1023 254 63 2048 2930272256 which is about a NTFS (or exFAT ) volume created under Vista or later (beginning on LBA 2048) sized 2,930,272,256 sectors, i.e. 1,500,299,395,072 bytes in size. Since you cannot access the logicaldrive through an assigned drive letter, you will need to use another approach to get the VBR. Now it would be about the right time to make either a dd-like image of the disk or to make a clone of it. You will need a 2 Tb disk to make an image or a 1.5 Tb disk to make a clone. Get the free version of DMDE: http://dmde.com/ and follow the instructions here: http://www.msfn.org/board/topic/170392-how-to-recover-accidentaly-deleted-partitionfiles/page-2#entry1061689 If you decide to not make the image (either because you feel adventurous or because you don't have the money to procure a new disk), you can skip (at your own risk) to the next step, which is, still using the DMDE and the linked above instructions, to save a copy of first (say) 2100 sectors. I.e. you need to set the Start sector to 0 and the Number of sector to 2100. What is actually relevant is just the sector LBA 2048 (which is the PBR or VBR, Partition or Volume Boot Record) but having a bunch more sectors may be useful to see if strange forms of corruption happened. You also want to make a copy of the very last sector of the partition, i.e. sector 2048+2,930,272,256=2,930,274,304 which is the PBR Mirrror, i.e. it should be an exact copy of sector 2048. Compress the two resulting files into a zip archive and upload them like you did for the MBR. jaclaz

Good , you choose to "activate by phone", call MS, explain the issue and they will issue a new activation for you: http://forums.majorgeeks.com/showthread.php?t=242370 But still, this has nothing to do with having Windows XP pre-activated (or needng no activation) on *any* computer. jaclaz

I would venture to say that it is an affirmation by omission. They simply miss millions of telemetry feeds (those of the people that DID NOT buy or use Windows 8.x) and the consequent digital silence is deafening. jaclaz

Actually (and strangely enough ) the title is somehow linguistically accurate. Malediction - which has now more commonly the meaning of "curse" has originally also the meaning of "slander", and in this less used meaning it applies perfectly: http://www.etymonline.com/index.php?term=malediction Joyvalle has a *somehow* failing hard disk that happens to be a Seagate 7200.11 and, knowing the extremely bad fame that this model has gained, assumed that the disk was "bricked", affected by either BSY or LBA0 (the known issues that affect at least a specific model/period of production/version of firmware) and posted on the huge mega-thread about those issues: http://www.msfn.org/board/topic/128807-the-solution-for-seagate-720011-hdds/?p=1066364 and was invited to start a new separate thread. A suitable title could be : but more seriously, it could be: jaclaz

I don't know. At the time you posted a (blacklisted) VLK key was not in the OP, there was still a (teeny-tiny) possibility that it was a legitimate kind of request, even if it did not sound like that. The Heart of Gold could have traveled six or seven solar system feeding it to the improbability drive, but still it existed . But the Mythbusters approach is usually sound: jaclaz

Good, start by providing a copy of the MBR (first absolute sector of the disk). A suitable tool (for the not-so-avanced user) is HdHacker: http://dimio.altervista.org/eng/ under Windows 7 you will probably need to run it as Administrator. Check which disk number the affected disk has in Disk Management (like Disk 0, Disk 1, etc. Disk n) In Hdhacker you want to select "Physical Drive (MBR)", n, then "First Sector (MBR)", "Number of continuous sectors to read" = 1 Then press button "Read sector from disk" Then press button "Save sector to file" Choose a location and filename and save the file. Then compress it to a zip archive and either attach the .zip to your next post or upload it *somewhere* and provide a link to it. jaclaz

Which part in Rule #1a: http://www.msfn.org/board/index.php?app=forums&module=extras&section=boardrules are you having troubles understanding? A non-enterprise (or if you prefer non-VLK) original CD needs activation or needs to be "cracked" (and this won't be discussed here). jaclaz

If you can see the disk drive in the BIOS but it is shows as 0 in size then it is the LBA0 problem. <- this is NOT your case If you cannot see the disk drive in BIOS then it is possible that it is the BSY problem. <- this is probably your case READ the read-me-first (which is what you should READ FIRST): http://www.msfn.org/board/topic/143880-seagate-barracuda-720011-read-me-first/ FORGET about the first post on this thread and READ instead the recommended guide by CarterinCanada: http://www.mapleleafmountain.com/seagatebrick.html If you cannot understand what is written in the two given above resource, as said, try asking for help to a friend of relative with some more familiarity with English, this is your actual problem! jaclaz

@TomasMascinskas You have to understand that there are three "levels" when it comes to a disk drive: Real physical level (this is what the BIOS can see and that in your case is OK) Physical level (or RAW device) which is what Disk Management uses to access the device Logical level (what Explorer or other file manager will use ONCE the Disk Manager above will have created a valid logical structure, i.e. partitions/volumes and filesystems on them)A bricked disk will not be accessed correctly at level #1 above and consequently it won't be available at the other two ones. An unbricked disk will be accessible at level #1 and at level #2 above but not necessarily at level #3 as, for a number of reasons its logical structure may have been corrupted. Your disk is detected correctly in the BIOS , and as such your disk is NOT "bricked" (anymore) , BUT evidently the logical structure on it has been damaged . Start a NEW thread and we will see if it is possible to repair/recover the logical structure of the disk or if at least file-based recovery is possible. In more detail, the partitioning of the disk is still OK (your disk management does see a single partition on it) BUT NO valid filesystem is recognised by the Windows and as such a drive letter CANNOT be assigned to it. jaclaz

Kostas275, really, it is not easy to understand your question. What you wrote is not English. It sounds like English, i.e. you are putting together English words, but the result cannot be understood. It is extremely important that you make understandable questions and that you understand completely the answers as an even minimal mistake may make the disk drive unrecoverable. Try writing in Greek simple sentences and using Google translate, it often produces a good enough result: http://translate.google.com/ remember, simple sentences Πραγματικά, δεν είναι εύκολο να καταλάβει την ερώτησή σας. Αυτό που έγραψε δεν είναι η αγγλική. Ακούγεται σαν αγγλικά, δηλαδή βάζετε μαζί αγγλικές λέξεις, αλλά το αποτέλεσμα δεν μπορεί να γίνει κατανοητή. Είναι εξαιρετικά σημαντικό ότι κάνετε εύλογα ερωτήματα και ότι έχετε κατανοήσει πλήρως τις απαντήσεις ως μια έστω και ελάχιστη λάθος μπορεί να κάνει το δίσκο ανεπανόρθωτο. Προσπαθήστε να γράψετε στα ελληνικά απλές προτάσεις και χρησιμοποιώντας το Google μεταφράζει, θα παράγει συχνά ένα αρκετά καλό αποτέλεσμα: http://translate.google.com/ θυμηθείτε, απλές προτάσεις jaclaz