jaclaz

It is perfectly possible that there is a "robots.txt" preventing indexing a part of the forum and not another. http://en.wikipedia.org/wiki/Robots_exclusion_standard You should ask the actual Forum Administrators if such a policy is in effect and how it is set. jaclaz

What is the difficult part in the README first? READ ATTENTIVELY point #10! Draw your own conclusions. jaclaz

The MBR is NOT the bootsector. This is where you probably are confusing matters. Normally the bootsector of first partition is at sector 63 (CHS 0/1/1) on "legacy" systems (up to XP/2003) and on sector 2048 (CHS 0/32/33) on Vista :ph34r:/2008/7 (if not patched to follow "legacy" Rules) The MBR is NOT part of the volume, it is part of the disk. Review this: http://mirror.href.com/thestarman/asm/mbr/DiskTerms.htm http://mirror.href.com/thestarman/asm/mbr/DiskTerms.htm#LOC and take some time on the Starman's pages to understand the structure of disks and partitions and volumes and filesystems. First sector of a hard disk (sector LBA0) is the MBR or Master boot record. The bootsector of a partition starts at first sector of the partition or volume, as said for first partition it is normally LBA 63 or 2048 depending on the OS that partitioned the volume. More generally you read the partition table in the MBR (and for extended partitions in the EPBR chain) to know where the bootsector of a given partition starts. FAT 12/16 the bootsector is 1 sector long FAT32 the bootsector is actually 3 sectors long, first, second and third if formatted under DOS/Win9x/Me: http://mirror.href.com/thestarman/asm/mbr/MSWIN41.htm first, second, third and thirteenth: http://mirror.href.com/thestarman/asm/mbr/FAT32brcomp.htm if formatted under 2K/XP and later (for the record, for unknown reasons the FAT32 of ReactOS uses 15th sector innstead of 13th) jaclaz

NO. Look, it works this way, in the Registry *something* says to start the intelppm driver (and - as said - the other ones mentioned) automatically. If you delete the file the *something* will try to start it nonetheless. You need to disable the *something*, i.e. set it so that it only starts "on demand": You can check if the "old" motherboard install the HAL uses a "normal" ACPI Uniprocessor HAL that will also support a multi-processor motherboard (Halaacpi.dll) http://support.microsoft.com/kb/309283/en-us Another option is offline sysprep: http://www.911cd.net/forums//index.php?showforum=43 jaclaz

Well, the easiest would be HDhacker but is NT/2k and following only. Beeblebrox and similar tools tend to just save the first sector (which actually in the case of FAT32 is however the only one containing meaningful DATA). For DOS you can use MBRwizard http://mbrwizard.com/ you want the "Legacy" version, please note how you need to get to the firesage site through the above "old" site in order to get the "Legacy" tab. But more generally any disk editor working under DOS/Win9x will do, a good one is the PTS-DE one: http://mirror.href.com/thestarman/tool/FreeTools.html#PTSDE http://mirror.href.com/thestarman/tool/de/PTS-DE.htm jaclaz

It's actually this one: http://www.theabsolute.net/sware/dskinv.html It is not - as a general rule - a good ide to link to a .exe file directly. It is clearly a gltch of the program. Open the disk in any "simple" tool, like the ones listed here: http://mirror.href.com/thestarman/asm/mbr/BootToolsRefs.htm or beeblebrox: http://replay.waybackmachine.org/20080423005903/http://students.cs.byu.edu/~codyb/ http://replay.waybackmachine.org/20060223003038/http://students.cs.byu.edu/~codyb/beeblebrox9xsetup.zip You will see that these data: Total logical sectors: 1062876402 Cylinders: 625 Sectors per cylinder: 63 Heads: 255 will remain the same (they are physical values of the actual hard disk). However, I was incorrect, these data come from system calls, particularly the 129 means drive 0x81 i.e. second drive in DOS (as taken from the BIOS) and the rest are physical values, but the cylinder one is also blatantly wrong. 625*255*63=10,040,625 sectors * 512=5,140,800,000 so they make NO sense. On the other hand, the value of 1,062,876,402+63=1,062,876,465/63=16,871,055/255=66,161 Cylinders Your disk should have a "virtual CHS geometry" of 66,161 or 66,162/255/63 jaclaz

Are you refeering to the two .txt files? WHAT did you use to make them? Anyway these: Are info that come from the MBR (and not from the bootsector) i.e. from PhysicalDrive and not from LogicalDrive. jaclaz

More specific info: http://mirror.href.com/thestarman/asm/mbr/MSWIN41.htm http://mirror.href.com/thestarman/asm/mbr/MSWIN41.htm#FSINFO Definitely byte 0x30 should be 0x01. What is not clear (to me at least) is whether this provision was "born" with FAT32 or it was added *sometime* later. jaclaz

Actually the issue is with the TOTAL length of the power leads : basically it's the TOTAL length from the power supply to that actual board that may (in some particular cases and ONLY with "bad" power supplies that send the spikes) create a voltage peak when switched on (capacitor effect). This SHOULD NEVER happen (i.e. no way it can happen ) if you power the PC BEFORE and later connect the Molex. There is NO possible switch bounce WITHOUT a switch (unless of course you have delirium tremens ) It WON'T happen if you use a battery to power the adapter. You may want to do it behind the green glass door where there are NO switch bounce nor voltage peaks, and lots of TTL-converters...(but NO USB ) The USB to TTL seems to me the best choice of the three mentioned as it is ALREADY powered by the USB BUS and you need not to fiddle with the power supply, you just insert the device in a USB port. jaclaz

Yes, usboot approach may work. The alternative being following the "good ol'" method by Dietmar (tutorials are in his signature): http://www.911cd.net/forums//index.php?showtopic=14181 you want to use Tutorial 3: http://www.911cd.net/forums//index.php?showtopic=14181&st=228 and/or Tutorial 6: http://www.911cd.net/forums//index.php?showtopic=14181&st=1515 with the added feature of USbbootwatcher: http://www.911cd.net/forums//index.php?showtopic=22473&hl= But yes, your mileage may vary. jaclaz

Well, with all due respect , if you got it from pololu how come you didn't read the NOTE: it's quite visible. WHERE are you based? India? Get this: http://www.embeddedmarket.com/products/USB-to-TTL-Converter-Module/ (just an example) Another one: http://www.rhydolabz.com/index.php?main_page=product_info&products_id=302 An USB to TTL one: http://www.rhydolabz.com/index.php?main_page=product_info&products_id=304 jaclaz

Yes, unfortunately it MAY happen. It is a RARE condition, but it may happen with a re-start (as opposed to switch off) in certain conditions. Compare with the issue detailed here: http://www.pololu.com/catalog/product/126 http://www.pololu.com/docs/0J16/all jaclaz

No elevenses but abbundant prenoon booze intermissions or recesses and they also indulge mollycoddle in the habit groove of Yukkaflux http://bigblogofbooze.blogspot.com/2005/12/dictionary.html BTW, they have no oranges, but apples a lot and plenty berries, expecially Abyssinian Gooseberries and Yellowberries.... jaclaz

Rule of thumb has always been to use the SAME SP level when doing a Repair Install (BTW if I recall correctly you could NOT repair an install with a "lower than installed" SP CD). Review this: http://michaelstevenstech.com/XPrepairinstall.htm You can try setting intelppm driver (and a few more ones) to start 3, only seemingly unrelated: http://www.911cd.net/forums//index.php?showtopic=22473&st=23 The "old" method was, with the XP install running on the "old" motherboard, go to device manager and delete EVERYTHING but: video keyboard mouse and shut down the system, then move the hard disk to the new motherboard, and WITHOUT letting it boot, start from CD the Repair install. jaclaz

It should be, in the sense that the tutorial is born with the idea of using "kosher" UNMODIFIED source .iso's, if (besides the actual integrated Service Packs) you actually modify them (like nlite, driverspack, unatttended and what not) it makes little sense, and another method, NOT using a .iso will save you the time to recreate the .iso. As well it is very possible that new KB's integrated may "break" the compatibility. Mind you I am not saying that any of the above will create a problem, only that it is possible that it may do so. jaclaz

No, you don't. Yes, but it has NOTHING to do with fonts and effects applied to that. The source (the tutorial page from which you copy) uses a DIFFERENT, "wrong" character codes for the quotes from the one that it is needed. The character code has NOTHING to do with font or effects applied to it. Compare with these (since you appear to use Word): http://www.ehow.com/how_6050557_delete-quotes-ms-word-2007.html http://support.microsoft.com/kb/206165/en-us Copy from the source. Paste into word. Select and change in ANY font you like and REMOVE the "italics" effect Do what is in the MS KB under "Replacing Existing Smart Quotes with Straight Quotes" Select and change in ANY font you like and add the "italics" effect Copy from Word Paste on command prompt However , I did my best you to explain the real cause of the issue to you, but if you are happy to think that it happens because quotes are in italic, you are perfectly free to do so. 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