Jump to content
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. ×


  • Content Count

  • Joined

  • Last visited

  • Donations


Everything posted by ilko_t

  1. 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/
  2. Thanks Jaclaz, our friends from east keep bringing amazing solutions.
  3. 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-
  4. 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 provide
  5. Grub4dos does not support EFI, thus under EFI only Windows versions supporting it are available.
  6. 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.
  7. 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.
  8. 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
  9. 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".
  10. 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.
  11. There are several tutorials: http://www.winsetupfromusb.com/tutorials/ As well as FAQ page: http://www.winsetupfromusb.com/faq/ Read FAQ 2 and 10.
  12. With both you can add way more sources. What made you think limit is 2? Are uou using latest versions?
  13. 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.
  14. 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.
  15. Did you check the FAQ page given? I don't think I could explain better, unless the question is more specific...
  16. Which box in particular and which part about it in the given FAQ link needs clarification?
  17. 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.
  18. 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.
  19. 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?
  20. What did you exactly do? Did you install onto the same disk? How was it formatted, using what tool and what settings? You'd have to describe the exact steps you did.
  21. @submix8c You can't just install XP ro USB, it will bluescreen 0x7b at the first reboot... USB drivers boot order has to be fixed and monitored. Besides, you can't just install XP to the same or another USB if no internal disks are available, again 0x7b if only removable disks are present. This is also taken care of. In short- forget about winnt32 and unmodified source/setup files and procedure. WinPE is another beer, OP is looking for a portable full XP, not PE.
  • Create New...