Yokemate of Keyboards
Posts: 2096 from 2003/2/24
From: po-RNO
Quote:
Cool_amigaN wrote:
Both of my current Work (75GB) and SYS partitions (5GB) are heavily modified and full of programs (which I refuse to start installing again from scratch after halfa decade of setups! :)). G4 is connected properly to an external Seagate NAS (NTFS format) - I also have a NEC usb 2.0 card but it falls when copying large amount of data, so copying via USB is out of question. Also, I don't want to mess with hardware deviations such as IDe to SATA connectors in order to move the files from G4 to G5.
With that much data I'd think it would be the easiest to either connect your G4 HD to G5 and copy then, or have an extra HD which you could use for transfer if you don't dare to move the original HD. I don't know about your connectors if I'd need any adapters. In any case use SFS or other Amiga filesystem on every medium, don't copy to that NTFS.
Or if you want to use NTFS or some other filesystem which supports very big filesizes, you could create an image file which would be formatted to SFS and then copy your backup inside of that mounted image file.
There is a guide for it, but don't use FAT because it doesn't support big enough filesizes.
Quote:
Idea is to copy contents from old G4 Work partition to G5 Work and copy old G4 SYS contents to new G5 SYS.
Will the backup program from Onyxsoft do the work or the safest route is to use a shell command?
I don't mind taking time for the migration, I just want to make sure that it will work (timestamps, file attributes etc).
Also, I have not installed the 3.9 SDK so, perhaps I don't have soft links? But I am not 100% sure about it..
If you don't have SDK: assign or at least it points to empty dir, then you don't have SDK installed. It's quite unusual to other programs to use soft links, so it'd be quite safe to copy with copy all clone method from the shell.
Check the exact directory sizes after the backup that you have exactly the same amount of bytes on both drives. If the amount differs then there might have been links or something which hasn't been copied correctly.