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

Really I cannot understand what is the difficult part in this. As said n times this Sparkfun thingy is a peculiar board with a peculiar behaviour. Another board (including yours) may behave in a completely different way, but this one, from the posted reports, behaves EXACTLY as advertised. And again with all due respect, you are missing some logic. Let's see, we are now talking of your self built interface: You have in the above THREE statements: MAX232 powered with +5V: MAX232 transmits @5V HDD transmits @3.3V #1 is a "real" statement, as I preeume you know what you power your interface with #2 is EITHER an assumption OR you measured the signal on the board TX wire #3 is - by your own words - an assumption based on your trust in what I said Now, logic tells that if I say two things, you cannot trust my word for only one of the two, you have to choose if EITHER believe BOTH or NONE, i.e. I'm EITHER reliable or I am NOT. On the other hand the same logic says that if you actually measured the signal on the board TX wire (and thus #2 is NOT an assumption) you have the means (oscilloscope or signal analyzer) to measure the signal levels, if it is so , you can well measure the signal on the HD TX pin and thus need not to trust me, and need not to assume #3. I have NOT the faintest idea at what level works what, I simply draw sums out of data. From this, which remains probably the only thing I can understand : http://www.interfacebus.com/voltage_threshold.html A "proper" TTL (@3.3V) will understand a signal at anything over 3.3 V as "a suffusion of yellow". It is possible that the whatever is on the stoopid seagate disk understands something more than this let's say 4V and your particular interface sends data at a lower level than the maximum 4.7 V that the (@5V) TTL/CMOS allows, say 3.99999 whilst the Sparkfun thingy, if powered at 5 V actually sends signals at 4.6999999 V. Or it is possible that for any reason your interface actually produces 3.3V level signals and thus works allright. Without actual measurement of signals of BOTH your circuit and of a sample of the Sparkfun thingy it's hard to say. UPDATE: After all maridadi is NOT using the RS232 SMD shifter, but rather a Prolific USB to TTL adapter: jaclaz

Why? Loop-back #1 has a (5v) signal exiting a (5v) board and looping back, thus entering a board capable of understanding a (5v) signal. OR: Loop-back #2 has a (3.3v) signal exiting a (3.3V) board and looping back, thus entering a board capable of understanding a (3.3v) Nothing strange. In loop-back test: Board transmits @5v->loop-back connection->loop-back connection->Board understands @5v OK Board transmits @3.3v->loop-back connection->loop-back connection->Board understands @3.3V OK In real life: Board transmit @5v->hard disk DOESN'T understand @5V->a suffusion of yellow -/- Hard disk trasmits @3.3V->Board DOESN'T understand @3.3v-> a suffusion of yellow NOT OK Board transmits @3.3v->hard disk understands @3.3V->hard disk transmits @3.3V->Board understands #3.3V OK After all this is called TTL where the L is for "Logic" . jaclaz

Just to avoid further misunderstanding , this: Actually means: The GND of the shifter to BOTH the GND of the harddrive AND the black wire (ground) of the power source (be it a 3V battery or wires coming from a power supply, Orange +3,3V and Black 0V or ground) Please review point #7 of the read-me-first jaclaz

But, did you use the 5V with your home made (officially "super-deluxe" ) thingy: or with this specific board "Shifter" from Sparkfun?: http://www.sparkfun.com/commerce/product_info.php?products_id=449 Maybe the$#!Za. (at least from the name he could be) is an undercover agent form SPECTRE attempting to upset world order by underpowering the stoopid shifter : and, later: Let's see if I can clear it. There are two different "TLL" levels standard, a "5V" and a a "3.3V" (sometimes called "2.8V") one. http://www.interfacebus.com/voltage_threshold.html The hard disk "wants" or "likes" the 3.3V ones. A converter can be: powered at 5V and output a 5V TTL level signals <-this WON'T work powered at 2.8V÷3.3 and output 3.3/2.8V TTL level signals <-this WILL work powered at 5V and ouput 3.3/2.8V TTL level signals, or more generally powered at ANY voltage and output a 3.3/2.8V TTL level signals<-this WILL work powered at 5V and ouput BOTH 5V and 3.3/2.8V TTL level signals, or more generally powered at ANY voltage and output BOTH 5V and 3.3/2.8V TTL level signals<-this WILL work if the HD is connected to the "right" TX/RX" of the converter That particular converter you used/got "autoswitches" output TTL level based on the voltage it is powered with. In other words it has an "advanced" feature that turned out as a problem in your case. With all due respect for your "deluxe thingy", it is perfectly possible that it works at 5V, or even at 4/9*SQ(PI) , but I presume that the Sparkfun board being an industrial product, ALL single boards of this model behave the same and "as advertised". Right now we have: Gradius2 (you know the peep you initially thanked as his guide saved your a**) using this adapter with a 3V battery Brad Garcia (you know, one of the other peeps that mostly contributed to save a**es around) using a plain adapter with a 3.3V supply (orange cable) the$#!Za. reporting specifically that this adapter did NOT work for him when powered at 5V BUT the same (this) worked when powered at 3.3V Everyone remains of course perfectly free to draw his/her conclusions, and either act accordingly or supply any voltage into any TTL converter, actual results may vary , but I won't buy that this adapter will ever work if powered at 5V. jaclaz

VideoRipper might have been a bit too laconic. I am pretty sure he meant without anything, but with the "shifter SMD" actually powered. Or is it supposed to get 3.3 V (NOT 5V) from thin air? Please note that theoretically the loopback test carried with: NO POWER -> will fail +5V -> will (hopefully) succeed BUT won't work with the hard disk +3.3V -> will (hopefully) succeed, AND will (hopefully) work with the hard disk Anyway, I give up, I see it's of no use. jaclaz

The shifter SMD NEEDS to be powered at 3.3 V, as I already pointed out to you on the "main thread", here: AND also (I hope clearly) stated on the read-me-first, point #11: WHAT is the difficult part in it? WHY starting a new thread? jaclaz

@lesmond74 Just for the record the given link is OK: http://web.archive.org/web/*/http://www.v72735.f2s.com/LetAssig/ It leads to a page on which you can choose between several snapshots of the page, just click on last one: http://web.archive.org/web/20080619125702/http://www.v72735.f2s.com/LetAssig/ and see if the file is available (it is ): http://web.archive.org/web/20080401085803/http://www.v72735.f2s.com/LetAssig/LetAssig.zip or try earlier snapshots. To disambiguate possible mis-reporting of the actual "placement" of the partitions, though it seems like clear enough, and you should wait for rloew's patch, can you in the meantime get from here grub4dos: http://nufans.net/grub4dos/ http://nufans.net/grub4dos/current_release/ http://nufans.net/grub4dos/current_release/grub4dos-0.4.4-2009-10-16.zip From the zip get just grub.exe, boot to plain DOS and run it. At the grub prompt issue command: geometry (hd0) [ENTER] and confirm that the output corresponds to: (hd0,0) C:\ - Win98 SE, FAT32, 25GB, Primary (hd0,1) F:\ - Win XP, FAT32, 15GB, Primary (hd0,2) Linux, Ext3, 10GB, Primary Extended partition containing the following logical volumes - (hd0,4) Linux, Swap, 512MB (hd0,5) Linux, Ext3, 35GB (hd0,6) E:\ - FAT32, 25GB @dencorso The dlmanip page is online : http://sta.c64.org/dlmanip.html no need in this case for the wayback machine... jaclaz

I have nothing much to add to what I wrote in points #6 and #7 of the read-me-first, but I can add the following data collection from a statistical viewpoint. (actual data for the "those that did NOT use ground is obviously faked , but anyway representative of actual values ): Group A (those that did connect properly the ground): Percentage of success 100% Problems with connection 0% Whining about the guide/tutorial 0% Group B (those that did NOT connect properly the ground): Percentage of success 56.65% Problems with connection 34,35% (of which solved by connecting ground 99.99% +/- 0.01%) Whining about the guide/tutorials 34,35% In other words, we have NO reports of people having problems with the ground connection, and a significative number of reports about people that had problems with the connection that were INVARIABLY solved once ground connection was established. Since you have that connector available, and there is NO evidence that it creates a problem, why NOT connecting it? Or, let's put it in yet another way, try without the ground connected, if it works, good , if it doesn't try again after connecting the ground, and hope that the problem was just the ground . Grounding is, as said STRONGLY advised, which doesn't mean that is COMPULSORY, not that the stoopid hard disk cannot be revived without a ground connection, it simply means that if I were you I would connect the ground too, with a total surcharge in costs of 0.00 US$ AND no harm done to any living being in the making of. jaclaz

You never had any issues with it integrating something into NT 4.00? http://www.nliteos.com/nlite.html Integrating NT 4.00 Service Packs is: NOT possible with nlite NOT possible (actually possible but NOT "easy") Here : http://www.msfn.org/board/index.php?showtopic=109439 jaclaz