Simplify the hackssign application usage.
You don't need anymore to specify which VM type you use. The client will attempt to discover it by looking at available shared folders providers.
If it recognizes one, it will perform the assignation.
No Guest Additions/Tools installed will make the tool refuse to assign a drive letter (obviously).
So basically, you just need to issue some: hackssign assign z ReactOS (for example)
svn path=/trunk/; revision=68802
Stack hacks!
Let's introduce hackssign. This application (and its associated driver) are here to allow
users to assign drive letter to their VMware/VBox shared folders.
It relies on two components: a client to communicate the instructions and a driver to execute such instructions.
Do not execute this application nor its driver outside ReactOS. There are barely no security checks nor sanety checks.
You could do substantial damages.
So, let's go back to shared folders state in ReactOS nowadays...
VMware
------
Configure your shared folders
Install VMware Tools
Reboot
From here, you can access your share from cmd or explorer with UNC path (for instance: \\vmware-host\Shared Folders\ReactOS)
Go to C:\ReactOS\bin (or whatever, depending on your setup)
Execute hackssign assign z ReactOS vmware (for instance)
z is the letter you want to give, and ReactOS is the name of your share (you gave it in VMware configuration)
You're done, you can access your share with the Z drive letter
VirtualBox
----------
Configure your shared folders
Install VBox Guest Additions
Reboot
Go to C:\ReactOS\bin (or whatever, depending on your setup)
Execute rosvboxmgmt start
From here, you can access your share from cmd or explorer with UNC path (for instance: \\vboxsvr\ReactOS)
Execute hackssign assign z ReactOS virtualbox (for instance)
z is the letter you want to give, and ReactOS is the name of your share (you gave it in VMware configuration)
You're done, you can access your share with the Z drive letter
Note that you can delete an assignement by performing a hackssign delete z (or whatever drive you want to remove).
In such case, the share remains available with its UNC path.
svn path=/trunk/; revision=68794
Add the "rosvboxmgmt" tool.
It's purpose is to allow to interact with the VBoxSF driver as we don't have working MPR yet.
In order to have UNC path available, all you need to do so far is rosvboxmgmt start. All the rest isn't mandatory.
svn path=/trunk/; revision=68778
Time to free some Sysinternals tool: ntfsinfo.
To make it short, this tool dumps various information about a NTFS volume and its reserved meta-data files
Our version comes with three advantages compared to the Russinovich's tool:
- It's FLOSS
- It works properly on NT5+ (developed with W2K3 & W7) whereas R's cannot display meta-data files information
- It will open a volume by default if none provided
One issue so far: it doesn't work properly on ReactOS!
CORE-8725
svn path=/trunk/; revision=68326
- Fix some newlines,
- Fireball == Aleksey, not Aleasky :P (ahh, GreatLord, we miss you ^^),
- Fix rosddt (ROS Device Detection Tool) readme file (convert into UTF-8 without BOM).
svn path=/trunk/; revision=63280
Move mode from rosapps to reactos trunk.
CORE-8001 #resolve #comment Moved from rosapps to reactos trunk in revision 62521.
svn path=/trunk/; revision=62521
- Remove the "kernel32" library reference in all .rbuild files of user-mode modules, because this one is already added by "mingw_common". Also fix the indentation in some files.
svn path=/trunk/; revision=44368
- Fix compilation of a number of modules.
- Delete outdated fmifs.h, the one from ReactOS includes should be used instead.
- Move more libs to /lib directory.
svn path=/trunk/; revision=34627
