Specifically where I can ask for help with the following problem:
I am installing 3.12 on a new server with two IDE hard drives. IDE 0 is a
Western Digital 6Gb and IDE 1 is a Maxtor 7.5Gb.
Both drives are recognized by CMOS and I can access either one in DOS.
The first drive (WD) is the C: drive (the D: is the Max).
When I load install.nlm, I can see the Western Digital, but NOT the
Maxtor. I want to create a volume that spans both drives, or barring that
create multiple volumes on both drives.
I apologize if this is bad ettiquette, but I need help ASAP.
Thanks in advance,
Carl K.
Carl
"Barry Schnur" <bsc...@cox.net> wrote in message
news:qfnrjuccg8a9qcesu...@4ax.com...
> >Specifically where I can ask for help with the following problem:
> >
> >I am installing 3.12 on a new server with two IDE hard drives. IDE 0 is a
> >Western Digital 6Gb and IDE 1 is a Maxtor 7.5Gb.
> >
> >Both drives are recognized by CMOS and I can access either one in DOS.
> >
> >The first drive (WD) is the C: drive (the D: is the Max).
> >
> >When I load install.nlm, I can see the Western Digital, but NOT the
> >Maxtor. I want to create a volume that spans both drives, or barring
that
> >create multiple volumes on both drives.
> >
> You do not want to set up a volume spanning both drives -- trust me on
this
> one -- if either drive goes bad, the entire volume is toast.
>
> Regarding the drives and seeing them in NetWare -- are these drives both
> connected to the primary controller, or is one connected to the secondary
IDE
> controller.
>
> Also, what drivers are you using for IDE drive support?
>
>
>
> Barry Schnur
> Novell Support Connection Sysop
>
> Please post replies ONLY via the Newsgroup
(oh and BTW, thank you for taking the time to work with me on this)
Carl
"Barry Schnur" <bsc...@cox.net> wrote in message
news:qfnrjuccg8a9qcesu...@4ax.com...
> >Specifically where I can ask for help with the following problem:
> >
> >I am installing 3.12 on a new server with two IDE hard drives. IDE 0 is a
> >Western Digital 6Gb and IDE 1 is a Maxtor 7.5Gb.
> >
> >Both drives are recognized by CMOS and I can access either one in DOS.
> >
> >The first drive (WD) is the C: drive (the D: is the Max).
> >
> >When I load install.nlm, I can see the Western Digital, but NOT the
> >Maxtor. I want to create a volume that spans both drives, or barring
that
> >create multiple volumes on both drives.
> >
If you want to use the latest ham drivers or use IDE drives greater than
8 gig you need to do the following and DO NOT USE BOTH IDE DRIVES ON THE
SAME CHANNEL.
1. Do NOT use LBA in the bios. Set the option to NORMAL
2. Create a 100 MB Dos drive with Dos 6.22
3. Install Dos
The following will speed up your install process if you have the CD-ROM
copies of NetWare and the 3.2 enhancement pack:
4. Xcopy the Netware.312 directory to the C: drive
5. Xcopy the 32enh directory off the 3.2 enhancement pack CD-ROM
If you xcopy the files to the drive, you'll not need to load the CD-ROM
drivers
6. Install NetWare
7. Create a 500 MB NetWare partition and use the ide.exe update dsk
driver
8. Install NetWare by using the install.nlm that is located at:
c:\netware\________\BC
command at the console prompt: load c:\netware.312\________\BC
\install.nlm
This will allow you to copy the system files from the C: drive Copy the
system files from the netware.312\english directory
9. Reboot the server
10. Install the 3.2 enhancement pack by using the install/product option
and point the install to c:\32enh
11. When the 3.2 enhancement pack is installed reboot the server
12. Download and install the 3.2 minimum patch listing from here:
http://support.novell.com/misc/patlst.htm
13. When the 3.2 minimum patch list is installed the server.exe file can
now use the HAM drivers that are in the NWPAUP1A.EXE file. This will
allow full use of your EIDE drive.
Now the part you'll not like:
14. Down the server and use the Dos fdisk.exe command to remove the
NetWare partition.
15. Install NetWare
16. Install the 3.2 enhancement pack
17. Install the 3.2 minimum patch list
You may have to perform the lswap procedure to recognize all the ram that
is in your machine also:
The possibility that the server.exe in the DOS partition did not get
updated. This the procedure to update the server.exe:
LSWAP EXE
============
The defaults used in the command lines are from NetWare 4.1x handling so
for
the typical 3.12 server update, if it does update automatically, you will
need to not only run it manually, but make sure that you use the correct
path
setting.
Both LSWAP.EXE and LSWAP.NLM use the same command line options. First
option specifies the location to LOADER.EXE.
(DEFAULT:C:\NWSERVER\LOADER.EXE).
The second option specifies location to SERVER.EXE or MSERVER.EXE.
(DEFAULT: C:\NWSERVER\SERVER.EXE).
So, it the typical scenario where you need to run this manually from the
DOS
prompt in the C:\Server.312 directory, you need to do the following:
1) Make sure that both LSWAP.EXE and LOADER.EXE are in the Server.312
directory.
2) Then use the following command syntax:
LSWAP C:\SERVER.312\LOADER.EXE C:\SERVER.312\SERVER.EXE
3) When this is done, you should end up with a SERVER.EXE with a new date
and
a copy of the old server.exe as SERVER.OLD with the old date.
--
Felton Green (SysOp)
Novell Support Connection Forums
First -- apply all current 312 updates:
NetWare v3.12 (Newest to Oldest) Available From:
http://support.novell.com/filefinder/147/index.html
ODIWAN1.EXE ODI WAN update to support ODI 3.31 30MAR2000
TCP312.EXE Common TCPIP.NLM for NW 3.12 30MAR2000
IPX660.EXE IPX Updates for NetWare 3.1x/4.1x 30MAR2000
ODI33G.EXE LAN Drivers 30MAR2000
STRTL8A.EXE STREAMS.NLM & TLI.NLM 30MAR2000
CLIBAUX1.EXE Updated Clibaux.nlm 08DEC1999
312PTD.EXE NetWare 3.12 OS Patches 22NOV1999
TTSY2K.EXE Y2K update for TTS 02NOV1999
312Y2KP2.EXE NetWare 3.12 Year 2000 fixes 28SEP1999
LIB312D.EXE CLIB Updates for NetWare 3.12 20SEP1999
AFP11.EXE NetWare for Macintosh 3.12 update 12JUL1999
NWPAUP1A.EXE Latest NWPA/HAM/CDM/CDROM Support 08JUN1999
CDUP5A.EXE CDROM.NLM (pre NWPA) updates 04MAY1999
PU3X01.EXE Print Utilities 02FEB1999
SBACK6.EXE SBACKUP.NLM and supporting files 02FEB1999
LANDR9.EXE LAN driver updates 02FEB1999
SMSUP6.EXE SMS Functions Updated 02FEB1999
LANDR9.EXE LAN driver updates 02FEB1999
MPR31B.EXE NetWare Multiprotocol Router 09JAN1998
VRP386.EXE Vrepair Updates for 3.12 31JUL1997
NAM312.EXE OS2 and MAC NameSpace Updates for 3.12 29OCT1996
ATK307.EXE AppleTalk Protocol 29JAN1996
MON176.EXE MONITOR.NLM v1.76 18SEP1995
PS3X02.EXE Print Server 30JUN1995
PBURST.EXE Packet Burst Update 14JUN1994
Note, I'd apply the LIB312D update first.
You will find that the NWPAUP1A.EXE update (which requires Lib312D and 312PTD
to be in place) includes updates for EIDE support (IDEATA.HAM driver set)
For 3.12 you should not use IDE.DSK, instead, patch the server current, then
use IDEATA.HAM instead.
Because you are using both controller, you need to load the IDE driver
re-entrantly.
For the secondary controller (assuming you get IDEATA.HAM drivers in place),
this would be:
Load IDEATA.HAM Port=1F0 INT=F
Note, until you get current patches in place, you do NOT want to load support
for the secondary controller (at INT=F (IRQ15), as that is problematic with
3.12 unless you are using the NWPA drivers (IDEATA.HAM is one of these) which
you can't use until the server OS is updated.
Carl
"Barry Schnur" <bsc...@cox.net> wrote in message
news:bbqrjuov7dakfuico...@4ax.com...
This would include updates to Monitor, Pserver, that sort of thing.
Yeah.. but I like to let the others who read the newsgroup have the
information.
[isn't that a good recovery? } %^ )
Here is what I do:
I make the following directories:
c:\patches\system\4\nls
c:\patches\system
c:\patches\login
c:\patches\public
c:\dosdrive\server.312
I download all the updates and expand them out, oldest to newest one at a
time. Them I move the updated files into the directory they belong in.
system, public, login etc.
the dosdrive will be on the C: drive where the server.312 directory is
and they'll need to be loaded when the server is down. When all the files
are moved, except for the updates that require a separate install you can
xcopy the files from the patches directory to the server sys vol.
i.e. xcopy c:\patches\*.* f:\ /v /s /e
and then you're off and running.
Carl
"Felton Green (SysOp)" <felton...@bigfoot.com> wrote in message
news:Tln%8.53$XL3...@prv-forum2.provo.novell.com...
Use the little shortcut Felton provided it'll save you a lot of time.
You might well get away with loading the IDE.DSK drivers and using them to
partition and create volumes. The use of the IDE.DSK drivers will let you
set up and patch in one operation. After you're all patched to date switch
to IDEATA.HAM drivers. If you see funky dates or less memory than is in the
box after patching run LSWAP.
Listen to Barry don't span a volume across two drives. Make your Sys:
volume 1 gig and no larger *unless* you have a really compelling reason.
--
Dave Lunn
NSCV Sysop
http://support.novell.com
Carl
You downloaded and installed all those updates? kewl..
You're welcome also...