DFSee version 16.1 22-05-2019 (c) 1994-2019: Jan van Wijk =========================[ www.dfsee.com ]========================== _______________________________________________________________________________ C O N T E N T S: _______________________________________________________________________________ Command reference = overview of FDISK specific commands Detailed description = description of every command Note: All generic commands can be found in DFSCMDS.TXT, for example: PART, ALLOC, CHECK, CLONE, IMAGE, RESIZE, RECOVER, SAVETO, SCAN, WIPE _______________________________________________________________________________ #010 C O M M A N D R E F E R E N C E: _______________________________________________________________________________ FDISK specific commands Active filesystem : FDISK / IBM-BMGR, specific commands are: APMAP [-v] = Display Apple-Part-MAP in first disk track ATTACH [opt] Fname | size [H S] = Attach a partionable medium (virtual / image) BMFIX [disk ] = Fix IBM BMGR bootsector W2K & CHS issues BMP [disk | -d:disknr ] = Show BMGR primary names sector for a disk CLEANUP [disk|.|* ] = Cleanup partitiontables, fix several errors CR [parameters][options] = Create a new partition, use 'CR' for usage DELETE [pid] [disk][options] = Delete one or ALL partitions from disk(s) DETACH disk | * | -all = Detach removable medium (virtual / image) DFSIBMGR disk [imagefilename] = Create new IBM BootManager image for 'create' DISK [disk] [-r] = Select disk, show MBR; = next EBR DISKLIST = Show compact list if all disks, including size FAT2OS pid [disk [boot-OS]] = Set FAT-BR boot code to OS2|NT|IBMDOS|MSDOS FIXCHS disk|.|* [-c:0|1|2] = Fix CHS values to match LBA/current geometry FIXEXT disk|.|* [to [from]] = Fix ext-partition types to standard value GENPART disk|.|* [fn] [opts] = Generate DFSee partitioning script for disk(s) GPT [ disk|.|* ] [-fix] = Display or fixup GPT partitioning informtion GPT pid -name:NewName = Set a new name for an existing GPT partition GPT2MBR [ disk|.] [options] = Convert a GPT-style disk to an MBR-style LVM [pid] [options] = Update name, letter and BM-menu for partition LVMCLEAN [disk|.|*] [-a] = Clean obsolete LVM DLAT sectors in MBR track LVMSHOW [pid | *] = Show related LVM-info for 1 or all partitions LVMREDO disk|.|* [-C] = Refresh LVM info sectors (DLAT) for disk(s) MBR2GPT [ disk|.] = Convert (or recover) an MBR-style disk to GPT NEWMBR [disk|.|*] [-c] = Refresh MBR boot code, [-clean] = delete all NTSIGN [disk [signature]] = Set NT-signature value (32 bits) in MBR PLIST p|f|e|m|b|w|l [d[r]] = List: part|free|ebr|mbr|boot|walk|lvm [opt] PCLEAR disk [P][Lvm[S]][Br] = Clear info in P-tables, LVM and/or Boot record PSAVE disk|.|* Fn [descr] = Save Partition table and LVM info in a file PRESTORE disk|.|* Fn [types] = Write info from file into P-tables and LVM PT [pid|drive|*] = Display partitioning sectors for partition(s) SETACCESS pid [hide|vis|multi] = Make partition 'pid' accessible or hidden SETBOOT opt[:options] = BootManager setup and reboot => 'setboot ?' SETLET pid letter | - [-n] = Set driveletter for DFSee; [-n] = no sync (NT) SETNAME pid [BM-name] = Set or reset (non-LVM) BMGR name for partition SETTYPE pid disk new [old] = Change partition type from old to new value STARTABLE pid [multi | clear] = Make partition 'pid' startable (ACTIVE) TYPE [type | first last] = Show system type description (for 00..ff) VCU disk | . | * -d[:nr] = Clear existing LVM-info, create new defaults VSTATUS = Show R/W and usage status of virtual disks WALK [disk | .] [-r] = Select disk, show the MBR, walk EBR chain For an up-to-date list of commands, use the '?' command FDISK specific sector types (see ??? command) 'A' = MAC DDM, drive description 'a' = MAC DPM, partition map, Apple 'l' = LVM disk and volume info 's' = LVM signature sector 'd' = LVM DriveLink sector 'D' = LVM DriveLink table 'f' = LVM BadBlockRelocation sector 'F' = LVM BadBlockRelocation table 'p' = VRAID phys device 'v' = VRAID devicetype1 'V' = VRAID devicetype2 'X' = Unidentified data _______________________________________________________________________________ D E T A I L E D D E S C R I P T I O N: _______________________________________________________________________________ #100 APMAP [-v] = Display Apple-Part-MAP in first disk track Purpose: Display any Apple Partition MAP records present in first track Options: -v = Verbose, multiple lines per partitions found Output: Prompting, progress and confirmation information. Remarks: This displays the CLASSICAL Apple partition map as used by older MAC's or MAC compatible removable media as well as some other hardware devices like the 'Tivo' media player. _______________________________________________________________________________ #260 ATTACH command ATTACH [opt] Fname | size [H S] = Attach a partionable medium (virtual / image) Purpose: Attach a new partionable medium (virtual, image, physical) Options: -o- Do NOT open the newly attached disk disk automatically -p:number Attach a physical disk by number (DOS, WIN, OS/2) -p:device Attach a physical disk by device name (Linux) -r:ImName Attach a RAW imagefile, like an SVISTA .HDD container -v Create and Attach a VIRTUAL disk, this is the default Parameters: Fname = Virtual with size and geometry as in the *.PD* file specified, created with an explicit PSAVE command, or with the generic DFSDISK procedure. The file will be automatically restored on the newly created virtual disk using a PRESTORE. This leads to a virtual disk with exactly the same partitions as the original disk had. If a *.SN* file with exported list sectors also exists, that will be imported as well. This is a very fast and convenient way to test with disk information from the DFSDISK script. size[,[d|x]m|g|c|s] Specific size value, hex or decimal. in MiB, GiB, Cylinders or Sectors. Default: decimal Megabytes H S = Heads & Sectors to use with specified size, for creation and mounting of Virtual disks only When no options or parameters are specified, or just the '-v' option is is used, an EMPTY virtual disk will be created and attached with the same size and geometry as the currently open disk (if any). Output: Attach details for the new disk, and a default partition view for that same disk. Example: attach -v 250,g 255 56 This create a virtual disk of 250 GB, with a disk geometry using 255 heads and 56 sectors per track. Remarks: A virtual disk created will be empty at start (zeroes), unless it is initialized using a PDx file. Only sectors written to will actually be created in memory, and this might be limited by the available memory. By default the attached disk is opened (made the current object) This will allow direct and easy use from scripts, without knowing the actual assigned disk number. A virtual disk is very useful when experimenting. An existing partition scheme can be copied by using PSAVE and PRESTORE. It is also used in DFSDISK analysis and script testing. Attaching RAW imagefiles is very useful to fix minor problems preventing booting such an image in a virtual machine. The deprecated 'VIRT' command is now a direct alias for ATTACH. _______________________________________________________________________________ #110 BMFIX command BMFIX [disk ] = Fix IBM BMGR bootsector W2K & CHS issues Purpose: Make IBM BootManager sectors survive a Win-2000 CHKDSK and fix inconsistent boot/datasector CHS values to match BMGR location Parameters: disk optional Nr of the disk containing IBM BootManager Options: -I13X = Require I13X capable MBR to boot beyond cyl 1024 -I13X- = Remove I13X requirement (this is the default) Output: Prompting, progress and confirmation information. Remarks: The method used is based on a C't article and uses the FAT bootsector field 'reserved sectors to 1st FAT' to protect the BMGR data area Some additional changes were inspired by Daniela Engert and avoid the nasty CHKDSK screen while booting W2K (ver 3.36) The CHS values that are embedded in the BMGR datasector are checked and corrected when needed. These will rarely cause problems but CAN trigger a bug in the IBM setboot program for incorrect values below cylinder 1024. This may lead to overwriting one sector of data at that (incorrect) location. The DFSee builtin setboot command, or external SETBOOT program (in eCS 1.2 and up) is not affected by this bug at all ... Finally it will deactivate the explicit 'I13X' check in the BMGR code that results in a dependency on the IBM MBR 'I13X' signature. After this deactivation, BMGR can be used with other MBR code like Linux GRUB as well. Note: To allow booting OS/2 with non-I13X MBR code, you should also perform a 'fixboot' on any bootable HPFS partitions that are beyond the 1024 cylinder limit. The MBR used MUST be able to start partitions beyond the 1024 cylinder limit, but does not need to set the 'I13X' signature normally required by OS/2 The standard Windows (XP) MBR does NOT work beyond 1024! To reactivate the I13X dependency use 'bmfix -I13X' Another (not DFSee related) thing you might do to avoid any conflicts is to hide your HPFS volumes from WIN2000. If you don't you will sometimes be prompted with the frightening: "Volume is not formatted, format it now?" If you reply with "YES" you just lost your HPFS partition! To hide a volume from normal WIN2000 programs like Explorer: Start Settings Control Panel Administration Tools Computer Management Disk Management Now select the HPFS partition from the list, based on drive-letter and/or partition size. Use right mouse button to get the context menu Change Driveletter and paths ... Now click the [remove] button This will only remove the DRIVE-LETTER association for that partition in WIN2000, the partition itself is not touched! The same can be done in Windows XP (and probably Vista :-) although the exact procedure may differ slightly ... _______________________________________________________________________________ #130 BMP command BMP [disk | -d:disknr ] = Show BMGR primary names sector for a disk Purpose: Show the IBM BootManager sector that has BM-names for primaries Parameters: disk optional Disk number with BMGR to show names for Options: -d[:disknr] Disk number with BMGR to show names for Output: Hexdump display of first part of that sector (if present) Remarks: This sector is an array of 4 lines for each physical disk, one for each possible primary partition. Each line has an active flag-byte, head+sector/cylinder,another flag which is set when on the BM-menu, and the name string When using an LVM-enabled BootManager, the startable primaries are represented here with a "--> LVM" string _______________________________________________________________________________ #140 CLEANUP command CLEANUP [disk] = Cleanup partitiontables, fix several errors Purpose: Clean up partitiontable flag values, making sure there is just ONE ACTIVE partition, clear non-standard flags and fix minor inconsistencies in partition chain, like removal of 'empty' extended containers and recalculation of the total size of each extended-container. Parameters: disk optional Disk to operate on, default is all disks Options: -c:[0|1|2|?] : CHS style: 1=PQMagic, 2=MS, default 0=IBM/DFSee Output: Progress information and confirmation messages Remarks: Inconsistencies can be caused by several operations, using DFSee, other FDISK versions, tools like Linux GRUB or Partition-Magic. Resizing and deleting with PQMagic can cause 'empty' extended containers. _______________________________________________________________________________ #150 CR command CR [parameters][options] = Create a new partition, use 'CR' for usage You can use positional parameters and/or position independent options. For a detailed description of all the positional parameters and the position independent options see further below, short description: parameters : pri|log|gpt [type [size [loc [pos [BMGR-name]]]]] -a:abs-pos : Position from start of disk (mcs-number like 1,c or 0x3e,s) -A:pid|letter : create AS another partition; using the same type and size -align- : Allow UNALIGNED partition start, and size. No alignment -attrib:'hex' : GPT style partition flags, in a 16 hex-digit STRING -b:BMGR-name : partition name for (IBM, non-LVM) Bootmanager menu -c:[0|1|2|?] : CHS dummy style: 1=PQmagic, 2=MS, default 0=IBM/DFSee -C (any type) : Clear bootsector with 0xF6 pattern (FDISK behaviour) -C (guard EE) : On GPT 0xEE create: Clear existing PTA (no recovery!) -d:disk-nr : location, use first fitting area on specified Disk -e:end-pos : Relative pos from end of freespace (mcs-number like 50,c) -F : Flag as bootable in partition-table status (active) -f:id : location, as Freespace id (1st column from 'part') -G:n : GAP value between table and bootsect, 1 .. tracksize -guid:'36-ch' : Explicit partition GUID value for a new GPT partition -i:i13-pos : Relative pos before Int-13 limit (mcs-number like 10,c) -I[:image] : Imagefile to be written to new partition -L : automatic 'lvm -V' on new partition -L:'lvm opts' : automatic 'lvm' using specified options -M : Allow multiple visible primaries (no automatic HIDE) -N : When an MBR is created, leave code-area/NT-sig empty -name:Pname : Partition name string for a GPT partition (max 36) -o : open the new partition after create -p, -l or -g : Make Primary, Logical or GPT part/guard. (mandatory) -r:rel-pos : Relative pos from start freespace (mcs-number like 99,c) -s:size : Size, will be rounded UP to next cylinder boundary -S:0|1|2|3 : prefered table entry for the partition, default 0 -t:number /sym: MBR partition Type, numeric HEX, decimal or a symbol -t:guidstr/sym: GPT partition Type, GUID-str without {}, or a symbol -x:e13-pos : Relative pos after Int-13 limit (mcs-number like 12,c) -X:0|1|2|3 : prefered MBR entry extended container, default 3 (last) -Y:0|1|2|3 : prefered EBR entry extended containers, default 1 (2nd) The mcs-number format is [0x]nnnn[,g|m|k|c|s] a HEX or decimal value, in GiB, MiB, KIb, Cylinders or Sectors. Default is decimal MiB. You can mix the old and new style syntax, as long as the 'old' type parameters are in the required fixed position as specified above and the 'pri|log|gpt' and 'type' are specified somehow. Examples: cr log hpfs 200 3 * OS2MAINT cr log hpfs 200 -d:3 -b:OS2MAINT cr log hpfs -s:200 -d:3 -b:OS2MAINT cr log -t:hpfs -s:200 -d:3 -b:OS2MAINT cr -log -t:hpfs -s:200 -d:3 -b:OS2MAINT cr -d:3 -b:OS2MAINT -t:hpfs -s:200 -logical cr log hpfs 50,c -a:10,c -d:3 -b:OS2MAINT All except the last are variants of the SAME cr command, the last one creates a partition with size and position as mcs-number in 'cylinders' Purpose: Create one new partition in an area that is now freespace Parameters pri|log|gpt mandatory Primary/Logical identifier; (old style) log | l Logical partition pri | p Primary partition gpt | g GPT guard primary type mandatory System-type for new partition; number Decimal value 0 .. 255 or Hex as 0x00 .. 0xff guid 16-byte UUID for GPT partition type symbolic A name from the predefined set of partition types, see the -t: option or SETTYPE for a list. Some symbolic names + HEX value for MBR-style partitiong: FAT = 01/04/06/0b/0c automatic FAT BMGR = 0a OS/2 Bootmanager FAT32 = 0b/0c 32-bit automatic FAT32 JFS = 35 Journaled FS (LVM) HPFS = 07 OS/2 native filesystem SWAP = 82 Linux SWAP partition NTFS = 07 Windows-NT filesystem EXT2 = 83 Linux EXT2 filesystem GUARD = ee GPT guard partition defined in the MBR for a GPT disk Some symbolic names + HEX value for GPT-style partitiong: EFI = ef / ef00 UEFI System partition BIOS = bb / bb00 BIOS Boot partition WIN, FAT, FAT32, EFAT, NTFS = 07 / 0700 Windows Basic Data REC = 27 / 2700 Windows Recovery SWAP = 82 / 8200 Linux Swap LIN, LINUX, EXT2, EXT3, EXT4 = 83 / 8300 Linux Data HOME = 8302 Linux Home ROOT32 = 8303 Linux Root x86-32 ROOT64 = 8304 Linux Root x86-64 SRV = 8306 Linux Server Data LUKS = 8309 Linux LUKS encrypted RAID = fd / fd00 Linux Raid APPLE = ab / ab00 Apple Boot HFS = af / af00 Apple MAC OSX HFS+ APFS = 73 / af73 Apple APFS Container Note that numeric values specified for MBR are interpreted as DECIMAL unless prefixed with '0x' and for GPT they are always HEXADECIMAL! size optional Desired size for the partition; * Use maximum size for the selected freespace-area number[,[d|x]m|c|s] Specific value, decimal or hex. Megabytes, Cylinders or Sectors. Default: decimal Megabytes loc optional Location to place new partition; * Use first 'matching' area @fsp-id Specific freespace area disk Use first matching area on the specified disk pos optional Position in loc-area; * Default position (at start) [+|-|@|{|}]number[,[d|x]m|c|s] Specific value, decimal or hex. Megabytes, Cylinders or Sectors. Default: decimal Megabytes Prefix modifiers are: + Relative to start of area - Relative to end of area @ Absolute from start of disk { Relative, before 1024-cyl limit } Relative, after 1024-cyl limit Note: The corresponding value with the prefix can be 0 or empty BMGR-name optional Add to the IBM BootManager menu using this name Options: -a:abs-pos : Absolute position from start of disk (mcs-number) (new style) -A:pid|let Create AS partition; using same type and size. This "CREATE AS" will use the specified partition primary/logical, type and size as a default. Other options can be added, and overrule any value set by the -A option. Example: "CR -A:2 -t:fat32" will create a partition just like the current 02 but with type FAT32. -align- Allow UNALIGNED partition start, and size. Any attempt to align the partition to cylinder of other defined boundaries is skipped, except where some alignment is required to make room for an EBR -attrib:'x': GPT style partition flags, in a 16 hex-digit STRING defining 64 flag bits for the new GPT partition. -b:BM-name : Partition name for (IBM, non-LVM) BootManager menu -C (normal) Clear bootsector with 0xF6 pattern (like FDISK) In combination with the -L option, this will also clear the LVM signature sector (BBR) to 0xF6. -C (guard) When creating a GPT guard partition (type 0xEE) an EMPTY GPT-partition-table-array is created, no recovery of any existing GPT information is done! -d:disk-nr : Location, use first fitting area on specified Disk -d or -d:0 : Location, currently open disk. (this is default) -d- : Use first fitting area on ANY disk. -e:end-pos : Relative pos from end of the disk (mcs-number) -f:id : Location, as Freespace id (1st column from 'part') -F : Set bootable flag in partition table (active) -G:n : GAP between the EBR and bootsector for a LOGICAL. A non-standard distance from partition-table to bootsector is sometimes seen on Linux (-G:1). Sector value, default is the tracksize (often 63) -i:i13-pos : Relative pos before the Int-13 limit (mcs-number) -I- : Do NOT install any image (like DFSIBMGR.IMG) here. -I[:image] : Imagefile to be written to new partition, this can be a RAW (.IMG) or compressed (.IMZ) image as used with the IMAGE and RESTORE commands. It is intended to initialize the new partition with existing data. When no name is specified, you will be prompted. -I13X Require an I13X capable MBR (from IBM or DFSee) to use bootmanager with partitions beyond cyl 1024. -l : Create a Logical partition -L Automatic 'lvm -V' on new partition -L:'lvmopts' Automatic 'lvm' using specified options In both cases LVM-information will be added for the new partition, either interactively or with defaults, or with the specified values. The 'lvmopts' are simply options that are valid for the LVM command, but combined in one string with either double or single quotes. -M : Allow multiple visible primaries (no auto HIDE) -o : Open the new partition after creation -p : Create a Primary partition -r:rel-pos : Relative position from start of area (mcs-number) -s:size : Size, will be rounded UP to next cylinder boundary except when specified in sectors Examples: -s:800 size of 800 MiB, rounded UP -s:30,c size of 30 cylinders, rounded UP -s:0x3fc0,s size of exactly 0x3fc0 sectors -S:0|1|2|3 : prefered partition-table entry (Slot), default 0 Used to exactly recreate a given layout, avoiding changes in partition numbering (BOOT.INI etc) -t:type : System Type, numeric, symbolic-name or (GPT) GUID The most used system-types for MBR style are: hex symbolic 0x01 FAT12 = FAT12 0x04 FAT16 = FAT16 < 32 MiB 0x05 EXT = Extended partition (chain) 0x06 FAT = FAT16 > 32 MiB 0x07 IFS = Installable File system 0x07 HPFS = IFS, HPFS (alias) 0x07 NTFS = IFS, NTFS (alias) 0x07 BJFS = IFS, Bootable JFS (eCS) (alias) 0x0a BMGR = IBM BootManager 0x0b FAT32 = FAT32 small and below cyl 1024 0x0c FAT32X = FAT32 large or beyond cyl 1024 0x0f BIGX = Large extended (Windows, PQMagic) 0x35 JFS = Journaled Filesystem (OS/2 4.5x) 0x35 LVM = LVM container, usually with JFS 0x82 SWAP = Linux swap partition 0x83 LINUX = Linux native fs (EXT2/3 etc) 0x83 EXT2 = Linux EXT2 data partition (alias) 0x83 EXT3 = Linux EXT3 data partition (alias) 0xeb BEOS = BeOS filesystem 0xfe PS2S = PS/2 system partition Note: The automatic FAT types will use the required value based on partition size and position. Example formats, all of the following are equal: -t:ext2 symbolic name (case insensitive) -t:0x83 hex value, with the '0x' prefix -t:131 decimal value, numeric format Note that numeric values specified for MBR are interpreted as DECIMAL unless prefixed with '0x' and for GPT they are always HEXADECIMAL! For GPT, either use the full GUID when known, or a symbolic value or hexadecimal type value as listed with the 'type' positional parameter -x:e13-pos : Relative pos after the Int-13 limit (mcs-number) -X:0|1|2|3 : prefered table entry for the MBR extended container default is 3, being the LAST slot in the table so the first three stay available for primaries -Y:0|1|2|3 : prefered table entry for the EBR extended containers default is 1, being the second slot in the table so the first stays available for the logical partition Output: Progress information and confirmation messages Remarks: When creating a type 0x0a = IBM BootManager partition, and an imagefile DFSIBMGR.IMG exists in the current directory, DFSee will prompt you to write this image to the new partition. In batch mode you can PREVENT an existing DFSIBMGR.IMG image to be installed by using the '-I-' option. A DFSIBMGR.IMG image can be created from an existing installation using the DFSIBMGR command. By default, the explicit 'I13X' check will be REMOVED from the bootsector code for the bootmanager, unless you specify -I13X- On creating logical partitions, with explicit start en size, note that the specified values are for the EXTENDED CONTAINER, so the actual logical partition itself starts a little further down, and is the same amount of sectors SMALLER than that. The amount is called the GAP size, and is the number of sectors between the EBR sector and the bootsector for the logical. It is typically ONE track in size but can be set to any desired value using the -G:gapsize option. So, to create a logical partition that starts exactly at sector 1000 and has a size of 500, using a gap of 50 sectors you would need: cr log FAT -a:950,s -s:550,s -G:50 _______________________________________________________________________________ #160 DELETE command DELETE [pid] [disk][options] = Delete one or ALL partitions from disk(s) Purpose: Delete one or ALL partitions. Parameters pid : Partition id for 1 partition or '*' for all partitions pid,r : Relative partition ID on specified or current disk disk : Physical disk number for 1 disk or '*' for all disks Used for extra verification only Options: -c- No full clear, just reset system-type to 0x00 -d Partition to delete must be on current disk -d:[nr] Partition to delete must be on specified disk -L- Do NOT delete related DLAT LVM info for a primary, as this allows recreation in same place (resizing). -p:x Partition ID (PID) to delete (same as 'pid' parameter) -p:x,r Relative partition ID on specified or current disk Output: Progress information and confirmation messages Remarks: The partition will by default be deleted by clearing ALL 16 bytes that make up the entry to ZEROES. Using the '-c-' option will just set the system-type to hex '00'. This is the minimum required change and may allow for relatively easy rollback. Note that some programs, like the OS/2 LVM.EXE have problems with partially deleted partitions, and claim the tables are invalid if the 'deleted' partition overlaps another. By default, related IBM BootManager (pre-LVM) and DLAT LVM information is automatically removed to avoid inconsistencies, unless the -L- option is used to keep that info present. _______________________________________________________________________________ #170 DFSIBMGR command DFSIBMGR disk [name] = Create new IBM BootManager image for 'create' Purpose: Create a DFSIBMGR.IMG image-file from the IBM BootManager installed on the specified disk, to be used later on 'create' commands when creating new IBM BootManager partitions. Parameters: disk mandatory Disk to get the IBM BootManager image from name optional Name for the image (default DFSIBMGR.IMG) Output: Progress information Remarks: The 'create' command will automatically search for an image with this name when a type 0x0a = BMGR partition is created. _______________________________________________________________________________ #173 DISKLIST command DISKLIST = Show compact list if all disks, including size Purpose: Show a single line for each disk, to make it easy to identify by number, UNIX devicename or OS/2 LVM name, size and other optional identification information (see remarks) Parameters: none Remarks: Linux implementation uses the 'hdparm -i devicename' command and a GREP filter to display the info, works mainly for IDE/SATA disks and may fail on some systems, in which case the 'Model' name for the disk is retrieved from the '/sys/block/DEV/device/model' file where DEV is the bare device name like 'sda' (works for USB disks) On Windows, the information is retrieved from the Registry: HKLM->System\CurrentControlSet\Services\Disk\Enum The 'DeviceInstanceID' found there is slightly formatted for better readability, specifically to show the Vendor, Product and Revision strings for USB devices. On OS/2, it will try to use the SCSI PASSTHRU ictl commands to get the vendor/product/revision information strings. This works well for USB (USBMSD.ADD) and probably for regular SCSI disks. For AHCI and IDE/PATA disks, it queries the info output from the OS2AHCI$ and IBMS506$ devices respectively for that info. Other platforms, not implemented yet. _______________________________________________________________________________ #180 FAT2OS command FAT2OS pid [disk [boot-OS]] = Set FAT-BR boot code to OS2|NT|IBMDOS|MSDOS Purpose: Replace boot code by OS/2, NT, IBMdos or MSdos boot code for FAT Parameters pid : Partition id for 1 partition or '*' for all pid,r Relative PID, on current or specified disk disk : Physical disk number for 1 disk or '*' for all boot-OS : Specifier for boot code, taken from operating system: OS2 - OS/2 version 4 (Warp, Merlin) NT - Win-NT version 4 IBMDOS - IBM DOS 7.0 PCDOS - IBM DOS 7.0 MSDOS - MS DOS 6.22 Options: -d[:nr] : Use current or [specified] disk for relative PID Output: Progress information and confirmation messages Remarks: a: The command only replaces the boot code part of the FAT bootsector. Other stuff, like the boot parameter block (BPB) is kept intact to preserve geometry and format information b: This command is intended to prepare a partition for booting the specified OS (FAT only), from a pure DOS environment. Step 1) Partition using DFSee FDISK (make at least 1 FAT) Step 2) Reboot, to make DOS assign a drive-letter Step 3) Format the FAT partition using standard DOS FORMAT Step 4) Use DFSEE FAT2OS command to make it correctly bootable Step 5) Xcopy a saved set of specific operating system files to the partition, including the system-files like OS2BOOT, OS2LDR, NTLDR, IBMBIO/IBMDOS, IO.SYS/MSDOS.SYS etc., depending upon the Operating System. Step 6) Boot that partition (directly or through a BMGR) _______________________________________________________________________________ #190 FIXCHS command FIXCHS disk [-c[:0|1|2|?]] = Fix CHS values to match LBA/current geometry Purpose: Change all nonstandard values for the CHS fields in partition tables to valid ones to avoid warnings or failures working with other disktools (FDISK, LVM, Partition-Magic etc) Parameters: disk mandatory Disknr or '.' for current, '*' for all disks Options: -c:[0|1|2|?] : CHS style: 1=PQMagic, 2=MS, default 0=IBM/DFSee or -c:IBM To override the global style being used, and or -c:PQ force ALL CHS value to use this specific style. or -c:MS useful to avoid "corruption" messages/errors by tools like Partition-Magic or LVM ... -c:? Will force the CHS-style selection dialog to be presented when 'make default' was used Output: Progress information and confirmation messages Remarks: Nonstandard values for the CHS fields sometimes cause problems in tools like LVM, it refuses to update anything because the "partition table might be corrupt" ... There are two cases: for cylinders below 1024 the CHS values must match the calculated linear values (LBA) exactly, and above cylinder 1024 they should be acceptable 'dummy' values. For the dummy values, a few styles are supported, the default is the one normally created by DFSee and by OS/2 FDISK or LVM but you can also select the PowerQuest style to make sure Partition-Magic or Drive-Image are satisfied. Note that the calculated LBA values depend on the logical geometry being used, so check if that geometry is the one you want (or need) to use. Fixing this will get rid of all the DFSee warnings related to CHS problems (as displayed with 'part -w:chs') However, cylinder alignment warnings will stay because the partitions are not moved or resized. This is often less of a problem than CHS mismatches. _______________________________________________________________________________ #200 FIXEXT command FIXEXT [disk | * [to [from]]] [-a] [-e] = Fix extended-container types Purpose: Change between the (windows specific) value 0x0f and the standard 0x05 value for the extended container(s). This will allow older operating systems like DOS and OS/2 to access the logical volumes inside the extended-partition. Parameters: disk optional Disk number or '*', default all disks = '*' to optional New system-type for EBR, default is 0x05 from optional Existing system-type, default is 0x0f Options: -a Change ALL containers, not just the first -e Force setting type other than 0x05 or 0x0f Output: Progress information and confirmation messages Remarks: The nonstandard type 0x0f was introduced by Win9x combined with the FAT32 filesystem. These allow partitions larger then 2GiB and spanning the 8GiB BIOS limit (1024 cylinders). Using the 0x0f type prevents older operating systems from accessing, and possibly damaging, the new partitions. When all FAT16 partition are below cylinder 1024, there seems to be NO VALID REASON to use this type, and it can be safely changed back to 0x05 to allow access by DOS, OS/2 and others. To change the type of a regular primary or logical partition use the 'settype' command, or force it being changed to a regular partition type by using the '-e' option. Note that changing an extended container to a regular primary or logical partition with '-e' will cause problems if it results in an illegal combination of defined partitions. _______________________________________________________________________________ #205 GENPART command GENPART disk | . | * [fn | -b:'fn'] [descr] [-s] [-f-]", GENPART disk|.|* [fn] [opts] = Generate DFSee partitioning script for disk(s) Purpose: Generate a DFSee script (.DFS) that will (re)create partitions as they are now, on the same or a different disk Parameters: disk mandatory Disk number or '*', default all disks = '*' fn optional Base filename for the script to generate descr optional Description string that will be added to the confirmation message when the script is RUN Options: -b:'fn' : Name specified as a string option instead of param Allows usage of space in the name -f- : Do NOT include freespace areas, by allowing automatic placement of the new partitions -s : Use SECTOR based size and location values instead of cylinder and megabyte values (exact copy) -! : Force interactive dialog to specify/confirm options Output: One line confirming each script being generated, and when applicable, the interactive dialog to specify options Remarks: none _______________________________________________________________________________ #210 GPT command GPT [ disk | . | *] [-fix] = Display or fixup GPT partitioning informtion GPT pid -name:newPartName = Change name for GPT partition 'pid' Purpose: Either display the GPT header and each of the partitions from the Partition Table Array (PTA), or RECOVER a missing primary or alternate GPT structure and FIXUP all GPT area CRC values, OR change the name for a specified GPT partition. Parameters: disk optional Physical disknumber, or * for all disks or . for the current disk (default) -fix optional Write back the retrieved GPT areas to the disk, effectively recovering from damage pid mandatory Partition ID (mandatory when changing name) -name:newPartName New name string for the partition name Enclose in single quotes when spaces present Output: Contents of the GPT header(s) and partition table arrays for the disk, or confirmation messages and results for fixing or for setting the new partition name. Remarks: The GPT information is ALWAYS available (retrieved, in-memory) whenever the disk information is read, to display partition information in the DFSee table overview or map display. The display, or FIX will work with that retrieved information and the FIX will WRITE it BACK to both the primary location at the start of the disk, and the alternate location at the end. Before writing, all embedded CRC values are recalculated. Note: to CREATE a GPT disk, use either 'cr gpt' or 'cr pri gpt' or the special MBR2GPT which can also change an existing MBR style disk to GPT _______________________________________________________________________________ #215 GPT2MBR command GPT2MBR [ disk|.] [options] = Convert a GPT-style disk to an MBR-style Purpose: Convert a disk that is currently using GPT-style partitioning to use the classic MBR-style partitioning Parameters: disknr optional Disk-number, '.' for current (default) Options: -a Clear the alternate GPT-header at the END of the disk too (will make automatic recovery to GPT much harder!) -a- Do NOT clear the alternate GPT header at end of disk (default) -p- Do NOT clear the primary-GPT header and the MBR partitions -m- Do NOT clear the MBR partitions, just the primary-GPT header Output: Progress and status information from the underlying commands Remarks: It will rewrite the MBR to remove the GPT guard partition (NEWMBR -c) and wipe sector 1 of the disk (the GPT header) to ZEROES After this, the currently existing GPT partitions will be gone, from any DFSee display (and other tools) but are still recoverable using the alternate-GPT information at the end of the disk. You will be prompted again to confirm if you want to remove those alternate GPT tables as well, making the operation UNRECOVERABLE!. _______________________________________________________________________________ #220 LVM command LVM [pid | *] [-d:nr] [set options] = Update LVM info for partition/disk Purpose: Set one or more LVM related values for selected partition(s), or disk(s) Parameters: pid optional Partition id for partition to update or '*' pid,r Relative PID, on current or specified disk Options: -c : DISK: Update CRC values for LVM sectors on selected disk(s) -C : Delete existing LVM signature sector (BBR) for non LVM type 0x35 partitions, forces COMPATIBILITY mode to avoid 'partition corrupt' errors from LVM.EXE or eCS installer Can be used with, or without specifying a specific PID -d:nr : disk number, restrict updates to specified disk only -d : restrict updates to the current disk only -D : Delete existing LVM info, and for an LVM-type (0x35) try to recover the values from an existing LVM-signature area Without recovery, default values will be substituted. -D -C : Delete existing LVM info including the signature area, and force default values (resets LVM to compatibility) -G : DISK: Update LVM geometry to match the DFSee L-Geo for disk -i or -i- : set installable status for volume, or remove it -l:drive : set prefered driveletter for the volume -l:"" or -l- : remove driveletter for the volume (hide) -list : List LVM structures only, no update, implies -P- -m or -m- : set volume on the IBM BootManager menu, or remove it -n[:name] : DISK: set new disk name for selected disk(s), optional prompt -n[:name] : With an explicit PID specified (partition update), will set the disk name to use, when no LVM diskname is known yet -p:part : set partition name for this partition -p:"" or -p- : remove partitionname. LVM will use a default. -P- : Do not prompt for any values with a dialog-window -r- : Do NOT use existing LVM-signature data in LVM recovery -s : force synchronization of start/size with p-tables -v:volume : set volumename (= IBM BootManager name if on menu) -v:"" or -v- : remove volumename. This deletes the volume for LVM -V : Automatically assign a volume-name for a new partition The options marked with 'DISK:' work at the disk level and do not require a 'pid' to be specified. Output: Confirmation and progress information, and when no -P- option is used, an LVM-update dialog window allowing change of most LVM values using entry-fields and check boxes. Remarks: When the -P- option is specified, the fields will be displayed only, from this display, the 'd' or key will display the full LVM-information structure, and the 'x' key the related partition table. LVMSHOW will use this to display that sector. When no LVM-info exists for the partition, it will be created automatically with a constructed default value for the partition name, or the name specified with the -n option. With the -V option, a volume name will be assigned as well. The -d/-c options will update the CRC values, useful after manual editing of the LVM-info sectors, and in combination with the -n options it will update the descriptive LVM diskname. No other options can be used with -d or -c The -c option alone will also check for obsolete DLAT entries, and can remove these to avoid the error messages from LVM that say: 'The partition table on this disk may be corrupt'. Be careful when updating a multiple partition volume (like JFS) the volume name and driveletter must be the same on all! The command can be called directly from the Operating System command line, as in: DFSOS2.EXE -b lvm 2 -v:System -menu This will place the 2nd partition on the BMGR menu as "System" Unlike the "delete volume" operation in LVM itself, the "-v-" option in DFSee does NOT delete the partition as well. All the other LVM-info will remain intact, including the driveletter. A subsequent "-v:volume" will recreate the volume with a new name and use the same ("existing") partition and driveletter. Note that YOU are responsible for keeping the driveletters unique for the whole system. Using the "-p-" option deletes the explicit partition name, LVM will use a default name like "[ A3 ]" in this case. While the dialog is up, commands that are started using a function key can still be executed. (F4 .. F9 are useful) The output in the "text output window" can still be scrolled using + arrow keys or + PgDn/PgUp. As another example, remove all RELEVANT info from the LVM info for a partition. This will delete everything that is normally used or displayed for an LVM volume. Example, for partition 06: lvm 06 -D -v- -p- -l- -m- -i- After applying it will NOT be considered a volume anymore. However, the LVM sector for the partition will still contain the disk name, the partition size, and LVM signature and a CRC. Using this partition with DFSee, LVM.EXE or LVMGUI would look the same as using a freshly created partition without any LVM info. _______________________________________________________________________________ #230 LVMCLEAN command LVMCLEAN [disk|.|*] [-a] = Clean obsolete LVM DLAT sectors in MBR track Purpose: Clean obsolete LVM DLAT sectors in MBR track area (1..254) for specified disk(s). (DLAT = Drive Letter Assignment Table) Parameters: disknr optional Disk-number, '.' for current or '*' for all disks Options: -a ALL, do NOT exclude DLAT for current disk geometry Note: This will DELETE the LVM info for any current primary partitions! Output: One line per DLAT sector being cleared, showing the sectornumber Remarks: Might be useful to clear left-over DLAT sectors after changing the disk geometry, to avoid confusion _______________________________________________________________________________ #235 LVMCRC command LVMCRC [disk] = OBSOLETE! Use "LVM -c" or "LVM -d" _______________________________________________________________________________ #240 LVMREDO command LVMREDO disk|.|* [-C] = Refresh LVM info sectors (DLAT) for disk(s) Purpose: Rewrite all the LVM information sectors like the DLAT and BBR to make them consistent (DLAT = Drive Letter Assignment Table) Parameters: disk mandatory Disk number or '*', default all disks = '*' Options: -C optional CREATE new default LVM information for partitions that do not have any yet. Output: Progress information Remarks: With the '-C' option specified, the LVMREDO is similar to the 'VCU' command, with main differences: - Existing LVM information is not cleared or changed - LVM info that is created new will not specify a driveletter _______________________________________________________________________________ #250 LVMSHOW command LVMSHOW [pid | letter | * | 0] = Show related LVM-info for 1 or all partitions Purpose: Perform a simple display of the LVM-info sector for the current or specified partition. (DLAT = Drive Letter Assignment Table) Parameters: pid optional Partition id for partition to be listed, letter optional or driveletter assigned to a partition, or '*' or '0' to list for all partitions. List CURRENT partition if not specified. Output: Contents of the LVM-info sector(s) with names and driveletter(s) Remarks: Uses the 'lvm' cmd in read-only to find the info, and a display of the then default sector to display it. It will fail when the partition has no LVM-info, and might display the wrong sector. To list for ALL partitions, a 'plist lvm' command is executed. _______________________________________________________________________________ #260 MBR2GPT command GPT2MBR [ disk|.] = Convert (or recover) an MBR-style disk to GPT Purpose: Convert a disk that is currently using MBR-style partitioning to use the classic GPT-style partitioning Parameters: disknr optional Disk-number, '.' for current (default) Output: Progress and status information from the underlying commands Remarks: It will rewrite the MBR to remove the MBR partitions (NEWMBR -c) and create a single primary 'GPT guard' partition instead After this, it will create empty GPT partition tables (CR gpt) at the start of the disk, as well as at the end (alternate) It WILL automatically recover any GPT partitions still defined in either the primary-GPT header+tables directly after the MBR or the alternate-GPT ones at the end of disk, when present (this would recover from an accidental 'newmbr' on the disk) Any new GPT partition can then be created using 'CR gpt ....' style commands, or the 'Create new partition' menu item. _______________________________________________________________________________ #270 NEWMBR command NEWMBR [disk | . | *] [-clean] = Refresh MBR boot code from various sources Purpose: Create or refresh the boot code in the master boot record (0) Parameters: disk optional Disk to operate on, default is CURRENT You can specify either this or use the -d option for a specific disk Options: -c[lean] = Clear the partition tables too, resulting in an empty disk, with valid MBR code This also clears the Windows 'NT-signature' -d:disk = Apply to specified disk or current disk -f:disk = Clone MBR-code from the specified disk to this one -I[:img] = Use specified or default (newmbr.img) imagefile for the boot code instead of the built-in code -n[ocode] = clear the code area, upto the Win-NT signature value -N[ocode] = clear the code area, including the Win-NT signature Output: Progress information and confirmation messages Remarks: Without the -c option, this command will ONLY replace the boot code part of the MBR, the partition tables and hence all the currently defined partitions will stay intact! Also the Windows disk identification number (NT-signature) will keep its value, so Windows should NOT re-assign all driveletters on the next boot :-) When using the '-c' option, the Windows disk identification number (NT-signature) will be set to all ZEROES as well. This makes sense, since the existing driveletter assignments that Windows keeps registered will be obsolete now the tables are empty ... On large-floppy (style FLP) or encrypted (style CRP) like LUKS, you will get an extra warning in the confirmation text, that it will destroy the current format/contents. In batch mode, or when executed from the OEM-engine, the command will fail with a warning. To apply NEWMBR then, you must first WIPE the first sector of the disk to remove the FLP/CRP style. _______________________________________________________________________________ #280 NTCDR command NTCDR CD-nr letter | - = Set driveletter for CDROM (NT version only) Purpose: Set or clear the driveletter for specified CDROM device Parameters: CD-nr mandatory Sequence number for CDROM, first is 1 letter mandatory Driveletter to be used for the CDROM device as displayed in the DFSee "NTMAP" command Specify '-' to clear the driveletter Output: Progress information and confirmation messages Remarks: Only available in the Windows version of DFSee (DFSWIN.EXE) For use on Windows NT-4 only, not recommended on 2000 or XP. _______________________________________________________________________________ #290 NTDDD command NTDDD action WIN32dev [NT-dev] = Direct manipulation of DosDevice mapping Purpose: Low level corrections, test and debugging of DosDevice mapping (NOT intended for normal use) Parameters: action mandatory Flag value to be passed to DefineDosDevice The default is 1 (RAW) Values: DDD_RAW_TARGET_PATH 1 DDD_REMOVE_DEFINITION 2 DDD_EXACT_MATCH_ON_REMOVE 4 DDD_NO_BROADCAST_SYSTEM 8 WIN32dev mandatory Specification for the WIN32 device, usually this will be a driveletter (check NTDEV) NT-dev optional Native NT device name (path) to define for the specified WIN32 device name. When not specified, the mapping is deleted Output: Success or failure status for the DefineDosDevice API call Examples: DDD 1 R: ;Unassign R: mapping DDD 1 Q: \Device\Cdrom0 ;Assign Q: to CDROM 1 DDD 1 F: \Device\HardDisk0\Partition3 ;Assign F: to 3rd part ;on the first harddisk Remarks: Only the (dynamic) mapping used by NT is updated, the registry key for driveletter mapping is not modified. Only available in the Windows version of DFSee (DFSWIN.EXE) For use on Windows NT-4 only, not recommended on 2000 or XP. _______________________________________________________________________________ #300 NTDEV command NTDEV [ device ] [mapping] = Show DosDevice mapping, wildcards limit output Purpose: Show the mapping between WIN32 devices, including driveletters, and the underlying system-wide NT device names Parameters: device optional Wildcard specification for the WIN32 name The default is "?:" resolving driveletters mapping optional Wildcard specification for native NT name The default is "*" for all devices useful are: "*partition*" for partitions "*lanmanager*" for NET USE... Output: A two column table with WIN32 versus NT native device names Remarks: useful to check the assignment of driveletters to partitions on a disk, but also for network drives (aka NET USE ...) Only available in the Windows version of DFSee (DFSWIN.EXE) For use on Windows NT-4 only, not recommended on 2000 or XP. _______________________________________________________________________________ #310 NTMAP command NTMAP [ verbose | sync ] = Show reg-diskkey, update & sync with DosDevice Purpose: Show a table with disk-number, relative (registry) partition nr, the driveletter assigned, the size in Megabytes and the native NT device name related to the driveletter. Parameters: verbose optional Expand table to multiple, detailed lines for each listed driveletter sync optional Synchronization request of the DFSee info with NT registry, MBR signatures and the dynamic driveletter assignments Note: automatically executed for "SETLET" commands without a "ns" parameter Output: Progress information Remarks: The driveletters as shown by the DFSee "Part" table will be leading, and replace any existing values. Actions performed: - When needed: NT signature in the MBR will be written - NT registry "disk" key will be (re)created - dynamic DosDevice mapping between WIN32 and native NT device names is updated when needed Only available in the Windows version of DFSee (DFSWIN.EXE) For use on Windows NT-4 only, not recommended on 2000 or XP. _______________________________________________________________________________ #320 NTSIGN command NTSIGN [disk [signature]] = Set NT-signature value (32 bits) in MBR Purpose: Set a well-known value as NT disk-administrator signature Parameters: disk optional Disk to operate on, default is all disks sign optional The signature value, decimal or prefixed hex Default value is the current one present. Output: Progress information and confirmation messages Remarks: Setting a fixed value for the NT signature value in the MBR can avoid unwanted reassigning of drive-letters when using Windows NT. It uses this value to correlate the drive-letter mapping kept in the registry. When cloning an NT image to a new disk, set the signature to the same (known) value. _______________________________________________________________________________ #330 PCLEAR command PCLEAR disk [P][Lvm[S]][Br] = Clear info in P-tables, LVM and/or Boot record Purpose: Clear contents of partition table, LVM or boot record sectors. The sectors will be completely filled with zero-bytes (0x00) Parameters: disk mandatory Physical disknumber, or * for all disks type Ptable Partition table sectors (MBR and EBRs) Lvm LVM disk/volume information sectors S LVM signature sectors (only valid with'L') Bootrec Boot records for each partition Only the first letter is required and multiple types can be specified. Output: Confirmation messages (interactive mode only) Remarks: Confirmations (yes/no) will be issued for each physical disk when clearing partition table and LVM-info sectors, and for each individual partition when clearing the boot record. _______________________________________________________________________________ #340 PLIST command PLIST p|f|e|m|b|w|l [opts] = list: part|free|ebr|mbr|boot|walk|lvm Purpose: Show one of several lists of partition related information Parameters: type optional type of list wanted: p|f|e|m|b|w|l part normal partitions free freespace areas ebr EBR-chain mbr MBR partition table entries boot Bootsectors for all partitions walk MBRs and all EBRs (as WALK cmd) lvm LVM volume information sectors and the LVM signature sectors Options: -d[:nr] Disk to operate on, default is all disks when not specified and current disk for '-d' -r Related, include extra-info on related sectors (MBR/EBR versus LVM-info) Output: The list of the requested type with info on start-sector and end-sector numbers, sizes and more. Remarks: All sector numbers are also stored in the DFS Sectorlist, for use with the LIST and EXPORT commands. _______________________________________________________________________________ #350 PRESTORE command PRESTORE *|disk Fname [types] = Write info from file into P-tables and LVM Purpose: Restore (selected) partition table, LVM and boot record sectors from a binary file created with the PSAVE command. Parameters: disk mandatory Physical disknumber, or symbolic value: . = Current disk * = ALL disks when no file extension present * = SAME disk as file with a file extension Fname mandatory Filename for file(s) to restore, when no extension is specified, the 'disk' parameter will be used to select the right .PDn file. An explicit extension can be used to restore from a different file (other disk number). types optional Only restore sectors of specified type(s) r = Master boot record e = Extended boot records G = GPT header sectors g = GPT entry sectors b = Filesystem boot records l = LVM information sectors L = LVM signature sectors (BBR) including feature area (IMZ) options: -c- = no confirmation for each sector, only for the complete .PDx file -l = list sectors only (no write back) -v = verbose display and prompting Output: Confirmation messages, depending on the specified options Remarks: Sectors are not restored when the '-l' option is specified. Quick restore with a single confirmation prompt for the whole file can be forced using the "-c-" option. When LVM signature sectors are restored (type letter 'L') it will also automatically restore the compressed imagefiles that are saved for type 0x35 partitions (*.Fnn files) that contain the complete LVM BBR feature area. _______________________________________________________________________________ #360 PSAVE command PSAVE *|disk Fname [comment] = Save Partition table and LVM info in file Purpose: Save contents of all partition table, LVM and boot record sectors in one binary file per physical disk, selectively restorable with the associated PRESTORE command. Parameters: disk mandatory Physical disknumber, or * for all disks Fname mandatory Base filename for saved file(s), the extension will be '.PDn' (n = disk nr) comment optional A text string that will be included in the saved file(s) for easy identification. Output: Progress info, one letter r, e, G, g, l, L or b for each sector Remarks: Each resulting file will start with an ASCII header that contains info on the DFSee version used, date and time and some info on the disk and partitions. It also includes the comment specified with the PSAVE command. This info can be easily referenced by a simple TYPE of the file, the ASCII part ends in an EOF character (ctrl-Z) so the rest of the binary info does not mess up the display. it will also automatically create one compressed imagefile for each type 0x35 partition in a *.Fnn file where the nn in the DFSee partition ID. It contains the complete LVM BBR feature area, important for bad-block relocation and for multiple-partition volumes. _______________________________________________________________________________ #370 SETACCESS command SETACCESS pid [hide|vis|multi] = Make partition 'pid' accessible or hidden Purpose: Set visibility for the specified partition. Parameters: pid mandatory Partition id, see PART and MAP display pid,r Relative PID, on current or specified disk hide optional Make this partition hidden (invisible) vis optional Make this partition visible, hide others multi optional Make this partition visible, but do allow multiple visible primary partitions per disk Options: -d[:nr] : Use current or [specified] disk for relative PID PID MUST be specified as relative 'pid,r' in this case, example, set 2nd part on 2nd disk hidden: SETACCESS 2,r -d:2 hide Output: Progress information and confirmation messages Remarks: The partition will be made visible (types 01 .. 0f). All other primaries on the same disk will be made hidden, except when the 'multi' parameter was given. _______________________________________________________________________________ #380 SETBOOT command SETBOOT [-]opt[:options] = IBM BootManager setup and reboot options Purpose: Configure BMGR; Set partition to boot, and (optionally) boot Parameters: opt mandatory Option letter/word for the setboot action options optional Depending on the selected option: -[0..5]:BM-name = set system 0..5 to a Bootmanager name -b = shutdown filesystems and reboot now -d:d = set next-boot to this driveletter (d:) -disk:nr = Operate on Bootmanager on specified disk -ibd:d = reboot from the drive letter specified -iba:BM-name = reboot from Bootmanager name specified -F- = no buffer flush, show PM popup message -list = List available names on Bootmanager menu -m:mode = set menu display to normal or advanced -q:[disknr] = query Bootmanager settings (on disknr) -Q- = Suppress the auto-quit feature in non-windowed operation. Need to use this when using the command from a script, non-windowed. (otherwise script will prematurely abort) -t:timeout = menu timeout, number of seconds or NO -x:number = set system-index to specified number System-indexes 0..5 have the following meaning: 0 default system Booted when no other selection is made from the menu, or when the timeout is set to NO. 1..3 fallback range On a failing boot on one of these systems, the next boot will be of the next lower-number system (fallback scenario) 4 force-reboot Indicates the system-name to boot next time, without display of the menu (forced). This is used by the /iba:name option. The name is automatically cleared on the next boot. 5 last-booted The system-name last booted using IBM BootManager. This will also be the default when the default system itself (0) is not set. Output: Progress information and confirmation messages Remarks: Both the 'classic' version of IBM BootManager (2.1 up to Warp4) and the "Warp Server for e-Business" or "eComStation" version working together with LVM are supported. The latter uses longer names for the partitions that are bootable. All Bootmanager names are CASE-SENSITIVE, boot will fail if an incorrect case name is specified on -iba or others. - The reboot from DFSOS2.EXE requires DOS.SYS to be loaded! - The reboot from DFSDOS.EXE will only work on Win9x when the external reboot program DFSDOSX.EXE is present. This executable is delivered in the package as dfsboot9.exe and needs to be renamed before it will work on Windows-9x. _______________________________________________________________________________ #390 SETLET command SETLET pid letter | - [-n] = Set driveletter for DFSee; [-n] = no sync Purpose: Set or clear the driveletter for a partition Parameters: pid mandatory Partition id, see PART and MAP display pid,r Relative PID, on current or specified disk letter mandatory Driveletter to be used with the partition as displayed in the DFSee tables. Specify '-' to clear the driveletter -n optional No Synchronize with NT registry and the WINDOWS: dynamic NT drive-letter assignment. Otherwise a complete sync between DFSee and the registry will be done, comparable with the "NTMAP sync" command. -n optional No Synchronize with the LVM Engine to get OS2/eCS: dynamic LVM drive-letter assignment. Otherwise the changed letter will be communictaed to the Engine and become effective immediately. Options: -d[:nr] : Use current or [specified] disk for relative PID Output: Progress information and confirmation messages Remarks: Setting the driveletter as used in DFSee tables works for all versions. However, the real use is with the NT version where the driveletter as used by NT itself will change too! It will be updated in the "Disk" key in the registry and in the dynamically maintained DosDevice mapping It might be wise to reboot or shutdown quickly after changing critical drive-letters like the WINNT system or boot drive. To change driveletters and other related info for systems with LVM (OS/2 4.5, eComStation) use the LVM command. _______________________________________________________________________________ #400 SETNAME command SETNAME pid [BM-name] = Set or reset IBM BootManager name for partition Purpose: Set or clear the name for a partition, adding it to the menu Parameters: pid mandatory Partition id, see PART and MAP display pid,r Relative PID, on current or specified disk Options: -d[:nr] : Use current or [specified] disk for relative PID BM-name optional When specified, this is the name to be used in the IBM BootManager menu. (length 8) When not specified, the partition will be removed from the menu by clearing the name in the IBM BootManager administration. Output: Progress information and confirmation messages Remarks: To change the volume name and other related info for systems with LVM (OS/2 4.5, eComStation) use the LVM command. _______________________________________________________________________________ #410 SETTYPE command SETTYPE pid disk new [old] [-e] = Change partition type from old to new Purpose: Change the system-type for a partition to a new value Parameters: pid mandatory Partition id, see PART and MAP display pid,r Relative PID, on current or specified disk disk mandatory Disknr, * or 0, used for verification new mandatory New system-type for the partition; number Decimal value 0 .. 255 or Hex as 0x00 .. 0xff symbolic A name from the predefined set of partition types. The most used system-types are: hex symbolic 0x01 FAT12 = FAT12 0x04 FAT16 = FAT16 < 32 MiB 0x05 EXT = Extended partition (chain) 0x06 FAT = FAT16 > 32 MiB 0x07 IFS = Installable File system 0x07 HPFS = IFS, HPFS (alias) 0x07 NTFS = IFS, NTFS (alias) 0x0a BMGR = IBM BootManager 0x0b FAT32 = FAT32 small and below cyl 1024 0x0c FAT32X = FAT32 large or beyond cyl 1024 0x0f BIGX = Large extended (Windows, PQMagic) 0x82 SWAP = Linux swap partition 0x83 EXT2 = Linux EXT2 data partition 0xeb BEOS = BeOS filesystem 0xfe PS2S = PS/2 system partition old optional Existing system-type, for verification Decimal, prefixed-hex or symbolic value Options: -e = Force change to an extended container type Output: Progress information and confirmation messages Remarks: Only the type of the partition in the partition table will be changed. The actual internal format of the partition is not affected by this operation. You can get an overview of all types with the 'TYPE' command. To change the type of an extended container (05 / 0f), use the 'fixext' command, or force it using the '-e' option. Note that changing a regular primary or logical partition to an extended container with '-e' will cause problems if it results in an illegal combination of defined partitions. _______________________________________________________________________________ #420 STARTABLE command STARTABLE pid [multi | clear] = Make partition 'pid' startable ([not]ACTIVE) Purpose: Make the selection partition the 'active' one to be booted Parameters: pid mandatory Partition id, see PART and MAP display pid,r Relative PID, on current or specified disk Options: -d[:nr] : Use current or [specified] disk for relative PID multi optional Allow multiple visible primary partitions on each disk. This is invalid for older operating systems like OS2 Warp 3 or 4, windows-9x, 3.x or DOS. clear optional Clear the 'active' flag to 'not startable' Output: Progress information and confirmation messages Remarks: The partition status will be set to 'active' (0x80) and, if needed the partition will be made visible. All other primaries on the same disk will be made hidden, except when the 'multi' parameter was given. When 'clear' is specified, the active bit will be reset (0x00) and no change in visibility for any partition will be made. _______________________________________________________________________________ #430 TYPE command TYPE [type | first last] = Show system-type description (for 00..ff) Purpose: Show short description for one or more known system types Parameters: type optional one system type to query first optional first type value for a range to show last optional last type value for a range to show Output: Single line when 'one type' queries, or 4 descriptions per line covering all known system-types from 00 through ff or from 'system-type' up to 'last' if a range is given. Remarks: none _______________________________________________________________________________ #440 VCU command VCU disk | * | -d[:nr] = Clear existing LVM-info, create new defaults Purpose: Create new LVM information like volume name and partition name Remove current LVM information when present. Parameters: disk | * Disk number or '*' for all disks Options -d[:nr] Disk number, or current disk Output: Progress information Remarks: This can be used to create default LVM-information with names derived from partition id, filesystem-types and size, and assign the drive-letters as currently known to DFSee. The default volume names will be taken from the current IBM BootManager names or the drive LABEL when available. LVM additional information in the signature sectors, as used by LVM/JFS partitions (type 0x35) will not be cleared, so it is safe to use this command on a system with JFS partitions. _______________________________________________________________________________ #450 VIRT command VIRT [opt] Fname | size [H S] = Mount a partionable medium (virtual / image) This is a deprecated command, and now a direct alias for the MOUNT command, see the description with 'mount' for details _______________________________________________________________________________ #460 DETACH command DETACH disk | * | -l = Detach mapped partionable medium Purpose: Remove a partionable medium from the list of available disks Parameters: disk Detach the disk with the specified DFSee-id * Detach all disks currently mounted -l Detach the LAST disk (highest DFSee-id) Output: Attachement details for the disk being removed Remarks: There is usually no need to remove attached disks, they automatically disappear when DFSee ends _______________________________________________________________________________ #470 VSTATUS command VSTATUS = Show R/W and usage status of virtual disks Purpose: Show nr of sectors in use and read/write statistics for virtuals Parameters: none Output: A few lines with statistics for every virtual disk _______________________________________________________________________________ #480 WALK command WALK [disk] = Select disk and walk MBR/EBR chain, reset Purpose: Show all partitioning information for the specified disk Parameters: disk optional disk nr, default is current if open or 1 Options: -r reset previously forced geometry -R open the disk in Read-only mode -R- force the disk in Read-write mode Output: Disk Geometry, MBR and all linked EBRs in partition format. EBR chaining errors like backward links and logical loops will be detected and warnings or errors will be displayed. Remarks: The dfs_number variable for REXX will be set to number of disks See also: DISK command (dfscmds.txt) _______________________________________________________________________________