ilko_t

Wow, nice, at last Did you complete setup? Did it pass the GUI mode using small ISO method?

Hi ilko_t, The BSOD stop code i got while installing Win XP pro x86 SP3 NL: 0x0000007B (0xF7916524, 0xC0000034,0x00000000,0x00000000) Thanks! Try the modified ntdetect.com:http://www.msfn.org/board/faqs-t116766.html You'd need to replace the one in the corresponding ISO file in WINSETUP directory, and just in case the one in I386 directory.

With 0.2.3 and former versions in case of fixed disk there is a filter driver used, which makes fixed disks to appear as removable, thus tricking Setup to put boot files on the internal disk. Other part is that USB disk is not checked for bootability, according to internal rules, thus no MBR/bootsector is chaned on the USB disk. Limitations as with every removable USB disk is that only first partition is visible. Just yet another workaround, not needed with the method used on 1.0.

I tried MountStorPE already, doesn't work that early. Haven't seen showdrive before, thanks.

@wwitthoff1 Look in the backup folder, all previous logs are cab archived there. Find the corresponding log file which has those errors. @KirSan When used 0.2.3 did you move the radio button FIXED/REMOVABLE? It should have been auto set to FIXED and should not be moved. With 1.0 beta did you check if you have setup.ex_ in \WINSETUP\XPpSP..\I386\ ? @Rotbard This would be quite sad if isn't working. Did you amend txtsetup.sif in the ISO file, not the original one on I386 folder? At start of GUI please type DISKPART in the cmd window and then "list volume" and "list disk". Is the USB disk listed, without drive letter? You may also try manually mounting the USB disk if it's shown in DISKPART output: mnt.exe Y: \device\harddisk0\partition1 dir Y:\ mnt.exe Y: \device\harddisk1\partition1 dir Y:\ ...Keep changing harddiskX if you have more disks or a USB card reader connected. Change partition1 to whatever partition source is in. Try also booting from the USB disk for the second part. Did the PC reboot couple of times at start of GUI, there a some changes made at each reboot. Did you let it reboot 2 times and see if it continues setup? As for the file copy speed in latest versions- yes, that's another benefit, since there are no write attempts involved, NTFS write cache does matter and different file systems perform with a similar speed.

A solution was found, see the last message here: http://www.msfn.org/board/2-t139737-page-20.html I've implemented these changes, along with some other in beta5, but am out of town for a few days and cannot test it in order to post it.

Did you try another USB stick?

Nic303- it's not about what you are putting on the USB stick. For some reason the program fails to install grub4dos MBR. This has nothing to do with what is being placed next on the USB stick. Can you zip and attach WinSetupFromUSB.log file in program directory? You may also try the following: 1. Format the USB stick with BootIce or RMPrepUSB 2. Close the program 3. Unplug the stick using safely remove hardware icon and plug it back in 4. Run the program again and select ONLY syslinux option. Ignore the warning about incompatible SysLinux and NTFS if you formatted in NTFS. 5. If you get again "Could not install grub4dos MBR"- close the program, zip WinSetupFromUSB.log file and attach it with your reply. 6. If you do not get that error, select Win7 source and continue, you should have successfully installed grub4dos MBR. Just in case- you did not try to run the program from within the 7z file, did you?

What's the error code?At what stage you got it? Did it happen on the same hardware where the other two worked fine? What's the hardware? Are the disks SATA? Do you have the drivers integrated if BIOS is in AHCI/SATA mode?

You will have to be more specific.

That's pity, quite Let's see if anyone responsible for forum maintenance/support replies.

Is there any progress with the forum links to a specific post issue? It quite helpful when you can point to a specific post, especially in long threads. Or if it is working, what's the easy way to do it?

Yes, strange indeed, left+right arrow key do the up/down select work. So I did see it somewhere, but not on boot-land README_GRUB4DOS.txt We do have configfile in winsetup.lst, but it's conditional to geometry(hdX) result, hence it seems ignored. Add "boot" as last line in each menu and everything goes back to normal:

Deleted test entries in boot.ini and left this: ; ;Warning: Boot.ini is used on Windows XP and earlier operating systems. ;Warning: Use BCDEDIT.exe to modify Windows Vista boot options. ; [boot loader] timeout=30 default=multi(0)disk(0)rdisk(0)partition(2)\WINDOWS [operating systems] multi(0)disk(0)rdisk(0)partition(2)\WINDOWS="Microsoft Windows XP Professional" /NOEXECUTE=OPTIN /FASTDETECT c:\grldr="Grub4dos" Run the program, gave admin privileges when asked and rebooted- no new entry in boot menu. Checked boot.ini- it was not modified. Win7 x64. Partition layoutand drive letters from 7: Boot.ini is on E:\ as seen in Win7. PLoP folder is present in C\Windows with 2 files inside.

I think you are not using the latest beta. In your case you'd need to edit presetup.cmd. Don't edit setup.cmd and TAGFILE in it.

I am working on this right now. Yep, search & replace %CDDRIVE%\WINSETUP\XPpSP2\OEM to %CDDRIVE%\OEM.The bolded part may vary depending on your source and if multiple similar sources were added.

For some reason AV vendors quite often falsely detect virus patterns in AutoIt compiled programs. When in doubt check online using multiple scanners: I'd click on the link you have "Reports as false positive..." B)

Thanks for the solution

It could be also because you are starting it from USB, thus additional kernel parameters may be needed for this particular machine, or other factors, not present when booted from a CD may matter. Sorry, I have no other hints, you've got plenty of them to try in the referenced link. And by the way, to be technically correct- it's Grub4dos, not GRUB, although grub4dos developers are also actively participating in GRUB2 developing

@NT Man I'd do the following: - chkdsk on the USB disk - compare MD5 sum for the ISO - change in BIOS SATA mode to IDE/compatible, if possible - test the memory modules, also by removing each of them if 2. - look at Ubuntu's forum for hints, additional kernel parameters may get you going, start with the ones mentioned here, several are posted: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/172937 - ask for help in Ubuntu's forum

Did you miss this post? Quick proof- just tested on motherboard MSI G31M3, 2 SATA disks in IDE mode, no option for AHCI/SATA. Upon changing boot order in BIOS, hard drive numbering changes too, no matter what port they are connected to, booting from USB using F11 hotkey. How would an average user know what his BIOS does, in order to select the appropriate entry? Which one it would be? The one shifting all internal disks one position up and USB disk last, or the desired disk mapped to hd0? One likes to manage boot via a boot loader, other prefers to use BIOS boot order. This is going to be a little mess, I'd stick with the default Setup behaviour, whatever BIOS provides as first internal disk, boot files go there. This is also well known and documented behaviour. Next would be Vista/7, behaviour is the same. There we cannot manipulate it, for now. An advanced user willing to take the other disk out of the equation should disconnect or disable that disk during setup, or amend entries manually. This goes to the help files. I 'd now rather focus on more important things to fix and add

What did you exactly do? You need to copy the ISO file manually and add the mentioned in that topic entries to menu.lst, according to Ubuntu version.

Meanwhile have a look here for Ubuntu, there are grub4dos entries for a few versions: http://www.boot-land.net/forums/index.php?...=5041&st=20

Quick proof- just tested on motherboard MSI G31M3, 2 SATA disks in IDE mode, no option for AHCI/SATA. Upon changing boot order in BIOS, hard drive numbering changes too, no matter what port they are connected to, booting from USB using F11 hotkey.

Thanks, so it works as expected. It will force them on the active partition on the second disk in this case. What happens if you use same entries and install to the first disk? How do you know that one is installing to first or second disk? I recall something seen on boot-land about the nested config files, have to search a bit. If it's still up Monday will post there to see what Tinybit and the rest of the band have in mind.Mind you, it's early stage. Other BIOSes may honor boot order and re-arange disk numbering. SATA/IDE mode may also matter.