jaclaz

I will throw on the table one of my usual semi-random ideas. Sure NUSB is great , but it is "complex" , installing it properly is a nightmare . Maybe a simpler solution for the USB Mass Storage may work: http://www.msfn.org/board/generic-98-usb-d...rks-t99220.html jaclaz

I will try again. The F6 needs a FLOPPY DRIVE, NOT a USB stick. (and the last character is again a full stop or PERIOD). If you have a USB floppy drive, you need NONETHELESS to patch the source, see here: http://www.msfn.org/board/using-f6-driver-...ppy-t82711.html In other words: there are at least three different (all working and tested by a few tens of thousands people with success) documented methods to install XP from USB: http://www.msfn.org/board/install-windows-usb-f157.html there is the good ol' DOS method, as well used by a great number of people with success: http://www.911cd.net/forums//index.php?showtopic=16713 ALL of the above require, in the case of a SATA hard disk, EITHER: an integrated source with the SATA drivers OR: a real floppy Now, you have to take your choice, you are wanting to either: install XP to that PC of yours or: find a new way, that noone succeeded with, to install XP with a CD + USB stick * (read as practical solution vs. theory of install) * not entirely true, there are "special" USB sticks that can be "seen" as USB floppy and a ramdisk method that makes use of a floppy image, but both are NOT easy to follow, the first one because requires this "special" hardware, the latter because it is still experimental and NOT suitable as a "first attempt" Mind you, it's not that anyone wants to "force" you to use one or the other methods, you are of course perfectly free to go your own way , but heck , you came here asking for advice, you were given it, it would be only polite and a form of respect for people who used their time to try and help you to actually try following that advice instead of going astray. If you have problems in following one of the documented methods we are here to try and help you, but you cannot come here crying that something that you did or you are doing by your own is not working, several people took months to devise those methods, to correct the bugs, to enhance them, you cannot expect to invent something by yourself, expecially overnight and when you are under pressure because you need to install that XP: it is possible, but very, very improbable. jaclaz

Only too happy to have contributed to make a happy bunny : http://www.msfn.org/board/cant-access-repa...27-page-10.html I just try and take these seriously: I did not solve anything, I simply pushed a bit Dave-H, luckily enough in the right direction.... jaclaz

@satyendra Let's see if I can better explain to you what other members have been trying to suggest you and that you completely failed to comply with. You are using an OUTDATED version of a program that was developed on this board, the new version is here: http://www.msfn.org/board/install-windows-usb-f157.html There are also other methods, developed since, check ALL the "stickies" in that Forum, but for the moment use the NEW, UP-TO-DATE, BETTERED version of USB_multiboot.cmd: http://www.msfn.org/board/install-xp-usb-t111406.html Choose one of the available options, FORGET the "Genius Hackers" thingy, FORGET anything HP may have told you, FORGET your personal opinions and ideas on HOW you should install XP, FORGET the floppy drive. ONLY read the FAQ's, the documentation or guides that come with the method you chose, and FOLLOW them exactly. Make sure you do not use nlite too "aggressively". Try installing following the above, if anything does not work as expected start a new thread in the said forum (if USB installing related): http://www.msfn.org/board/install-windows-usb-f157.html or continue here if nlite related. jaclaz

Check also the 4.9 version here: http://www.mobipocket.com/en/downloadSoft/...nualInstall.asp jaclaz

Re-read, SLOWLY this time, posts #12,#13 and #14: http://www.msfn.org/board/je-jins-dism-too...04-page-11.html Summed up: Je Jin is NOT going to support this thing under XP. There is (hopefully) a way to run DISM under XP. You DO NOT use Winbuilder for it. You may EXTRACT from the Winbuilder .script the commands needed to register the .dlls and add the Registry entries YOU will need to do the experimenting. Examples: This line: "translates" to: http://winbuilder.net/help/scripts/script_..._ShellExecuteEx regsvr32.exe /s %Windir%\System32\Dism\CbsProvider.dll This line: means: http://winbuilder.net/help/scripts/script_...x.html#RegWrite Add a new key in the Registry, in Hkey_Local_Machine, under \System\CurrentControlSet\Enum\Root\, call it LEGACY_WIMMOUNT, add to it a new value of type 0x04 (Dword) name it Nextinstance and set it's value to 1. You may also want to strudy the sintax of the Reg.exe app that comes with XP. I don't want to seem unfriendly , but you are asking for something "advanced" and that will take lots of time to do, you are expected to have "advanced" knowledge (or learn a bit) and do yourself the steps needed to achieve the "advanced" result you are looking for. jaclaz

Well, the whole idea is to fix whatever you have in your hands BEFORE moving it somewhere else. I mean, if you move "perfectly and successfully" a "botched" install, how do you expect it will work? By magic? Besides, you have two basic errors in your approach: You need to understand the REASON why the "blue screen thing" is happening AND you don't want to "screw around", you want to FIX it. Start by properly describing the BSOD you are having and it's STOP ERROR CODE. jaclaz

@bozo8787 Maybe to clarify, you do not add "several installs" in "one pass", you re-run the program from start for each source you want to add. It's an "incremental" kind of "building". jaclaz

Maybe because it has NOT a "corner" and NOT a "square"? The "poorman's" choice has a simple SATA Power to "plain IDE Power" Converter. Maybe it's clearer from this photo this type of design: (the above is from Vantec) However, since you already have the Coolmax, do as Twittwilly explained B) IF your SATA power cable is long enough, otherwise get an extension, something like these: http://www.newegg.com/Product/Product.aspx...N82E16812189190 http://www.maplin.co.uk/Module.aspx?Module...;!_11914225 jaclaz

More specifically there is "sticky" in the appropriate Forum: http://www.msfn.org/board/install-windows-usb-f157.html Curously titled: http://www.msfn.org/board/faqs-t116766.html Q3 may be interesting, as well as the point 2. in the "main" related thread: http://www.msfn.org/board/install-xp-usb-t111406.html the use of BTS DriverPacks is usually advised, as it is a tested method, whilst the success of direct integration of drivers through nlite or other means may be dependent on the actual drivers needed/used. jaclaz

That's the tricky part , most probably (read as "undoubtedly" ) won't work "right" if a Phison device is not detected, thus I simply cannot help you "specifically" (in the sense I cannot replicate locally). Nor I have an "indirect experience" with it as another used: http://www.msfn.org/board/do-split-my-usb-...pid-887182.html abandoned the game long before getting into the "action" part of it. BUT there is a manual for those around: http://www.flashboot.ru/uploads/files/publ..._UserManual.rar I guess that you want to try re-programming it to mode 3 or mode 8. Only recommendation I can make is: print the manual, see if it makes sense, re-read it, and then again, BEFORE attempting flashing the thingy. Ask if you have any doubts BEFORE flashing. jaclaz

Then, use something like the second one: http://cgi.ebay.com.my/ws/eBayISAPI.dll?Vi...em=260477902803 (NOT an enclosure BUT a power supply for the drive, it won't "cover" the GND/TX/RX) jaclaz

It's the same thing. It is the "Microsoft Corporation.img" or "Arnes Boot Record" which is the El-Torito no emulation boot image and that is written to the CD bootsector. Let's say that before being actually burned to CD it is a Boot Image and after it has been burned it is a Boot Sector. Here: http://flyakite.msfn.org/xpprosp1.htm it's called Boot Sector, it's the 2048 bytes long file that ends like this: jaclaz

If I may , the idea is to "follow flyakite's guide principles" BUT skip over a few of them and follow cdob's tutorial. The flyakite guide and what Gremo originally did is (basically and at it's core) made of two "main" steps: expand/create the \$WIN_NT$.~BT\ and \$WIN_NT$.~LS folders through WINNT32.exe and rename the first to "\PRO1" and move the contents of second to "\I386" and "\AMD64\" hexedit/patch/modify paths in relevant files What cdob's suggested/hinted is to NOT expand anything and just rename/move directories and hexedit/patch modify paths in relevant files. In other words flyakite's original approach is "bring back to CD a HD install", whilst cdob's suggested one is "modify the original CD based install to work from a different path". jaclaz

Good , and bad news at the same time, but at least now we know that nothing is wrong with the 2K. That's more or less what has been discussed here in the last few days: Good morning, Mr de La Palice. : http://en.wikipedia.org/wiki/Jacques_de_La_Palice Now, do you think I would have advised you to try using the Manufacturer Tool if I thought you could get away with the "plain" security app? OF COURSE the security program WON'T work to restore it. jaclaz

Two point JFYI: you DO NOT want an enclosure you DO NOT want to add an extra layer of possible problems (the USB connection) However, if you are going to use the USB interface, get a "free" one, examples: http://cgi.ebay.com.sg/New-USB-to-SATA-Con...=item3a53b43d76 http://cgi.ebay.com.my/ws/eBayISAPI.dll?Vi...em=260477902803 jaclaz

Judging from version history: http://www.peid.info/history.html upgrading 0.94 to the 0.95 version is a "must" jaclaz

Not only "backup", also make sure you can restore. Better be VERY safe than sorry. jaclaz

Back to square #58: http://www.msfn.org/board/problem-installi...74-page-57.html But we have not yet determined, if: the flash device is hosed (and the ONLY way is for you to test it on another computer) OR the 2K Registry is hosed. If #1 using the manufacturer tool may bring it back to pristine state. If #2 using the manufacturer tool is pretty much unuseful/unneeded and risky If BOTH installing the Manufacturer Tool on a "shaky" 2K may do more harm than expected and possibly really "hose" both the device AND OS/Registry. However, all in all you have not much to lose, so I would go on all the way down, AFTER having tried to properly clkean the Registry USB related keys - ALL the steps. Take this thread LOOSELY as a base reference for a typical use of MP Tool: http://www.msfn.org/board/screwed-up-usb-drive-t137990.html though a USBest is talked about there, most manufacturer tools have a similar approach. jaclaz

NO you are not. ANother solution has been given in the thread you referenced. You are looking for a way to perform the Registry shrink solution. I agree that slimming down the Registry is a better and more elegant way, but you cannot slim it down if not up to a certain limit. I would try RegSeeker, but do not expect miracles: http://www.hoverdesk.net/freeware.htm The sizes you report do not seem to me "abnormal". Something you may want to explore would be to reduce the ControlSet002 to the bare minimum, but you are effectively losing (at least partially) an "escape pod" in case of troubles. You sure you have just ControlSet001 and ControlSet002, I had a 2K machines where in time I had as much as 5 ControlSets. Using the nirsoft tool that GrofLuigi suggested, this usually results as a "problematic" area: http://www.pctools.com/guides/registry/detail/1238/ jaclaz

Read the stickies here: http://www.boot-land.net/forums/index.php?showforum=77 particularly this one: http://www.boot-land.net/forums/index.php?showtopic=9201 AND if needed this thread: http://www.boot-land.net/forums/index.php?showtopic=9051 jaclaz

Read flyakite's guide: http://flyakite.msfn.org/ http://flyakite.msfn.org/xpprosp1.htm Editing "setupldr.bin" Alternative: grub4dos or grub4dos+floppy images: http://www.msfn.org/board/please-help-w-du...sp2-t127900.htm Cannot say if everything that applies on 32 bit also works exactly the same on x64. jaclaz

Sure, and as well ANY number of other softwares would do that, point is/was that the numerical data in the usb.if file is Decimal, whilst all the commonly used tools in the "usb field" use Hexadecimal. Maybe useful hint : usbif2csv.cmd|FIND "13FE" Results in: jaclaz

WHICH Linux tool? jaclaz

Maybe the ones I posted a link to? jaclaz