jaclaz

Why a fixed list? This match selected "normal" install only. What about a dynamically created list? I do like people proving me wrong , expecially when they are right. jaclaz

Trying to put some sense to it, this is the "other" (slightly later) version found: Maybe it is possible to find IEAK3.2 and check if there is any "support" file. The .txt document I found explicitly talks about "CompressionType" being switchable between MSZIP and QUANTUM. This document is seemingly much earlier than both the files and the .htm: the reference is last modified file which is 8/5/94 1.00.21 (Build 507) The version found by Petr in IEAK3.2 is 1.00.0540 (02/01/96). It contains at least one reference to Quantum, as there is embedded in it an error message: "Quantum Compression Level not in range (%1..%2)". The version found by submix8c is 1.00.0530 (03/29/95). And it contains the SAME error message. The .htm document I found is dated July 10, 1996 and misses ANY reference to Quantum. Without knowing in advance that also Quantim is supported, the "CompressionType" part becomes seemingly senseless: An option with just one value to chose from ...and there is no reference to two seithces that are in the .txt: Compressionlevel and Compressionmemory (the latter probably not being anymore a problem ) The pseudo-code is nice : I am pretty much sure (knowing how the good MS guys tend to re-use code) that some info can be still gathered (by an actual C programmer) from the actual FCI and FDI sources inside the (MAKECAB related) cabinet SDK: http://yumsn98.spaces.live.com/blog/cns!7A1111C0D6CB4DC4!172.entry Actual file courtesy of the Wayback Machine: http://web.archive.org/web/*/http://download.microsoft.com/download/platformsdk/cab/2.0/w98nt42kmexp/en-us/cabsdk.exe the FCI.H (online here): http://yumsn98.spaces.live.com/blog/cns!7A1111C0D6CB4DC4!178.entry and FDI.H (online here): http://yumsn98.spaces.live.com/blog/cns!7A1111C0D6CB4DC4!179.entry are seemingly explicit enough. The actual docs: http://msdn.microsoft.com/ja-jp/library/bb417343.aspx only talk of MSZIP and LZX. jaclaz

What about Offline Sysprep? http://www.911cd.net/forums//index.php?showforum=43 (and/or just the two available injectors): http://www.911cd.net/forums//index.php?showtopic=22523 http://www.911cd.net/forums//index.php?showtopic=22313 jaclaz

Yes, NEVER edit a bootable .iso. If you are into experimenting, you can try the pesort approach and you can probably shave a few (several) seconds at boot time: http://www.911cd.net/forums//index.php?showtopic=6869 OT I don't recall anyone publishing or testing a list for "normal" install, but maybe the same increase of speed can be achieved. jaclaz

NO. READ the read-me-first: jaclaz

OW, comeon: Attached. Great find, BTW. BTW, with the "right" keywords, it seems like ther is also: http://www.freewarehof.org/hof.txt I have no idea where to find it, the date seems "the same", but the size is much smaller. jaclaz MCABIN10.ZIP

@ilko_t If, for any reason, you don't do your computer properly seated on a chair , please do take one and seat comfortably on it before accessing this : http://downloadcenter.mcafee.com/products/tools/foundstone/ Directory on McAfee site where free tools are available. I was there getting a fresh copy of the excellent BinText utility (BinText303.zip) today, and noticed file (near the bottom of the list/page): warning.txt I had a look at it: Their Anti-virus detected a packer inside their own file! ...and obviously did NOT delete it as file SharePointDiscovery.exe has the same timestamp 21-Oct-2010 09:04 of warning.txt ... jaclaz

It depends "how" you image the computer. If the Disk Signature changes, any "non-standard" drive letter assighed is lost and a "defult drive letter" enumerating is applied. Of course you can manually attribute a Disk Signature and "fix" MountedDevices hive contents in the Registry. Open, when booted from the "original", with the "right" X: assigned, HKEY_LOCAL_MACHINE\SYSTEM\MountedDevices and save it's contents as .reg file. Open when booted from the "restored", with the "X: reassiggned to D:", HKEY_LOCAL_MACHINE\SYSTEM\MountedDevices and save it's contents as .reg file. Compare the two .reg's. jaclaz

The files are seemingly "right", their content unfortunately isn't. This means that the info in the MBR is completely "nuts". Try getting Dmde and analyze the image: http://softdm.com/ jaclaz

And indeed, without ALSO the MBR and DISK SIGNATURE you won't be able to boot the restored "backup" easily. jaclaz

If I understood you right, you are looking for something that will compare "newly added" files to a list of "old files" MD5 list? But how would the "newly added" files be actually "added"? I mean, maybe you need also another function (or two) like a "folder watching" utility and/or a "file adding" one. Which kind of files are we talking about? I mean big sized like - say - videos or smallish like - say - batch and text files? The performance of an OS with a folder with thousands of files may be slowed down considerably when using a file manager like Explorer. Something like this: http://www.datamystic.com/filewatcher.html http://leelusoft.blogspot.com/2010/07/watch-4-folder-22.html Which could "trigger" a batch or whatever that: calculates the MD5 checksum for the new files only and compares them one by one to the saved list of MD5 for the "old" files then IF match deletes the "new" file IF no match doesn't do anything jaclaz

Remember that DriveImageXML images drives , NOT disks! JFYI: http://www.911cd.net/forums//index.php?showtopic=22984 A number of tools you can use: If I were you right now I would try ODIN: http://odin-win.sourceforge.net/ or Clonedisk: http://erwan.l.free.fr/clonedisk/ Good ol' Selfimage did work allright, though: http://www.softpedia.com/get/System/Back-Up-and-Recovery/SelfImage.shtml If you want to use ImageX, you might probably want to read this thread: http://www.911cd.net/forums//index.php?showtopic=19355 Particularly the part about the "queer" license ImageX has (or maybe had at the time ) http://www.911cd.net/forums//index.php?showtopic=19355&st=132 jaclaz

You are missing the important bit. The general idea with datarescuedd is to make partial images. When you hit a bad spot, you "jump" over it, skipping a reasonable" number of sectors. If the skip is not enough, you try skipping some more. Once you have reached disk's end, you re-try the skipped areas backwards. You may still have "holes" in the image, but if a sector is "bad" it is "bad" at least without specialized hardware and "lower level" tools. You can fill this "holes" with empty sectors and finally have an image from which *some* data can hopefully be recovered. Just get what you can, without "insisting" on bad spots. "Something", though worse than "everything", is still MUCH better than "nothing". jaclaz

Not at all. Anything is interesting. As long as you: do not "publish" non-redistributable MS (or other third party) code/binary files your tutorial/illustrative document does not contain "cracks" or ways to circumvent activation, proper licensing, etc. it is allright (and much appreciated) to share it. (here or elsewhere) jaclaz

If the bearing/motor is stuck, the only things possible to attempt are: open the drive (in a "clean room" or similar) and attempt UNstucking the bearing manually open the drive (in a "clean room" or similar) and attempt transplanting the platters on another working drives BOTH require (besides some "special" tools/environment) a VERY good experience in the specific tasks. To unstuck a bearing a certain force is needed, like: good : http://forum.hddguru.com/hard-drive-bearing-motor-tool-t11827.html bad : http://forum.hddguru.com/barracuda-7200-fell-plates-won-spin-t7040.html mind you there is NO guarantee whatsoever that the UNstuck bearing will still allow the platters to rotate properly (centered, smoothly, etc.) but it is still far easier than doing a platter transplant and it is worth anyway an attempt. jaclaz

WHY? I mean, I don't have any use for the "other" (main, boot, working) drive. The "right" files for the drive should be only: image[0-51200].dd MBR_HardDisk1.dat BootSector_DriveF.dat BootSector_DriveG.dat BootSector_DriveH.dat Ther is nothing actually wrong in the MBR_HardDisk1.dat (same contents of image[0-51200].dd) exception made for the extended partition marked 05 (CHS mapped) instead of 0F (LBA mapped). I don't believe TESTdisk can have the output you posted, unless the problem is in the actual EPBR's. First partition (what becomes "F:") is from LBA 63 for 41913522 up to 41913585 First EPBR is at LBA 41913585 Second partition (first volume inside Extended, what becomes "G:") has a "strange" sectors before of 65. Third partition (second volume inside Extended, what becomes "H:") has "standard" sectors before of 63. BOTH volumes inside extended have "crazy" values for $MFT and $MFT mirror placement. Let's have a look at the actual EPBR's. IF the data in the sectors you posted is correct you have: the extended partition from sector LBA 41913585 for 153452880 i.e. 78,567,874,560 bytes Inside it you should have (unless I am mistaken): 63 hidden sectors for the first EPBR 89,755,088 sectors for the G: NTFS filesystem (45,954,605,056 bytes) 1 exceeding sector for PBR mirror 63 hidden sectors for the second EPBR 63,697,656 sectors for the H: NTFS filesystem (32,613,199,872 bytes) 1 exceeding sector for PBR mirror Values #2 and #5 don't make much sense as they don't respect 255/63 geometry. Let's try with three more files - hoping we'll get the actual EPBR's and the PBR mirrors: Start at sector 41,913,580 for 100 sectors Start at sector 131,668,730 for 100 sectors Start at sector 195,366,365 for 100 sectors jaclaz

I don't know what's happening. Maybe the image itself has some corrupted data? Anyway, do the following: re-attach the drive to a Xp machine in a USB enclosure run HDhacker: http://dimio.altervista.org/eng/ you want to save: the MBR or first sector of PhysicalDrive (the PC inner hard disk is \\.\PhysicalDrive0, if you don't have other HD's the USB attached one will be PhysicalDrive1) the PBR or first sector of each and every partition you can see (LogicalDrives) Additionally, run again Drdd. You want to save the initial part of the hard disk, starting from (if the drive was partitined under 2K/XP) sector 0 to sector 100 or (if the drive was partitioned under Vista or 7) from sector 0 to sector 2100. (sectors NOT megabytes) Compress all the resulting files into a .zip archive and either attach the resulting archive to yur next post or upload them simewhere and post a link. jaclaz

Are you implying that Italians do it better? Sure, that's a known fact. jaclaz

... taking the generic - actually Linux derived - example given on diddy's guide and assuming that it will be the "right" syntax for a PE 1.x .... The good news are that you are not the first one to do so: http://reboot.pro/9696/ http://reboot.pro/9696/page__hl__mkisofs__st__26 jaclaz

Just for the record Diamond.exe OFF-TOPIC posts/thread: Quantum compressor (pre-MS) here: ftp://ftp.sac.sk/pub/sac/pack/quant097.zip jaclaz

You can most probably get/rebuild a valid \I386\ source, but it is a "manual" operation and a lengthy/cumbersome one. Generally speaking those images ALSO have a \I386\ directory, but cannot say if this is your case. Have a look here (and links within): jaclaz

Of course they exist. Problem might be if you gonna like their price (examples): http://www.iogear.com/product/GUW2015VKIT/ http://www.ramelectronics.net/wireless/wireless-hdmi/wireless-pc-to-hdtv-adapter-usb-av2010/prodUSBAV2010.html http://www.ramelectronics.net/computer-parts/computer-cables/monitor-cables/wireless-display-extension/gefen-gtv-wvga-sr/prodGTVWVGASR.html http://www.ramelectronics.net/wireless/wireless-vga/gefen-gtv-wvga-lr/prodGTVWVGALR.html It must be really hard to live with a broken google.... Above links found in under 5 miutes time googling for "VGA wireless".... jaclaz

It seems like you have a well garbled MBR DATA. What happens with "Quick Search", and if still "meaningless data is found", with "Deeper Search"? jaclaz

You are welcome. If you have access to some tool capable of moving/resizing partitions you can (partially) fix the current situation. What you can do is to resize the second partition to respect cylinder boundary. What I think you cannot do "plainly" with those tools is to have the second partition as first (as it should be). <- but this is a "minor" deviation from "standard" I want to ressure you, if all it is required by that netbook is to do some e-mails, navigate the internet and more generally "used normally", the current setup won't create any problem. If you are going to "play" with it using on it partitioning tools, installing other Operating Systems and the like, there is a concrete possibility that this non-standard situation may "trick" some program into doing something "non appropriate" (which I presume it is what happened to the XP install when it formatted the disk - keeping the previous partitioning scheme and creating the "wrong" Sectors Before value in the bootsector/PBR). If the "E:\" volume doesn't contain DATA (or - as you should) you have a backup of the data, the procedure would be: delete the "E:\" volume and Extended partition containing it move the "C:\" primary to the beginning of the disk resize it to respect cylinder boundaries recreate an Extended partition in the rest of the disk recreate the "E:\" volume inside the Extrended partition restore (if any) the data to the E:\ volume If you are "home" user, there are a few such tools freely available, examples: http://www.partition-tool.com/easeus-partition-manager/comparison.html http://www.paragon-software.com/home/pm-express/ Point is that most probably they won't resize/move the actual system volume from which they are run, so you will need something like a PE running them from USB. I have not experience with this kind of tools as I tend to do my partitioning by hand and never resize/move partitions, maybe there are some other available programs capable of doing the changes that are more easily bootable from USB, first thing that comes to my mind is parted Magic: http://partedmagic.com/doku.php creating a USB key with it through Unetbootin: http://unetbootin.sourceforge.net/ should be a breeze. jaclaz

I am not at all familiar with the Seagate tools, they may or may not be able to re-create the G-list. (and I have no idea idf this will work without "low--level" formatting the HD BTW "low-level" formatting doesn't exist anymore, at the most is "intermediate level" formatting) 176000 bad blocks in a row is well beyond "normal". This kind of problem is often due to a head crash. As said, insisting on that area may make things worse. You can try changing the Partition ID in the MBR (as an example with MBRWIZ DOS: http://mbrwizard.com/download.php ) to an "unmountable" for windows partition ID, like - again as a example - ID 12, this way the mount manager should ignore the partition. (but we don't know if the "lock" or "freeze" in windows is connected with the actual "disk manager" or with "Mount manager" ). If this trick works, DatarescueDD should be able to access the physicaldrive allright. jaclaz