Jump to content











Photo
- - - - -

DiskMgr


  • Please log in to reply
7 replies to this topic

#1 erwan.l

erwan.l

    Gold Member

  • Developer
  • 1975 posts
  • Location:Nantes - France
  •  
    France

Posted 01 April 2017 - 05:15 PM

index.php?app=downloads&module=display&s

File Name: DiskMgr
File Submitter: erwan.l
File Submitted: 01 Apr 2017
File Updated: 01 Apr 2017
File Category: Tools

DiskMgr has been developed primarily for use in a Windows Forensic Environment (WinFE) to provide a user friendly method of changing the following DISK attributes -

  • Offline
  • Online
  • Read-Only
  • Read-Write

DiskMgr is similar in use to Colin Ramsden's "Write Protect" application (see here). DiskMgr is available in native Windows 32-bit and 64-bit versions.

Click here to download this file


  • Blackcrack and genetix like this

#2 misty

misty

    Silver Member

  • Developer
  • 703 posts
  •  
    United Kingdom

Posted 01 April 2017 - 05:21 PM

Well done on another addition to your growing portfolio - another great addition.

:worship:

Misty
  • Blackcrack likes this

#3 genetix

genetix

    Frequent Member

  • Advanced user
  • 132 posts
  •  
    Finland

Posted 01 April 2017 - 11:57 PM

Heh, perhaps I should of turn to you before I used 3 hours to write my hardware.dll library (query to WMI) just last week.

 

Nice work there.



#4 erwan.l

erwan.l

    Gold Member

  • Developer
  • 1975 posts
  • Location:Nantes - France
  •  
    France

Posted 02 April 2017 - 12:24 PM

Heh, perhaps I should of turn to you before I used 3 hours to write my hardware.dll library (query to WMI) just last week.

 

Nice work there.

 

Hi Genetix,

 

Let me know if you need help.

WMI is a nice feature but it is not always available under winpe, is not always "stable", and sometimes is depending on admin persmissions.

Hence, I usually try to stick to native windows api (found in kernel32.dll) which greatly mitigate the above issues.

 

Regards,

Erwan


  • genetix likes this

#5 Blackcrack

Blackcrack

    Frequent Member

  • Advanced user
  • 321 posts
  •  
    Germany

Posted 04 April 2017 - 03:35 AM

Hi,

 

i have see you PartManager, VolumeManager and now this there..

sorry for the question,

so why not all in one, an

 

PaVoDi-Manager ?

 

One Fonted with 3 Funtions or manager..

 

short Pa-Vo-Di  have also an sound in the name who sounded good so far

 

Pa..Vo..Di...

 

Manager ..

 

and it is all in one fonded and it don't need to open every single Gui's

"one  partition.. klick.. close.. one for Volumes.. klick and close

and one for the Diskmanagement.. klick and close.. oh vorget the Volume to activate.. damn.. doubleclick.. managing.. and then close .. again.. gnh.. okey, now should i can working further .."

 

no,

"one Gui, one klick and some can manageing disk, or volumes or Partitions..

and then if all done .. close .."

 

if this idea/suggestion bad, so forget it and sorry for that :)

 

best regards

Blacky



#6 erwan.l

erwan.l

    Gold Member

  • Developer
  • 1975 posts
  • Location:Nantes - France
  •  
    France

Posted 04 April 2017 - 07:31 AM

Actually, the "one in all" is CloneDisk.

 

These 3 new softwares (partmgr, volumemgr, diskmgr) are all coming from CloneDisk.

 

Idea there is too make quick, easy & portable "one form" utilities mainly meant at WinPE (but not only).


  • Blackcrack likes this

#7 genetix

genetix

    Frequent Member

  • Advanced user
  • 132 posts
  •  
    Finland

Posted 04 April 2017 - 09:52 AM

Hi Genetix,

 

Let me know if you need help.

WMI is a nice feature but it is not always available under winpe, is not always "stable", and sometimes is depending on admin persmissions.

Hence, I usually try to stick to native windows api (found in kernel32.dll) which greatly mitigate the above issues.

 

Regards,

Erwan

 

Then again I don't see why not include powershell, wmi even .NetFX for WinPE.

 

Usually using those at every build I make from my apps. As for digging from kernel32.dll or well internals I consider that to be more dangerous route than query wmi for information. Problem with wmi is overhead while using timers to query information fast where kernel32.dll would be way better to be used over general hardware information.

 

Atm, I am stuck actually with VolumeID and boot sector low level writing and C#.NET as it requires byte or uint as hex and well at C#.NET it's just not gonna happen converting string to uint.



#8 erwan.l

erwan.l

    Gold Member

  • Developer
  • 1975 posts
  • Location:Nantes - France
  •  
    France

Posted 04 April 2017 - 10:07 AM

Then again I don't see why not include powershell, wmi even .NetFX for WinPE.

 

Adding these to WinPE, although possible, introduces more complexity and will make your WinPE fat.

 

I personally prefer to stick to windows API which means my apps have little or no dependencies and will work on most if not all windows systems (back to XP).

But this is a pure personal choice.

 

And if you finally decide to call windows native API from .Net, then you will struggle with types.

Calling windows api from .Net is a bit losing the advantage of this framework (which is about hiding complexity).






0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users