ilko_t

I won't be able to offer much support for Rufus and don't think Akeo comes often around, you may try here. You could prepare the USB disk again with WinSetupFromUSB and try again, links are in my signature. If that doesn't work, then use unmodified XP SP3 source and try the boot option "auto-setect and use F6 SATA/AHCI driver + Firadisk" to rule out messed up source. If again no luck, then integrate BTS mass storage driver pack in unmodified source, making sure Text mode option is selected. What it the exact model of this laptop?

First off- welcome to the MSFN forum. Assuming you are installing from USB disk, how was it prepared? Did you follow a guide (which one), used a tool (which one)...?

To add custom NTDETECT.COM when preparing XP/2003 source: DPMS boot menu, try the second option if the first one doesn't work: Is it better now?

Correct, as mentioned, version is determined from boot.wim, since it's extracted from the ISO file anyway and install.wim is too large to be extracted just to determine version.

Did you read my reply carefully? Please do so again.

Can you post [1].xml to see if detection was incorrect?

How did you replace NTDETECT.COM ? It's better to use the advanced option for the purpose. I'd try clean source with modified NTDETECT.COM and use the DPMS option + FIRADISK before starting first part of setup.

Version is detected from the strings in VERSION tags in [1].xml in boot.wim. Can you post this file to see if detection was incorrect. You'd also need to edit \Windows\System32\WinPEShl.ini with the new path in the boot image in boot.wim, typically image 2. Edit BCD store in \EFI\Microsoft\boot\ as well, it is the one used when booted in EFI mode. A side note, there is an advanced option to use custom folder and boot menu names for such sources, in case if you haven't noticed it.

I've had similar case (grubinst output "Should be a disk image", yours is "Unknown image type" ) on my computer recently and was going to dig further why that happens. It seems something (read Windows) changes the FBinst data at some point and grubinst no longer accepts the first 512 bytes as a valid MBR, hence the error. For a quick workaround- use the advanced option "Do not check and install grub4dos MBR", it should get you going, there won't be any checks if grub4dos MBR is present and install if not. In the next version it should be fixed.

@mraeryceos The software you are mentioning is still warez. MSFN board rules are strict about that. Period. Back to your problem- how was the flash partitioned last time? What Windows are you running the program on? Have a look ate FAQ #14 and post here a download link with the log files.

Yep, I was talking about the method which WinSetupFromUSB uses, since it was mentioned in the OP.

Actually the ISO file is mounted by ImDisk once PE is loaded, and does not have to be contiguous. In all latest versions none of the NT6 files has to be contiguous, grub4dos loads only bootmgr which does the rest- loading the relevant boot.wim etc. This method might have some disadvantages, e.g. not supporting heavily modified sources, having multiple boot.wim's but seems to be the most convenient way to have multiple sources of this type and works quite reliably.

I don't think there is any noticeable difference in speed. If you're in doubt, you could always test both ways and share your results.

WinSetupFromUSB updated to version 1.3, list of changes: Fixed bug when adding NT6 source with missing new line feeds in WinPEShl.iniFixed handling of NT6 sources with install.esdFixed bug with NT6 sources with EFI directory but no BCD file in itAdded Ei.cfg and CVersion.ini Removal Utilities in \tools\winisoutils directory should one needs those files removed from the NT6 source ISO fileWimLib updated to version 1.6.0 for compatibility with new WIM formats

It's by design, and been like this in all recent versions. The other options will be expecting sources as ISO files in next versions too. The plan is to have only one field to add sources and program to decide what the source is with help of user if its type cannot be determined automatically.

You are correct, in all newer 1.x versions an ISO file is expected as NT6 (Vista and later) source. There is no way to provide directory as a source.

I'll have this fixed in the next version which should be out soon, just need to accumulate more changes to release it. The problem with this source is that there is folder EFI but most likely there is no BCD file in \efi\microsoft\boot\ and program fails when trying to update it, since it's missing. I've added a few more checks which should eliminate such errors. Meanwhile, I think this source could also be added using the third option "Linux ISO/Other Grub4dos compatible ISO" if there are no files needed for the booted WinPE outside boot.wim. Thanks for reporting.

Please post WinSetupFromUSB.log file, and use only the Vista/7... option for this source. You can upload it to http://pastebin.com/ or http://www.datafilehost.com and provide download link.

The links cannot be opened, try some other web site.

You are using the option to add PE1, XP/2003 based, whereas your source considering its name seems to be PE3, Windows 7 based. Use the Vista/7.... option and provide path to the ISO file.

I don't quite understand your question, lost in translation. Vista and later setup currently works like this: BIOS/legacy mode: boot device-->MBR-->grub4dos is loaded-->bootmgr (reads BCD store)-->boot.wim -->install imdisk driver and mount the ISO file as virtual DVD-->start Setup EFI mode: FAT32 partition/efi/bootx64.efi (reads BCD store)-->boot.wim-->install imdisk driver and mount the ISO file as virtual DVD-->start Setup Typical EFI firmware supports FAT32, no NTFS. For NTFS and EFI, load a NTFS driver. Again:

Again, the image is copied as is, the whole ISO, it is not extracted. Have a look at the contents of <USB disk>\WINSETUP\W71\ or whatever the name of the directory is, there are boot.wim and WindowsXYZ.ISO. How do you fit larger than 4GB WindowsXYZ.ISO on FAT32?

One could always use any of the beta versions to add it the old way, I wouldn't add it as an option for now, unless there is lots of interest in such option.

ISO file size is 4 217 568 KiB x 1024 = 4 318 789 632 bytes. FAT32 maximum supported file size is 4 294 967 295 bytes, so everything is as it should be, the warning is correct, since the whole ISO file is going to be copied. You have the following options with this ISO: 1) Use FAT32 and 1.0 beta versions, which do not copy the whole ISO, but support only one source of this type. If you need EFI, it should need no further modifications if source is Windows 8.X 2) Use 1.0 and later versions and NTFS, multiple sources of this kind are supported, but no EFI support with NTFS, unless you load a NTFS driver, for EFI or motherboard manufacturer added NTFS EFI driver. http://www.rodsbooks.com/refind/drivers.html http://forums.mydigitallife.info/threads/46981-Install-Win8-Windows-8-1-UEFI-With-a-Over-sized%28over-4GB%29-install-wim

Program updated to 1.2, list of changes: Fixed bug where program running on Windows localized in other than English language would not add NT6 sourceImproved handling when program is placed and run from directories which contain special characters- `~@#$%^&()-+=,; Single quote – ‘ is not supported in program directory path and there is a check for thatAdded an advanced option for NT6 (Vista and later) sources to add Q-Dir File Explorer, which starts before Setup. This is useful to quickly browse disk contents and backup and restore files before launching Setup, rather than booting first in another OS to perform the same task. When Q-Dir is closed, Setup starts.BootIce updated to 1.3.2.1Download: http://www.winsetupfromusb.com/downloads/