jaclaz

Unfortunately you have to test this on "real hardware", as Virtual Machines, besides the USB limitation, may have other "features" or "peculiarities" that do conflict in these "particular" cases (USB booting, and install from USB). Additionally if I remember correctly Virtualbox has a bug in drive enumeration that prevents some of the approaches (not necessarily this particular one, but I do suspect it ): BUT , this particular method, though named "How to install XP onto a Hard Disk from an XP ISO on a bootable USB drive" and actually intended for that, could be named: "How to install XP onto a partition on first Hard Disk from an XP ISO on a bootable disk temporarily set as first disk" as it does NOT use/need "particular" USB settings. In practice, you can try it in Qemu (+Qemu Manager, recommended): http://www.davereyn.co.uk/download.htm by mapping the USB stick as \\.\PhysicalDrive as 1st hard disk and the VM hard disk as second and later "promote" the VM disk to which you installed the XP to 1st one. Some reference: http://reboot.pro/9688/ http://reboot.pro/8581/ jaclaz

NO need to be sorry and NO feathers were ruffled , I am grumpy by nature . You fell for the "end product" (the .iso) overlooking it's components, i.e. you extended the use of the .iso outside of the intended context (an actual CD). And you missed as well how the Author of the netbootdisk did extraordinary efforts to compress and reduce source in order to fit it in a 1.44 Floppy disk, and only after succeeding in this "exported" the product to the CD, thus implementing in it "artificial limits". In other words, you asked yourself (and on the board) a "wrong question": whilst the "real question" you had was: Most probably because of: you mistook the method with the actual problem, it happens quite often, compare with: http://homepages.tesco.net/J.deBoynePollard/FGA/put-down-the-chocolate-covered-banana.html If you need help with the making of the image, or it's booting, here are a few things that might be of interest to you: http://www.911cd.net/forums//index.php?showtopic=16745 http://reboot.pro/3963/page__st__3 http://www.911cd.net/forums//index.php?showtopic=21212 http://reboot.pro/11549/ jaclaz

...but they never get stoned, nor high. Issue appears connected with excessive occasions to swallow moonshine, but they miss the consequences of the distilled goop. Seemingly and possibly, they are affected by an illness that forestalls offshoots and fallouts. jaclaz

It is likely (but not "definitely") that the un-plug/re-plug caused a power surge and one (or more) capacitors ALREADY on the verge of going dead, actually died. That symptom is typical, see here: http://www.aplusperfect.com/articles/lcd_capacitor_repair jaclaz

Yes , and again, it is not because they are italics, or because they are in Calibri font, it is because the whatever the Author of the Tutorial used to write the html page automatically replaced "plain quotes" with "left and right ones". This has NOTHING to do with: font used effects (like bold, italics, underlined or striken) applied I am not talking about the "final result" of the problem I am talking about the cause that you attribute to it. Let me show you: Font Courier New: Font Microsoft Sans Serif: jaclaz

Of course NOT. And grub4dos is NOT grub (legacy) and NOT GRUB (2). You need to launch a .bat from an OS environment (i.e. DOS). The .iso that you are using is probably an El-Torito floppy emulation one, in other words it is just a container for a "normal" floppy. We are talking of this, right? http://netbootdisk.com/ http://netbootdisk.com/bootcd.htm Since you use grub4dos, you can boot INSTEAD of the .iso the floppy .ima or .img. This can be write/read (UNLIKE .iso) Additionally, you can make a larger floppy image and uncompress part of the contents of the disk as you have more space. Also, if you want to still go (needlessly) through the .iso route, remember that the El-Torito floppy emulation is compatible with 2.88 Mb sized disks. Rather obviously this topic has NOTHING to do with "Install windows from USB" and should have been posted on a grub4dos dedicated place, like: http://reboot.pro/forum/66/ jaclaz

All the issues are NOT about "stability" but rather about "compatibility" and "convenience". Rather obviously utilities developed since a couple of years are more and more widely tested on different hardware and have been "refined" and "adjusted" to be compatible with the most hardware and "uncommon" versions of XP. The more recent ones have had less testing and may be need such refinements/corrections. The newish method by cdob is the one potentially more "convenient" in the sense that you can use an UNMODIFIED .iso and need NOT a large amount of RAM: a spin-off, more detailed, is here: http://sites.google.com/site/rmprepusb/tutorials/install-xp-from-an-iso But obviously your mileage may vary. Just try it, if it works for you, GOOD , if it doesn't, please report the problem you get, so that it can be corrected or a workaround found. jaclaz

Sorry if it is not up to your expectations. Reading? The intended essence of that post is that seemingly MS pulled Quantum compression from CAB related utils sometime in 1996. jaclaz

Yes , but what you have wrong is that the issue is NOT about "italics" the only "double quotes" that you can enter by pressing a keyboard key are "plain ones" aka Char hex 22. A number of word processors/nice GUI programs when they parse a set of double quotes replace them with left and righ quotes, aka Char hex 93 and 94. This has NOTHING to do with the font used and with the effects applied to the font. jaclaz

Of course. Can you tell me how to write double quotes in Italic on command prompt? (unless you use ALT+0147 and ALT+0148 - and that's NOT "italic") No, it is NOT. Copy and paste the following in a new, empty Notepad window: BAD QUOTES :“” GOOD QUOTES :"" Save the file. Open it with a hex editor: You will see how the double quote is character 22 whilst left and right quotes are character 93 and 94 hex Exactly. jaclaz

An only seemingly unrelated consideration: http://www.pcguide.com/ref/hdd/file/partFAT32-c.html Such a big partition with smallish cluster size may have different performance with different amounts of available RAM. jaclaz

Sure , google-fu is behind the green glass door, but peeps in it do not master it, nor get the hang of it.... They should really double and triple their efforts, actually progress to attain and accomplish threefold current awareness of this matter . jaclaz

Just to try and understand, the "right" things are the plain "double quotes", so if you TYPE the commands given in the Tutorial they will work BUT if you attempt a copy and paste it will fail? jaclaz

Well, it depends on which version of *anything* you are using, I presume. Quantum compression has been discussed here: jaclaz

...and in the wrong place. See here : Install Windows from USB http://www.msfn.org/board/forum/157-install-windows-from-usb/ jaclaz

Connect the hard disk. Boot and get to the BIOS setup. Can BIOS see the disk? Yes/No If No it's probably in BSY state If Yes, then does it show it's size in BIOS as LBA 0? Yes/No If Yes it's definitely in LBA0 state. WHAT caused the BSY or LBA0 state? Will the proposed fix work on the particular BSY or LBA0 state? ...the answer my friend, is blowing in the wind.... jaclaz

MInd you the following is my PERSONAL opinion. There are reports of the i365 guys to be either extremely correct and honest or completely nuts and false (up and beyond the border of "robbery") I suspect that this may depend on several factors including: the actual "channel" through which your drive was sent to them the actual "operator" that actually puts his/her hands on your drive Point is whether your drive was originally affected by either LBA0 or BSY problem, what we commonly define as "bricked" as in: For what we know: it is NOT possible to upgrade the firmware UNLESS the drive is "unbricked" first. once the drive is unbricked (and WITHOUT ANY firmware upgrade) it won't re-brick itself spontaneously for at least three months of daily use (six to twelve month being proven to be the most likely cases) logically NO data recovery service would (though it is possible) re-brick the drive after the firmware upgrade actually upgrading the firmware has NO (immediate) consequence to the actual "brick status" of the drive If I were you (and mind you - AGAIN - this is just my PERSONAL take on the matter), if you are sure enough of the symptoms your drive had when it failed, i.e. you are confident enough that it was in a LBA0 or BSY state, I would call the bluff and get the drive back. Mind you also that there is a line that is quite "elastic" between "recovering a drive" and "recovering the filesystem", and even another elastic line between "recovering the filesystem" and "recovery of MOST contents of it". PLEASE go to "Search" and search for "i365" make sure you select "Show results As posts" and take some time reading the results (you'll get two pages of results): http://www.msfn.org/board/index.php?app=core&module=search&search_in=forums Come back when you have read ALL those posts and have a better idea of the past experiences of the other members, as said quite contrasting. jaclaz

Dear user , you have probably been pointed here because you completely failed to read the FGA's and particularly FGA #1: You also completely failed to read the main thread, where very often a new member, just like you, thinks to be smart and that he can get away with a PCB swap, a few examples: http://www.msfn.org/board/index.php?showtopic=128807&st=1821 http://www.msfn.org/board/index.php?showtopic=128807&st=2173 http://www.msfn.org/board/index.php?showtopic=128807&st=2240 http://www.msfn.org/board/index.php?showtopic=145290 Now, swapping PCB's is in this case a very bad idea, and deemed to failure. It is NOT new, and it´s offending the intelligence of the people who found/developed the methods to recover from a BSY or LBA0 error, and a kind of lack of respect towards the ones that try to help others in following that procedure, and that spent a lot of time in wording both the read-me-first (which should be read FIRST): and the FGA's: It also does not stand a logical verification. You had this great new idea, allright : since it's new, then noone has ever tested it, thus noone can possibly tell you if it will work or it won't. On the other hand, asking if it will work on the main thread dedicated to bricked 7200.11, implies that you presume that peeps in there do know where their towel is, and know more (or better) than you on this specific topic. So, these guys/gals are recommending a rather complex procedure, involving a data converter and issuing a set of commands to the drive, and you come to ask them if a much simpler procedure (swapping PCB's) will work? What do you think they will answer you? A typical answer would be: [sarcasm] Sure it will work, the reason why we use and advice another and much more complex and error prone procedure is basically because we like deceiving other people and make things that are completely unneeded, and besides we are covertly financed by the USB-to-TTL and RS232-to-TTL sellers lobby, we already tricked several hundreds people into buying this completely unneeded hardware, so we are pretty good at it. [/sarcasm] As a known shoe manufacturer would say: Just do it! Only, please don't come here whining it didn't work. jaclaz

For NO apparent reason : jaclaz

Oh, my ! Do you mean that the battery actually (when tested with a voltmeter/multimeter) does give 3 V (or whatever it should give) BUT that the BIOS cannot hold the settings? Have you tried ACCURATELY cleaning contacts on the motherboard's battery holder/connector? jaclaz

Well, for the record the "initialize disk" is there since at least Win2K (really cannot remember NT 3.51/4.0 had the same , but I would think yes). JFYI : http://reboot.pro/12253/page__st__8 jaclaz

Pheew. But you have the screenshots, and you can manually add new partitions: http://www.cgsecurity.org/wiki/Data_Recovery_Examples#Two_FAT32_partitions_to_recover Only, it is not advised (better wait a few hours and avoid a possible mistake) jaclaz

Sure , guess WHY the drivespack were developed? http://driverpacks.net/ jaclaz

Sorry, but NO (meaning that you did *something* before thoroughfully checking, as you were told it would be needed). You write what you see. If the partitions were not listed when you hit Write they won't be there, that is essentially the meaning of my previous post. You might have deleted them accidentally before the disk scan, but if you did so, they were NOT there when you hit the Write. jaclaz

Specific to the CONTROLLER (not on the disk model). Also, performance advantages depend on hardware. If you have "old" hardware it is likely you won't have any. JFYI: jaclaz