Jump to content
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble

MSFN is made available via donations, subscriptions and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. Alternatively, register and become a site sponsor/subscriber and ads will be disabled automatically. 



ilko_t

Super Moderator
  • Content count

    1,720
  • Donations

    $0.00 
  • Joined

  • Last visited

Everything posted by ilko_t

  1. Here comes the first GUI for our little project. What it can be used for adding to your USB stick/disk: Multiple sets of Windows setup files- XP, 2000, 2003, Vista, WIndows 7, Server 2008, Windows 8, Server 2012, both 32 and 64 bit versions are supportedMultiple WinPE2 (Vista and above) based sources from ISO files such as Windows Defender Offline, recent Norton Ghost versions and PE (preinstallation environment) based PC manufacturers recovery disks.Single WinPE1 source, such as BartPE, UBCD4Win, LiveXP and similar WinBuilder projects, WinFLPC etc.Multiple Linux based distributions and utilities from ISO files- Debian, Ubuntu, Fedora, CentOS to name a few, this includes most Antivirus Rescue DisksMany other ISO images as long as they are compatible with grub4dos CD emulation, such as Ultimate Boot CD, Windows 95/98 and most DOS based utilities, Acronis and Paragon boot disks and so onSyslinux boot meny and optionally single source which uses Syslinux or Isolinux as boot loaderWinSetupFromUSB can also prepare Windows XP (2000, 2003) setup files to be installed onto a USB disk. I've put some FAQ and Tutorials. Here is a incomplete list of tested sources. If reporting problems, please attach your compressed log file (WinSetupFromUSB.log) and the exact steps to reproduce the problem. Thanks Warning: Several antivirus vendors detect the included in many versions setup.ex_ and setup_dbg.ex_ as viruses. This is false positive: http://www.msfn.org/board/topic/141734-virus-suspected-in-xp-inst-v047z/ You may need to turn temporarily off your antivirus protection when using the program. Hopefully AV vendors will respond at last to the numerous emails sent and take off those signatures. Downloads and changelog: http://www.winsetupfromusb.com/downloads/
  2. Would need to see the log files to be able to help. Details how to provide these are on the FAQ page, #14 - http://www.winsetupfromusb.com/faq/
  3. I'd say the drive is just faulty.
  4. Thanks Jaclaz, our friends from east keep bringing amazing solutions.
  5. FBInst code made by bean123 is much larger, requires ~8MB reserved space before the first partition and can't fit in the same sectors as standard or grub4dos MBR, so no option to simply put that code instead of a standard one. You can try replacing grub4dos with newer version which have USB drivers embedded, although as far as I recall this won't solve the issues with those weird BIOS-es which can't even find grldr. I kinda lost track if USB support was merged in the mainstream versions and how mature now it is. You may want to start from here: http://reboot.pro/topic/19883-improve-grub4dos-boot-speeds-by-using-the-046-usb-driver/
  6. I have done a few tests to measure copy speed during Text portion of setup. Here are the results: NLited XP source, 5251 files occupying 399.7 MB. After the copy part on destination drive are found 2850 files, occupying 476MB. Preparation made by WinSetupFromUSB 0.1.1, run on XP SP2 system, C2D 4300@2.9GHz. USB stick- Lexar JD Lightening 1100 1GB, which is relatively fast: In all cases stick was quick formatted using HP USB format tool 2.0.6. To check if USB write protection via migrate.inf plays role I tested without it as well. All tests performed intentionally on an old Celeron 1.7MHz/384MB RAM/VIA 266KM chipset, which supports USB 2.0 once the USB drivers are loaded. FAT16: Stick prepared for ~15 min. (899 secs.) Text mode copy part with USB write-protection- 4:10 Text mode copy part without USB write-protection- 6:13 FAT32: Stick prepared for ~21 min. (1253 secs.) Text mode copy part with USB write-protection- 12:58 Text mode copy part without USB write-protection- 7:15 NTFS: Stick prepared for ~4 min. (238 secs.) Text mode copy part with USB write-protection- 1:42 Text mode copy part without USB write-protection- 1:45 It really puzzles me why FAT32 is so slow compared to FAT16 If your system supports USB boot from NTFS formatted partitions AND you are not planning excessive usage of the USB stick in terms of write operations, where NTFS may wear it out (disputable with modern USB sticks), NTFS seems to be the way to go.
  7. You do not have to use it. Some other alternatives: http://www.winsetupfromusb.com/faq/#faq3 Consider this option as last resort. I guess you mean preparing the drivers hangs, not the actual Windows Setup, right? The DPMS script is from Chenall, the current main grub4dos developer, it was later modified by Steve, the author of RMPrepUSB. I wouldn't play with this script unless there is a trivial change needed. The script can be modified to pause every now and then, but this would be overwhelming for the average user, cannot be set as default behaviour. The information you provided, the driver names, is sufficient to troubleshoot the script. Just edit menu.lst or winsetup.lst using any text editor- Notepad++ etc. etc. Alternatively, there is advanced options button where you can set custom names for the source being added and its folder name on the USB disk. As above, you do not have to use the option for SCSI/SATA/RAID drivers. Thank you
  8. Grub4dos does not support EFI, thus under EFI only Windows versions supporting it are available.
  9. New version 1.5 was released. Updated to detect and support Windows 10 and Server 2012 and a few little bugs fixed when run on non-english locales.
  10. I think OP asked about the DPMS folder on the USB disk root, which folder contains DPMS.iso. You are talking abou the DPMS folder inside the ISO. I am aware of Cosmias, nice stuff! Currently I am reading as before, just not writing much, as spare time is very limited.
  11. Default files are used to auto move between the menus making default one the appropriate one. I.e. afer first part of XP setup is completed/booted, make the second one default boot menu, thus allowing unattended setup. Default file is for the main menu, windefault is for the NT5 (xp, 2000,2003) boot menu. I wouldn't play with those file unless you have a good reason to do so. DPMS.iso location can be changed, given that you ammend all file locations accordingly. @Jaclaz DPMS is Chennal's dpms.bat modified by Steve wrapped in an ISO file, only making use of driver pack mass storage, and I doubt their forum would be able to offer much help, unless it's a specific driver issue.
  12. Ohh, come on mate, you are an agent, should know stuff
  13. 3 OS on a USB stick

    Sorry, but I am clueless for a better answer to the question "what does boot first internal disk option do", but "it boots the first internal disk".
  14. 3 OS on a USB stick

    Bingo123, have you read carefully and tried the option? If yes, which part in the name is unclear or confusing? I am more than sure that figuring out what it does would not be a challenge for you, you just have to try.
  15. 3 OS on a USB stick

    There are several tutorials: http://www.winsetupfromusb.com/tutorials/ As well as FAQ page: http://www.winsetupfromusb.com/faq/ Read FAQ 2 and 10.
  16. 3 OS on a USB stick

    With both you can add way more sources. What made you think limit is 2? Are uou using latest versions?
  17. For such ISOs you could simply replace the ISO file with the new one in folder ISO and make sure it's not fragmented, say with the included WinContig in \files\tools\rmprepusb\wincontig. Same applies for Windows Vista/7/8 sources, given that boot.wim is the same. No need to defragment here. You may also need to edit menu.lst in root and correct the title and file names if they are changed.
  18. I wouldn't touch it, it is exactly as in the original bcd store. The only reason you see it is that there is a menu displayed, in the original configuration the same entry is no displayed, but booted right away. If it bothers you and you know what you are doing, you can use bcdedit, BootIce, or VisualBCD and edit bcd stores in \boot and \efi\microsoft\boot. http://msdn.microsoft.com/en-us/library/windows/hardware/ff542193(v=vs.85).aspx You'd need to use the /store parameter as well and point to the target bcd store, for both BIOS and EFI stores.
  19. Did you check the FAQ page given? I don't think I could explain better, unless the question is more specific...
  20. Which box in particular and which part about it in the given FAQ link needs clarification?
  21. Sorry, I meant the first disk, the 16 GB one.
  22. http://www.winsetupfromusb.com/faq/#faq7 In short- you can tick the no DPMS option to save ~50 MB, plus, it's for 32 bit drivers only. I think you'll have better luck preparing the second disk with the setup files and installing onto the same, with no other disk present. In case the previous advice didn't work.
  23. Are both USB disks the same type? What is the exact model? Try to format the target one with RMPrepUSB before launching Setup and leave it as it is during it.
  24. Try to delete all pattitions on the target disk and create new ones from within Setup. Is the "source" disk still bootable and intact after the procedure? Are all other disks invisible to the Setup, i.e. do you see only the 2 USB disks on the partitioning screen during Setup?
×