Jump to content











Photo
- - - - -

Community OFA NVMe 1.5 Storport Miniport for Windows Server 2003 R2 SP2

nvme ofa storport 2003

  • Please log in to reply
269 replies to this topic

#251 Dietmar

Dietmar

    Frequent Member

  • Advanced user
  • 205 posts
  •  
    Afghanistan

Posted 4 days ago

Waaoh, the legacy nvme Toshiba RD400 is now recogniced in Bios

as Toshiba RD400,

some other nvme disks are named PataSS:

like in the Fernando forum,

but still no complete legacy nvme boot

Dietmar

 

f664b2-1555279943.jpg



#252 agent_x007

agent_x007

    Newbie

  • Members
  • 23 posts
  •  
    Poland

Posted 4 days ago

Progress !
CSM is loaded as Legacy first (with both "Legacy and UEFI" options active when available) ?


Edited by agent_x007, 4 days ago.


#253 Dietmar

Dietmar

    Frequent Member

  • Advanced user
  • 205 posts
  •  
    Afghanistan

Posted 3 days ago

The question ist, which *.dxe files from UEFI Bios

are needed for full CSM support (Compatibility Support Module).

We need a tool like Dependency Walker, for to see,

which files call each other, are connected.

The UEFITool tries something in this direction,

when you change a *.dxe file, sometimes another *.dxe file

is changed also. But this function in UEFITool is not as good

as in Dependency Walker, because in this case legacy nvme boot

was done already,

Dietmar

 

PS: Any help is welcome, how UEFI Bios with CSM really works!



#254 Dietmar

Dietmar

    Frequent Member

  • Advanced user
  • 205 posts
  •  
    Afghanistan

Posted 3 days ago

Ok, fun goes on:

After additional adding the following files from X79-Deluxe Bios to Bios of Sabertooth x79

all nvme disks are recogniced by their name.

 

AcpiModeEnable

AHCI

AhciSmm

AINT13

CsmVideo

NTFS

SBAHCI

SBDXE

SBIDE

SBRun

SecureBootMod

SIOBasicIODxe

 

But on boot of a working nvme XP on  MBR  I get the message

 

"Reboot and select proper boot device or insert boot media in selected boot device and press a key"

 

Dietmar

 

408c71-1555332814.jpg



#255 Dietmar

Dietmar

    Frequent Member

  • Advanced user
  • 205 posts
  •  
    Afghanistan

Posted 3 days ago

Win10 on MBR with NTFS shows the same error message,

even with those new copied files to Bios of Sabertooth X79

 

Runtime

SBSMI

SbPchSmi

SataDiver_12_7

NBDXE (NOT copied, because not screen!)

BootPriority

BIOSBLKIO

AMITSE

UefiPxeBcDxe

UHCD

MSOA

IdeSMART

ResLoader

ASUSFTMDXE

OEMDXE

uefi64

 

Dietmar



#256 Dietmar

Dietmar

    Frequent Member

  • Advanced user
  • 205 posts
  •  
    Afghanistan

Posted 3 days ago

Same behavior,

after I add to Bios of the Sabertooth x79 board.

 

TcgPlatformSetupPolicy

TcgDxe

TcgDxeplatform

TCGSmm

TcgLegacy

AmiTcgPlatformDxe

AmiTcgNvflagSample

 

Dietmar



#257 Dietmar

Dietmar

    Frequent Member

  • Advanced user
  • 205 posts
  •  
    Afghanistan

Posted 2 days ago

The problem is still,

which files are really needed for legacy nvme boot.

 

A new idea is, to delete files in Bios one by one on

a working nvme Bios and look,

at which point nvme legacy boot stops working

and shows the same symptoms as for me

"Reboot and select proper boot device or insert boot media in selected boot device and press a key"

 

From my results until now I see,

that the nvme devices are recogniced with full name (good),

but Bios still wants them in UEFI mode.

So the switch between UEFI and legacy

does not work for nvme drives until now

with just additional (changed) drivers to Bios

Dietmar



#258 Dietmar

Dietmar

    Frequent Member

  • Advanced user
  • 205 posts
  •  
    Afghanistan

Posted 2 days ago

A new search for "nvme" in Bios

with ASCII and with unicode gives results for the following files in nvme Bios:

 

Nvme

NvmeSmm

NVMEINT13

CSMCORE

Setup

 

 

The word "legacy" is in

 

CORE_DXE

CSMCORE

LegacyInterrupt

LegacyRegion

AMITSE

(TCGLegacy)

(USBINT13)

Int10ToSmi

(IntelGigabitLanx64)

Setup

 

Oh, "Setup"  and  "Int10ToSmi"  I have not replaced until now,

so lets see :)

Dietmar

 

EDIT: If this is the right way, I can test:

I have an Asrock Z77 Extreme4

which was the very first motherboard with nvme support.

There was a Bios before nvme and a Bios with nvme.

Just doing the same steps as above, it should awake legacy nvme

on the old Bios without nvme support.

 

EDIT2: The problem on the Sabertooth X79 board is now, that when I integrate "Setup" from Bios of X79-Deluxe,

the board (after resetting CMOS) starts only to "Press delete, for to enter UEFI Bios" but the compi does not react

to anything.



#259 Dietmar

Dietmar

    Frequent Member

  • Advanced user
  • 205 posts
  •  
    Afghanistan

Posted 2 days ago

Ok, with original "Setup" DXE file from Sabertooth X79 board

after integrating the files

 

Nvme

NvmeSmm

NVMEINT13

CSMCORE

 

CORE_DXE

LegacyInterrupt

LegacyRegion

AMITSE

Int10ToSmi

 

I came to the same result as yesterday:

All nvme devices are recogniced by their names

but when you boot from them the message appears

"Reboot and select proper boot device or insert boot media in selected boot device and press a key"

 

Dietmar



#260 Dietmar

Dietmar

    Frequent Member

  • Advanced user
  • 205 posts
  •  
    Afghanistan

Posted 2 days ago

Cool, I can INSTALL :ph34r:  :)  :)  :)  :ph34r:  XP SP3

on the Sabertooth X79 board

on nvme disk Toshiba RD400.

The nvme disk is recogniced.

The nvme disk Toshiba RD400 is the only device on this board

Dietmar

 

854503-1555425651.jpg

 

 

EDIT: I understand, what happens. XP builds from nvme.sys an ntbootdd.sys with signature entry

in the boot.ini for the nvme Toshiba RD400. But the problem ist, as I found out in last summer:

ntbootdd.sys only works for a scsiport driver. I checked this in ntldr. And here, nvme.sys depends on storport.sys.

Crazy, when we would have an nvme.sys, which is build from the OFA open source code based on scsiport instead

of storport, we could boot XP on any older compi from legacy nvme with my integrated files above.

So, the installationsroutine from XP :) does really its best, but crazy Bios does not recognice (until now) the nvme disk

as a bootable device.


  • agent_x007 likes this

#261 agent_x007

agent_x007

    Newbie

  • Members
  • 23 posts
  •  
    Poland

Posted 2 days ago

Can this even by done ?
(making OFE from ntbootdd.sys instead of storport.sys)

Could Vista be booted this way ?
Would BCD change things for XP booting (since in theory, BIOS didn't have to search for ntdlr at that point) ?
BCD should be able to detect ntdlr by itself... and may be more compatible (and reliable) as boot option with non-modified UEFI.


Edited by agent_x007, 2 days ago.


#262 Dietmar

Dietmar

    Frequent Member

  • Advanced user
  • 205 posts
  •  
    Afghanistan

Posted 2 days ago

I just make a try with Win2003 R2 install on Toshiba RD400

and nvme boot.

Exact the same happens: ntbootdd.sys is build

with signature of the Toshiba RD400 in boot.ini.

First step installation works,

but on reboot I get the same message as with XP,

"Reboot and select proper boot device or insert boot media in selected boot device and press a key"

because even win2003 uses storport,

for to build ntbootdd.sys it uses scsiport for its ntldr.

 

Now I make a try to modify the setup.dxe from the Asus X79-Deluxe board,

comparing it with its own version before nvme

Dietmar

 

PS: Is there a disassembler for modern UEFI Bios?



#263 Dietmar

Dietmar

    Frequent Member

  • Advanced user
  • 205 posts
  •  
    Afghanistan

Posted 2 days ago

All files in Bios from the nonnvme Bios 902

and the files in Bios from nvme Bios 4805

are nearly identic.

 

The biggest difference is in Bios from Asus X79-Deluxe

 

CsmcoreRawbody902.raw

CsmcoreRawbody4805.raw

 

They are to 100% identic, but at the end of it there comes the nvme module in the 4805,

which is absent in 902

Dietmar

 

EDIT: With Winhex, I put exact this nvme part at the end of the original CSMCORE.raw part

from the original Sabertooth X79 board.

I put only those 3 files in Bios

 

Nvme

NvmeSmm

NVMEINT13

CSMCORE

 

Now is the behavior: The exact name of the nvme device is found by Bios,

but then again comes this message

"Reboot and select proper boot device or insert boot media in selected boot device and press a key"

 

So, this is the minimal change, so that the Bios can detect the legacy nvme device,

but is not able to boot from it until now. -_-



#264 Dietmar

Dietmar

    Frequent Member

  • Advanced user
  • 205 posts
  •  
    Afghanistan

Posted 20 hours ago

After no success with legacy nvme Bios mod (crazy Bios shows nvme legacy disk with full name as bootable, but this is not true),

 

I take a closer look at the method from s4e.

This method is much better, than you may think.

 

When you install new software, after you only have to copy the updated HIVE SYSTEM from

C:\WINDOWS\system32\config of the nvme disk to the starter usbstick, this is all.

I noticed, that in HIVE SYSTEM also some parts of software are stored.

 

The fascination in the s4e method is, that you can boot from really everything, as long as you have driver for XP for this,

no matter what kind of Bios you have (USB2,3, Firewire, nvme..)

Dietmar

 

PS: By the way I noticed, that also Win 7 32 bit and Win 10 on mbr refuse to install

on this nvme disk. So, XP with ntbootdd is better :rolleyes: ..

If we only had nvme.sys for scsiport. XP can handle storport and scsiport at the same time, but ntbootdd needs scsiport.



#265 ruthan

ruthan
  • Members
  • 6 posts
  •  
    Czech_ Republic

Posted 17 hours ago

Hi,

1)  Im trying to select some cheap NVME just for testing, if i would be able to make NVME booting working, which one you would recommend (if some would work):

Patriot Scorch SSD 256GB
ADATA XPG SX6000 Lite SSD 256GB
Kingston A1000 240GB NVMe

GIGABYTE M.2 PCIe 256GB SSD
ADATA XPG SX6000 Pro SSD 256GB
 

2) Would work Samsung 970 evo plus with XP too? It seems to be good one as final solution. 

 

 

3) Where to get last version of these files?

2.) Copy the file storport.sys (vers. 5.2.3790.4173) to folder C:\WINDOWS\system32\drivers on your XP harddisk.

4.) Click on the folder nvme, where the files nvme.inf and nvme.sys (vers 1.3) from Kai are in.

 

 

4) That Z370, i have XP on Gigabyte Z370 and Z170, but i have with both problems with XP - browsers except IE werent responding, games had microfreezes etc.. it was because i had some ACPI problems, someone fixed for me Z170 bios is now ok.. for Z370 im waiting for fix. Did you have some problems with not Gigabyte boards?



#266 Dietmar

Dietmar

    Frequent Member

  • Advanced user
  • 205 posts
  •  
    Afghanistan

Posted 16 hours ago

Hi ruthan,

I think they work all.

The Adata XPG SX8200 seems to me good and cheap.

The file I call nvme.rar

and you can find him at

 

https://www.win-raid...C-parts-13.html

 

Dietmar

 

PS: XP works for me like a charm on all boards, that I have even on i486 - z390!

It can happen, when the timer does not work correct. Read about it at the Fernando forum above and at

https://msfn.org/boa...t-winxp/?page=5

 

file  ACPIcool.rar



#267 Dietmar

Dietmar

    Frequent Member

  • Advanced user
  • 205 posts
  •  
    Afghanistan

Posted 12 hours ago

For what kind of fun the s4e method can be used :rolleyes: :

I just boot one USB stick from another (clone).

May be it is possible, to do this with one USB stick alone:

You put the identic Bit by Bit copy two times on one USB stick,

a little bit like 2 partitions, but it is the same twice :P

Dietmar

 

EDIT: This works only, when the second USB stick is NOT recogniced

          from Bios before.



#268 ruthan

ruthan
  • Members
  • 6 posts
  •  
    Czech_ Republic

Posted 11 hours ago

Thanks.

 

These identical copied? There is not tool which able to make them corrrecly, you have to use some hex editor magic? Do you tested R-Drive image, Partition Wizzard, or Acronis Trueimage, Paragon HDD suite?



#269 Dietmar

Dietmar

    Frequent Member

  • Advanced user
  • 205 posts
  •  
    Afghanistan

Posted 11 hours ago

With Winhex it is possible.

I thought about as a joke,

but now I test :D

Dietmar

 

EDIT: Even not so easy with Winhex, but just in this moment

I am copying whole USB partition with mbr and offset 2048 again on this stick,

direct after first.



#270 Dietmar

Dietmar

    Frequent Member

  • Advanced user
  • 205 posts
  •  
    Afghanistan

Posted 10 hours ago

Alone this USB stick with clone in itself shows BSOD 0x7B.

I think, XP ignores just the existence of clone.

But it still boots the nvme disk.

Take a look, what Winhex tells about this USB stick:

Cyl: 7551

 

Dietmar

f73de3-1555620078.jpg






0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users