MountList for my 120MB Quantum HD for A1000

[Thomas]

I just tried it and it's like I said: the normal Format program of WB 1.3 is not able to format a PFS partition and sfsformat does not run on Kick 1.3. So there is no way to use PFS3 on Kick 1.3 without preparing the harddrive on a Kick 2.0+ machine first.


Edit: here is the mountlist changed to use PFS3aio if you want to try it anyway:

Code: [Select]


SDH0:
     Device         = StarDrive.device
     Unit           = 4
     Flags          = 0
     Surfaces       = 1
     BlocksPerTrack = 173
     Interleave     = 0
     Reserved       = 2
     BufMemType     = 0
     Buffers        = 30
     LowCyl         = 0
     HighCyl        = 459
     FileSystem     = l:pfs3_aio-handler
     GlobVec        = -1
     DosType        = 0x50465303
     Mount          = 1
#

SDH1:
     Device         = StarDrive.device
     Unit           = 4
     Flags          = 0
     Surfaces       = 1
     BlocksPerTrack = 173
     Interleave     = 0
     Reserved       = 2
     BufMemType     = 0
     Buffers        = 30
     LowCyl         = 460
     HighCyl        = 919
     FileSystem     = l:pfs3_aio-handler
     GlobVec        = -1
     DosType        = 0x50465303
     Mount          = 1
#

SDH2:
     Device         = StarDrive.device
     Unit           = 4
     Flags          = 0
     Surfaces       = 1
     BlocksPerTrack = 173
     Interleave     = 0
     Reserved       = 2
     BufMemType     = 0
     Buffers        = 30
     LowCyl         = 920
     HighCyl        = 1379
     FileSystem     = l:pfs3_aio-handler
     GlobVec        = -1
     DosType        = 0x50465303
     Mount          = 1
#


[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?

[motrucker]

@ Thomas,
      Thank you for this info. I am about to do the same thing on my A1000 with the very same controller. Could not have come at a better time.

[blakespot]

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

[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?

[Thomas]

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.

In WB < 2.0 the copy command is a bit picky about its parameters. To copy a directory recursively, you specify the directory and not its contents.

So the correct command line is

copy dh0: dh1: all clone quiet

and not dh0:#?.

[LoadWB]

In WB < 2.0 the copy command is a bit picky about its parameters. To copy a directory recursively, you specify the directory and not its contents.

So the correct command line is

copy dh0: dh1: all clone quiet

and not dh0:#?.

I'm not certain that just pre-2.0 Copy that's persnickety.  ISTR having similar results later.  The device-only syntax is what I've always used successfully from 1.3 to 3.9 when copying full drives via the CLI.