Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion GroupsWindows Server 2003Windows 2000Windows NTSmall Business ServerVirtual ServerExchange ServerIISHost Integration ServerISA ServerSMSWSUSMOMWindows Media ServerSecurityCertification
Related Topics
SQL ServerMS WindowsMS OfficePC HardwareMore Topics ...

Windows Server Forum / Windows NT / Setup / March 2005

Tip: Looking for answers? Try searching our database.

Floppyless install NT 4.0

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
DAD56 - 10 Mar 2005 16:03 GMT
I have a new server and want to Install NT4.0 as a BDC in preparation of
upgrading teh domain to W2K3 AD.  The new server does NOT have a floppy drive
and the ServeRaid controller is not in the Retail copy of NT server.  

I have created a 1.99GB partition and formatted it with MS DOS 6.22 (SCSI
BIOS enabled).  I have copied the i386 folder to the drive  and have
downloaded the NT4.0 driver for the controller and copied it to the $OEM$
folder as per the instructions for unattended installation mode.  I then run
c:\i386\winnt.exe /b /u:c:\unattend.txt which copies the uncompressed files
to $WIN_NT$.~LS and the boot files to $WIN_NT$.~bt and restarts the server.  
The error message is "cant locate txtsetup.oem".  I followed the article on
creating the unattended.txt file and the have copied the OEM files as
instructed but no go.

Does anyone have instruction to install NT4.0 in a diskless enviroment using
an IBM ServeRAID controller?

DAD56
nospam.please@ualberta.ca - 10 Mar 2005 16:38 GMT
> I have a new server and want to Install NT4.0 as a BDC in preparation
> of upgrading teh domain to W2K3 AD.  The new server does NOT have a
[quoted text clipped - 16 lines]
>
> DAD56

I don't have an answer - I'm just wondering why people go to such effort.
Surely there is a floppy drive in an old machine that could be
temporarily connected, or one could spend $10 and get a new one?  Or, if
the budget allows, get a USB floppy drive?
DAD56 - 10 Mar 2005 16:53 GMT
The server is an IBM X336 and doesn't have a floppy controller or physical
space on board for it.  Do you have a USB driver for DOS that NT 4.0 setup
will use?
DAD56

> > I have a new server and want to Install NT4.0 as a BDC in preparation
> > of upgrading teh domain to W2K3 AD.  The new server does NOT have a
[quoted text clipped - 21 lines]
> temporarily connected, or one could spend $10 and get a new one?  Or, if
> the budget allows, get a USB floppy drive?
nospam.please@ualberta.ca - 11 Mar 2005 17:10 GMT
> The server is an IBM X336 and doesn't have a floppy controller or
> physical space on board for it.  Do you have a USB driver for
DOS that
> NT 4.0 setup will use?
> DAD56

Most newer machines that I have seen will see a USB floppy and
boot from
it without any extra drivers.  Usually this is turned on in the
BIOS via
a setting called something like "legacy USB support".

Since a USB floppy drive is usually available as an option when
you buy
an IBM X336, I assume that it knows how to use one.
DAD56 - 12 Mar 2005 12:35 GMT
Thanks,
I already tried that using an IBM USB floppy drive.  The text mode NT 4
setup process doesn't recognize the USB floppy is the problem and a diskette
is required to load the new SCSI driver.

I got the unattended mode install to work, had to move the folders around
until it ran but the server blue screened on the driver install.  We are
going to use another machine as the upgrade machine and install W2K3 on the
floppyless box, promote it to a DC and then move the roles to it.  We have
done this several times successfully but it causes problems as the NT servers
still in production require multiple reboots when the PDC changes in the
domain.  We have three NT 4.0 domains on this network that have domain trusts
established and are in the process of upgrading them.  We had four and
upgraded one successfully already.  We found through testing that the easiest
upgrade method was to use the IP of the current PDC as the IP of the upgrade
machine as it only requires one change in the LMHOSTS file of the NT 4.0
servers currently in production and hence one reboot.  The W2K machines react
properly to a WINS change but the NT 4 servers don’t.  When you have 28
server in two server farms in a 24/7 environment multiple reboots are not
easily accomplished.
Thanks for the help.

DAD56

> > The server is an IBM X336 and doesn't have a floppy controller
> or
[quoted text clipped - 12 lines]
> you buy
> an IBM X336, I assume that it knows how to use one.
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2009 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.