jaclaz

It sounds familiar.... http://en.wikipedia.org/wiki/Chewbacca_defense ...jaclaz ducking really fast... jaclaz

Sure , even a single happy bunny is better than none , but still, if with a little effort you can make more happy bunnies, life would be better..... http://www.msfn.org/board/index.php?showtopic=128727&st=10 jaclaz

Normally I would use fsz.exe (part of the dsfok toolkit): http://members.ozemail.com.au/~nulifetv/freezip/freeware/ that is if you have the space available to create a "whole" file, but It should be more convenient to use instead mksparse, here: http://reboot.pro/3191/page__st__25#entry70583 this way the file will grow only with the actual "chunks" that you write to it. And the reference app to write these chunks is dsfi (still part of the dsfok toolkit). I can give you specific instructions if this other approachs actual succeeds in getting more data. But if the test with DMDE on the original disk gives the same results, than there is a more serious issue somewhere "before" (partial unbricking or "failed" unbricking) though as said it sounds "strange". jaclaz

....don't forget "convenience" and "freedom" . Really, I do understand how there might be difficulties and even "unresolvable" ones in doing this in practice , and as said you are perfectly free to manage your project every which way you want/can , but the concept of "modularity" should IMHO be the first one whenever designing this kind of tools. We already have the MS guys that pretend to know better than we do what is best for us..... Try seeing it another way, let's take nlite as an example. Nuhi designed it in such a way that it is VERY modular (and this is actually a drawback as some "interconnectedness" is not IMHO explained or explained "well enough" ) But he could have made as well a three radio button choice thingy: Remove nothing Remove average (this is what is advised as the "best thing for you") Remove everything (max reduction) then, simplify it to a two choices: Remove average (this is what is advised as the "best thing for you") Remove everything (max reduction) (if you dont' want to remove anything then do not run nlite) Or even a single choice: Remove average (this is what is advised as the "best thing for you" and be done with it . (but I think that IF nlite was designed this latter way it would have had much less success ) jaclaz

Not really, different linguistical interpretation, nothing of much relevance . I read "already" as "already" as opposed to "at that point",or, if the actions suggested in #1 were carried: the bolded part in 2) would be a truism. (double one , as in #1 the third partition is made active and also in #13 of the linked tutorial) on the other hand, IF the thrid partiion had not been made active, the system wouldn't have booted at all..... The "play safe" was actually refered to the "Move" (as opposed to "copy"): I am pretty sure that your approach is very correct :, but as I see it missed a "what if something goes wrong" wayback provision, IMHO when dealing with disks/data always "better be safe than sorry" . jaclaz

@Ilko_t Thanks for the update. NO , the currently active one is the second. @SteveOC You want to play "safe". When you are in the grub4dos prompt, input these commands: map (hd0) (hd1) map (hd1) (hd0) map --hook root (hd0,1) Now run ls you should see the files BOOTMGR listed. Now: chainloader /bootmgr boot You should boot to Windows 7 "normally". Now copy the BOOTMGR and the \boot\ directory to the "main" Windows 7 partition. Reboot, and again at the grub4dos prompt run: map (hd0) (hd1) map (hd1) (hd0) map --hook root (hd0,2) chainloader /bootmgr boot (please note how this time we are loading the bootmgr from (hd0,2) i.e. from the "main" "third" partition). You should be able to boot again the Windows 7 normally. If this happens, then open Disk Management and set the "main" "third" system partition as the Active one, and reboot, this time without the USB stick/grub4dos. If everything is OK, then, and only then you can remove the contents of the (hd0,1) or even delete that partition allright. jaclaz

This should mean that the $MFT is OK (i.e. no need to analyze it manually with mft2csv). But if you ran the DMDE on the (incomplete) image, this may still be "normal". And, AGAIN, you are using a WRONG approach (attempting to image the whole disk at once). For the THIRD time, please read again this: You might want to try with even smaller "chunks". Another test (but be careful): What happens with DMDE on the original disk? I find it strange that the $MFT is "perfect" (as it seemingly is) but *all* the disk is unreadable (I could understand some areas, but not the large majority of the disk) jaclaz

Yep, this is what I was not sure about . If I recall correctly the mentioned Paul.lee thingy can open both, it is very possible that it has a "double" internal parser. The site is not reachable today, just in case: http://wayback.archive.org/web/*/http://paullee.ru/regstry.html Since the source code tor the "real mode" version is available, maybe someone familiar with Borland Pascal may be interested in woring on it.... The original site for regdat: http://people.freenet.de/h.ulbrich/ is also no more (and unfortunately is not cached in the Wayback Machine) . The "main" site has only the "front page" cached: http://web.archive.org/web/20110202154630/http://regdat.com/ The tool itself (shareware) is still available here: http://files.brothersoft.com/utilities/registry_tools/Regdat_15017.zip jaclaz

It seems to me like you are still missing a point. The Registry (online) is nothing but an assembly of 2 (win 9x) or 5 (NT) "databases" (or actually IMHO "filesystems") files. See also: http://www.911cd.net/forums//index.php?showtopic=24370&st=0&p=168043entry168043 Since you are seemingly old enough to remember good ol' DOS databases, you have to think to it as you would at a good ol DBaseIII (not that more modern databases are that much different ). You had a number of tables containing DATA, that were assembled and accessed in an "assembled" way through a form, and the results (still coming form the assembly) were visualized through a report. The normal online registry editor is nothing but a combined form/report "DBase" or "Clipper" app. Of course, like you could use *any* dbase uility to access directly the tables, you can use *any* registry tool to access the single files composing the Registry (offline). If you prefer, the Registry (online) as you are used to see it, is a building erected on-the-fly when booting with a number of bricks (and broken again into single elements when shutting down). Nothing prevents you to access the bricks when they are not assembled all together. jaclaz

See what is the issue (on the clone). Make a copy of the basic sectors the MBR and the PBR. The MBR is "easy", it is the first sector of the disk, CHS 0/0/1 or LBA 0. A suitable tool to make a copy of it is HDhacker: http://dimio.altervista.org/eng/ you want the first sector of the \\PhysicalDriven or you can use the mentioned rawcopy: rawcopy 512 \\.\PhysicalDrive1 C:\drive1.bin To get the right n try having a look at the disk in "disk management". If you have only a disk in your PC, it will be PhysicalDrive0 and the "clone" you attach to it will be PhysicalDrive1. While you are at it, can you see the Partitions(s)/Volume(s) in it? (LogicalDrive(s)). If yes, you need a copy also of the first sector of it (them), but since you are running 7, that sector may be locked. If this is the case, you might want to try this other software CLONEDISK: http://reboot.pro/8480/ http://labalec.fr/erwan/?page_id=42 or a tool to dismount the drive(s)/Partition(s)/Volume(s): http://reboot.pro/12413/ and then use direct disk access (rawcopy, etc.) to copy the PBR(s). Once you have the MBR and the PBR(s) copies compress them in a .zip file and attach them to your next post. If you have difficulties in getting the PBR's attach just the MBR and I will give you more detailed instructions on how to get the PBR(s). AFTER having got these copies, you can start TESTDIDK following this guide: http://www.cgsecurity.org/wiki/TestDisk_Step_By_Step You WANT a log file. If the disk was parittioned under VIsta or 7 you want to answer "Y" to the questions if irt should look for Partitions created under Vista. If you are lucky, the procedure might fix the issue. Report. jaclaz

666 (seriously, *any* number will do, the "number dialing" is only to make the modem connect). You know, like http://www.maturion.de/dreamcast/mterlouw/dcisp.htm You have to find a way (look in the Windows docs or, more likely in the actual modem documentation, how to set the "blind dial", if by any chance the modem is waiting for a dial tone, it will wait "forever"). The sense of the suggestion with Hyperterminal was "beyond" your test with the mobile phone (making sure that each of the PC has a functional Hyperterminal and Modem, which is however a good idea ), the point was if you could manage to connect the two PC's through Hyperterminal. (this would verify that there are no hardware or "hardware settings" issues or a "wrong" initialization string on either modem, the "AT&F0" sets the modem to "default" (factory), but different modems may have different "defaults") And you should read again the pages you found, there won't be *any* call as you have not an actual telephone line and not even a "plain" simulator for it, let alone a simulator with ring generation (which is a rather comples electronic "box" or that you can buy for a few hundreds bucks ). So, it is pointless to set the "server" as "waiting for incoming calls": http://www.maturion.de/dreamcast/mterlouw/trickwin.htm Tricking Windows into Answering the Line jaclaz

It seems like "standard" somehow "initiating" or "forcing" bootux.dll during booting: http://www.boyans.net/BootMenuPolicy.html Also, in a "dual boot" 7/8 environment it seems like it has a "bad" side effect: http://www.sevenforums.com/installation-setup/249301-bootmenupolicy-standard-win-7-hides-multi-boot-menu.html I would dare to call it "new non-standard" as opposed to "standard".... Or, on the other hand, it is interesting how Windows 7 is ALREADY considered "legacy" . jaclaz

Yep, this is the issue. In order to boot the XP the files NTLDR, BOOT.INI and NTDETECT.COM are NEEDED. Theoretically they should go to the Primary Active partition (i.e. (hd1,1) in your case) or at least in a Primary partiton (booting from a Logical Volume, though possible with a few tweaks is not "standard" nor "normal"). Check also the other partitions for the above files (it is possible that they went inside the recovery partition or to one of the two logical volumes). Since you have seen (during the Blue text part of the setup that you ran) that files were copied, they must exist *somewhere*. You should also check for directories named: $WIN_NT$.~BT $WIN_NT$.~LS at least the first one should exist and for files: SETUPLDR.BIN TXTSETUP.SIF jaclaz P.S.: Are you sure about partition numbers here?: There should be no Partiion Num 3, but a Partition Num 5 (maybe a typo?)

As I see it this part is senseless not because it is in anyway "wrong" , but because it is essentially an "act of faith" (without having any real world signs that what would be a good move actually is one): Let's see in detail: this is a wish, and a good one IMHO, in the sense that when and if someoine will provide us with something that is actually better than the desktop, I am pretty sure everyone will embrace the new technology. But untill the thing that should replace it is a monkey training toy, or Metro NCI, this is unlikely to happen. The logic fallacy is evident, the syllogism "new=better" has been proved right many times, but as many times it has been proved wrong. The further implied "if you don't embrace this new technology then you are senselessly conservative" is of course m00t, the actual senceful sentence being "if you don't embrace this new technology, that is evidently and proven to be far superior to the preceding one, then you are senselessly conservative" may have of course it's merits, but the actual evidence of the pretended superiority is far from being clear and surely not proved. Next sentence is even worse, another good wish: It is more along the lines of "I have a dream....", there are AFAIK not any particualr improvements regarding malware or viruses (and even if there are they will be worked around in no time) nor in anything that by sheer magic will make complexities vanish or make the thingy in any way "more reliable". Now if the proposal was to throw away what essentially is a NT system with a design going back to the early 90's with an entirely new archtecture/codebase, let's say a Real TIme OS like (example) QNX: http://www.qnx.com/ and/or tools like (other example) ERLANG: http://www.erlang.org/ that would be something we could actually talk about, but applying a (crappy) interface to (actually forcing it onto) a substantially "traditional" OS and call it "new" (I mean from the point of security/complexity/reliability) it's evidently a false statement or, in the best case an idealistic wish. This is instead (while still being a "wish") pure "bull§h**": Noone (here or elsewhere) is afraid of changes, but of course if the change is "for the better". Our own lives were revolutionized by the Facsimile, by the PC, by Internet, by the Mobile Phones, and we glided across these large technology shifts without a hitch (just like our grandfathers or grand-grandfathers glided across the changes connected to inventions like the Telegraph, then Radio, Cars, Telephone, Airplanes, Television and what not), adapting and learning new ways. It won't be difficult at all for us to learn how to use a "designed for 5 years old" interface, we learned from thin air how to deal with BASIC, and then with DOS and UNIX, do you really think that this change will be a problem for us? There is nothing "revolutionary": http://www.merriam-webster.com/dictionary/revolutionary in Windows 8, nor in it's new crappy interface, no "technology change" at all. It reminds me of motorbikes (mopeds), a modern 50 cc engine can have without an issue 8 HP's or more (please read - for politically correctness - 5.968 kW or more ) and a bike made with it can easily have a max speed of 60 or 70 km/h, but in order to be registered as "moped" (in Italy) and thus allowed to be driven by 14 year old kids, they must: have at max 4 kW have a max speed of 45 km/h what the industry does is simply to "dumb down" (usually by "capping" the intake) a bike (by itself capable of much better performances) in order to comply with the Laws and fulfill the requests of this market. Now, it makes a lot of sense for a moped you give to a kid, the fact that the "original" bike was designed for higher speeds means indirectly that it will have better brakes and handling and thus it will be safer at lower speeds when compared to a "strictly designed as moped" competitor, and it is senceful that the kids will have some time learning to drive at a "forced" lower speed. But usually, you don't look at mopeds as the source for innovation.... and I have seen very few people getting one of these : and have it "capped" because it goes too d@mn fast.... (or have an automatic gearbox fitted to it because it thus becomes easier to drive) jaclaz

The 0x21 is a "special" partition made by RMPREPUSB on the USB stick to increase the compatibility with pesky BIOS when (you used the option C: 2 Partitions or something lke that in RMPREPUSB, right?). THis is "normal" if you used RMPREPUSB. So, (hd0) is still the USB stick (which is allright, since you have rebooted and you did not run any .lst entry). But what do you mean by "and hd(1) is FDD" ? A device is either a Hard Disk or a floppy. If the USB stick is (hd0) and it has two partitions (hd0,0) and (hd0,1), the latter being the "special" one cylinder partition made by RMPREPUSB, the (hd1) must be (or at least SHOULD be) the internal hard disk. You should be able to access 5 (five) partitions on (hd1): (hd1,0) <- the "recovery" partition (hd1,1) <- the Windows 7 100 Mb "boot" partition (hd1,2) <- the Windows 7 "system" partition (hd1,4) <- the fist Logical volume (hd1,5) <- the second logical volume See: http://diddy.boot-land.net/grub4dos/files/syntax.htm There exists NO "root" on device (hd0) as it is a "WHOLE" hard disk, nor there is one on (hd1) which is again a "WHOLE" hard disk. A partition/volume/filesystem has an accessible "root", the "root" of the whole hard disk contains no files (as it has not even a filesystem). When you issue the command: root (hd1,1) grub4dos will provide some feedback, like: http://diddy.boot-land.net/grub4dos/files/basics.htm Filesystem type is NTFS, partition type 0x07 Again I am more interested on the output/feedback of the commands than to the description of them, if you could simply post the exact commands you issued and the exact feedback that you had, it would be more straightforward, right now I have to guess , based on your description: what command you issued what feedback you had what you assumed from that feedback or from something else that you didn't cite As an example, this: is what I call "vague" and can be read in at least three or four different ways..... WHICH exact commands? WHAT was the exact feedback? <. this is what they actually show HOW you derived from the feedback of the commands your colcusions? <- this is what you represented as "shown" by the "commands". NEVER use an acronym unless it is "universally accepted", FDD means "Floppy Disk Drive" but could also mean "Fixed Disk Drive", sometimes spending a couple more words can help If the USB device is (hd0) and the (hd1) is NOT the internal hard disk , then there is an "earliier" issue (at BIOS level detection of connected disks). jaclaz

Have a look at this, also: http://microapache.kerys.co.uk/ and to the various "altenatives": http://www.portablefreeware.com/index.php?sc=125 jaclaz

@ Fredledingue Here (scoop! ) is a screenshot of the new MS advanced training program (Lesson #2: identifying objects by their shape and colour and recognize simple English words) and the effects of the first Windows 8 Virus jaclaz

Actually it is a very interesting approach. The given link is about haveing the Dreamcast as "client" and the Windows Machine (with both the dial-up modem AND the "broadband", let's say DSL connection, as "server"). Now, if I get it right you want the Satellite to become a "Dreamcast" (client ) and the P4 become the "server". So, *somehow* you must "translate" this set of instructions: http://www.maturion.de/dreamcast/mterlouw/dcisp.htm to the Satellite running Windows 98 And apply these sets of instructions: http://www.maturion.de/dreamcast/mterlouw/trickwin.htm http://www.maturion.de/dreamcast/mterlouw/inconect.htm http://www.maturion.de/dreamcast/mterlouw/connect.htm to the P4 machine. BUT, there is the possibilty that one of the two modems (or both) have an issue with the (missing) phone line, so it is possible that you will need the "Modem Line Voltage Simulator". See also this: http://www.jagshouse.com/modem.html and this: http://www.computing.net/answers/windows-31/pc-to-pc-via-modem-article-here/10182.html Have you made some tests with Hyperterminal (or similar)? jaclaz

OK, let's start See how CASUALLY there is a dedicated Forum for this specific topic: http://www.msfn.org/board/forum/157-install-windows-from-usb/ jaclaz

Yes, now that we have a correct idea about your hard disk status, we have to understand what happens. Try describing what happens (and which choices you took). When you are booted from the USB and get to the grub4dos chioices, you can press c to get to grub4dos command prompt. From this you can run a few commands to understand what is happening (and/or boot to the Windows 7 if it doesn't). First step, since you already run (partially) the tool would be to understand WHAT files were copied WHERE. At the grub> prompt try issuing the commands: geometry (hd0) [ENTER] geometry (hd1) [ENTER] this will tell us if the drive order is USB=(hd0)=first disk or Internal hard disk=(hd0)=first disk i.e. if the drive order has been kept "normal" or has it already been re-mapped by an already run grub4dos command. Let's say that the drive order has not been changed, if it is replace in the following the 1 (hd1,x) with 0: root (hd1,1) [ENTER] ls [ENTER] can you see, besides BOOTMGR also NTLDR, BOOT.INI and NTDETECT.COM? If yes, issue: cat /boot.ini [ENTER] what are the contents of BOOT.INI? If not (that was the 100 Mb "boot" partition), try doing the same above but on (hd1,2) (the "main" primary partition). Report. jaclaz

Vey good this is the part that is interesting: =========================================================================================================== Partition Information for Disk 1: 152,625.3 Megabytes Volume PartType Status Size MB PartSect # StartSect TotalSects =========================================================================================================== Type 27 Pri 15,360.0 0 0 2,048 31,457,280 NTFS Pri,Boot 100.0 0 1 31,459,328 204,800 NTFS Pri 102,398.7 0 2 31,664,128 209,712,497 ExtendedX Pri 34,765.7 0 3 241,376,633 71,200,072 EPBR Log 12,307.6 None -- 241,376,633 25,205,977 NTFS Log 12,307.6 241,376,633 0 241,376,696 25,205,914 EPBR Log 22,458.1 241,376,633 1 266,582,610 45,994,095 NTFS Log 22,458.0 266,582,610 0 266,582,673 45,994,032 Here it is commented: =========================================================================================================== Partition Information for Disk 1: 152,625.3 Megabytes Volume PartType Status Size MB PartSect # StartSect TotalSects =========================================================================================================== Type 27 Pri 15,360.0 0 0 2,048 31,457,280 <- the recovery partition NTFS Pri,Boot 100.0 0 1 31,459,328 204,800 <- the "fresh install" 100 Mb Windows 7 "boot" partition this one contains BOOTMGR and boot\BCD NTFS Pri 102,398.7 0 2 31,664,128 209,712,497 <- the "main" Windows 7 "system" partition (remember this is "right" and opposite to MS terms) ExtendedX Pri 34,765.7 0 3 241,376,633 71,200,072 <-the whole Extended partition EPBR Log 12,307.6 None -- 241,376,633 25,205,977 NTFS Log 12,307.6 241,376,633 0 241,376,696 25,205,914 <-the first logical volume inside it EPBR Log 22,458.1 241,376,633 1 266,582,610 45,994,095 NTFS Log 22,458.0 266,582,610 0 266,582,673 45,994,032 <-the second logical volume inside it jaclaz

@SteveOC If (after dinner) you will be able to read this, it means that the whole idea of splitting the topic became self-evident . jaclaz

Well, then you should go and ask your questions to some kids ... BTW I wouldn't take your posts as an example of correct spelling, let alone grammar: jaclaz

A non-obvious idea Patented innovating technology And an App exploiting it http://www.nosedial.com/whatis.html The need for phone sanitizers might increase.... jaclaz

Yep. Almost but not quite. See if this helps you (it should): http://www.multibooters.co.uk/multiboot.html (please read "Windows 7" instead of "Vista ") More generally the MBR is the first absolute sector of a hard disk (or hard disk like) device. It contains: boot CODE partition DATA (the partition table) some more DATA (disk signature) The "object" of the EASEUS tool is (mainly) the partition table inside the MBR (for what relates to Primary Partition(s) and to the Extended Partition) and to one or more EPBR's (one for each logical volume) chained from the Extended Partition entry in the MBR. Strangely enough the BCDEDIT tool is a tool to EDIT the BCD store. This is a (BTW stoopid, as it has been coded with the same structure of a registry hive) sort of configuration file or .ini, as a matter of fact it does exactly the same functions the "old" BOOT.INI did on NT/2K/XP/2003. In a nutshell standard booting sequence is: NT/2K/XP/2003: BIOS->MBR->PBR of Active (primary) partition->NTLDR->BOOT.INI (user choices)->NTDETECT.COM->Windows Vista :ph34r./7 and later: BIOS->MBR->PBR of Active (primary) partition->BOOTMGR->\boot\BCD (user choices)->Windows The instructions you see are a (rather complex) set of grub4dos commands, making use of an additional external grub4dos script (shifthd.bat), it would be very complex to explain them, as it would need first making you aware of the grub4dos syntax and way of working (interesting but maybe OT or too confusing for you right now). In case you want to take a "crash course" on the matter, you would need to go through the grub4dos guide: http://diddy.boot-land.net/grub4dos/Grub4dos.htm and, after having got the "basics" there, find your way to the more advanced topics (mostly undocumented or badly so) related to the newish grub4dos features of batch scripting... Simplified the working is the following, the set of grub4dos commands attempt to "autodetect" the exact way your BIOS "sees" the mass storage devices connected to your system and tries to re-map them the way they "should be" when you have NOT booted from the external USB, in order to make the install work. Your pre-existant install of WIndows 7 is most probably made originally using a feature of the Windows 7 OS that makes two separate partitions, the "Boot" and the "System" one (that MS names "the other way round") compare with: http://www.multibooters.co.uk/system.html http://www.multibooters.co.uk/articles/windows_seven.html#install7 It is possible that this (combined with the still UNdetailed) situation of your other partitions) "confuses" the grub4dos detection and *somehow* the devices (and/or the partitions in them) are not presented "in the right order/way" to the BIOS (for further booting) or to the actual XP installer routine. So, we need to: understand how exactly your disk is partitioned what exactly the grub4dos sees when it "fails" (and why exactly it "fails") find a way by either changing the partition scheme or changing the grub4dos commands or issuing manually a few of them on the grub4dos command line to have the thingy work Since I presume that this will be not an "easy-peasy" one, if you are OK with it (please acknowledge this post of mine) I would split your posts and related replies to a new thread, so that we limit the length of this "main one" and the outcome (hopefully successful) will not risk to be lost among the many pages of this thread. I would title it: jaclaz