R1KAB@AKRONVM.BITNET (Kevin Butler) (02/08/90)
When I execute IPX and NET3 on a true blue AT, the network drive is F:. If I change to drive f:, I am in the LOGIN directory. When I execute IPX and NET4 on a PS/2, I must change to H: to get the LOGIN directory. I would like everyone to have to go to the F: drive in order to login. This makes programs and instructions machine independent. The PS/2 has device drivers for extended memory and virtual disk. The AT does not. How does Netware shell determine which drive to assign to the network? SFT Netware Version 2.15A, Server is IBM PS/2 Model 80. Thanks. Kevin Butler, Programmer/Analyst, Computer Based Education, Univ. of Akron.
MARK@CCCLAN.BYU.EDU (Mark Ungerman) (02/08/90)
You can use DOS command LASTDRIVE to set where your network drives will begin. This command is issued in the CONFIG.SYS file and has the syntax LASTDRIVE= x where X is any letter A through Z. If you specify LASTDRIVE = G then your network drives will begin with H: Good Luck! Mark Ungerman Technical Coordinator BYU Computer Consultation Center
BEEBE@YALEMED.BITNET (Rick Beebe) (02/08/90)
>When I execute IPX and NET3 on a true blue AT, the network drive >is F:. If I change to drive f:, I am in the LOGIN directory. > >When I execute IPX and NET4 on a PS/2, I must change to H: to get the >LOGIN directory. > >I would like everyone to have to go to the F: drive in order to login. >This makes programs and instructions machine independent. The PS/2 >has device drivers for extended memory and virtual disk. The AT does not. > >How does Netware shell determine which drive to assign to the network? >SFT Netware Version 2.15A, Server is IBM PS/2 Model 80. Thanks. > >Kevin Butler, Programmer/Analyst, Computer Based Education, Univ. of Akron. Netware uses the next available, non-reserved-by-DOS drive. On most machines, DOS reserves drives a: - e:, hence netware comes up with drive f: My guess is that your virtual disks are taking drives f: and g: _OR_ there is a "lastdrive=g:" in the config.sys file. There are a couple of ways around this. 1) put "lastdrive=g:" in the config.sys of your AT's. That will make netware start with H: on those machines as well. The other way is to put the command "DRIVE H:" in the system login script. That forces the current drive to be H: instead of F: The first one is the more useful if you have automatic login batch files, because netware will start with H: on all machines. It's a little harder to implement, because you have to modify all the machines' config.sys files. The second one is a one-shot change, but it doesn't help the machines _before_ they actually log in. ----------------------------------------------------------------------------- Rick Beebe (203) 785-4566 ***** ***** ***** * * Biomedical Computing Unit * * * ** * Yale University School of Medicine * * *** * * * 333 Cedar Street, New Haven, CT 06514 * * * * ** * * * * * BEEBE@YALEMED.BITNET beebe%biomed.decnet@venus.ycc.yale.edu -----------------------------------------------------------------------------
Tim_Munro@CARLETON.CA (02/08/90)
NETx uses the LASTDRIVE= line in your config.sys, for regular Dos
the lastdrive defaults to e:, it looks like os/2's lastdrive defaults
to g:. So, if os/2 has a config.sys type setup then place lastdrive=e
in the config and then LOGIN should go to F:.
Tim <Tim_Munro@carleton.ca> Fax:(613) 788-4448
Voice:(613) 788-3722rick@OFA123.FIDONET.ORG (Rick Ellis) (02/09/90)
>How does Netware shell determine which drive to assign to the network? >SFT Netware Version 2.15A, Server is IBM PS/2 Model 80. Thanks. You should be able to switch to any invalid drive and be placed in the network login directory. -- Rick Ellis ...!{dhw68k,conexch}!ofa123!rick rick@ofa123.FIDONET.ORG 714 544-0934 2400/1200/300 [PCP: CASAN]