Jump to content

Welcome to MSFN Forum
Register now to gain access to all of our features. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, post status updates, manage your profile and so much more. This message will be removed once you have signed in.
Login to Account Create an Account


Photo

How to boot/install from USB key ?


  • This topic is locked This topic is locked
485 replies to this topic

#226
cdob

cdob

    MSFN Expert

  • Member
  • PipPipPipPipPipPip
  • 1,000 posts

peldr seeks txtsetup.sif first in root directory, in minint folder next.
Hexedit peldr using TinyHexer. Change in peldr the first occurrence of txtsetup.sif in notsetup.sif
Now BartPE will boot from minint folder and will not use WinXP txtsetup.sif from root directory.

Thanks for correcting. Sorry, bad message from bad memory last time.

I opened old logs and found:
U:\minint>gsar -o -s:000txtsetup.sif:000 -r:000txtsetup.off:000 setupldr.bin
setupldr.bin: 6 occurrences changed
Yes, \txtsetup.sif is the keyfile.


How to remove advertisement from MSFN

#227
Biohead

Biohead

    ^^ Yes, that IS a Robin Reliant shuttle!

  • Member
  • PipPipPip
  • 336 posts
Great work to all involved.

Is there anyway to get this working for XP Media Center edition? When I've tried it, it just installs XP Pro and none of the media center components, nor any of my additional programs after installation of Windows.

It did not install IE6 or WMP10 either. I upgraded to IE7 and that still was not present after installing, and WMP11 would refuse to install saying I needed Unsupported Operating System. I did make a mistake with undoren.cmd - would this have caused this problem or is this an unrelated problem?
Beware the evil donkey falling slowly from the sky. You can choose the way you live my friend, but not the way you die!

Moral: You can plan, but they will never be followed perfectly.

#228
jaclaz

jaclaz

    The Finder

  • Developer
  • 14,373 posts
  • OS:none specified
  • Country: Country Flag

Great work to all involved.

Is there anyway to get this working for XP Media Center edition? When I've tried it, it just installs XP Pro and none of the media center components, nor any of my additional programs after installation of Windows.

It did not install IE6 or WMP10 either. I upgraded to IE7 and that still was not present after installing, and WMP11 would refuse to install saying I needed Unsupported Operating System. I did make a mistake with undoren.cmd - would this have caused this problem or is this an unrelated problem?


No, if you somehow "skipped" the run of undoren.cmd the only effect is that you have on your stick the two "install" directories mis-named, so you will not be able to run a second install from the stick.

What you report appears to me more like something missing in txtsetup.sif or however in a similar file that lists all added components for Media Center.

Are you positive that you used as base the correct txtsetup.sif?

Maybe you can use some of the info here:
http://www.msfn.org/...ion_t61070.html
:unsure:

jaclaz

Edited by jaclaz, 22 June 2007 - 04:19 AM.


#229
Biohead

Biohead

    ^^ Yes, that IS a Robin Reliant shuttle!

  • Member
  • PipPipPip
  • 336 posts
I'm currently rebuilding the entire usb stick.

Its structure will be:
$OEM$\
$WIN_NT$.~BT\
$WIN_NT$.~LS\
cmpnents\
DOCS\
DOTNETFX\
I386\
SUPPORT\
VALUEADD\
Autorun.inf
Boot.ini
grldr
menu.lst
ntdetect.com
ntldr
README.HTM
README.TXT
Setup.exe
Setupldr.bin
SETUPXP.HTM
txtsetup.sif
WIN51
WIN51IP
WIN51IP.SP2

I wasn't sure what to do with folders on my install disc as it doesn't mention, so I put them on the root of the stick as above (I can afford the space). Is there anything extra I have to do to these folders? I pretty much followed the guide on page 10 of this thread by ilko_t.

Once I've finished rebuilding, I'll reinstall it all again and see whats missing then repost.

UPDATE: It still does exactly the same thing. Its missing IE6, WMP, Windows Messenger, Media Center, Outlook Express. It does not install the Royale theme (the MCE theme) and is the standard Blue Luna.

Edited by Biohead, 22 June 2007 - 10:23 AM.

Beware the evil donkey falling slowly from the sky. You can choose the way you live my friend, but not the way you die!

Moral: You can plan, but they will never be followed perfectly.

#230
Biohead

Biohead

    ^^ Yes, that IS a Robin Reliant shuttle!

  • Member
  • PipPipPip
  • 336 posts
@jaclaz: Where should I have gotten the txtsetup.sif from?? I originally got it from one of the WIN_NT folders as the guide states. Am I best off getting it from the i386 folder (or wherever it is usually located?).
Beware the evil donkey falling slowly from the sky. You can choose the way you live my friend, but not the way you die!

Moral: You can plan, but they will never be followed perfectly.

#231
jaclaz

jaclaz

    The Finder

  • Developer
  • 14,373 posts
  • OS:none specified
  • Country: Country Flag
@Biohead

As I won't touch MediaCenter with a three feet long stick (though shorter of the five feet one I currently use to NOT touch VISTA ;)) I only supposed that the additional components you find missing are not specified in the txtsetup.sif you used.

Maybe, when you create the two bootfolders, a "reduced" file is generated?

Just check what differences are (if any) between the one on stick and the one on CD you already installed from succesfully.

jaclaz

#232
ilko_t

ilko_t

    MSFN Addict

  • Super Moderator
  • 1,722 posts
  • OS:none specified
  • Country: Country Flag

@ilko_t

Please try A updated BOOT_REN.CMD

Tested it with both mapping and no mapping, result is a "proper" boot.ini, however no copy of the original file is present, just bootini.new, which is exact copy of the final boot.ini. I would prefer to set the attributes of the 3 files on the root at the end of the script.
With mapping signature must have been present, in my test both ways ended up with the same boot.ini, haven't checked though whether signature was used, but should have been.


In my "bootsector renaming" script there is a re-usable (clever? :unsure: ) routine that checks the attribute status of BOOT.INI, whatever it is, does the needed changes and re-applies the same attributes.

jaclaz

Jaclaz, there is a lot more of "usable" ideas in that script, but unfortunately (for me) I cannot make use of it, due to general lack of capabilities in this field :rolleyes:
The first script you made for creating boot.ini works fine too.

Is there any way to get the proper arcpath and amend or create a new boot.ini according to it?
Something like:
1. Scan for windows installations and get their arcpath
2. Find a marker file, which is present only in prepared for GUI part partition, and set this partition default
This will simulate pretty much the function of bootcfg command, which we need.

@Biohead have a look also at differences in both winnt.sif files, can you also post the folder structures on the CD and the USB stick?#

Regards,
ilko

Install Windows from USB, boot Linux, multiboot and a lot more with WinSetupFromUSB


#233
jaclaz

jaclaz

    The Finder

  • Developer
  • 14,373 posts
  • OS:none specified
  • Country: Country Flag

Is there any way to get the proper arcpath and amend or create a new boot.ini according to it?
Something like:
1. Scan for windows installations and get their arcpath
2. Find a marker file, which is present only in prepared for GUI part partition, and set this partition default
This will simulate pretty much the function of bootcfg command, which we need.


I don't seem to remember any simple way to get arcpath, but I'll look into the matter, maybe we can get something from the Registry.... :blink:

jaclaz

#234
AlexTitov

AlexTitov
  • Member
  • 4 posts
Greetings and thanks to jaclaz and porear who started that work, to ilko_t who joined later, to cdob who added drops of spices (as wise advices in right moments) and to Halfwalker who started that topic :hello:

I found out that MsDosInitiated parameter influences $WIN_NT$.~?? directories deletion.
I.e. if you change \windows\system32\$win_nt$.inf file this way before GUI portion of setup:

\windows\system32\$win_nt$.inf
[s]msdosinitiated = 1[/s]msdosinitiated = 0
then $WIN_NT$.~?? directories will not be deleted after setup.
So you may avoid directory renaming.

Though read-only stick protection is still necessary: I failed to use that msdosinitiated trick for text portion of setup :( Windows refuses to search for files at hdd and asks for setup cdrom.

#235
jaclaz

jaclaz

    The Finder

  • Developer
  • 14,373 posts
  • OS:none specified
  • Country: Country Flag
@AlexTitov

Good find! :)
Another little step towards perfection. :thumbup

@all
About the arcpath thingy, I had a look but it is not an easy thing at all.

What we actually need would be the behaviour, under Recovery Console, of the
map arc

command, which is very fast and has an output which is something like:
C: FAT32 500MB multi(0)disk(0)rdisk(0)partition(1)
D: FAT32 800MB multi(0)disk(0)rdisk(0)partition(2)
E:					  \Device\CdRom0

I tried a few of the (less known) utilities that come with XP, but could not find any that gave the wanted results in an easily "parsable" form.

The only one that gave good results is the dmdiag.exe that comes from the Resource Kit (but that is downloadable) as either "Windows XP Service Pack 2 Support Tools":
http://www.microsoft...61-BA8011FABF38
or as dmdiag.exe (this is the W2K tool, but should work as well):
http://support.micro...kb/927229/en-us
that outputs all the symbolic names of various disks and partitions, i.e. info enough to recreate an arcpath.
Still there is the need to test it's output, unlike, as I did, on a normal working system, in the possibly "reduced" environment in which it is expected to re-create the arcpath.

Another possibility could be some clever working with the output of diskpart, but again one has to check if it works when we need it, and the parsing is definitely not easy.

I am still loking for some small nifty third party utility that may be easier to use, so please, if any one has ANY idea, post it to the thread. :)

jaclaz

#236
ilko_t

ilko_t

    MSFN Addict

  • Super Moderator
  • 1,722 posts
  • OS:none specified
  • Country: Country Flag
I have found a small utility, which does pretty much the job we need- CHKBTINI, which comes with 16 and 32bits versions. I have just tested it and it works fine, however with very limited options.
It can fix only errors or discrepancies in rdisk(X)partition(X), if multi(X), disk(X) are wrong or signature part is present it cannot fix it, but these parts are created properly anyway and signature is avoided by not using mapping.
In summary- using direct chainloading creates boot.ini like
multi(0)disk(0)rdisk(1)partition(1)\WINDOWS

and the utility fixes it to:

multi(0)disk(0)rdisk(0)partition(1)\WINDOWS

when launched during GUI part. If only 2 lines are in boot.ini- default and under "operating systems" it changes both lines, if there are more than 1 line under "operating systems" it changes only "default" line. On the test system it works just fine, but on my working system it cannot find the windows partition, listing it as NON-NT PRIMARY PARTITION and skips it, 1 NTFS primary partition which is active with NT boot sector, and 3 NTFS logical partitions, I need to test why it skips it. BOOT.INI can be system/read-only, it's not a problem.

A little drawback, if a proper boot.ini is present and no mapping is used TXT Setup may not see windows installation to be repaired, I'll test this further.

@AlexTitov- welcome :hello: and thanks for info.
Idea- $win_nt$.inf could be changed during GUI part, lets say by a script, launched at T-9 instead of boot_ren.cmd, will jaclaz or cdob create something to test with?

ilko

Edited by ilko_t, 01 July 2007 - 01:34 PM.

Install Windows from USB, boot Linux, multiboot and a lot more with WinSetupFromUSB


#237
jaclaz

jaclaz

    The Finder

  • Developer
  • 14,373 posts
  • OS:none specified
  • Country: Country Flag
Interesting. :)

For the record, the "multi" syntax is a derivative of the "scsi" one or whatever, in any case,
multi is ALWAYS multi(0)
and
disk is ALWAYS disk(0)

reference:
http://support.micro...b;en-us;q102873

MULTI(X) Syntax
The MULTI(X) syntax of the ARC path is only used on x86-based computers. In Windows NT version 3.1 this path is only valid for IDE and ESDI drives; in Windows NT version 3.5, 3.51 and 4.0 it is valid for SCSI drives as well.

The MULTI() syntax indicates to Windows NT that it should rely on the computers BIOS to load system files. This means that the operating system will be using interrupt (INT) 13 BIOS calls to find and load NTOSKRNL.EXE and any other files needed to boot Windows NT.

The X, Y, Z, and W parameters have the following meaning:


• X is the ordinal number of the adapter and should always be 0 (see the text below for the reason).
• Y is always 0 (zero) if the ARC path starts with MULTI(), because MULTI() invokes the INT 13 call as described above and therefore does not need the DISK() parameter information.


so THAT is not the problem. ;)

However, if we define a "standard" for our install, it can be done in batch, no problem, it is when there are multiple \WINDOWS directories on different partitions that the problem might be tricky to resolve, though I am not yet done with this....


jaclaz

#238
porear

porear

    Newbie

  • Member
  • 49 posts
Hey guys! Sorry for a slightly OT post, just wanted to say hi and I am excited by your success. I have not been on here in a while, the new little man in our house has obviously changed our lives quite a bit. I am looking forward to finding some time to try out the ilko_t method, thanks very much to you and cdob, and of course jaclaz, who has been an excellent mentor in this whole process. :thumbup

#239
jaclaz

jaclaz

    The Finder

  • Developer
  • 14,373 posts
  • OS:none specified
  • Country: Country Flag
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). :thumbup

jaclaz

#240
ilko_t

ilko_t

    MSFN Addict

  • Super Moderator
  • 1,722 posts
  • OS:none specified
  • Country: Country Flag
Hi porear, welcome back :)


...If I get it right, with this latest one, since there is no drive "exchange" grub4dos is only needed to chainload setupldr.bin.

If you think it might be of use, I could follow cdob's idea and get from the FAT12 bootsector of the first of the install floppies the code for invoking setupldr.bin instead of NTLDR and prepare an easy way to patch any FAT16 or FAT32 bootsector (for NTFS it might prove to be tricky).
We could use a NTLDR and add to it an entry to direct chainload such a patched bootsector....

The idea came from this post of yours and wimb's posts in 911cd.net about loading io.sys via boot.ini.
Saved a copy of USB stick bootsector with HDHacker, hexedited it and changed NTLDR to STLDR, saved it on stick as bootsect.dat, rename setupldr.bin to stldr, add in boot.ini

c:\bootsect.dat="TXT Setup"

TXT mode worked just fine, GRUB is no longer needed, unfortunately the new boot.ini on the hard drive gets multi(0)disk(0)rdisk(1)partition(1)\WINDOWS, I was hoping that when started directly by setupldr.bin that may change the order, but no, modification is still needed.

Regards,
ilko

Install Windows from USB, boot Linux, multiboot and a lot more with WinSetupFromUSB


#241
jaclaz

jaclaz

    The Finder

  • Developer
  • 14,373 posts
  • OS:none specified
  • Country: Country Flag

Saved a copy of USB stick bootsector with HDHacker, hexedited it and changed NTLDR to STLDR, saved it on stick as bootsect.dat, rename setupldr.bin to stldr, add in boot.ini

Well, you missed my post here:
http://www.msfn.org/...o...1384&st=218

And the batch I wrote:
http://www.boot-land...?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 :whistle:, 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....ot/editbini.htm
http://www.goodells....ot/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? :unsure:

If yes, I think I can jolt it down in batch quite easily.....


jaclaz

#242
ilko_t

ilko_t

    MSFN Addict

  • Super Moderator
  • 1,722 posts
  • OS:none specified
  • Country: Country Flag

Well, you missed my post here:
http://www.msfn.org/...o...1384&st=218

And the batch I wrote:
http://www.boot-land...?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 :whistle:, I guess that changing loader in bootsectors is an activity that very few people do)


Shame on me :blushing:, my memory is so short, I even downloaded that script when you posted the link here, but completely forgot about it. Yesterday I was reading wimb's ideas and though "why not try this on Xp from USB?" and it worked. Apologies for the ignorance.

About the arcpath...

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? :unsure:

If yes, I think I can jolt it down in batch quite easily.....


jaclaz

I think that should do the trick, we need to change only rdisk, the rest is always OK, however I am not sure what the situation will be on mixed SATA/ATA disks environment.
Mind you when preparing the script to think about a situation when another XP exist, and a second copy is being installed. In this case SETUP will preserve the old lines, will change the default line and add a new one under [operating systems], am I right? In this case will you be able to keep the old line(s) and amend just the 2 new lines?
I haven't had spare time to experiment with CHKBTINI, will do it as soon as I can, it may be just enough to fix boot.ini when run before the end of GUI part.

Install Windows from USB, boot Linux, multiboot and a lot more with WinSetupFromUSB


#243
wimb

wimb

    Senior Member

  • Developer
  • 679 posts

Well, you missed my post here:
http://www.msfn.org/...o...1384&st=218

And the batch I wrote:
http://www.boot-land...?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 :whistle:, I guess that changing loader in bootsectors is an activity that very few people do)

Already sometime ago I tried your script, but was not able to use it.

#244
wimb

wimb

    Senior Member

  • Developer
  • 679 posts

The idea came from this post of yours and wimb's posts in 911cd.net about loading io.sys via boot.ini.
Saved a copy of USB stick bootsector with HDHacker, hexedited it and changed NTLDR to STLDR, saved it on stick as bootsect.dat, rename setupldr.bin to stldr, add in boot.ini

c:\bootsect.dat="TXT Setup"

TXT mode worked just fine, GRUB is no longer needed

Good to hear that TXT-mode Setup can be added to boot.ini Menu and that GRUB4DOS is no longer needed.
I have tested it and everything is OK :)

Launching TXT-mode Setup Windows XP via boot.ini has been added
as one of the boot options in my post #5 in 911cd.net
http://www.911cd.net...showtopic=20036

The MultiBoot USB-stick is becoming more and more versatile
with all the new boot options via boot.ini Menu :thumbup

Regards, wimb

Edited by wimb, 10 July 2007 - 06:28 AM.


#245
jaclaz

jaclaz

    The Finder

  • Developer
  • 14,373 posts
  • OS:none specified
  • Country: Country Flag

Already sometime ago I tried your script, but was not able to use it.


Well, this does not help much in correcting it (if needed ;)), does it? :unsure:

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:

[Boot Loader]
Timeout=5
Default=multi(0)disk(0)rdisk(0)partition(5)\WINNT
[Operating Systems]
multi(0)disk(0)rdisk(0)partition(5)\WINNT="Microsoft Windows 2000 Professional IT" /fastdetect
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Professional" /fastdetect
multi(0)disk(0)rdisk(1)partition(1)\WINDOWS="Microsoft Windows XP Home Edition" /fastdetect
multi(0)disk(0)rdisk(0)partition(2)\WINDOWS="Microsoft Windows XP" /fastdetect
C:\Bootsect.w98="Windows 98 Command Line" /win95
C:\BOOT\FDOS1440.bin="Test boot"


The result when modified by the new install, let's say on first hard disk, partition 3, will be:

[Boot Loader]
Timeout=5
Default=multi(0)disk(0)rdisk(z)partition(3)\WINDOWS
[Operating Systems]
multi(0)disk(0)rdisk(0)partition(5)\WINNT="Microsoft Windows 2000 Professional IT" /fastdetect
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Professional" /fastdetect
multi(0)disk(0)rdisk(1)partition(1)\WINDOWS="Microsoft Windows XP Home Edition" /fastdetect
multi(0)disk(0)rdisk(0)partition(2)\WINDOWS="Microsoft Windows XP" /fastdetect
C:\Bootsect.w98="Windows 98 Command Line" /win95
C:\BOOT\FDOS1440.bin="Test boot"
multi(0)disk(0)rdisk(z)partition(3)\WINDOWS="Microsoft Windows XP Professional" /fastdetect


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:

[Boot Loader]
Timeout=5
Default=multi(0)disk(0)rdisk(z-1)partition(3)\WINDOWS
[Operating Systems]
multi(0)disk(0)rdisk(0)partition(5)\WINNT="Microsoft Windows 2000 Professional IT" /fastdetect
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Professional" /fastdetect
multi(0)disk(0)rdisk(1)partition(1)\WINDOWS="Microsoft Windows XP Home Edition" /fastdetect
multi(0)disk(0)rdisk(0)partition(2)\WINDOWS="Microsoft Windows XP" /fastdetect
C:\Bootsect.w98="Windows 98 Command Line" /win95
C:\BOOT\FDOS1440.bin="Test boot"
multi(0)disk(0)rdisk(z-1)partition(3)\WINDOWS="Microsoft Windows XP Professional" /fastdetect


Am I correct?
What happens with SATA drives?

jaclaz

#246
wimb

wimb

    Senior Member

  • Developer
  • 679 posts

Already sometime ago I tried your script, but was not able to use it.


Well, this does not help much in correcting it (if needed ;)), does it? :unsure:

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.


I have used your script and was able now to use it successfully !

In Boot-land Forum http://www.boot-land...?showtopic=2362
is described the solution of the problem I had on first use of the script.

#247
ilko_t

ilko_t

    MSFN Addict

  • Super Moderator
  • 1,722 posts
  • OS:none specified
  • Country: Country Flag

....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:

[Boot Loader]
Timeout=5
Default=multi(0)disk(0)rdisk(z-1)partition(3)\WINDOWS
[Operating Systems]
multi(0)disk(0)rdisk(0)partition(5)\WINNT="Microsoft Windows 2000 Professional IT" /fastdetect
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Professional" /fastdetect
multi(0)disk(0)rdisk(1)partition(1)\WINDOWS="Microsoft Windows XP Home Edition" /fastdetect
multi(0)disk(0)rdisk(0)partition(2)\WINDOWS="Microsoft Windows XP" /fastdetect
C:\Bootsect.w98="Windows 98 Command Line" /win95
C:\BOOT\FDOS1440.bin="Test boot"
multi(0)disk(0)rdisk(z-1)partition(3)\WINDOWS="Microsoft Windows XP Professional" /fastdetect


Am I correct?
What happens with SATA drives?

jaclaz

Yep, that's it.
About SATA drives- if it is a mixed environment- SATA+ATA, USB stick would be listed fisrt when hard drives are detected by TXT Setup, if one plans to install on ATA when SATA is present, SATA disk must be disconnected or controller disabled, and vice versa, if installation is on SATA and IDE (no matter CD or HD) is present it must be disconnected/controler disabled. This might be BIOS dependant.
Therefore SATA/ATA shouldn't matter for script's functionality.

ilko

Install Windows from USB, boot Linux, multiboot and a lot more with WinSetupFromUSB


#248
wrayal

wrayal

    Junior

  • Member
  • Pip
  • 54 posts
Hey guys,
I've been following all the stunning progress you guys have been making here - very impressive! I had one other suggestion though, that might work. If you read uberplay's OEM guide (http://uberplay.org/.../oemguide3.html), it demonstrates how it is possible to use sysprep + vistaPE to install any version of windows for which a sysprep exists. Notably, it does a vista-style partitioning system I believe, then simply installs your carefully setup system - you can even integrate all sorts of drivers, hotfixes and programs very easily, and with a faster install time than nlite gives. As vista can easily be installed from a USB disc, I imagine this can? Has anyone tried this?

Wrayal

#249
jaclaz

jaclaz

    The Finder

  • Developer
  • 14,373 posts
  • OS:none specified
  • Country: Country Flag
Ok, here is the tentative :rolleyes: 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? :unsure:) 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

Attached Files



#250
wimb

wimb

    Senior Member

  • Developer
  • 679 posts
I have been testing binifix.cmd and got:

C:\>binifix.cmd
Drive is C:
Source is "C:\BOOT.INI"
Druk op een toets om door te gaan. . .
DefaultEntry is
EntryDesc is
Timeout is
4==scsi niet verwacht op dit moment.
C:\>
Is not working yet, approach is interesting, will try to find source of problem.

wimb

Edited by wimb, 11 July 2007 - 11:07 PM.





0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users



How to remove advertisement from MSFN