Welcome, Guest. Please login or register.

Author Topic: Bsc Tandem ide+cd installation  (Read 7179 times)

Description:

0 Members and 1 Guest are viewing this topic.

Offline DandoloTopic starter

  • Newbie
  • *
  • Join Date: Feb 2013
  • Posts: 18
    • Show all replies
Re: Bsc Tandem ide+cd installation
« Reply #14 from previous page: February 16, 2013, 02:08:33 PM »
Quote from: Thomas;726553
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
 

Offline DandoloTopic starter

  • Newbie
  • *
  • Join Date: Feb 2013
  • Posts: 18
    • Show all replies
Re: Bsc Tandem ide+cd installation
« Reply #15 on: February 17, 2013, 11:31:57 AM »
Quote from: Thomas;726581

 
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?
 

Offline DandoloTopic starter

  • Newbie
  • *
  • Join Date: Feb 2013
  • Posts: 18
    • Show all replies
Re: Bsc Tandem ide+cd installation
« Reply #16 on: February 17, 2013, 12:43:51 PM »
Quote from: Thomas;726679
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:
 

Offline DandoloTopic starter

  • Newbie
  • *
  • Join Date: Feb 2013
  • Posts: 18
    • Show all replies
Re: Bsc Tandem ide+cd installation
« Reply #17 on: February 18, 2013, 02:19:08 PM »
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?
 

Offline DandoloTopic starter

  • Newbie
  • *
  • Join Date: Feb 2013
  • Posts: 18
    • Show all replies
Re: Bsc Tandem ide+cd installation
« Reply #18 on: February 19, 2013, 02:00:19 PM »
Quote from: Thomas;726800
On WB 3.1 there is a command called ShowConfig which lists all expansion boards recognised by the system. I didn't find a similar program on WB 1.3, so I wrote this: http://thomas-rapp.homepage.t-online.de/download/showboards.lha
 
Run it and look for a board with Vendor=082c and Product=06. This is the hardware the AT driver binds to (see icon information -> tool types).
 
Only if the hardware is recognised, the driver will load and initialize.

Hi Thomas, thanks a lot for your support. Well, I think card is broken 'cause it isn't recognised by system: here you are the output from you progs:
 
type=e6 product=$51 vendor=0202 serial=00000000 addr=2000000 size=200000
type=d2 product=$03 vendor=07e1 serial=00000000 addr=0200000 size=020000
type=e7 product=$0a vendor=0202 serial=00000000 addr=6000000 size=400000
type=c4 product=$01 vendor=0201 serial=00000000 addr=4000000 size=080000
 
Useful prog, congratulation! I have tried to reboot system and load Workbench by floppy (1.3) bypassing any startup-sequence command that could cause conflict, but the result was the same. I tried to change the card position onto another slot but same result: Maybe it's really broken , I've made a bad purchase. I'd like to a my friend to bring me his tandem card to test if works on my big box (he has succesfully installed the card on his A4000 ). Bad Luck!