version 0.4 : cosmetic work!
last for the day
Posted 02 October 2013 - 10:12 PM
@olof
This is yet another fantastic tool to add to my collection - ImDisk has been my favourite virtual drive tool since you made it available on the forum. It looks like I'll also be using this in the future too!
@erwan.l
Tested in Windows 7 (x86) - appears to be working fine - once I remembered to run as administrator! Thanks - I would not have got around to testing Olof's work without your GUI due to the .NET requirements.
to both of you!
Regards,
Misty
Posted 02 October 2013 - 10:35 PM
@olof
This is yet another fantastic tool to add to my collection - ImDisk has been my favourite virtual drive tool since you made it available on the forum. It looks like I'll also be using this in the future too!
@erwan.l
Tested in Windows 7 (x86) - appears to be working fine - once I remembered to run as administrator! Thanks - I would not have got around to testing Olof's work without your GUI due to the .NET requirements.
to both of you!
Posted 03 October 2013 - 06:42 AM
The Arsenal driver and GUI are working OK in XP.
Thanks Olof and Erwan
Mini XP VHD can be mounted and is visible as drive Q: in Disk Management
ISO can be mounted, but is not recognised.
Disk Management thinks it is a harddisk and it wants to Initialize the MBR
May be better not to allow ISO as selection.
Might it be possible to use ISO in future .... ?
Posted 03 October 2013 - 07:17 AM
@wimb, starting with windows8, as it is natively supported, i could easily mount the iso but it would be best for sure if this feature could come from the Arsenal driver itself.
Probably a silly idea but could playing with the offset (i hardcoded 0 as default) could help there?
Probably not as mounting an iso is probably more complex than just mounting an imafile file at a different offset...
Posted 03 October 2013 - 07:19 AM
I look forward to this, this is really good and are subsequently reactos.org also fully the possibilities also from Win7, mounting from emulated harddisks or maybe also encryptet harddisks ..
and this in Reactos also ... yea
best regards
Blacky
Posted 03 October 2013 - 07:23 AM
Probably a silly idea but could playing with the offset (i hardcoded 0 as default) could help there?
Probably not as mounting an iso is probably more complex than just mounting an imafile file at a different offset...
Posted 03 October 2013 - 08:33 AM
It will be very nice if ISO support can be added to the Arsenal driver
It would also be interesting if we can use the Arsenal driver to make RAMDISK
Would that be possible as well ?
Posted 03 October 2013 - 08:54 AM
And if you add an iscsi initiator feature next to that then we have the perfect tool
Helas my c++ and kernel mode skills are very low so I would not be able to help there.
Posted 03 October 2013 - 09:00 AM
It would also be interesting if we can use the Arsenal driver to make RAMDISK
Would that be possible as well ?
Memory disk should already be possible in the same way as for ImDisk. Just specify a size and no filename to create a virtual memory backed virtual disk. To create a virtual disk backed by physical RAM in all cases, specify a size and use \\.\awealloc as filename. (The latter needs awealloc driver to be installed and loaded, of course. For example, install ImDisk.)
And if you add an iscsi initiator feature next to that then we have the perfect tool
iSCSI is probably more a matter of communication translation. Both this driver and iSCSI are based on SCSI commands, which is pretty much a widely accepted standard. So I guess that is probably a lot easier than for example to implement CD/DVD support.
Posted 03 October 2013 - 09:04 AM
Memory disk should already be possible in the same way as for ImDisk. Just specify a size and no filename to create a virtual memory backed virtual disk. To create a virtual disk backed by physical RAM in all cases, specify a size and use \\.\awealloc as filename. (The latter needs awealloc driver to be installed and loaded, of course. For example, install ImDisk.)
iSCSI is probably more a matter of communication translation. Both this driver and iSCSI are based on SCSI commands, which is pretty much a widely accepted standard. So I guess that is probably a lot easier than for example to implement CD/DVD support.
I'll play with ramdisk this evening at home to see if I can add support for this in my GUI.
Sounds good around iscsi : means we may see that coming at some point.
Posted 03 October 2013 - 09:15 AM
@Olof - Interesting that RAMDISK will be possible already.
@Erwan - Nice that you are going to add RAMDISK support to your GUI
After Install of SetupVirtualCloneDrive5440.exe then Mounting of ISO is possible.
ISO Drive Q: is visible in Disk Management.
So it might be possible to add ISO support to the Arsenal driver in a similar way .... ?
Posted 03 October 2013 - 09:37 AM
@Olof - Interesting that RAMDISK will be possible already.
@Erwan - Nice that you are going to add RAMDISK support to your GUI
After Install of SetupVirtualCloneDrive5440.exe then Mounting of ISO is possible.
ISO Drive Q: is visible in Disk Management.
So it might be possible to add ISO support to the Arsenal driver in a similar way .... ?
Yes, should be possible, of course. Someone just need to do some work in the driver. That is, implement device type READ_ONLY_DIRECT_ACCESS_DEVICE along with handling CD/DVD specific requests such as SCSIOP_READ_TOC and SCSIOP_GET_CONFIGURATION. And hopefully do that without breaking compatibility with the rather annoyingly touchy XP version...
Posted 03 October 2013 - 05:18 PM
Thanks for new version
RAMDISK can be made, but is not yet initialised.
Manually I created NTFS formatted partition and that is working OK
RAMDISK is visible in Disk Management as Drive R:
It would be nice if the created RAMDISK would have already NTFS formatted partition.
Posted 03 October 2013 - 05:25 PM
Good idea indeed.
Now i need to find a way to link my devicenumber with a physical drive to initialise it and eventually format it.
May be Olof can put me on the right path.
Will start looking.
Erwan
Posted 03 October 2013 - 05:40 PM
Good idea indeed.
Now i need to find a way to link my devicenumber with a physical disk to initialise it and eventually format it.
May be Olof can put me on the right path.
Will start looking.
Sorry, but I don't know of any more practical way than trying to open each \\.\PhysicalDriveN device and send IOCTL_SCSI_GET_ADDRESS to each of them and pick the first one that matches.
But there should probably be better ways to do this. For example I would guess that it would be possible to use setupapi in some way to follow the plug-and-play device tree from the adapter down to the disk objects. But I have never dived into that.
Posted 03 October 2013 - 06:24 PM
Sorry, but I don't know of any more practical way than trying to open each \\.\PhysicalDriveN device and send IOCTL_SCSI_GET_ADDRESS to each of them and pick the first one that matches.
But there should probably be better ways to do this. For example I would guess that it would be possible to use setupapi in some way to follow the plug-and-play device tree from the adapter down to the disk objects. But I have never dived into that.
Will try that.
Or use IOCTL_STORAGE_QUERY_PROPERTY and look for a ProductID = "Virtual" and BusType="Fibre"
Posted 04 October 2013 - 07:53 AM
Can you add
Auto download or extract devcon.exe and put it where it needs to be so the driver can be installed.
I forgot what scripts do that. I think ive seen some scripts auto do it when building pe's.
Some icons you might want to use.
http://www.softicons...ch=RAM&x=30&y=8
http://www.softicons.../ram-drive-icon
http://www.softicons.../drive-ram-icon
http://www.bijusubha...delete-icon-set
http://www.softicons...ch=plus&x=0&y=0
Posted 04 October 2013 - 03:18 PM
Hi TheHive,
Thanks for the icons !
The one I used definitely made my eyes tear blood... I am an awful designer when it comes to front end
I also may need a more meaningfull name ('mount' is a bit generic...).
About the driver install, I believe we should definitely propose 1/propose a nsi script or 2/integrate drvinst.dll as pointed out by Wonko.
I might give a try to drvinst.dll (low prio thus) but will not have time to dive in the nsi script.
Regards,
Erwan
Posted 04 October 2013 - 05:35 PM
version 0.6
As requested by Wimb, after a memory drive is created, the app will propose to initialise the drive (i.e createdisk+createpartition).
For this I reused functions from my app CloneDisk.
After this, windows will propose to format it.
The interface also displays the mathing physicaldrive using IOCTL_SCSI_GET_ADDRESS as advised by Olof.
And I used TheHive program icon.
Need to look at (or rather make my choice) between buttons hinted by TheHive.
/Erwan
Posted 04 October 2013 - 06:50 PM
GREAT DUDE...
You always come up up with great things...
...
I dont need to say that imDisk is a great tool... everybody knows that...
I hope this one go the same way...
...
Just when I was switching to AOE... Well... let's gave again some time to iSCSI...
Thanx... you're the Man... ;-)
Posted 04 October 2013 - 07:11 PM
GREAT DUDE...
You always come up up with great things...
...
I dont need to say that imDisk is a great tool... everybody knows that...
I hope this one go the same way...
...
Just when I was switching to AOE... Well... let's gave again some time to iSCSI...
Thanx... you're the Man... ;-)
All credits goes to Olof there.
I am merely offering a portable GUI
An iSCSI initiator (and why not AOE) initiator would be super cool indeed.
Thus now that I have some code to pilot a driver, I am wondering If I could not reuse it with the AOE driver (from winaoe or winvblock).
Maybe disgressing there...
/Erwan
Posted 04 October 2013 - 07:59 PM
Names
GIM - Great Image Mounter
IM - Image Mounter
AIM - An Image Mounter
AIMG - Arsenal Image Mounter Gui
Gmail - Greatly Mounts Alot Images Lol!
IMount - Based on ImDisk
IMount.ico 84.33KB
1012 downloads
0 members, 0 guests, 0 anonymous users