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 [ 07 | June | 2003 ]

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


Date: Sat, 7 Jun 2003 12:13:40 PDT7
From: waynec@linkline.com
Reply-To: scoug-help@scoug.com
To: scoug-help@scoug.com
Subject: SCOUG-Help: Need Netware requester setup help

Content Type: text/plain

=====================================================
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.
=====================================================

Steven Levine writes:

> In <20030605074757.86220.qmail@courtney.linkline.com>, on 06/05/03
> at 12:47 AM, waynec@linkline.com said:
>
> If you haven't fixed this yet...
>
>>Also there were some config.sys entries of a type that were unfamiliar
>>to me, and a lot more networking entries than I'm used to seeing. I
>>tried manually adding the files I knew should be there to config.sys and
>>the os2\boot folder, but I keep getting the same logo-screen hang.
>
> You need to use Alt-F2 to see which driver is hanging. Also, if you
> needed an updated kernel and/or drivers to get the boot diskettes to work,
> you need to be sure that the expected versions got copied on to the boot
> drive. Keep in mind you are using an installer that was implemented in
> the mind '90s. It may need some help to do the right thing in 2003.

I did use Alt-F2, and I did copy the missing drivers to the hard drive
folders. I found a paragraph in the ibm1s506.add instructions that said it
can hang on certain notebook motherboards, and maybe others, and it
recommended changing parms on it's config.sys statement. That got me to
another hang ...can't recall for certain right now which driver, may have
been Sony31a, which I rem'd in the diskette config.sys to get the diskettes
to boot. I changed the same statement on the hard drive's config.sys.

I have since found that I'm apparently back to the ide problem again... I
can only boot Warp from the scsi drive with the ide drive power plug pulled.
When booted from diskettes, Fdisk (the latest version I found, dated
11/15/00, invoked off the diskette or from the Warp os2\boot folder) says
there's something wrong with the master boot record on the ide drive and
will not show partitions or replace the mbr (deja-vu all over again).
ibm1s506.add is dated 12/20/02, and os2dasd.dmd is dated 9/6/02

This problem is getting very very very very tiresome... thought I had a
handle on it a week ago, but now I'm back to square 1. Bios shows the ide
drive geometry the way it was when we finally got it corrected after finding
that bios error, and ptedit utility seems to show only partition codes that
Warp understands; there is only one empty logical partition (hpfs) on the
ide drive, about 10gb into the drive. Several versions of PQmagic see it
correctly, and I did not try to change it with PQmagic.

I am considering using the WDC install diskette utilities to write zeros
across the whole ide drive, then boot Warp from my tailored diskettes
(assuming it WILL boot at that point) and use fdisk to create one hpfs or
fat16 partition on the drive.

How do you think I should proceed?

>
>>in the P2, so that's probably how I got them mixed up, although I
>>thought I heard somewhere that the protocol.ini address doesn't have to
>>match the actual card address.
>
> Some NICs will allow you to override this, although it gets very
> interesting if you do this and have two NIC with the same address on the
> same network.
>
>>Never had those entries in the past... I tried them tonight, then took
>>them back out when it still wasn't working. I'll put 'em back in if you
>>really think they're needed.
>
> I'm not sure what the defaults are. I have needed them in the past for
> "special" servers. Some Netware admins did strange things.
>
>>Another question... I remember at one time having specified "netbios"
>>protocol on the NIC, at someone's advice, but I don't remember why.
>
> You will want NetBIOS if you are going to use the Peer LAN networking or
> if you are going to run a CID server.
>

Thanks.

Wayne

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

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 [ 07 | June | 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.