Partition Manager feedback

[JonAbbott]

SD card in slot 1 of card reader: Still not recognised.

As mentioned previously, I've not figured out how to support Mass Storage Class devices yet so only the first LUN will be recognised.

PartMgr is now closing all open Filer windows on SSD4 when run

Sorry about that, its fixed in today's build.

I had previously opened a Filer window on the (now-deleted) FAT32 partition on the SD card in the card reader, and on clicking the drive icon this (presumably still-cached) directory display reappeared. Is this to be expected?

It probably depends on how the FAT partition was opened. When a FAT32FS mounted partition is deleted, PM will attempt to dismount it - but only if it was previously mounted by FAT32FS before PM was loaded.

FAT mounted via an Image filesystem through a linked file will still appear to work if the linked file isn't deleted (ie !Boot.Loader).

FAT drives mounted via an Image filesystem might also still work as PM can't determine the drive is mounted, so can't notify the filesystem that it's been deleted.

[paintings]

its fixed in today's build.

That's much better, thanks.

When a FAT32FS mounted partition is deleted, PM will attempt to dismount it - but only if it was previously mounted by FAT32FS before PM was loaded.

That doesn't quite square with what I'm seeing.

Sequence of events is:
1. Insert SD card reader with 32GB SD card in slot 0. This appears as drives :0 and :1.
2. Click on the icon for drive :0. A Fat32FS directory window opens.
3. Close the Fat32FS directory window.
4. Start PartMgr.
5. Use PartMgr to delete the FAT32 partition on the SD card in slot 0 of the card reader.
6. Close PartMgr.
7. Click on the icon for drive :0. A Fat32FS directory window opens (contents identical to that in step 2).
Files inside the Fat32FS window can still be accessed, and traversing the directory tree is still possible (this is no great surprise as only the partition entry in the MBR would have been zapped: the original contents of the partition are still on the SD card). Copying a file to the partition seems to work, but as the partition has been deleted this is of little practical benefit.
Explicitly dismounting :0 does work as expected: the drive then responds "Disc not understood".
Log file "fat32SD.txt" attached.

[JonAbbott]

When a FAT32FS mounted partition is deleted, PM will attempt to dismount it - but only if it was previously mounted by FAT32FS before PM was loaded.

That doesn't quite square with what I'm seeing.

Try the build I've just uploaded.

With the 4 in 1 attached and no card in the first slot, could you grab the output from the tests below please:

Code: Select all

SYS "XSCSI_Initialise",2,0,&10000 TO ;E%
PRINT E%
*MEMORY B 10000+10
SYS "XSCSI_Initialise",3,0,&10000,64 TO ;E%
PRINT E%
*MEMORY B 10000+40 

[paintings]

Try the build I've just uploaded.

Yes the FAT32 partition is now dismounted properly.

With the 4 in 1 attached and no card in the first slot, could you grab the output from the tests below please:

I'll have a go at posting the results inline. I think I managed to select ISO8859-1 encoding...

Code: Select all

         2

Address  :  0  1  2  3  4  5  6  7  8  9  A  B  C  D  E  F  0  1  2  3  4  5  6  7  8  9  A  B  C  D  E  F :            ASCII Data
00010000 : 00 00 06 02 47 00 00 00 FF 7F F9 0D 00 02 00 00                                                 : ....G...ÿ.ù.....
         2

Address  :  0  1  2  3  4  5  6  7  8  9  A  B  C  D  E  F  0  1  2  3  4  5  6  7  8  9  A  B  C  D  E  F :            ASCII Data
00010000 : 00 00 06 02 47 00 00 00 FF 7F F9 0D 00 02 00 00 69 62 72 61 72 79 0D 00 02 04 0D 00 03 13 DD 20 : ....G...ÿ.ù.....ibrary........Ý 
00010020 : F2 77 69 6D 70 5F 68 61 6E 64 6C 65 72 0D 00 04 49 20 20 EA 20 70 6F 6C 6C 25 2C 72 65 61 73 6F : òwimp_handler...I  ê poll%,reaso

[JonAbbott]

I'll have a go at posting the results inline. I think I managed to select ISO8859-1 encoding...

I'm really sorry, could you try that again, I forgot to put the buffer size on the SCSI_Initialise 3 line

[paintings]

I'm really sorry, could you try that again, I forgot to put the buffer size on the SCSI_Initialise 3 line

Here you go.

Code: Select all

         2

Address  :  0  1  2  3  4  5  6  7  8  9  A  B  C  D  E  F  0  1  2  3  4  5  6  7  8  9  A  B  C  D  E  F :            ASCII Data
00010000 : 00 00 06 02 47 00 00 00 FF 7F F9 0D 00 02 00 00                                                 : ....G...ÿ.ù.....
         2

Address  :  0  1  2  3  4  5  6  7  8  9  A  B  C  D  E  F  0  1  2  3  4  5  6  7  8  9  A  B  C  D  E  F :            ASCII Data
00010000 : 30 3A 30 2E 30 20 20 44 69 72 65 63 74 2D 61 63 63 65 73 73 20 20 20 20 20 20 31 31 32 20 47 62 : 0:0.0  Direct-access      112 Gb
00010020 : 79 74 65 73 20 41 53 4D 54 20 20 20 20 20 32 31 30 35 20 20 20 20 20 20 20 20 20 20 20 20 20 00 : ytes ASMT     2105             .

[JonAbbott]

SD card in slot 1 of card reader: Still not recognised.

Could you try the current build and upload the debug log please.

[paintings]

Could you try the current build and upload the debug log please.

This time SCSI 0:1:1 appeared in the list of drives, and the FAT32 volume on the drive appeared in the list of volumes.

Looking good. As far as I can see, all the bugs I reported have now been fixed.

Debug log attached just in case.

[JonAbbott]

This time SCSI 0:1:1 appeared in the list of drives, and the FAT32 volume on the drive appeared in the list of volumes.

Perfect, now please confirm the build I've just uploaded finds it.

[paintings]

Perfect, now please confirm the build I've just uploaded finds it.

Yes it's still there.