Jump to content

WinNTSetup v5.3.4


JFX

Recommended Posts


Hello 'JFX'

 

Can 'WinNTSetup v3.6.1' install 'Win 8.1 Update1' in both 'BIOS/MBR' drive partitions and 'UEFI/GPT' drive partition without changing Partition scheme ?

 

 

1-

 

IC570854.jpg

 

 

 

2-

 

IC514408.png

 

 

I mean Can 'WinNTSetup v3.6.1' install 'Win 8.1 Update1' into 'Windows Partition' of both 'BIOS/MBR'  and 'UEFI/GPT' partition scheme without converting partition scheme ?

 

Please confirm if it works for both.................

 

 

Thanks...........

Link to comment
Share on other sites

Hi,

 

Are there any known issues with Win 8.1 Enterprise 32b?

 

I have used the great WinNTSetup 3.6.1 method before to successfully install Win 8 pro to USB HD.

 

I have now repeatedly and unsuccessfully tried with Win 8.1 Enterprise 32b with exactly same procedure, on same PC, to same USB HD.

Everything was double checked and looked fine (MBR,  BOOTMGR.PBR, BOOT PART)  and installation was reported as successful, but the first reboot to USB HD looped to a blinking prompt indefinitely.

 

Thanks for any help,

 

edborg

Link to comment
Share on other sites

Hi edborg,

 

no there are no problems with Win 8.1 Enterprise 32b.

A blinking cursor on the top left screen is usually cause by a BIOS and boot sector incompatibly.

 

If possible delete the partition and create a new one with some partition software.

Link to comment
Share on other sites

Thanks JFX for your prompt reply  :)

 

I have done that already, more than once, to no avail.

 

I have now run bootsect.exe /NT60 X: to rewrite the partition boot record with the bootsect.exe version included in WinNTSetup v3.6.1, to no avail either. :wacko:

 

I may have to try to rebuild from Win8 as my previous attempts (including the successful ones for Win8 pro!) were made from WinXP

 

edborg

 

Ediit:

I forgot to mention that the Win8.1 Enterprise 32b is the evaluation version made available for free from Microsoft to IT developers

 

Update:

rebuild from Win8 did not solve the problem either 

Edited by edborg
Link to comment
Share on other sites

Just for the record,  not all bootsect.exe's are the same:

http://www.msfn.org/board/topic/171749-bootsectexe-various-versions-compared/

but the blinking underscore is usually an issue with partitioning (frequently connected with HS geometry), and bootsect.exe won't do anything to solve it (it just replaces the bootsector CODE, while the issue is more likely to be with the DATA).

 

jaclaz

Link to comment
Share on other sites

Just for the record,  not all bootsect.exe's are the same:

http://www.msfn.org/board/topic/171749-bootsectexe-various-versions-compared/

but the blinking underscore is usually an issue with partitioning (frequently connected with HS geometry), and bootsect.exe won't do anything to solve it (it just replaces the bootsector CODE, while the issue is more likely to be with the DATA).

 

jaclaz

Happy to "see" you here jaclaz!  :sneaky:
 
Based on your always detailed and reliable info I could ascertain that the bootsect.exe included in WinNTSetup v3.6.1 is the Win8 version (8/Waik4/PE4.x->6.2.9200.16384->25/07/2012->117,688 bytes).
 
I therefore downloaded with GetWaikTools the Win8.1 version (8.1/Waik5/PE5.1->6.3.9600.16384->21/08/2013->100.968 bytes) and updated the boot code with that.
 
However, as expected (by you), this did not solve the issue.
 
The USB HD I am using has three primary partitions with one Win8 working installation (and two non working Win8.1 attempts :no: ).
 
How could I solve the issue with the DATA in the bootsector without repartitioning?
Could I only (once more) delete and recreate THAT partition, without affecting the others?
If repartitioning is a MUST, how could I make sure that the problem doesn't show again on the freshly repartitioned and reformatted disk?
 
Thanks  :hello:
 
edborg
Edited by edborg
Link to comment
Share on other sites

A good idea would be:

1) starting a new thread, as this issue is unlikely to be related to WinNTSetup and it makes little sense to hijack this thread

2) provide some data about that hard disk, how it is partitioned, etc. and on the PC(s) you are finding this issue with

3) post as an attachment to your post on the new thread, inside a compressed .zip or .7z file, a copy of BOTH your MBR and bootsector(s) made using (say) Hdhacker : 

http://dimio.altervista.org/eng/index.html

or *any* dd-like tool you might have handy/you are familiar with.

 

jaclaz

Link to comment
Share on other sites

  • 2 weeks later...

You can do it with bcdedit.exe

Bcdedit /create {legacy} /d "Windows XP"Bcdedit /set {legacy} device bootBcdedit /set {legacy} path \ntldrBcdedit /displayorder {legacy} /addlast

But you also need to copy ntldr, ntdetect.com, boot.ini and optional bootfont.bin from your XP partition to the current boot partition.

The one where bootmgr and Boot\Bcd is located.

Link to comment
Share on other sites

But you also need to copy ntldr, ntdetect.com, boot.ini and optional bootfont.bin from your XP partition to the current boot partition.

The one where bootmgr and Boot\Bcd is located.

OT :ph34r: This is what I never managed to get some accurate test results about. :w00t:

 

Possibly these files are not needed at all (i.e. BOOTMGR+boot\BCD+winload.exe can load a XP fine) :unsure:

 

Like:

http://www.betaarchive.com/forum/viewtopic.php?t=9602

http://www.msfn.org/board/topic/139807-difference-in-winloadexe-

 

Sanbarrow forum is not working, here is through Wayback Machine:

https://web.archive.org/web/20110106042923/http://sanbarrow.com/phpBB2/viewtopic.php?t=1695

 

jaclaz

Edited by jaclaz
Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...