WB 1.2 SCSI mountlist?

[blakespot]

I am trying to get this SCSI disk formatted under WB 1.2 working with WB 1.3 and I've only got 1.3 (FFS) mountlists to go from.  Can someone show me a WB 1.2 SCSI mountlist?

I've got a Quantum ProDrive 40S if it matters and a Microbotics StarDrive board. Thanks!



blakespot

[blakespot]

Ok, the StarDrive SCSI installed / setup disk created a WB 1.2 bootable disk that contains this in the Startup-Sequence.  

DHMount d=StarDrive.device F=0x3030 I=0 S=3 BPT=37 LC=1 HC=738 U=6

(It must be OFS and not FFS, as it was formatted under 1.2, right?  Though I've been using KickStart 1.3 for all of this.)  There is no MountList entry for DH0: on that WB 1.2 disk, yet HD0: mounts just fine and is fully accessible.

My goal is to get that drive working with a WB 1.3 boot disk.

Under 1.3, just adding the above line to the Startup-Sequence does not mount the disk.  So, I've removed that line from the WB1.3 SS and tried the following two MountList entries (though, of course, not at the same time):

But under 1.3, this does NOT (from devs/MountList):

DH0:   Device = StarDrive.device
      Unit = 6
      Flags = 0x3030
      Surfaces = 3
      BlocksPerTrack = 37
      Reserved = 2
      Interleave = 0
      LowCyl = 1 ; HighCyl = 738
      Buffers = 17
      BufMemType = 1
      
It should be noted that StarDrive.device -- a file -- does not exist anywhere.  I assume this is being pulled from the firmware on the interface.  It does not exist on the WB disk that the installer generated.

Can anyone suggest something that will let me get WB 1.3 up and running on the A1000?



bp

[Jope]

So you're sure there's no stardrive.device in devs: or sys:expansion? I looked at the pictures for that card and there's no ROM on board.

Or is this a different stardrive than the one that goes inside the starboard expansion?

[blakespot]

Yea, this is the StarDrive module, attached to a StarBoard II.

There's no StarDrive.device in devs/ but I have not looked in expansion/.  I will check that when I get home.  

Also, there is a 6-8K binary called StarDrive with an icon sitting on one of the disks, but it does not seem to be called by the successfully booting / mounting WB1.2 boot disk.  So...dunno what that is.

I'll get back here when I check.  Thanks.



bp

[Nostalgiac]

I could be wrong but...

If the HD got formatted from a 1.2 system, then it's unlikely to have the RDB (Rigid Disk Block) type of format that was introduced in 1.3

In other words.... its quite likely that this harddisk will only be readable when used with the exact original controller it got formatted on.

Tom UK

[save2600]

Blakespot, you ever get this going? I'm dealing with the same **** right now. The Stardrive 1.5 software I have formats and reads the disc, but I can't get icons to show on the desktop (using KS and WB 1.3), even after mounting the drive manually using the xxx.list the software created in devs. When I query DH0: from the CLI, says it's not a valid DOS disk. Getting somewhere now, but is it too much to ask to have the ****ing icons pop up on Workbench instead?  :mad:

Okay, so you have to mount the thing manually, then format it through the CLI for it to become recognizable as a DOS disk. Then you copy over the system software. To finish this obnoxiously tedious project, you then follow the instructions included in the Startup-Sequence.hd file located in the S directory of your Workbench floppy and edit it to mount the Stardrive by pointing it to the devs:xxx.list file that the Stardrive software created and placed for you when you performed its HD read. Get all that?  :lol: