🚀 go-pugleaf

roddi@bruce.cs.monash.OZ.AU (Roddi Walker) writes:
>Hi!
>	Recently I installed the WB 2.0 roms in my A2000.  However, I
>have had some trouble reformatting my GVP Impact Series II harddisk
>with 40MB Quantum, which is split into 2 partitions, DH0: and DH1:.
>	I fooled around with GVP's FaaastPrep, but this didn't seem to
>reformat the drive - (a) it was too fast and (b) the UpdateWB program kept
>complaining that DH0: wasn't a dos disk (or somesuch).  So, in a fit of
>blind fury, I used the DOS format command (after booting off the 2.0
>Workbench disk) to format the 2 partitions, with the following commands:

>format drive dh0: name Boot ffs
>format drive dh1: name Sock ffs

>Well, this seems to work fine.  Problem is, I *DON'T* have gvpscsi.device
>in DEVS: and I *DON'T* have dh0_mountlist in SYS: ( which contains mountlist
>entries for DH0: and DH1: - I presume this is where it belongs - when I got
>the drive (pre-formatted and set up) that's where it was.  Should I add it
>to DEVS:MountList and do a "mount dh0:", "mount dh1:" in my user-startup?).

>	What I basically need to know is:
>*	What do I do with gvpscsi.device	?
>*	What do I do with dh0_mountlist		?

>Help!

>Yours in Advance 

>Roddi

Perhaps you might try the HDToolbox on the 2.0 disks.  To get it to read the
gvp disk, you type in at the CLI "hdtoolbox gvpscsi.device".  You can change
the partitions to your heart's content.  It will allow you to low level format
it if you want.

The reason there is no gvpscsi.device and dh0_mountlist is because the
drives are automounted on system startup.  They _should_ be working if
the jumper on the GVP II is in the autoboot position.  The parameters
for the drive sizes are stored in the RDB (Rigid Disk Blocks in C= terms).
HDtoolbox and faaastprep (why the hell did they put so many "a"s in there??)
read and write these RDB's.

I also suggest that you might want to only have one partition on such a small
drive.

Disclaimer:  I dont have a SCSI disk attached to a GVP series II controller
so therefore I dont know what I am talking about.

But I have run HDtoolbox on gvpscsi.device and it did correctly locate
a SCSI device (a tape drive FYI) and I know the RDB's created on a GVP
controller will work on a 2091 and an A3000.  That means it should work.

Of course, if you were going to tempt fate by doing this you should back
everything up first.  But in this case, it looks like the drives have
already been erased, so you have nothing to loose.

Good luck (and let me know how you go...)
-- 
Peter Wemm : peter@zeus.dialix.oz.au
Diplomacy is the art of saying "nice doggy" until you can find a suitable rock.