Conference noted::windows95

    If you've got an NT Server CD (a real one, not the DEC one), look in
    the CLIENTS directory - there's a DOS LAN Manager 3.0 client in there
    that might fit on a floppy, I believe
    

    I asked the same question in the IBM-PC conference (albeuit regarding
    NT installation).
    
    .1 is one possibility (but you obviously need some kind of bootable
    floppy - the server kit only contains the network files).
    
    The other possibility (if you don't have access to the above) is to
    copy the required files from Microsoft's ftp server - they are freely
    downloadable.
    

RE: -.2   No gots....

RE: -.1  I looked at at ftp.microsoft.com and came up with -

ftp://ftp.microsoft.com/bussys/Clients/MSCLIENT/
        and found dsk3-1.exe & dsk3-2.exe
        Is this what I need?  The README.NOW file in /bussys/Clients
        dosn`t mention anything about Netbeui.....

        I`m having trouble downloading disk1, I always get 
        a partial file, usually ~64k out of 844k....

Rich M.
(milkwy::meyer)

An update -

        First a little background.  The pc I am testing this on is
        a P-166 with a EtherExpress-16 card with 3 hard drives.  The first
        2 drives are on the primary IDE bus, they are set-up with full
        Win95.  The 2 node Lan works perfectly and is connected to a P-133
        running Win95 with Netbeui.  For this test I didn`t want any
        chance of messing up the P-166 Win95 installation so I disable the
        drives on the primary bus in BIOS, giving C: boot up on the 
        third drive.  This drive has simple (format/s) win95 boot up
        (no GUI).  For reference, the P-166 is called PC-1, the P-133
        is called PC-2.  The P-133 will be running  Win95 with all
	the usual GUI, Netbeui, etc....

        Well the MSClient disks were not what I wanted, so I pulled over
        the Lanman22c disks.  These seemed to work.  Well, after a few
        hours of poking & proding I got it to work-

        1) The installation bombed out extracting "netwrksta". 
            On first boot I got an error saying netwrksta.exe could not
            be found.  I found netwrksta.500 and renamed it to netwrksta.exe
            and copied it to the lanman.dos\program directory.  This 
            seemed to fix that as no boot errors occurred.

        2) The last line in autoexec.bat is - net logon PC-1 *
           An error always occurs saying a server could not be found,
           check cables, bla-bla-bla....
           This is where I spun my wheels for ~1hr, I understand the need
           for the workstation to tell the Lan it is alive, I can`t figure
           out why a password is always needed.  Plus the error is misleading
           I knew the cable was fine & the "server"(PC-2) was up so I spent
           some time making sure the NIC was set properly in protcol.ini.  
             Finally I typed in -
                   net use d: \\pc-2\c
                the connection works, I saw the C: drive on PC-2 (as D:)
                was able to to get dirs, & copying.

        3) One of the tests I did was to xcopy/x/c a whole directory tree to
           the server, after a short time both system hung and a hard
           boot to both had to be done.  Could this be because I`m using
           16bit drivers (lanman22c) in a 32 bit environment?  Copying
           (with the copy command) to/from server worked fine.
           I wonder if I should just boot to dos 6.22 on the workstation.
                (it dosn`t matter to me)


        Now the next challage is to get all this to fit on a 1.44m floppy...

Rich M.
(milkwy::meyer)

    I've done this. I've got the whole setup on a 1.44 floppy.  I use a
    cheap-o network card (computer show..$25).  The disks I used to set it
    up are from the NT 3.51 client install kit.  It is a 2 disk set that
    you use to install to a hard drive and then boot the machine and make a
    netbeui connection on a participating server.  I just boot to the 1.44
    and make a network connection on my Win95 system and copy directly off
    the Win95 directory onto the win95 directory on the local c drive.  The
    client disks were available on dec's net somewhere over in Cleveland I
    believe.  i just copied them from the net.
    L8tr..
    Steve m..
    ps.. Just used this setup again last week.  Worked great.  The only
    specific thing you need is to worry about putting the lan driver for
    your specific card on the disk and configuring it correctly.  
    ps... I could contract out my network service if you need it ! 
    pss... If you need the disks i probably could put them on a server for
    you somewhere. 

    I got it going last night.  The Lanman22c install has two choices,
    basic & exteneded.  I was originaly installing the exteneded.  Did
    a RTFM, found I should have done basic install.  Every thing works now.
    I just chopped out a few un-needed files from the lanman.dos directory
    that install created, and had plenty of room for doskey, mouse, himem
    emm386, etc...  It was so easy to run the install I ended up making two
    boot/netbeui floppies, 1 for the Ether Express-16 card in the P-166, and
    one for the generic (ACCTON) Ne2000 card in the P-133.  I`m ready
    for the next card/connection.

>>    ps... I could contract out my network service if you need it ! 
    I think there is a clash of ideas here... There is a method to my
    madness, I wouldn`t be doing thi$ ju$t to $ay I can do it... ;-)

>>    pss... If you need the disks i probably could put them on a server for
>>    you somewhere. 

    If they are better/newer than what I have, I`d be interested...;-)

Rich M.