rogers@ux1.cso.uiuc.edu (Bill Rogers) (03/18/91)
We are trying to use the packet driver (version 7.6) for the western digital 8003eb board. If we boot from the floppy in which we did the dosgen then everything works fine. Using the remote reset, the autoexec exits after net3 and won't do the following login command. Everything else works fine after that. I've tried several hundred variations on this theme, but not the right one. Can anyone help? Here is the last version I tried: config.sys: buffers=25 files=40 lastdrive = e autoexec.bat: wd8003e -d -n 0x60 3 0x280 0xd000 ipx <- BYU ipx packet driver v2.01 - 890427 net3 <- Plain old net3 that works otherwise. Dies here. f: <- Never gets here, although default drive is now f: login student <- This works fine, if entered now. Thanks, Bill rogers@ux1.cso.uiuc.edu rogers@vmd.cso.uiuc.edu rogers@UIUCVMD
u5533129@ucsvc.ucs.unimelb.edu.au (03/19/91)
> We are trying to use the packet driver (version 7.6) for the western digital > 8003eb board. If we boot from the floppy in which we did the dosgen then > everything works fine. Using the remote reset, the autoexec exits after net3 > and won't do the following login command. Everything else works fine after that. > I've tried several hundred variations on this theme, but not the right one. > Can anyone help? We've found this too, and I assumed it was a Novell "feature". One way round it is to copy the autoexec.bat file into your login directory. Things are more complicated if you need different autoexec.bat files for different machines. Does anyone have a better way? Peter Summers
jc58+@andrew.cmu.edu (Johnny J. Chin) (03/19/91)
Excerpts From Captions of netnews.comp.sys.novell: 18-Mar-91 Re: Autoexec dies during re.. u5533129@ucsvc.ucs.unime (697) >> We are trying to use the packet driver (version 7.6) for the western digital >> 8003eb board. If we boot from the floppy in which we did the dosgen then >> everything works fine. Using the remote reset, the autoexec exits after net3 >> and won't do the following login command. Everything else works fine after >that. >> I've tried several hundred variations on this theme, but not the right one. >> Can anyone help? > >We've found this too, and I assumed it was a Novell "feature". > >One way round it is to copy the autoexec.bat file into your login directory. >Things are more complicated if you need different autoexec.bat files for >different machines. Does anyone have a better way? Yes, there may be a better way. What I've done and seems to have worked is the following: 1. Create a standard boot diskette for *EACH* NIC or DOS type. 2. In your AUTOEXEC.BAT, you should *ONLY HAVE ONE LINE* which includes the <Ctrl-Z> (end-of-file marker) at *END OF THE LINE* and *NOT* on the next line. 3. This ONE LINE in the AUTOEXEC should read something like this: IBM-PS2.BAT if you are booting a PS/2. In otherwords, call a seperate batch file. 4. Place your actual boot routine in this "seperate" batch file. And copy this batch file into the SYS:LOGIN directory. 5. Be sure to name all you IPX.COM files differently for each of the different NICs. 6. Also remmeber to include all necessary files called by these batch files in the SYS:LOGIN directory. I hope this helps. __________ Carnegie Mellon University ___ / \ / / /_/ / /\/ _/ / / / "Happy Computing ..." __/. /__ / / / / / / / / -- Computer Dr. / / Internet: Johnny.J.Chin@andrew.cmu.edu / ------- / 4730 Centre Ave. #412 BITnet: jc58@andrew \__________/ Pittsburgh, PA 15213 UUCP: ...!uunet!andrew.cmu.edu!jc58
news@brian386.uucp (News Administrator) (03/21/91)
In article <1991Mar18.153110.9114@ux1.cso.uiuc.edu> rogers@ux1.cso.uiuc.edu (Bill Rogers) writes: [Stuff deleted] > >autoexec.bat: > >wd8003e -d -n 0x60 3 0x280 0xd000 >ipx <- BYU ipx packet driver v2.01 - 890427 >net3 <- Plain old net3 that works otherwise. Dies here. >f: <- Never gets here, although default drive is now f: >login student <- This works fine, if entered now. > Have you checked your PATH to make sure there are no files called net3.bat somewhere before net3.com. If this is the problem, you will need to add "call" in front of net3, or else remove net3.bat. brian