os/boardsupport/emulator/emulatorbsp/win_drive/win_drive.ini
changeset 0 bde4ae8d615e
     1.1 --- /dev/null	Thu Jan 01 00:00:00 1970 +0000
     1.2 +++ b/os/boardsupport/emulator/emulatorbsp/win_drive/win_drive.ini	Fri Jun 15 03:10:57 2012 +0200
     1.3 @@ -0,0 +1,114 @@
     1.4 +;==========================================================================
     1.5 +;   This is the configuration file for the "win_drive.fxt" filesystem extension for the emulator.
     1.6 +;   See \emulator\wins\win_drive.
     1.7 +;
     1.8 +;   This file shall reside in \epoc32\data\ directory.
     1.9 +;
    1.10 +;==========================================================================
    1.11 +
    1.12 +[Drive_T]
    1.13 +
    1.14 +
    1.15 +[Drive_X]
    1.16 +;--------------------------------------------------------------------------
    1.17 +; The name of the Windows device that can be used by win_drive.fxt extension as the media.
    1.18 +; The device can be "physical", for example HDD partition or removable drive or "image file", when 
    1.19 +; the specifie file will be used as EPOC drive.
    1.20 +
    1.21 +; 1. "Physical" media:
    1.22 +;   This key value shall look like: DeviceName=\\.\F:
    1.23 +;   'F:' in this case is the Windows drive letter that will be used. This drive can be removable or 
    1.24 +;   non-removable. 
    1.25 +;   preferable settings:
    1.26 +;     * BytesPerSector=0 or not defined, it is unlikely that Windows drives will use something different
    1.27 +;                        from 512 bytes; '0' means "use windows volume partition information"
    1.28 +;
    1.29 +;     * MediaSizeInSectors=0 or not defined if you wish to use existing partition information for this windows volume.
    1.30 +;       Or it can be the number of sectors, less than the real number of sectors on this windows drive; in this
    1.31 +;       case only a part of the drive will be used. It can't be more than maximal number of sectors on the 
    1.32 +;       specified windows drive - it's impossible to increase the partition size.
    1.33 +;
    1.34 +; 2."Image file" media
    1.35 +;   This key value shall look like: DeviceName=\epoc32\data\media\my_image_file.bin
    1.36 +;   preferable settings:
    1.37 +;     * BytesPerSector=0 or not defined for 512 bps; 1024, 2048 and 4096 bps are also valid, 
    1.38 +;       but if they are supported or not, depends on the appropriate .fsy for this epoc drive.
    1.39 +;
    1.40 +;     * MediaSizeInSectors=0 or not defined only for the case, when the image file already exists.
    1.41 +;       In this case EPOC drive geometry will be calculated depending on the image file size and BytesPerSector value
    1.42 +;       If 'MediaSizeInSectors' value is specified, the image file will be created/expanded/shunk to correspond
    1.43 +;       to this size; its size in bytes will be MediaSizeInSectors*BytesPerSector
    1.44 +;
    1.45 +; Default value: there is no devault value, the device name must be correctly specified
    1.46 +
    1.47 +;DeviceName=\\.\F:
    1.48 +;DeviceName=\\.\Z:
    1.49 +DeviceName=\epoc32\data\media\MMCCRD0A1.BIN
    1.50 +
    1.51 +;--------------------------------------------------------------------------
    1.52 +; bytes per sector. Valid values are: 0, 512, 1024, 2048, 4096.
    1.53 +; '0' means 'Auto' if the media is a physical volume, its partition info will be used in this case,
    1.54 +;   if the media is the image file, 512 bytes per sector will be used.
    1.55 +; Actually, using anything rather than 512 is not recommended.
    1.56 +;
    1.57 +; Default value:0
    1.58 +
    1.59 +;BytesPerSector=0
    1.60 +
    1.61 +;--------------------------------------------------------------------------
    1.62 +; This parameter specifies the EPOC media size in sectors. 
    1.63 +;* Value '0' means "Auto". 
    1.64 +;   In this case if the 'DeviceName' parameter specifies the windows physical volume,
    1.65 +;   its partition information will be used. If the 'DeviceName' parameter specifies the image file, this file
    1.66 +;   must exist and its total length will be used to calculate media size in sectors.
    1.67 +;
    1.68 +;* If the value of this key is > 0
    1.69 +;    For physical media it can't be more than maximal number of the sectors on the windows volume;
    1.70 +;    if less, only the beginning of the partition will be used.
    1.71 +;    If "image file" media is used, this image file will be opened/created and its size set to MediaSizeInSectors*BytesPerSector
    1.72 +;
    1.73 +; Default value:0
    1.74 +
    1.75 +MediaSizeInSectors=40960
    1.76 +
    1.77 +
    1.78 +;--------------------------------------------------------------------------
    1.79 +; If this parameter !=0, this EPOC drive ([Drive_*]) will be visible as Read-Only  
    1.80 +;
    1.81 +; Default value:0
    1.82 +;
    1.83 +;ReadOnly = 1;
    1.84 +
    1.85 +;--------------------------------------------------------------------------
    1.86 +; You can override media type (TMediaType) for this particular drive.
    1.87 +;
    1.88 +; Default value:0, which means that it won't be overriden by this extension and taken from the original media driver.
    1.89 +;
    1.90 +;MediaTypeOverride=3 ;EMediaHardDisk
    1.91 +
    1.92 +;--------------------------------------------------------------------------
    1.93 +; You can override media attributes (TLocalDriveCaps::iMediaAtt) for this particular drive by specify 'AND' and 'OR'. 
    1.94 +; masks that can be applied to the TLocalDriveCaps::iMediaAtt field returned by the original media driver.  
    1.95 +; These values mut be in hex!
    1.96 +;
    1.97 +; Default value for "AND" mask :0xFFFFFFFF
    1.98 +; Default value for "OR"  mask :0x0
    1.99 +;MediaAttOverride_AND=0xFFFFFFFD ; will clear KMediaAttFormattable flag
   1.100 +;MediaAttOverride_OR=0x010 ; will set KMediaAttLockable flag 
   1.101 +
   1.102 +
   1.103 +
   1.104 +;--------------------------------------------------------------------------
   1.105 +; You can override drive attributes (TLocalDriveCaps::iDriveAtt) for this particular drive by specify 'AND' and 'OR'. 
   1.106 +; masks that can be applied to the TLocalDriveCaps::iDriveAtt field returned by the original media driver.  
   1.107 +; These values mut be in hex!
   1.108 +;
   1.109 +; Default value for "AND" mask :0xFFFFFFFF
   1.110 +; Default value for "OR"  mask :0x0
   1.111 +;DriveAttOverride_AND=
   1.112 +;DriveAttOverride_OR=
   1.113 +
   1.114 +
   1.115 +
   1.116 +
   1.117 +