copy under magellan

[lionstorm]

Hi all,
I still have a problem with dopus magellan2 5.82. I use to transfer files from an internal ZIP IDE drive (PC formatted, use FAT95 as filesystem) to my HD (amigaOS3.9 BB2).
If I copy an lha file from the zip to the HD under dopus4 or WB, no problem everything is fine. If I do it under magellan, the lha file is corrupted on the HD. So my question is do I have a problem with the internal copy command of magellan ? I doubt it is something to do with lha itself since I have only one version on my whole HD.
How to explain and how to change that so that I dont fear anymore to transfer files under magellan ?
Lio

[lionstorm]

Thanks Thomas.
Could you tell me more about it ? Why would it work under WB or Dopus4 and failed under Magellan if they all use the same Zip driver ??
Lio

[lionstorm]

Thanks for this explaination but it does not necesseraly occur on large files : I had a compressed lha of 300Kb and get corrupted.
Anyway here is the zip driver description :
* PC-IBM ZIP-Disk Mountlist
 *
 */

Flags           = 0
FileSystem      = L:fat95
Surfaces        = 1
BlocksPerTrack  = 68
Reserved        = 0
PreAlloc        = 0
Interleave      = 0
LowCyl          = 0
HighCyl         = 2890
Buffers         = 100
BufMemType      = 1
MaxTransfer     = 0x00ffffff
Mask            = 0xffffffff
DosType         = 0x46415401
GlobVec         = -1
StackSize       = 8192
Mount           = 1
BootPri         = 0
Priority        = 10

/* The Device and Unit fields are controlled
 * by tooltypes in the icon.
 *
 * Device       = scsi.device
 * Unit         = 5
If I get it, I change here the maxtransfer to oxfe00 ?

Now I have another question : my mountlist contains only a description for virtual floppy drives directed by fms and everything else is provided by drivers in devs or storage.
AFAIK to mount something, you need the driver and the handler so what the mountlist usefull for ?
Lio

[lionstorm]

good question about memory. I am getting in trouble with my 64Mb ram not recognised sometimes, only 3years old whereas my even older 32Mb still works like a charm.
Lio

[lionstorm]

tried 0xfe00 but I got a complain about the driver. I tried another setup (which I do not remember right now cause I am a t work). I thought problem was gone but no, I trasnfer zip files yesterday and they are corrupted.
Thomas : is oxfe00 (is it the letter o or zero) exactly what I should write or does it miss a few f ?
Lio