MountList for my 120MB Quantum HD for A1000

[nicholas]

C:Format should work nicely.

I recommend PFS3AIO rather than FFS though, assuming it works on your machine but I see no obvious reason why it wouldn't.

http://aminet.net/package/disk/misc/pfs3aio

[nicholas]

Why, in a nutshell?

All the old 1.3, 1.2 apps will play happy? What is the win? Thanks.



bp

Faster file and directory operations, rock solid stability, slim to no chance of any filesystem corruption, small memory footprint, still actively maintained, open source, very optimized code and Toni Wilen and Piru are both working on it which is a +75bazillion in my book.

It rocks basically!

edit: Your apps will be blissfully unaware of what filesystem they are running on btw. apart from Disksalv type tools I guess, but there is PFS Doctor for that. not that you'll need it very often if at all.

You'll find the tools and docs in this archive but don't use the filesystem handler from this one as it won't work, use the PFS3AIO handler I posted earlier.

http://aminet.net/disk/misc/PFS3_53.lha

[nicholas]

Actually it is Sys:System/Format.

You should use the quick option with it because you already low-level formatted the drive and the format command cannot reformat it anyway.

Code: [Select]

format drive dh0: name MyFirstPartition ffs noicons quick

So it is, my mistake. That'll teach me to post without having slept at all last night!

I still think he should go with PFS3 rather than FFS though, unless you can suggest any reasons why it wouldn't be a good idea?

[nicholas]

I am quite sure that the PFS3 tools need Kick 2.0+

Also I don't know if the WB 1.3 format program is able to format foreign file systems. So if pfsformat does not run on WB 1.3, you are a bit lost...

Toni Wilen fixed it to run on KS1.2+

From the readme:

This is improved all-in-one 100% OS 1.x/2.x/3.x/68000+ compatible
port of recently open sourced Professional File System III (PFS3),
SVN version. Sources available in AROS source tree.

Changes:

2.1
---

- Fixed access fault when booting under KS 1.3.

2.0
---

- Improved version of PFS3 for KS1.x
- Direct SCSI merged with standard PFS3.
- NSD support added.
- Autodetects block access mode (TD, TD64, NSD, DirectSCSI),
  does not mount any partitions that can't be fully or partially
  accessed due to driver limits.
- >256 block transfer ROM IDE driver bug workaround included.
  ("Max Transfer" bug)

Includes also all PFS3 for KS1.X updates:

1.1
---

- Merged latest official SVN updates.
- Compatible with KS 1.3 + 2.x extended ROM CDTV with v37 exec.
- Enabled removable media support.
- Fixed ACTION_DIE (unmount) crash.
- WB 1.x C:Info reports correct state information.

Autodetection details:
----------------------

If last block of partition is inside of first 4G of drive:

- Test if standard CMD_READ can access last block.
- Test if HD_SCSICMD Read(10) can access last block.

If both tests failed, do not mount, show error requester.

HD_SCSICMD test is needed because A590 pre-7.0 and CDTV SCSI
CMD_READ have 1G limit, HD_SCSICMD does not have any limits.
(Other old SCSI controllers may have similar restrictions.)

If last block of partition is outside of first 4G of drive:

- Test if NSD is supported and can access last block.
- Test if TD64 is supported and can access last block.
- Test if HD_SCSICMD Read(10) can access last block.

If all tests failed: do not mount, no requester shown.

If DOSType = PDSx: test HD_SCSICMD Read(10) first.

[nicholas]

I am quite sure that the PFS3 tools need Kick 2.0+

Also I don't know if the WB 1.3 format program is able to format foreign file systems. So if pfsformat does not run on WB 1.3, you are a bit lost...

Ah, I see you wrote "PFS3 tools" not "PFS3".

That could indeed be a sticking point but there's no harm in trying them or just a plain old "format DRIVE dh0: NAME System QUICK" if the PFS3 tools failed.

Nothing ventured nothing gained.

[nicholas]

That's a bummer.

I wonder why Toni didn't fix the tools for 1.2/1.3 instead of just the filesystem handler?

But.... as the machine is an A1000 is there a kickstart disk with KS2.x available?

[nicholas]

So I got the drive mounted and quick formatted (thanks Thomas) and went to copy the contents of old drive to new. (The whole point here is that disk validation can't validate dh0:, so I am adding the new drive. I seem to be able to read from dh0: fine, tho - can't write.)

I issued:

copy dh0:#? dh1: all clone quiet

...and it copied only files at the root level of the source disk, no subdirectories or their contents. Am I missing something?

Thanks.

bp

It looks correct, the only thing i'd do differently is the order of the arguments but I don't think it should make any difference.

copy CLONE DH0:#? DH1: ALL

Strange indeed, sorry I can't be more helpful.  Perhaps Thomas knows what the cause is?