[Bug 7065] Get SecuROM copy-protection working

[wine-bugs at winehq.org]

http://bugs.winehq.org/show_bug.cgi?id=7065





--- Comment #56 from Anastasius Focht <focht at gmx.net>  2007-11-30 07:07:25 ---
Hello,

Louis won't get any patch with empty or fake "MountedDevices" registry data
into wine source tree.
This data has to be generated and managed by wine, which requires some work.

For an overview, how "MountedDevices" data is derived you might read this:
http://www.goodells.net/multiboot/partsigs.htm ("How does Windows XP remember
drive letters?" part)

Although it touches only the surface it should give the general idea.

This data is managed by mount manager which is a windows kernel module,
communicating with user mode API thru IOCTL_MOUNTDEV_* ioctls.
If an application/API needs the relation between symbolic link name, unique ID
for the volume and the nonpersistent device name it asks the mount manager
(IOCTL_MOUNTMGR_QUERY_POINTS).
With that data, a mapping between driver letters and device name through unique
id can be established.

For preliminary implementation, wine just needs to generate unique IDs and
manage corresponding drive letters [in it's own way].
This stuff should of course take any dynamic configuration changes into
account, e.g. make sure all private data that keeps track of the assigned drive
letters is in sync with MountedDevices registry data.

For the time being, just create an empty "MountedDevices" key [as outlined
several times] and be happy ;-)

Regards


-- 
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.