I've run into this issue with DL140's and other servers that didn't come
with floppy drives. I suggest downloading nLite and adding the drivers to
the install process. Once that's done grab this tool and create a bootable
CD:

http://isorecorder.alexfeinman.com/isorecorder.htm

hth


On Thu, Sep 18, 2008 at 3:11 PM, Murray Freeman <[EMAIL PROTECTED]> wrote:

>  We've got lots of floppies, but the Server doesn't have a floppy
> interface, so we are using USB floppies. The Proliant recognizes the floppy,
> but the Windows Server 2K3 is having trouble recognizing the floppy.
>
>
> *Murray*
>
>
>  ------------------------------
> *From:* Christopher J. Bosak [mailto:[EMAIL PROTECTED]
> *Sent:* Thursday, September 18, 2008 2:04 PM
> *To:* NT System Admin Issues
> *Subject:* RE: CREATING NEW 2K3 SERVER PROBLEM WITH LOADING FROM FLOPPY DR
>
>   Can't temporally grab a floppy drive from another machine?
>
>
>
> Christopher J. Bosak
>
> Vector Company
>
> c. 847.603.4673
>
> [EMAIL PROTECTED]
>
>
>
> *"You need to install an RTFM Interface, due to an LBNC issue."*
>
> *- B.O.F.H. (Merged 2 into 1) - Me*
>
>
>
> *From:* Murray Freeman [mailto:[EMAIL PROTECTED]
> *Sent:* Thursday, September 18, 2008 14:00 hrs
> *To:* NT System Admin Issues
> *Subject:* CREATING NEW 2K3 SERVER PROBLEM WITH LOADING FROM FLOPPY DR
>
>
>
> We're trying to build a new Windows Server 2K3, and since our server has no
> floppy drive, we're using a USB floppy and while the BIOS recognizes the
> drive, Windoes Server can't find the file it's looking for. We have also
> used a USB thumb wheel which we formated to look like a Floppy Drive, and
> same result. Unfortunately, Windows Server 2K3 will only look for the Hard
> drive drivers on a "floppy" disk. We have a HP Proliant ML110 and were
> trying to set up a raid. Any ideas on how to get around the floppy issue?
>
>
>
> *Murray*
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>

~ Finally, powerful endpoint security that ISN'T a resource hog! ~
~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/>  ~

Reply via email to