keldon85 wrote:Hi, just double checking the logistics here...
... and why not ?
keldon85 wrote:Situation
I have an MPC3000, external Zip100 for the MPC and an internal Zip100 for the PC.
Pretty standard affair.
Discussed MANY times on this MPC-FORUM and the one at YAHOO GROUPS.
keldon85 wrote:I have two Zip disks; DISK_A - formatted by the MPC with xx partitions,
DISK_A is a native formatted MPC3000 disk.
keldon85 wrote:and DISK_B - formatted using MPC editor.
DISK_B contains a "single, safe and cross platform transfer partition of 32 megabytes"
keldon85 wrote:DISK_A is not visible by the PC, but
... because an MPC3000 disk with any OS lower than Vailixi doesn't create a regular disk format/partition structure that can be accessed by a computer.
In some cases the first partition can be seen with some operating systems systems.
Access to this partition can be a little problematic though.
keldon85 wrote:DISK_B is visible in both the PC and the MPC but seems to be limited to around 8MB (or possibly a file count).
The "single, safe and cross platform transfer partition of 32 megabytes" will not necessarily be fully usable.
512 files per root of partition limit.
The 512 files per root of partition limit will be reduced if you are using a Windows machine and the and an appropriate registry entry is not set.
IE: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FileSystem
The entry in this regard being "Win31Filesystem".
In this case where such a registry entry is not applied.
Windows will write LFN directory entries.
IE: A double sized directory entry.
Effectively reducing the files per root of partition limit to 256.
So.
A combination of a reduced directory entry count and lots of small files may limit the apparent partition size to an amount seemingly less than 32 megabytes.
IE: The partition is still 32 megabytes in size but you won't actually be able to fill it up.
keldon85 wrote:The windows partition editor (in Disk Management) can not delete DISK_B partitions but can delete DISK_A partitions!.
Where DISK_A is concerned. Windows is not seeing a valid MBR/PARTITION/FILE SYSTEM.
So in this case the Disk Manager functions as normal.
Where DISK_B is concerned.
This is a M$ limitation.
On a PC running any operating M$ system from Windows NT and higher the following M$ restrictions on removable media ( CF, ZIP, JAZ, SYQUEST, etc ) apply:
_____________________________________________________________
From M$ KB:Article ID : 254109
You cannot use the Disk Management snap-in to create or delete partitions on removable storage media, such as tapes and optical disks. Such media either do not require partitioning, or should contain only one partition. Using more than one partition confuses the Removable Storage service.
_____________________________________________________________
From M$ KB:Article ID : 300415
You cannot use Diskpart to create a partition on removable media. Windows supports at most one MBR partition on removable media. If the media is manufactured with an MBR, that MBR cannot be altered, but the MBR is followed even if multiple partitions or logical drives are configured. If the media is manufactured without an MBR, the media is treated as a "superfloppy" and no partition structure is written to the media.
_____________________________________________________________
Plenty more examples can be found regarding "removable media issues" within the M$ knowledge base.
I have expressed how "lame" of M$ this limitation is.
As have others.
keldon85 wrote:I have no intention of upgrading to Valaxi and am using the latest OS disk update from Rohan.
Well, I Rohan say then; enjoy your free ride and keep on enjoying my old 3.16 floppy boot release that was released years ago.
keldon85 wrote:Working approach
I transfer files from the PC to DISK_B, which I then load into the MPC and some times archive into DISK_A in one of the partitions.
Sounds like the usual approach to me.
keldon85 wrote:Question
- Is there a file count limit to the partitions
Yes.
512 root of partition file limit unless reduced as discussed already in my reply.
keldon85 wrote: - Is there supposed to be a file/size limit to DISK_B access as described?
It's a 32 megabyte partition.
Size of files.
Number of files in root of partition.
Number of directory entries available within the root of partition.
All points need to be considered.
keldon85 wrote: - Are my current actions correct/incorrect (i.e. should I be using the MPC to format Zip disks, and applying my given working approach)?
I'll go with correct.
Check out the appropriate Windows registry entry as described above.
Usual "at your own risk precautions apply" where registry editing is concerned.
Rohan.
