Archived from groups: microsoft.public.win2000.setup_deployment (More info?)
I am looking for a way to remove old SCSI hardware that is reporting in the
SCSI devices in the registry.
Situation:
After replacing a "PLASMON FTA" tape library, the new unit came wiht an
Identity String of "EXABYTE 110L". Windows detected and created the strings
in the SCSI devices with no problems, but after correcting the Identity
String to "PLASMON FTA" Windows 2000 Server hangs during the boot process
until I either power fail the unti, or perform a soft reset of the unit.
My goal is to remove the settings in the registry so that windows knows
nothing about the old or the new Library and allow the SCSI device to be
redetected.
I tried to delete the registry entries for the devices, and windows will not
allow me.
So my question is how do I get rid of the old SCSI devices, because I
suspect that there is a windows conflict in what it sees during the boot, 2
devices identicle but with different strings and windows does not know which
one to load.
Additionally, where can I log the boot process to see exactly what is going
on behind the scenes? And trace any issues that might be happening.
Thanks
J
Archived from groups: microsoft.public.win2000.setup_deployment (More info?)
1.) To display hidden devices, non-Plug and Play devices, and devices not
attached to the computer (commonly known as "ghosted" or "phantom" devices)
Save the following two lines as a file then execute.
--------------------------setdev.bat---------------------
set DEVMGR_SHOW_NONPRESENT_DEVICES=1
start devmgmt.msc
---------------------------------------------------------
Then, View|Show Hidden Devices to remove or reconfigure these devices. Do
not edit the registry.
2.) Try F8 at startup and 'Enable Boot Logging' then look for 'ntbtlog.txt'
in the %windir% directory.
--
Regards,
Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect
"Smurfman" wrote:
|I am looking for a way to remove old SCSI hardware that is reporting in the
| SCSI devices in the registry.
|
| Situation:
| After replacing a "PLASMON FTA" tape library, the new unit came wiht an
| Identity String of "EXABYTE 110L". Windows detected and created the
strings
| in the SCSI devices with no problems, but after correcting the Identity
| String to "PLASMON FTA" Windows 2000 Server hangs during the boot process
| until I either power fail the unti, or perform a soft reset of the unit.
|
| My goal is to remove the settings in the registry so that windows knows
| nothing about the old or the new Library and allow the SCSI device to be
| redetected.
|
| I tried to delete the registry entries for the devices, and windows will
not
| allow me.
|
| So my question is how do I get rid of the old SCSI devices, because I
| suspect that there is a windows conflict in what it sees during the boot,
2
| devices identicle but with different strings and windows does not know
which
| one to load.
|
| Additionally, where can I log the boot process to see exactly what is
going
| on behind the scenes? And trace any issues that might be happening.
|
| Thanks
| J
Archived from groups: microsoft.public.win2000.setup_deployment (More info?)
Great information!
I believe delete the hidden device will resolve this issue. In addition,
you may also check the following regsitry key:
HKEY_LOCAL_MACHINE\Hardware\Devicemap\Scsi\ScsiPortx\ScsiBusx\
TargetIdx\LogicalUnitIdx
I suggest you backup this registry and delete the corresponding keys,
restart the machine to allow it automatically detect the SCSI drive. I
would like to list the following articles for your reference:
How to troubleshoot error messages about Event ID 9 and Event ID 11
http://support.microsoft.com/?kbid=314093
Hope it helps.
Any udpate, let us get in touch!
--------------------
>From: "Dave Patrick" <mail@Nospam.DSPatrick.com>
>References: <7653072C-94F6-4206-997C-24CED9D1B17F@microsoft.com>
>Subject: Re: Removing SCSI Hardware Entries
>Date: Sat, 11 Jun 2005 04:14:35 -0600
>Lines: 59
>X-Priority: 3
>X-MSMail-Priority: Normal
>X-Newsreader: Microsoft Outlook Express 6.00.2900.2180
>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
>Message-ID: <eJoPf5mbFHA.228@TK2MSFTNGP12.phx.gbl>
>Newsgroups: microsoft.public.win2000.setup_deployment
>NNTP-Posting-Host: 65.126.47.56
>Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP12.phx.gbl
>Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.win2000.setup_deployment:3021
>X-Tomcat-NG: microsoft.public.win2000.setup_deployment
>
>1.) To display hidden devices, non-Plug and Play devices, and devices not
>attached to the computer (commonly known as "ghosted" or "phantom"
devices)
>Save the following two lines as a file then execute.
>
>--------------------------setdev.bat---------------------
>set DEVMGR_SHOW_NONPRESENT_DEVICES=1
>start devmgmt.msc
>---------------------------------------------------------
>
>Then, View|Show Hidden Devices to remove or reconfigure these devices. Do
>not edit the registry.
>
>
>2.) Try F8 at startup and 'Enable Boot Logging' then look for
'ntbtlog.txt'
>in the %windir% directory.
>
>--
>Regards,
>
>Dave Patrick ....Please no email replies - reply in newsgroup.
>Microsoft Certified Professional
>Microsoft MVP [Windows]
>http://www.microsoft.com/protect
>
>"Smurfman" wrote:
>|I am looking for a way to remove old SCSI hardware that is reporting in
the
>| SCSI devices in the registry.
>|
>| Situation:
>| After replacing a "PLASMON FTA" tape library, the new unit came wiht an
>| Identity String of "EXABYTE 110L". Windows detected and created the
>strings
>| in the SCSI devices with no problems, but after correcting the Identity
>| String to "PLASMON FTA" Windows 2000 Server hangs during the boot process
>| until I either power fail the unti, or perform a soft reset of the unit.
>|
>| My goal is to remove the settings in the registry so that windows knows
>| nothing about the old or the new Library and allow the SCSI device to be
>| redetected.
>|
>| I tried to delete the registry entries for the devices, and windows will
>not
>| allow me.
>|
>| So my question is how do I get rid of the old SCSI devices, because I
>| suspect that there is a windows conflict in what it sees during the
boot,
>2
>| devices identicle but with different strings and windows does not know
>which
>| one to load.
>|
>| Additionally, where can I log the boot process to see exactly what is
>going
>| on behind the scenes? And trace any issues that might be happening.
>|
>| Thanks
>| J
>
>
>
Best regards,
Rebecca Chen
MCSE2000 MCDBA CCNA
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
=====================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
Archived from groups: microsoft.public.win2000.setup_deployment (More info?)
In case of "set DEVMGR_SHOW_NONPRESENT_DEVICES=1" does not work, you can
open the Device Manager and click View menu, check "Show hidden device" to
see the hidden device and delete the old SCSI one.
--------------------
>From: "Dave Patrick" <mail@Nospam.DSPatrick.com>
>References: <7653072C-94F6-4206-997C-24CED9D1B17F@microsoft.com>
>Subject: Re: Removing SCSI Hardware Entries
>Date: Sat, 11 Jun 2005 04:14:35 -0600
>Lines: 59
>X-Priority: 3
>X-MSMail-Priority: Normal
>X-Newsreader: Microsoft Outlook Express 6.00.2900.2180
>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
>Message-ID: <eJoPf5mbFHA.228@TK2MSFTNGP12.phx.gbl>
>Newsgroups: microsoft.public.win2000.setup_deployment
>NNTP-Posting-Host: 65.126.47.56
>Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP12.phx.gbl
>Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.win2000.setup_deployment:3021
>X-Tomcat-NG: microsoft.public.win2000.setup_deployment
>
>1.) To display hidden devices, non-Plug and Play devices, and devices not
>attached to the computer (commonly known as "ghosted" or "phantom"
devices)
>Save the following two lines as a file then execute.
>
>--------------------------setdev.bat---------------------
>set DEVMGR_SHOW_NONPRESENT_DEVICES=1
>start devmgmt.msc
>---------------------------------------------------------
>
>Then, View|Show Hidden Devices to remove or reconfigure these devices. Do
>not edit the registry.
>
>
>2.) Try F8 at startup and 'Enable Boot Logging' then look for
'ntbtlog.txt'
>in the %windir% directory.
>
>--
>Regards,
>
>Dave Patrick ....Please no email replies - reply in newsgroup.
>Microsoft Certified Professional
>Microsoft MVP [Windows]
>http://www.microsoft.com/protect
>
>"Smurfman" wrote:
>|I am looking for a way to remove old SCSI hardware that is reporting in
the
>| SCSI devices in the registry.
>|
>| Situation:
>| After replacing a "PLASMON FTA" tape library, the new unit came wiht an
>| Identity String of "EXABYTE 110L". Windows detected and created the
>strings
>| in the SCSI devices with no problems, but after correcting the Identity
>| String to "PLASMON FTA" Windows 2000 Server hangs during the boot process
>| until I either power fail the unti, or perform a soft reset of the unit.
>|
>| My goal is to remove the settings in the registry so that windows knows
>| nothing about the old or the new Library and allow the SCSI device to be
>| redetected.
>|
>| I tried to delete the registry entries for the devices, and windows will
>not
>| allow me.
>|
>| So my question is how do I get rid of the old SCSI devices, because I
>| suspect that there is a windows conflict in what it sees during the
boot,
>2
>| devices identicle but with different strings and windows does not know
>which
>| one to load.
>|
>| Additionally, where can I log the boot process to see exactly what is
>going
>| on behind the scenes? And trace any issues that might be happening.
>|
>| Thanks
>| J
>
>
>
Best regards,
Rebecca Chen
MCSE2000 MCDBA CCNA
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
=====================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
Archived from groups: microsoft.public.win2000.setup_deployment (More info?)
But the View|Show Hidden Devices does not show devices that are currently
not connected. It's not clear whether it is still connected hardware or not.
http://support.microsoft.com/defau [...] US;Q315539
--
Regards,
Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect
""Rebecca Chen [MSFT]"" wrote:
| In case of "set DEVMGR_SHOW_NONPRESENT_DEVICES=1" does not work, you can
| open the Device Manager and click View menu, check "Show hidden device" to
| see the hidden device and delete the old SCSI one.
|
Archived from groups: microsoft.public.win2000.setup_deployment (More info?)
Agree.
--------------------
>From: "Dave Patrick" <mail@Nospam.DSPatrick.com>
>References: <7653072C-94F6-4206-997C-24CED9D1B17F@microsoft.com>
<eJoPf5mbFHA.228@TK2MSFTNGP12.phx.gbl>
<ed3J5l8bFHA.3928@TK2MSFTNGXA01.phx.gbl>
>Subject: Re: Removing SCSI Hardware Entries
>Date: Sun, 12 Jun 2005 21:49:20 -0600
>Lines: 20
>X-Priority: 3
>X-MSMail-Priority: Normal
>X-Newsreader: Microsoft Outlook Express 6.00.2900.2180
>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
>Message-ID: <ey2bir8bFHA.924@TK2MSFTNGP10.phx.gbl>
>Newsgroups: microsoft.public.win2000.setup_deployment
>NNTP-Posting-Host: 65.126.47.56
>Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP10.phx.gbl
>Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.win2000.setup_deployment:3026
>X-Tomcat-NG: microsoft.public.win2000.setup_deployment
>
>But the View|Show Hidden Devices does not show devices that are currently
>not connected. It's not clear whether it is still connected hardware or
not.
>
>http://support.microsoft.com/default.aspx?scid=kb;EN-US;Q315539
>
>--
>Regards,
>
>Dave Patrick ....Please no email replies - reply in newsgroup.
>Microsoft Certified Professional
>Microsoft MVP [Windows]
>http://www.microsoft.com/protect
>
>""Rebecca Chen [MSFT]"" wrote:
>| In case of "set DEVMGR_SHOW_NONPRESENT_DEVICES=1" does not work, you can
>| open the Device Manager and click View menu, check "Show hidden device"
to
>| see the hidden device and delete the old SCSI one.
>|
>
>
>
Best regards,
Rebecca Chen
MCSE2000 MCDBA CCNA
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
=====================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
Archived from groups: microsoft.public.win2000.setup_deployment (More info?)
Hi Guys,
Excellent info...I was able to run the commands as you outlined, and removed
the phantom devices that were listed, and corresponded to the registry
entries that I found.
However, my problem did not go away. The server still hung during the boot
process, so I flip flopped the devices attached to the two channels, and the
problem moved to the other device. I suspect at this point I have a SCSI
card issue that has been masking my Backup Software issues...just not sure
why all of a sudden for a windows boot that the issue started.
Thanks guys
J
"Dave Patrick" wrote:
> 1.) To display hidden devices, non-Plug and Play devices, and devices not
> attached to the computer (commonly known as "ghosted" or "phantom" devices)
> Save the following two lines as a file then execute.
>
> --------------------------setdev.bat---------------------
> set DEVMGR_SHOW_NONPRESENT_DEVICES=1
> start devmgmt.msc
> ---------------------------------------------------------
>
> Then, View|Show Hidden Devices to remove or reconfigure these devices. Do
> not edit the registry.
>
>
> 2.) Try F8 at startup and 'Enable Boot Logging' then look for 'ntbtlog.txt'
> in the %windir% directory.
>
> --
> Regards,
>
> Dave Patrick ....Please no email replies - reply in newsgroup.
> Microsoft Certified Professional
> Microsoft MVP [Windows]
> http://www.microsoft.com/protect
>
> "Smurfman" wrote:
> |I am looking for a way to remove old SCSI hardware that is reporting in the
> | SCSI devices in the registry.
> |
> | Situation:
> | After replacing a "PLASMON FTA" tape library, the new unit came wiht an
> | Identity String of "EXABYTE 110L". Windows detected and created the
> strings
> | in the SCSI devices with no problems, but after correcting the Identity
> | String to "PLASMON FTA" Windows 2000 Server hangs during the boot process
> | until I either power fail the unti, or perform a soft reset of the unit.
> |
> | My goal is to remove the settings in the registry so that windows knows
> | nothing about the old or the new Library and allow the SCSI device to be
> | redetected.
> |
> | I tried to delete the registry entries for the devices, and windows will
> not
> | allow me.
> |
> | So my question is how do I get rid of the old SCSI devices, because I
> | suspect that there is a windows conflict in what it sees during the boot,
> 2
> | devices identicle but with different strings and windows does not know
> which
> | one to load.
> |
> | Additionally, where can I log the boot process to see exactly what is
> going
> | on behind the scenes? And trace any issues that might be happening.
> |
> | Thanks
> | J
>
>
>
Archived from groups: microsoft.public.win2000.setup_deployment (More info?)
According to your description, I believe this is the SCSI card issue. It is
possible that the card corrupted and Windows cannot recongnize it.
Please contact the SCSI manufacturer to change card to test this issue.
Good luck!
--------------------
>Thread-Topic: Removing SCSI Hardware Entries
>thread-index: AcVwNbYI8OM8tuL/TtapWn8USu1DPQ==
>X-WBNR-Posting-Host: 209.217.222.70
>From: "=?Utf-8?B?U211cmZtYW4=?=" <smurfman@news.postalias>
>References: <7653072C-94F6-4206-997C-24CED9D1B17F@microsoft.com>
<eJoPf5mbFHA.228@TK2MSFTNGP12.phx.gbl>
>Subject: Re: Removing SCSI Hardware Entries
>Date: Mon, 13 Jun 2005 09:34:03 -0700
>Lines: 76
>Message-ID: <827F4AE0-9084-4411-9B4D-095A88F5BDB9@microsoft.com>
>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.0
>Newsgroups: microsoft.public.win2000.setup_deployment
>NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
>Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGXA03.phx.gbl
>Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.win2000.setup_deployment:3029
>X-Tomcat-NG: microsoft.public.win2000.setup_deployment
>
>Hi Guys,
>Excellent info...I was able to run the commands as you outlined, and
removed
>the phantom devices that were listed, and corresponded to the registry
>entries that I found.
>
>However, my problem did not go away. The server still hung during the
boot
>process, so I flip flopped the devices attached to the two channels, and
the
>problem moved to the other device. I suspect at this point I have a SCSI
>card issue that has been masking my Backup Software issues...just not sure
>why all of a sudden for a windows boot that the issue started.
>
>Thanks guys
>J
>
>"Dave Patrick" wrote:
>
>> 1.) To display hidden devices, non-Plug and Play devices, and devices
not
>> attached to the computer (commonly known as "ghosted" or "phantom"
devices)
>> Save the following two lines as a file then execute.
>>
>> --------------------------setdev.bat---------------------
>> set DEVMGR_SHOW_NONPRESENT_DEVICES=1
>> start devmgmt.msc
>> ---------------------------------------------------------
>>
>> Then, View|Show Hidden Devices to remove or reconfigure these devices.
Do
>> not edit the registry.
>>
>>
>> 2.) Try F8 at startup and 'Enable Boot Logging' then look for
'ntbtlog.txt'
>> in the %windir% directory.
>>
>> --
>> Regards,
>>
>> Dave Patrick ....Please no email replies - reply in newsgroup.
>> Microsoft Certified Professional
>> Microsoft MVP [Windows]
>> http://www.microsoft.com/protect
>>
>> "Smurfman" wrote:
>> |I am looking for a way to remove old SCSI hardware that is reporting in
the
>> | SCSI devices in the registry.
>> |
>> | Situation:
>> | After replacing a "PLASMON FTA" tape library, the new unit came wiht an
>> | Identity String of "EXABYTE 110L". Windows detected and created the
>> strings
>> | in the SCSI devices with no problems, but after correcting the Identity
>> | String to "PLASMON FTA" Windows 2000 Server hangs during the boot
process
>> | until I either power fail the unti, or perform a soft reset of the
unit.
>> |
>> | My goal is to remove the settings in the registry so that windows knows
>> | nothing about the old or the new Library and allow the SCSI device to
be
>> | redetected.
>> |
>> | I tried to delete the registry entries for the devices, and windows
will
>> not
>> | allow me.
>> |
>> | So my question is how do I get rid of the old SCSI devices, because I
>> | suspect that there is a windows conflict in what it sees during the
boot,
>> 2
>> | devices identicle but with different strings and windows does not know
>> which
>> | one to load.
>> |
>> | Additionally, where can I log the boot process to see exactly what is
>> going
>> | on behind the scenes? And trace any issues that might be happening.
>> |
>> | Thanks
>> | J
>>
>>
>>
>
Best regards,
Rebecca Chen
MCSE2000 MCDBA CCNA
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
=====================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
Archived from groups: microsoft.public.win2000.setup_deployment (More info?)
Thanks again.
Changed the card, still the same results. Received a new unit, same results.
Finally what I noticed in the hardware config of the Tape Drive, was that
there was no BarCode Reader Installed. The original hardware had a bar code
reader for LTO tapes, the BrightStore software supports a bar code, and
allows for quicker inverntory of daily tapes. But with out a bar code reader
installed in the unit, the software times-out, and dismounts the slots in the
library.
The manufacturer sent a reader, installed it, and problem solved. Who knew!
Thanks for the Device Manager tips though, I will be adding this to my bag
of tricks.
J
""Rebecca Chen [MSFT]"" wrote:
> According to your description, I believe this is the SCSI card issue. It is
> possible that the card corrupted and Windows cannot recongnize it.
>
> Please contact the SCSI manufacturer to change card to test this issue.
>
> Good luck!
>
> --------------------
> >Thread-Topic: Removing SCSI Hardware Entries
> >thread-index: AcVwNbYI8OM8tuL/TtapWn8USu1DPQ==
> >X-WBNR-Posting-Host: 209.217.222.70
> >From: "=?Utf-8?B?U211cmZtYW4=?=" <smurfman@news.postalias>
> >References: <7653072C-94F6-4206-997C-24CED9D1B17F@microsoft.com>
> <eJoPf5mbFHA.228@TK2MSFTNGP12.phx.gbl>
> >Subject: Re: Removing SCSI Hardware Entries
> >Date: Mon, 13 Jun 2005 09:34:03 -0700
> >Lines: 76
> >Message-ID: <827F4AE0-9084-4411-9B4D-095A88F5BDB9@microsoft.com>
> >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.0
> >Newsgroups: microsoft.public.win2000.setup_deployment
> >NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
> >Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGXA03.phx.gbl
> >Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.win2000.setup_deployment:3029
> >X-Tomcat-NG: microsoft.public.win2000.setup_deployment
> >
> >Hi Guys,
> >Excellent info...I was able to run the commands as you outlined, and
> removed
> >the phantom devices that were listed, and corresponded to the registry
> >entries that I found.
> >
> >However, my problem did not go away. The server still hung during the
> boot
> >process, so I flip flopped the devices attached to the two channels, and
> the
> >problem moved to the other device. I suspect at this point I have a SCSI
> >card issue that has been masking my Backup Software issues...just not sure
> >why all of a sudden for a windows boot that the issue started.
> >
> >Thanks guys
> >J
> >
> >"Dave Patrick" wrote:
> >
> >> 1.) To display hidden devices, non-Plug and Play devices, and devices
> not
> >> attached to the computer (commonly known as "ghosted" or "phantom"
> devices)
> >> Save the following two lines as a file then execute.
> >>
> >> --------------------------setdev.bat---------------------
> >> set DEVMGR_SHOW_NONPRESENT_DEVICES=1
> >> start devmgmt.msc
> >> ---------------------------------------------------------
> >>
> >> Then, View|Show Hidden Devices to remove or reconfigure these devices.
> Do
> >> not edit the registry.
> >>
> >>
> >> 2.) Try F8 at startup and 'Enable Boot Logging' then look for
> 'ntbtlog.txt'
> >> in the %windir% directory.
> >>
> >> --
> >> Regards,
> >>
> >> Dave Patrick ....Please no email replies - reply in newsgroup.
> >> Microsoft Certified Professional
> >> Microsoft MVP [Windows]
> >> http://www.microsoft.com/protect
> >>
> >> "Smurfman" wrote:
> >> |I am looking for a way to remove old SCSI hardware that is reporting in
> the
> >> | SCSI devices in the registry.
> >> |
> >> | Situation:
> >> | After replacing a "PLASMON FTA" tape library, the new unit came wiht an
> >> | Identity String of "EXABYTE 110L". Windows detected and created the
> >> strings
> >> | in the SCSI devices with no problems, but after correcting the Identity
> >> | String to "PLASMON FTA" Windows 2000 Server hangs during the boot
> process
> >> | until I either power fail the unti, or perform a soft reset of the
> unit.
> >> |
> >> | My goal is to remove the settings in the registry so that windows knows
> >> | nothing about the old or the new Library and allow the SCSI device to
> be
> >> | redetected.
> >> |
> >> | I tried to delete the registry entries for the devices, and windows
> will
> >> not
> >> | allow me.
> >> |
> >> | So my question is how do I get rid of the old SCSI devices, because I
> >> | suspect that there is a windows conflict in what it sees during the
> boot,
> >> 2
> >> | devices identicle but with different strings and windows does not know
> >> which
> >> | one to load.
> >> |
> >> | Additionally, where can I log the boot process to see exactly what is
> >> going
> >> | on behind the scenes? And trace any issues that might be happening.
> >> |
> >> | Thanks
> >> | J
> >>
> >>
> >>
> >
>
> Best regards,
>
> Rebecca Chen
>
> MCSE2000 MCDBA CCNA
>
>
> Microsoft Online Partner Support
> Get Secure! - www.microsoft.com/security
>
> =====================================================
>
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
>
> =====================================================
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
>
Archived from groups: microsoft.public.win2000.setup_deployment (More info?)
Great experience sharing!
I will also put your expereince to my bag of tricks.
Best regards,
Rebecca Chen
MCSE2000 MCDBA CCNA
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
=====================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
--------------------
>Thread-Topic: Removing SCSI Hardware Entries
>thread-index: AcV3PS0rz2aQlvVvTW6KSQcW6c6x7Q==
>X-WBNR-Posting-Host: 209.217.222.70
>From: "=?Utf-8?B?U211cmZtYW4=?=" <smurfman@news.postalias>
>References: <7653072C-94F6-4206-997C-24CED9D1B17F@microsoft.com>
<eJoPf5mbFHA.228@TK2MSFTNGP12.phx.gbl>
<827F4AE0-9084-4411-9B4D-095A88F5BDB9@microsoft.com>
<4gjpAcIcFHA.3052@TK2MSFTNGXA01.phx.gbl>
>Subject: Re: Removing SCSI Hardware Entries
>Date: Wed, 22 Jun 2005 08:15:08 -0700
>Lines: 160
>Message-ID: <4C8FFB98-E301-47BD-BCA0-D22724DCA179@microsoft.com>
>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.0
>Newsgroups: microsoft.public.win2000.setup_deployment
>NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
>Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGXA03.phx.gbl
>Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.win2000.setup_deployment:3065
>X-Tomcat-NG: microsoft.public.win2000.setup_deployment
>
>Thanks again.
>Changed the card, still the same results. Received a new unit, same
results.
>Finally what I noticed in the hardware config of the Tape Drive, was that
>there was no BarCode Reader Installed. The original hardware had a bar
code
>reader for LTO tapes, the BrightStore software supports a bar code, and
>allows for quicker inverntory of daily tapes. But with out a bar code
reader
>installed in the unit, the software times-out, and dismounts the slots in
the
>library.
>
>The manufacturer sent a reader, installed it, and problem solved. Who
knew!
>
>Thanks for the Device Manager tips though, I will be adding this to my bag
>of tricks.
>J
>
>""Rebecca Chen [MSFT]"" wrote:
>
>> According to your description, I believe this is the SCSI card issue. It
is
>> possible that the card corrupted and Windows cannot recongnize it.
>>
>> Please contact the SCSI manufacturer to change card to test this issue.
>>
>> Good luck!
>>
>> --------------------
>> >Thread-Topic: Removing SCSI Hardware Entries
>> >thread-index: AcVwNbYI8OM8tuL/TtapWn8USu1DPQ==
>> >X-WBNR-Posting-Host: 209.217.222.70
>> >From: "=?Utf-8?B?U211cmZtYW4=?=" <smurfman@news.postalias>
>> >References: <7653072C-94F6-4206-997C-24CED9D1B17F@microsoft.com>
>> <eJoPf5mbFHA.228@TK2MSFTNGP12.phx.gbl>
>> >Subject: Re: Removing SCSI Hardware Entries
>> >Date: Mon, 13 Jun 2005 09:34:03 -0700
>> >Lines: 76
>> >Message-ID: <827F4AE0-9084-4411-9B4D-095A88F5BDB9@microsoft.com>
>> >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.0
>> >Newsgroups: microsoft.public.win2000.setup_deployment
>> >NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
>> >Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGXA03.phx.gbl
>> >Xref: TK2MSFTNGXA01.phx.gbl
microsoft.public.win2000.setup_deployment:3029
>> >X-Tomcat-NG: microsoft.public.win2000.setup_deployment
>> >
>> >Hi Guys,
>> >Excellent info...I was able to run the commands as you outlined, and
>> removed
>> >the phantom devices that were listed, and corresponded to the registry
>> >entries that I found.
>> >
>> >However, my problem did not go away. The server still hung during the
>> boot
>> >process, so I flip flopped the devices attached to the two channels,
and
>> the
>> >problem moved to the other device. I suspect at this point I have a
SCSI
>> >card issue that has been masking my Backup Software issues...just not
sure
>> >why all of a sudden for a windows boot that the issue started.
>> >
>> >Thanks guys
>> >J
>> >
>> >"Dave Patrick" wrote:
>> >
>> >> 1.) To display hidden devices, non-Plug and Play devices, and devices
>> not
>> >> attached to the computer (commonly known as "ghosted" or "phantom"
>> devices)
>> >> Save the following two lines as a file then execute.
>> >>
>> >> --------------------------setdev.bat---------------------
>> >> set DEVMGR_SHOW_NONPRESENT_DEVICES=1
>> >> start devmgmt.msc
>> >> ---------------------------------------------------------
>> >>
>> >> Then, View|Show Hidden Devices to remove or reconfigure these
devices.
>> Do
>> >> not edit the registry.
>> >>
>> >>
>> >> 2.) Try F8 at startup and 'Enable Boot Logging' then look for
>> 'ntbtlog.txt'
>> >> in the %windir% directory.
>> >>
>> >> --
>> >> Regards,
>> >>
>> >> Dave Patrick ....Please no email replies - reply in newsgroup.
>> >> Microsoft Certified Professional
>> >> Microsoft MVP [Windows]
>> >> http://www.microsoft.com/protect
>> >>
>> >> "Smurfman" wrote:
>> >> |I am looking for a way to remove old SCSI hardware that is reporting
in
>> the
>> >> | SCSI devices in the registry.
>> >> |
>> >> | Situation:
>> >> | After replacing a "PLASMON FTA" tape library, the new unit came
wiht an
>> >> | Identity String of "EXABYTE 110L". Windows detected and created
the
>> >> strings
>> >> | in the SCSI devices with no problems, but after correcting the
Identity
>> >> | String to "PLASMON FTA" Windows 2000 Server hangs during the boot
>> process
>> >> | until I either power fail the unti, or perform a soft reset of the
>> unit.
>> >> |
>> >> | My goal is to remove the settings in the registry so that windows
knows
>> >> | nothing about the old or the new Library and allow the SCSI device
to
>> be
>> >> | redetected.
>> >> |
>> >> | I tried to delete the registry entries for the devices, and windows
>> will
>> >> not
>> >> | allow me.
>> >> |
>> >> | So my question is how do I get rid of the old SCSI devices, because
I
>> >> | suspect that there is a windows conflict in what it sees during the
>> boot,
>> >> 2
>> >> | devices identicle but with different strings and windows does not
know
>> >> which
>> >> | one to load.
>> >> |
>> >> | Additionally, where can I log the boot process to see exactly what
is
>> >> going
>> >> | on behind the scenes? And trace any issues that might be happening.
>> >> |
>> >> | Thanks
>> >> | J
>> >>
>> >>
>> >>
>> >
>>
>> Best regards,
>>
>> Rebecca Chen
>>
>> MCSE2000 MCDBA CCNA
>>
>>
>> Microsoft Online Partner Support
>> Get Secure! - www.microsoft.com/security
>>
>> =====================================================
>>
>> When responding to posts, please "Reply to Group" via your newsreader so
>> that others may learn and benefit from your issue.
>>
>> =====================================================
>> This posting is provided "AS IS" with no warranties, and confers no
rights.
>>
>>
>
There are 583 identified and unidentified users. To see the list of identified users, Click here.
You are about to answer a thread that has been inactive for more than 6 months.
If you still wish to proceed, please ensure that your posting is original and does not duplicate or overlap any prior responses to this thread.

