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

[Thomas]

Change MaxTransfer to oxfe00 in the ZIP mountlist.

Bye,
Thomas

[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

[Thomas]

Workbench and the AmigaDOS Copy command and probably also DOpus4 use very small buffers and therefore do small reads on the drive.

DOpus5 is optimised for speed and uses large buffers so the read sizes can exceed the possible maximum transfer chunks on big files. Reducing MaxTransfer below this size will prevent the filesystem from reading more than possible in one go.

The possible MaxTransfer value depends on the controller and the drive. 64kb is small enough for all possible drives and controllers.

Bye,
Thomas

[lempkee]

hmm i didnt know ... , is this why my cdrom can't un lha /lzx on the fly aswell ??  if i do  i get heaps of errors ( from cd to hdd/ram )

(in dopus mag)

[Thomas]

Maybe. Just try to change the MaxTransfer value in the CD0 mountlist either. If it helps, you now know the reason.

Bye,
Thomas

[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

[Cymric]

Are you sure your system memory is working okay? I remember I got mysterious compression errors too, and could lay the blame at a faulty SIMM. Replace the memory and see what happens.

As to your question about the mountlist: it contains information about the type of thing you want to mount, but which the device is unable to supply for itself. Floppy drives come to mind. In many cases, you don't need all the things listed in the mountlist you posted. However, you can achieve very funny effects with them. For example, you can make a copy of this mountlist, then change both so that their LowCyl/HighCyl entries read

LowCyl = 0
HighCyl = 1444

and

LowCyl = 1445
HighCyl = 2890

If you save both under a different name (say ZIP0 and ZIP1), you can mount them both, using the same ZIP-disk. In other words, you now have two file systems on a single physical disk. You can format them, copy files between them, and so on... Quite funny to try that. Make sure you use an old ZIP-disk for this experiment, and issue a 'format ZIP0:' and 'format ZIP1:' before use. You can assign a different filing system to ZIP1 too if you like.

[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

[Thomas]

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 ?

Don't get confused. I used mountlist as a synonym for dosdriver. Actually a dosdriver and a mountlist contains the same: a description of a DOS device. While a dosdriver contains only one device whose name is given by the file name, the mountlist can contain multiple device entries with the name given in the list. The mount command first searches the devs/dosdrivers directory for a file with the given name and then searches the mountlist for an entry with the name.
Dosdrivers are easier to handle. You can activate and move them from the Workbench and you can use Workbench's info menu to change attributes. The mountlist is compatible to OS 1.3 and below.

Bye,
Thomas

[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