Welcome to MSFN

Register now to gain access to all of our features. Once registered and logged in, you will be able to contribute to this site by submitting your own content or replying to existing content. You'll be able to customize your profile, receive reputation points as a reward for submitting content, while also communicating with other members via your own private inbox, plus much more! This message will be removed once you have signed in.


crashnburn4u

Migrating Windows 7 or 8 Install from BIOS machine to Native Boot VHD

36 posts in this topic

Migrating Windows 7 or 8 Install from BIOS machine to Native Boot VHD on UEFI – Intricate Issues, Questions & Meticulous Steps

 

A lot of the info gathered here was based on the steps and posts on these threads: 

o   http://forums.mydigitallife.info/threads/55775-Transfer-Thinkpad-Win7-Instance-to-New-4K-Win8-1(conserve)-Laptop-to-a-Partition-Img

o   http://reboot.pro/topic/19954-win-7-transfer-migrate-to-win81-laptop-sysprep-generalize-vs-disk2vhd-or-both/

o   http://www.sevenforums.com/virtualization/339361-win-7-transfer-win8-1-laptop-sysprep-generalize-vs-disk2vhd-both.html#post2847502

 

All details are being posted here, as the best and closest to such scenario seems to be experienced by MagicAndreas over here on MSFN (fromo Pg 2 to 4/5):

http://www.msfn.org/board/topic/129475-boot-windows-7-from-vhd-an-amazing-concept/page-4

 

Creating a fresh thread (for the differences) but also bringing alive the old one (related & similar info) so that we can pull info & people over here. 

 

Hope the Mods wont get mad as this has not been an easy thing to do or undergo for few weeks. 

 

I believe the solution and best guidance would be found here. 

 

·       BIOS vs UEFI issues and learnings:

o   Windows has 2 flavours of bootloaders that look alike : 1. For BIOS systems, 2. for UEFI systems.
Can be told apart as UEFI bootloader presents "Boot from Device" as one of root menu options

o   http://blogs.msdn.com/b/dai/archive/2014/04/10/using-vhd-native-boot-with-uefi-firmware-bcdedit-vs-bcdboot.aspx

o   TIME CONSUMING EXPERIENCES with 2 VHD + 1 VHDX instances I created using Disk2VHD:

§  1st MBR VHDX (Boots in Hyper-V Gen 1, Native Boot VHDX - Windows 7 not supported??)

§  1st  MBR VHD (Boots in Hyper-V Gen 1 & VMWare)

§  2nd MBR VHD Converted to GPT + GPT VHD now has System + MSR partitions

§  http://www.dertechblog.de/en/2014/01/howto-hyper-v-gen1-vm-convert-gen2-vm/

Mount-VHD -Path "C:\Win7or8.vhd"  ..Dismount-VHD at end of all commands below
gptgen.exe -w \.physicaldrive#
            # = disk number , get via Get-Disk

§  create partition efi size=100
format quick fs=fat32 label=”System
assign letter =”S”

create partition msr size=128

bcdboot g:\windows /s s: /f UEFI  …EFI boot files copied to “System” Partition i.e. Virtual EFI partition

§  bcdboot g:\windows …Add to UEFI Boot Entry (PRIOR: Remove any VHD Native Boot bcdedit /delete {guid} entries)

·       Hyper-V Gen 2 not accept VHD, Only VHDX

·       In VMWare (w EFI hack): GPT VHD boots & later SYSPREP OOBE applied also boots

·       Native Boot GPT VHD Win7 freeze even in Safe Mode – Even after SYSPREP

o   Stuck at classpnp.sys, disk.sys. Some suggest AHCI registry thing or this etc.

o   Possibility: Win7 won’t work at all w/ new Hardware, so updated GPT VHD Win 7 Ult > 8 Pro (next 8.1)

§  Preserved: Programs + Settings on GPT VHD Updated Win 8 Pro: VMWare Boots, Native NOT

Some new errors, and I can’t figure out how to repair recover them

 

·       MAIN QUERIES on the OPTIONS on NEXT STEPS MOVING FORWARD: (some EFI/ PARTITIONS/ stuff Queries wrt URL 1 & 2 above)
I can multitask some stuff I’ve tried below, but prefer clarity for clean EFI & Imaging minus errors/ issues

o   A. Existing HOST Preinstalled Win 8.1 HDD already has EFI partition.. HOST HDD v/s Guest GPT VHD

§  Does guest GPT VHD need EFI, System, MSR & Pre OS partitions created? (like URL2 CMD steps)

§  Can VHD have its own EFI partition and still boot NATIVELY with Host Partitions EFI?

o   B. Better to image OS PARTITIONS or entire DISK DRIVE w/ EFI/ MSR partitions or Create new EFI/MSR?

o   1. (Tried/ Can try again) Fresh Install Win7 &/or 8 on Native VHDs. See if boots at all on new hardware

THIS except BCDEDIT used BCDBOOT - http://jaminquimby.com/joomla253/work-stations/85-windows-7/73-how-to-install-windows-7-ultimate-onto-a-vhd-drive

o   2. Please guide on ways to trace & fix and make Win 7 UEFI VHD able to Native Boot

o   3. If Win 7 fails fully, take Upgraded Win 8/ 8.1 IMAGE to Native VHD that boots?

·       ACTION STEPS & POSSBILITIES:

·       OLD SYSTEM: BIOS - MBR Windows 7 x 64 SP1

o   Original: IBM Partition + 200 MB Boot Partition > Eliminated & Sys Repair

o   Recently: Empty 238MB > Recreated ‘System Reserved’ 200 MB using DiskMgmt

·       NEXT STEPS – ACTIONS NEEDED (Best Order to be determined):

o   SYSPREP

o   CREATE IMAGE (Options): With or without EFI, System, MSR i.e. Pre OS Partitions?

§  (1) Disk Management – SHRINK OS PARTITION/ DISK ??

§  (2) Two ways: (i) Disk2VHD 1.64 vs 2.01 – Check All Partitions or not? v/s OS Partition only?

§  (ii) ImageX/ Disk2WIM/ DISM steps: (Better than Disk2VHD? Ignores EFI, System, MSR partns?)

·       Capture Sysprep-ed Windows 7 or 8 image

o   (wimlib-imagex capture C:\ D:\Win7or8.sysprepped.wim)

·       TRANSITION STEPS

o   MBR to GPT conversion of disk partition configuration using GPTGEN or

§  GUI Tool like: AOMEI Partition Asst etc. http://www.disk-partition.com/free-partition-manager.html

o   MAYBE: INSERT PARTITIONS and STUFF, before OS Partition based Answers to Queries A & B

·       NEW SYSTEM: UEFI – GPT Preinstalled Win 8.1 Pro x64 – Secure Boot Disabled (for Win 7)

o   Boot using Win PE

o   Run Diskpart Commands to create a VHD

§  create vdisk file=C:\w7or8.vhd maximum=25000 type=expandable

select vdisk file=C:\w7or8.vhd

attach vdisk

o   MAYBE: INSERT PARTITIONS and STUFF, before OS Partition based Answers to Queries A & B

o   CREATE OS PARTITION

§  create partition primary

active

format fs=NTFS quick label=Win7or8VHD

assign letter=V

o   APPLY IMAGE

§  Apply capture (sysprep) image to mounted VHD

·        (wimlib-imagex apply D:\Win7or8.sysprepped.wim 1 V:\)

o   CREATE BOOT INFO: BCDBOOT

§  Created boot files on C: drive - my active partition

·        (V:\system32\bcdboot.exe V:\windows /s C:)

§  ..

o   DETACH VHD

§  In opened Diskpart window detach vdisk command & Reboot

§  ..

o   Create VHD Native Boot ENTRY

§  Using BCDBOOT

§  Using Easy BCD ??

·       SYSPREP Again before Native Boot??

·       ..

·       ADDITIONAL INTERSTING URLS:

o   http://1staidkit.wordpress.com/2012/09/05/boot2vhd-switching-between-hyper-v-native-vhd-boot-disk/      

o   http://en.community.dell.com/techcenter/extras/w/wiki/uefi-boot-to-vhd.aspx

o  

o   ..

·       ORIGINALY POSTED, PRACTICED & RECEIVED STUFF:

o   http://reboot.pro/topic/19954-win-7-transfer-migrate-to-win81-laptop-sysprep-generalize-vs-disk2vhd-or-both/

o  

 

 

Edited by crashnburn4u
0

Share this post


Link to post
Share on other sites

Migrating Windows 7 or 8 Install from BIOS machine to Native Boot VHD on UEFI

Which hardware do you use? BIOS, firmware, driver relates to this.

 

Stuck at classpnp.sys, disk.sys.

A basic driver is not resporting success to the kernel. Of course antoher driver, not the mentioned ony.

Can be the driver itself (a OS default driver or a third party driver), BIOS, firmware, hardware.

 

Some suggest AHCI

This would result antother error: BSOD 0x7b. No it's not the current issue.

Does other users use Windows 7 at relating hardware?

As for testing:

mount the VHD

format the partition

apply a default windows 7 install.wim to this partition.

unmount the VHD.

Boot to the VHD.

If it's boots, blame a third party driver at the other VHD.

 

By the way: the VHD can be MBR or GPT style, both works from winload.efi.

0

Share this post


Link to post
Share on other sites

Can you please shed some light on the requirements for a VHD to "Native Boot"? in terms of preOS partitions? 

 

I want to ensure VHD and their pre OS partitions and stuff are done properly. Because my VHDs are booting fine inside VMWare with EFI, but not booting NATIVE. So either something issue with one of the following:

UEFI/BIOS > Bootloader > EFI partitions > OS Partition > Driver Issue

 

- For a VHD to Native Boot, can it be with and/or without its "own" self contained preOS set of partitions: EFI, System, MSR (on the VHD v/s pre OS on the Host Drive)

.. Or can it/ does it have to use the EFI etc of a HOST drive partition? 

.. This is in reference to Query A. 

 

- When I image an existing Install on a HDD Disk, is it better to Image with the PreOS partitions (EFI/MSR) or without? 

- i.e. Create Fresh pre OS partitions (EFI/MSR) and then create and insert into Primary Partition the SysPrep Image of the installed OS

.. Query B.. kind of related to Query A

 

Why am I asking the above? Because that is what was done by the MS fellow in URL 2. 

 

§  http://www.dertechblog.de/en/2014/01/howto-hyper-v-gen1-vm-convert-gen2-vm/

Mount-VHD -Path "C:\Win7or8.vhd"  ..Dismount-VHD at end of all commands below
gptgen.exe -w \.physicaldrive#
            # = disk number , get via Get-Disk

§  create partition efi size=100
format quick fs=fat32 label=”System
assign letter =”S”

create partition msr size=128

bcdboot g:\windows /s s: /f UEFI  …EFI boot files copied to “System” Partition i.e. Virtual EFI partition

§  bcdboot g:\windows …Add to UEFI Boot Entry (PRIOR: Remove any VHD Native Boot bcdedit /delete {guid} entries) 

 

 

·       OPTIONS on NEXT STEPS MOVING FORWARD: (some EFI/ PARTITIONS/ stuff Queries wrt URL 1 & 2 above)
I can multitask some stuff I’ve tried below, but prefer clarity for clean EFI & Imaging minus errors/ issues

 

o   A. Existing HOST Preinstalled Win 8.1 HDD already has EFI partition.. HOST HDD v/s Guest GPT VHD

§  Does guest GPT VHD need EFI, System, MSR & Pre OS partitions created? (like URL2 CMD steps)

§  Can VHD have its own EFI partition and still boot NATIVELY with Host Partitions EFI?

 

o   B. Better to image OS PARTITIONS or entire DISK DRIVE w/ EFI/ MSR partitions or Create new EFI/MSR?

 

o   1. (Tried/ Can try again) Fresh Install Win7 &/or 8 on Native VHDs. See if boots at all on new hardware

THIS except BCDEDIT used BCDBOOT - http://jaminquimby.com/joomla253/work-stations/85-windows-7/73-how-to-install-windows-7-ultimate-onto-a-vhd-drive

o   2. Please guide on ways to trace & fix and make Win 7 UEFI VHD able to Native Boot

o   3. If Win 7 fails fully, take Upgraded Win 8/ 8.1 IMAGE to Native VHD that boots? 

Edited by crashnburn4u
0

Share this post


Link to post
Share on other sites

 

Migrating Windows 7 or 8 Install from BIOS machine to Native Boot VHD on UEFI

Which hardware do you use? BIOS, firmware, driver relates to this.

 

Stuck at classpnp.sys, disk.sys.

A basic driver is not resporting success to the kernel. Of course antoher driver, not the mentioned ony.

Can be the driver itself (a OS default driver or a third party driver), BIOS, firmware, hardware.

 

Some suggest AHCI

This would result antother error: BSOD 0x7b. No it's not the current issue.

Does other users use Windows 7 at relating hardware?

As for testing:

mount the VHD

format the partition

apply a default windows 7 install.wim to this partition.

unmount the VHD.

Boot to the VHD.

If it's boots, blame a third party driver at the other VHD.

 

By the way: the VHD can be MBR or GPT style, both works from winload.efi.

 

Original Hardware: Thinkpad T6x/X6x series with BIOS Firmware - Uses BIOS - MBR Windows 7 x 64 SP1

New Hardware: Toshiba P55T with UEFI Firmware - Uses - UEFI – GPT Preinstalled Win 8.1 Pro x64

 

It is not even booting successfully in SAFE MODE. Only closest Win7 with new hardware example I found was MagicAndre. 

 

I don't know what hardware and driver is causing issues. How can I trace and log, my PROBLEM causing DRIVER when I cant even boot into Safe Mode (on native boot). It boots fine inside VMWare. 

 

PS: VHD can be MBR or GPT, but if my Firmware is set to UEFI boot and not CSM (Legacy BIOS boot), then the VHD has to be GPT right? 

Then what kind of partition structure must that VHD have? Only OS Partition or it must have System, EFI, MSR partitions (As given in the Link 2 by the Microsoft guy) Please see that. 

Edited by crashnburn4u
0

Share this post


Link to post
Share on other sites

Original Hardware: Thinkpad T6x/X6x series with BIOS Firmware

New Hardware: Toshiba P55T with UEFI Firmware

Name the true model, not the family. Which one T6x/X6x do you use? Which one P55T do you use?

 

It is not even booting successfully in SAFE MODE. Only closest Win7 with new hardware example I found was MagicAndre.

Did you disable GOP at firmware at the unknown P55T?

 

It boots fine inside VMWare.

VHD layout is appropiate. Enable boot logging http://www.msfn.org/board/topic/162071-w2k12-show-os-boot-information/ Post ntbtlog.txt up to HdAudio.sys.

 

PS: VHD can be MBR or GPT, but if my Firmware is set to UEFI boot and not CSM (Legacy BIOS boot), then the VHD has to be GPT right?

No, VHD can be MBR or GPT nontheless.

UEFI booting to a VHD GPT is possible.

And UEFI booting to a VHD MBR is possible.

What about apply Windows 7 install.wim to the VHD?

Do you have a spare hard disk? Swap the Toshiba hdd and install Windows 7.

 

Only OS Partition or it must have System, EFI, MSR partitions (As given in the Link 2 by the Microsoft guy) Please see that.

Documentation list a friendly approach. Ignore the documentation.
0

Share this post


Link to post
Share on other sites

Thanks for the Info CrashNBurn..

 

~DP :whistle:

1

Share this post


Link to post
Share on other sites

Please tell me what would be the best steps to migrate from Thinkpad Disk Drive to Toshiba as a VHD Native Boot. 

 

I used Disk2VHD as it seemed simple and outlined all steps and issues I faced above.

 

Is there better tool and steps that you would suggest to IMAGE the Disk Drive into VHD? Or are the VHDs good enough?

 

 

Original Hardware: Thinkpad T6x/X6x series with BIOS Firmware
New Hardware: Toshiba P55T with UEFI Firmware

Name the true model, not the family. Which one T6x/X6x do you use? Which one P55T do you use?

 

Original: Thinkpad T61 with NVS140m and X61T (The drive has been swapped and used between both) - Sysprep was used after to clear both drivers. 

Toshiba Satellite P55T 4K Ultra HD Touchscreen: P55T-B5235:
Device Driver Support for Windows 7 vs Windows 8 and 8.1?

http://forum.notebookreview.com/toshiba/758332-help-toshiba-satellite-p55t-4k-ultra-hd-touchscreen-p55t-b5235-device-driver-support-windows-7-vs-windows-8-8-1-a.html

 

 

It is not even booting successfully in SAFE MODE. Only closest Win7 with new hardware example I found was MagicAndre.

Did you disable GOP at firmware at the unknown P55T?

 

How do I do that? Where/ how can I go to do that? I dont see any option labeled GOP inside Firmware. Could it be called something else? 
 

It boots fine inside VMWare.

VHD layout is appropiate. Enable boot logging http://www.msfn.org/board/topic/162071-w2k12-show-os-boot-information/ Post ntbtlog.txt up to HdAudio.sys.

 

VHD Layout is apporpriate? Meaning with or without all Pre OS partitions? 

I see that is there is bootlog BCDEDIT commant {} for drive? Will that be okay for VHD?

Assuming it works, it will crash and then I have to MOUNT the VHD in Win 8.1 to see ntbtlog.txt right?  

Here's my BCD /enum ALL output

Firmware Boot Manager---------------------identifier              {fwbootmgr}displayorder            {bootmgr}timeout                 2Windows Boot Manager--------------------identifier              {bootmgr}device                  partition=\Device\HarddiskVolume2path                    \EFI\Microsoft\Boot\bootmgfw.efidescription             Windows Boot Managerlocale                  en-USdefault                 {current}displayorder            {current}timeout                 30Windows Boot Loader-------------------identifier              {current}device                  partition=C:path                    \Windows\system32\winload.efidescription             Windows 8.1 Prolocale                  en-USrecoverysequence        {85453c64-21cd-11e4-94cc-e2420fc53d1b}recoveryenabled         Yesosdevice                partition=C:systemroot              \Windowsresumeobject            {2ec76d62-21c5-11e4-8291-806e6f6e6963}bootmenupolicy          Standardhypervisorlaunchtype    OffWindows Boot Loader-------------------identifier              {85453c64-21cd-11e4-94cc-e2420fc53d1b}device                  ramdisk=[\Device\HarddiskVolume1]\Recovery\WindowsRE\Winre.wim,{85453c65-21cd-11e4-94cc-e2420fc53d1b}path                    \windows\system32\winload.efidescription             Windows Recovery Environmentlocale                  en-USinherit                 {bootloadersettings}displaymessage          Recoveryosdevice                ramdisk=[\Device\HarddiskVolume1]\Recovery\WindowsRE\Winre.wim,{85453c65-21cd-11e4-94cc-e2420fc53d1b}systemroot              \windowsnx                      OptInbootmenupolicy          Standardwinpe                   YesResume from Hibernate---------------------identifier              {2ec76d62-21c5-11e4-8291-806e6f6e6963}device                  partition=C:path                    \Windows\system32\winresume.efidescription             Windows 8.1 Prolocale                  en-USinherit                 {resumeloadersettings}filedevice              partition=C:filepath                \hiberfil.sysdebugoptionenabled      NoWindows Memory Tester---------------------identifier              {memdiag}device                  partition=\Device\HarddiskVolume2path                    \EFI\Microsoft\Boot\memtest.efidescription             Windows Memory Diagnosticlocale                  en-USDevice options--------------identifier              {85453c65-21cd-11e4-94cc-e2420fc53d1b}description             Windows Recoveryramdisksdidevice        partition=\Device\HarddiskVolume1ramdisksdipath          \Recovery\WindowsRE\boot.sdi 

PS: VHD can be MBR or GPT, but if my Firmware is set to UEFI boot and not CSM (Legacy BIOS boot), then the VHD has to be GPT right?

No, VHD can be MBR or GPT nontheless.
UEFI booting to a VHD GPT is possible.
And UEFI booting to a VHD MBR is possible.

 

I was told this was not allowed and as per the MS blog link I posted, they had to be converted to EFI-GPT

What about apply Windows 7 install.wim to the VHD? -

I can try this again (did try once) and report back. Which METHOD / STEPS should I use for this? 

Do you have a spare hard disk? Swap the Toshiba hdd and install Windows 7. 

I might have a spare, but I doubt if I can get to this hardware that easy like Thinkpad Drive bays. 

Nor do I want to as I have to return it to employer comany in 2 or 3 months after contract is over.  
 

Only OS Partition or it must have System, EFI, MSR partitions (As given in the Link 2 by the Microsoft guy) Please see that.

Documentation list a friendly approach. Ignore the documentation.

Meaning? "friendly" ignore? I dont quite understand what you are saying here. 

Edited by crashnburn4u
0

Share this post


Link to post
Share on other sites

Please tell me what would be the best steps to migrate from Thinkpad Disk Drive to Toshiba as a VHD Native Boot.

The best way: do not do this.

There is no best way.

 

I used Disk2VHD as it seemed simple and outlined all steps and issues I faced above.

The issue relates not to Disk2VHD, most likely there is another reason.

P55T-B5235: http://support.toshiba.com/support/modelHome?freeText=1200008303

P55t-A5202 http://support.toshiba.com/support/modelHome?freeText=1200005514

Version 1.20 - 2013-07-23

Updated: VGA GOP driver V5.0.1032.

I assume the P55T-B5235 uses GOP too.

Which firmware version do you use?

 

Where/ how can I go to do that? I dont see any option labeled GOP inside Firmware. Could it be called something else?

Yes, there can be another name. Or there is no option at all.

As for apply the windows 7 intall.wim: You qouted already http://www.msfn.org/board/topic/129475-boot-windows-7-from-vhd-an-amazing-concept/page-5#entry1083966

DISM.exe /Apply-Image /ImageFile:E:\sources\install.wim /Index:4 /ApplyDir:V:\

1

Share this post


Link to post
Share on other sites

The issue relates not to Disk2VHD, most likely there is another reason.

P55T-B5235: http://support.toshiba.com/support/modelHome?freeText=1200008303

P55t-A5202 http://support.toshiba.com/support/modelHome?freeText=1200005514

Version 1.20 - 2013-07-23

Updated: VGA GOP driver V5.0.1032.

I assume the P55T-B5235 uses GOP too.

Which firmware version do you use?

 

Where/ how can I go to do that? I dont see any option labeled GOP inside Firmware. Could it be called something else?

Yes, there can be another name. Or there is no option at all.

As for apply the windows 7 intall.wim: You qouted already http://www.msfn.org/board/topic/129475-boot-windows-7-from-vhd-an-amazing-concept/page-5#entry1083966

DISM.exe /Apply-Image /ImageFile:E:\sources\install.wim /Index:4 /ApplyDir:V:\

 

 

I guess the above would be the best way to IMAGE the DRIVE. 

 

Anyways, you are a genius: I posted also on Toshiba forums to get confirmation for BIOS. I am posting here too with additional info about my laptop as posted here. 

http://forums.toshiba.com/t5/Drivers-and-Utilities/Help-Satellite-4K-P55T-B5235-Boot-amp-Driver-support-for-Win-7/m-p/604899#M21076

 

 

I am running into bit of confusion figuring out what is the LATEST BIOS version for this laptop? 

 

Is the Driver Mapping & Selection engine/ configurator FAULTY here? 

 

My Model is this: Satellite P55T-B235

Part No: PSPNVU - 01Q01E

System BIOS: 1.10

EC: 1.00

 

As per the help I am getting here: 

http://www.msfn.org/board/topic/172462-migrating-windows-7-or-8-install-from-bios-machine-to-native-boot-vhd/ 

 

Insert Model: P55T-B5235

http://support.toshiba.com/support/modelHome?freeText=1200008303

 

Then filter by BIOS shows: 

BIOS version 1.20 for Satellite P50 (PSPNSx/PSPNUx/PSPNTx/PSPNVx)Posted Date: 2014-07-30 | Version: 1.20 | Size: 14.87M

BIOS version 1.10 for Satellite P50 (PSPNSx/PSPNUx/PSPNTx/PSPNVx)Posted Date: 2014-06-16 | Version: 1.10 | Size: 17.96M

 

Insert Model: P55t-A5202

http://support.toshiba.com/support/modelHome?freeText=1200005514

 

Then filter by BIOS shows:

BIOS version 1.80 for Satellite P50/P55/P55t (PSPMJx/MKx/PSPKKAx/KEx)Posted Date: 2014-06-25 | Version: 1.80 | Size: 16.32M

ACPI Flash BIOS version 1.70 for Satellite P50/P55/P55t (PSPMJx/MKx/PSPKKAx/KEx)Posted Date: 2014-06-25 | Version: 1.70 | Size: 16.3M

ACPI Flash BIOS version 1.60 for Satellite P50/P55/P55t (PSPMJx/MKx/PSPKKAx/KEx)Posted Date: 2014-02-12 | Version: 1.60 | Size: 16.29M

ACPI Flash BIOS version 1.50 for Satellite P50/P55/P55t (PSPMJx/MKx/PSPKKAx/KEx)Posted Date: 2014-01-08 | Version: 1.50 | Size: 16.28M

 

First search result shows BIOS etc for P50 etc using exact model

 

Second search result shows BIOS etc for P55t etc. using a different model

 

What is with these mismatched BIOS results? 

Can we have Toshiba Support chime in on this and point out which is the MATCHING, LATEST BIOS for the Model I have? 

 

Given that this is BIOS, I am rather upset there are such mixups. I cant experiment with this until there is proper confirmation. 

0

Share this post


Link to post
Share on other sites

What is with these mismatched BIOS results?

Yes, it's confusing.

Which part number do yo use?

README.TXT 2014-07-30 CDC

BIOS version 1.20 for Satellite P50 (PSPNSx/PSPNUx/PSPNTx/PSPNVx)

-----------------------------------------------------------------------------

This BIOS is applicable to the following models:

o All models having part numbers beginning with "PSPNSM", "PSPNSP",

"PSPNSU", "PSPNTM", "PSPNTP", "PSPNTU", "PSPNUM", "PSPNUP", "PSPNUU",

"PSPNVM", "PSPNVP", or "PSPNVU".

README.TXT 2014-06-25 CDC

ACPI Flash BIOS version 1.80 for Satellite P50/P55/P55t (PSPMJx/MKx/PSPKKAx/KEx)

-----------------------------------------------------------------------------

This BIOS is applicable to the following models:

o All models having part numbers beginning with "PSKKAM", "PSKKAP",

"PSKKAU", "PSKKEM", "PSKKEP", "PSKKEU", "PSPMJM", "PSPMJP", "PSPMJU",

"PSPMKM", "PSPMKP", or "PSPMKU".

Break, do not flash the firmware so far.

Go back to basic testings:

Can you boot a Windows 7 DVD at BIOS mode? Can you press shift F10?

Can you boot a Windows 7 DVD at UEFI mode? Can you press shift F10?

0

Share this post


Link to post
Share on other sites

My Model is this: Satellite P55T-B235


Part No: PSPNVU - 01Q01E


System BIOS: 1.10


EC: 1.00


 


Model (P55T) matches second one, Part no (PSPNVU) matches first one. 


 


I will check both Windows 7 DVD Boots and get back to you. I think both work (atleast one of them does). Let me check and come back to you. Are you on some Instant Messenger somewhere? (AIM, GTalk, Skype, MSN, Y! or something?) 


0

Share this post


Link to post
Share on other sites

I updated to new BIOS 1.2 - It doesnt show any GOP options. I called Tech Support to ask them and they said Level 2 guy will call me (never happens Hmm..)

Any thoughts / suggestions on what I should tell/ ask/ demand of them, given their older MACHINES & BIOS show GOP on their BIOS? 

Can it be an included hidden feature or its something that would be a "change able" i.e. enable / disable setting? 

 

How do I make them add it or find it? 

--------------------

 

I have several versions/ instances of Windows 7 ISOs and I have a Zalman VE 200 (USB Virtual Optical/ HDD) (ISO Mount & Booter). 

 

I tried one of them WIn7x64 Ultimate SP1 ISOs using both Firmware Modes and selecting Zalman as Boot Device: 

- UEFI Mode: No Win7 at all, Goes to HDD and boots that

- CSM Mode: Win 7 Installer + SHIFT F10 works

 

Is there a certain ISO / DVD released by MS that is more UEFI setting boot favorable? Let me know and I can download.. from MSDN or TechNet or Retail variation (we're gold partners for decades)

0

Share this post


Link to post
Share on other sites

Is there a certain ISO / DVD released by MS that is more UEFI setting boot favorable? Let me know and I can download.. from MSDN or TechNet or Retail variation (we're gold partners for decades)

Well, you can re-master one with ONLY the UEFI booting, see:

http://www.msfn.org/board/topic/172122-got-tips-on-how-to-make-a-bootable-cd-from-bootable-usb/

but the "original" should have been already made as "dual boot" BIOS/UEFI, while it is entirely possible that the VE 200 *somehow* only emulates the BIOS booting.

If I were you I would use a "real" DVD drive or make a UEFI compatible USB stick for testing the install.

 

jaclaz

0

Share this post


Link to post
Share on other sites

PS: Can I/ should I try to use that SHIFT + F10 to create a fresh VHD and install WIn7 on it? To see how it works? How would I make it boot once Installed? 

 

Any steps/ guide you'd recommend? (PS: Dont want to make mistakes over overwrite any boot or partition info of the preinstalled Win 8.1). 

0

Share this post


Link to post
Share on other sites

Do you think a PURE windows 7 install on a Partition or a Hard Drive would work from CSM Mode? Given that GOP option is not there in current BIOS? 

0

Share this post


Link to post
Share on other sites

Also, lets assume GOP and Windows 7 might not work at all. Then, I dont mind moving to Windows 8/8.1 with Native Boot VHD.

 

In that scenario, what would be the best way to "migrate" the OS Partition/ Disk from Old System to a Native Boot VHD 

0

Share this post


Link to post
Share on other sites

I have a Zalman VE 200 (USB Virtual Optical/ HDD) (ISO Mount & Booter). 

 

I tried one of them WIn7x64 Ultimate SP1 ISOs using both Firmware Modes and selecting Zalman as Boot Device: 

- UEFI Mode: No Win7 at all, Goes to HDD and boots that

Try a real DVD.

 

Do you think a PURE windows 7 install on a Partition or a Hard Drive would work from CSM Mode?

Yes, should work at CSM mode, remember

CSM Mode: Win 7 Installer + SHIFT F10 works

Do you have a fast USB drive? Best a SSD?

Some UEFI firmware offers to select the boot drive, e.g. press F12 at the Thinkpad.

 

Also, lets assume GOP and Windows 7 might not work at all. Then, I dont mind moving to Windows 8/8.1 with Native Boot VHD.

 

In that scenario, what would be the best way to "migrate" the OS Partition/ Disk from Old System to a Native Boot VHD

I don't kown a way to proper "migrate" the applications and data.
0

Share this post


Link to post
Share on other sites

Ok, I am kind of giving up on Windows 7.

 

So, just to test the ability and issues around this new Toshiba Laptop and Native booting,
I ImageX 2 VHDs with fresh install from Win 8 and Win 8.1 each.
Did a simple bcdboot ?:\Windows to added them to Boot Menu. 
They are running fine. 
W8.VHD GPT [Simple Volume]W81.VHD GPT [Simple Volume]

They have a simple single volume structure and no System, EFI or MSR Partitions within

 
For some reason the VHDs I have created from my Source Machine are working with Hyper-V & VMWare.
But not working Native Boot.
 
So, I am wondering if it has something due to the Primary OS Parition and Pre OS partition (Reserved, EFI, System, MSR) structures? 

 

Please don't ignore the following Paragraph: I think this is a key issue where I am making some mistake with the VHDs or its Structure and Inter Partition mapping

 

I need to figure out the following:

X) - STRUCTURES of VHDs that work fine for Native Booting

e.g. Should they have Simple Volume Primary partitions ONLY?

AND/ OR they will be fine with/without Virtual EFI, System, MSR, Reserved etc. Internal to VHD i.e. Virtual Partitions that will work without issues.

 

Y) - Right WAY to IMAGE Existing machine: (Full DIsk w PreOS Partitions or Only OS Partition) and MAP the IMAGE to the correct part of the STRUCTURE of VHDs (as outlined above) 

 

Now, the VHD I have from my source system has gone through following changes:
 
Original & Current Source System
- MBR [1/200 MB Reserved/SystemPartition][Primary Partition Win7x64 SP1]
 
>> Disk2VHD
W7-MBR.VHD
- MBR [1/200 MB Reserved/SystemPartition][Primary Partition Win7x64 SP1]

(Works in Hyper-V + VMWare, NOT Native Boot)

 
>> Converted to GPT VHD with using gptgen and added System + MSR Partition as outlined here - http://www.dertechblog.de/en/2014/01/howto-hyper-v-gen1-vm-convert-gen2-vm/
W7-GPT.VHD 
- GPT [EFI:100,FAT32, "System",S:][MSR:128][][Primary Partition Win7x64 SP1]

>> EFI boot files copied to “System” Partition i.e. Virtual EFI partition

The important UEFI boot files will then use the tool bcdboot copied to the system partition. Where h corresponds: the drive letter of the virtual Windows partition and s: the drive letter of the virtual EFI partition: 
bcdboot h:\windows /s s: /f UEFI
(Works in VMWare with EFI, NOT Native Boot .. Windows 7 issues as pointed out in first post)
 
(So, I figured lets take this VHD to Windows 8)
>> Upgraded to Win8 inside VMWare >> SYSPREP
W7to8-GPT.VHD 
- GPT [EFI:100,FAT32, "System",S:][MSR:128][][Primary Partition Win8x64 Pro]

( Native boot still does not work | VMWare booting works)

 
Error on screen for this Most current error for this Win 7 upgraded to Win 8 VHD 
 
RECOVERYYour PC needs to be repairedThe operating system couldn't be located because the system registry file is missing or contains errors File: \Windows\System32\config\systemError Code: 0xc0000000dYou'll need to use the recovery tools on your installation media. If you dont have any installation media (like a disc or USB device), contact your system administrator or PC manufacturer

I guess the typical reply would be to try and REPAIR this OS. 

But, I think OS is working (in VMWre), but some part of the FLOW of  BOOTING to Native VHD has some issue. i.e from 

Firmware > HDD Host EFI > [VHD > Virtual EFI Partition > VIrtual OS Partition]

On the other VHDs the flow is probably this: 

Firmware > HDD Host EFI > [VHD > VIrtual OS Partition]
Do you get what I am saying here? 
 
So I am wondering of the following.. where is the error coming into the picture:
- While CREATING/ IMAGING the VHD? 
- While converting from MBR to VHD? 
- While/ DUE to INSERTING the Virtual EFI & MSR partitions? - Would it be better not to have these in the VHD? Or something was done wrong with them?
- Would it be better to only IMAGE the OS Partition, and image it to a blank Partition on the GPT VHD? (Avoid conversion)
 
I don't mind doing a FRESH IMAGING of the OLD MACHINE. I will have to do it anyways as the OLD MACHINE has changed in last few weeks of this experiment. 
 
But, I'd like to do it RIGHT this time and Create the Correct VHD structure to support it. 
Use ImageX or DISM instead of Disk2VHD if you guys think thats better. 

 

PS: The last time I ran a recovery disc to try and fix the Win7to8.VHD, it ended up messing up my Host HDD Win8 booting. How can I avoid that if at all you are suggesting some STEPS to REPAIR the Win7to8.VHD

Edited by crashnburn4u
0

Share this post


Link to post
Share on other sites
For some reason the VHDs I have created from my Source Machine are working with Hyper-V & VMWare.
But not working Native Boot.
There are some vitual hardware, especial the graphic card including the VGA BIOS.
Native booting uses native graphic card including the VGA BIOS or firmare.

What about the real DVD Windows 7 UEFI booting? Edited by cdob
0

Share this post


Link to post
Share on other sites

 

For some reason the VHDs I have created from my Source Machine are working with Hyper-V & VMWare.

But not working Native Boot.

There are some vitual hardware, especial the graphic card including the VGA BIOS.

Native booting uses native graphic card including the VGA BIOS or firmare.

What about the real DVD Windows 7 UEFI booting?

 

 

I get that.

With Windows 7 on the VHD it would boot initially and get stuck later at Logo

With Windows 8(upgraded to from win 7), the VHD, it gets gets stuck earlier before boot

 

My biggest question here is this - Do VHD's need to have or follow certain STRUCTURE to Native Boot? Will some structures fail to boot?

I think there's something wrong with the STRUCTURE of my VHD. 

Can/ should VHDs have PreOS 'Special' Partitions or NOT? 

 

Most people are saying they are equivalent of having a PHYSICAL HDD. 

But, has anyone had MULTIPLE PARTITIONS on a VHD and try MULTI BOOTING from them?

Because something is OFF with my VIRTUAL PARTITIONS. 

0

Share this post


Link to post
Share on other sites

( Native boot still does not work | VMWare booting works)

Error on screen for this Most current error for this Win 7 upgraded to Win 8 VHD

There is a different \boot\bcd used. Verify the native \boot\bcd after upgrade again.

 

Do VHD's need to have or follow certain STRUCTURE to Native Boot?

No, no certain requriements. Diffeent partitions are possible.

 

Will some structures fail to boot?

Yes, a expandable VHD will fail given low space at hard disk.

Native VHD Boot: A Walkthrough of Common Scenarios

http://download.microsoft.com/download/A/8/4/A847B017-B2CC-40E0-895A-266D88A43C99/Native-VHD-Boot-A-Walkthrough-of-Common-Scenarios.doc

Step 12: Prevent the VHD from expanding to its full size

During boot time, a dynamically expanding VHD will expand to its full size to guarantee space on the computer and to prevent data corruption. If the computer cannot allocate sufficient space from the physical disk that the VHD resides on, it will generate a stop error message and prevent the operating system from booting.

It's shown a BSOD 0x136.

You may disable VirtualDiskExpandOnMount.

Which VHD file size, and VHD disk size do you use?

Which free space is at real hard disk?

As jaclaz pointed already: make slow steps.

The true reason is not resolved so far.

Do you remember the question about real DVD Windows 7 UEFI booting?

Next setp: build a new VHD (fixed size) file and apply install.wim.

Given hardare / software request is unlear in detail. Nobody can provide a guaranteed working solution.

It may be possible to resolve the request later, if some small lessons learned.

1

Share this post


Link to post
Share on other sites

crashnburn4u

Do VHD's need to have or follow certain STRUCTURE to UEFI Native Boot?

 

The suggestion made to you to separate multiple tasks and learn step-by-step is the best. I haven't read the entire thread, but the above question appears to be your main one. :sneaky:  You might be missing some insight that UEFI OEM FW Boot Manager (UBM) is not equivalent to Windows Boot Manager - it shouldn't mount VHD or boot Windows itself, its done through a chain via Mobo NVRAM Boot Menu auto updated at each OS install. When UBM transfers control to Windows Bootmgr.efi (WBM) located on EFI HDD partition - then it mounts VHD if needed and calls Windows Boot Loader to boot OS, whether from HDD or VHD. What it means in practice: your HDD is expected to have Fat32 EFI System partition, which contains all files required to chainload WBM and then boot OS from "anywhere". Once you accomplished that, move on: format your VHD as GPT with partition structure too, and add Windows to it with DISM or restore from backup. Then use bcdboot  to add required boot files to it, and also add the VHD to main Windows Boot Menu. You might also need to do other adjustments to convert Windows install from BIOS to EFI and boot from USB drive. And your question about "multiple systems installed on VHD - I guess that's what you mean under "multiple partitions" - YES, its possible via VHD own Boot Menu, but 1st you need to learn booting at least ONE OS from it before adding more. While Secure Boot when active may impose limitations on OS multiboot.    :whistle:

 

Look through some MS docs, in particular:

 

Converting Windows BIOS installation to UEFI

Configure UEFI/GPT-Based Hard Drive Partitions by Using Windows PE and DiskPart

Boot to VHD (Native Boot): Add a Virtual Hard Disk to the Boot Menu

Securing the Windows 8 Boot Process

 

So your main question can be rephrased: "Can my PC UEFI FW mount a VHD before it starts looking for EFI partition"? If YES, will it be the 1st UEFI partition it finds? If NOT, would EFI partition still be required on that VHD?  What's NVRAM Boot Menu role in this?   :blushing:

 

 

P.S. Sorry for some offtop. As often happens in this estranged world, I'm also lost on some issues just like the topic starter. For example, still trying to find any solution (not questions) on booting a typical PC service UEFI ISO (WinPE or Linux based, example - Acronis) directly (no USB Flash conversion) on UEFI laptop without Legacy mode support, or at least explanation WHY its not possible??? This forum or inet Search gives positively NO conclusive hints. But... given the presence of well known gurus, is anyone able to point to such solution, say Grub2 based or such?

Edited by zamarac
1

Share this post


Link to post
Share on other sites

Thanks guys :) This will be my experiments for the next few days. I will read and follow every step and option.. yeah I know.. too many steps as Wonko also pointed out on Reboot.Pro

 

PS: cdob - I will try to find some DVDs burn Windows 7 on them and see if the boot on UEFI. Any particular MSDN / Digital River ISOs you'd recommend / know of that will WORK? 

 

PPS: I have a spare HDD (cant open laptop).. But I can attach via USB.. DO you think I should try installing and booting Windows 7 off that on a Partition? Just to see whether this Laptop will at all support Windows 7 in ANY mode? 

Edited by crashnburn4u
0

Share this post


Link to post
Share on other sites

 

P.S. Sorry for some offtop. As often happens in this estranged world, I'm also lost on some issues just like the topic starter. For example, still trying to find any solution (not questions) on booting UEFI Acronis ISO (WinPE or Linux based) directly (no USB Flash conversion) on UEFI laptop without Legacy mode support, or at least explanation WHY its not possible??? This forum or inet Search gives positively NO conclusive hints. But... given the presence of well known gurus, is anyone able to point to such solution, say Grub2 based or such?

Cannot say if it can be of any help with your issue, but it is possible that "between the lines" of this thread:

http://reboot.pro/topic/19516-hack-bootmgr-to-boot-windows-in-bios-to-gpt/

it can be found something of use. :unsure:

 

jaclaz

0

Share this post


Link to post
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.