SCOUG Logo


Next Meeting: Sat, TBD
Meeting Directions


Be a Member
Join SCOUG

Navigation:


Help with Searching

20 Most Recent Documents
Search Archives
Index by date, title, author, category.


Features:

Mr. Know-It-All
Ink
Download!










SCOUG:

Home

Email Lists

SIGs (Internet, General Interest, Programming, Network, more..)

Online Chats

Business

Past Presentations

Credits

Submissions

Contact SCOUG

Copyright SCOUG



warp expowest
Pictures from Sept. 1999

The views expressed in articles on this site are those of their authors.

warptech
SCOUG was there!


Copyright 1998-2024, Southern California OS/2 User Group. ALL RIGHTS RESERVED.

SCOUG, Warp Expo West, and Warpfest are trademarks of the Southern California OS/2 User Group. OS/2, Workplace Shell, and IBM are registered trademarks of International Business Machines Corporation. All other trademarks remain the property of their respective owners.

The Southern California OS/2 User Group
USA

SCOUG-HELP Mailing List Archives

Return to [ 12 | September | 2003 ]

>> Next Message >>


Date: Fri, 12 Sep 2003 00:05:39 PDT7
From: "Steven Levine" <steve53@earthlink.net >
Reply-To: scoug-help@scoug.com
To: scoug-help@scoug.com
Subject: SCOUG-Help: started out well, went downhill fast

=====================================================
If you are responding to someone asking for help who
may not be a member of this list, be sure to use the
REPLY TO ALL feature of your email program.
=====================================================

In <3F617520.7E9A1ED5@pacbell.net>, on 09/11/03
at 11:24 PM, "J. R. Fox" said:

>O.K., so I'm assembling this small form factor system. Followed the
>step-by-step
>instructions for the hardware, and it all seemed to be going together
>pretty well.

You need to fix the line wrap settings on your WinXX Netscape setup. A
message half-full of lines with one or two words is hard on these old
eyes.

>it had never been unpacked. The old one was a boot h/d, and I'm pretty
>sure it was
>set as HD-0, though I still need to confirm that.

Yes, you do.

>ASPI8U2.SYS and ASPI8DOS.SYS. (On their website, Adaptec has a U160DOS

For reference, here's what worked last time I booted DOS on this box:

config.sys has:

device=c:\ezscsi\aspi8u2.sys /d
device=c:\ezscsi\aspi8dos.sys /d

which corresponds to:

9-16-99 3:03 37,984 0 ASPI8DOS.SYS
12-06-99 10:11 44,872 0 ASPI8U2.SYS

>were among the ones I tried.) What's weird is that if I boot DOS off of
>a floppy,
>*without ANY* of the ASPI files, I can see the DOS C:, even run some
>programs
>on it.

Sure. What else would you expect to happen? You are using the same SCSI
BIOS that allows you to boot the C: partition (if you had it working).
Since it's only a 9GB drive, you can probably access all the visible
partitions with just the BIOS IO routines.

>I think I have all the correct settings set in the Award Bios, and in the
>29160 Bios.
>One thing I noticed right away was that, at boot time, the drive "signs
>on" only with
>its make and model #, **not** with anything like the _additional_
>"ULTRA-2 LVD"
>I'm used to seeing flash by on my U2W-based desktop system. A cabling
>issue ? I dunno,

Cabling would be my first suspect and and termination. You need to get
into the SCSI BIOS and look at this stuff when it's not flashing by.

>that if you move
>an existing drive to a new controller, you will need to re - low-level
>the drive. But I doubt

I suspect the wording is "may" need to. This not so much of a problem
these days since almost everything uses the same maximal LBA translation
values. Also, they probably mean other vendor's HBAs.

>that's what's going on here. The U160 is supposed to be backwards
>compatible with earlier
>Adaptec models.

You are making assumptions as to what the definition of backwards
compatible means to Adaptec.

>ID ahead of time, but the on-the-HA utilities pick it up as factory set
>at ID-6, so I set it
>to that for booting purposes.

That's probably not the best for boothing DOS.

Rule one when assembling a new system. Don't bolt together anything that
doesn't require it until you are sure everyone wants to play nice
together. If it was me, the hard drive would be sitting next to the case
on a piece of cardboard until it was functioning correctly with the rest
of the hardware.

>or OS/2 is going to be viable on the drive either, under these
>circumstances.

I wouldn't conclude that. I would try a proper set of DOS boot diskettes
and a proper set of OS/2 boot diskettes and I would spent some time with
dfsee to understand the drive characteristics.

>no way I can see to get extra cooling in there. I don't even have the
>cover on yet, so it's only going
>to get hotter.

This may be a problem. Blade servers are designed to keep the SCSI drives
cool. It appears that your box was designed for IDE.

>I am almost looking foward to grappling with the various eCS setup
>issues, but first things first. Gotta
>get the basic hardware side squared away.

At this point, I'm not so sure that you don't have a MB issue.

Does the 29160 and the drive work when plugged into another box with
proper drivers?

Steven

--
----------------------------------------------------------------------
"Steven Levine" MR2/ICE 2.37 #10183 Warp4/FP15/14.093c_W4
www.scoug.com irc.webbnet.info irc.fyrelizard.org #scoug (Wed 7pm PST)
----------------------------------------------------------------------

=====================================================

To unsubscribe from this list, send an email message
to "steward@scoug.com". In the body of the message,
put the command "unsubscribe scoug-help".

For problems, contact the list owner at
"rollin@scoug.com".

=====================================================


>> Next Message >>

Return to [ 12 | September | 2003 ]



The Southern California OS/2 User Group
P.O. Box 26904
Santa Ana, CA 92799-6904, USA

Copyright 2001 the Southern California OS/2 User Group. ALL RIGHTS RESERVED.

SCOUG, Warp Expo West, and Warpfest are trademarks of the Southern California OS/2 User Group. OS/2, Workplace Shell, and IBM are registered trademarks of International Business Machines Corporation. All other trademarks remain the property of their respective owners.