Organization: University of Southwestern Louisiana
Newsgroups: bit.listserv.novell
Date:         Mon, 14 Dec 1992 17:42:14 CST
Reply-To:     Novell LAN Interest Group <NOVELL@SUVM.BITNET>
From:         Guruswamy Karthikeyan <kxg8272@USL.EDU>
Subject: Re: Novell Programming Environment (hints, please.)

In article <9212130334.AA15837@umbc7.umbc.edu> you write:
>Hey..
>
>I designing a programming environment which will focus on netware programming,
>and other general purpose network related stuff.  The packages I've been
>looking at are Borland's DOS/WINDOWS IDE w/ Application Framework, Watcom C/386
>compiler kit, and Microsoft's C/C++ v7.x kit.
>
>Does anybody have any preferences as far as compiler systems, any hints
>and/or tips, other related (or unrelated, for that matter) suggestions?
>All info is appreciated.  Thanks.
>
>Dave

Hi,

I would put a couple of things in your wish list (and mine too ...)

(a) I'll put SCSI express on the 3.11 server and put a Microsoft Programmers
    Library there (What's Netware without DOS ?) so that the users can hit
    a hot key and cut and paste some source code from Microsoft Encylopedia.
    You might want to have C-source libraries on-line. If your software needs
    expression parser you can yank it on-line ...
(b) Put the Ralph's brown interrupt list and a tsr hotkey program to get the
    API online (syntax stuff) on your Borland C workspace.
(c) If you are developing NLMs I would put a low-key Netware 386 system
    (plain vanilla) for testing and one for intense use. If you can afford it
    it's good to have a Netware 2.15 also so that you can test VAPs kindof
    stuff. Its good to test your programs on both versions of Netware before
    you give to someone. Who told you that 3.11 is upward compatible fully ?
(d) I'll want to have different ethernet cards on each system I use so that
    I can test my ODI/Packet-driver/NDIS stuff on each one of them. Split
    the network to token-ring and ethernet and use low-key old version
    programs or tools so that they are guaranteed to be acceptable by others
    who havent upgraded to the latest stuff.
(e) In general keep the network as heterogenous and non-standard as possible
    so that chances of your software being run elsewhere w/o problems is
    99.99 %.
(f) I would put a sniffer in my network.
(g) Internet access and IP bridge for SOS in comp.sys.novell (8!)
(h) Source code tracking with periodic backups on users different development
    stages. Tape backup in a cool 1 Gbyte media.

** Dont forget site license in CD-ROM sharing - I dont know. Is there any ?

Karthik
/----------------------------------------\--------------------------\
| Karthikeyan Guruswamy                  | I survived               |
| Graduate Student, Computer Science     |                          |
| Center for Advanced Computer Studies   |    HURRICANE ANDREW .... |
| Univ. of SouthWestern Louisiana        |                          |
| Lafayette, LA 70501                    |                          |
| Email: jmfres11@ucs.usl.edu            |                          |
|                                        \--------------------------\
| The opinions stated are solely mine and does not reflect the views|
| of anyone in my organization ...                                  |
\-------------------------------------------------------------------/
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU