Welcome, Guest. Please login or register.

Author Topic: Odd filecopy behavior fixed by smart workaround. Suggestions welcome...  (Read 1198 times)

Description:

0 Members and 1 Guest are viewing this topic.

Offline LPTopic starter

  • Sr. Member
  • ****
  • Join Date: Jan 2003
  • Posts: 358
    • Show only replies by LP
    • http://bailout.dk
Hi there guys and girls!

In one of my  Previous threads I had a wierd error when copying files from the AmigaOS 3.9 CD to my HD...

I finally found a fix for this problem...

And it was damn strange but worked in the end...

Please refer to my Previous thread.

I tried to copy the mentioned files: Input, Locale and Screenmode continual times but no luck, tried to copy to floppy and then back to HD without luck...

Then I tried to make LHA add an archive with the files in, and then extract them to my HD, and check this out: IT WORKED!
The files weren't corrupted any more...

So if any of you have a good idea on why this "fix" works, I'd like to hear it...

 

Offline Ilwrath

Re: Odd filecopy behavior fixed by smart workaround. Suggestions welcome...
« Reply #1 on: October 26, 2003, 07:05:09 PM »
I think Amiga1260 was right.  MaxTransfer bug.  Had it on my A1200.  Different files, but same behavior.  My 1.3 kickstart image would constantly corrupt as soon as it was written to the drive.  Storing it in an LHA worked fine, though.  Fixed MaxTransfer settings, could copy the file without it corrupting.
 

Offline Thematic

  • Jr. Member
  • **
  • Join Date: Aug 2003
  • Posts: 69
    • Show only replies by Thematic
Re: Odd filecopy behavior fixed by smart workaround. Suggestions welcome...
« Reply #2 on: October 26, 2003, 07:24:02 PM »
Quote
Then I tried to make LHA add an archive with the files in, and then extract them to my HD


It worked because lha used a sufficiently small buffer when extracting & writing the files.
When encountering this phenomenon when maxtransfer can't readily be altered, one
option is to use the shell command 'copy', with a parameter like BUFFER=60000
I think the default is 65536, but only when the device(s) being used do not specify something instead.
So you have the strings in your palm. Do you know what they are for?