San Boot Win2K8 R2 SP1 x64 on UCS blades B with M81KR installation issue

I am trying to install a storage San Boot Win2K8 R2 SP1 x64 on UCS blades,(There are only 1 path to the OS installation drive during the installation.)
I loaded drivers for the M81K2 following the "UCS Windows Install Guide" , and I can see the LUN I mapped from XIV. I was able to create and format partitions, make it online, but when
I try to install, windows gives the error:"Windows cannot be installed to this disk. The computer's hardware may not support booting to this disk. Ensure that the disk's controller is enabled in the computer's BIOS menu."
any one know this issue?
Thanks

My UCS manager firmware and Adapter is 1.3.1p,
the boot policy has been set to Boot to SAN,
I checked "Hardware and Software Interoperability Matrix for UCS System Release 1.3.1"
It seems the 1.3.1 only can support the "windows 2008 r2 x64 w/Hyper-v",
so, I updated the UCS manager Bios and the adpter firmware to 2.0, but the I/O module still is 1.3.1p
I can install the "windows 2008 r2 x64" successfuly...
Now, my concern is I have a mix component software versions on my ucs blade(I used the UCS manager 1.3.1, IO module 1.3.1, the UCS Bois 2.0.1 and the adapter 2.0.1)
will the mix component software versions cause some other issues? Dose anyone can give me some suggestion?
Thanks a lot

Similar Messages

SAN Boot Target-Cisco folks, please advise

Hi:
Just want to know the difference of the following 2 configurations for SAN Boot for UCS with 2 WWPNs being presented from SAN Storage
Array: I know 1 will work, but how about Option 2????
Cisco UCS manual DOES NOT go into the details needed.
1.
SAN Primary, SAN Target Primary- vHBA-A - Fabric A
SAN Secondary, SAN Target Primary - vHBA-B - Fabric B
VS
2.
SAN Primary, SAN Target Primary - vHBA-A - Fabric A
SAN Secondary, SAN Target Secondary - vHBA-B - Fabric B
Thanks.
KP Sim

I don't think the system will let you introduce a secondary target on the second vHBA if you haven't defined a primary target for that vHBA.
SAN boot works as follows if you have a policy with 4 targets and 2 vHBAs:
1. try primary vHBA, first (primary) target
2. if that doesn't work, try secondary target on primary vHBA
3. if that doesn't work, switch to secondary vHBA, primary target
4. if that doesn't work, try secondary target on secondary vHBA

Cisco UCS Blade Deployment Without N5K or N7K ?

Dear all,
Is it possbile to deploy cisco UCS blade solution with only Blade Chassis, FI, FEX/IOM and using third party SAN and LAN switch ?
Thanks

Yes of course !
There are many installations with e.g. Brocade FC switches
The only caveat I see: are your uplink ethernet switches 1G or 10G; technically either one will work, however, with 1 G Northbound connectivity, some data flows are limited in bandwidth. see below

UCS 1.4(3M) BIOS Issue ? no network/san boot when diskless

Recreated faithfully on multiple blades and chassis with VIC cards. Have many SAN boot nodes in production and testing and after upgrading firmware this week anytime I apply my store policy of "diskless" to a blade I lose the ability to boot from network. After much effort to work around comes down to no matter what I do with diskless storeage policy, the configured boot order will never become the actual boot order. In the BIOS all network boot options/reference are invisible, cannot enable nor add to options. Upon removing diskless storeage profile and applying "any other that I have" I see in FST that it's powering up internal storage, starting up and updating pre-boot environments, and other things related that connected the dots. Returning to BIOS all reference and options have returned as I expected due to actual boot order screen updating to match configured order and hba's of course login the fabric right away, boot is fine. While I can faithfully replice across many, many blades, they are all the models with same mezz running 1.4.3 so curious if anyone else is seeing, particuaraly now with new version out, as I have done last few weeks without issues leading me towards the firmware.
In a nut shell I see that when going diskless this is actually shutting down the storage/raid controller. i can see that clearly but no bios access to it and not sure what else is or why it's affecting network and hba also since I cannot see, it's shutting more down than low powering drive side raid. I use different profiles due to some blades having disks removed, some retain them. moving a san boot service-profile dynamically around multiple chassis will fail to associate with errors on some due to disk setup and all that. some i have disks pulled and diskless based on documentation and best practices as this customer needed several san boot only blades in that pool. But yes if I use a storage profile allowing "any disk config" for association whether it has disks, no disks, raided drives, replaces the diskless policy in same service profile it faithfully follows my boot order and boots via hba's across multiple blades, up to about 8 or 10 as of today.....b200-m2's with vic's
thx
dave

My UCS manager firmware and Adapter is 1.3.1p,
the boot policy has been set to Boot to SAN,
I checked "Hardware and Software Interoperability Matrix for UCS System Release 1.3.1"
It seems the 1.3.1 only can support the "windows 2008 r2 x64 w/Hyper-v",
so, I updated the UCS manager Bios and the adpter firmware to 2.0, but the I/O module still is 1.3.1p
I can install the "windows 2008 r2 x64" successfuly...
Now, my concern is I have a mix component software versions on my ucs blade(I used the UCS manager 1.3.1, IO module 1.3.1, the UCS Bois 2.0.1 and the adapter 2.0.1)
will the mix component software versions cause some other issues? Dose anyone can give me some suggestion?
Thanks a lot

Dose UCS B200 release 1.3.1 with M81KR support the Sanboot Win2K8 R2 SP1?

I have a UCS blade B200 need to install a storage sanboot system Win2K8 R2 SP1. the HBA is M81KR, the current UCS manager release is 1.3.1p, and the adapter firmware is the 1.0.1. looks like the below picture
I check the Interoperability Matrix of 1.3.1, it seems only support the OS version Windows Server 2008 R2 w/Hyper-V.
so, my question is, if I want to install a sanboot system Win2K8 R2 SP1, I should only update the hba firmware to 1.3.1p? or update the UCS Bios and UCS manager and hba adapter firmware both to the latest version 2.0.1?
Currently,
"Windows cannot be installed to this disk. The computer's hardware may not support booting to this disk. Ensure that the disk's controller is enabled in the computer's BIOS menu." will happen during installing the OS
who can give me some advise?
thanks a lot

#1 - you definitely need to update your UCS Manager and adapter BIOS. You are more than 1 year behind.
You need to check a few things:
1) If you using Virtual Media to install, make sure you re-mount the OS media and click the refresh button.
2) Make sure the UCS Boot Policy has a matching LUN number to the LUN being presented by the array to the host.
3) Make sure the target (array) WWPN in the UCS Boot Policy matches the array's WWPN that the adapter can see on the perspective fabric.
For #2 and #3, you will know if you have it right during the server POST when it initializes the M81KR - it will display the array's WWPN and the LUN ID. If it just pauses and never displays this, something is wrong in the Boot Policy. You will need to disable "Quite Boot" the server bios to watch Palo initialize and see these messages.

UCS C Series SAN Boot

Hi All,
How to configure SAN Boot on the UCS C Series platform ?
On B Series, we can configure the boot order from vHBA, but on the UCS C Series I found nothing.
The C Series SAN boot had being enabled and also the boot target was configured on the vHBA properties, but the C Series can't boot from SAN
Attached are the detailed of the configuration on C Series
Please help, if you have C Series boot from SAN succesfully
Thanks,
Gofi

Hi Padma,
Yes, that will be the flogi into the upstream switch.
Below are the configurations of Nexus 5K, while I used 2 N5k as the upstream FCoE switch
N5K1# sh run int vfc113
!Command: show running-config interface vfc113
!Time: Wed Jun 17 03:21:56 2009
version 5.2(1)N1(5)
interface vfc113
bind interface Ethernet113/1/1
switchport trunk allowed vsan 10
no shutdown
N5K1# sh run int eth113/1/1
!Command: show running-config interface Ethernet113/1/1
!Time: Wed Jun 17 03:22:05 2009
version 5.2(1)N1(5)
interface Ethernet113/1/1
switchport mode trunk
switchport trunk allowed vlan 10,120,125,130,135,200-201
N5K1# sh run | sec fex
feature fex
fex 113
pinning max-links 1
description "FEX0113"
fcoe
fex 123
pinning max-links 1
description "FEX0123"
N5K1# sh feature | i fcoe
fcoe                  1         enabled
fcoe-npv              1         disabled
N5K2# sh run int vfc123
!Command: show running-config interface vfc123
!Time: Wed Jun 17 03:24:12 2009
version 5.2(1)N1(5)
interface vfc123
bind interface Ethernet123/1/1
switchport trunk allowed vsan 20
no shutdown
N5K2# sh run int eth123/1/1
!Command: show running-config interface Ethernet123/1/1
!Time: Wed Jun 17 03:24:29 2009
version 5.2(1)N1(5)
interface Ethernet123/1/1
switchport mode trunk
switchport trunk allowed vlan 20,120,125,130,135,200-201
N5K2# sh run | sec fex
feature fex
fex 113
pinning max-links 1
description "FEX0113"
fex 123
pinning max-links 1
description "FEX0123"
fcoe
N5K2# sh feature | i fcoe
fcoe                  1         enabled
fcoe-npv              1         disabled
The CNA server connected to FEX Nexus 2K, while the Nexus uplinks are controlled by 2 Nexus 5Ks (vPC on the N5K)
Any suggestions ?
Thanks,
Gofi

UCS Central - Making Boot Policy - SAN boot target Provisioning

Gents
Some objects is always related to the domains and need to be provisioned in global like
VLANs: but we can did it by Provisioning VLANs with UCS Central Using VLAN ID Aliasing.
VSANs: the same idea in VLAN ID Aliasing.
Boot Policy adding SAN boot target : what about this issue how can I provision it so I can configure it globally in abstract way then it will take targets depend on domain during associating the global service profile.

@Gmonroy
Thanks for support
But if I need to make a global Service profile temp so I can deploy SF from it in any domain, and if I referenced this service profile temp to one boot policy so i need to unbind each service profile created from this temp to associate a different boot policy in each domain ? " I will lose the benefit of updating service profile template "
Or I have to create different template per domain ? " I will lose the key benefit of centralizing Templates in UCS central"
Or there is any workaround to deply this senario.

B230-M2 - MK81KR - Win 08 R2 San Boot

Chaps.
I need to SAN boot this server with Win 08 R2 on the metal.
Service profile works with VMware, so the Zoning/Masking is correct.
On install from 08 Disk, no Hard Drives shown, I loaded the Cisco Storage Driver, now I see the Lun twice, Disk1
Unpartitioned space and Disk2 Unpartitioned space.
There is a Bios not enabled warning when I try to install.
UCS Version 1.4.3Q
Driver Disk : 1.4.1
Please assist
Danie

No change on either option.
On the CD sequence.
I clicked load driver, mounted the 1.4.3 Drivers cd, browsed to Windows\Storage\Cisco\MK81KR\Win08R2\64
I listed the driver.
I then mounted the Win08 cd, and clicked next to load the driver, it could not find the path, as I had un-mounted the driver disk, so remounted 1.4.3, clicked next, green bas flashed a couple of times, and I got to the Where do you want to install screen. My 40GB disk showed as offline.
Mounted the Win08 Disc, and clicked refresh, twice....
Disk stayed offline, show details on the error allowed me to bring the disk online.
Now the error stated that the BIOS is not setup for booting of this controller, ignored the warning, and clicked next.
Setup was unable to create a new system partition or locate an existing system partition.
I can create and delete partitions manually.
EFI disabled and the same install sequence, same results
Thanx

XenServer 6.1 SAN boot on B200M2

I'm new to XenServer. We have UCS with B200M2's with the M81KR CNA in them. We primarily use VMware ESXi and we SAN boot all of those machines. We have had no issue SAN booting ESXi servers. I've created a new serivce profile template for the XenServer's and brought up a couple machines. I've allocated the storage and when I got to install XenServer it doesn't see the boot LUNs. I know the storage is allocated properly. I can see the LUNs when the blade is booting and I can install ESXi onto the boot LUNs without issue. The issue is with XenServer seeing the LUN. I did the F2 > mulitpath option that it says to do in the Appendix of the install guide for XenServer but that makes no difference. What needs to be done to have XenServer see a boot LUN on a B200M2?

6.0
Please see the UCS Support Matrix tool for further info:
http://www.cisco.com/web/techdoc/ucs/interoperability/matrix/matrix.html
Support is coming in the upcoming UCSM 2.1 release before the end of the year (tentatively). I'm just confirming if support will be included in a future 2.0.x patch or not.
Regards,
Robert

Long loading Win7 SP1 x64 after installing the driver

Good day!
Installed on a laptop Lenovo IdeaPad B570 59329770 (59-329770) operating system Windows 7 SP1 x64, then started to put the drivers from the disc that came in the kit and noticed that much longer to boot the system and not only greatly increased the time off the computer. In the system messages of this inhibition is written. Through trial and error, found that a driver card reader. Once the driver is removed - the system again loaded quickly. Driver is removed and the unit is now and hangs unidentified, but the system does not boot for a long time (start or shutdown for about three minutes.)
Has anyone encountered similar? How to decide? Pay attention to the operating system.

Windows usually makes a restore point before installing drivers.
So the simple fix to get rid of the bad one...
Repeatidly tap F8 over and over at startup... that will take you to the Optional startup menu.
I would choose StartUp Repair .. which will tak you to another window...
There I would use System Restore and choose the restore point that was made before the bad driver was installed.

Print spooler log error ID 808 [Internet Explorer 11 + MS Office 2003 x86 on Win7 sp1 x64 ONLY!]

howdy all,
Could you please help me to resovle the very much odd issue of HP Priner driver on Win7sp1x64 as below.
1.HP Deskjet 970Cse printer connected thru usb to a router and installed to all LAN PCs thru a standard tcp/ip ports works well (i.e. printing anyting w/o any problem) on 3 PCs - 2 of 3 with win7sp1x64; and 1 of 3 - win7sp1x86. All 3 with
IE11[11.0.9600.17041] recently(!) updated from IE8.
2. However BOTH (that is 2 of 3) above PCs of win7sp1x64 return errors to admin log every time when printing any web page from IE11 and/or docs from Office as below:
Error in short:
The print spooler failed to load a plug-in module C:\Windows\system32\spool\DRIVERS\x64\3\UNIDRVUI.DLL, error code 0xc1. See the event user data for context information.
This error in log occurs only if printing from IE11 and/or MS Office. None of other printing jobs are affected including a printing from Acrobat, ACDSee, Google Chrome and Opera. The printing of Test Page by printer
itself not affected as well!!!
3. win7sp1x86 PC prints everything w/o any errors in log!
4. Printer uninstall incl. cleaning of Print Server config + clean install doesn't work.
5. Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\..>printui /s /t2
C:\Users\..>filever c:\windows\system32\spool\drivers\x64\3\*.dll
--a-- W32x64 DLL ENU      11.0.0.305 shp     55,432 09-23-2012 adobepdf.dll
--a-- W32x64 DLL ENU      11.0.0.305 shp     26,768 09-23-2012 adobepdfui.dll
--a-- W32x64 DLL ENU      11.0.0.305 shp     39,048 09-23-2012 adregp.dll
--a-- W32x64 DLL ENU      11.0.0.305 shp 1,294,472 09-23-2012 aduigp.dll
--a-- W32x64 DRV ENU 6.1.7601.17514 shp    623,104 11-21-2010 fxsapi.dll
--a-- W32x64 DRV ENU 0.3.7601.17514 shp    380,416 11-21-2010 fxsdrv.dll
--a-- W32x64 DRV ENU 6.1.7601.17514 shp 6,566,400 11-21-2010 fxsres.dll
--a-- W32x64 DRV ENU 6.1.7601.17514 shp    434,688 11-21-2010 fxstiff.dll
--a-- W32x64 DRV ENU 6.1.7601.17514 shp    160,256 11-21-2010 fxsui.dll
--a-- W32x64 DRV ENU 6.1.7601.17514 shp    156,672 11-21-2010 fxswzrd.dll
--a-- W32x64 DLL ENU         1.0.0.1 shp    522,240 06-22-2009 hpf900al.dll
--a-- W32x64 DLL ENU        0.20.6.0 shp 1,692,672 05-07-2008 hpfimg50.dll
--a-- W32x64 DLL ENU         1.0.0.1 shp     79,872 05-07-2008 hpfud50.dll
--a-- W32x64 DLL ENU         1.0.0.1 shp    134,144 06-22-2009 hpfui50.dll
--a-- W32x64 DRV ENU 0.3.7601.18126 shp 1,402,880 04-10-2013 jnwdrv.dll
--a-- W32x64 DRV ENU 0.3.7600.16385 shp     98,816 07-14-2009 jnwdui.dll
--a-- W32x64 DLL ENU         1.0.0.1 shp     16,384 09-20-2010 oemps.dll
--a-- W32x64 DRV ENU 0.3.7601.21853 shp    854,304 12-04-2013 ps5ui.dll
--a-- W32x64 DRV ENU 0.3.7601.21853 shp    636,704 12-04-2013 pscript5.dll
--a-- W32x64 DRV   -       0.3.151.3 shp     47,392 12-08-2013 tpprn.dll
--a-- W32x64 DLL ENU     7.15.297.19 shp    172,328 12-08-2013 tpprnui.dll
--a-- W32x64 DLL   -     7.15.297.20 shp     75,512 12-08-2013 tpprnuichs.dll
--a-- W32x64 DLL CHT     7.15.297.21 shp     75,544 12-08-2013 tpprnuicht.dll
--a-- W32x64 DLL   -     7.15.297.22 shp     80,208 12-08-2013 tpprnuicsy.dll
--a-- W32x64 DLL DEU     7.15.297.23 shp     81,704 12-08-2013 tpprnuideu.dll
--a-- W32x64 DLL   -     7.15.297.24 shp     80,200 12-08-2013 tpprnuiell.dll
--a-- W32x64 DLL ESN     7.15.297.25 shp     80,712 12-08-2013 tpprnuiesn.dll
--a-- W32x64 DLL   -     7.15.297.26 shp     81,208 12-08-2013 tpprnuifra.dll
--a-- W32x64 DLL   -     7.15.297.27 shp     80,224 12-08-2013 tpprnuihun.dll
--a-- W32x64 DLL JPN     7.15.302.41 shp     76,656 12-08-2013 tpprnuijpn.dll
--a-- W32x64 DLL   -     7.15.297.29 shp     76,568 12-08-2013 tpprnuikor.dll
--a-- W32x64 DLL   -     7.15.297.30 shp     80,176 12-08-2013 tpprnuiplk.dll
--a-- W32x64 DLL   -     7.15.297.31 shp     79,680 12-08-2013 tpprnuiptg.dll
--a-- W32x64 DLL   -     7.15.297.32 shp     80,728 12-08-2013 tpprnuirus.dll
--a-- W32x64 DLL   -     7.15.297.33 shp     80,184 12-08-2013 tpprnuitha.dll
--a-- W32x64 DLL   -        7.9.30.2 shp    152,816 12-08-2013 tpps.dll
--a-- W32x64 DRV ENU 0.3.7601.17514 shp    479,232 11-21-2010 unidrv.dll
--a-- W32x64 DRV ENU 0.3.7601.17514 shp    884,224 11-21-2010 unidrvui.dll
--a-- W32x64 DRV ENU 0.3.7601.17514 shp    762,368 11-21-2010 unires.dll
6. C:\Windows\System32
spoolss.dll = v6.1.7600.16385
spoolsv.exe = v6.1.7601.22149
C:\Windows\SysWOW64
spoolss.dll = v6.1.7600.16385
spoolsv.exe = v6.1.7600.16385
7. I blame IE11 when there was no such error before its update from IE8.
8. This is a re-repost from here "http://answers.microsoft.com/en-us/ie/forum/ie11-windows_7/print-spooler-log-error-id-808-internet-explorer/f52ff25c-4702-4ce3-827e-e1e9a5d324cf" and here "http://social.technet.microsoft.com/Forums/windows/en-US/7b24d6b9-171a-4703-82f9-81cb4732e02f/print-spooler-log-error-id-808-internet-explorer-11-ms-office-20032007-x86-on-win7-sp1-x64?forum=w7itproappcompat"
w/o any good answer!
That's it. Any questions are welcome.
Thank you.
PS: I just wanna confirm that this odd error occurs only when printing from IE11 and MS Office 2003 on Win7sp1x64. MS Office 2007 is not affected!

OK, Z COMPLETE SOLUTION FOUND!
Although z cause of this odd issue is yet unclear. However it seems to be z HP driver problem after all.
Actually my printer is not HP Deskjet 970Cse but HP Photosmart 1115 Series. Z very nice working dinosaur, which was officially run out by HP Support from WinXPx86 times. Though it was always working
just nice with either HP Deskjet (DJ) 970Cse Win7driver (better) or HP Photosmart (PS) 7200 Series one (worse – when it works no so good with TCP/IP printer installation).
Well… when I got into z recent problem with DJ970cse driver I happened to check if printer works with z PS7200 one. Oops, same not good as before but NO LOG ERROR! A bit of study gave me understanding
that both drivers are using z absolutely same core files but PS7200 driver uses its own PCL Language Monitor as well as z Print Processor (not a standard winprint of Windows).
And while I unfortunately got no any reasonable ideas on how to solve this issue from IT Pros and others MS MVP during a few days after my posting here and there, except those very smart ones
like ‘uninstall, reboot and install again’, I had no option other than to find solution by myself.
I’ve downloaded a bunch of HP printer models Win7x64 driver pack from MS Update Catalog "http://catalog.update.microsoft.com/v7/site/Search.aspx?q=hp%20deskjet%20970cse" (x86 also available.
This driver pack is for maybe over 400 HP printer models incl. both DJ970Cse & PS7200) and modded its genuine INF file for HardwareID of my PS1115 as HPPHOTOSMART_11150FFF with use of 970Cse driver but also some DLLs and PCL Language Monitor
of PS7200 one.
This modded by me INF file is attached as a Code Block. Pls be advised that all originally integrated printer devices strings except DJ970cse & PS7200 ones were deleted for convenience and
z 1 new combined string for PS1115 added. Then everybody interested can compare & track z changes done. This modded driver is now installed and working w/o any glitch on 2 of my Win7sp1x64 PCs. Although I’ve maybe spent totally a day or
so on all that fuss of posting about & studying around.
My final conclusion is z very much common one
– f**k HP… and/or MS as well, when it’s yet unknown why this error occurred after z years of no problem use of DJ970Cse driver but after Win7sp1 updating to IE11 and/or KB2775511 and only with x64 version
of OS.
bye for now.
PS: btw, why I’m not able to attach any small text file or post a link to MS site here???!!!
END
UPDATE 2014-06-12-Thu: there is one more small glitch of printing to paper from IE11 only found! now it's about a Print Processor settings...
pls set not any hp oem print processor but z standard windows one aka 'winprint' to be used for printing in Printer properties > Advanced sub-menu, otherwise a printout is incorrect in part of a printed page header &
footer. a page print preview is ok but z printed header is incomplete = cut at right side, and no footer printed at all.
pls be advised that above note is valid for both modded & genuine driver installed and for both x86 & x64 win7...
rgds,
; Windows Inbox Printer Drivers
[Version]
Signature="$Windows NT$"
Provider="Microsoft"
ClassGUID={4D36E979-E325-11CE-BFC1-08002BE10318}
Class=Printer
CatalogFile=prnhp001.cat
DriverVer=06/21/2006,6.1.7233.0
[Manufacturer]
"HP"=HP,NTamd64
[HP.NTamd64]
"HP DeskJet 970Cse" = HPFDJ97E.GPD,HEWLETT-PACKARDDESKJ8FFF,HP_DeskJet_970Cse ; Hardware ID
"HP Photosmart 1115 Series" = HPFDJ97E.GPD.ICM_LH_PHASE5,HPPHOTOSMART_11150FFF,HP_Photosmart_1115_Series ; Hardware ID
"HP Photosmart 7200 Series" = HPP7200T.GPD.ICM_LH_PHASE5,hpphotosmart_7200_se8fD3,hpphotosmart_7200_se5294,HP_Photosmart_7200_Series ; Hardware ID
[OEM URLS]
"HP"="http://go.microsoft.com/fwlink/?LinkID=37&prd=10798&sbp=Printers"
[Previous Names]
"HP DeskJet 970Cse"="HP DeskJet 970C Series"
[ControlFlags]
ExcludeFromSelect=HWPC211,HWP2250,HWP2286,HWP2284,HWPC212,HWP2140,\
HWP21A0,HWP20F0,HWP2160,HWP20D0,HWP20E0,HWP2100,HWP21B0,HWP21E0,\
Hewlett-PackardHP_LaD4FF,Hewlett-Packardhp_LaFBC4
[HPFDJ97E.GPD]
[email protected],@HPFUD50.DLL,@HPFUI50.DLL,@HPFIMG50.DLL,@HPF900AL.DLL,@HPFDJ97E.GPD,@HPFDJ970.GPD,@HPFDJ97X.GPD,@HPFNAM50.GPD
DataFile=HPFDJ97E.GPD
CoreDriverSections="{D20EA372-DD35-4950-9ED8-A6335AFE79F0},UNIDRV.OEM,UNIDRV_DATA","{D20EA372-DD35-4950-9ED8-A6335AFE79F3},sRGBPROFILE.OEM"
[HPFDJ97E.GPD.ICM_LH_PHASE5]
CopyFiles=HPC_COMMON_LH,HP_PRNPROC,@HPFDJ50.INI,@HPFUD50.DLL,@HPFUI50.DLL,@HPFIMG50.DLL,@HPF900AL.DLL,@HPFDJ97E.GPD,@HPFDJ970.GPD,@HPFDJ97X.GPD,@HPFNAM50.GPD,@HPZEVLHN.DLL,@HPZSTLHN.DLL,@HPZUILHN.DLL,HP_LANGMON
DataFile=HPFDJ97E.GPD
LanguageMonitor="PCL hpz3llhn,hpz3llhn.dll"
PrintProcessor="hpzpplhn,hpzpplhn.dll"
CoreDriverSections="{D20EA372-DD35-4950-9ED8-A6335AFE79F0},UNIDRV.OEM,UNIDRV_DATA"
[HPP7200T.GPD.ICM_LH_PHASE5]
CopyFiles=HPC_COMMON_LH,HP_PRNPROC,@HPZ3RLHN.DLL,@HPZ3ALHN.DLL,@HPZSSLHN.DLL,@HPP7200T.GPD,@HPP7X00T.GPD,@HPZ3CLHN.INI,@HPZSMLHN.GPD,@HPZ3MLHN.GPD,@HPP7200T.XML,@HPZSCLHN.DTD,@HPFRES50.DLL,@HPFIME50.DLL,@HPFIGLHN.DLL,@HPZPRLHN.DLL,HP_LANGMON
DataFile=HPP7200T.GPD
LanguageMonitor="PCL hpz3llhn,hpz3llhn.dll"
PrintProcessor="hpzpplhn,hpzpplhn.dll"
CoreDriverSections="{D20EA372-DD35-4950-9ED8-A6335AFE79F0},UNIDRV.OEM,UNIDRV_DATA"
[MS_ABOUT_UI]
HPCABOUT.DLL
HPCSTR.DLL
[CIO_COPYFILES_SPOOL]
HPZIDR12.DLL,,,0x00000020
HPZINW12.DLL,,,0x00000020
HPZIPM12.DLL,,,0x00000020
HPZIPR12.DLL,,,0x00000020
HPZIPT12.DLL,,,0x00000020
HPZISN12.DLL,,,0x00000020
[CIO_COPYFILES_SYS32]
HPZIDR12.DLL,,,0x00000020
HPZINW12.DLL,,,0x00000020
HPZIPM12.DLL,,,0x00000020
HPZIPR12.DLL,,,0x00000020
HPZIPT12.DLL,,,0x00000020
HPZISN12.DLL,,,0x00000020
[MS_COLOR]
HPCCLJ1.DLL
HPCCLJUI.DLL
[DMC_x86]
HPCDMCLH.DLL,,,0x00000020
[GPD_COMMON3]
HPZSMLHN.GPD
[DUSTDEVIL_COPYFILES_SPOOL]
HPBMIAPI.DLL,,,0x00000020
HPBMINI.DLL,,,0x00000020
HPBOID.DLL,,,0x00000020
HPBOIDPS.DLL,,,0x00000020
HPBPRO.DLL,,,0x00000020
HPBPROPS.DLL,,,0x00000020
HPEACLHN.HPI,,,0x00000020
[DUSTDEVIL_COPYFILES_SYS32]
HPBMIAPI.DLL,,,0x00000020
HPBMINI.DLL,,,0x00000020
HPBOID.DLL,,,0x00000020
HPBOIDPS.DLL,,,0x00000020
HPBPRO.DLL,,,0x00000020
HPBPROPS.DLL,,,0x00000020
HPEACLHN.HPI,,,0x00000020
[HP_ICC]
HP DJ 6900-PREM PAPER(TRICOLOR+BLACK).ICC,hpf69000.icc,,0x00000020
HP DJ 6900-PREM PAPER(TRICOLOR+GRAY).ICC,hpf69002.icc,,0x00000020
HP DJ 6900-PREM PAPER(TRICOLOR+PHOTO).ICC,hpf69001.icc,,0x00000020
HP DJ 6900-PREM PLUS PHOTO(TRICOLOR+BLACK).ICC,hpf69003.icc,,0x00000020
HP DJ 6900-PREM PLUS PHOTO(TRICOLOR+GRAY).ICC,hpf69005.icc,,0x00000020
HP DJ 6900-PREM PLUS PHOTO(TRICOLOR+PHOTO).ICC,hpf69004.icc,,0x00000020
HP OJ 6300-PREM PAPER(TRICOLOR+BLACK).ICC,hpo63000.icc,,0x00000020
HP OJ 6300-PREM PAPER(TRICOLOR+PHOTO).ICC,hpo63001.icc,,0x00000020
HP OJ 6300-PREM PAPER(TRICOLOR+GRAY).ICC,hpo63002.icc,,0x00000020
HP OJ 6300- PREM PLUS PHOTO(TRICOLOR+BLACK).ICC,hpo63003.icc,,0x00000020
HP OJ 6300- PREM PLUS PHOTO(TRICOLOR+PHOTO).ICC,hpo63004.icc,,0x00000020
HP OJ 6300- PREM PLUS PHOTO(TRICOLOR+GRAY).ICC,hpo63005.icc,,0x00000020
[HP_LANGMON]
HPZ3LLHN.DLL
[HP_LIDIL_LANGMON]
HPZLLLHN.DLL
[HP_PRNPROC]
HPZPPLHN.DLL
[HPC_COMMON]
HPZEVLHN.DLL
HPZSTLHN.DLL
HPZUILHN.DLL
[HPC_COMMON_LH]
HPZEVLHN.DLL
HPZSTLHN.DLL
HPZUILHN.DLL
[HPCLJ5V2_COLOR]
HPCLJ5.ICM
[HPDJ500C_COLOR]
HP500ND.ICM
HP500NG.ICM
[HPPRPROC]
HPZPPLHN.DLL,,,0x00000020
[MANUAL_DUPLEX]
HPZEVLHN.DLL,,,0x00000020
[PSRENDER]
HPZSRLHN.DLL,,,0x00000020
[RENDER]
HPZ5RLHN.DLL,,,0x00000020
[RES_COMMON]
HPZSTLHN.DLL,,,0x00000020
[STRING_DLL]
HPZSTLHN.DLL,,,0x00000020
[UI]
HPZLSLHN.DLL,,,0x00000020
HPZSSLHN.DLL,,,0x00000020
HPZUILHN.DLL,,,0x00000020
[PML_user_Inst.AddService]
; PML Service configuration info
DisplayName = "Pml Driver HPZ12"
ServiceType = 0x00000020
StartType = 0x2
ErrorControl = 1
ServiceBinary = %11%\svchost.exe -k HPCIO
AddReg=PML_Addreg
[NET_user_Inst.AddService]
; NET Service configuration info
DisplayName = "NET Driver HPZ12"
ServiceType = 0x00000020
StartType = 0x2
ErrorControl = 1
ServiceBinary = %11%\svchost.exe -k HPCIO
AddReg=NET_Addreg
[PML_AddReg]
; Registry configuration info
HKLM,SOFTWARE\Microsoft\Windows NT\CurrentVersion\SvcHost,"HPCIO",0x00010008,"Pml Driver HPZ12"
HKLM,SYSTEM\CurrentControlSet\Services\Pml Driver HPZ12\Parameters,"ServiceDll",0x00020000,"%11%\HPZipm12.dll"
[Net_AddReg]
; Registry configuration info
HKLM,SOFTWARE\Microsoft\Windows NT\CurrentVersion\SvcHost,"HPCIO",0x00010008,"NET Driver HPZ12"
HKLM,SYSTEM\CurrentControlSet\Services\Net Driver HPZ12\Parameters,"ServiceDll",0x00020000,"%11%\HPZinw12.dll"
[DustDevilReg]
11,,HPBMIAPI.DLL,1,300
11,,HPBOID.DLL,1,300
11,,HPBOIDPS.DLL,1,300
11,,HPBPRO.DLL,1,300
11,,HPBPROPS.DLL,1,300
[DestinationDirs]
DefaultDestDir=66000
HP_PRNPROC=66001
HPPRPROC=66001
CIO_COPYFILES_SYS32=66002
DUSTDEVIL_COPYFILES_SYS32=66002
HP_LANGMON=66002
HP_LIDIL_LANGMON=66002
HP_ICC=66003
HPCLJ5V2_COLOR=66003
HPDJ500C_COLOR=66003
[SourceDisksFiles]
hpf69000.icc = 1
hpf69001.icc = 1
hpf69002.icc = 1
hpf69003.icc = 1
hpf69004.icc = 1
hpf69005.icc = 1
hpo63000.icc = 1
hpo63001.icc = 1
hpo63002.icc = 1
hpo63003.icc = 1
hpo63004.icc = 1
hpo63005.icc = 1
HP_3P522.PPD = 1
HP4M3_V1.PPD = 1
HP4M6_V1.PPD = 1
HP4ML_V1.PPD = 1
HP4MP3_1.PPD = 1
HP4MP6_1.PPD = 1
HP4MPLS.GPD = 1
HP4PLUS3.PPD = 1
HP4PLUS6.PPD = 1
HP4SI6_1.PPD = 1
HP500ND.ICM = 1
HP500NG.ICM = 1
HP5SI.GPD = 1
HP5SIM.GPD = 1
HPBMIAPI.DLL = 1
HPBMINI.DLL = 1
HPBOID.DLL = 1
HPBOIDPS.DLL = 1
HPBPRO.DLL = 1
HPBPROPS.DLL = 1
HPC1220P.PPD = 1
HPC1220P.XML = 1
HPC1RWSL.PPD = 1
HPC1RWSL.XML = 1
HPC1RXSL.PPD = 1
HPC1RXSL.XML = 1
HPC2GW6L.GPD = 1
HPC2GW6L.XML = 1
HPC3050F.GPD = 1
HPC3050F.XML = 1
HPC3052F.GPD = 1
HPC3052F.XML = 1
HPC3055F.GPD = 1
HPC3055F.XML = 1
HPC3346L.GPD = 1
HPC3346L.XML = 1
HPC3390F.GPD = 1
HPC3390F.XML = 1
HPC34I6L.GPD = 1
HPC34I6L.XML = 1
HPC35W6L.GPD = 1
HPC35W6L.XML = 1
HPC38O6L.GPD = 1
HPC38O6L.XML = 1
HPC3BG6L.GPD = 1
HPC3BG6L.XML = 1
HPC3H06L.GPD = 1
HPC3H06L.XML = 1
HPC3IE6L.GPD = 1
HPC3IE6L.XML = 1
HPC3JS6L.GPD = 1
HPC3JS6L.XML = 1
HPC3UW6L.GPD = 1
HPC3UW6L.XML = 1
HPC3XO6L.GPD = 1
HPC3XO6L.XML = 1
HPC48S6L.GPD = 1
HPC48S6L.XML = 1
HPC5200F.GPD = 1
HPC5201F.GPD = 1
HPC5200F.XML = 1
HPC5201F.XML = 1
HPC520XF.GPD = 1
HPC6686L.GPD = 1
HPC6686L.XML = 1
HPC6906L.GPD = 1
HPC6906L.XML = 1
HPC6AE6L.GPD = 1
HPC6AE6L.XML = 1
HPC6K4SL.PPD = 1
HPC6K4SL.XML = 1
HPC6LI5L.GPD = 1
HPC6LI5L.XML = 1
HPC6LISL.PPD = 1
HPC6LISL.XML = 1
HPC6Y06L.GPD = 1
HPC6Y06L.XML = 1
HPCABOUT.DLL = 1
HPCCLJ1.DLL = 1
HPCCLJ1.INI = 1
HPCCLJUI.DLL = 1
HPCDMCLH.DLL = 1
HPCFONT.DLL = 1
HPCLJ5.ICM = 1
HPCLJ5V2.PPD = 1
HPCSTR.DLL = 1
HPDJ340.GPD = 1
HPDJ340M.GPD = 1
HPDJ400.GPD = 1
HPDJ400M.GPD = 1
HPDJ420.GPD = 1
HPDJ500.GPD = 1
HPDJ500C.GPD = 1
HPDJ5550.CFG = 1
HPDJ600.GPD = 1
HPDJ600M.GPD = 1
HPDJ890C.GPD = 1
HPDJRES.DLL = 1
HPF0450T.GPD = 1
HPEACLHN.HPI = 1
HPF0450T.XML = 1
HPF3550T.GPD = 1
HPF3550T.XML = 1
HPF3650T.GPD = 1
HPF3650T.XML = 1
HPF3745T.GPD = 1
HPF3745T.XML = 1
HPF3840T.GPD = 1
HPF3840T.XML = 1
HPF3920T.GPD = 1
HPF3920T.XML = 1
HPF4A63L.GPD = 1
HPF4A63L.XML = 1
HPF4A6AL.GPD = 1
HPF4BK3L.GPD = 1
HPF4BK3L.XML = 1
HPF5400T.GPD = 1
HPF5400T.XML = 1
HPF5740T.GPD = 1
HPF5740T.XML = 1
HPF5940T.GPD = 1
HPF5940T.XML = 1
HPF6540T.GPD = 1
HPF6540T.XML = 1
HPF6840T.GPD = 1
HPF6840T.XML = 1
HPF6940T.GPD = 1
HPF6940T.XML = 1
HPF6980T.GPD = 1
HPF6980T.XML = 1
HPF880AL.DLL = 1
HPF900AL.DLL = 1
HPF940AL.DLL = 1
HPFDJ50.INI = 1
HPFDJ640.GPD = 1
HPFDJ69X.GPD = 1
HPFDJ6XX.GPD = 1
HPFDJ816.GPD = 1
HPFDJ830.GPD = 1
HPFDJ840.GPD = 1
HPFDJ845.GPD = 1
HPFDJ84X.GPD = 1
HPFDJ89X.GPD = 1
HPFDJ920.GPD = 1
HPFDJ930.GPD = 1
HPFDJ940.GPD = 1
HPFDJ948.GPD = 1
HPFDJ94X.GPD = 1
HPFDJ950.GPD = 1
HPFDJ955.GPD = 1
HPFDJ957.GPD = 1
HPFDJ95X.GPD = 1
HPFDJ96C.GPD = 1
HPFDJ970.GPD = 1
HPFDJ97E.GPD = 1
HPFDJ97I.GPD = 1
HPFDJ97X.GPD = 1
HPFDJ980.GPD = 1
HPFDJ98C.GPD = 1
HPFDJ990.GPD = 1
HPFDJ99E.GPD = 1
HPFDJ99X.GPD = 1
HPFH5900.EXP = 1
HPFIGLHN.DLL = 1
HPFIME50.DLL = 1
HPFIMG50.DLL = 1
HPFNAM50.GPD = 1
HPFRES50.DLL = 1
HPFUD50.DLL = 1
HPFUI50.DLL = 1
HPIII522.PPD = 1
HPIIP522.PPD = 1
HPIJ2280.CFG = 1
HPIJ3000.CFG = 1
HPLJ__31.PPD = 1
HPLJ_3P1.PPD = 1
HPLJ1100.GPD = 1
HPLJ2.GPD = 1
HPLJ21P6.GPD = 1
HPLJ2300.CFG = 1
HPLJ2P.GPD = 1
HPLJ2PP.GPD = 1
HPLJ2X.GPD = 1
HPLJ3.GPD = 1
HPLJ3P.GPD = 1
HPLJ4.GPD = 1
HPLJ4100.CFG = 1
HPLJ4200.CFG = 1
HPLJ4300.CFG = 1
HPLJ4550.CFG = 1
HPLJ4600.CFG = 1
HPLJ4L.GPD = 1
HPLJ4M.GPD = 1
HPLJ4ML.GPD = 1
HPLJ4MV.GPD = 1
HPLJ4MV1.PPD = 1
HPLJ4P.GPD = 1
HPLJ4PS.GPD = 1
HPLJ4SI.GPD = 1
HPLJ4V.GPD = 1
HPLJ5.GPD = 1
HPLJ5100.CFG = 1
HPLJ5500.CFG = 1
HPLJ5L.GPD = 1
HPLJ5M.GPD = 1
HPLJ5M_4.PPD = 1
HPLJ5MP.GPD = 1
HPLJ5N.GPD = 1
HPLJ5P.GPD = 1
HPLJ5P_1.PPD = 1
HPLJ5SI1.PPD = 1
HPLJ5SIM.PPD = 1
HPLJ6L.GPD = 1
HPLJ6MP.GPD = 1
HPLJ6P.GPD = 1
HPLJ6P_4.PPD = 1
HPLJ8150.CFG = 1
HPLJ8550.CFG = 1
HPLJ9000.CFG = 1
HPMCPB25.GPD = 1
HPMCPC25.GPD = 1
HPMCPC25.PPD = 1
HPMCPD25.CFG = 1
HPMCPD25.PPD = 1
HPMCPDP5.XML = 1
HPMCPDPS.XML = 1
HPMCPL25.GPD = 1
HPMCPM25.GPD = 1
HPMOJ50.INI = 1
HPMOJR40.GPD = 1
HPMOJR45.GPD = 1
HPMOJR4I.GPD = 1
HPMOJR60.GPD = 1
HPMOJR65.GPD = 1
HPMOJR80.GPD = 1
HPMOJR8I.GPD = 1
HPMOJRX.GPD = 1
HPMOPY.GPD = 1
HPMOPYUI.INI = 1
HPMPSC50.GPD = 1
HPO0410T.GPD = 1
HPO0410T.XML = 1
HPO1100T.GPD = 1
HPO1100T.XML = 1
HPO1200T.GPD = 1
HPO1200T.XML = 1
HPO1300T.GPD = 1
HPO1300T.XML = 1
HPO1310T.GPD = 1
HPO1310T.XML = 1
HPO13X0T.GPD = 1
HPO1400T.GPD = 1
HPO1400T.XML = 1
HPO1500T.GPD = 1
HPO1500T.XML = 1
HPO1600T.GPD = 1
HPO1600T.XML = 1
HPO1X00T.GPD = 1
HPO2100T.GPD = 1
HPO2100T.XML = 1
HPO2150T.GPD = 1
HPO2150T.XML = 1
HPO2170T.GPD = 1
HPO2170T.XML = 1
HPO2200T.GPD = 1
HPO2200T.XML = 1
HPO2300T.GPD = 1
HPO2300T.XML = 1
HPO2350T.GPD = 1
HPO2350T.XML = 1
HPO2400T.GPD = 1
HPO2400T.XML = 1
HPO2500T.GPD = 1
HPO2500T.XML = 1
HPO2600T.GPD = 1
HPO2600T.XML = 1
HPO2700T.GPD = 1
HPO2700T.XML = 1
HPO3100T.GPD = 1
HPO3100T.XML = 1
HPO3200T.GPD = 1
HPO3200T.XML = 1
HPO3300T.GPD = 1
HPO3300T.XML = 1
HPO3X00T.GPD = 1
HPO4100T.GPD = 1
HPO4100T.XML = 1
HPO4105T.GPD = 1
HPO4105T.XML = 1
HPO410XT.GPD = 1
HPO4200T.GPD = 1
HPO4200T.XML = 1
HPO4300T.GPD = 1
HPO4300T.XML = 1
HPO4PG3L.GPD = 1
HPO4PG3L.XML = 1
HPO5500T.GPD = 1
HPO5500T.XML = 1
HPO5600T.GPD = 1
HPO5600T.XML = 1
HPO5H83L.GPD = 1
HPO5H83L.XML = 1
HPO6200T.GPD = 1
HPO6200T.XML = 1
HPO6300T.GPD = 1
HPO6300T.XML = 1
HPO6X00T.GPD = 1
HPO7200T.GPD = 1
HPO7200T.XML = 1
HPO7300T.GPD = 1
HPO7300T.XML = 1
HPO7400T.GPD = 1
HPO7400T.XML = 1
HPO7X00T.GPD = 1
HPOEMUI.DLL = 1
HPOF300T.GPD = 1
HPOF300T.XML = 1
HPOGDS3L.GPD = 1
HPOGDS3L.XML = 1
HPOH3550.EXP = 1
HPOH5500.EXP = 1
HPOJ1600.CFG = 1
HPOJ2600.CFG = 1
HPOJ2700.CFG = 1
HPOJ6200.CFG = 1
HPOJ720.GPD = 1
HPOJ7200.CFG = 1
HPOJ7300.CFG = 1
HPOJ7400.CFG = 1
HPOJ750.GPD = 1
HPOJ750I.GPD = 1
HPOJ920.GPD = 1
HPOJ950.GPD = 1
HPOJG55.GPD = 1
HPOJG55I.GPD = 1
HPOJG85.GPD = 1
HPOJG85I.GPD = 1
HPOJG95.GPD = 1
HPOJK60.GPD = 1
HPOJK60I.GPD = 1
HPOJK80.GPD = 1
HPOJK80I.GPD = 1
HPOJV30.GPD = 1
HPOJV40.GPD = 1
HPOJV40I.GPD = 1
HPOJV45.GPD = 1
HPP0320T.GPD = 1
HPP0320T.XML = 1
HPP0330T.GPD = 1
HPP0330T.XML = 1
HPP0370T.GPD = 1
HPP0370T.XML = 1
HPP0380T.GPD = 1
HPP0380T.XML = 1
HPP03X0T.GPD = 1
HPP0420T.GPD = 1
HPP0420T.XML = 1
HPP0470T.GPD = 1
HPP0470T.XML = 1
HPP1160T.GPD = 1
HPP1160T.XML = 1
HPP2570T.GPD = 1
HPP2570T.XML = 1
HPP7200T.GPD = 1
HPP7200T.XML = 1
HPP7400T.GPD = 1
HPP7400T.XML = 1
HPP7800T.GPD = 1
HPP7800T.XML = 1
HPP78X0T.GPD = 1
HPP7X00T.GPD = 1
HPP8000T.GPD = 1
HPP8000T.XML = 1
HPP8100T.GPD = 1
HPP8100T.XML = 1
HPP8200T.GPD = 1
HPP8200T.XML = 1
HPP8400T.GPD = 1
HPP8400T.XML = 1
HPP8700T.GPD = 1
HPP8700T.XML = 1
HPP8X00T.GPD = 1
HPPH0330.EXP = 1
HPPH0380.EXP = 1
HPPH0420.EXP = 1
HPPH0470.EXP = 1
HPPH1500.EXP = 1
HPPH3100.EXP = 1
HPPH3200.EXP = 1
HPPH3300.EXP = 1
HPPH7800.EXP = 1
HPPH8000.EXP = 1
HPPH8100.EXP = 1
HPPH8200.EXP = 1
HPPH8400.EXP = 1
HPV600AL.DLL = 1
HPV700AL.DLL = 1
HPV800AL.DLL = 1
HPV820AL.DLL = 1
HPV880AL.DLL = 1
HPVDB720.DLL = 1
HPVDB820.DLL = 1
HPVDJ50.INI = 1
HPVDJ610.GPD = 1
HPVDJ612.GPD = 1
HPVDJ615.GPD = 1
HPVDJ660.GPD = 1
HPVDJ66E.GPD = 1
HPVDJ67X.GPD = 1
HPVDJ690.GPD = 1
HPVDJ691.GPD = 1
HPVDJ693.GPD = 1
HPVDJ694.GPD = 1
HPVDJ695.GPD = 1
HPVDJ697.GPD = 1
HPVDJ69X.GPD = 1
HPVDJ6XX.GPD = 1
HPVDJ710.GPD = 1
HPVDJ720.GPD = 1
HPVDJ7XX.GPD = 1
HPVDJ812.GPD = 1
HPVDJ815.GPD = 1
HPVDJ82E.GPD = 1
HPVDJ82I.GPD = 1
HPVDJ82X.GPD = 1
HPVDJ870.GPD = 1
HPVDJ87E.GPD = 1
HPVDJ87I.GPD = 1
HPVDJ87X.GPD = 1
HPVDJ882.GPD = 1
HPVDJ89E.GPD = 1
HPVDJ89I.GPD = 1
HPVDJ89X.GPD = 1
HPVIMG50.DLL = 1
HPVNAM50.GPD = 1
HPVSCP50.DLL = 1
HPVUD50.DLL = 1
HPVUI50.DLL = 1
HPW0460T.GPD = 1
HPW0460T.XML = 1
HPW1000T.GPD = 1
HPW1000T.XML = 1
HPW1200T.GPD = 1
HPW1200T.XML = 1
HPW1B83L.GPD = 1
HPW1B83L.XML = 1
HPW1QI3L.GPD = 1
HPW1QI3L.XML = 1
HPW1RC3L.GPD = 1
HPW1RC3L.XML = 1
HPW2BC6L.GPD = 1
HPW2BC6L.XML = 1
HPW9800T.GPD = 1
HPW9800T.XML = 1
HPWH0460.CFG = 1
HPWH9800.CFG = 1
HPWK550T.GPD = 1
HPWK550T.XML = 1
HPWK850T.GPD = 1
HPWK850T.XML = 1
HPWM50AL.DLL = 1
HPWM5100.GPD = 1
HPWM5112.GPD = 1
HPWM5122.GPD = 1
HPWM5125.GPD = 1
HPWM5225.GPD = 1
HPWM5350.GPD = 1
HPWM535M.GPD = 1
HPWM5CON.INI = 1
HPWM5DB1.DLL = 1
HPWMACRO.GPD = 1
HPZ3ALHN.DLL = 1
HPZ3CLHN.INI = 1
HPZ3LLHN.DLL = 1
HPZ3MLHN.GPD = 1
HPZ3RLHN.DLL = 1
HPZ5CLHN.INI = 1
HPZ5RLHN.DLL = 1
HPZ6CLHN.INI = 1
HPZ6MLHN.GPD = 1
HPZ6RLHN.DLL = 1
HPZEVLHN.DLL = 1
HPZFNLHN.NTF = 1
HPZIDR12.DLL = 1
HPZLALHN.DLL = 1
HPZINW12.DLL = 1
HPZIPM12.DLL = 1
HPZIPR12.DLL = 1
HPZIPT12.DLL = 1
HPZISN12.DLL = 1
HPZLELHN.DLL = 1
HPZLLLHN.DLL = 1
HPZLSLHN.DLL = 1
HPZPPLHN.DLL = 1
HPZPRLHN.DLL = 1
HPZSCLHN.DTD = 1
HPZSCLHN.INI = 1
HPZSMLHN.GPD = 1
HPZSRLHN.DLL = 1
HPZSSLHN.DLL = 1
HPZSTLHN.DLL = 1
HPZUILHN.DLL = 1
[PrinterPackageInstallation.amd64]
PackageAware=TRUE
CoreDriverDependencies={D20EA372-DD35-4950-9ED8-A6335AFE79F0},{D20EA372-DD35-4950-9ED8-A6335AFE79F1},{D20EA372-DD35-4950-9ED8-A6335AFE79F2},{D20EA372-DD35-4950-9ED8-A6335AFE79F3}
[Strings]
;Localizable
Disk1="Windows Installation Disc"
[SourceDisksNames.x86]
1 = %Disk1%,,,"I386"
[SourceDisksNames.amd64]
1 = %Disk1%,,,"Amd64"
[SourceDisksNames.ia64]
1 = %Disk1%,,,"Ia64"

Solaris 10 SAN Boot issue

During Solaris 10 Installation on a SAN Based disk, SUN Fire V10 was not rebooting after the first CD installation. It does memory dump...

I really don't like san boot for operating system. You have too many points of failure for the basic operation.
Anyway, during installation, ensure that you access the disk using just one path (using zoning for example). After you enable and configure MPxIO, you could enable other paths.

SAN boot disk in a cluster node?

As far as I remember, SC requires local boot disk.
Is it possible to use the SAN boot disk? Can this configuration work being just not supported by SUN or there is some technical limitation ?
I am thinking of low price configuration with two diskless X2100s + HBAs and SAN storage. Possible?
thanks
-- leon

As far as I remember, SC requires local boot disk.
Is it possible to use the SAN boot disk? Can this
configuration work being just not supported by SUN or
there is some technical limitation ?The rule for boot disks gos like this:
Any local storage device, supported by the base platform as a boot device, can be used as a boot device for the server in the cluster as well. A shared storage device cannot be used as a boot device for a server in a cluster. It is recommended to mirror the root disk. Multipathed boot is supported with Sun Cluster when the drivers associated with SAN 4.3 (or later) are used in conjunction with an appropriate storage device (i.e. the local disks on a SF v880 or a SAN connected fiber storage device).
So your boot disk can be in a SAN as long the base platform supports it as a boot disk and it is not configured as a shared lun in the SAN (i.e. visible to other nodes than the one that uses it as boot disk).
I am thinking of low price configuration with two
diskless X2100s + HBAs and SAN storage. Possible?You need to check the support matrix of the storage device you plan to use, if it is supported as a boot device for the X2100 + HBA. If the answer is yes, you just must make sure that this lun is only visible to that X2100.
Greets
Thorsten

210-4125 will not boot when windows 7 x64 is installed

i have posted this problem a while ago "210-4125 will not boot when windows 7 x64 is installed"
hoping that some one new might have had the same problem
HP.......................................HP MINI PC 210-4125
model ................................210-4125
Bios ...................................F08
ser no................................ [edited Serial Number by Moderator]
product no.........................A8V56EA#ABU
Ram ..................................4.0 GB
system board ID............... 338d
processor .........................Atom(TM) CPU N2800 1.86GHz
Product configuration ID..0797200000204600000300100
acording to INTEL the cpu is X64 bit, but the bios will not let a X64 boot up only a x32 bit ?
and i get a message on black screen "you are trying to load an opperating system not compatable" or some thing like that
it would seem that the bios is the problem and not the CPU ? the 08 bios update only covers x32 bit and not x64
if any one out there is running x64 bit windows 7 on the 210-400 range of netbook can you tel me
1. model no
2.CPU
3.Ram installed
4 bios No
thank you
JB

thank you George
i will bear that in mind next time
i see that you work for HP ? do you have any suggestion's for my problem ?
as i mentioned before the notebook works faultlessly when X64 windows 7 is installed via the OEM disk in the external DVD drive , but if i disconnect the DVD drive it will not boot, but gets stuck in boot loop , then if i connect the drive with any windows installation disc loaded in it , it loads perfect and works perfect even if i disconnect when loaded , but i can not keep the drive connected ?
i have tried to use a USB flash drive to install X64 windows 7 but it comes back that the present CPU is not compatible ??
when it clearly states on Intel web site that it is and it works perfect when loaded ?? even the Windows update manager confirms that it will run all X64 windows OS
i understand the the bios "InsydeH20" is a very difficult bios to work with, and that Insyde have blocked the "hidden menu" via software ? i have exhausted all the software functions to open the complete bios that i can find at the moment , i think it is locked out from out side the bios and not from inside.?
any pointers in the right direction would be very helpful ,
many thanks
John

UCS-Blade do not boot from disk local

Hi everyone,
I have a UCS-Blade and UCSM with version 2.1 (1e), I create the boot policy to boot from the disk local and raid 1.
The trouble is that when the Blade server boot show me the screen in SHELL, in other words the server startup on mode UEFI, I need enter the word "EXIT" to enter the "ESXi", the version of the ESXi is 5.1.0.
attach the image
everyone have any suggestions
thk for help me!!!

Josue,
I would like to know what server model you are using and if the ESXi version you installed is the customized Cisco ESXi version?
I bet this is a new installation... It looks like the server does not see an image to boot from, even though it looks like the boot policy actually points to the local disks, but I have also seen how weird things happen when the non-Customized ESXi .iso image is used.
Try to use the customized version found here ;
https://my.vmware.com/web/vmware/details?downloadGroup=CISCO-ESXI-5.1.0-GA-25SEP2012&productId=285
And check compatibility with one of my favorite tools:
http://www.cisco.com/web/techdoc/ucs/interoperability/matrix/matrix.html
I hope this helps you, if it did, rate it!
-Kenny
Cisco Support Community is also present in Spanish:
https://supportforums.cisco.com/community/spanish/data_center

San Boot Win2K8 R2 SP1 x64 on UCS blades B with M81KR installation issue

Similar Messages

Maybe you are looking for