-
-
Notifications
You must be signed in to change notification settings - Fork 314
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
The Win7 system uses the diskLayout method to return an empty array #950
Comments
@yangbin11 can you describe the problem in English ? My Chinese is actually not good enough. Please change title ad add a clear description. Thank you in advance! |
My description is incorrect. When I do not insert the recording pen device, it can recognize the disk array information. After inserting the recording pen, it returns an empty array |
@sebhildebrandt Brother, I'm sorry.. Why haven't you replied to me yet? I understand that Win7 supports up to Node13 version, but currently my application is installed on version 16. I'm not sure if this issue is causing it |
@yangbin11 ... when you are using version 4.0.7 of systeminformation, this is a 6 year old version. Can you check it also with the latest version? |
@sebhildebrandt I am glad to receive your reply. In fact, I have tested version 5.23, but unfortunately using diskLayout returns an empty array. When I use version 4.0.7 without inserting a recording pen USB device, the expected disk array information can be returned on Win7, while debugging with a recording pen USB device returns an empty array. I'm not sure if my description is clear... |
Describe the bug
使用si.diskLayout() 函数查出空数组
To Reproduce
Steps to reproduce the behavior:
si.diskLayout()
Current Output
If applicable, add output to help explain your problem.
Expected behavior
A clear and concise description of what you expected to happen.
Environment (please complete the following information):
systeminformation :4.0.7
platform:window
release:6.1.7601
kernel:6.1 .7601
arch:X64
hostname:USER-ONVAR3H3DM
To get all needed environment information, please run the following command:
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: