Yep, I must have changed names while developing the batches , the correct file name is "mkdualdisk.cmd" of course, I'll edit/correct the readme.txt.
When you run mkprilog.cmd, at the end it should display:
The image should have been created as Prilog.img, now you need to
manually dd it to the destination disk, a suitable command would be:
dsfi.exe \\.\PhysicalDrive[n] 0 0 Prilog.img
Make sure that you use the RIGHT Disk Number [n], do check in Disk Manager.
The disk can be mounted indifferently through the 4kb or the 512
bytes/sector interface to deploy the image.
Once the image has been deployed you may need to disconnect and reconnect the
disk to have the FAT12 volume be recognized and mounted.
Then you can go to Disk Manager and create a Primary partition, NTFS formatted
extending on all the available space on disk (or on just a portion of it).
It is "better" to use a Vista (or later) OS to create the NTFS partition
The partition would be better if Megabyte aligned.
(or do it manually or use a suitable third-party tool) as the XP will align it
on head/cylinder boundaries, whilst a MB-aligned partition will be faster on
slow buses such as USB 2.0
The partition and the NTFS filesystem MUST be created when the disk is connected as
a 4kb sectored device, this is NOT negotiable.
Once the second partition has been created, and I repeat, this MUST be done
with the device connected as 4kb sectored, you can run the mkdualdisk.cmd
Which will modify the disk and create the needed EPBR's.
Now , check the drive letter assigned in Disk Manager to the 256 MB FAT (or assign to it one), you will see how that that same drive letter in "My Computer" is assigned to the 31.6 MB FAT partition (the size of the FAT partition comes from the choice you made in mkprilog.cmd, where you are asked to provide a size for the partition between 1 and 32 Mb).
The batch create however an image with only one partition, the first one, primary (on the left in Disk Manager) which is a (smallish) FAT(12) one and the second one (on the right in Disk Manager) which is a (largish) NTFS partition that you create manually in DIsk Manager, which is later trasformed by the riunning of mkdualdisk.cmd into a Logical Volume inside Extended so guess to which partition I refer with:
Once the mkdualmode.cmd has been run successfully, you need to copy to the first (FAT12) primary partition ...
I know that the choice of using dark blue for primary partition and of light blue for logical volumes and a tiny light green border around the Extended partition is not the best choice in the world to distinguish something visually, but you should sue MS for this .
I cannot refer to the partition as having a given size, as it depends on the choice you make when running mkprilog, and the size of the "other" partition of course depends from the size of the disk and/or from the size of the partition you created manually in Disk Manager, I thought, that order (first), filesystem used (FAT12) and nature of partition (primary) was clear enough, but I am open to any suggestion to make this more clear.
The .bss files should have been generated in the same folder where mkdualmode.cmd was run, i.e. C:\MkPriLog\ in your case, and where should be also the dsfi.exe, elevate.exe and Switcher.cmd, maybe I could call this "tool folder" to better make it clear?
The file as4kbNTFS.bss and as512NTFS.bss are created by "mkdualdisk.cmd" when it displays:
Creating a copy of the 4kb bytes/sector NTFS bootsector
And modifying it to become the 512 bytes/sector NTFS bootsector
I may add a couple more lines f text so that it becomes:
Creating a copy of the 4kb bytes/sector NTFS bootsector and saving it as C:\MkPriLog\as4kbNTFS.bss
And modifying it to become the 512 bytes/sector NTFS bootsector, saving it as C:\MkPriLog\as512NTFS.bss
Edited by jaclaz, 23 January 2015 - 01:03 PM.