ilko_t

This topic has been moved from "Install Windows from USB" to "Windows 7" discussions, hope that's the OS you need to deploy. Next time please post in relevant to your question subforum.

Why did you attach this file? It's only about Windows Setup, 2000/XP/2003 versions.infotronix, you asked about Linux Mint and an answer was given. Now you are talking about something which only you and the crystal ball know about. I have no clue what you are attempting, but do not expect us to be mind readers, nor expect from the program to magically convert and boot whatever ISO you throw at it. Open up a new topic, ask other questions if you need to add other stuff apart from Linux Mint and Windows setup and be as specific as possible. Read your answers, try, try again, read again, do not expect spoon feeding, try again then ask again in that topic if no luck.

Was the disk partitioned in advance? How did you do it? Can you delete all partitions during the first part, reboot, start first part again and create new ones ? You were already told how to do it, just a few posts above.

Rename the iso file to something including 'ubuntu', i.e. linux-mint-ubuntu-32bit.iso. Format the stick. Add linux mint first to the stick using the PartedMagic/Ubuntu option. Defragment the iso file in the USB stick\Ubuntu\ if fragmented using the included in \file\tools\WinContig\Wincontig.exe. Add the rest to the USB stick.

Use 1.0 beta7.Format the USB stick in FAT32, use the tools included. Select Windows 2000/XP/2003, point to the source directory. Select Parted Magic/Ubuntu/Other G4D compatible ISO, point to the Red Hat ISO file. Press GO. You may need to defragment the Red Hat ISO file once it's on the USB stick, use contig or wincontig. Use google to find links. WinContig is already included in WinSetupFromUSB directory\files\tools\WinContig. Once you boot Red Hat installer press enter for default boot options, further in the process select Hard Drive for Installation Method, select the usb device and for directory where the ISO is type ./ http://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/6/html/Installation_Guide/s1-installmethod-x86.html http://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/6/html/Installation_Guide/s1-begininstall-hd-x86.html

It's ok, but just in case test it in QEMU to confirm.

Is any of the subfolders empty? Does it happen if you select only BartPE/UBCD4Win ?

Good info Wimb, thanks. I wonder how RMPrepUSB and fbinst behave in such machines, does anyone have any experience? @LordX It would be helpful to test a few applications and see which one overcomes the boot problem on your machines. Do you want to help a bit? Do you have such machines around you?

Are there any files in E:\SetupFiles\UBCD4Win\BartPE\ ? Not in the subfolders, in BartPE. If not- put a dummy file, empty or whatever, doesn't matter. Seems like a bug, will be fixed, thanks for feedback.

No specific instructions. You'd need to find out what options work on those particular models. No need to format in advance either, RMPrepUSB would do that. To save time- do not put anything else on the USB, just experiment various format options and find out which one boots. To put grub4dos MBR the easiest way would be either to use again RMPrepUSB if you downloaded it separately, or select only SYSLINUX option in WinSetupFromUSB. Or use BootIce in \files\tools, select Process MBR and pick GRUB4DOS MBR, then INSTALL/CONFIG-->SAVE TO DISK. As for the BSOD on Dells- check the pinned FAQ topic, replace NTDETECT.COM in your source with the modified one. If stick is already prepared with the 1.0 betaX version- replace the one in the small ISO file in WINSETUP folder on your USB stick.

Thanks for the feedback.

In txtsetup.sif, SetupData section, there is OsLoadOptions, maybe that could be used to add an extra line, using something like \r\n or any other value which would make Setup write a new line, or it's just for the Text mode and ignored later on

What is on the screen at that point? Did you try not to slim it down too much?

What are contents of winnt.sif? Shouldn't $OEM$ folder be a subfolder of i386? http://support.microsoft.com/kb/314479

Look at the FAQ, , Q3/A3. Replace NTDETECT.COM with the modified one.

You do need to set msdosinitiated to 0, or Setup will be looking for the default ~BT and ~LS folders. As for the new error- if you do have the proper licensing and agree with EULA put in [data] section the following lines: As a side note- there are number of tested and proven to work applications and methods for the purpose, pick one from the pinned topics. There is no need to reinvent the wheel unless you want to study the matter. This is just one of the many issues you might hit. Next question would be what do I do with boot.ini, next is why my unattended settings do not work and so on. If you want to go further this path- please search in this subforum, you most likely will find answers of all the questions and issues you'd come across. All those have already been answered and taken care of in the referenced methods.

Did you follow instructions in this thread? Are you willing to experiment or need tested and working solutions? What are contents of winnt.sif? Hide the sensitive information in it and post it. Where did you place it? What did you change in txtsetup.sif? Where did you place it? Do you get this message at start of GUI mode or after initialization of Text mode, before displaying available disks? Did Text mode part complete without errors?

What's the BSOD error code, 0x0000007B or ... ?

The program dynamically changes setup.cmd according to the source used. Usbehci service and other ehci entries would be used if source is NOT 2000. There are other lines besides the one you mentioned which are adjusted.

USB services names in 2000 are different than those in XP/2003.

@Legorol You might find these topics interesting, basically covering most of what you have pointed out, if haven't read them yet: There is another glitch you have not encountered yet, described in those topics- USB hard disks and perhaps some card readers not detected, read no valid source during GUI mode of some Windows versions. Added: As for boot.ini- it's generated/amended at the very end of text mode. You may try to add another one via txtsetup.sif. Timeout will be reset to 0, or 1, can't recall exactly. User would need to start tapping F8 quickly when booting for GUI mode in order to get to the boot menu and select the custom entry, not the one added by Setup. Binifix.cmd is always an option too. As for the drive letter D- this is limitation, user might have another internal disk, or it could be already partitioned, or not partitioned, another reboot is required in the latter case. Fixed letter via migrate.inf works, but there are cases (USB sticks without serial number for example), when it does not, or machines wirh ParentIDPrefix starting with 6, or 8, not the usual 7. Not criticizing or something, just pointing out the issues we have already been through. Good work of yours so far

@majinzin When you finish repartitioning etc. and still get that error message correct the following files with the proper partition number: 1) winsetup.lst 2) txtsetup.sif in the small ISO file in WINSETUP folder, section SetupData 3) setup.cmd in \WINSETUP\XPpSP3\I386 , search for the line containing partition1 or simply redo the USB disk.

Where did you add the modified ntdetect.com ? If using WinSetupFromUSB 1.0X versions it has to be replaced in the small ISO file on the USB stick if it's already made, which is in folder WINSETUP, or just replace it in your source before using the program to create the stick.

I'd leave it as it is since it's working alright now.

Can you confirm that windows 7 x64 works fine from partition 2? Are all three partitions primary? Which one is active? Is there such? Can you rename ei.cfg to ei.cfg.bak in partition3\sources and try again?