Jump to content


  • Posts

  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    United Kingdom

Everything posted by ilko_t

  1. Can you try again? You must have started downloading when I was updating the web site.
  2. Version 1.0 released which can be downloaded from here. Apart of the missing beta in the name, there are a few important changes since beta8: Ability to add multiple Windows Vista, 7, 8, Server 2008/2012 sources from ISO file as a source. Use the same option to add PE2 (Vista/Server 2008) and above based utility. Thanks to synchronicity for his amazing wimlib project.Ability to add almost any Linux based ISO which uses hybrid cd-rom/hard disk mode, credits to cdob . Refer to this page for a non exhaustive list of tested ISOsAuto-format option when used with NTFS would do its best when formatting the disk, to avoid fragmented large files on this volume later on by moving $MFT at the beginning of the partition. This way $MFT zone remains at the beginning of the volume and there should be way more contiguous space available large files to occupyDPMS updated to DPMS2, thanks to Stevethe command prompt window during GUI mode of XP/2000/2003 setup is now hidden, thanks to cdob. It’s needed to keep the USB drive mounted throughout the GUI mode of setupadded ability to copy all log files to the relevant WINSETUP sub-folder during PE phase of NT6 (Vista and later) boot. Create an empty file debugme with no extension in the relevant sub-directory, e.g \WINSETUP\Win7x64\debugme, and all log files from the start of PE phase will be copied next to itoffer custom boot menu name when Linux/Other ISO is addedwhen XP/2003/2000 source is added and incorrectly the i386 folder is pointed as root directory, program uses its parent directoryupdates of the tools includedI've also modified the first post since it became quite outdated. Versions would be from now on in the form of X.Y. Honestly, I'll miss those betas The program now also has it's own web page, with some hopefully useful info and download links - www.winsetupfromusb.com .
  3. Reinstall grub4dos in MBR or PBR. There is grubinst_GUI.exe tool included in the package. Or use BootIce. I guess Vista setup, or some other program later on put back regular NT MBR or PBR, wiping out the grub4dos one. If you are using the old 0.2.3 version, I'd highly recommend you to redo the USB disk with the latest version announced: http://www.msfn.org/board/topic/120444-how-to-install-windows-from-usb-winsetupfromusb-with-gui/
  4. You should refer to Microsoft requirements for each OS you're installing, but in any case 2GB should be well above the recommended minimum. As already pointed out, prior to starting each installation, there is no special requirement, or it's well below the ones from the manufacturer.
  5. It entirely depends on what are you going to start from this USB stick and its requirements- windows setup or whatever. The initial part with the grub4dos boot manager does not have any special requirements, but what is going to be started might have. Is that what your question was about?
  6. I consider it announced when I post to a link and info in the first post as well as new post, announcing that there is new version. Any other version floating around is most likely one of the many work-in-progress versions, just my understanding. All other points are already being taken care of, apart for the new competition
  7. Jaclaz, these are not announced versions and naming is just temporary. Shared only for people who need to use the new options and get going quickly before a new version is announced and who want to help with testing. There is no "beta" in the version I posted. Finishing off a simple website to resolve the issue with download links and help files as well. As for the competition- I'd not agree to second or third place. It's got to be either everything or nothing. Off to working on gama17
  8. Hmm ... my results ? Should be working fine now. The version Jaclaz has is a bit older one.
  9. Here is the most recent version: Win Setup_1-0RC4.7z Win Setup_1-0RC4.zip
  10. What did not work? Care to give more details? There were 3 solutions proposed.
  11. Prepare the USB disk with WinSetupFromUSB 1.0 beta8. Replace \DPMS\DPMS.iso with this file: https://copy.com/2YwNdBNDqrHR Start from USB. First select "Auto-detect and use F6 SATA/RAID/SCSI Driver", then continue as usual with First part of Windows Setup. Or integrate in your source BTS mass storage driver pack, making sure Text mode option is selected and redo the USB disk: http://www.driverpacks.net/docs/beginners-guide-windows-xp Or integrate the appropriate single SATA/AHCI driver in your source using nLite for example: http://www.komku.org/2007/11/integrate-driver-into-windows.html
  12. Yes, you can. If using 1.0 beta8 remove > nul redirections in intrd lines in menu.lst, or use newer grub4dos version. http://reboot.pro/topic/17875-redirecting-to-nul-after-kernel-line
  13. There are many options to format the USB disk. If the auto-format option (recommended) did not work, you can experiment with RMPrepUSB options. Not sure why that is relevant. When do they come into play? Oops, missing EHCI drivers in SP0, but program expects them and adds records for them. When booting Setup complains for missing usbehci.sys. Telling you all that to get you going quickly.
  14. http://flashboot.ru/files/file/2/ http://www.computerbild.de/download/WinSetupFromUSB-4353983.html
  15. Are both winnt.sif identical? I recall there was an option in winnt.sif which makes Setup to ignore migrate.inf. Added: It is oempreinstall=yes , according to this article: http://support.microsoft.com/kb/234048 Whether this applies for XP/2003 I haven't tested.
  16. Another solution beside the proposed ones- if you extract that ISO in a folder, extract I386\txtsetup.si_ to I386\txtsetup.sif and use WinSetupFromUSB 1.0 b8 you should get RC working. A plus is that upon launching it hard disks will be swapped so the internal ones are first and USB last, which would also help when using RC utilities manipulating MBR/bootsector/boot.ini. Have to use XP SP2/3 sources, the non-SP one doesn't include USB drivers.
  17. Actually the issue is that in QEMU and VirtualBox the USB stick/disk is emulated as internal IDE/SCSI disk. Drive letter is different because migrate.inf has records for removable disk in your case and the emulated one is fixed, but what breaks Setup is that source is not prepared with such setup in mind, from internal disk.
  18. Not sure I can now troubleshoot this better than you...Just in case- is the USB stick tested for real size? http://www.rmprepusb.com/tutorials/-fake-usb-flash-memory-drives It may also be a good idea to keep the antivirus software off while preparing the USB disk.
  19. I have just finished a test installation of XP x64 in VMWare Player, booting from USB. USB stick prepared with WinSetupFromUSB 1.0 beta8. Winnt.sif very similar to yours. Windows directory changed to XP in txtsetup.sif as in yours. NLite.cmd, added to AMD64 alongside entries to be copied in txtsetup.sif, slightly modified to: @echo offTimeOut /T 40for /f "tokens=3" %%i IN ('reg query HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Setup /v "SourcePath" ^| findstr "REG_SZ"') do set SOURCE=%%iecho %SOURCE%pause::CMD /R %Source%Run1_XP-64.bat::%SOURCE%\Tweaks\Tweaks.bat::%SOURCE%\Drivers\kxdrv3550-x64-full.exeEXITAt first logon %SOURCE% is displayed with a proper path to setup files- W:\WINSETUP\XPpSP1x\ . NLite.inf was not used, is it executed from cmdlines? In short- if there were any updates or add-ons they should have run just fine. What version of WinSetupFromUSB did you use? Try 1.0 beta8 if you haven't. What is drive letter of USB disk during GUI mode, you can see it in %SystemRoot%\WinPreSetup.log or in %SystemRoot%\System32\$winnt$.inf. What is drive letter of USB disk at first login, did it change? What is source path value in HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Setup after first logon? Is there any discrepancy? Did you test on real hardware?
  20. Can you attach nlite.cmd and nlite.inf? I have removed the attachment in your previous post because of the few entries in winnt.sif which should not be public.
  21. My best guess is that some customizations use hard-coded paths. Please put in a zip archive and attach it here winnt.sif, removing any sensetive information from it, txtsetup.sif, and any RunOnce or whatever custom scripts there are in the source.
  22. Just add it, there is no special way, both set of files can coexist safely.
  23. Migrate.inf, which is responsible for the drive letters at text mode, was made for the removable USB disk which was being prepared. VirtualBox emulates and boots USB drives as fixed disks. If you were using USB fixed(hard) disk , I guess drive letters would remain as expected. You may test in VMWare Player, boot from a PLoP CD, connect the USB disk to the virtual machine, select boot from USB in PLoP. This is as close as possible to real USB boot. There is also BIOS for QEMU which also supports USB boot.
  • Create New...