jaclaz

No prob, I'll add the option to keep the "USB Repair" entry in the batch. Just an abstract idea, mind you, but we could make a second batch to "clean" the BOOT.INI from the signature(aabbccdd) and "USB repair" option entries on second boot, i.e. once the user is certain that the procedure worked. You are right, I'll add this check to the batch. Have fun and relax. I am not sure I fully understand this last part, but I think that if anything changes between USB stick and USB Hard Disk, we can make a detection in the batch for the type of media and have a conditional execution of different instructions. jaclaz

No need whatsoever to apologize, your contributions have been and are of the max importance. However, since the binifix3.cmd has the same functionalities of binifix2.cmd, one could stay with it, just in case some other user, with different/strange BIOS or something else, should come out with a signature(aabbccdd) entry in boot.ini. jaclaz

@wimb Please try the attached binifix3.cmd Changes: 1) Replaces (if Default entry) signature(aabbccdd)disk(0)rdisk(z)partition(w)\windir with: multi(0)disk(0)rdisk(z)partition(w)\windir Both in default entry and in [Operating Systems] 2) Writes original entry in [Operating Systems]: signature(aabbccdd)disk(0)rdisk(z)partition(w)\windir="Some description" /some parameters modified as follows: signature(aabbccdd)disk(0)rdisk(z)partition(w)\windir=(signature) "Some description" /some parameters This should cover all cases , I guess that the user that uses this "experimental" way will be able to delete the (signature) entry from boot.ini manually once the new "default" one has proved to be working. jaclaz P.S.: Just found a smaller problem in binifix3.cmd Removing the attachment, will re-add it later, as soon as I fix it. OK, now it should work. binifix3.zip

@wimb Could not the batch file provide a way to automatically get rid of the signature(aabbccdd) line of your post #141? If I get it right, that line gets the correct rdisk(z), and as so it would just be a matter of replacing signature(aabbccdd) in the lines with multi(0). As "normally" there are no entries with signature(aabbccdd) syntax in boot.ini, if one is found it should always be the one created by the install. Just to be on the safe side one could just correct the default entry and duplicate the [Operating Systems] one, leaving one entry with the multi(0) and one with the signature(aabbccdd) syntax that could be manually selected in case the "direct" one, for any reason, won't boot. jaclaz

@all Please find attached a 2nd tentative version of the batch file. Unlike the first version, this will ONLY work with a BOOT.INI on root of a drive (or in a path without spaces in it) Solved three problems: 1) one or more "=" signs on the right of the "main" one 2) one or more leading or trailing spaces in entry or entry description 3) empty lines Added backup feature for original BOOT.INI, saving a maximum of three versions. @cdob I'll look at your suggestions, I have not yet a complete and definite idea on how to find the right drive. There is a key in Registry: HKEY_LOCAL_MACHINE\SYSTEM\Setup\SystemPartition where this values are set: "SetupType"=dword:00000000 "SystemSetupInProgress"=dword:00000000 "CmdLine"="setup -newsetup" "SystemPrefix"=hex:c2,0b,00,00,00,40,3f,20 "SystemPartition"="\\Device\\HarddiskVolume1" "OsLoaderPath"="\\" Though illogical as it may seem, the "SystemPartition" actually appears to represent the "Boot" partition, as opposed to %SystemRoot%. "\\Device\\HarddiskVolume1" is a "symbolic" link for which I have not found (at least yet ) a way through pure batch and through "normal" XP included command line tools. One could however use the vlm.exe utility (part of the DSFOK toolkit) to "couple" this link to actual drive letter. Otherwise we are back to "square 1" with DMDIAG.EXE. I would greatly prefer to only use "standard" tools, so any idea is welcome, maybe this is possible through a .wbs script? jaclaz P.S.: Please someone have a look at this batch: http://www.robvanderwoude.com/bootdrive.html (I have not handy a XP machine right now) Does this return "System" or "Boot" drive? binifix2.zip

@wimb Hey, I don't want to seem unfriendly, I am not, and at times I am also an extraordinarily friendly guy , but when one asks (I guess politely) for something, like: and: Please do post some examples of these boot.ini's so that I can adapt the code. One expects two kinds of replies: #1: Yes, here are the examples required. #2: No, I will never post what you required. (and all possible variations of the above) Quite frankly telling me HOW I should correct a batch file I wrote, because it does not work with some entries of which I have not (and asked for twice) any example is a bit trying for my otherwise good manners. However, should I have failed in explaining this before, can you please post some examples of boot.ini files that do not work with the tentative batch I posted? jaclaz

@wimb This should work as well, takes into account multiple (if any) "=" but the main one, and is a bit more simple : FOR /F "tokens=1,* delims==" %%A in ('TYPE %source%') DO ( IF /I "%%A"=="default" SET DefaultEntry=%%B IF "%%A"=="!DefaultEntry!" SET EntryDesc=%%B IF /I "%%A"=="timeout" SET Timeout=%%B ) Please do post some examples of these boot.ini's so that I can adapt the code. @ilko_t Ok, I'll see what I can do with the Registry thingy. jaclaz

@cdob @wimb Good work in bug finding guys! I'll try and fix the reported misbehaviour of the batch. @cdob Yes, I just added the signature(aabbccdd) syntax as a "proof of concept" that the "logic" in the batch can be adapted to ANY situation, you are right, we can get rid of it in "final" release. About drive letter, I give as assumed that boot.ini is on the root of the drive, I wasn't sure that, at the time when the batch needs to be run, %systemdrive% represents correctly the latter (and I am still NOT convinced of it, I know I am a bit tough ) but as I usually, and from immemorable time, install Windows NT/2K/XP in extended partitions, %systemdrive% does NOT represent the BOOT drive. I had gathered from the thread that the "definitive" boot.ini is ALWAYS on C:\, boot drive, i.e. First Primary Active Partition of First Hard Disk, no matter where windows is installed, I would like to have a confirm of that, otherwise I think we need to use the batch passing to it a parameter. No problem if I can access the DosDevices key of the Registry, what I am not sure about is if at the time the batch is meant to run the Registry is accessible (I suppose not) and if the proper entry has already been written to the key. But, as said, if NO other "strange" setting has been applied, First Primary Active Partition of First Hard Disk, should always be C:\, maybe I can add the drive letter as an optional parameter for the batch (if not supplied willl default to C: ) No prob in adding a BOOT.INI -> BOOT.BAK feature, nice (and safe) idea. @wimb Can you post an example of line where the "=" sign is used on the left of the "main" "=" sign for description? Also, are there any cases where more than one "=" sign is used (besides the "main" one)? I guess I can modify the "tokens=1,2" "to tokens 1,*" or "tokens 1,2,3", but I need one (or more) example(s) to test the behaviour. jaclaz

@NOTS3W This might be of interest for you: http://www.msfn.org/board/index.php?showtopic=69151 Various ways to implement a "tee" like command. jaclaz

Ok, here is the tentative batch to transform rdisk(z) into rdisk(z-1) As is, it is a bit complicated by the fact that it is written for debugging, it works with a boot.ini in the same directory as the batch, and, knowing how people love working in directories with spaces in them (why? ) provides support for them. Once it has been tested with positive results, it could be simplified as to work with %drive%\BOOT.INI. @ilko_t BOOT.INI should always be on C:\BOOT.INI, whatever the hard disk(s) setup is, am I correct? jaclaz binifix.zip

No, the idea is to have under win9x/Me GUI (NOT under DOS 7.x command line) an alternate command interpreter capable of running .cmd batch scripts INSTEAD of .bat ones and take advantages of most (but NOT all) added features of batch commands from NT/2K. For a replacement of DOS command.com, the reference is of course the JP Softwares 4DOS, which used to be Commercial, then was released as FREEWARE and recently became OPEN SOURCE !: http://www.boot-land.net/forums/4DOS-is-no...urce-t2549.html Start here: http://www.4dos.info/ http://www.4dos.info/4dinfo.htm if you do not know what 4DOS is. I don't get it , the download on the given site: http://cygutils.fruitbat.org/consize/ has TWO builds of it, already compiled. jaclaz

Just for the record, there is a "cmd.exe" that works under win9x that has almost, but not quite, all the functionalities of 2k/Xp "cmd.exe": http://www.boot-land.net/forums/?showtopic=2392 jaclaz

Well, as specified in the page I referenced before, you need to add the "/unattend" switch, NOT hte "/unattend[num]:[answer_file]" one. But the problem is that your PC does not qualify for an upgrade, and cannot say if the nlite "remove limits" option will work or not in the case of an upgrade. However, as several people already said, installing XP on that machine is more like committing suicide than anything else (even if you succeed you will have a sloow death, you will die during sleep from boredom while waiting for system to boot and later, little by little, by each minimal but significant lag of time between any command you may give and the system response..... ) What I personally find adequate (which does NOT mean minimum, but rather minimum to have acceptable responsiveness): 32 Mb Win95 or lited 98 64 Mb NT 4.00 and Windows 9x 128 Mb for Windows 2000 256 Mb for Windows XP jaclaz

Well, this does not help much in correcting it (if needed ), does it? Can you reply to the original topic on boot-land (as to not clutter this one) and tell me more about the problems you had? I tested it on two separate machines, and it worked, but since both PC's are my own, they have very similar setups so they do not represent a good test. @ilko_t I'll try and see what I can come out with. About the "already" present lines, it should not be a problem since, if I a not mistaken the "new" entry will be by default the "default" one (pardon me the pun ). What I mean is, if on First hard disk there is already a "complex"BOOT.INI like this: The result when modified by the new install, let's say on first hard disk, partition 3, will be: And what the batch has to do is to look at the arcpath specified in "Default=" and change just that entry and the corresponding menu one below with same arcpath as follows: Am I correct? What happens with SATA drives? jaclaz

Well, you missed my post here: http://www.msfn.org/board/index.php?showto...1384&st=218 And the batch I wrote: http://www.boot-land.net/forums/index.php?showtopic=2362 it does EXACTLY that. Allowed are ANY 8+3 names, so you can leave SETUPLDR.BIN as is without renaming it. (You may notice the amount of feedback I received , I guess that changing loader in bootsectors is an activity that very few people do) About the arcpath, I am still thinking about it, the problem may lay with some "unorthodox" Partition tables, see these: http://www.goodells.net/multiboot/editbini.htm http://www.goodells.net/multiboot/notes.htm#10 Easiest would probably "assume" that one would use USB install just for installing XP on FIRST PRIMARY partition of FIRST harddisk, as it happens, say, in 99% of cases and operate a manual adjustement for the remaining 1% (like myself) that install to Logical Volumes inside Extended Partition or that install to a non first hard disk. In this case the batch could ask user if he installed it to first active partition of first disk, and if answered yes write on BOOT.INI a line referencing multi(0)disk(0)rdisk(0)partition(1)\WINDOWS or otherwise write several lines like: multi(0)disk(0)rdisk(0)partition(1)\WINDOWS multi(0)disk(0)rdisk(0)partition(2)\WINDOWS multi(0)disk(0)rdisk(0)partition(3)\WINDOWS multi(0)disk(0)rdisk(0)partition(4)\WINDOWS multi(0)disk(0)rdisk(0)partition(5)\WINDOWS multi(0)disk(0)rdisk(1)partition(1)\WINDOWS multi(0)disk(0)rdisk(1)partition(2)\WINDOWS multi(0)disk(0)rdisk(1)partition(3)\WINDOWS multi(0)disk(0)rdisk(1)partition(4)\WINDOWS multi(0)disk(0)rdisk(1)partition(5)\WINDOWS Another idea would be to parse the existing boot.ini lines with: multi(0)disk(0)rdisk(z)partition(w)\windir get the rdisk(z) value and just subtract 1 from it, leaving al the rest as is. What do you think of this last idea, it came to me just as I was writing this post, could it work? If yes, I think I can jolt it down in batch quite easily..... jaclaz

Yep, FIRST you run: C:\I386\winnt32 /checkupgradeonly If no "strange" errors are reported, you LATER run: C:\I386\winnt32 (with NO parameters) The /noreboot is an optional parameter, it is only needed if you need to do some work on the files in the \$WIN_NT$.~BT or \$WIN_NT$.~LS directory or to the boot files (NTLDR, NTDETECT.COM and BOOT.INI) from your currently running Windows 9x/Me. However, here is a complete list of WINNT32 parameters, in an easy to read format: http://www.quepublishing.com/articles/arti...qNum=6&rl=1 Be VERY AWARE of Murphy's Law, it is not recommended to have NO way out if something goes wrong, for any reason... jaclaz

Hey, porear, glad to see you are still around. Congratulations to you and Mrs. porear, for the contribution to the world population (much more important than your however notable contributions to finding a way to install XP from USB). jaclaz

And, if I may add a further reason to prathapml's post, simply to prove that it CAN be done when Official docs say that it can't. jaclaz

Just a small correction : Next time touch a metallic part of the computer case first, if it is a desktop PC (and thus it is grounded), if it is a laptop (which is NOT grounded) touch any metallic part that is grounded you find around you, such as a handrail or a radiator or a massive metal object, such as a steel file cabinet. jaclaz

Well, actually Methyl detailed step by step tutorial is nice because adding to the stick the grub4dos files you can have a multiboot stick that can, besides installing Vista, do other things. Nothing really new (no offence intended to Methyl ) for expert grub4dos users, but still a really very good thing for less experienced ones. jaclaz

What I would do is to simply run WINNT32 from C:, without the Syspart command. Before that I would prepare, through the use of bootpart.exe, a dual-boot system, so that if anything goes wrong you should be able to boot in your old Win9x allright. And of course DO run the winnt32 /checkupgradeonly ! Details are here: http://support.microsoft.com/kb/316639/en-us DO NOT convert the filesystem to NTFS during install. The only drawback I can see is that you won't probably be able to install XP to the \Windows partition as that one is already taken by your Win98, you'll have to install to \WinXP or some other name. jaclaz

Here: http://www.techdirt.com/articles/20070131/073609.shtml jaclaz

Yes, spacesurfer, you are perfectly correct, the =FLOOR(F3/10,1) function would work, as well as these other (simpler) two : =ROUNDDOWN(F3/10,0) =INT(F3/10) but only in this particular case, (where a numeric value is requested as end result). I tried to give a more "general" solution, including the ability to output text or whatever is in the lookup table, i.e. to possibly replicate the behaviour of the I-ching calculator found by Douglas Adams' character Dirk Gently: The calculator is now available on-line as a java script: http://www.thateden.co.uk/dirk/ And, just for the record , I was a math wiz too. jaclaz

Though I never heard about anybody attempting (let alone succeeding) in this, my other experiences in all matter USB related tells me that the problems (if any) might most probably reside on the actual PC/motherboard BIOS than on the card side. jaclaz

Yep, sure, there are a few utilities to that effect: http://www.msfn.org/board/index.php?showtopic=49184 http://www.msfn.org/board/index.php?showtopic=49103 http://www.nirsoft.net/utils/nircmd.html http://www.commandline.co.uk/cmdow/ jaclaz