jaclaz

That is a glitch of the batch. I assumed that a ParentIdPrefix would always be 12 characters long, with a central part always 8 characters long, I see this is not the case with that one. I will find a way to "fix" the batch for this special case. jaclaz

Hmmm, strange. However one Windows 7 can co-live on the same primary partition as the (one or various) XP's. In other words: 1st partition one or more XP + 1 instance of 7 2nd partition "other" version of 7 64 bit version were having some problems, though. You may wait for a reply by ilko_t, he should be able to better clear the matter and help you specifically. Rest assured , your English is better than you think. jaclaz

Good. ... and how do you expect that setup can see the internal SATA drive without it's drivers? @asriphet Re-read, this time attentively, post #1 Please read "Multiple Vista" as "Multiple Vista or Windows 7". jaclaz

strarc (was "xcopynt" ) can also handle junctions, but I am failing to understand the "direct replacement" requisite, maybe it's not what you want: http://www.ltr-data.se/files/strarc.txt http://www.ltr-data.se/opencode.html jaclaz

It's not clear WHEN the internal hard disk is not seen. Try this: boot from the USB device and press "c" at the grub4dos choices. You will get to the grub4dos command prompt. Type in it find ( and press [TAB] key. You should see a (hd0) and a (hd1) devices. Has the source the drivers (SATA) for the internal hard disk integrated, right? jaclaz

You may try using a virtual floppy with grub4dos. You create the CD #2 to boot grub4dos, and put in it a floppy image with WINNT.SIF You map the floppy image with WINNT.SIF on it as (fd0). You boot from CD #1. Cannnot say how the two CD-ROM's will be seen, I don't have a machine handy with two of them, you may want to try with command line, to find which devices are seen by grub4dos at boot. Alternatively you can use just one CD adding to it the floppy image. Grub4dos guide: http://diddy.boot-land.net/grub4dos/Grub4dos.htm Forum: http://www.boot-land.net/forums/index.php?showforum=66 If the floppy needs to "remain" connected in protected mode, you will need a driver like firadisk, some hints are given here: http://www.msfn.org/board/2-t137714.html jaclaz

Waiter come taste this soup ..... http://www.imdb.com/title/tt0094898/crazycredits Aha. Aha! ... jaclaz P.S.: Attaching migrateinf2txt.cmd version ALPHA 003 It should now be much faster and able to parse also multi-device migrate.inf's, both in the "plain" format MkMigrateinf.cmd does and in the "complex" one MakeMigrateInf.exe create. Migrate2txt_003.zip

No, that one looks like being self-powered (from the USB port). Pin 1 of the USB is connected to both pins 4 and 20 of the IC. But surely you can ask them to make sure before buying. jaclaz

You can use IMDISK allright, there is a 64 bit version of it. http://www.ltr-data.se/opencode.html http://www.boot-land.net/forums/index.php?showforum=59 jaclaz

Maybe you should look here, also: http://www.911cd.net/forums//index.php?showtopic=22523 http://www.911cd.net/forums//index.php?showtopic=22313 jaclaz

Here is the point you are missing. You can properly format a USB stick ONLY AFTER the HP utility (or other utility) PARTITIONED it at least once. Quick guide: usually (read ALWAYS) sticks are ONLY formatted (NOT partitioned) as a superfloppy device usually (read ALWAYS) sticks are set as "Removable", thus Windows WON'T partition them once a MBR and a partition table is written to the stick by one of the utilities, Windows will read them and will allow formatting the Volume in the Partition table (as opposed as formatting the whole stick as superfloppy) jaclaz

Just to disambiguate. This Forum is "Install Windows from USB", as OPPOSED to "Run Windows from USB" or "Install Windows on USB". With all due respect , your report is not really news, the usboot.org is online since 2006 , we might ask ...Tim... but I guess that the method made USB booting XP for a few tens of thousands people, maybe hundreds of thousands. And as well, I doubt the "any" in this: How did you solve different HALs and different processors? You might be interested in this : http://www.boot-land.net/forums/index.php?showtopic=9227 jaclaz

You don't need to go through the code. I will rephrase once again Given this: WHAT DO YOU THINK the HP USB Disk Storage Format Tool V2.0.6 does? jaclaz

No, i'm just using the "MULTIBOOT_USB_10.cmd" with option (H) to format the whole stick and it boots fine. Well, then WHAT DO YOU THINK the "MULTIBOOT_USB_10.cmd" with option (H) does? jaclaz

There is an entire sub-forum about installing windows FROM USB device (including Windows 7): http://www.msfn.org/board/install-windows-usb-f157.html jaclaz

Where are you based? How much are you wanting to spend? Some results from a fresh search on e-bay: http://cgi.ebay.it/INTERFACCIA-USB-3V-TTL-...=item2c50e23ba9 http://cgi.ebay.ph/USB-To-TTL-Converter-AR...=item53dd53df4e http://cgi.ebay.com/ws/eBayISAPI.dll?ViewI...em=320393829874 http://cgi.ebay.it/Cavo-Seriale-USB-TTL-3-...=item1c0dc6fa62 http://cgi.ebay.com/USB-To-TTL-Converter-M...id=380170437518 http://cgi.ebay.co.uk/USB-to-TTL-serial-Co...=item4834ba47d9 Some various links: http://www.ftdichip.com/Products/EvaluationKits/TTL-232R.htm http://www.rs232-converters.com/single_usb...l_converter.htm http://deccanrobots.com/productdetails.asp?prid=29 http://www.pololu.com/catalog/product/391 http://www.acroname.com/robotics/parts/S22...L-INT-CONN.html http://spiffie.org/electronics/archives/ha...0Converter.html http://www.usbgear.com/computer_cable_deta...199%2C601%2C461 Please note that I do NOT personally endorse ANY of the products listed above, the above list is just an attempt to help you. ANY "USB to TTL" converter will work, most are based on the said MAX232 or on FTDI chips, but no matter which chip is used, a USB to TTL adapter will do. jaclaz

It seems like the SD card gets two Parent Id's. The Migrate.inf (rightly) gets 7&d7f206a&0. This ParentIdPrefix is "understood" by the "AsusEee" rightly, but evidently NOT by the "Acer5738". My guess is that it's something BIOS related. Or maybe the "Acer5738" uses a different way to enumerate devices. What happens, once the XP - one way or the other - is installed on the "Acer5738"? What ParentIdPrefix does the SD card gets on the "Acer5738" already running XP? Still the same 7&d7f206a&0 ? Use this "updated" batch: @ECHO OFF ::migrate2txt.cmd rudimental batch to extract ParentIdPrefix from migrate.inf file ::by jaclaz ALPHA 0.02 Release 7th November 2009 ::supports both "removable" and "fixed" devices SETLOCAL ENABLEDELAYEDEXPANSION SETLOCAL ENABLEEXTENSIONS SET TEXT= SET SOURCE=%1 IF %SOURCE%.==. SET SOURCE=%~dp0MIGRATE.INF&SET CLeanSource=MIGRATE.INF IF NOT defined CleanSource SET CLeanSource=%~nx1 IF /I NOT "%CLeanSource%"=="MIGRATE.INF" GOTO :MIA FOR /F "tokens=* delims=" %%A IN ('MORE %SOURCE%^|FIND ",00,"') DO ( SET UNICODE=%%A ) SET UNICODE ECHO. SET SPACESUNICODE=%UNICODE:,= % FOR %%? IN (%SPACESUNICODE%) DO ( IF NOT %%?.==00. ( CALL :bin2txt %%? SET /P Var=!s!<NUL SET TEXT=!TEXT!!s! ) ) CLS SET UNICODE ECHO. SET TEXT="%TEXT:@=&%" SET TEXT=%TEXT:§=?% SET BEGIN=%UNICODE:~0,8% IF NOT "%BEGIN%"=="5C,00,3F" GOTO :Fixed SET TEXT ECHO. SET Prefix="\??\STORAGE#RemovableMedia#" SET BEGIN=%TEXT:~0,28%" IF %BEGIN%==%Prefix% SET ParentIdPrefix="%TEXT:~28,11%" SET ParentIdPrefix&GOTO :EOF :Fixed SET DiskSignature="%UNICODE:~0,2%%UNICODE:~3,2%%UNICODE:~6,2%%UNICODE:~9,2%" SET DiskSignature ECHO (as seen in a hex editor viewing the MBR) GOTO :EOF :bin2txt Set s=%1 For %%A In ( 23# 26@ 2D- 300 311 322 333 344 355 366 377 388 399 3A: 3B; 3D= 3F§ 41A 42B 43C 44D 45E 46F 47G 48H 49I 4AJ 4BK 4CL 4DM 4EN 4FO 50P 51Q 52R 53S 54T 55U 56V 57W 58X 59Y 5AZ 5B[ 5C\ 5D] 5F_ 61a 62b 63c 64d 65e 66f 67g 68h 69i 6Aj 6Bk 6Cl 6Dm 6En 6Fo 70p 71q 72r 73s 74t 75u 76v 77w 78x 79y 7Az 7B{ 7D} ) Do Call :DoPairs %%A GOTO :EOF :DoPairs Set _=%1 Call Set s=%%s:%_:~0,2%=%_:~2,4%%% Goto :EOF :MIA ECHO File MIGRATE.INF not found! GOTO :EOF Is the SD card partitioned, right? If the "Acer5738" thinks that the SD card is a "Fixed" Hard Disk, INSTEAD of ParentIdPrefix it will use Disk Signature in the MBR to identify it. It costs nothing to try adding to MIGRATE.INF a mapping for the Disk Signature as "V:\" and see what happens. Read the thread that "started it all": http://www.911cd.net/forums//index.php?showtopic=19663 Add to MIGRATE.INF these lines: HKLM,"SYSTEM\MountedDevices","\DosDevices\V:",0x00030001,\ ww,xx,yy,zz,00,7E,00,00,00,00,00,00 Replacing the ww,xx,yy,zz values with the ones you can get by peeking with a hex/disk editor in the MBR or using a tool like MBRfix to read the SD card signature. jaclaz

Do you have a bootfix.bin file? jaclaz

Were you blindfolded when looking? To re-cap: the HD accepts TTL level signals a USB-to-TTL or a RS232-to-TTL or a USB-to-RS232 AND a RS232-to-TLL interface is what is needed there are commercially available (or it is remarkably simple to autobuild) such interfaces, this thread is FULL of links to various models Most cellular phones, including Nokia ones, are also programmed through a TTL level interface. Thus, if you ALREADY have one of those cellular phone cables around and you don't use it anymore, it costs you nothing to see if it works. Buying a new one is NOT advised because: you have to open it and while doing so there is a probability you will break it there are several types of these cables some work, some DO NOT, some have NOT the "right" drivers, and when you buy one of them there is no practical way to know if it's the "good" type besides, some of these cables get their power from the USB port, whilst some get it (if I may one of the stoopidest ideas I've ever seen in my life ) from the actual phone battery, so you have to connect an additional battery to replace the power normally drawn from the phone There are SEVERAL posts in this thread about this issue, most notably an illustrated one here: http://www.msfn.org/board/solution-seagate...-page-1756.html More generally, the various tutorial are to be used as a cooking recipe should be: if you are a professional cook, or you have some experience in the field, you can use the recipe as a base and change doses and ingredients and vary cooking time, result will probably be edible. if you are not expert at this, you should not change anything and do exactly as it is written in the recipe you chose. This said there are as well SEVERAL reports of success using various original and non-original CA-42, a couple examples: http://www.msfn.org/board/solution-seagate...-page-1805.html http://www.msfn.org/board/solution-seagate...-page-1833.html Common point is that due (generally speaking ) to the lack of experience of users, when there is a report of failure it is sometime difficult to say whether a given cable is the problem or it is the way the user connected it (or failed to connect it) or whatever. jaclaz

NO, he is saying that IF the problem is one of the two detailed and IF the APPROPRIATE equipment has been used following PROPERLY the instructions, it has worked in a few THOUSANDS of cases. Swapping boards CANNOT work, unless a far more difficult procedure is used (involving soldering and desoldering on the board) AND the boards are really identical. You: basically: bought a cable that is not the "best" advised solution, and possibly is also one of the NO GOOD ones either managed to break it or the thingy was DOA: "connecting the tx to the rx cable produces no echo in hyperterminal either" don't want to buy another cable This does not count as a report of the unbricking not working, as you have a DEAD cable/not working equipment. jaclaz

I would try to check what the Maxtor utilities have to say first thing, it could well be a dead drive, after all. You can find them (together with a bunch of HD tools) in UBCD: http://www.ultimatebootcd.com/ Then I would try the unlocking tool for oldish TiVo's: http://www.weaknees.com/maxtor_powermax.php Please do understand that the "locking mechanism" may not be the same for all DVR's, so unlocking it may work or fail, even if the drive is functional. jaclaz

Well, NOW you should see WHY: 1 problem=1 thread=1 method=1 solution (hopefully ) would have been faster and is advised. Happy this one is solved. jaclaz

Almost. You need only one "mkmigrateinfxx.cmd" either the one that is in the original topic or the latest version linked to. The small batch I posted should be called migrate2txt.cmd as in: (again to avoid confusion) If you copy the mkmigrateinf.cmd to the stick you do not need to specify the drive letter of the tick itself, otherwise (as an example if you put it in C:\batches\) you need to specify the USB stick drive letter. All the rest is OK. jaclaz

I do believe you, rest assured. PRELIMINARY STEPS: Open a drawer. Put inside the drawer the 2G stick AND the SD card. Close the drawer. Lock it. Put the drawer key in a self addressed envelope and send it via snail mail to yourself. The above are to avoid confusion. REAL STEPS : get latest mkmigrateinf.cmd http://www.msfn.org/board/index.php?act=at...st&id=27356 copy it somewhere insert the 8G stick (you should have not any other ones around) take note which drive letter it gets open a command prompt and run mkmigrateinf.cmd <driveletter_of_the_stick>, example: mkmigrateinf.cmd G: it should produce a migrate.inf file verify (using my batch or whatever) the ParentIdPrefix within it replace the existing migrate.inf on the 8G stick with the one produced IF it matches what was said before jaclaz

[sarcasm] This HAS been asked before, and the answer has been all the times: Why do you think people found this difficult method if simply exchanging the boards would work? It has been also put into music by Bob Dylan: [/sarcasm] [serious] You would have TWO not working drives, and it is even possible that when you return the board borrowed to the drive where it was, you will still have TWO not working drives. DO NOT do it! [/serious] [sarcasm] It depends, this method does not do anything to existing partitions, as long as they were originally formatted in a month without the "r" in it's name (it's urdu name of course) and that were NOT partitioned with full moon. [/sarcasm] jaclaz