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 [ 06 | March | 2004 ]

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


Date: Sat, 6 Mar 2004 09:48:50 PST8
From: "Steven Levine" <steve53@earthlink.net >
Reply-To: scoug-help@scoug.com
To: scoug-help@scoug.com
Subject: SCOUG-Help: (Crossposted from ecs group) Can't install eCS 1.1 to TP 600E

=====================================================
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 <200403060928.5775246.6@scoug.com>, on 03/06/04
at 09:28 AM, "Dr. Jeffrey Race" said:

>> fdisk /query:bootable

> :) FDISK
> SYS1041 The name fdisk is not recognized as an internal or
> external command

You have used OS/2 long enough to know that you need to use a set of Warp4
diskettes to run this.

>[as run from command console of eCS CD#1]

>>
>>or
>>
>> lvm /query:bootable
>>
>>report?

> Logical Volume Type Status File System Size Z:
>ecs Memory-Boot-Disk FAT 16 Compatibility FAT16 7

There's something going on with your partitioning and/or BIOS that is
preventing eCS from believing that the volumes above 1024 are bootable.
The installer is forced to use the information is has available.

>MBR ?

Master boot record. How long have you been using PCs? Also, there's
always Google.

Try:

lvm /newmbr

This will rewrite the MBR code with what is supplied with eCS.

>BM: Using IBM BM installed from eCS CD #1

Perhaps it did not really get installed. Using the command line LVM.

- start LVM
- delete BM
- save and exit
- start LVM
- install BM

Does this change the symptoms?

>Yes I used Partition Magic as instructed in the eCS installation manual
>(and which worked fine for eCS 1.0 install).

This usually works, but nothing with computers is 100%. Green is a color,
but then again, so it red. They are not the same thing.

>More ideas?

Let me know the results of refreshing the MBR and BM. If this does not
resolve the problem, we are probably going to need to use dfsee to get a
more detailed view of partitioning.

Regards,

Steven

--
----------------------------------------------------------------------
"Steven Levine" MR2/ICE 2.41 #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".

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


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

Return to [ 06 | March | 2004 ]



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.