Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Windows Server 2003 VM support #1

Closed
Zero3K opened this issue Sep 7, 2019 · 17 comments

Comments

@Zero3K
Copy link

commented Sep 7, 2019

It would be nice if it you could get it to work in a x86/x64 Windows Server 2003 VM. I tried the version available at https://sourceforge.net/projects/nvme-for-windows-2003-server/ (which didn't work in either architecture). It gave me a "Code 10" error in its Properties that is available via Device Manager and froze the OS when trying to boot with a disk image associated to the NVMe controller that I had added to the VM's settings (both VMWare Workstation Player 15 and VirtualBox resulted in the same thing happening).

@Zero3K

This comment has been minimized.

Copy link
Author

commented Sep 7, 2019

I tried using WDK 7600.16385.1 to build it under the Windows Server 2003 x86 Checked Build Environment using the attached .cmd and it didn't work (it told me that it was missing some files):

make_chk.zip

@csm10495

This comment has been minimized.

Copy link
Owner

commented Sep 7, 2019

@Zero3K

This comment has been minimized.

Copy link
Author

commented Sep 7, 2019

I wasn't able to get any debug output with the build I was using. Which is why I wanted to use yours since you added some debug output. The reason why I want support for Windows Server 2003 is because ReactOS uses it as a base.

@Zero3K

This comment has been minimized.

Copy link
Author

commented Sep 7, 2019

"Windows cannot load the device driver for this hardware. The driver may be corrupted or missing. (Code 39)" Is what I get when I try to install the driver in a Windows Server 2003 x86 VM.

@csm10495

This comment has been minimized.

Copy link
Owner

commented Sep 7, 2019

@Zero3K

This comment has been minimized.

Copy link
Author

commented Sep 7, 2019

I think its because its a Windows 7 driver trying to load in Windows Server 2003.

@Zero3K

This comment has been minimized.

Copy link
Author

commented Sep 7, 2019

And when I tried adding the two files (generated using Visual Studio 2017) in the attached archive to the source directory then running the .cmd I attached earlier, I get a bunch of errors:

nvmeMofData.zip

EDIT: Maybe you could take a look at the source code of the driver that I linked to in the Issue's description and see if there's anything that points to it not working or use it as a reference to get yours compiling for Windows Server 2003.

@Zero3K

This comment has been minimized.

Copy link
Author

commented Sep 7, 2019

(sdk/lib/rtl/image.c:428) Unknown/unsupported fixup type 11.
(sdk/lib/rtl/image.c:430) Address 00746008, Current 0, Count 2181, *TypeOffset b924
(sdk/lib/rtl/image.c:505) Error during call to LdrProcessRelocationBlockLongLong()!
(../boot/freeldr/freeldr/ntldr/winldr.c:335) err: Can't load boot driver 'System32\drivers\nvme.sys'!

That is what one guy who tried the driver had happen for him in ReactOS.

@Zero3K

This comment has been minimized.

Copy link
Author

commented Sep 7, 2019

You could try joining https://chat.reactos.org/reactos/channels/development and asking for help on getting it to work in Windows Server 2003/ReactOS.

@csm10495

This comment has been minimized.

Copy link
Owner

commented Sep 7, 2019

I'm not likely to work on this request. You're free to contact them if you want to work on it and pull request a solution

@Zero3K

This comment has been minimized.

Copy link
Author

commented Sep 7, 2019

I did but they told me they won't consider working on it, etc. until it works in Windows Server 2003. By the way, I'm not a developer.

@Zero3K

This comment has been minimized.

Copy link
Author

commented Sep 8, 2019

I tried asking other developers but they are either too busy or not interested.

EDIT: Getting it to where it can be compiled for Windows Server 2003 x86/x64 shouldn't be too hard to do.

@Zero3K

This comment has been minimized.

Copy link
Author

commented Sep 8, 2019

Any more thoughts?

@csm10495

This comment has been minimized.

Copy link
Owner

commented Sep 8, 2019

You are free to do it and pull request if you would like.

@Zero3K

This comment has been minimized.

Copy link
Author

commented Sep 8, 2019

I might as well close this issue then since I am not a developer and no one wants to help.

@Zero3K

This comment has been minimized.

Copy link
Author

commented Sep 8, 2019

I hope I am wrong and someone does help soon.

@Zero3K

This comment has been minimized.

Copy link
Author

commented Sep 8, 2019

I'm going to close it. Sorry for wasting your time.

@Zero3K Zero3K closed this Sep 8, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
2 participants
You can’t perform that action at this time.