jaclaz

Usually on a notebook, there is somewhere printed in LARGE LETTERS the manufacturer's name and usually in small ones the actual model. You read this info, enter it in google and press the Search button. It is likely you will have access to datasheets where you can find out what kind of hard disk that particular notebook uses and possibly also to drivers for it. Usually this happens going to the manufacturer's site and accessing an area called "Support", sometimes with a sub-area called "Downloads". You can also (should you feel lucky ), try the "I'm feeling lucky" button... Example: http://tinyurl.com/3a7sxcw jaclaz

Open a command prompt. In it type: DIR /S E:>C:\mydirlist.txt (presuming that your "1 Tb" drive is E:\, this will produce a Directory listing on the volume in file C:\mydirlist.txt - change drive letters accrding to your setup) Compress mydirlist.txt into a .zip file and attach it to your next post. This way we have an exact view of the files you are using. Also, post some info on what you mean by "store b". jaclaz

Please read point #5 of the read-me-first (which you should have ALREADY read ): There are a few common misconceptions about hard disk drives. The first one is "they are reliable" (which is normally true) which is wrongly perceived as "they will never break" (which is UTTERLY false). An accurate statement is for this special case: ANY hard disk, from ANY manufacturer, of ANY series WILL break, sooner or later. The "general" point is if you are going to take your chances of losing your data WHEN it will break. The specific points are: we DO NOT actually know if the wrong log entry is the ONLY cause of the problem (anything posted officially by Seagate is either incomplete, misleading or simply false) we DO NOT actually know HOW to diagnose the problem (we think this problem can cause two different kind of errors, the LBA0 or the BSY one, but obviously it is b*ll**it, a single problem normally causes a single error - always the same - or a given series of errors - always the same, if you cross-reference this with the different boards, different firmwares and what not the result is "A suffusion of yellow") we DO NOT actually know if the fix is appropriate (what we know is that in the very large majority of hard disks showing the LBA0 or a BSY error, by performing a series of actions we are able to "unbrick" them, that's all, just like if your car stops and you change spark plugs and the battery and the carburetor and the coil and the gasoline in the tank and all the filters, and then you say "I fixed it" - without having the faintest idea WHAT was the cause and WHAT solved the problem) However, even assuming that the "cause" has been well diagnosed AND that the "fix" was the right one, the result is NOT a "failproof" drive, at the best is a drive AS reliable AS another of the same manufacturer/series, which, as said, tells you NOTHING about it's actual reliability. So, in the BEST hypothesis, you SHOULD NOT trust the fixed drive ANY better than you would another one, i.e. DO NOT TRUST it AT ALL. (of course if you care for your data) There is ONLY one way to keep data safe, and it is called REDUNDANCY, the three Golden Rules of Backup: Backup Backup again After considering the philosophy of the above two points, BACKUP AGAIN! jaclaz

Dear friend, I would presume that in almost two years the Original Poster has found a solution and/or is now using another OS. jaclaz

OK. (which means NOT OK ). Now try booting a DOS on that machine (any will do, like FreeDOS or a DOS 7.1 or 8.0), I have seen machines re-booting when the graphic card (windows driver) was initialized or soon after. jaclaz

Spike1, first thing: DON'T PANIC (assume the above to be written in large, friendly letters) The "caddy" you are talking about is a USB external enclosure, right? Usually you don't want to "format" a hard disk that you buy second hand, you want first to wipe it, to (re-) partition it, BEFORE attempting formatting it: it is very possible that the hard disk was partitioned/formatted with an incompatible kind of IPL/MBR or filesystem. You should also test it. There are different tools to perform the above, from XP easiest will probably be: Wipe: Roadkil's Disk Wipe: http://www.roadkil.net/program.php/P14/Disk%20Wipe Partition: XP Disk Manager Format: XP Disk Manager Test: Hard disk Manufacturer's Utility http://pcsupport.about.com/od/toolsofthetrade/tp/tophddiag.htm HDDscan: http://hddguru.com/ http://hddguru.com/software/2006.01.22-HDDScan/ jaclaz

Sure , I am NOT doubting in the least *your* need for 6.22 , I am doubting the actual *need* by HenriK of BOTH 6.22 AND a high amount of space . Just for the record AFAIK there are several ways to double boot 6.22 and 7.x, most notably MS own use of the renaming of boot files: http://www.mdgx.com/osr2.htm#2BOOT jaclaz

Please note that MS-DOS 6.22 has a number of limitations that DOS 7.x (i.e. the DOS that comes with Win9x systems) has not. If you use 7.x you can access natively FAT32 partitions, and have LBA available. There are very few reasons to use 6.22 instead of 7.x, but they can be set in a dual boot environment allright, and even if you actually *need* 6.22 for a few programs , you can use the 7.x for all the rest and have separate partitions. You can write the word "OLD" allright, together with white hairs we also get some tolerance to it. (but please DO NOT use the term "Vintage computing" ) I am unaware of any DOS 6.22 compatible ONLY program that will need such a big amount of space for data, remember the common size of hard disks in the last period of times when DOS 6.22/Win 3.1x were installed on PC's "in factory" (i.e. just before Windows 95) was 300Mb. I remember buying as "very last" DOS machines a few Compaq's that were advertised as having a 300 Mb HD but actualy had a 500 Mb one. A *very large* "consumer" hard disk at the time was the Quantum Fireball 1 GB. On "high end" machines (running NT 3.51 and later 4.0) I remember having large storeage in th eform of a set of a RAID with 3 2.1 GB hard disks! jaclaz

Only too happy of having contributed to another happy bunny: http://www.msfn.org/board/index.php?showtopic=128727&st=10 jaclaz

This one seems like the "real" thing. The DATA in it appears correct, it has a first partition which is the right size and offset as the bootsector and a second Hidden partition that is "normal" if you used RMPREPUSB with the the "Boot as HDD (C: 2 ptns)", CODE seems like some version of GRUB or grub4dos. The "Missing MBR helper" comes from it. If it's a grub4dos MBR, it will look for file grldr in root of the partitions. If there isn't any such file, the message will be printed to screen. Would it be possible that after the formatting by RMPREPUSB (which if you chose "XP/BartPE bootable (NTLDR)" should have written a "normal" Win2K/XP/2003 MBR) somehow the install on it of grub4dos (by WinsetupfromUSB) failed? Or that some other GRUB/grub4dos installing program was run on the stick? (It doesn't look like the grub4dos MBR that winsetupfromUSB uses AFAIK) What I would do if I were you is the following: get MBRFIX: http://www.sysint.no/nedlasting/mbrfix.htm http://www.sysint.no/products/Download/tabid/536/language/en-US/Default.aspx open a command prompt, and in it run: (the correct <num> shoud be 2 if your last posted file is named "correctly") then copy to the stick: NTLDR (you can copy it from your working XP) NTDETECT.COM BOOT.INI (as well you can copy it from your working XP, BUT it needs to have at least TWO entries in it, a suitable one to copy and paste is here: http://diddy.boot-land.net/grub4dos/files/install_windows.htm#windows1 ) [*] try to boot from the stick, if you can see the two choices, it means that now the stick is OK [*] if it is OK, you can try running again WinsetupfromUSB, and see if it recognizes the USB stick without need to repartition/reformatting it jaclaz

I think you got the "wrong" disk. If you created the MBR from hard disk 0, that is the FIRST hard disk, i.e. the one you booted from, and thus you can boot from the stick allright . Seriously, the MBR is of a device that has a NTFS formatted Primary Partition 20,974,431,744 bytes in size and an Extended one 99,048,821,760 in size, that all in all looks like a 120 Gb hard disk. The bootsector is probably correct, as it is that of a NTFS partition 8,011,389,952 bytes in size, that looks like possible for an 8 Gb stick. jaclaz

Here: http://www.threatexpert.com/reports.aspx?find=xeaoqlbtssd&x=8&y=6 http://www.threatexpert.com/report.aspx?md5=233f69aa26bdf7d9ecff0d9e2464170b http://www.threatexpert.com/threats/packed-win32-krap-ai.html Though cannot say what it means, nor where it may have come from. jaclaz

Actually it is quite common (IF it is what I think ): too much power drawn from the PSU (which translates into a bad PSU) Try with another PSU, first thing. jaclaz

Cannot say about the "wimcopyfile.exe failed" That's not a problem. Simply change: to: or remove the two lines (they were just a check): i.e.this is the "semi-final" version: and once you have it woreking you can remove also the red PAUSE's. The "command is not recognized as a in- external command", as now said for the 3rd (THIRD) time is because the executable named "bcdboot.exe" is NOT found in the current directory NOR in the current PATH. You need to EITHER: add the path where "bcdboot.exe" is to the PATH variable copy the "bcdboot.exe" in the working directory of the batch change the batch to include the FULL path to the "bcdboot.exe" file. something like: \\server\reminst\images\windows7\bcdboot.exe D:\Windows or: D:\Windows\system32\bcdboot.exe D:\Windows Remember that the general idea is to help you learning how to write your own batches, not that of writing them for you, you need some patience and trial and error, but you also need some time to try understanding WHAT the batch commands do and introduce your own checks. jaclaz

Only to happy to hear there is another happy bunny in the basket : http://www.msfn.org/board/index.php?showtopic=128727&st=10 jaclaz

Add a 5th PAUSE statement right after the bootbcd command: and post the actual error you get. jaclaz

Hmmm, not really: I see now what the problem is. What I posted originally: What you actually wrote: Try again, COPY and PASTE: The "bcdboot.exe not recognized" is another problem, most probably you have to supply the full path to the bcdboot.exe file. jaclaz

Well, you linked to page #2, the actual interesting thing is on page #1: http://www.nytimes.com/2010/06/29/technology/29dell.html?pagewanted=1&ref=technology Here is a snippet of the leaked source of the program that created the failure : jaclaz

As said, try REMming out the checks AND add a PAUSE: and post what happens. jaclaz

Whatever it was, it happened more than one year ago: jaclaz

No matter what your question is , a good question is : can you provide EXACT data about the hardware you are using? It is very possible that some member can find the appropriate driver for your board SATA controller. As well it is very possible that your board BIOS can be set into "Ide emulation mode" or equivalent and then you won't need the driver during install. jaclaz

Ok, then power it at 3÷3.3V, if it is this "RS232 SMD shifter": http://www.sparkfun.com/commerce/product_info.php?products_id=449 jaclaz

Yep. Just for the record, this is the post where I already posted this kind of considerations: Only hypothesis, of course. This: http://digital.ni.com/public.nsf/3efedde4322fef19862567740067f3cc/2708a51f9c861e6c8625681000648c4a seems however to confirm the general idea: jaclaz

There are a few ideas/schemes here: MAX232 based: http://users.picbasic.org/Howto/TTL-RS232/ttl.htm http://www.seattlerobotics.org/encoder/aug97/cable.html Poorman's solutions: http://www.uchobby.com/index.php/2007/06/11/ttl-to-rs232-adaptor-explained/ http://freecircuitdiagram.com/2009/03/27/simple-ttl-rs232-level-converter-using-transistor/ http://www.cypress.com/?docID=2209 It would be much easier to use a "Nokia" cable, that you should be able to find, provided it is the "right" kind. Besides the present thread, here are nice info on the various cables available: http://buffalo.nas-central.org/index.php/Use_a_Nokia_Serial_Cable_on_an_ARM9_Linkstation Also you can make a FBUS Nokia cable: http://www.panuworld.net/nuukiaworld/hardware/cables/index.htm http://www.panuworld.net/nuukiaworld/hardware/cables/basics.htm http://www.panuworld.net/nuukiaworld/hardware/cables/old.htm http://www.panuworld.net/nuukiaworld/hardware/cables/fbus.htm http://www.nomad.ee/micros/nokiacable.html As said before, your mileage may vary: jaclaz

No prob , but then forget anything I wrote about the actual Rs232 shifter SMD, since you are NOT using one. jaclaz