jaclaz

The ST2000dl003 is NOT a 7200.11. IF it suffers from the same kind of problems, this is the only resource I know of (and links within it): jaclaz

Maybe a floppy image on a CD or on a USB stick might have been a more suited suggestion jaclaz

Hmm. You need to upload the images on a free image hosting website, NOT Imageshack as it seemingly has some limitations, and then post the links to the hosted pictures, and obviously NOT the path to the picture on your hard disk. jaclaz

START A NEW thread, please. Here: http://www.msfn.org/board/forum/169-hard-drive-and-removable-media-issues/ Title it "Folders 0 byte s in size" jaclaz

Not at all my field, but wouldn't PuTTY do? http://www.chiark.greenend.org.uk/~sgtatham/putty/ jaclaz

yes i do have it , it's connector #1 ! AND #2 AND #3. Look, it's not difficult, if the actual CD/DVD has "protruding pins" it is non-standard (and possibly "type #1" will fit them), if it has connectors on the "outer edge" ALL among #1, #2 and #3 will do, as said they are ALL the same thing. jaclaz

I now see what you mean , type #1 seems like a "dual" kind of connector (with internal sockets for "pins" just like the ones used on 2.5" HDD) whilst #2 is ONLY a "slim ATAPI" one (i.e. the contacts are on the "outer edge"). ALL slimline drives I ever saw use these "outer edge connectors", compare with: http://www.laptopparts101.com/cd-dvd-optical-drive/ But you have on your hands the actual CD/DVD drive, don't you? The connector is actually called also "50 pin JAE" or "ATAPI-50" or "ATAPI JAE". http://www.hardwareanalysis.com/content/image/10312/ The actual "code" should be: "JAE KX15-50ELD1L" http://jae-connector.com/en/general_en.cfm?l_code=EN&series_code=KX14/KX15 http://jae-connector.com/en/pdf/2008-35-36-KX1415.pdf Example drive (page 13): http://www.prince-tech.com.tw/Eng/Pic/PicNdfUVp_66201.pdf jaclaz

Are you joking or what? Items #1 and #2 are the SAME thing (only difference is that one comes with a USB Y cable and one doesn't). Item #3 is STILL the SAME thing, only, being for a SUPER-Slim drive, the actual PCB is 10 mm in height instead of 13.5 mm. The use of ANY of the above in conjunction with a slim-line drive is allright. The only thing you need to check is power requirement, remember that a single USB port maxes out at 500 mA. What you should get would be INSTEAD of the connector, an actual external case for slimline drives (examples): http://www.amazon.co.uk/StarTech-com-Slimline-Optical-Drive-Enclosure/dp/B003GSCS2G http://www.walmart.com/ip/Startech-USB-to-Slimline-SATA-CD-DVD-Optical-Drive-Enclosure-SLMSOPTB/14860262 http://www.amazon.com/External-Enclosure-Laptop-Notebook-Connector/dp/B0011TR71Y Poorman's DYI: http://www.instructables.com/id/DIY-USB-Slimline-Optical-Drive-Enclosure/ Rest assured that the actual slim IDE connector is standard. jaclaz

If I were you I would rather check for available solutions, first : http://www.rlmueller.net/freecode4.htm jaclaz

If you can see the folders (but not the files in them) you ARE NOT suffering from LBA0. (and you won't find ANYTHING useful in this thread, please start a new one (DO NOT post here on this thread, start a NEW thread) with an actual EXACT description of the actions taken, current status, etc. Keep in mind these: http://homepages.tesco.net/J.deBoynePollard/FGA/problem-report-standard-litany.html http://homepage.ntlworld.com./jonathan.deboynepollard/FGA/put-down-the-chocolate-covered-banana.html as a general guideline. In any case, should it have been a LBA0, yes, you would have had to "dirty your hands" and "have to take the whole segeant apart hook up all the wires and put it back together", do you really think that if it was fixable without specific hardware, and by simply running a few lines in hyperterminal we would instead be suggesting the actual (complex) procedure as we do? jaclaz

You are welcome. "random USB images" reminds me of "any .ISO" : TANSTAAFL! http://reboot.pro/8944/ Start by making a plan. Post it in an understandable manner (and NO, "a bootable Windows 7 image with an Acronis recovery image (True Image and Disk Director)" is NOT a description that anyone not being you or failing to have handy a finely tuned crystal ball can understand). Then you will likely be pointed to things to study and experiments to carry (in other words do not expect anyone is going to do your homework, if you want to do simpe things, it is simple to learn how to do them, if you want to do complex things, it will be complex to learn how to do them). jaclaz

JFYI: http://reboot.pro/14258/ http://reboot.pro/14258/page__st__7 Here: http://sites.google.com/site/rmprepusb/ jaclaz

If I may, let's not (yet again) confuse two DIFFERENT things Backing up is one thing and Imaging is another, each has it's advantages and disadvantages. There is a dedicated thread to imaging solutions available: a number of those will also run from DOS or Windows 9x/Me. As dencorso said, if you want to image, you DO NOT run the tool from the booted system, but from "something else", so you have NOT the limit of it needing to run on Win9x/Me, and there are several Linux based solutions. For Backup (NOT imaging) the now discontinued SAMEDIR: http://www.nonags.com/freeware-samedir_529.html http://replay.waybackmachine.org/20070807003907/http://samedir.sbn.bz/ is in my experience a very handy solution jaclaz

Well, you can still READ the thread and maybe you will find liks to OTHER more modern ways/approaches, like, you know: jaclaz

I thought you could only have that as an update to "Windows Millennium Enterprise" jaclaz

If really only 5% was wiped it means roughly 5% of 500 Gb = 25 Gb This (if the drive was a "single BIG partition) means that no useful filesystem data can be retrieved. BUT of course file based recovery would work allright. If the drive had been recently and thoroughfully defragged, the probabilities of recovering a high percentage of the remaining 95% are pretty high. If the drive was heavily fragmented probabilities decrease dramatically (expecially if files were biggich, like .iso's or movies or large databases or large compressed archives) If the drive was multipartitioned, ANY partition starting after the 5% should be FULLY recoverable. Start a new thread, and we'll see what can be done. jaclaz

Now I see. The actual PB (Progress Bar) is NOT what you think (i.e. a "real" progress bar) . Batch processing is sequential, once you have started 7zip, "focus" or actual "execution" won't return to the batch backed Wizapp until 7zip finishes. To understand what PB does, imagine that you prepare 5 bitmaps of a progress bar: progress bar at 0% progress bar at 25% progress bar at 50% progress bar at 75% Progress bar at 100% Than you have code (pseudo-code, actually) like: SHOW bitmap #1 RUN a command Show bitmap #2 RUN a command Show bitmap #3 RUN a command Show bitmap #4 RUN a command Show bitmap #5 Now, replacing the "SHOW bitmap" with PB, you would have: Wizapp PB OPEN RUN a command Wizapp PB UPDATE 25 RUN a command Wizapp PB UPDATE 50 RUN a command Wizapp PB UPDATE 75 RUN a command Wizapp PB UPDATE 100 What you can do (at the most) in your case is: Wizapp PB OPEN 7z x def.7z -aoa -o"D:\" Wizapp PB UPDATE 100 (pretty much unuseful ) I hope you understand the issue. jaclaz

By pure chance I used it / use it: http://jaclaz.altervista.org/Projects/VDM/vdm.html BUT if you had posted a link to it's page might have helped. http://wizapp.sourceforge.net/ I cannot understand your question(s) can you try re-wording them more explicitly? jaclaz

Actually it llooks a lot like you want to switch between the two well before booting the PE (or the "full 7"). This is something that you can do with grub4dos (or a similar bootmanager). The place where to go is (on MSFN) here: http://www.msfn.org/board/forum/157-install-windows-from-usb/ Otherwise browse reboot.pro grub4dos Forum: http://reboot.pro/forum/66/ and/or the Windows 7 one: http://reboot.pro/forum/77/ Particularly check the tutorials on steve6375's site: http://sites.google.com/site/rmprepusb/ By "putting together" different things you should be able to reach your goal. This might also interest you : http://www.multibooters.co.uk/floppy.html jaclaz

No. But it is possible using grub4dos: http://reboot.pro/5041/ http://reboot.pro/5041/page__st__86 title BitDefender Rescue 2011 find --set-root --ignore-cd /BootZone/iso-files/LIVE_OS/bitdefender-rescue-cd.iso map /BootZone/iso-files/LIVE_OS/bitdefender-rescue-cd.iso (0xff) # try this map --mem /BootZone/iso-files/LIVE_OS/bitdefender-rescue-cd.iso (0xff) map --hook chainloader (0xff) Read the grub4dos Guide FIRST: http://reboot.pro/forum/66/ http://reboot.pro/5187/ http://diddy.boot-land.net/grub4dos/Grub4dos.htm Take your time understanding the basics, should you need help, please DO NOT post on the mentioned thread: http://reboot.pro/5041/ but start a new thread in the appropriate Forum: http://reboot.pro/forum/66/ jaclaz

Does it attempt to spin up when powered on (or DID it BEFORE you detached/insulated the PCB contacts)? If Yes, somehow you have a bad contact (or somehow managed to fry something, which IS a problem ). If No, your disk may suffer from a sticky bearing, which may be a far worse problem ): jaclaz

Did you "start fresh"? But yes, you need to use a DVD: http://www.raymond.cc/blog/archives/2008/03/02/how-to-make-a-cd-with-all-current-drivers-for-windows-xp/ The .iso should be created allright. Just insert a DVD instead of a CD when burning the .iso. jaclaz

Several things may be possible, examples: nlite integration not being suitable to "repair" install differences in "more relevant/earlier drivers" (like chipset or PCI bus drivers) that create the 0x0000007b at an "earlier" stage tha the actual "mass storage drivers" You might want to try adding the "whole" driverspacks: http://driverpacks.net/ and/or attempt an offline sysprep: http://www.911cd.net/forums//index.php?showforum=43 jaclaz

It could be almost anything, but basically you need first thing to get a BSOD, so that we know what the issue might be. If I get it right, you had a 0x0000007b BEFORE, but NOW your XP reboots without giving you the time to read which BSOD it is. You need to disable autoreboot, see here: http://reboot.pro/14142/ and post the BSOD STOP ERROR code, first thing. jaclaz

Maybe had you taken a few minutes reading the read-me first, you might have learned what the requirements are and how to find one of those USB to TTL or Serial to TTL cable and how to choose one: Additionally another five minutes on Board Rules might have lead you to read (among the others Rule #13): http://www.msfn.org/board/index.php?app=forums&module=extras&section=boardrules The main thread is CHOKING FULL of links to online resources where you can buy one ALREADY proved to be working: jaclaz