Welcome, Guest. Please login or register.

Author Topic: SCSIDEV.DEVICE  (Read 1371 times)

Description:

0 Members and 1 Guest are viewing this topic.

Offline Drake008Topic starter

  • Newbie
  • *
  • Join Date: Mar 2007
  • Posts: 9
    • Show only replies by Drake008
SCSIDEV.DEVICE
« on: March 22, 2007, 04:53:12 PM »
I got myself another Scsicontroller. It's the Impact A2000-HC (no RamSlots!). There are two roms on it which are divided in odd and even which seems to have the GVP Rom 1.0 on them.

If I start the HDToolsBox for partioning my HDD I use scsidev.device behind the filename. After that the program hangs.

Can somebody tell me how to avoid this.
 

Offline skurk

  • Hero Member
  • *****
  • Join Date: Dec 2006
  • Posts: 929
    • Show only replies by skurk
Re: SCSIDEV.DEVICE
« Reply #1 on: March 22, 2007, 05:46:40 PM »
Try a newer version of HDToolBox or get HDInstTool.
Code 6502 asm or... DIE!!

[C64, C128, A500, A600, A1200, A3000, MBP+Mini, Efika/MOS2.1, Sam440 w/AOS4.1
 

Offline Thomas

Re: SCSIDEV.DEVICE
« Reply #2 on: March 22, 2007, 05:46:53 PM »
Select the HDToolbox icon with Workbench, then choose Icon -> Information from the menu.

You will see tooltypes like these:

SCSI_DEVICE_NAME=scsi.device
SCSI_MAX_ADDRESS=6
SCSI_MAX_LUN=7

Change them to

SCSI_DEVICE_NAME=scsidev.device
SCSI_MAX_ADDRESS=1
SCSI_MAX_LUN=0

Then run HDToolbox from Workbench.

If it still hangs, then check your cabling and the jumpers on your HDD. The SCSI ID of the HDD should be 0 or 1. A SCSI bus usually needs to be terminated at both ends of the cable.

Also I am in doubt if scsidev.device is correct (never heard of it). Try scsi.device instead. Or read the manual, it should tell the correct name.

Bye,
Thomas

Offline Drake008Topic starter

  • Newbie
  • *
  • Join Date: Mar 2007
  • Posts: 9
    • Show only replies by Drake008
Re: SCSIDEV.DEVICE
« Reply #3 on: March 22, 2007, 07:21:53 PM »
I will try it. The problem is that I got no manual (just an old installer Disk from a drivers site). The small 30 MB SCSI HDD which run is on the controller. It is a ST-138N which cannot be termnated.

The normal initialization tool preps the hdd but only with OFS.
 

Offline melange

  • Full Member
  • ***
  • Join Date: Jun 2005
  • Posts: 235
    • Show only replies by melange
Re: SCSIDEV.DEVICE
« Reply #4 on: March 25, 2007, 11:02:47 AM »
Hi I hate to disappoint you, but I have two of those cards, one is a HC (No Ram) and the other a HC2 (2meg).  Using the 1.0 version of scsidev.device you will not be able to query the scsibus at all.  Scsidev.device will allow you a single HDD on SCSI ID 0 (I think?).  You cannot put a CDROM drive on the system either, not even if you get the addresses and termination perfect.  Whenever you query the scsibus, it'll hang.

I got around this problem by disabling the on board ROMS and booting with a floppy disk that mounted the HDD using the binddrivers gvpscsi.device v3.15 from Ralph Babels site.  I then used a command called defdisk and swapped to booting from the HDD.  If you do this you can have a CDROM as well.

Ralph Babels site has what are supposed to be ROM updates for those cards.  I tried my heart out to get them to work, but alas twas not to be!!

The ROM updates do not look like they are compatible at all.

If you find anybody that has an updated scsidev.device, please share the goodies :-))

I tried for quite a bit here, but it eventually disappeared and was forgotten  :-(

I then brought replacement cards off ebay, coz I didn't like booting from floppy   :lol:
2 x A1200 Blizzard IV 030@50Mhz
1 x A3000D 030@25Mhz
1 x A2000 030@25Mhz
1 x A2000, 2 x A600
2 x A500