Jump to content

ilko_t

Patron
  • Posts

    1,720
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    United Kingdom

Everything posted by ilko_t

  1. The problem is not new. It could be done this way, but I'd rather keep them in separate folders, in case someone uses different sets/versions of DP for 2000, XP and 2003. If disk space is a problem- they could be moved to root manually and setup.cmd adjusted, or in case of NTFS- use hard links with the included DFHL.exe. Need more feedback from guys using BTS and USB setup with multiple sources.
  2. Nice, slowly, but progressing, probably nearly done Hopefully someone will join the game.I am still curious if ARC path is generated, what ARC path Windows setup would accept and can grub4dos mapping make the USB stick as multi(0)disk(0)rdisk(X)partition(Y). The ~BT & ~LS method has number of limitations, so I'd rather not go too deep in this direction.
  3. I'd try the modified ntdetect.com- Q3/A3: http://www.msfn.org/board/faqs-t116766.html How did you map the stick- map (fd0) (hd0) or (hd0,0) ? Next could be trying the small ISO method and BootDevice/SetupSourceDevices "multi(0)disk(0)fdisk(0)" and no mapping. Actually the small ISO is needed just to get around the improperly generated boot.ini at the end of Text mode. For experimenting you can dump entire contents of the CD to a folder, chainload setupldr.bin in it directly and amend txtsetup.sif with the relevant BootPath, BootDevice, SetupSourcePath and SetupSourceDevice. BTW this method should work as Setup loads completely from an emulated CD: http://www.msfn.org/board/7-t137714.html
  4. Or said the other way around - dummydisk/cfadisk with removable disk might get you going from the second partition on USB stick, given it's formatted in acceptable by XP way, but this would not help in solving your problem with the USB hard disk, which should be something to do with the partitioning. Last few days I've done numerous installs from 2nd and 4th partitions on USB hard disk using this method, all worked just fine. Having 4 primary partitions, regular NT5 bootsectors and grub4dos MBR, drive initially partitioned with XP Disk management. If you write a few steps how to partition and format it in a similar like in your setup, I could join the game. Idea- prepare the USB stick in the traditional way, attach the USB disk as well, boot setup from the USB stick, might need to play a bit with the proper ARC path or grub4dos mapping. How does setup display the USB hard disk on the partitioning screen? Which partitions are visible? What's the partition number displayed for each of them?
  5. RMPrepUSB and Bootice both have an option to format in USB-ZIP mode. Could you try them and report if their formatting works too? As I get it now, your stick is formatted in a way, so it's both bootable and capable to be mapped as a hard disk. Next would be to attempt to complete Setup start, you up for it? Thanks for all the patience and cooperation by the way, this really helps. Jaclaz, crossposting
  6. New beta uploaded, refer to the first post for list of changes and download link.
  7. Lets say it clearly- this program is NOT (yet) intended to install Windows ON USB disk. It's purpose is to install Windows FROM USB disk.
  8. Nice progress At some point I got lost, what's different compared to the initial attempts?
  9. fatih, did you try to install Window ON the USB stick? On th epartitioning screen what did you select, where to install Windows?
  10. fatih, how was it formatted before?
  11. Try using 8.3 file names, e.g. \WIN_SETUP\XP_Home_OEM\ --> \WINSETUP\XP_H_OEM\ Since MCE setup boots to somewhere, USB disk is seen as hd0, which is as expected. Try also a regular NT MBR and bootsector, and launch grldr by renaming it to ntldr ot bootmgr, depending on your bootsector. At start of Setup there seem to be number of checks, it may panick by weird/unknown MBR or bootsector. For multiple VLK/OEM/Retail versions this might be useful to you: http://www.msfn.org/board/install-winxp-oe...mb-t140351.html But do it once you get everything else working
  12. Two options I can think of: 1) Wrong BootDevice and BootPath in txtsetup.sif in the ISO file, amend accordingly. 2) USB stick seen as floppy, join the party: http://www.msfn.org/board/2-t140479.html
  13. You most likely have the same problem like this one:http://www.msfn.org/board/2-t140479.html Check in your BIOS for option to emulate USB stick as HD/hard disk.
  14. I don't get you here, are you saying to modify the source, before it's copied to the USB disk? Don't think it's good idea. And to copy the whole source to a temp folder just to modify a few files is also overkill. Anothr modified file is BTS presetup.cmd, with the new path to OEM directory. On 2000, and XP/2003, both 32 and 64 bit? I am only worried if mountvol.exe works that early on all versions equally well. It should hide as soon as I start using the regular fake setup.exe, not the debug version which shows the cmd window. Currently, for troubleshooting, as at that stage the troubles are expected, the debug version is used. I recall something similar, will test again with a few sources and get back.
  15. Whats new, did you considered this: This would require significant change in code, plus there are a few changes in the source folder- winnt.sif and fake setup.exe. Wouldn't do it unless there is enough interest in implementing it. A lot of stuff is new, menu.lst creation is fixed, using short file names, excessive logging etc. Besides, there were just a couple of spartan reports for the previous beta As for what's new from 0.2.3- the whole method of installing: http://www.msfn.org/board/2-t139737.html Sure, it's actually in the to-test list
  16. Most likely setupldr.bin cannot find ntdetect.com. Try: map (fd0) (hd0,0) chainloader (fd0)/setupldr.bin or map (fd0)+1 (hd0,0) chainloader (fd0)/setupldr.bin
  17. Just another piece of puzzle, which is pushing me to find a similar machine and play a bit on it.
  18. Changes from which to which? Which one is the "second reboot", the GUI mode, or after it? You can place any versions of 2000/XP/2003 in the same partition, as many as you want using the beta WinSetupFromUSB (don't go beyond 99 thought ), and one of the Vista/7/server 2008 into the same partition. The other Vista/7/2008 must go in a separate partition, which should not be a problem since you are using USB hard disk. Vista and above cannot go into own folder, unless you launch first some type of Vista/7 PE, and start setup from cmd line executing setup.exe from the folder you placed the setup files.Have a look in the subforum, this has been discussed numerous times. At first page of this topic is also mentioned what's supported and what's not. Thanks In other hand- call for community participation- only for a few hours since beta2 was posted it was downloaded over 1000 times, and not a single feedback so far. I can hardly release a stable version without some help with testing and feedback, no matter if there were issues or not. Guys, come on, give a hand
  19. It's quite likely when setup loads from a floppy, to ignore BootPath directive, which works for CD and HD installs, and to look for the rest of the boot files in root. You can try copying biosinfo.inf to root of USB stick and see if error message changes to another file name. If that's the case, we need to figure out how to successfully map fd0 to hd1. Using the apparently proper multi(0)disk(0)fdisk(0) would not help much, unless we use root for holding all files. Not quite sure how would we point to the source files once reach the file copy stage, no wonder if there is something else hardcoded again, just as msdosinitiated=1 behavior Looking at microsoft support wouldn't help, most of this is undocumented at all, actually the whole project for installing from USB was developed mostly by experimenting, very often using random shots in the darkness PLoP is included by default in the next beta, which I should be posting in a few hours in the main WinSetupFromUSB thread.
  20. Lets go step-by-step. How is setup launched- grub4dos' grldr loads setupldr.bin, which looks on several places for ntdetect.com and txtsetup.sif. After ntdetect.com is executed and passed back the hardware information, txtsetup.sif is read. The directives BootDevice and BootPath tell setupldr where to continue loading files from, up to the EULA screen, or if disabled- to the partitioning screen. In your case we need to get past this point. After that SetupSourceDevice and SetupSourcePath tell Setup where to find the source files which will be copied, you have not reached this point yet, so those values should not be relevant. BootPath is the directory where I386 can be found, this is in the device, specified by BootDevice. For BootDevice we need to figure out what would be acceptable syntax. For USB disk seen as hard disks there is a proper ARC path created- multi(0)disk(0)rdisk(0)partition(X), since its the first booted device, and it's a hard disk. Using grub4dos mapping we can "swap" places with the internal hard disk, so Setup places boot files on the internal disk, which after "swapping" Setup thinks it's the boot device. Basically we amend the ARC path with this mapping. http://support.microsoft.com/kb/102873 For sticks seen as FDD, there might not be an ARC path created at all, or we missed the proper syntax, which should be something like these: multi(0)disk(0)fdisk(0) multi(0)disk(0)fdisk(0)partition(0) multi(0)disk(0)fdisk(0)partition(1) In this case, when seen as floppy, there is no need to "swap" hard drives, as our internal one is already the first internal hard disk, and boot files will go there. If you still have a working widnows on this machine, try WinObj, go to GLOBAL?? and find all symlinks to your USB stick, there will be several. Can you list them all here, even better with a few screenshots for complete view. Another shot- try changing all names, including directory names from WIN_SETUP to WINSETUP. Next change XP_Pro_SP2 or whatever you have to XP. You need to change directory names and BootPath and SetupSourcePath in TXTSETUP.SIF, also winsetup.lst. If none the above helps, we can try to put the first files windows loads on the USB stick, and try to boot them with various options in boot.ini, which would be on the USB stick. Another idea- try to create a single partition when formatting with RMPrepUSB or Bootice, if you created two. And another one- try launching PLoP first, the select USB, then try setup again, but with rdisk(1) values in txtsetup.sif and mapping in winsetup.lst.
  21. The log file is from 0.2.3, not from the beta version I gave you link to, did you try it at all? I do have something in mind to point you to that version. What partition are you installing on? Was it created in advance? Using what tool? Under what operating system? Describe your partitions with their sizes and file systems too. Can you attach these files from your source- D:\I386\TXTSETUP.OEM and WINNT.SIF, in the latter remove any sensible information such as serial number etc.
  22. Well done, thanks for reporting Next is Jaclaz to pull my ears for not using 8.3 filenames More interesting is why it matters in your setup, what file system was this USB disk formatted in?
  23. Did you move the radio button fixed/removable? You may also try the latest beta, which works in a slightly different manner: http://www.datafilehost.com/download-20d0545c.html
  24. I mean do you understand the changes we are making, so you can experiment on your own?
  25. Hmm, try: BootDevice=\device\floppy0 SetupSourceDevice=\device\floppy0without map entries in winsetup.lst. One if these combinations should work, there should be a way to do it Did you get the idea what we are changing?
×
×
  • Create New...