Windows Vista Tips

Windows Vista Tips > Newsgroups > Windows Server > Server Setup > System Looking for Floppy Disk to Install Devive Drivers

Reply
Thread Tools Display Modes

System Looking for Floppy Disk to Install Devive Drivers

 
 
TPATEL
Guest
Posts: n/a

 
      03-11-2009
Hello.

I am trying to Install Windows 2003 Standard Server on IBM Blade HS21 -
Model 8853. I copied the SAS drivers from Setup CD to Floppy, Start the
Setup, Hit F6 to add the SAS Drivers, System takes the Drivers, let me Create
partition and Format the Drive. then as soon it tried to start copying files,
It somes with a Message
Insert the Disk labeled: LSI Logic Fusion-MPT SAS Storport Driver into drive
A:
* Press Enter when ready "
 
Reply With Quote
 
 
 
 
Darrell Gorter[MSFT]
Guest
Posts: n/a

 
      03-12-2009
Hello,
Did you check if the floppy disk has that label on it? "LSI Logic
Fusion-MPT SAS Storport Driver "
from another machine run
Label A:
Check the output
should be something similar to this output:

C:\>label a:
Volume in drive A: is LSI Logic Fusion-MPT SAS Storport Driver
Volume Serial Number is EA96-3EF0
Volume label (11 characters, ENTER for none)?

If it is not correct, you can change the label to LSI Logic Fusion-MPT SAS
Storport Driver
to check if that works
Thanks,
Darrell Gorter[MSFT]

This posting is provided "AS IS" with no warranties, and confers no rights
--------------------
| >Thread-Topic: System Looking for Floppy Disk to Install Devive Drivers
| >thread-index: AcmigDm6xuC0+/wATx6SU3egKPCiSQ==
| >X-WBNR-Posting-Host: 207.46.19.228
| >From: =?Utf-8?B?VFBBVEVM?= <>
| >Subject: System Looking for Floppy Disk to Install Devive Drivers
| >Date: Wed, 11 Mar 2009 12:33:16 -0700
| >Lines: 10
| >Message-ID: <0BB33E10-FF90-4258-835B->
| >MIME-Version: 1.0
| >Content-Type: text/plain;
| > charset="Utf-8"
| >Content-Transfer-Encoding: 7bit
| >X-Newsreader: Microsoft CDO for Windows 2000
| >Content-Class: urn:content-classes:message
| >Importance: normal
| >Priority: normal
| >X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.3168
| >Newsgroups: microsoft.public.windows.server.setup
| >Path: TK2MSFTNGHUB02.phx.gbl
| >Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.windows.server.setup:6198
| >NNTP-Posting-Host: tk2msftibfm01.phx.gbl 10.40.244.149
| >X-Tomcat-NG: microsoft.public.windows.server.setup
| >
| >Hello.
| >
| >I am trying to Install Windows 2003 Standard Server on IBM Blade HS21 -
| >Model 8853. I copied the SAS drivers from Setup CD to Floppy, Start the
| >Setup, Hit F6 to add the SAS Drivers, System takes the Drivers, let me
Create
| >partition and Format the Drive. then as soon it tried to start copying
files,
| >It somes with a Message
| >Insert the Disk labeled: LSI Logic Fusion-MPT SAS Storport Driver into
drive
| >A:
| >* Press Enter when ready "
| >

 
Reply With Quote
 
Dave Patrick
Guest
Posts: n/a

 
      03-15-2009
Wow that would be a strange one. I've always just used whatever floppy disk
was handy and never had to label the disk.



--

Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect


""Darrell Gorter[MSFT]"" wrote:
> Hello,
> Did you check if the floppy disk has that label on it? "LSI Logic
> Fusion-MPT SAS Storport Driver "
> from another machine run
> Label A:
> Check the output
> should be something similar to this output:
>
> C:\>label a:
> Volume in drive A: is LSI Logic Fusion-MPT SAS Storport Driver
> Volume Serial Number is EA96-3EF0
> Volume label (11 characters, ENTER for none)?
>
> If it is not correct, you can change the label to LSI Logic Fusion-MPT SAS
> Storport Driver
> to check if that works
> Thanks,
> Darrell Gorter[MSFT]
>
> This posting is provided "AS IS" with no warranties, and confers no rights


 
Reply With Quote
 
TPATEL
Guest
Posts: n/a

 
      03-22-2009
I had the similar situation for IBM 3650 8KI Drivers and had to change the
file to reflect the name. But do not remember the location.

Also when setting up servers we usually do not use the setup CD to setup the
server, we only use it to create a Raid Partitions.

"Dave Patrick" wrote:

> Wow that would be a strange one. I've always just used whatever floppy disk
> was handy and never had to label the disk.
>
>
>
> --
>
> Regards,
>
> Dave Patrick ....Please no email replies - reply in newsgroup.
> Microsoft Certified Professional
> Microsoft MVP [Windows]
> http://www.microsoft.com/protect
>
>
> ""Darrell Gorter[MSFT]"" wrote:
> > Hello,
> > Did you check if the floppy disk has that label on it? "LSI Logic
> > Fusion-MPT SAS Storport Driver "
> > from another machine run
> > Label A:
> > Check the output
> > should be something similar to this output:
> >
> > C:\>label a:
> > Volume in drive A: is LSI Logic Fusion-MPT SAS Storport Driver
> > Volume Serial Number is EA96-3EF0
> > Volume label (11 characters, ENTER for none)?
> >
> > If it is not correct, you can change the label to LSI Logic Fusion-MPT SAS
> > Storport Driver
> > to check if that works
> > Thanks,
> > Darrell Gorter[MSFT]
> >
> > This posting is provided "AS IS" with no warranties, and confers no rights

>
>

 
Reply With Quote
 
Dave Patrick
Guest
Posts: n/a

 
      03-22-2009
Yes, typically the files named oemsetup.inf, txtsetup.oem, and the *.sys
file for your drive controller are what's required on the floppy. Just never
ran into a situation where the disk LABEL command was needed.




--

Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect


"TPATEL" wrote:
>I had the similar situation for IBM 3650 8KI Drivers and had to change the
> file to reflect the name. But do not remember the location.
>
> Also when setting up servers we usually do not use the setup CD to setup
> the
> server, we only use it to create a Raid Partitions.


 
Reply With Quote
 
Darrell Gorter[MSFT]
Guest
Posts: n/a

 
      03-23-2009
Hello Dave,
I had not heard of requiring the label either, however the error message
indicated that setup was looking for a disk with a specific label.
It should get that information from the INF file,

Thanks,
Darrell Gorter[MSFT]

This posting is provided "AS IS" with no warranties, and confers no rights
--------------------
| >From: "Dave Patrick" <>
| >References: <0BB33E10-FF90-4258-835B->
<>
<#>
<A6510026-BD13-4A7F-9218->
| >In-Reply-To: <A6510026-BD13-4A7F-9218->
| >Subject: Re: System Looking for Floppy Disk to Install Devive Drivers
| >Date: Sun, 22 Mar 2009 17:40:19 -0600
| >Lines: 25
| >Organization: MVP
| >MIME-Version: 1.0
| >Content-Type: text/plain;
| > format=flowed;
| > charset="utf-8";
| > reply-type=original
| >Content-Transfer-Encoding: 7bit
| >X-Priority: 3
| >X-MSMail-Priority: Normal
| >X-Newsreader: Microsoft Windows Mail 6.0.6001.18000
| >X-MimeOLE: Produced By Microsoft MimeOLE V6.0.6001.18049
| >Message-ID: <uC#>
| >Newsgroups: microsoft.public.windows.server.setup
| >NNTP-Posting-Host: 71-220-255-238.chyn.qwest.net 71.220.255.238
| >Path: TK2MSFTNGHUB02.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSF TNGP05.phx.gbl
| >Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.windows.server.setup:6254
| >X-Tomcat-NG: microsoft.public.windows.server.setup
| >
| >Yes, typically the files named oemsetup.inf, txtsetup.oem, and the *.sys
| >file for your drive controller are what's required on the floppy. Just
never
| >ran into a situation where the disk LABEL command was needed.
| >
| >
| >
| >
| >--
| >
| >Regards,
| >
| >Dave Patrick ....Please no email replies - reply in newsgroup.
| >Microsoft Certified Professional
| >Microsoft MVP [Windows]
| >http://www.microsoft.com/protect
| >
| >
| >"TPATEL" wrote:
| >>I had the similar situation for IBM 3650 8KI Drivers and had to change
the
| >> file to reflect the name. But do not remember the location.
| >>
| >> Also when setting up servers we usually do not use the setup CD to
setup
| >> the
| >> server, we only use it to create a Raid Partitions.
| >
| >

 
Reply With Quote
 
Dave Patrick
Guest
Posts: n/a

 
      03-23-2009
Ok, thanks Darrell. Guess it was worth a shot.



--

Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect


""Darrell Gorter[MSFT]"" wrote:
> Hello Dave,
> I had not heard of requiring the label either, however the error message
> indicated that setup was looking for a disk with a specific label.
> It should get that information from the INF file,
>
> Thanks,
> Darrell Gorter[MSFT]
>
> This posting is provided "AS IS" with no warranties, and confers no rights

 
Reply With Quote
 
Lior Paster Rackable
Guest
Posts: n/a

 
      03-24-2009
This is very frustrating, I get the exact issue. As suggested, I tried to
change the floppy disk label -

C:\Program Files\Support Tools>label a:
Volume in drive A: has no label
Volume label (11 characters, ENTER for none)? LSI Logic Fusion-MPT SAS
Storport Driver
Invalid volume label

I guess there is a limit of 11 characters for the label. So how do I get
around that?

Also, if I need to change anything in the lsi_sas.inf" file, what needs to
change?

Thank you.



""Darrell Gorter[MSFT]"" wrote:

> Hello,
> Did you check if the floppy disk has that label on it? "LSI Logic
> Fusion-MPT SAS Storport Driver "
> from another machine run
> Label A:
> Check the output
> should be something similar to this output:
>
> C:\>label a:
> Volume in drive A: is LSI Logic Fusion-MPT SAS Storport Driver
> Volume Serial Number is EA96-3EF0
> Volume label (11 characters, ENTER for none)?
>
> If it is not correct, you can change the label to LSI Logic Fusion-MPT SAS
> Storport Driver
> to check if that works
> Thanks,
> Darrell Gorter[MSFT]
>
> This posting is provided "AS IS" with no warranties, and confers no rights
> --------------------
> | >Thread-Topic: System Looking for Floppy Disk to Install Devive Drivers
> | >thread-index: AcmigDm6xuC0+/wATx6SU3egKPCiSQ==
> | >X-WBNR-Posting-Host: 207.46.19.228
> | >From: =?Utf-8?B?VFBBVEVM?= <>
> | >Subject: System Looking for Floppy Disk to Install Devive Drivers
> | >Date: Wed, 11 Mar 2009 12:33:16 -0700
> | >Lines: 10
> | >Message-ID: <0BB33E10-FF90-4258-835B->
> | >MIME-Version: 1.0
> | >Content-Type: text/plain;
> | > charset="Utf-8"
> | >Content-Transfer-Encoding: 7bit
> | >X-Newsreader: Microsoft CDO for Windows 2000
> | >Content-Class: urn:content-classes:message
> | >Importance: normal
> | >Priority: normal
> | >X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.3168
> | >Newsgroups: microsoft.public.windows.server.setup
> | >Path: TK2MSFTNGHUB02.phx.gbl
> | >Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.windows.server.setup:6198
> | >NNTP-Posting-Host: tk2msftibfm01.phx.gbl 10.40.244.149
> | >X-Tomcat-NG: microsoft.public.windows.server.setup
> | >
> | >Hello.
> | >
> | >I am trying to Install Windows 2003 Standard Server on IBM Blade HS21 -
> | >Model 8853. I copied the SAS drivers from Setup CD to Floppy, Start the
> | >Setup, Hit F6 to add the SAS Drivers, System takes the Drivers, let me
> Create
> | >partition and Format the Drive. then as soon it tried to start copying
> files,
> | >It somes with a Message
> | >Insert the Disk labeled: LSI Logic Fusion-MPT SAS Storport Driver into
> drive
> | >A:
> | >* Press Enter when ready "
> | >
>
>

 
Reply With Quote
 
Lior Paster Rackable
Guest
Posts: n/a

 
      03-24-2009
Never mind. I found the solution. The problem is not Floppy Label. It is
actually a need to support some USB Floppy devices. The solution is:

http://www.msfn.org/board/index.php?showtopic=82711

It's basically solving the issue by adding several lines to the txtsetup.oem
file on the floppy so that file is loaded after you hit F6 and then it is
used again to load additional drivers during the install so the problem went
away.

Here is the solution for your conveniance:


Create your Storage device driver on the floppy disk and open textsetup.oem
Add the following lines to the bottom of [HardwareIds.scsi.(device name)]
If this section does not exist you must create it!
If your USB floppy drive still does not work, look for the hardware ID in
the floppy drive driver's .inf file, and make sure any legacy floppy drives
are disabled in the bios.

CODE
id = "USB\VID_03F0&PID_2001", "usbstor" #--HP
id = "USB\VID_054C&PID_002C", "usbstor" #--Sony
id = "USB\VID_057B&PID_0001", "usbstor" #--Y-E Data
id = "USB\VID_0409&PID_0040", "usbstor" #--NEC
id = "USB\VID_0424&PID_0FDC", "usbstor" #--SMSC
id = "USB\VID_08BD&PID_1100", "usbstor" #--Iomega
id = "USB\VID_055D&PID_2020", "usbstor" #--Samsung


(more data on the link above)
 
Reply With Quote
 
 
 
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
usb floppy disk drive drivers sunshine_rainne Windows Vista Hardware 1 02-02-2008 08:27 PM
prepare bootable system floppy disk UNIORYOU Windows Media Center 1 10-29-2007 11:53 AM
Floppy disk Seek failure plus Slection of Operating System Rex Ferbrache Windows Media Center 1 05-13-2007 08:47 PM
Automated System Recovery (ASR) NO floppy disk mmonteiro89 Windows Media Center 3 09-15-2006 08:47 AM
Install asking for drivers from floppy T. Reinholtz Windows Server 2 05-16-2006 08:19 AM



1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59