Discussion Locked

Creating a DOS Network Bootable Diskette

0 helpful
17 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

How do I /manually/ create a DOS Network Bootable Diskette?

Assume I have the drivers for the Network Card, I have a Windows 95/98 OS to create Boot Disks with.

(Extra info: I am attempting to install Windows NT Workstation on workstations without CD roms and need a DOS Network Boot Disk to install via network. NOTE: Answers relating to any automated service for creating network boot disks in NT Server are unacceptable.)

17 replies

by kevin_b

Why do you need a boot disk? just connect to the share with 95/98 or whatever and copy the i386 directory to the hard drive and then run winnt.exe and it should work.

by techadept

I wanted to manually create the DOS boot disk to connect to the network. Appreciate the suggestion of alternate solutions, but this won't work for me.

by darthbuck

I hope this helps. This was copied from a technet article.

This article explains how to add an NDIS driver for Network Interface Cards
(NIC) that were not originally included in the Network Client Administrator.
This information applies to theNetwork Client version 3.0 for MS-DOS and
Windows Startup Disk.

Verify that the 3.5" HD disk to which the client files will be copied is a DOS
system disk and formatted under DOS. If the disk is formatted under NT, the copy
process will fail.

MORE INFORMATION
================

To configure this disk:

NOTE: The following example is for the Intel EtherExpressPro NIC; however, this
example can serve as a template for all NDIS compatible drivers.

1. Copy the Epro.dos driver to the A:\Net directory.

2. Modify the Net\Protocol.ini file and change the [EPRO$] section to
"drivername=EPRO$".

NOTE: The "drivername=" information is included on most manufacturers' disks
in the sample Protocol.ini file that comes with the network

by darthbuck

Well that didn't work very well did it. If you want the full article, E-mail me and I will send it to you.

t_buck@email.com

by ravi

The Admin. Tools program group in NT Server has a utility to make the network boot disk.

by liebenberg

I know you say that you don't want this but it is the only way I can think of. Go to the computer that has the source files (assuming it is an Nt server computer) and create the installetion disk set from there. I assume you know that the first computer online should be the PDC (nt server computer) if you are creating a domain. To manually create a bootdisk for an NT installation you will need a NT boot disk which can not be created with a Win 95/98 machine only an NT machine.

by csandleben

1. copy the system from the 9x machine onto the diskette with explorer
2. run the installation from the DOS 3.0 client from the NT machine
3. Copy the MSNET folder you created down to the diskette
4. Copy the new autoexec.bat and config.sys down to the diskette
5. edit the autoexec.bat and config.sys so that they point to the diskette folder.
Reboot from that disk and it will bring up the machine without a hard drive.

by techadept

This looked like a viable option, but I couldn't follow the directions. I wish I could say this worked, this looked like the best solution to my question out of all of them.

by rindi1

You'll have to try to get hold of Windows for Workgroups for DOS, with that you should be able to create a boot diskette which can connect to the network. This is the same client which is on the nt4 server CD. Unfortunately, it doesn't come with theworkstation version, but the standalone version shouldn't cost too much. If you can't find a copy, send me a mail, I'll try to get hold of one for you (it's about 2.5 MB).

by techadept

Didn't really help, but the WfW option was the only one that worked. Of course, getting ahold of WfW was impossible within the timeframe that this question was important.

by tedbovis

Check out, WWW.BovisTech.co.uk you will find several TCP/IP boot disk just for such a request. Download the self extracting files and have a disk ready, most are flexible enough to work on any network with minimal changes. Send me some comments (viathe web site) about the disks/site not been up very long!

by techadept

The TCP/IP boot disk you have as an example on your site is for ghosting machines. This is not what I was doing, but it did provide a fairly good example of what one should look like, once you isolated the ghost application parameter commands.

This discussion is closed to new replies.