Print

[BenJeremy]

QUOTE (jackmeph @ Feb 27 2003, 07:55 PM)

QUOTE QUOTE BenJeremy >>>From the programmer's perspective, the system boots up applications with a D:, T:, U:, and the X:, Y; Z: drives. The last three are utility drives. These are symbolically linked; D: is wherever the program sits, even if it's in a subdirectory of what most users think of as the "E:" drive.  In fact, C:, E:, and F: have to be symbolically linked by the application itself in order to be seen.  Of course, the accuracy of the above info is not 100% because I'm on my way out of the door at work, not at home with all my Xbox info. End Quote How can the hombrew dynamicly link the c:. f: and D:(Real dvd)?? Any help would be appreciated. JackMeph

#define CdRom "\\Device\\Cdrom0"
#define CDrive "\\Device\\Harddisk0\\Partition2"
#define EDrive "\\Device\\Harddisk0\\Partition1"
#define FDrive "\\Device\\Harddisk0\\Partition6"
#define SDrive "\\Device\\Harddisk0\\Partition1\\TDATA"
#define VDrive "\\Device\\Harddisk0\\Partition1\\UDATA"

There's a function in my code:

DWORD RebuildSymbolicLink( LPCTSTR szSymbolicDrive, LPCTSTR szNewDeviceLocation, bool bDelete = false );


that does everything needed. Feel free to steal it. It should be in any source code for MXM in the 0.9 series. Look for it in "the usual places"


If need be, you can access the drive using the above as the path:

\Device\Harddisk0\Partition6\Apps\SomeDirectory\SomeFile.zzz