search

tmcdos / ramdisk

Replacement (GUI + windows service) for ImDisk Toolkit - by using Arsenal Image Mounter as a driver for RAM-disks.
MIT License
39 stars 7 forks source link

The data area passed to a system call is too small #1

Open chromecut001 opened 3 years ago

chromecut001 commented 3 years ago

I keep getting this error when attempting to use your software

"The data area passed to a system call is too small"

also there are no instructions listed anywhere

Im assuming you replace the gui and service files with the one located in imdisk's post installed win10 program folder

how does the arsenal driver come into play? once installed I dont see how to direct your imdisk replacement to use aresnal as the driver instead of the built in imdisk driver

When working this could be some amazing software and solves a lot of issues as AMD ramdisk while easy to setup does not have the arsenal driver and its features but does handle persistant disks with ease-now that is a gui that you should mimic and intel's cache software would work wonderfully with your persistant ram drive tool

I own a consulting business and depending on the costs (your labor) I would be interested in developing this for resale-I have many potential projects I need help with

I also need a bios editor which may not be your strong suit it will not matter as I have done most of the work and your insite/guidance would be invaluable as most bios programmers are "it looks good on paper" people and have zero creativity or the abiliuty to see beyond their code to adapt to real world situations and usually high end programmers like yourself always "I have a guy" to turn to when you are stumped

feel free to contact me

thank you for your hard work

ken eglinton 480-652-8267 keneglinton@yahoo.com

tmcdos commented 3 years ago

Ken, I replied to you by email - I'm not sure if you received my message, please check the SPAM folder.

longyn commented 1 year ago

Hi tmcdos,

Thanks for your tool.

But I met the same problem when start RamDiskUI.

I have installed DriverSetup.7z\Win10\phdskmnt.inf and DriverSetup.7z\ctlunit\ctlunit.inf and then put RamdiskUI.exe, RamService.exe in the same folder.

Once click RamdiskUi.exe(As an Administrator), it pop up error, no ramdisk created R:. In Windows Service, there is a service named "ArsenalRamDisk" is running.

Am I missed something here?

Best Regards, Frank

tmcdos commented 1 year ago

Can you post screenshots from the UI (without the error popup) and then with the error popup ?

longyn commented 1 year ago

Thank you for reply, here is a gif:

ramdisk_error

tmcdos commented 1 year ago

I have released a new version - can you try it and share your feedback? If still not working, can you also share the output from DebugView (you can download it from https://learn.microsoft.com/en-us/sysinternals/downloads/debugview) - begin capturing before running RamDiskUI.

longyn commented 1 year ago

I have released a new version - can you try it and share your feedback? If still not working, can you also share the output from DebugView (you can download it from https://learn.microsoft.com/en-us/sysinternals/downloads/debugview) - begin capturing before running RamDiskUI.

Ramdisk v1.1 works for me on my laptop.

But there is another problem when I test it in a qemu Virtual Machine, it's failed to create a ramdisk, and the UI freezed.

The original mounttool works well.

I'll upload a log later.

longyn commented 1 year ago

Here is the log

PhDskMnt: Blank filenames only supported for non-zero length vm type disks.
[6736] ?????
[6736] ???????

PhDskMnt::ImScsiInitializeLU: Unique id: {4a2c4a98-09a7-11ee-b1e3-bfd5f7488173}
[7816] ???????
[9064] 06/13/2023  9: 6:15.00000604:RegEnumKeyExW failed with (259)
[9064] 06/13/2023  9: 6:15.00000604:GP object initialized successfully
[9064] 06/13/2023  9: 6:15.00000604:Deny_All not set for all. Will query other 6 GUIDs
[9064] 06/13/2023  9: 6:15.00000604:Policy for other GUID is not enabled, status:  3
[9064] 06/13/2023  9: 6:15.00000604:Policy for other GUID is not enabled, status:  3
[9064] 06/13/2023  9: 6:15.00000604:Policy for other GUID is not enabled, status:  3
[9064] 06/13/2023  9: 6:15.00000604:Policy for other GUID is not enabled, status:  3
[9064] 06/13/2023  9: 6:15.00000604:Policy for other GUID is not enabled, status:  3
[9064] 06/13/2023  9: 6:15.00000604:Policy for other GUID is not enabled, status:  3
[7816] ???????

PhDskMnt::ImScsiInitializeLU: Unique id: {4a2c4b6e-09a7-11ee-b1e3-bfd5f7488173}
[8360] ???????
[9064] 06/13/2023  9: 7:54.00000918:Deny_All not set for all. Will query other 6 GUIDs
[9064] 06/13/2023  9: 7:54.00000918:Policy for other GUID is not enabled, status:  3
[9064] 06/13/2023  9: 7:54.00000918:Policy for other GUID is not enabled, status:  3
[9064] 06/13/2023  9: 7:54.00000918:Policy for other GUID is not enabled, status:  3
[9064] 06/13/2023  9: 7:54.00000918:Policy for other GUID is not enabled, status:  3
[9064] 06/13/2023  9: 7:54.00000918:Policy for other GUID is not enabled, status:  3
[9064] 06/13/2023  9: 7:54.00000918:Policy for other GUID is not enabled, status:  3
[8360] ???????
tmcdos commented 1 year ago

Do you know how can I reproduce the freezing in VirtualBox ?

longyn commented 1 year ago

I didn't test in VirtualBox, but in Hyper-V and qemu virtual machine.

OS: Windows Server 2019 10.0.17763.3887

Here is qemu virtual machine config:

Memory                 8.00 GIB/16.00 GiB
Processors             16 (2 sockets, 8 cores)
BIOS                   Default (SeaBIos)
Display                Default
Machine                Default (i440fx)
SCSI Controller        Virtlo scsi
Hard Disk (scsi0)      vm-001-disk-0,cache=writeback,size=180G
tmcdos commented 1 year ago

I don't have access to Hyper-V or Windows Server - only VMware Player and VirtualBox. Here is a debug build - it should provide a stacktrace so I can get a better idea what might be happening. RamdiskUI.zip

longyn commented 1 year ago

Here is the new logs:



![12](https://github.com/tmcdos/ramdisk/assets/5205838/39eeaa9e-3dae-4363-a8a2-5b17ed38dd98)
tmcdos commented 1 year ago

This will take some time as I am on Win7 and will have to create an environment similar to yours and hope that the issue will be reproduced. Stay tuned.