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
323 replies to this topic

#76 Dietmar

Dietmar

    Frequent Member

  • Advanced user
  • 236 posts
  •  
    Afghanistan

Posted 24 July 2018 - 04:58 PM

Hi dencorso,

on day after tomorrow I will try to install XP on a x58 mainboard.

There is only 1 PCIe slot and no graphic in processor,

so I ordered a cheap PCI graphik card.

Because NT4 and reactos start to install on the 950 pro nvme,

I come to the idea, that it may be because of the emulated IDE controller

from the 950 pro card. The only compi, where I can install XP on this card

is my Asus z370. And this computer has no IDE at all, crazy :).

To disable IDE in Bios may not be enough. So today I will make a try to

remove the IDE driver in Bios. I am sure, that it is a simple conflict between

Bios from motherboard and BIOS from 950 pro,

have a nice day

Dietmar



#77 Dietmar

Dietmar

    Frequent Member

  • Advanced user
  • 236 posts
  •  
    Afghanistan

Posted 24 July 2018 - 05:50 PM

I also try to install on this 950 pro card XP with original

XP bootdisk from Teac USB floppy. Funny, on my Asus z370 compi this works,

but on all other compis: In the moment, when the 950 pro is recogniced via

the bootfloppy (you can see blue LED flashing) on 950 pro adapter,

it halted. So, very easy, there mus be a conflict. But how to solve?

I never saw before, that the XP bootfloppy is frozen

Dietmar



#78 Wonko the Sane

Wonko the Sane

    The Finder

  • Advanced user
  • 15108 posts
  • Location:The Outside of the Asylum (gate is closed)
  •  
    Italy

Posted 24 July 2018 - 06:44 PM

As a side-side note, and should any of the good guys from the ReactOS project come by, there was a few years back some *undocumented* or *experimental* report that the ReactOS FREELDR could actually boot Windows Server 2003.

 

I was never able to find :blush: (and remember  I am The Finder ;)  ) any proper confirmation that it actually worked, though, let alone any - if not instructions - examples on how to use the (supposed) feature.

 

If anyone is going to work on the FREELDR code it would be the "right" moment to:

1) have it boot XP, besides 2003 (provided that 2003 is actually bootable)
2) check what (the heck) is happening with nvme

 

:duff:

Wonko



#79 Dietmar

Dietmar

    Frequent Member

  • Advanced user
  • 236 posts
  •  
    Afghanistan

Posted 24 July 2018 - 07:08 PM

Hi jaclaz,

I saw a video of booting reactos with FREELDR to WinServer 2003.

And also nearly XP, as I remember, it hangs in last few seconds of boot.

Now reactos 0.49 is out. It is an amazing project,

they also import storport.sys with the extendend functions and a lot

of programs for Win10 can run there. But it goes on very slowly.

May be in 2019, after end of support for XP embedded,

this is future

Dietmar

 

PS: The thing with the nvme disk 950 pro and XP is really crazy.

I deleted AINT13 in Bios. With the result, that I cant boot from harddisk after this, it is not listed as boot device anymore.

But the 950 pro still shows "ntldr not found" and is listed as bootdevice. Hm, this means, 950 pro depends not on INT13

and maybe, all the problems with XP come from this. Yeppp, putting AINT13 back to BIOS, black WD2TB appears again and gives crazy like "snowflakes in stripes" :P  crash on beeing together with 950 pro!



#80 Dietmar

Dietmar

    Frequent Member

  • Advanced user
  • 236 posts
  •  
    Afghanistan

Posted 25 July 2018 - 09:26 AM

Hi all,

on MSi MS-7379 with Intel Core 2 Quad Q6600

installing the Samsung 950 pro nvme as only bootdevice,

gives blinking cursor and frozen, not possibel to go to Bios

Dietmar

 

 

#81 Dietmar

Dietmar

    Frequent Member

  • Advanced user
  • 236 posts
  •  
    Afghanistan

Posted 25 July 2018 - 09:48 AM

For to make sure,

that my build of this 10 years old compi with MS 7379 board works,

I changed the 950 pro in graphicard slot against 960 pro.

 

On Win7 with the nvme.sys ver. 1.3 from Kai gives

 

-----------------------------------------------------------------------
CrystalDiskMark 5.1.2 © 2007-2016 hiyohiyo
                           Crystal Dew World : http://crystalmark.info/
-----------------------------------------------------------------------
* MB/s = 1,000,000 bytes/s [SATA/600 = 600,000,000 bytes/s]
* KB = 1000 bytes, KiB = 1024 bytes

   Sequential Read (Q= 32,T= 1) :   833.926 MB/s
  Sequential Write (Q= 32,T= 1) :   668.875 MB/s
  Random Read 4KiB (Q= 32,T= 1) :   276.080 MB/s [ 67402.3 IOPS]
 Random Write 4KiB (Q= 32,T= 1) :   248.430 MB/s [ 60651.9 IOPS]
         Sequential Read (T= 1) :   771.619 MB/s
        Sequential Write (T= 1) :   635.718 MB/s
   Random Read 4KiB (Q= 1,T= 1) :    48.797 MB/s [ 11913.3 IOPS]
  Random Write 4KiB (Q= 1,T= 1) :   111.860 MB/s [ 27309.6 IOPS]

  Test : 1024 MiB [L: 2.7% (12.7/476.9 GiB)] (x5)  [Interval=5 sec]
  Date : 2018/07/25 11:36:34
    OS : Windows 7 Home Premium SP1 [6.1 Build 7601] (x86)

 

Dietmar



#82 Dietmar

Dietmar

    Frequent Member

  • Advanced user
  • 236 posts
  •  
    Afghanistan

Posted 25 July 2018 - 12:38 PM

Next test on Acer FX58M (Intel X58 chipset) with i920 processor.

The Samsung 950 pro is at once recogniced as IDE device.

Together with an hardisk with XP boot, it gives the snowflakes in stripes crash.

Also it is not possible to install XPSP3 on it (crashes when pressed key message for to boot from CD), same behavior as on other motherboards.

I also noted, that on XP, it can there not work as codevice, also not 960 pro.

This is all because of INT13 I think. Those nvme disks can not be hotpluged like USB stick.

Interesting, if this is the case for other mainboards too,

have a nice day

Dietmar

 

PS: In next days I make new tests with XP nvme boot on Asrock z77 extreme 4.

       They offered a new BIOS with full nvme support, also legacy which you can see,

       when you download BIOS ver. Z77 Extreme4(2.90P)ROM

      

https://www.asrock.c...dex.de.asp#BIOS

      

      The newest BIOS 3.0 has much less support for nvme.

      This is one of the latest motherboards with full XP support for Ivy Bridge chipset.



#83 Dietmar

Dietmar

    Frequent Member

  • Advanced user
  • 236 posts
  •  
    Afghanistan

Posted 25 July 2018 - 03:01 PM

Hi all,

on Asus z87-pro (without any nvme in Bios)

with bootdevice XP on harddisk it is possible, to use the Samsung 960 pro as codevice.

Just copy storport.sys ver. 5.2.3790.4173  to folder C:\Windows\system32\drivers

and install the nvme.sys ver. 1.3 from Kai.

 

Here CristalDiskMark

 

Asusz87-pro with 960 pro as codevice only XP
-----------------------------------------------------------------------
CrystalDiskMark 5.1.2 © 2007-2016 hiyohiyo
                           Crystal Dew World : http://crystalmark.info/
-----------------------------------------------------------------------
* MB/s = 1,000,000 bytes/s [SATA/600 = 600,000,000 bytes/s]
* KB = 1000 bytes, KiB = 1024 bytes

   Sequential Read (Q= 32,T= 1) :  3319.434 MB/s
  Sequential Write (Q= 32,T= 1) :  2070.767 MB/s
  Random Read 4KiB (Q= 32,T= 1) :   509.035 MB/s [124276.1 IOPS]
 Random Write 4KiB (Q= 32,T= 1) :   515.009 MB/s [125734.6 IOPS]
         Sequential Read (T= 1) :  2784.229 MB/s
        Sequential Write (T= 1) :  2013.824 MB/s
   Random Read 4KiB (Q= 1,T= 1) :    58.182 MB/s [ 14204.6 IOPS]
  Random Write 4KiB (Q= 1,T= 1) :   220.617 MB/s [ 53861.6 IOPS]

  Test : 1024 MiB [D: 2.7% (12.7/476.9 GiB)] (x5)  [Interval=5 sec]
  Date : 2009/01/01 1:19:10
    OS : Windows XP Professional SP3 [5.1 Build 2600] (x86)

 

Dietmar



#84 Dietmar

Dietmar

    Frequent Member

  • Advanced user
  • 236 posts
  •  
    Afghanistan

Posted 25 July 2018 - 09:11 PM

Hi cdob,

can you please tell me step by step,

how you make steps more easy in "Kansas City Shuffle"?

Which points you change? Here at reboot I only find 1 page, where you tell about.

I will try this also for nvme boot, because I noticed that ALL the other tutorials in web

about nvme boot are only for UEFI nvme.

This Tutorial will be valid also for any legacy boot from nvme on nearly every compi. And may be,

the fake "CD" can also been put on the same nvme disk, because I noticed, that the MBR from the nvme can be read with UEFI nvme.

 

Windows XP boots from USB and nvme

Author: Dietmar Stölting, 16 March 2008  updated 29 July 2018
dietmar.stoelting@t-online.de
Germany

Thanks to s4e, who told us his idea.

 

This tutorial works on any device with a mbr and a driver. No need for Bios support.

Tutorial (Version 7)

 

1.) Connect an USB or nvme harddisk to your working XP or install first a fresh XP
on your normal harddisk.
This XP has to stay on the first partition of the first harddisk.
If you have no USB, nvme, or all USB is disabled in Bios or only USB1.1,
insert an USBtoPCI slotcard or nvme disk via slotcard.
The USB hardisk has to be connected to your XP, because the drivers for
the USBtoPCI slotcard and for the USB harddisk must be installed there.
Only one, and that must be the first partition, is allowed on the USB
harddisk.
Disable the pagefile.
Copy this XP to that USB, nvme harddisk, may be on an other comuter. I use AOMEI.
It can be Fat, Fat32, NTFS, doesnt matter.
Dont change the filesystem.
It works on XP, XP SP1, SP2, SP3, nvme works only for XP SP3.

2.) For USB, make the XP on the USB harddisk USB bootfriendly, use Tutorial 3, 4 or 6,

     for nvme add storport.sys 5.2.3790.4173 from Winserver 2003 and nvme.sys ver. 1.3 from Kai.

3.) Get the files mkimg.zip, vdk32-050406.zip, dsfok.zip,
gsar121.zip, mksparse.zip, mbrbatch002.zip, DumpHex-1.0.1.zip,
grub4dos-0.4.3-2008-03-14.zip, SetupImgBurn_2.4.0.0.exe, mkisofs.exe from
pebuilder3110a, contig.exe from Microsoft (Sysinternals)
Unzip them all to the root folder C:\ of your working XP.
You can use other programs also.

4.) Generating a virtual harddisk with a size of 100 MB.
Type at the commandline of your working XP C:\mkimg , name it otto, chose
100M size, 128/63 geometry, 07 for NTFS, and then /fsz for building a 100 MB
virtual harddisk, format it with j. Format it with XP to Fat32 or to NTFS.
IF XP dont like to do that, format an 100MB empty file from Qemu.
If this does not work, shrink a real partition with working XP via AOMEI.

5.) Copy now from your external USB bootfriendly harddisk (or nvme disk) the following
files to the 100MB virtual harddisk:

BOOT.INI with a content of

[boot loader]
timeout=30
default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="USB Windows"

NTDETECT.COM (best (?) is modified one, when you get)
NTLDR

WINDOWS\AppPatch\drvmain.sdb

WINDOWS\FONTS\vga850.fon
WINDOWS\FONTS\vgaoem.fon

WINDOWS\INF\biosinfo.inf

WINDOWS\system32\bootvid.dll
WINDOWS\system32\c_1250.nls (in germany instead c_1252.nls)
WINDOWS\system32\c_850.nls
WINDOWS\system32\hal.dll
WINDOWS\system32\kdcom.dll
WINDOWS\system32\l_intl.nls
WINDOWS\system32\ntkrnlpa.exe
WINDOWS\system32\ntoskrnl.exe
WINDOWS\system32\config\system
WINDOWS\system32\drivers\  (all, means also nvme.sys and storport.sys for NVME)

6.) Make a Bit to Bit copy of your virtual 100 MB harddisk, with MBR and
partitionstable. I use therefor Winhex.
Name it XP.IMG (Case sensitive)

7.) Open in Winhex XP.IMG and the USB (nvme) harddisk. Have a look at both of
their first 512 Byte (MBR).
Save those 512 bytes (MBR) each on your working XP as XPIMGMBR.dat and
USBHDMBR.dat.

Now comes the most critical procedure to fake the SIGNATURE and give both
MBR the same checksum.

Compare the first 512 Bytes of both MBR:
The only differences that are allowed at the moment, stay in 1B8, 1B9,
1BA, 1BB , this is the place of the SIGNATURE and 1C0, 1C1...to 1CF, the
size of each Harddisk.

Write the SIGNATURE of the external harddisk to the SIGNATURE of the
XP.IMG.
This means, to write the values in 1B8, 1B9, 1BA, 1BB of the harddisk to
the same place into MBR of XP.IMG.

Then write 1C0...1CF of the external harddisk to 1A0...1AF of the XP.IMG.


Then write 1C0...1CF of XP.IMG to 1A0...1AF to the external harddisk.

Compare once more the MBRs of XP.IMG and the USB harddisk.
There must now be correspondending differences in 1A0...1AF and
1C0...1CF.


8.) Open the commandline of the working XP and type there at C:\

mkdir iso_root
copy grldr iso_root
copy menu.lst iso_root
copy XP.IMG iso_root

9.)

Run from commandline    

contig.exe C:\iso_root\XP.IMG

that the file is continues for mapping in grub4dos.

 

Go to C:\iso_root. There are now XP.IMG, menu.lst, and grldr.

Open menu.lst with the editor and delete all its content.

Put into menu.lst:

title Image chainloading USB (or nvme)
map --read-only /XP.IMG (hd0)
map --hook
chainloader (hd0,0)/ntldr

10.) Go to commandline and type at C:\

mkisofs -R -b grldr -no-emul-boot -boot-load-size 4 -o grldr.iso iso_root

This gives you in C:\ the file grldr.iso.

11.) Burn grldr.iso with SetupImgBurn or Nero to a CD.

12.) Shut your compi down and restart with that CD and the connected USB or nvme
       harddisk to USB XP.

13.) First test, if your CD gives you the XP-bootscreen after grub4dos window.

Dietmar
 



#85 Wonko the Sane

Wonko the Sane

    The Finder

  • Advanced user
  • 15108 posts
  • Location:The Outside of the Asylum (gate is closed)
  •  
    Italy

Posted 26 July 2018 - 10:54 AM

Dietmar, if you use the copysgcs by Karyonix:

http://reboot.pro/to...2-sp2/?p=207270

 

the procedure will be much simpler.

 

 

C:\Downloaded>copysgcs.exe
Copy MBR signature and checksum
Usage : copysgcs srcfilename dstfilename [offsetcs]

srcfilename Source MBR image file name
dstfilename Destination MBR image file name
offsetcs Offset of a safe place to modify 4 bytes data in destination MBR
If not specified, the program will not clone checksum

the checksum is written to a set of contiguous 4 bytes, a "good" offset for this (used by convention originally) is 0x1B0.

 

:duff:

Wonko



#86 Dietmar

Dietmar

    Frequent Member

  • Advanced user
  • 236 posts
  •  
    Afghanistan

Posted 26 July 2018 - 11:21 AM

Hi jaclaz,

when I succeed, I write new tutorial.

At the moment I am just doing my own tutorial just for nvme.

I remember very good soo many blue screens, for example that you have first to format fakeimage to ntfs and then back to fat32.

Also I tested nvme boot XP for Fat16. It works.

In about 2 hours I write more what happens :rolleyes: ,

have a nice day

Dietmar



#87 Dietmar

Dietmar

    Frequent Member

  • Advanced user
  • 236 posts
  •  
    Afghanistan

Posted 26 July 2018 - 11:55 AM

Hi jaclaz, the first error is using mkimg.exe:

The image is unmoutable.

What do you think: Can this happen, because it is build for IDE

and I have AHCI? Can I also use qemu, fo to build the emty image?

Oha, not so easy I think,

Dietmar



#88 Wonko the Sane

Wonko the Sane

    The Finder

  • Advanced user
  • 15108 posts
  • Location:The Outside of the Asylum (gate is closed)
  •  
    Italy

Posted 26 July 2018 - 12:28 PM

I have no idea what mkimg.exe is, maybe you mean my (good :unsure: ) old mkimg.cmd?

 

Nowadays it should be faster/better/whatever to use the Arsenal Image Mounter or the KernSafe driver or (suggested in this case) the MS "own" vss driver.

 

See here:

http://reboot.pro/to...storage-driver/

the created drive image will be mounted as a "proper" physicaldrive (and as such is seen in both Diskpart and Disk Manager), so it is easier to create the partition and format it.

 

:duff:

Wonko



#89 Dietmar

Dietmar

    Frequent Member

  • Advanced user
  • 236 posts
  •  
    Afghanistan

Posted 26 July 2018 - 01:29 PM

Hi jaclaz,

I use the XPSP3 install CD,

after I build with Qemu a 100MB otto.raw disk.

XP Install CD cries, that not enough space.

But I can format this disk, can not be better,

is real XP like,

ok,

now fun starts

Dietmar



#90 Dietmar

Dietmar

    Frequent Member

  • Advanced user
  • 236 posts
  •  
    Afghanistan

Posted 26 July 2018 - 02:43 PM

Hm, I cant build the iso with mkisofs.exe from pebuilder3110a.

 

mkisofs -R -b grldr -no-emul-boot -boot-load-size 4 -o grldr.iso iso_root

 

There comes a message, that the wrapper.cmd is missed,

Dietmar



#91 Dietmar

Dietmar

    Frequent Member

  • Advanced user
  • 236 posts
  •  
    Afghanistan

Posted 26 July 2018 - 03:16 PM

Ok, this was because of a corrupted file mkisofs.exe from pebuilder3110a.

I found working and build boot CD for nvme.

Boot CD starts, but then hangs after message Filesystem type is fat, partitiontype 0xb

oh my,

but I will make next try

Dietmar



#92 Dietmar

Dietmar

    Frequent Member

  • Advanced user
  • 236 posts
  •  
    Afghanistan

Posted 26 July 2018 - 06:23 PM

I make a complete new try:

First I install XP Sp1 with IDE to the Asus z87-pro motherboard on a 1900 MB partition with NTFS.

There I install storport.sys and nvme.sys ver. 1.3 from Kai.

I test, if the 960 pro is recogniced from this harddisk, no nvme in Bios at all.

Then I make with WinHEX on my Asus z370 compi a bit to bit copy from this harddisk to the 960 pro nvme disk.

After this, I modify MBR and check sum of MBR as s4e tolds, on 960 pro and the harddisk.

After this I install grub4dos on the harddisk, without any fake image I try to start with this harddisk the nvme disk 960 pro

on Asus z87-pro,

have a nice day

Dietmar



#93 Dietmar

Dietmar

    Frequent Member

  • Advanced user
  • 236 posts
  •  
    Afghanistan

Posted 26 July 2018 - 07:25 PM

XP Sp1 does not work with nvme at all

Dietmar



#94 Dietmar

Dietmar

    Frequent Member

  • Advanced user
  • 236 posts
  •  
    Afghanistan

Posted 26 July 2018 - 11:17 PM

The s4e methode seems not to work for nvme boot.

I tried boot from CD, boot from harddisk. I am sure, that I did everything correct, even I

use contig.exe that the XP.IMG file is continues before mapping.

No flashing LED on nvme disk.

This is other situation as with usb boot.

I remember very good, that even through crashes,

always was some reaction on the connected usb disk.

Here with nvme is no difference between connected nvme disk or not.

Grub4dos just hangs (no matter, if nvme disk is connected or not), no boot.ini entries can be seen and this means,

something goes wrong on fake disk, because in other case you would see

the 2 entries in boot.ini there

 

Dietmar

 

PS: I tried Fat32 and NTFS.

 

EDIT: NO because with floppy it works(Something is wrong with the fake Image. I copied the fake image XP.IMG direct to an harddisk.

          But no switches in boot.ini can be seen: "Fehler beim Laden des Betriebssystems"

          Oh, this looks to me, as if some more files are necessary in XP Sp3 than for XP SP1 or SP2 in the minimage.)

          (Other possibility is, that it hangs because of loading the nvme.sys file and storeport.sys:No, because the same

            error message after I renamed nvme.sys file and storeport.sys. So I think, files are missed in fake XP.IMG for    boot.)

 

EDIT2: Qemu running with the fake XP.IMG tells "BIOS panic at rombios.c, line 11051". Any idea?
EDIT3: With USB boot floppy with ntldr, ntdetect.com and boot.ini I can start the fake XP.IMG,

            strange...



#95 Dietmar

Dietmar

    Frequent Member

  • Advanced user
  • 236 posts
  •  
    Afghanistan

Posted 27 July 2018 - 08:29 AM

It works :)

 

but some things I do not understand until now

 

Dietmar



#96 Dietmar

Dietmar

    Frequent Member

  • Advanced user
  • 236 posts
  •  
    Afghanistan

Posted 27 July 2018 - 09:40 AM

XP SP3 gets more information about correct mbr than XP sp2, Sp1.

And correcting with fixmbr does not help!

 

So I did the following:

I copy bit by bit with Winhex a working 2000 MB NTFS image to the 960 pro disk

AND the same image to the underlying harddisk. I compare with Winhex 100% identic.

Then I delete nearly all files on harddisk, only those I named in Tutorial 7 stay on harddisk.

After starting with this "harddisk", I disconnect it.

Now nvme 960 pro is only device, connected to the Asus z87-pro motherboard.

 

Voila, nvme disk 960 pro is shown as c:\ , I make defrag on it just for fun (LED on nvme card flashes as much as possible) and play pinball.

 

Hihi, works, legacy nvme XP on a motherboard, that never heard in life about nvme.

Should work on nearly every compi with a Pcie slot.

 

The problem in this first try is: The disks have real different geometries. I did NO changes in mbr,

they are 100% identic.

And: When you let the harddisk connected, XP writes something back,

so it works until now only one time :rolleyes:. Only with Fat32 it is possible to reduce writes to zero.

I remember this behavior from Usb boot: Because of this in booting with grub4dos is the readonly switch.

Even this does not work and because of this in Tutorial 7 I use CD for boot,

have a nice day

Dietmar



#97 Dietmar

Dietmar

    Frequent Member

  • Advanced user
  • 236 posts
  •  
    Afghanistan

Posted 27 July 2018 - 12:15 PM

Now I use just my tutorial 7

for to bring this fake image 100MB with corrected mbr and also corrected mbr on nvme 960 pro to CD.

This time, the CD starts, I see the Zebra-stripes agian during loading from CD, the LED flashes on 960 pro,

but then reboot..brr..

Dont know, what happens,

Dietmar

 

PS: The fake image works, I use contig for the Fake image and the mbr corrections after chkdsk exakt as s4e did.



#98 Dietmar

Dietmar

    Frequent Member

  • Advanced user
  • 236 posts
  •  
    Afghanistan

Posted 27 July 2018 - 12:39 PM

I found out, that this time it is the fault of the XP on the nvme disk 960 pro. This one reboots.

Strange, this looks like, if XP SP3 cannot start after the mbr corrections via s4e

Dietmar



#99 Dietmar

Dietmar

    Frequent Member

  • Advanced user
  • 236 posts
  •  
    Afghanistan

Posted 27 July 2018 - 01:27 PM

Yessa I got it via boot from CD!!!

 

ONLY nvme disk 960 pro connected to Asus z87-pro.

 

For this I make a new XP image on the 960 pro,

copy the MBR from image before on it

and change nothing on CD,

 

Dietmar



#100 Dietmar

Dietmar

    Frequent Member

  • Advanced user
  • 236 posts
  •  
    Afghanistan

Posted 28 July 2018 - 08:49 AM

Hi all,

 

is there a possibility to do a warm reboot on XP (INT19),

like reboot.com for DOS?

This would allow, to start XP from drivers in memory in 1. boot.

 

Have a nice day

Dietmar






0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users