home *** CD-ROM | disk | FTP | other *** search
- Here are some messages to read to get hints on installing the new
- shells (and windows) on a lan:
-
- #: 67427 S1/General Info/Misc.
- 24-May-90 06:29:27
- Sb: #67395-3.01 shgen problem
- Fm: Jeffrey R. Drumm 76655,3322
- To: Robert Wessel 75170,32
-
- SHGEN works fine off a local hard drive (and the network, I presume) if you
- place SHGEN.EXE in a directory all by itself, and all of the files supplied
- in DSWIN2.ZIP, as well as the IPX.OBJ file from DSWIN1.ZIP into a
- subdirectory named SHGEN-1 off of the directory in which SHGEN.EXE resides.
- Took a little experimentation to figure this out, but no problems since. If
- you've got third party LAN drivers to load, just make the appropriate
- sub-directory (LAN_DRV_.???) off of the directory in which SHGEN.EXE
- resides. Here's what I used:
-
- \NETWARE
- SHGEN.EXE (from DSWIN2.ZIP)
- \SHGEN-1
- Contents of DSWIN2.ZIP
- IPX.OBJ from DSWIN1.ZIP
- \LAN_DRV_.???
- *.LAN
- *.OBJ
- .
- .
- .
- It works fine for me. The new IPX.COM winds up in \NETWARE\SHGEN-1.
-
- For those who haven't yet bothered, DSWIN3.ZIP and DSWIN4.ZIP are most
- definitely worth the download time. The new MAP and LOGIN provide for false
- roots (and LOGIN has LOTS of other goodies) and NDIR seems to have speeded up
- (as well as received a menu interface). FLAG got a little buggered though,
- NRW is no longer a valid option (gotta use N all by itself instead).
-
- Jeff (@MaineMedical)
-
-
-
- #: 16115 S2/Upgrades
- 30-May-90 18:14:47
- Sb: #Install 3.01
- Fm: Andy Fraser 71301,637
- To: All
-
- Notes on how to upgrade your Novell shell with the upgrade disks:
-
- Download the four DSWIN files, unZIP them onto four floppies, and change the
- set the volume name of the floppies to the following:
-
- Disk contents Required volume name
-
- DSWIN1 doesn't seem to need a name
- DSWIN2 SHGEN-1
- DSWIN3 UTIL-1
- DSWIN4 UTIL-2
-
- In addition to the four DSWIN files, you will also need the .LAN and .OBJ file
- for the particular Ethernet card you have installed. You already have these
- files somewhere, or the person who originally installed your present Novell
- driver has them. The
- LAN and .OBJ files are likely on the SHGEN-1 or LAN_DRV disks used previously,
- probably not on your hard drive anymore.
-
- Copy the IPX.OBJ file from the DSWIN1 disk to the SHGEN-1 disk. Copy your .LAN
- file onto the SHGEN-1 disk. Have the Ethernet card's .OBJ file ready on a
- disk with the volume name of LAN_DRV_002 (it's possible your system will
- accept the file on the SHGEN-1 disk, or a LAN_DRV_001 disk).
-
- Before proceeding, reset your PCX without loading IPX or NETx. After it's up,
- type IPX then NETx (NET3 or NET4) and watch for what interrupt and Ethernet
- card I/O address is being used.
-
- Place the SHGEN-1 disk into drive A, change to drive A, type SHGEN.
-
- The screen will show a typical Novell window, and present various menus to
- chose the type of card, interrupt and card I/O address to use, and so on. It
- will then create the new IPX.COM file, and leave it on the SHGEN-1 floppy.
-
- Rename your old IPX.COM to, for example, WIN2IPX.COM in case the new one
- doesn't work. Also rename your NETx.COM file to WIN2NETx.COM (x is 3 or 4,
- depending whether you're using DOS 3 or 4).
-
- Copy the new IPX.COM onto your hard drive. Copy either NETx.COM, EMSNETx.COM,
- or XMSNETx.COM onto your hard drive, depending on whether you're going to be
- using NET in main memory, expanded (true LIM 4.0, not emulated) memory, or
- extended memory (up in HIMEM.SYS I expect). Change your AUTOEXEC.BAT or
- LAN.BAT file as required for the new NET file.
-
- [continued]
-
- There is 1 Reply.
-
- #: 16116 S2/Upgrades
- 30-May-90 18:17:06
- Sb: #16115-Install 3.01
- Fm: Andy Fraser 71301,637
- To: Andy Fraser 71301,637 (X)
-
- [continued]
-
- Re-boot your PC. Start Windows. The network should now be available there.
- The network drives will show up in the File Manager, the Print Manager will
- let you watch the network printer queue, and you can make a PIF file for
- Novell's mail.exe. Mail is also nicely integrated; when an express mail
- message is received, a window pops up in the middle of the screen announcing
- it's arrival.
-
- ..These procedures and observations were based on installing the shell on my
- AT with DOS 3.21, and using the plain NET file, and should be very close to
- what would work on your PC. Better than the (lack of) instructions Novell
- provided. I expect installing it on a 386 or using the extended or expanded
- NETs will also work fine, but haven't tried them yet. I also have not changed
- any of the files on the server, as discussed in DOC.TXT; I don't know whether
- they need to be if only a workstation is being upgraded.
-
- Hope this helps clarify what to do with that megabyte you've downloaded! It
- is nice to have Word 5, mail, and everything else available from Windows.
-
- -=Andy~
-
- #: 54635 S1/Servers & Workstn
- 29-May-90 20:29:40 Thread= Parent=
- Sb: #54596-3.01 SHGEN floppy frenzy
- Fm: Ken Jones 73135,1243
- To: ken westerback 73547,3520
-
- Say Ken,
-
- Clever, isn't it, that the docs talk about three disks, and there're FOUR Zip
- files... Inspect the docs and check to see which collection of files is a
- UTIL, which is a SHGEN or whatever, AND NAME THE FLOPPIES APPROPRIATELY using
- the DOS LABEL command. Works for me. and that fourth disk is a do it
- yourself public, I think.
-
- Cheers.
-
- #: 54493 S3/Printing
- 29-May-90 06:18:19 Thread= Parent=
- Sb: #54476-3.0 Shells
- Fm: Mickey Applebaum(Sys-Op) 76704,71
- To: John Thompson 76635,2062 (X)
-
- John,
-
- I personally would recommend upgrading ALL the stations to the new shells...
- There were some bugs in the 2.15 shells that have been fixed, and the new
- shells offer some new SHELL.CFG and command line features that weren't in the
- old shells. Also, if ANY of the machines you use are 80286 or 80386, or have
- EMS memory you can use the high memory shells and recover about 30k of RAM...
- For the EXTENDED memory machines (286/386) with more than 640k of RAM
- installed go to the IBM or MicroSoft forums and download the HIMEM.ARC file
- For the EMS systems, all you need is the new shell.
-
- * Reply: 54945-
-
- #: 55148 S3/Printing [***] Message 118 of 245
- 01-Jun-90 06:48:15 Prev= Thread=J486 Parent=J488
- Sb: #54945-3.0 Shells
- Fm: Jeffrey R. Drumm 76655,3322
- To: Al de la Torre 76416,551
-
- Well, if you use the HIMEM shell (XMSNETx.EXE), you can free up most of the
- amount of high memory that NETx.COM used when it was loaded high. Reserving
- 64K of EXTended memory with QEMM doesn't hit on your high RAM at all; you just
- lose 64K of emulated EXPanded memory. You might take a 6K hit on low RAM,
- though, if you don't have enough HI memory to initialize XMSNETx.EXE. The XMS
- shell loads HI OK (I tried it on my Compaq Portable/386), and only uses 6K of
- HI memory.
-
- The new shells get you the MAP ROOT feature, the ability to set a preferred
- server in SHELL.CFG, and some other goodies. Performance with the new shells
- is actually a little slower; 5-10% lower seems to be the norm.
-
-
- #: 55545 S1/Servers & Workstn [*T*] [***] Message 76 of 250
- 04-Jun-90 04:23:59 Prev=J411 Thread
- Sb: Windows 3.0 Swap File
- Fm: Sean Baxter 76044,1173
- To: ALL
-
- Hello Windows 3.0 networking fans, hear is another one of those hidden program
- facts you don't like to hear. It appears Win3.0 likes to have about a 4 Mb or
- more swap file (enhansed mode), preferably a permantent swap file. I called
- MS Windows support and they confirmed this fact and strongly recommned that a
- local hard drive be used for the swap file for each Win3.0 workstation. Can
- you imagine a 4 Mb swap file per user on the file server and all of that added
- NIC traffic.
-
- >> Sean <<
-
- * Reply: 55675-
-
- #: 55675 S1/Servers & Workstn [***] Message 77 of 250
- 04-Jun-90 18:54:19 Prev= Thread= Parent=
- Sb: #55545-Windows 3.0 Swap File
- Fm: Jeff Hofstetter 70365,110
- To: Sean Baxter 76044,1173
-
- Actually, you can disable swapping while in enhanced mode by putting
- "paging=no" into your [386Enh] section of SYSTEM.INI. This will (of course)
- disable the vitrual memory feature but on our network most folks find that
- 4meg is adequate for normal use and losing the virtual memory isn't too bad.
- ..Jeff
-
- #: 55539 S1/Servers & Workstn [*T*]
- 04-Jun-90 02:07:14 Thread
- Sb: #3.01 Shells with 2.12?
- Fm: Milton Taylor 75360,1516
- To: SYSOP (X)
-
- Can the new 3.01 shells be used with Advanced Netware 2.12?
-
- (I'll be a bit disappointed if we have to go through a rather
- expensive 2.12 -> 2.15 upgrade).
-
- -- Milton Taylor
-
- * Replies: 55552-, 55630-J35
-
- #: 55552 S1/Servers & Workstn
- 04-Jun-90 05:18:14 Thread= Parent=
- Sb: #55539-3.01 Shells with 2.12?
- Fm: Dave Kearns<Sys-Op> 76704,62
- To: Milton Taylor 75360,1516
-
- That's what upgrades are for, Milton. Should I be disappointed that they don't
- work with my 4.61's or my 1.01's?
- That said, there really shouldn't be a problem with 2.12....
-
- -dave
-
- * Reply: 55754-
-
- #: 71122 S3/NetWare 2.1x
- 12-Jun-90 20:49:14
- Sb: #71027-Shell 3.01 hangs
- Fm: Larry Cadloff (Hartco) 75120,16
- To: PANUG 76424,262
-
- Try using SETUP /I/N. There seems to be a problem with cards using 2E0 or
- possibly IRQ 2. The /I parameter forces SETUP to NOT attempt a hardware
- check. There's a mention of it buried deep in the manualsl; apparently a
- check for the 8514/A card can cause this problem with some ARCnet
- configurations.
-
- If that doesn't help, tried reconfiguring on workstation using a base address
- other than 2E0. Use that machine to run SETUP for everybody's account.
- Windows itself has no trouble running with the usual ARCnet configuration.
-
- --LC
-
-
- #: 18566 S14/On your Soapbox!
- 20-Jun-90 15:00:26
- Sb: TCC ARCNET & Windows 3.0
- Fm: Thomas-Conrad Corp. 75410,1407
- To: All
-
- Thomas-Conrad Arcnet Products and Microsoft Windows 3.0.
-
- We have found several parameters in Windows 3.0 that require setting to work
- properly in the Windows 386 ENHANCED mode in a Novell Network environment.
-
- One important step that should be done is if you are going to be using
- Interrupt (IRQ) 2 with an Arcnet card you must run the INSTALL program that is
- provided with Novell's new 3.01 shell. This INSTALL program will patch the
- Windows program to allow IRQ 2 to be used. Please note that this is provided
- by Novell for use with Microsoft's Windows 3.0 and has nothing to do with
- compatibility of TCC products.
- Another step you must do is to edit the Windows SYSTEM.INI file to
- include the Microsoft's EMMexclude=####-#### command to exclude the Base
- Memory address that your card will be using. Please see page 549 of the
- Windows 3.0 manual for more information on using this command.
-
- Additional information:
-
- If you will be using more than 1 megabyte of RAM for running Windows and will
- be wanting to use Extended Memory you may want to use the Microsoft command
- HIMEM.SYS (included with Windows) in your systems CONFIG.SYS file (see page
- 583 of the Windows 3.0 manual). Default values were used with our testing.
-
- You may use Thomas-Conrad Versions 2.20 and 2.12 Arcnet drivers for the
- Workstation shell. Please remember that you should use the new Novell 3.01
- shell to generate a new IPX. If you will be using Extended memory you will
- want to use either the XMSNET3.COM or XMSNET4.COM file depending upon which
- DOS you are using. If you are not using any Extended memory you will want to
- use either NET3.COM or NET4.COM.
-
-
- #: 60403 S14/New Shells/WIN 3.0
- 01-Jul-90 19:39:34
- Sb: #60370-Win3 & Ethernet
- Fm: Dennis Beach (Sys*Op) 76701,146
- To: Mark Winzenburg 76674,1430
-
- Windows 386 enhanced mode uses IRQ 2. If you are going to use 386 enhanced
- mode, there is a patch to leave Irq 2 open for your network card. In
- System.Ini you would change VPICD entry to VPICDA.386. Also copy VPICDA.386
- and .EXE from shells download to Windows directory. This has worked okay for
- some, but has not worked well for others. You may also need to include a
- statement in SYSTEM.INI to exclude the network cards address.
-
-
- #: 60945 S14/New Shells/WIN 3.0
- 04-Jul-90 22:19:51
- Sb: #60905-#Windows3 Booters
- Fm: Robert Wessel 75170,32
- To: Ed Wear 74017,1147 (X)
-
- Ed,
-
- Put the files from DSWIN1 and DSWIN2 into a directory called
- "\NETWARE\SHGEN-1", then copy SHGEN.EXE into "\NETWARE" and run it from that
- directory.
-
- Or, copy all the files (from DSWIN1 & 2) on to a floppy with the label
- "SHGEN-1".
-
- -Robert
-
- There is 1 Reply.
-
- #: 60947 S14/New Shells/WIN 3.0
- 04-Jul-90 23:13:05
- Sb: #60905-#Windows3 Booters
- Fm: Allan Puariea 71020,2431
- To: Ed Wear 74017,1147 (X)
-
- Ed:
- Download DSWIN0.TXT. So many people asked this same question that a txt
- file was added to explain it. <Al>
-
- There is 1 Reply.
-
-