Right. Warp recognizes the SCSI adapter whether or not anything is
attached. The order of the ide and scsi drivers affects which drive Warp
will try to boot from. 

Tekram scsi adapters were considered a good deal for a time. 7 years
ago. Some used chips supplied by a better-known scsi supplier. The
problems were too long ago to recall. ISTR some may have worked with a
driver by that chipmaker.

Before spending $$ on adapters, consider that a buslogic or adaptec scsi
card with the right external plug for your scanner can be had for the
cost of shipping on ebay. And be sure the Tekram driver works with a
scanner. Advansys's scsi driver is fine for hdds. But not scanners. But
that was 5 hours wasted 7 years ago. 

said Harry, stirred by:
     Tim Yoder 's message of:
     Wednesday 25 Jan 06 at 11:12 PM,
     On: [OS2HW] SCSI under IDE
     [echoed below, at least in part]

--------
I'm running eCS 1.25 in an IDE environment which consists of two Maxtor
200 GIG ATA drives, among other things.  I also have an old Warp4
desktop P.C. that is using a SCSI 2 GIG drive.  I want to pull the SCSI
drive from the desktop and temporarily hook it up to the eCS system,
just long enough to XCOPY the HPFS files to one of the Maxtor drives. 
In the long term, I intend using the SCSI adaptor card to connect to my
HP 4C SCSI scanner.

The problem is, I can't get eCS to recognize the Tekram SCSI
controller.

If you like, you can check the card and the drivers at
http://www.tekram.com.cn:8060/ProductSpec.ASP?Product=DC-315U
http://www.tekram.com.cn:8060/SoftwareUpdate.asp?Product=DC-315U
(Choose "For Windows9X/NT/2K/XP/2003/Novell netware" for the drivers)

When I dual boot to Windows XP, it sees the Tekram hardware (i.e.:  PCI
Slot 3, bus 0, device 7) so I assume the problem is in eCS.

On the eCS side, in an attempt to get the controller recognized, I've
done the following variations:
- Manually put TRM3X5.ADD into C:\OS2 and C:\OS2\BOOT
- Manually put BASEDEV=TRM3X5.ADD into CONFIG.SYS
- Also used the "Device Driver Install" icon to try the above
  variations.
- Put BASEDEV=TRM3X5.ADD ahead of BASEDEV=OS2SCSI.DMD
- Put BASEDEV=TRM3X5.ADD behind BASEDEV=OS2SCSI.DMD
- In all cases, made sure to keep them after
  BASEDEV=DANIS506.ADD /!BIOS /V

Because my Warp4 P.C. is sitting in the middle of a heavy desk, it will
be a significant effort to pull any of my SCSI devices and hook them up
to the Tekram controller, so I haven't actually connected any hardware
to the adaptor yet.  But, should that be necessary?  It seems like the
system ought to recognize the adaptor even without a device connected
to it.

If it's relevant, here is some of my setup:

-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-  Hardware:
MSI Athlon64 socket 754 motherboard (MB-MSI-K8T-Neo-FSR)
AMD Athlon64 3000+ CPU
1 GIG DDR333 RAM DIMM memory
-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-  BIOS:
Standard CMOS Features
  Primary IDE Master           Auto    6Y200P0
  Primary IDE Slave            Auto    6Y200P0
  Secondary IDE Master         Auto    Hewlett-Packard D
  Secondary IDE Slave          Not Installed
  Plug and Play Aware          No
  Boot Sequence
    1st Boot Device            Floppy 1.44 MB 3.5
    2nd Boot Device            CD/DVD-0: Hewlett-Packard DVD Writ
    3rd Boot Device            IDE-0: Maxtor 6Y200P0
    Try other Boot Devices     Yes


Tim
HPT
-- 
-----------------------------------------------------------
htravis at attglobal dot net
DemostiX
-----------------------------------------------------------





 
Yahoo! Groups Links

 To visit your group on the web, go to:
    http://groups.yahoo.com/group/os2hardware/

 To unsubscribe from this group, send an email to:
    os2hardware-unsubscribe{at}yahoogroups.com

 Your use of Yahoo! Groups is subject to:
    http://docs.yahoo.com/info/terms/
 




---