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 [ 21 | April | 2006 ]

<< Previous Message << >> Next Message >>


Date: Fri, 21 Apr 2006 07:55:24 PST8
From: Zdenek Jizba <jizba@verizon.net >
Reply-To: scoug-help@scoug.com
To: scoug-help@scoug.com
Subject: SCOUG-Help: detecting hard disk

Content Type: text/plain

Steven Levine wrote:

>In <4447D45A.3060107@verizon.net>, on 04/20/06
> at 11:36 AM, Zdenek Jizba said:
>
>
>
>>I have DFSEE. I used it to define a boot partition and a partition for
>>eCS, but
>>the installation of eCS still does not recognize the hard drive.
>>
>>
>
>This is expected, assuming you were working from the bootable dfsee CD.
>It's going to use BIOS I/O, which by definition, has to understand how to
>run the SATA controller.
>
>The problem you have is that your hardware is too new for drivers on the
>eCS 1.2 CD. However, the drivers on the eCS 1.2 Media Refresh CDs should work.
>
>
>
When you say Media Refresh do you mean eCS 1.2R? That is the only other
bootable
eCS 1.2 that I have.

>
>
>>> 3. Used LVM to partition the SATA drive as LVM aware
>>>
>>>
>>>
>>Same problem with LVM as with DFSEE.
>>
>>
>
>Huh? You just said you used dfsee to partition the drive. What do you
>really mean?
>
>
>
With DFSEE I can access the hard disk and make partitions. However doing so
does not enable my eCS 1.2 CD installation to recognize the existence of
that
hard drive.

>>I think that the BIOS does recognizes my SATA drive, but I am not sure.
>>
>>
>
>If the BIOS does not recognize the drive you have a hardware problem, but
>I doubt this is the case. The BIOS screen will show what is recognized.
>Position the cursor to the "auto" field and press enter.
>
>
The BIOS does recognize the hard drive. Here is what it displays:
Primary IDE Master [LITE-ON CD-RW SOHR]
Primary IDE slave (not detected)
Third IDE Master [WDC WD800JO-00CSA0]

>
>
>>My DFSEE is on a small size CD. I use it on booting the PC, but lately I
>>have
>>been getting error messages such as: OS/2 !! SYS01475 and OS/2 !!
>>SYS02027
>>
>>
>
>The CD or the drive is probably dirty.
>
>
I do not think so. I get these error messages whenever the boot sequence
does not begin with the CD reader.

>
>Steven
>
>
>
You probably can tell that I am confused, which is true, but I am learning
(slowly) but it is frustrating and all help is greatly appreciated.

Denny Jizba

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

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
"postmaster@scoug.com".

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


<< Previous Message << >> Next Message >>

Return to [ 21 | April | 2006 ]



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.