Bsc Tandem ide+cd installation

[Dandolo]

Please connect the CF card to your A1200, run TSGUI, click on CF0 in the list and select "create mountlist" from the menu. Attach the resulting file here.
 
FastFileSystem won't be able to read a FAT disk. You need MessyFileSystem if the card is formatted as FAT.
 
And as I said above you need to put valid values into LowCyl, HighCyl, Surfaces and BlocksPerTrack. TSGUI on the A1200 should be able to read these values and save them to the mountlist.

Ok, done and placed correct parameters showed by tsgui into mountlist (CF 4 Gb) and reinserted MessyfileSystem in dh0:l, but after mounting and trying to access to CF0, system crash. Here you are the file generated by Tsgui:[ATTACH]2693[/ATTACH]

[Dandolo]

Is this mountlist correct?

[Thomas]

Done, after selected oktagon.device, tsgui reply: "Cannot determine HDD size".

At which unit number is the CF card?

[Thomas]

Is this mountlist correct?

This might be a working mountlist entry for Kick 1.3:

Code: [Select]


CF0:
FileSystem     = L:MessyFileSystem
StackSize      = 8192
GlobVec        = -1
Device         = oktagon.device
Unit           = 0
Flags          = 0
BlockSize      = 512
Surfaces       = 1
BlocksPerTrack = 1
Reserved       = 2
Interleave     = 0
LowCyl         = 0
HighCyl        = 7812819
Buffers        = 25
BufMemType     = 1
DosType        = 0x4D534400
Mount          = 1
#


Except for the unit number which must match the actual position of the CF card reader.

[Dandolo]

At which unit number is the CF card?

It's number 0, I've tried other number (until 7) but message was the same.
Quote:
Originally Posted by Dandolo
Is this mountlist correct?
 
This might be a working mountlist entry for Kick 1.3:
 
 
Code:
CF0:    FileSystem = L:MessyFileSystem    StackSize = 8192    GlobVec = -1    Device = oktagon.device    Unit = 0    Flags = 0    BlockSize = 512    Surfaces = 1    BlocksPerTrack = 1    Reserved = 2    Interleave = 0    LowCyl = 0    HighCyl = 7812819    Buffers = 25    BufMemType = 1    DosType = 0x4D534400    Mount = 1#
Except for the unit number which must match the actual position of the CF card reader.
 
Tonight I try to mount your entry, thanks for your patience Thomas!:angel:

[Dandolo]

It's number 0, I've tried other number (until 7) but message was the same.
Quote:
Originally Posted by Dandolo
Is this mountlist correct?
 
This might be a working mountlist entry for Kick 1.3:
 
 
Code:
CF0: FileSystem = L:MessyFileSystem StackSize = 8192 GlobVec = -1 Device = oktagon.device Unit = 0 Flags = 0 BlockSize = 512 Surfaces = 1 BlocksPerTrack = 1 Reserved = 2 Interleave = 0 LowCyl = 0 HighCyl = 7812819 Buffers = 25 BufMemType = 1 DosType = 0x4D534400 Mount = 1#
Except for the unit number which must match the actual position of the CF card reader.
 
Tonight I try to mount your entry, thanks for your patience Thomas!:angel:

I have put your entry in mountlist: this time Amiga doesn't crash but nothing appear, after mounting CF0: and trying cd CF0: results is "Can't find CF0:" ...

[Thomas]

After reading the docs I come to the conclusion that fat95 should work on Kick 1.3. Tried it and it does.

So this mountlist entry should work:

Code: [Select]


CF0:
    Device = oktagon.device
    Unit = 0
    Flags = 0
    BufMemType = 1
    MaxTransfer = 0x20000
    Mask = 0xfffffffe
    Filesystem = l:fat95
    StackSize = 4096
    GlobVec = -1
    Buffers = 200
    Mount = 1
    LowCyl = 0
    BlockSize = 512
    HighCyl = 1
    BlocksPerTrack = 1
    Surfaces = 1
    DosType = 0x46415401
#


Make sure that the fat95 program is in L.

[Dandolo]

After reading the docs I come to the conclusion that fat95 should work on Kick 1.3. Tried it and it does.
 
So this mountlist entry should work:
 

Code: [Select]

CF0:
    Device = oktagon.device
    Unit = 0
    Flags = 0
    BufMemType = 1
    MaxTransfer = 0x20000
    Mask = 0xfffffffe
    Filesystem = l:fat95
    StackSize = 4096
    GlobVec = -1
    Buffers = 200
    Mount = 1
    LowCyl = 0
    BlockSize = 512
    HighCyl = 1
    BlocksPerTrack = 1
    Surfaces = 1
    DosType = 0x46415401
#

Make sure that the fat95 program is in L.

I'm going crazy .... :hammer::hammer::hammer:.... finished to insert new entry in mountlist, mounting CF0: A2000 says: "Software error - task held, Finish ALL disk activity, Select CANCEL to reset/debug" the GURU meditation #00000004.002A44A8.
AAArgh ... :madashell:

[Thomas]

I suppose there is something wrong with your oktagon.device. Which version of the driver disk do you use? There are four different versions on the Amiga Hardware Database: http://amiga.resource.cx/exp/tandem

What happens if you use the supplied HDInstTools program? Does it find the CF card? Does it allow to create partitions on the CF card? (Warning: this will delete all existing data on it!!)

If everything works so far, please try this program: http://thomas-rapp.homepage.t-online.de/download/getgeometry.lha
Unpack it to ram and run it from the Shell like this:

ram:getgeometry oktagon.device 0

Does it crash, too? If not, what does it print?

[Dandolo]

I suppose there is something wrong with your oktagon.device. Which version of the driver disk do you use? There are four different versions on the Amiga Hardware Database: http://amiga.resource.cx/exp/tandem
 
What happens if you use the supplied HDInstTools program? Does it find the CF card? Does it allow to create partitions on the CF card? (Warning: this will delete all existing data on it!!)

I haven't an install disk, it wasn't supplied when I bought the used card; I have tried ALL the .dms archives from link above suggested and nothing of these works.
Oktagon.device wasn't present in any of the .dms on amiga.resource. oktapussy.device cannot be used because needs OS > 2.04.
I have tried to download an oktagon.device from an ALF controller on amiga.resource but the "Version" command says 3.20 on my miggy1200, "Error in open" on my Big Box 2000. Really you're right: problem maybe is relative to the oktagon.device, but I haven't install disks (original or copies). Google doesn't help me this time (for the moment!)
 
Version of HDInstTools program downloaded from amiga.resource, after command "oktamount", starts correctly but says "This program requires a BSC controller" and stop (no partition or HD showed, all "grey").
This is, in absolute, the hardest installation of HW that I have tried!

[Dandolo]

If everything works so far, please try this program: http://thomas-rapp.homepage.t-online.de/download/getgeometry.lha
Unpack it to ram and run it from the Shell like this:
 
ram:getgeometry oktagon.device 0
 
Does it crash, too? If not, what does it print?

Workbench reply: cannot open oktagon.device unit 0

[Thomas]

There: http://www.amiga.org/forums/showpost.php?p=726401&postcount=13
you say that in TSGUI you can select oktagon.device and that the CF card is shown at unit 0. Is this still true? Can you make a hardcopy of the window after you selected the CF card unit?

Oktagon.device wasn't present in any of the .dms on amiga.resource.

oktagon.device is created in memory when the AT file is executed by Binddrivers. Please don't mix drivers for different controllers.

[Dandolo]

 
oktagon.device is created in memory when the AT file is executed by Binddrivers. Please don't mix drivers for different controllers.

Hi Thoms, sorry, I'm really Newbie :laughing:
Well, I've deleted the octagon.device obtained from ALF controller, re-controlled all directories (devs, l) and mountlist to insure all it's ok with your instruction. Then I launched Tsgui: but there isn't oktagon.device in "select raw device" this time. I suppose last time was present because I've copied the driver from other controller driver. Sorry ... I hadn't understood that AT file was made to create the oktagon.device in memory ...
Maybe it's necessary to control/mount something in the startup-sequence?

[Thomas]

You need AT and AT.info in Extensions and BindDrivers in Startup-Sequence. (AT.info is only visible in a DOS shell. If you see AT in the Workbench drawer, then AT.info is present.)

Also make sure that the hardware is still connected properly. If you often remove and insert the CF card, some other components might loose connection, especially if the CF card reader is connected directly to the controller (not through a cable).

[Dandolo]

You need AT and AT.info in Extensions and BindDrivers in Startup-Sequence. (AT.info is only visible in a DOS shell. If you see AT in the Workbench drawer, then AT.info is present.)
 
Also make sure that the hardware is still connected properly. If you often remove and insert the CF card, some other components might loose connection, especially if the CF card reader is connected directly to the controller (not through a cable).

Yeah, AT is present in dh0:expansion and visibile in workbench. Bindrivers is present as command in Startup-Sequence. HW is mounted correctly (I think): CF reader is connected to card by IDE cable. I cannot understand why AT file doesn't generate oktagon.device: infact when I try to start HDInstTool it says "Cannot find oktagon.device". If I copy the file called "oktamount" from dms present at amigaresource, then start HDInstTool by-pass this problem but then says "THis program requires a BSC controller" and stop. maybe it's a card problem (chips damaged?). Another way to test could be try to change the CF reader with another one 40 pin IDE: I have already tested the card with a 40 Gb HD IDE but nothing, same message on HDInstTool...:angry:

[Dandolo]

I have the suspect that something wrong happens with AT file: this file should create oktagon.device, putting it in memory, but exactly where? I'm looking for this device and I cannot find it anywhere.
Maybe AT file must be loaded "manually"  in startup-sequence? I think that BindDrivers doesn't recognize it, so that oktagon.device cannot be found with impossibility to activate the hardware. AT file has an .info icon associated, so I can see it in workbench: it is possibile to active it also after startup-sequence? Anyone has ideas? No one has tried to use tandem IDE on amiga 2000 kick 1.3?