Jump to content











Photo
- - - - -

VMLite VBoot - Boot any Windows from VHD/VMDK/VDI/Raw


  • Please log in to reply
104 replies to this topic

#101 reboot.pro-er

reboot.pro-er
  • Members
  • 7 posts
  •  
    Botswana

Posted 3 weeks ago

thx for answer Wonko.

1) u mean delete all dosdevice included C: too?

2) delete all volume-strings?

so it means delete all?

3) first 4 strings its truecypt's records (if open it in editor there will be wrote trucrypt) is this necessary? i guess no


Edited by reboot.pro-er, 3 weeks ago.


#102 reboot.pro-er

reboot.pro-er
  • Members
  • 7 posts
  •  
    Botswana

Posted 3 weeks ago

tried both ways what u suggested : delete binary data from Volume-hives and second one - delete all dosdevices. Wont helped. is there any way to permanently connected volume with letter?

P.S. i feel need try recovery from distrib



#103 Wonko the Sane

Wonko the Sane

    The Finder

  • Advanced user
  • 13745 posts
  • Location:The Outside of the Asylum (gate is closed)
  •  
    Italy

Posted 3 weeks ago

I am still not sure to understand the actual issue.

Can you try to describe better what happened (and what happens now)?

 

When the contents of the MountedDevices is deleted, the OS attempts to re-enumerate all devices, so you should now have all the physical devices volumes entries recreated new.

Anything that is not "physical" (such as a filedisk, ramdisk or similar, and this should include the Truecrypt volumes) won't be there anymore until you re-run the program/driver and thus re-mount "manually" the volume.

 

:duff:

Wonko



#104 reboot.pro-er

reboot.pro-er
  • Members
  • 7 posts
  •  
    Botswana

Posted 3 weeks ago

"should now have all the physical devices volumes entries recreated new"

ok any idea how to do it manually? i m in doubt that system can do it, probably cause there no ability during the system cutted



#105 Wonko the Sane

Wonko the Sane

    The Finder

  • Advanced user
  • 13745 posts
  • Location:The Outside of the Asylum (gate is closed)
  •  
    Italy

Posted 3 weeks ago

No simple way that I know of.

 

Creating a drive letter (for a hard disk volume) is simple enough.

 

They are the Disk Signature and the offset (in bytes) to the beginning of the volume, see:
https://web.archive....t=0#entry130963

 

As well creating the {GUID] (the actual values in the {GUID} entry are the same.

 

Now creating the actual {GUID} might be a little tricky, the automatically generated one is a v1 "semi-random" GUID per RFC but it has to be seen if there is a validation of some kind or if it is just a "semi-random" string .

 

The UUID tool mentioned here:

https://www.forensic...586892/#6586892

should be able to produce a valid {GUID}:

http://soft.rubypdf....idgen-ossp-uuid

 

Please understand that the above is just "generic" a booting system should create those automatically, if it doesn't then there might be other and different problems outside and before the drive letter assignment, agan idf you don't somehow manage to repoort more exactlythe symptoms, it is difficul ot impossible to provide a diagnosis (let alone a cure).

 

:duff:

Wonko






0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users