anyone know how to get an iso of 10 that fits on a DVD

Assuming the eMachines is legacy BIOS, because if it was UEFI you could boot from USB flash drive:

1. You would use the diskpart clean command to completely erase the HDD from the eMachines.
2. Convert MBR to make sure the drive is MBR.
3. Create a small, primary partition, 100 MB is sufficient, mark it as active, format as NTFS or FAT32 (NTFS is standard for legacy BIOS). This will be the system partition. Assign it a drive letter.
4. Create a second primary partition filling the rest of the drive. Format as NTFS. This will hold the OS. Assign it a drive letter.
5. Mount the ISO file containing the Winodws 32 bit OS. The mounted ISO file will get a drive letter.
6. Use the dism /apply-image command to apply the correct version (specified by the index #) to the second partition you created on the HDD.
7. Use the bcdboot command to write the boot files from the new Windows partition to the system partition.
8. Probably be a good idea to use the bootsect command found in the boot folder of the mounted ISO file to make sure the MBR is set up for booting on the eMachines hard drive.
9. Move the hard drive back to the eMachines computer.

NavyLCDR said:

Assuming the eMachines is legacy BIOS, because if it was UEFI you could boot from USB flash drive:

1. You would use the diskpart clean command to completely erase the HDD from the eMachines.
2. Convert MBR to make sure the drive is MBR.
3. Create a small, primary partition, 100 MB is sufficient, mark it as active, format as NTFS or FAT32 (NTFS is standard for legacy BIOS). This will be the system partition. Assign it a drive letter.
4. Create a second primary partition filling the rest of the drive. Format as NTFS. This will hold the OS. Assign it a drive letter.
5. Mount the ISO file containing the Winodws 32 bit OS. The mounted ISO file will get a drive letter.
6. Use the dism /apply-image command to apply the correct version (specified by the index #) to the second partition you created on the HDD.
7. Use the bcdboot command to write the boot files from the new Windows partition to the system partition.
8. Probably be a good idea to use the bootsect command found in the boot folder of the mounted ISO file to make sure the MBR is set up for booting on the eMachines hard drive.
9. Move the hard drive back to the eMachines computer.

Thanks, so all that can be done from within a running win10 64 bit PC?
That sounds very interesting

Be interesting to hear what happens

sdowney717 said:

Thanks, so all that can be done from within a running win10 64 bit PC?
That sounds very interesting

Yes.

NavyLCDR said:

Yes.

<br>

it's working so far


- - - Updated - - -

Apply Windows Image using DISM Instead of Clean Install

after this says do this bcd boot command, my drive is 'E' where the windows image is going onto
G:\Windows\System32\bcdboot G:\Windows

Is that it then?


- - - Updated - - -

8. Probably be a good idea to use the bootsect command found in the boot folder of the mounted ISO file to make sure the MBR is set up for booting on the eMachines hard drive.

what would be this command for mine?
Drive G: is source, E: destination, D: is the 100mb first partition

- - - Updated - - -

ok, doing something wrong, G: is the source, E: is where DISM copied all the windows files



- - - Updated - - -

ok, got it, was supposed to be E:
C:\Windows\system32>E:\windows\System32\bcdboot E:\
windowsBoot files successfully created.

- - - Updated - - -

the little 100mb partition called D:, is still empty,

so what to do next?

- - - Updated - - -

Well, I put it into the Emachines, I get
Disc Boot failure, insert system disc and press enter.

So what does that mean now?
Seems the drive is not bootable

- - - Updated - - -

I can boot the drive off the PC I imaged from, so it does boot.
It just wont boot on the Emachines, gives that error

It looks like you didn't use the correct bcdboot command. Assuming that D: is the 100mb partition and it is the partition you set as active, and assuming E: is the partition containing the new Windows, the command would be:

Code:

bcdboot E:\Windows /s D: /f BIOS

Obviously, E:\Windows needs to be whatever drive letter Windows was installed to, and the drive letter after /s needs to be the drive letter assigned to the 100mb system partition marked as active.

Is e active?

NavyLCDR said:

It looks like you didn't use the correct bcdboot command. Assuming that D: is the 100mb partition and it is the partition you set as active, and assuming E: is the partition containing the new Windows, the command would be:

Code:

bcdboot E:\Windows /s D: /f BIOS

Obviously, E:\Windows needs to be whatever drive letter Windows was installed to, and the drive letter after /s needs to be the drive letter assigned to the 100mb system partition marked as active.

thanks, on the PC where it boots, I have 2 win10 drives, and got a boot menu to select one of the 2, so yes I will try this command later.

makes sense as nothing was done with D: yet

- - - Updated - - -

SIW2 said:

Is e active?

yeah, dont know.

sdowney717 said:

thanks, on the PC where it boots, I have 2 win10 drives, and got a boot menu to select one of the 2, so yes I will try this command later.

makes sense as nothing was done with D: yet

- - - Updated - - -


yeah, dont know.

You should have set d drive as active (the small 100mb partition). The sequence of diskpart commands should have been:

Code:

diskpart
list disk
select disk # <-replace # with the actual drive number for the eMachines HDD
clean <-this will erase the disk selected above, make sure it is the eMachines HDD!
convert mbr
create part pri size=100
format fs=NTFS quick label="System Reserved" <-label is not really necessary, though
assign
active
create part pri
format fs=NTFS quick label="Win 10" <-label is not really necessary
assign
exit

##then you would determine what drive letters got assigned and after applying the Windows 10 image, the next command would be:##
bcdboot E:\Windows /s D: /f BIOS <changing E: and D: as needed to the correct drive letters

If you discover the small partition is not marked as active, you can set it active at any time:

Code:

diskpart
select vol d <-change d to whatever letter the small partition got assigned
active
exit
exit

ok, got the bcdboot done right, now onto the next part
G:\>bcdboot E:\Windows /s D: /f BIOS
Boot files successfully created.
G:\>

- - - Updated - - -

ok made sure it is active


- - - Updated - - -

now will test it again

- - - Updated - - -

well, no go.
IT goes through a bios boot loop. No message about the drive as in insert system disk, just loops and loops

recorded a video, something is still not right, all because it cant boot a usb.
Can you put the windows boot install on a hard drive instead of a usb?
Shared album - Scott Downey - Google Photos

- - - Updated - - -

Maybe the thing to do is wait till I have my other PC fixed where the Samsung Evo drive failed, then try to make a DVD+R on it to boot windows 10 install on the Emachine.