@djnick

Quote:

Where is old Magic Menu prefs placed now? I want to set Right Click on Workbench [and other system-friendly programs] to Right Mouse Click stays opened, once clicked. At default system I have to hold it which is not good to me.

GUI Prefs -> Menus

_________________
BroadBlues On Blues BroadBlues On Amiga Walker Broad

@djnick

Quote:

djnick wrote: @all Ok I am now copying whole system to USB Flash. Tomorrow we will connect SSD disk to Amiga X1000, Quick Format it [I suppose], add several partitions [including 1st one for that small Amiga .sf file for boot and copy back AmigaOS from Flash.

why indirectly with usb as intermediate?
why not just hook the ssd and copy all over directly?
(i'll do this later today or tomorrow here with my x1000 and my brand new ssd drive )

using usb in between will be quite slow. are the protection bits copied correctly? how's the usb drive formatted?

regards
michael

_________________
Michael Merkel
(Michael.Merkel@gmx.net Home)
Member of Amiga-Freunde Pfalz, OS4 Welt

@broadblues

Thank you very much! :)

@MichaelMerkel

I noticed that it copies extremly slow and each file slower and slower when for example it enters into dir with lots of smaller files... for example Prefs/Presets... Damn slow... 10 seconds for each file...

Yes it is a good idea to connect both HDs, format SSD and copy all files from HD to SSD.

It didn`t come to my mind in just simple experience with Sam: it was impossible to connect two devices until sata card was bought... And still for some reason DVD rom can be seen and sometimes not...

Last edited by djnick on 06-Jul-2014 at 01:15 AM.

_________________
nykk | deetronic.rs | youtube.com/djnykk | gfx.river | mamavolibebu.com

@all

I can not believe what I see... AmigaOS is STILL [8 hours later] copying ONE SINGLE DIRECTORY and all files from it:

SYS:Prefs/Presets/tbimages/

There is 5369 files with siz of ~1kb each and AmigaOS copies them to Flash for over 8 hours!!! Now it is somewhere in the middle. It takes over minute to copy SINGLE 1kb file!!!

What is happening? Is AmigaOS always been that slow??????

I am using Filer's Copy/Paste?

I remember it was slow when I was copying from system but using Filemaster [at that time] - copy paste was fast.

Filer is a FileMaster / DOpus clone. Why it works that slow!?!?!?

_________________
nykk | deetronic.rs | youtube.com/djnykk | gfx.river | mamavolibebu.com

@djnick

AmigaOS as a whole is not that slow.

But your USB stick might be, I have two sticks one is incredibly slow at writing the other quite fast.

I wouldn't recomend copying an entire disk with filer, you waste too much time updating listings, possibly creating (and recreating or renedering) thumbnails etc, but still I've never experienced it being *that* slow.

Ideally you should have done

COPY CLONE COPYLINKS ALL

_________________
BroadBlues On Blues BroadBlues On Amiga Walker Broad

@broadblues

BTW is Filer displaying the TBIMGES dir in the destination? If so it will possibly rendering 5000 thumbnails everything you add a file. Turn thumbnail creation off for mass coppies like that.

_________________
BroadBlues On Blues BroadBlues On Amiga Walker Broad

@broadblues

Well I turned on showing thumbnails [during copying] but as far as I know AmigaOS refreshes copied list and each time it does the same when new file is appeared.
I stopped copying from Filer, started DOpusMagellan as WB Clone and start copying all files again from that directory to see how long it will take...

_________________
nykk | deetronic.rs | youtube.com/djnykk | gfx.river | mamavolibebu.com

@djnick

Don't forget that copying multiple items in parallel can cause lots of slowdown on USB copies as well, and that's OS independent. Try it in Windows and you'll see, it'll take far longer than doing the copies one after another. IIRC MacOS gets around this by queuing up copy requests, and some Linux distros do that too.

Really, I think you should stop and connect the drive internally and save yourself hours of time. There could be other issues going on as well, for example, if Vox had been messing about with USB settings and disabled USB2.0 it could be running really slowly. God only knows what other thins had been messed with on that machine - the partition setup alone is enough to think crazy things were going on with the setup.

_________________
RobTheNerd.com | InstallerGen | SMBMounter | Atoms-X

@Daedalus

Okay if this takes too long [this single directory] I will connect this definitelly HD [I've never opened X1000 but I suppose there is place where I can connect SSD disk]

Then I will start Partition program and see what to do.

Are there "Step by step" using partition program - as Vox will not come today to me - I decided to do alone with your help, of course. It would help a lot if there is Step by Step with IMAGES [or no need for images but for good explanation] what to do and how to partition SSD to boot quickly?

Then I will copy back from HD to SSD everything and disconnect old 2TB HD.

The biggest issues are file systems.

I decided to have SSD -> AmigaOS and on old HD - a Linux.

_________________
nykk | deetronic.rs | youtube.com/djnykk | gfx.river | mamavolibebu.com

@djnick

USB copying can be slow on fat fs. If backing up Amiga files you need to use an Amiga fs.

You can reformat using SFS which is good for faster copy from the Ctrl Alt M commodity. You may need to install RDB from MTB.

I use a workbench to copy with show all then drag all and drop. In the Workbench Prefs I max out the copy buffer. For me this works well.

Last edited by Hypex on 06-Jul-2014 at 03:45 PM.

@djnick

I think it would be better all round to stop right now if you're using FAT32 on the SSD right now - when you copy back you'll be missing the file permissions and that could give you other problems which might be tricky for you to resolve.

What I would do:

- Stop copying right now
- Install the SSD internally
- Make the partitions using MediaToolBox (please note I don't have an X1000 but this is what I gather is needed):
+ boot partition (tiny)
+ Workbench partition (~1GB)
+ SWAP partition (~2GB)
+ Other partitions (whatever size you like, but I like multiple small partitions dividing up the space, Work: Games: Music: Files: for example)
- Make first (boot) partition FFS
- Make all other partitions SFS except SWAP
- Format all partitions except SWAP
- Copy old system to new (using CLONE to keep file dates etc. intact)

Please check with someone who has a *properly set up* X1000 (i.e., not Vox) to confirm the proper partition set up. I don't know if you got any documentation about the partitions required, but my copy of OS4.1 for the XE came with some. Might be worth a look.

Last edited by Daedalus on 06-Jul-2014 at 02:29 PM.

_________________
RobTheNerd.com | InstallerGen | SMBMounter | Atoms-X

@Daedalus

This is one of the best helpful informations :)

As I have only one montor right now I will snapshot your email as photo and loop at phone image while I will be installing :)

I remember when SAM arrived to me 2 [or more?] years ago, I got enormous help from... oh damn... the guys name [that lives in Japan now]... forgot... And I remember we were using Skype and he was telling me exactly what to do in MediaToolBox to create perfectly working partitions. And what I remember - he used Load something [in L:] and edited in textual file editor something and THEN only he formatted HD.

Thank you very much again. In the mean time I will see if there is [once more] a good link [maybe in Epsilon's AmigaOne X1000 Blog or similar] with photos how MediaToolBox will look when SSD HD is partitioned.

I will start doing it later at night when baby goes to sleep :)

_________________
nykk | deetronic.rs | youtube.com/djnykk | gfx.river | mamavolibebu.com

@broadblues

Quote:

broadblues wrote: ... Ideally you should have done COPY CLONE COPYLINKS ALL

but COPYLINKS will convert links to real files... that is not good if you want an exact copy (-> keep the links as links)

reagrds...
michael

_________________
Michael Merkel
(Michael.Merkel@gmx.net Home)
Member of Amiga-Freunde Pfalz, OS4 Welt

@djnick

Quote:

djnick wrote: @all I can not believe what I see... AmigaOS is STILL [8 hours later] copying ONE SINGLE DIRECTORY and all files from it: SYS:Prefs/Presets/tbimages/ There is 5369 files with siz of ~1kb each and AmigaOS copies them to Flash for over 8 hours!!! Now it is somewhere in the middle. It takes over minute to copy SINGLE 1kb file!!! What is happening? Is AmigaOS always been that slow?????? I am using Filer's Copy/Paste?

i alywas use the great Backup for cloning drives.
enter source and destination disks and start. that's all.
you can even stop and restart later and only the missing/changed files will be copied.
well - it is a backup/clone tool and doing its job perfectly well!

i just did so installing my brand new ssd and cloning ~10 partitions. did all this and are now up and running the new ssd

regards...
michael

_________________
Michael Merkel
(Michael.Merkel@gmx.net Home)
Member of Amiga-Freunde Pfalz, OS4 Welt

Quote:

Daedalus wrote: @djnick I think it would be better all round to stop right now if you're using FAT32 on the SSD right now - when you copy back you'll be missing the file permissions and that could give you other problems which might be tricky for you to resolve. What I would do: - Stop copying right now - Install the SSD internally - Make the partitions using MediaToolBox (please note I don't have an X1000 but this is what I gather is needed): + boot partition (tiny) + Workbench partition (~1GB) + SWAP partition (~2GB) + Other partitions (whatever size you like, but I like multiple small partitions dividing up the space, Work: Games: Music: Files: for example) - Make first (boot) partition FFS - Make all other partitions SFS except SWAP - Format all partitions except SWAP - Copy old system to new (using CLONE to keep file dates etc. intact) Please check with someone who has a *properly set up* X1000 (i.e., not Vox) to confirm the proper partition set up. I don't know if you got any documentation about the partitions required, but my copy of OS4.1 for the XE came with some. Might be worth a look.

agree with the smaller partition sizes but I'm pretty sure OS4.1 no longer requires a dedicated SWAP partition though it's been quite a few years now since I set up my system so hopefully someone else can confirm this

_________________
____________________________
c64-2sids, A1000, A1200T-060@50(finally working!),A4000-CSMKIII
! My Master Miggies- Amiga 1000 & AmigaOne X1000 !
mancave-ramblings
X1000 I BELIEVE

@klx300r

I never even bothered with a swap partition with my XE with 1GB so I certainly wouldn't bother on an X1000.

The FFS boot partition I use on my X1000 is 1.1MB which is overkill since it still has 94% free space.

@MichaelMerkel

Quote:

but COPYLINKS will convert links to real files... that is not good if you want an exact copy (-> keep the links as links)

Yes but not adding COPYLINKS means the links are ignored. So you have to make a not of all links and recreate them, which is a possibilty.

_________________
BroadBlues On Blues BroadBlues On Amiga Walker Broad

@all

First THANK YOU all for all tips and tricks! And to Vox to helped me finally to close the Amiga pain circle :)

Amiga X1000 now WORKS AMAZINGLY FAST!!! It was HARD DISK and large partition!!!

Tonight I was on the edge to quit everything... Vox came to me 8 hours ago, and we started. I will try to be as short as possible!

- First we connected SSD next to HD and DVDRom. It booted and we partitioned SSD HD to look like this:

1st partition = 100mb = Boot [and checked to be Bootable - it was wrong]
2nd partition = 4GB = System [and checked to be Bootable and Automount]
3rt partition = 2GB = Swap [default]
4rd partition = 4GB = Work
All the rest was left intacted for future Linux installation

Then... we spent over 7 hours to figure out all problems that happened.

First it didn't boot [because it takes us around 45 minutes to read into manual that AmigaX1000 will NOT boot any other HD that is NOT connected to SATA0 or SATA2 connector on motherboard...] Then it booted [after plugged into SATA0 or SATA2] but without system. Then we realized that it starts booting after all into Boot [100mb] partition where is no system. Then we disabled visibility of that partition by holding 2mousebuttons from early startup menu and then it starts booting into 4rd partition named Work!? It was mystery.

And THEN we found that disabling BOOT in MediaToolBox and Mounting causing AmigaOS to finally BOOT!

Then we reformatted again and copied default system from AOS4.1 CDRom to SSD.

Then we connected both HDs and copied working system from old HD to SSD.

Rebooted - and 7 hours later - it finally worked! And it WORKS VERY very VERY fast!

Incredible speed! I didn't expect this! It works faster than Android tab! [while it was impossible in last 2 years with Sam and default non-SSD Amiga X1000]!

I think it was fast explanation :) I am going now to explore more :) But looks like I will have to go to sleep first!

_________________
nykk | deetronic.rs | youtube.com/djnykk | gfx.river | mamavolibebu.com

@djnick

good news & thanks to Vox for finally fixing what he seriously screwed up in the 1st place word of advice to Vox...RTFM and ask questions BEFORE you start a hardware project eh

btw, why all that space for Linux when I'm sure your new HD has ALOT of GB left?? I would create a 5th partition for Games (say min. 20GB), 6th for Demos, 7th for Music, 8th etc etc with large partitions

Last edited by klx300r on 07-Jul-2014 at 03:58 AM.

_________________
____________________________
c64-2sids, A1000, A1200T-060@50(finally working!),A4000-CSMKIII
! My Master Miggies- Amiga 1000 & AmigaOne X1000 !
mancave-ramblings
X1000 I BELIEVE

@djnick

Finally! You got it. Well done.

You'd think by now they'd have worked out a way to make these new systems easier for users. Remember when computing was fun? Before we had these damn AmigaOne machines drving us into craxy confusion!

It also shows how the boot volume is made to be easier on the delvelopers and harder on the users. I also wonder how to update it. Their updater would need to track down every booter and update it.