Partition Manager

711 posts, 56 voices

Pages: 1 ... 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29

Feb 17, 2021 3:19pm Jon Abbott (1421) 2651 posts	Did you do this without DIM LOCAL? I used DIM LOCAL. I also created a localised version of 26bit BASIC so it can be softloaded whilst PM is running, without affecting the existing BASIC. I put in for GPT LBA, as there is a form of extended partition that allows for relative offset I believe you’re referring to MBR, which supports both CHS and LBA addressing and has Extended partitions. GPT is only LBA based and doesn’t require Extended partitions as there’s no limit on the size of the partition table. If required, I will add support for CHS in MBR but at the minute it’s LBA based. I’ve not bothered supporting Extended partitions as they will never be a thing in RISCOS – we’re going straight to GPT. I’m only adding MBR to cover the Pi. I’ve allowed up to 128 in my implementation, which matches the recommended spec. Hopefully something will be done to fix FileCore’s limitation of 8 drives, otherwise only the first 8 will be accessible – I don’t think that will be an issue for most people, but there’s always the edge cases.

Feb 24, 2021 7:37am André Timmermans (100) 655 posts	While looking for something totally unrelated I found partitioning info in FileCore.Doc.MiscOp. A good summary with some info on the incompatibilities with FileCore which may be of use (for example the GPT issue with the boot block). FileCore partitioning Pros: first partition on a disc is fully compatible with old FileCore unlimited number of FileCore-formatted partitions fully compatible with CHS addressed drives Cons: not supported by any other operating systems (except RISC iX) only the last partition can be non-FileCore format partitions can only start and end on cylinder boundaries partition size is limited to 65535 cylinders = approx 502 GiB assuming 512-byte sectors, 63 (max) sectors/track, 255 (max) heads MBR partitioning Pros: can be overlaid on the first track of a FileCore partition, leaving the boot block at &C00, so the first partition is compatible with old FileCore (except for old-map or single-zone new-map discs, where the MBR partition table clashes with the FileCore free space map) compatible with most other operating systems partitions can start and end at any sector Cons: limited to 4 partitions partition size is limited to 2 TiB GPT partitioning Pros: supports 128 partitions supports partitions up to 8 ZiB (9.4 × 10^21 bytes), although in practice the FileCore disc size limit of 16 EiB (16 million terabytes, or 1.8 × 10^19 bytes) would apply first partitions can start and end at any sector Cons: incompatible with old FileCore (cannot place boot block at &C00) incompatible with 32-bit Windows, and any version of Windows, Mac OS X or Linux prior to approx 2007 cannot support CHS addressed drives (because you can’t fit partition table and boot block into first track)

Feb 25, 2021 3:26am Jon Abbott (1421) 2651 posts	Must have been written a while ago if it’s stating an incompatibility with Windows! GPT is now the defacto standard by virtue of UEFI. I’ve been pondering on the whole FileCore debacle whilst coding PM. Why don’t we just deprecate FileCore and switch to an image file system? FileCore really isn’t suited to modern drives, which require TRIM and wear levelling and we have a real problem in that nobody understands it and the documentation is very poor.

Feb 27, 2021 8:51pm Paul Porcelijn (8775) 10 posts	RISC OS does not recognise the USB-interface of the recent RPi_Pico card, complaining “Has it been formatted?”. This is caused by FAT32FS not detecting Pico’s rather spartan, read-only FAT16 layout. I was very pleased by finding Jon Abbott’s PartMan outwitting FAT32FS, duly detecting Raspberry Pico’s first (and only) MBR-partition as FAT16 formatted. This is however only shown in the PartMan logfile text. I took the liberty of extending PartMan v0.50 with a small library that detects both BBC_MicroBit and/or RPi_Pico when plugged into any USB-slot. The result is displayed on the PartMan window bars. To minimise the impact on existing v0.50 only 2 lines were added/changed in Runimage, all added stuff is inside new library ppExtras. Works fine on ARMX6 and Raspberry B, other machinery non checked. My version is at www.bigbenclub.nl/extras/partmgr50pp.zip Paul Porcelijn

Feb 28, 2021 10:22am Jon Abbott (1421) 2651 posts	PartMan outwitting FAT32FS I can’t speak for FAT32FS, as I’ve not looked at its source code. Partition Manager uses the official Microsoft method of detect FAT type as detailed in p15 of Microsoft Extensible Firmware Initiative FAT32 File System Specification v1.03 (Word Document) `If(CountofClusters < 4085) { /* Volume is FAT12 / } else if(CountofClusters < 65525) { / Volume is FAT16 / } else { / Volume is FAT32 */ }` This is however only shown in the PartMan logfile text Could you post the log files please, so I can see see why its not displaying in the volume view.

Feb 28, 2021 1:32pm Paul Porcelijn (8775) 10 posts	In this log file: SCSI 0:0 is HardDisc4, SCSI 0:1 is RPi_Pico (card inserted while its reset button was pressed) SCSI 0:2 is BBC_Microbit card Only the log file bottom part (marked off by asterisks) was added by my extension. OS Version=529 CDFS found SCSIFS found SDFS found read_drives =========== SCSIFS ------ SCSI 0:0 found LBA Size =512 Size in LBA =&00DF94BB0 D_Removable%=0 SCSI 0:1 found LBA Size =512 Size in LBA =&00003FFFF D_Removable%=128 SCSI 0:2 found LBA Size =512 Size in LBA =&00002007F D_Removable%=128 SDFS ---- SDFS 1 found LBA Size =512 Size in LBA =&000F07800 D_Removable%=-1 add_partitions_GPT ================== SCSI 0:0 checking for GPT partition table read_bytes_SCSIFS(0,&0,&0,..,&200) SCSI_Op,&0,10,READ,&200 Address : 0 1 2 3 4 5 6 7 8 9 A B C D E F &000000 : EB 3C 90 43 61 73 74 6C 65 00 00 00 02 00 00 00 .<.Castle....... &000010 : 00 00 00 00 00 00 00 00 3D 00 3D 00 00 00 00 00 ........=.=..... &000020 : AA F0 33 0E 00 00 00 00 00 60 32 4E 4F 20 4E 41 ..3......`2NO NA &000030 : 4D 45 20 20 20 20 20 20 20 20 20 20 20 20 FA 31 ME .1 &000040 : C0 8E D0 BC 00 7C FB 8E D8 E8 00 00 5E 83 C6 19 ............^... &000050 : BB 07 00 FC AC 84 C0 74 06 B4 0E CD 10 EB F5 30 .......t.......0 &000060 : E4 CD 16 CD 19 0D 0A 4E 6F 6E 2D 73 79 73 74 65 .......Non-syste &000070 : 6D 20 64 69 73 6B 0D 0A 50 72 65 73 73 20 61 6E m disk..Press an &000080 : 79 20 6B 65 79 20 74 6F 20 72 65 62 6F 6F 74 0D y key to reboot. &000090 : 0A 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ &0000A0 : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ &0000B0 : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ &0000C0 : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ &0000D0 : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ &0000E0 : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ &0000F0 : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ &000100 : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ &000110 : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ &000120 : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ &000130 : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ &000140 : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ &000150 : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ &000160 : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ &000170 : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ &000180 : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ &000190 : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ &0001A0 : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ &0001B0 : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ &0001C0 : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ &0001D0 : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ &0001E0 : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ &0001F0 : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 55 AA ..............U. add_partitions_MBR ================== SCSI 0:0 checking for MBR partition table read_bytes_SCSIFS(0,&0,&0,..,&200) SCSI_Op,&0,10,READ,&200 Address : 0 1 2 3 4 5 6 7 8 9 A B C D E F &000000 : EB 3C 90 43 61 73 74 6C 65 00 00 00 02 00 00 00 .<.Castle....... &000010 : 00 00 00 00 00 00 00 00 3D 00 3D 00 00 00 00 00 ........=.=..... &000020 : AA F0 33 0E 00 00 00 00 00 60 32 4E 4F 20 4E 41 ..3......`2NO NA &000030 : 4D 45 20 20 20 20 20 20 20 20 20 20 20 20 FA 31 ME .1 &000040 : C0 8E D0 BC 00 7C FB 8E D8 E8 00 00 5E 83 C6 19 ............^... &000050 : BB 07 00 FC AC 84 C0 74 06 B4 0E CD 10 EB F5 30 .......t.......0 &000060 : E4 CD 16 CD 19 0D 0A 4E 6F 6E 2D 73 79 73 74 65 .......Non-syste &000070 : 6D 20 64 69 73 6B 0D 0A 50 72 65 73 73 20 61 6E m disk..Press an &000080 : 79 20 6B 65 79 20 74 6F 20 72 65 62 6F 6F 74 0D y key to reboot. &000090 : 0A 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ &0000A0 : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ &0000B0 : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ &0000C0 : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ &0000D0 : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ &0000E0 : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ &0000F0 : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ &000100 : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ &000110 : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ &000120 : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ &000130 : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ &000140 : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ &000150 : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ &000160 : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ &000170 : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ &000180 : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ &000190 : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ &0001A0 : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ &0001B0 : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ &0001C0 : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ &0001D0 : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ &0001E0 : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ &0001F0 : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 55 AA ..............U. MBR partition table not valid add_partitions_FileCore ======================= Attempting to link SCSI 0:0 to a FileCore drive SCSI partitioning supported, using SCSIFS_Partitions to find the SCSIFS drive Trying SCSI 0:0.0 Found SCSI::4 DescribeDisc Address : 0 4 8 C &000000 : 003D3D09 02000E13 00200B01 82CA7701 .==....... ..w.. &000010 : F2970A00 6148674A 69446472 0D346373 ....JgHardDisc4. &000020 : 00000FCD 0000001B 00070102 00000001 ................ Checking SCSI::4 for FileCore Free=&15F5694000 OS Size in LBA=&00DF94B85 Valid FileCore disc found, disc name is: HardDisc4 SCSI::4 detected as: E+, Boot, Big map Full disc FileCore detected add_partitions_GPT ================== SCSI 0:1 checking for GPT partition table read_bytes_SCSIFS(1,&0,&0,..,&200) SCSI_Op,&1,10,READ,&200 Address : 0 1 2 3 4 5 6 7 8 9 A B C D E F &000000 : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ &000010 : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ &000020 : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ &000030 : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ &000040 : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ &000050 : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ &000060 : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ &000070 : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ &000080 : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ &000090 : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ &0000A0 : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ &0000B0 : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ &0000C0 : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ &0000D0 : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ &0000E0 : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ &0000F0 : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ &000100 : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ &000110 : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ &000120 : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ &000130 : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ &000140 : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ &000150 : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ &000160 : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ &000170 : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ &000180 : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ &000190 : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ &0001A0 : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ &0001B0 : 00 00 00 00 00 00 00 00 F0 86 A6 02 00 00 00 00 ................ &0001C0 : 00 00 0E 00 00 00 01 00 00 00 FF FF 03 00 00 00 ................ &0001D0 : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ &0001E0 : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ &0001F0 : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 55 AA ..............U. add_partitions_MBR ================== SCSI 0:1 checking for MBR partition table read_bytes_SCSIFS(1,&0,&0,..,&200) SCSI_Op,&1,10,READ,&200 Address : 0 1 2 3 4 5 6 7 8 9 A B C D E F &000000 : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ &000010 : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ &000020 : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ &000030 : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ &000040 : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ &000050 : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ &000060 : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ &000070 : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ &000080 : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ &000090 : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ &0000A0 : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ &0000B0 : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ &0000C0 : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ &0000D0 : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ &0000E0 : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ &0000F0 : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ &000100 : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ &000110 : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ &000120 : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ &000130 : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ &000140 : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ &000150 : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ &000160 : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ &000170 : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ &000180 : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ &000190 : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ &0001A0 : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ &0001B0 : 00 00 00 00 00 00 00 00 F0 86 A6 02 00 00 00 00 ................ &0001C0 : 00 00 0E 00 00 00 01 00 00 00 FF FF 03 00 00 00 ................ &0001D0 : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ &0001E0 : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ &0001F0 : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 55 AA ..............U. MBR partition table found Partition 0 ----------- Partition type=&E Start LBA =&000000001 Size in LBA =&00003FFFF Checking SCSI 0:1 partition 0 for FAT read_bytes_SCSIFS(1,&1,&0,..,&200) SCSI_Op,&1,10,READ,&200 FAT header ---------- Word : 0 1 2 3 4 5 6 7 8 9 000000 : 3CEB 4D90 5753 4E49 2E34 0031 0802 0001 0002 0002 .<.MSWIN4.1......... 000010 : F800 0081 0001 0001 0001 0000 FFFF 0003 0000 F029 ..................). 000020 : A686 5202 4950 522D 3250 2020 2020 4146 3154 2036 ...RPI-RP2 FAT16 000030 : 2020 FEEB 0000 0000 0000 0000 0000 0000 0000 0000 .................. 000040 : 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 .................... 000050 : 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 .................... 000060 : 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 .................... 000070 : 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 .................... 000080 : 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 .................... 000090 : 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 .................... 000100 : 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 .................... 000110 : 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 .................... 000120 : 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 .................... 000130 : 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 .................... 000140 : 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 .................... 000150 : 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 .................... 000160 : 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 .................... 000170 : 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 .................... 000180 : 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 .................... 000190 : 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 .................... 000200 : 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 .................... 000210 : 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 .................... 000220 : 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 .................... 000230 : 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 .................... 000240 : 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 .................... 000250 : 0000 0000 0000 0000 0000 0000 ............ add_partitions_GPT ================== SCSI 0:2 checking for GPT partition table read_bytes_SCSIFS(2,&0,&0,..,&200) SCSI_Op,&2,10,READ,&200 Address : 0 1 2 3 4 5 6 7 8 9 A B C D E F &000000 : EB 3C 90 4D 53 44 30 53 34 2E 31 00 02 08 01 00 .<.MSD0S4.1..... &000010 : 02 20 00 00 00 F8 41 00 01 00 01 00 00 00 00 00 . ....A......... &000020 : 80 00 02 00 00 00 29 74 19 02 27 44 41 50 4C 49 ......)t..'DAPLI &000030 : 4E 4B 2D 44 4E 44 46 41 54 31 36 20 20 20 FA B8 NK-DNDFAT16 .. &000040 : C0 07 05 20 01 8E D0 BC 00 10 B8 C0 07 8E D8 BE ... ............ &000050 : 6D 00 E8 0B 00 EB FE B4 0E B7 00 B3 07 CD 10 C3 m............... &000060 : 8A 04 46 08 C0 74 05 E8 ED FF EB F4 C3 50 4C 45 ..F..t.......PLE &000070 : 41 53 45 20 52 45 4D 4F 56 45 20 54 48 45 20 41 ASE REMOVE THE A &000080 : 52 4D 20 4D 42 45 44 20 44 41 50 4C 49 4E 4B 20 RM MBED DAPLINK &000090 : 55 53 42 20 44 45 56 49 43 45 20 41 4E 44 20 52 USB DEVICE AND R &0000A0 : 45 42 4F 4F 54 20 54 48 45 20 53 59 53 54 45 4D EBOOT THE SYSTEM &0000B0 : 2E 2E 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ &0000C0 : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ &0000D0 : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ &0000E0 : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ &0000F0 : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ &000100 : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ &000110 : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ &000120 : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ &000130 : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ &000140 : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ &000150 : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ &000160 : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ &000170 : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ &000180 : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ &000190 : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ &0001A0 : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ &0001B0 : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ &0001C0 : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ &0001D0 : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ &0001E0 : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ &0001F0 : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 55 AA ..............U. add_partitions_MBR ================== SCSI 0:2 checking for MBR partition table read_bytes_SCSIFS(2,&0,&0,..,&200) SCSI_Op,&2,10,READ,&200 Address : 0 1 2 3 4 5 6 7 8 9 A B C D E F &000000 : EB 3C 90 4D 53 44 30 53 34 2E 31 00 02 08 01 00 .<.MSD0S4.1..... &000010 : 02 20 00 00 00 F8 41 00 01 00 01 00 00 00 00 00 . ....A......... &000020 : 80 00 02 00 00 00 29 74 19 02 27 44 41 50 4C 49 ......)t..'DAPLI &000030 : 4E 4B 2D 44 4E 44 46 41 54 31 36 20 20 20 FA B8 NK-DNDFAT16 .. &000040 : C0 07 05 20 01 8E D0 BC 00 10 B8 C0 07 8E D8 BE ... ............ &000050 : 6D 00 E8 0B 00 EB FE B4 0E B7 00 B3 07 CD 10 C3 m............... &000060 : 8A 04 46 08 C0 74 05 E8 ED FF EB F4 C3 50 4C 45 ..F..t.......PLE &000070 : 41 53 45 20 52 45 4D 4F 56 45 20 54 48 45 20 41 ASE REMOVE THE A &000080 : 52 4D 20 4D 42 45 44 20 44 41 50 4C 49 4E 4B 20 RM MBED DAPLINK &000090 : 55 53 42 20 44 45 56 49 43 45 20 41 4E 44 20 52 USB DEVICE AND R &0000A0 : 45 42 4F 4F 54 20 54 48 45 20 53 59 53 54 45 4D EBOOT THE SYSTEM &0000B0 : 2E 2E 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ &0000C0 : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ &0000D0 : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ &0000E0 : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ &0000F0 : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ &000100 : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ &000110 : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ &000120 : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ &000130 : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ &000140 : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ &000150 : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ &000160 : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ &000170 : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ &000180 : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ &000190 : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ &0001A0 : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ &0001B0 : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ &0001C0 : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ &0001D0 : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ &0001E0 : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ &0001F0 : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 55 AA ..............U. MBR partition table found Unallocated block ----------------- P_Start_LBA_Low%=&1 P_Start_LBA_High%=&0 P_Size_In_LBA_Low%=&2007E P_Size_In_LBA_High%=&0 add_partitions_GPT ================== SDFS 1 checking for GPT partition table read_bytes_SDFS(3,&0,&0,..,&200) SDFS_DiscOp64 drive=1 high=&0 low=&0 Address : 0 1 2 3 4 5 6 7 8 9 A B C D E F &000000 : EB 3C 90 43 61 73 74 6C 65 00 00 00 02 00 00 00 .<.Castle....... &000010 : 00 00 00 00 00 00 00 00 0D 00 13 00 00 00 00 00 ................ &000020 : F8 1F FD 00 00 00 00 00 00 60 32 4E 4F 20 4E 41 .........`2NO NA &000030 : 4D 45 20 20 20 20 20 20 20 20 20 20 20 20 FA 31 ME .1 &000040 : C0 8E D0 BC 00 7C FB 8E D8 E8 00 00 5E 83 C6 19 ............^... &000050 : BB 07 00 FC AC 84 C0 74 06 B4 0E CD 10 EB F5 30 .......t.......0 &000060 : E4 CD 16 CD 19 0D 0A 4E 6F 6E 2D 73 79 73 74 65 .......Non-syste &000070 : 6D 20 64 69 73 6B 0D 0A 50 72 65 73 73 20 61 6E m disk..Press an &000080 : 79 20 6B 65 79 20 74 6F 20 72 65 62 6F 6F 74 0D y key to reboot. &000090 : 0A 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ &0000A0 : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ &0000B0 : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ &0000C0 : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ &0000D0 : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ &0000E0 : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ &0000F0 : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ &000100 : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ &000110 : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ &000120 : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ &000130 : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ &000140 : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ &000150 : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ &000160 : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ &000170 : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ &000180 : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ &000190 : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ &0001A0 : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ &0001B0 : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ &0001C0 : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ &0001D0 : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ &0001E0 : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ &0001F0 : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 55 AA ..............U. add_partitions_MBR ================== SDFS 1 checking for MBR partition table read_bytes_SDFS(3,&0,&0,..,&200) SDFS_DiscOp64 drive=1 high=&0 low=&0 Address : 0 1 2 3 4 5 6 7 8 9 A B C D E F &000000 : EB 3C 90 43 61 73 74 6C 65 00 00 00 02 00 00 00 .<.Castle....... &000010 : 00 00 00 00 00 00 00 00 0D 00 13 00 00 00 00 00 ................ &000020 : F8 1F FD 00 00 00 00 00 00 60 32 4E 4F 20 4E 41 .........`2NO NA &000030 : 4D 45 20 20 20 20 20 20 20 20 20 20 20 20 FA 31 ME .1 &000040 : C0 8E D0 BC 00 7C FB 8E D8 E8 00 00 5E 83 C6 19 ............^... &000050 : BB 07 00 FC AC 84 C0 74 06 B4 0E CD 10 EB F5 30 .......t.......0 &000060 : E4 CD 16 CD 19 0D 0A 4E 6F 6E 2D 73 79 73 74 65 .......Non-syste &000070 : 6D 20 64 69 73 6B 0D 0A 50 72 65 73 73 20 61 6E m disk..Press an &000080 : 79 20 6B 65 79 20 74 6F 20 72 65 62 6F 6F 74 0D y key to reboot. &000090 : 0A 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ &0000A0 : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ &0000B0 : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ &0000C0 : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ &0000D0 : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ &0000E0 : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ &0000F0 : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ &000100 : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ &000110 : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ &000120 : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ &000130 : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ &000140 : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ &000150 : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ &000160 : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ &000170 : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ &000180 : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ &000190 : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ &0001A0 : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ &0001B0 : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ &0001C0 : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ &0001D0 : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ &0001E0 : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ &0001F0 : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 55 AA ..............U. MBR partition table not valid add_partitions_FileCore ======================= Attempting to link SDFS 1 to a FileCore drive Found SDFS::1 DescribeDisc Address : 0 4 8 C &000000 : 00130D09 02000A13 00209401 23012E01 .......... ....# &000010 : E0EFDA00 7953C67E 6D657473 20393235 ......System529 &000020 : 00000FCD 00000001 00070100 00000001 ................ Checking SDFS::1 for FileCore Free=&173067400 OS Size in LBA=&000F077ED Valid FileCore disc found, disc name is: System529 SDFS::1 detected as: E+, Boot, Big map Full disc FileCore detected * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * Check SCSI:1 sector 300 for RPI-RP2 read_bytes_SCSIFS(1,&12C,&0,..,&200) SCSI_Op,&1,10,READ,&200 Address : 0 1 2 3 4 5 6 7 8 9 A B C D E F &00025800 : 55 46 32 20 42 6F 6F 74 6C 6F 61 64 65 72 20 76 UF2 Bootloader v &00025810 : 31 2E 30 0A 4D 6F 64 65 6C 3A 20 52 61 73 70 62 1.0.Model: Raspb &00025820 : 65 72 72 79 20 50 69 20 52 50 32 0A 42 6F 61 72 erry Pi RP2.Boar &00025830 : 64 2D 49 44 3A 20 52 50 49 2D 52 50 32 0A 00 00 d-ID: RPI-RP2... &00025840 : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ RPi_Pico detected Check SCSI:2 sector 0 for DAPLINK read_bytes_SCSIFS(2,&0,&0,..,&200) SCSI_Op,&2,10,READ,&200 Address : 0 1 2 3 4 5 6 7 8 9 A B C D E F &00000000 : EB 3C 90 4D 53 44 30 53 34 2E 31 00 02 08 01 00 .<.MSD0S4.1..... &00000010 : 02 20 00 00 00 F8 41 00 01 00 01 00 00 00 00 00 . ....A......... &00000020 : 80 00 02 00 00 00 29 74 19 02 27 44 41 50 4C 49 ......)t..'DAPLI &00000030 : 4E 4B 2D 44 4E 44 46 41 54 31 36 20 20 20 FA B8 NK-DNDFAT16 .. &00000040 : C0 07 05 20 01 8E D0 BC 00 10 B8 C0 07 8E D8 BE ... ............ BBC_MicroBit detected Ouch.. Log file conclusions were wrong way around. “BBC-Microbit” and “RPi Pico” were swapped. I have immediately updated my extension..

Mar 1, 2021 5:17am Jon Abbott (1421) 2651 posts	Neither have a partition table, so it’s marking them as unpartitioned/unformatted. I need to rework the format detection code to handle unpartitioned drives and mark the drive as read only. Unrelated, but I coded up initialising FAT partitions yesterday. I just need to give it a second pass to add in all the error handling, handle 4K sectors, allow manual forcing of FAT16/32 and limit the partition size accordingly.

Mar 1, 2021 1:00pm Andrew Rawnsley (492) 1445 posts	Jon – going back to your “wondering” of the 23rd, about replacing filecore etc, this topic surfaced again during the last ROD/ROOL meeting. There was no love for filecore in this regard on either side, and the thinking was that replacing it (or perhaps adding something new alongside) seemed a perfectly valid approach going forwards. The general goal will be to remove the 8 drive limit, allow for large drives and support partitions, but since doing this is bound to break the current system in terms of backwards compatibility, I don’t think anyone is particularly wedded to the idea of stretching the old tech even further, when something else might work far better. The main proviso is that RISC OS metadata (filetypes, datestamps, access details etc) need to work seemlessly, as do existing SWIs, to ensure broad software compatibility. By way of example, whilst many things work from FAT32FS, quite a few things don’t, because they’re doing things expecting filecore-y responses. Any replacement would need to be as seemless as possible in that regard (although I understand that some SWIs may impose limits such as number of bits allocated which could pose real problems when dealing with larger discs and more of them). The real problem is that going forward, storage needs someone with a very clear head (vision) to come up with a best approach. The idea that 1 disc = 1 drive = 1 icon is very 1980s, and in an era of Storage pools, RAID, JBOD, ZFS and journaling file systems, someone needs to have a coherent vision for a next-gen RISC OS filesystem.

Mar 1, 2021 1:23pm Paul Porcelijn (8775) 10 posts	The RPi_Pico FAT partition being read-only is not obvious. There is no standard FAT marking for this feature. Can only be deduced from its product-ID in the partition’s first sector (=in sector 300). The other way to find out is by trying: any FAT write will fail. But that’s risky! RPi_Pico’s FAT front is in fact a hardware facade to facilitate easy file-uploading to its 16Mbit (=2MB) program flash. Any upload is auto-checked for valid UF2-format, but this is no full guaranty against incidental flashing..

Mar 19, 2021 3:58pm André Timmermans (100) 655 posts	Got a new 4TB Seagate drive today. Thought I’d play with it on the PI first. For some reason Fat32Format sees only 2047GB, after some reflection it might be due trying to define it as an MBR partition. Got on the Raspbian side, used GPart to format it as FAT32. It reserved the whole disc as a single partition with 2047GB used by FAT32 and the rest unused ??! Ok, changed that to 2 FAT32 partitions. Checked on a PC Laptop. The 2 partiions are OK. Back on RISC OS. Fat32FS does not see them (no GPT support I presume) and PartMgr sees the drive as GPT 2047GB with 2 partions: Basic 1870GB and Unallocated 177GB. Finally I checked with *scsi:devices the drive is reported as 2048GB. Seems like the SCSI and/or USB driver modules need a little update to support 64-bit LBA.

Mar 19, 2021 6:38pm David J. Ruck (33) 1635 posts	FAT32 is limited to 2TB, so that’s why you can’t format to greater than 2047GB. You could create a 4TB ext4 partition, but that wouldn’t be much good for RISC OS.

Mar 19, 2021 8:17pm Steffen Huber (91) 1953 posts	FAT32 is limited to 2TB I think the limit depends on sector size, so with 4kiB sectors (not unusual on 4 TB drives), it should be 16 TiB? Fat32FS and its tools on the other hand…might only work with 512 byte sectors. And/or have different limits. They have to cope with Filecore’s 256GiB limit and IIRC they “fake” larger discs by using pseudo-partitions and corresponding sector offsets. Obviously I forgot most details I once knew…maybe Jeff can provide the details.

Mar 21, 2021 12:12pm Raik (463) 2061 posts	Ok, changed that to 2 FAT32 partitions. Checked on a PC Laptop. The 2 partiions are OK. Have you try to mount the second partition manually like the description in the help/readme file? For me it was working with a 4TB HDD but can not try because it is placed since any month in my NAS and formated to NTFS.

Mar 21, 2021 12:47pm André Timmermans (100) 655 posts	Have you try to mount the second partition manually like the description in the help/readme file? For me it was working with a 4TB HDD but can not try because it is placed since any month in my NAS and formated to NTFS. No, since it was done via GPT, I could no even access the first one. I have since reformatted the drive to exFat, moved the content of a 2TB one to it, formatted that one to FAT and moved my DVD backups to it so that I can test them with KinoAmp. Of course I was interrupted has I was about to format the drive and distracted ended up formatting the wrong drive, so I am know trying to remember 15 evenings worth of tests and bug-fixes since my last backup of the KinoAmp sources :-(

Mar 22, 2021 7:05am Jon Abbott (1421) 2651 posts	Back on RISC OS. Fat32FS does not see them (no GPT support I presume) Use the PartMan Modules from this post to access FAT based GPT partitions. I think the limit depends on sector size, so with 4kiB sectors (not unusual on 4 TB drives), it should be 16 TiB? FAT32 is “interesting”. It’s technical limit is 2TB for 512 byte sectors, there are however reasons why you would not want to go beyond 32GB due to the cluster size (space used for each file) getting too large. I don’t have the figures to hand, but for a 2TB partition, off the top of my head the cluster size is going to be 256KB. You can probably x8 that for 4Kn drives. Quite a few of FAT’s variables are specified in KB, instead of sectors, so I’m not 100% sure at this point how it’s going to react to 4Kn drives. I’ve certainly added the relevant alignment code for 512e when formatting, but haven’t tested with 4Kn as I don’t have a suitable drive to hand. Progress update. I have MBR/GPT partitioning coded, FileCore format and FAT16 are working. There’s an issue with FAT32 formatting I need to resolve and I need to go back and double check all the 512e/4Kn alignment is correct. I’m aiming to have a test release public in April.

Apr 16, 2021 8:42pm Jon Abbott (1421) 2651 posts	0.63 is now available, which adds MBR and GPT partition initialisation, volume creation, FAT and FileCore formatting. Due to the limited amount of testing, avoid using it with any critical drives attached. The Debug log is off by default to avoid any potential issues with writes to the filesystem whilst its formatting. To turn it on, edit !RunImage and set DEBUG%=TRUE. I would advise running it from RAM: when generating a debug log.

Apr 17, 2021 11:42am David J. Ruck (33) 1635 posts	Just tried it, and pressed cancel on the Format dialog which resulted in an Abort on Data Transfer at &FC1AF98C (offset &00005E1C in module ‘BASIC’ )in “Wimp Library” at line 252. Not reproducible though.

Apr 18, 2021 8:05am Jon Abbott (1421) 2651 posts	Just tried it, and pressed cancel on the Format dialog which resulted in an Abort on Data Transfer &FC1AF98C (offset &00005E1C in module ‘BASIC’ )in “Wimp Library” at line 252. Not reproducible though. Thanks for the feedback. If you find the right series of steps to produce it reliably, please let me know. EDIT: I’ve managed to reproduce it. Set the ALU size, then click Cancel. I’ll investigate

Apr 18, 2021 9:17am Jon Abbott (1421) 2651 posts	0.64 is now available, which fixes the bug reported by David above. It turned out to be an “off by 1” error causing a buffer overrun.

Apr 18, 2021 9:25am Martin Avison (27) 1494 posts	Found a bug on v0.63 … was posting and saw v0.64 … but it still has the bug: `10:20:19.66 WimpError from Partition Manager Error : &0000001D Message: No such function/procedure in "FS.ADFS" at line 121` That line is `121 IF DEBUG% THEN IF (FNword(data%) AND (1<<15))=0 THEN PROCdebug_text("Magnetic media based drive") ELSE PROCdebug_text("Flash based drive")` but when DEBUG%= FALSE the ELSE is executed, and the Debug library has not been included where the PROC resides.

Apr 18, 2021 3:55pm Jon Abbott (1421) 2651 posts	Thanks for the report Martin, I’ll fix it in the next release. The line should be: `IF DEBUG% THEN IF (FNword(data%) AND (1<<15))=0 THEN PROCdebug_text("Magnetic media based drive") ELSE IF DEBUG% THEN PROCdebug_text("Flash based drive")`

Apr 18, 2021 7:36pm Jon Abbott (1421) 2651 posts	0.65 is now available, which fixes the bug reported by Martin above. I’ve also moved the Format libraries to OVERLAY’s and reduced the app footprint from 512K to 350K. Next on the list are QoL improvements, such as: Add a menu option to refresh the drive info Add a menu option to backup the partition table Detect and refresh when drives are inserted/removed Removing the reliance on FileCore to read FileCore partition info Version info Dismounting drives before they’re modified Eject/Inject after partition changes I’m not sure how to do the last point as not all Filesystems support software triggered eject/inject. Short of RMReIniting FileCore and/or Filesystems, it might need development on the OS side.

Apr 19, 2021 6:01am David J. Ruck (33) 1635 posts	Please can we have an info item on the menu, regardless of where on the window the menu is opened. Or have an iconbar icon and menu with info on. I had a copy running for a few days, and there was no way of telling what version it was.

Apr 19, 2021 7:32am John WILLIAMS (8368) 493 posts	Please can we have an info item… I second the idea in principle, but suggest, as the application quits when its window closes and there is no main menu, that the version number goes in the titlebar. This would also be the easiest to implement!

Apr 28, 2021 4:00am Raik (463) 2061 posts	Sorry for the delay. I’m busy with non RISC OS things. Thanks for your work. Have try V0.65 and only the device detection at this time. “PartMan-Device” gives "Unkown or missing variable in “Partitions.GPT” and PartMgr is gone. In an earlier version it was detected. Remove the GPT device. As I wrote in an earlier post, I use an 500GB device. First partiton is FileCore and detected correct. Also the size of the device. Second partition is FAT32 made with Antons partiFC. I mount with somithing like “fat32fs:mount -fp2 :15 { > null: }” and is working without problems on Titanium (RISC OS and Linux). The second FAT32 partition is not detected by PartMgr.