DMM and switch systems

I am trying to put together a system that is capable of measuring 48 current shunts that I would like to maintain isolation from the SCXI chassis ground.  I am considering using a PCI 4065 and an SCXI-1127 or 1128 switch module, 2 of one of them.  What I am unsure about is which type of switch I should use, the solid state or relay?  Also I am not sure how the termination of wires should be made.  Each shunt will have two wires coming from it.  Should these two wires from each shunt go into the switch module and are then all terminated at the DMM?  Is there a cleaner way to do this or is my assumption incorrect on the wiring strategy?
Is there a better solution?
Will the DMM provide results similar to a handheld DMM?  i.e. averaging the voltage level read. 
thanks in advance.   

Hi,
FET switches such as the SCXI-1128 will have a faster scan
rate and lower power requirements than mechanical relay switches such as the
SCXI-1127.  The advantage of using a mechanical
relay is the amount of current it can switch and carry.  You should base your decision on the specifications
of your input signal and how fast you will eventually need to scan through the
channels. 
The two wires from each shunt will connect to the terminal block (which will have inputs corresponding to the channels of your switch module) and the DMM will connect to the output of the switch
module (through the terminal block).  Scanning through the channels
will connect one channel to your output (DMM) at a time.  The Developer Zone articles: How to connect signals to the SCXI-1127 and How to connect signals to the SCXI-1128 describe the connections in detail.  The DMM will then average the voltage measurements
to provide a more accurate reading.
Best Regards
Hani R.
Applications Engineer
National Instruments

Similar Messages

  • IVI questions with DMM and SWitch

    I am trying to simulate an NI-4060 DMM and numerous SCXI-1129 cards using the IVI drivers in CVI.
    Of preference I want to setup the simulation in MAX rather than programmatically in my application. I have numerous questions:
    Is there a document that shows you how to setup MAX to simulate an IVI instrument??? Everything that I have read so far talks about the architecture, how wonderful IVI is what you can do etc, but NOT EXACTLY HOW you set-up MAX - one document briefly touched on this but with no detail whatsoever. There seems to be a lot of assumed knowledge in all the docs.
    If I try and configure in MAX I can get the DMM working, but the exact same steps give an error for the switch cards in my application. An
    y ideas?
    How do I use Soft-panels from my application?
    If I am programmatically using an InitWithOptions which seems to be the only way to get the Switch cards to simulate what is the expected syntax or options for the "DriverSetup" string????
    I am using NI-DAQ 6.9.0f7 and IVI 1.61 with CVI 5.5 on NT 4.0

    Ricardo,
    There is a document on our web site on how to configure your IVI system in MAX and also how to simulate your hardware in LV and CVI using IVI drivers:
    ni.com>>Resource Library>>Instrument Connectivity>>Instrument Driver IVI
    or
    http://zone.ni.com/devzone/devzone.nsf/webcategori​es/5FB594A1C20D93E3862569FD0071D18A?opendocument
    This should point you in the right direction. I will continue to gather information and post what I find!
    Best Regards,
    Chris D
    Applications Engineer
    National Instruments

  • I have an iphone6. I am unsure whether to go from 8.1.3 operating system and switch to  ICloud Drive or not?  Has anyone done this?  Is it awesome?  I need to be able to access my resume from phone. I think this will help me achieve this.am i right?

    I have an iphone6. I am unsure whether to go from 8.1.3 operating system and switch to  ICloud Drive or not?  Has anyone done this?  Is it awesome?  I need to be able to access my resume from phone. I think this will help me achieve this?  Am i right?  Is there any body out there right now that could help me?  I'm thinking about going from 8.1.3 to I guess yosemite?  Or is that for Mac computers?  I don't understand the language entirely on the help page.   Anyone's straight forward and easy stepped advice would be much appreciated.  I'm so frustrated and I need a job so badly!  Drowning in debt.  Any help appreciated!
    Thanks,
    A

    You're a Windows user, correct? If so, read here:
    http://support.apple.com/kb/DL1455

  • Configuring and Troubleshooting Virtual Switching System (VSS)

    With Anand Ganesan
    Welcome to the Cisco Support Community Ask the Expert conversation. This is an opportunity to learn and ask questions about how to monitor, configure, and troubleshoot the Virtual Switching System (VSS) in Cisco Catalyst 6500 Series Switches with expert Anand Ganesan.
    VSS is network system virtualization technology that pools multiple Cisco Catalyst 6500 Series Switches into one virtual switch, increasing operational efficiency, boosting nonstop communications, and scaling system bandwidth capacity to 1.4 Tbps. At the initial phase, a VSS will allow two physical Cisco Catalyst 6500 Series Switches to operate as a single logical virtual switch called a virtual switching system 1440 (VSS1440). 
    For more information, visit:  www.cisco.com/en/US/prod/collateral/switches/ps5718/ps9336/prod_qas0900aecd806ed74b.html
    The VSS simplifies network configuration and operation by reducing the number of Layer 3 routing neighbors and by providing a loop-free Layer 2 topology.
    Anand Ganesan is a customer support engineer in the High-Touch Technical Service team at Cisco specializing in switching protocols. He has been supporting major service providers and enterprise customers in switching and all other switching technologies for more than two years with Cisco. He has a total of eight years of experience in the IT industry. He holds a bachelor of engineering degree from Bharathiyar University, Coimbatore.
    Remember to use the rating system to let Anand know if you have received an adequate response. 
    Because of the volume expected during this event, Anand might not be able to answer every question. Remember that you can continue the conversation in the Network Infrastructure subcommunity, LAN Switching & Routing shortly after the event. This event lasts through September 6, 2013. Visit this forum often to view responses to your questions and the questions of other Cisco Support Community members.

    Okay..they are two different /30 networks.
    my BFD interfaces are GigabitEthernet1/3/48 and GigabitEthernet2/3/48 and they work fine.
    interface GigabitEthernet1/3/48
    description Switch 1 BFD Interface
    no switchport
    ip address 10.48.0.17 255.255.255.252
    bfd interval 100 min_rx 100 multiplier 3
    end
    interface GigabitEthernet2/3/48
    description Switch 2 BFD Interface
    no switchport
    ip address 10.48.0.21 255.255.255.252
    bfd interval 100 min_rx 100 multiplier 3
    end
    switch virtual domain 1
    switch mode virtual
    switch 1 priority 110
    dual-active pair interface GigabitEthernet1/3/48 interface GigabitEthernet2/3/48 bfd
    show switch virtual dual-active bfd
    Bfd dual-active detection enabled: Yes
    Bfd dual-active interface pairs configured:
    interface-1 Gi1/3/48 interface-2 Gi2/3/48
    router eigrp 1
    network 10.0.0.0
    network 10.1.201.0 0.0.0.255
    network 10.48.0.12 0.0.0.3
    network 10.48.177.0 0.0.0.255
    network 97.0.0.0
    network 99.0.0.0
    network 100.0.0.0
    network 100.7.7.0 0.0.0.255
    network 192.34.145.0
    network 192.168.15.0
    show ip ei in
    EIGRP-IPv4 Interfaces for AS(1)
                           Xmit Queue   Mean   Pacing Time   Multicast   Pending
    Interface       Peers Un/Reliable SRTT   Un/Reliable   Flow Timer   Routes
    Gi1/2/40           1       0/0         1       0/1           50           0
    Gi1/2/41           0       0/0         0       0/1           0           0
    Vl1               1       0/0         1       0/1           50           0
    Vl7               0       0/0         0       0/1           0           0
    Vl13               0       0/0         0       0/1           0           0
    Vl15               0       0/0         0       0/1           0           0
    Vl21               0       0/0         0       0/1           0           0
    Vl25               0       0/0         0       0/1            0           0
    Vl26               0       0/0         0       0/1           0           0
    Vl134             0       0/0         0       0/1           0           0
    Vl135             0       0/0         0       0/1           0           0
    Vl140             0       0/0         0       0/1           0           0
    Vl300             0       0/0         0       0/1           0           0
    Vl400             0       0/0         0       0/1           0           0
    Vl199             0       0/0         0       0/1           0           0
    Vl6               0       0/0         0       0/1           0           0
    Vl20               0       0/0         0       0/1           0           0
    Vl24               0        0/0         0       0/1           0           0
    Vl30               0       0/0         0       0/1           0           0
    Vl31               0       0/0         0       0/1           0           0
    Vl37               0       0/0         0       0/1           0           0
    Vl2               0       0/0         0       0/1           0           0
    Gi1/3/48           0       0/0         0       0/1           0           0
    Gi2/3/48           0       0/0         0       0/1           0           0
    Vl17               0       0/0         0       0/1           0           0
    Gi2/6/40           0       0/0         0       0/1           0           0
    Gi2/6/41           0       0/0         0       0/1           0           0
    Gi2/1/45           1        0/0         1       0/1           50           0
    Gi1/1/33           1       0/0         1       0/1           50           0
    My questions revolve around the same point.
    Are there any significance in running eigrp or any other routing protocol over this BFD link?
    Is the Dual active scenario detected by BFD or BFD notifies a routing protocol like eigrp and in turn dual active is detected?
    Should I suppress the eigrp HELLOs on these interfaces to get rid of the log message?
    Regards
    Vinayak

  • DMM and Show and Share: System Requirement

    Hi
    I want to install DMM and SnS for a test environement (vmware), but i can't find the system requirements for both servers, i know that is a Hardware only Server supported and a preinstalled plateforme.

    Hi Youssef;
    Maybe this will help;
    There is a DMS sub-forum here
    https://supportforums.cisco.com/community/netpro/collaboration-voice-video/digital-media-system?view=discussions
    Cisco Digital Media Manager 5.4 Virtual Machine
    http://www.cisco.com/en/US/prod/collateral/video/ps9339/ps6681/data_sheet_C78-722975.html
    http://www.cisco.com/en/US/docs/video/digital_media_systems/5_x/5_4/dmm/vm/dmm54x_vm.html
    Cisco Show and Share
    System Requirements
    Cisco  Show and Share is available for purchase on two different supporting  server appliances. All of the required operating system software,  required configuration, and Cisco Show and Share applications are  shipped to customers preinstalled on the server appliance they choose.  Cisco Show and Share is not available for purchase as a standalone  application.
    http://www.cisco.com/en/US/prod/collateral/video/ps9339/ps6681/data_sheet_c78-565776_ps6682_Products_Data_Sheet.html
    Cheers!
    Rob
    "When it comes to luck you make your own  " 
    - Springsteen

  • Follow-up: Starting, Launching and Switching ...

    Follow-up: Starting, Launching and Switching ... Messing around with the Windows UI - not a feature problem, but a provisioning problem! Now start listening and please fix it this time! 
    (Is it still program managers or people in power designing the UI for Windows? It certainly does not look like domain specialist or software engineering designing the solution here - it's just too weak for that to look like a professional solution?
    Please let educated people do their work ...)
    Problem:
    - Task Bar = (is and still is originally) Start. So keep promoting task bar and kill the new Start. Task Bar is Start.
    - Virtual Desktop lacks virtual Start (= virtual Task Bar) (Virtual Desktop only have virtual launch from the virtual documents (the virtual desktop) ... you need to add virtual start beyond virtual launch.
    - Starting universal Windows apps including touch goes to the virtual task bar (add virtualization above, i.e. context changes - for touch meaning i.e. increasing the task bar (Start) areas height)
    Cause:
    Steven Sinofsky:
    @Computermensch writes “The problem with this "analysis" (show me the data) is that you're only managing current activities surrounding the taskbar. So with respect "to evolving the taskbar" you're only developing it within its
    current operational framework while developing or evolution of it really should refer to developing the taskbars concept.” 
    0) A history reminder - where is Windows 10 now starting program: Back where Windows 7 left off.
    Well, guess I do not have to remind about what happened to Windows 8. Now we're back at it. Welcome back to testing ...
    I did some of them, testing Windows client for Windows Vista, Windows 7, Windows 8 and now Windows 10.
    Let's go back in time to 2008 - Engineneering Windows 7: 
    Follow-up: Starting, Launching, and Switching
    http://blogs.msdn.com/b/e7/archive/2008/09/29/follow-up-starting-launching-and-switching.aspx
    Steven Sinofsky:
    @Computermensch writes “The problem with this "analysis" (show me the data) is that you're only managing current activities surrounding the taskbar. So with respect "to evolving the taskbar" you're only developing it within its
    current operational framework while developing or evolution of it really should refer to developing the taskbars concept.” 
    Then let's go forward in time - to Windows 8 coming up with a new start and launch context namely the Start Screen - and now kind of back in time again to Windows 7 and the desktop using Windows 10. So now we're also back to the Task Bar!!!! Hence we're
    back to developing and evolving the way of Starting programs.
    Microsoft just have a serious problem working the provisioning in it system, i.e. what concepts you supply (provision) to the user. For instance just compare an open instance of Windows Explorer with MacOS Finder. It's the same features - but the provisioning
    is just much better in Finder. The concepts are just an important mess in Windows - and needs serious clean up.
    No new features! Evolvle the pinning (task bar and make it work with the virtual desktop - including touch (just add some height man ...).
    And fix the freaking provisioning of concepts in the All Apps list. For instance take a look at the naming in Linux for some standard folders - instead of the bloating 3rd party names.
    1) Provisioning: Now back to Windows 10 and starting programs
    It's the task bar that needs development (Windows 8 kind-of "Start Menu" in Windows 7)  Take a look at my comment above again for engineering Windows 7 about the taskbar on evolution - now in context with Virtual Desktops:
           - May add some height to the task bar - and you can have kind-of tilesized stuff there.
           - Have the taskbar configuration of pins switch (be variable) with the virtual desktop. May add an ekstra feature to pin program across all virtual desktops.
           - Do not have 2 different places for pinning programs (really bad provisioning ...). Lets see some nice categories instead when pressing the start button. It really confusing pressing the start menu button - and
    then you see a place like the task bar to pin programs. Typical Microsoft end up scenario, the more, the merrier ...
    Please cut it down to having a pinning feature working variably in context (the task bar) with virtual desktops.
    2) Finally the All Apps list pressing the start menu button: using navigation (categories, tags or filters!!!!!) to look up and finding programs not in use on a daily or weekly basis - now in context with the virtual desktop
    The All Apps list that needs a nice feature to support categorization, really better provisioning in the UI of user or standard concepts (now come on, man - fix the mess. Just take a look at the complexity in that list ...). You could add a feature
    to filter the All Apps list in context with the concepts for the virtual desktop.
    At least provide the application infrastructure for categorization in the Start Menu. So you could process it as a third party. See what happens. Add app store later then. Whatever. Make categorization happen. No more bloat navigating for programs.
    Add a template feature to the categorization. Provide 2-3 templates with Windows and let people tag there programs. Let them extend the templates ... the concepts when doing their own user concepts.
    With a template feature a user just have to fill in the blanks i.e. tag his/her programs - and the menus will parse equally. Hey, the template feature could even parse into virtual desktops. I.e. using a dev variant of a template.
    It's going to be 2015. And compositional software design have been around for some time. Including factories for configuring software variability. Some come on now. Let's work.
    4) Conclusion
    360 degrees now on virtual desktops, task bar, all apps and workflow please! Make it happen.
    The problem with Windows 8 was not bad features - but bad provisioning including empty programs like the new wau media players ... underdeveloped features (no really good quantity of content demonstrating value = bad provisioning) ... completely lack of
    demonstrating the value of the new UI. Like if Sharepoint or any other CMS was demonstrated completely blank with no sites and empty features, no templates. Just nothing.
    Please do not miss the oppertunity to demonstrate the value of an evolved UI this time.
    Please complete the provisioning. Your greatest problem is releasing undone things - may be the intension is there (recall DB schemas). However the "DB extension" is empty on release? Which consumers just buy the DB schema :o). Add some "movies"
    (content) please ... add frameworks for content and provisioning ... use templates. If you do not understand this ... go away program manager ;o) Let a good software engineering read it.
    Now let's fully develop the virtual features in the desktop in Windows 10. And have them provisioned - so people can see how to use them. That unfortunately never happened during engineering in Windows 8.

    3 different ways and displays for pinning a program for Start!
    Please consider merging Start (on the Start), Start Screen and the task bar - with pins extending the Task Bar and using the Metro UI icons overall including on the desktop. It would be a nice move on the look and feel - while the task bar would be
    the same. Add virtualization for pins as well on the task bar. Make shortscuts and docs on the virtual desktop actual as well - binding dynamically to a virtual desktop - instead of formal and static.
    Just observed the Start Screen can be turned back on using properties on the Task Bar.
    Many ambigious concepts now for Starting programs instead of just using a Consolidated Start concept for Start Screen, Start on the Start Menu and Task bar.

  • "Bookmarks and history system will not be functional" with corrupt files found by Avast and websites loading slow ONLY in Firefox

    Firefox is the only browser that lets me connect with my microphone. I need to use this feature for an online class. Earlier this evening, the message prompting me to allow or deny the class website permission to use the microphone stopped appearing, and without it the recording won't pick up any sound and I can't record anything.
    I tried exiting and restarting Firefox. I had some extensions in use at the time, in particular Session Manager. The allow/deny message still wouldn't appear, so I restarted my computer.
    Now when I open Firefox I see the "The bookmarks and history system will not be functional" error message. In addition, the browser loads websites extremely slowly; it takes several minutes to load each page or for me to be able to click on anything (the URL bar, the menus, etc) My other browsers (Internet Explorer and Chrome) are running normally and load websites at a normal speed. I tried downloading the latest version of Firefox but it didn't fix anything. I also tried restarting the computer again but that didn't help either.
    I ran my Avast software system check and it turned up that the following files under "C:\Users\(me)\AppData\Roaming\Mozilla\Firefox\Profiles\Irozixj7.default" are "corrupted and unreadable":
    -cookies.sqlite-shm
    -cookies.sqlite-wal
    -localstore.rdf
    -places.sqlite-shm
    There was one more problem on the scan, but it probably isn't relevant: for the file "C:\ProgramData\Microsoft\Windows Defender\Definition Updates\{9A2C6FA7-E04E-4819-B86A-8363A9D1E42A}\mpengine.dll" it says "The system cannot find the path specified." When I attempted to follow the path indicated, one of the folders (I can't remember which) said something along the lines of "You can't access this folder, do you want to permanently allow access to this folder?" I said yes and was able to access the folder.
    I have tried to add the Places Maintenance extension but the speed is too sluggish to download anything. Trying to access any of the menus results in the browser freezing for several minutes then unfreezing but with the menu still unopened. Therefore none of the solutions found here (https://support.mozilla.org/en-US/kb/fix-bookmarks-and-history-will-not-be-functional?esab=a&as=aaq) seem to work.
    My questions are as follows:
    -Is it possible to figure out what caused the problem in the first place?
    -Is there a way for me to fix it without losing my bookmarks and history?
    -How can I avoid this happening again in the future?

    First, I recommend backing up your Firefox settings in case something goes wrong. See [[Backing up your information]]. You can copy your entire Firefox profile folder somewhere outside of the Mozilla folder. To quickly access this folder:
    Help > Troubleshooting Information > "Show Folder" button
    Next, keep this folder open, exit Firefox, and try moving the "corrupted and unreadable" files to a different folder. With the exception of localstore.rdf, which stores window positions, toolbar customizations, and other nonessential data, the other files appear to be session-specific files that hopefully are not critical. If you restart Firefox, does it behave more normally?
    If not, try creating a fresh Firefox profile. It will have the Flash plugin, which is the control sites usually use to connects your camera and/or microphone, and other plugins, but otherwise will be a new setup. This article has the steps for starting up in the Profile Manager: [[Use the Profile Manager to create and remove Firefox profiles]].
    If sites work normally in the new profile, you can import your bookmarks from your old profile, as well as copying over other files that don't seem to be causing the problem. Some trial and error might be required to determine that. This article has some tips: [[Recovering important data from an old profile]].
    If the new profile is no better, you can exit Firefox and use the Profile Manager to switch back to your original profile.
    Any improvement?

  • How do I just remove the current update to 3.6.12 and go back to an earlier version as I can not take the continual freeze ups ever few mins.? If this continues I will remove Firefox totally and switch to another browser I can not take this anymore.

    I can NOT take the continual freeze ups of my entire browser even worse when updating a page let alone just opening email. I closed the browser and have had to use even just microsoft or Google since this Firefox has gotten so horrible...
    I clear my history and my cache so many times a day I can not keep track anymore and that is insane to have to do it as many times as I am even worse that it does not help in the least!
    I have used Firefox for years now but if I have to remove it and switch to a different one by the days end I will and I will post in Facebook to all my friends who I had switch to Firefox what and why though some have already just switched to other browsers.

    First, that cannot be an iBook G4 as that machine cannot run Snow Leopard let alone Mountain Lion.  To run Snow Leopard it has to be an Intel processor, not a G4.  What does it show as the Model Identifier in About This Mac, More Info, System Report, Hardware, Model Identifier?
    Second, if you have erased the hard drive there should not be remnants of any prior content.  Even though Disk Warrior is saying nothing is wrong with the hard drive, it sounds as though there are problems.  You may want to consider simply replacing the hard drive so there are no questions about faults.  A good source is OWC, http://www.macsales.com where they also have on-line videos showing how to do the replacement.
    Third, you could also try again to restart using the Snow Leopard DVD/CD and use Disk Utility on that install disk to erase again, and do it a couple times, then try to install.  If it continues to refuse, then it sounds as though there is a fault with the hard drive.

  • Windows 7 hangs and switches off network access

    We are running a Windows 7 Ultimate 32-bit operating system as our server.
    About on 30 minute intervals the computer hangs and switches off network access.
    If the computer is in this state and you try and access it from another computer nothing happens.
    While in this state you can see the desktop indicating that it's not in sleep mode.
    The problem is rectified by click the mouse on the computer.
    It has not gone into a sleep mode as everything on the power options is set to never.
    Please help?
    Regards,
    Andries Malherbe
    Vizier Systems

    About on 30 minute intervals the computer hangs and switches off network access.
    If the computer is in this state and you try and access it from another computer nothing happens.
    Could you plaese share more information about "switches off network access" with us? I don't quite understand this situation
    Please also check the event viewer to collect related information about this issue when you re-use the Windows 7.
    Meanwhile, Please update the driver for network adapter or reinstall for a test.
    Regards
    Yolanda
    TechNet Community Support

  • I have CS5 for Windows, can I upgrade to Creative Cloud and switch to Mac

    I originally purchased my Adobe CS software for Windows - I recently have switched to Mac . . . so I am forced to upgrade my CS software. Can I use the upgrade discount of $29.99 a month and switch platforms?

    If you have an Education version you will not receive a discount, since Education versions are already discounted
    Once you have the Cloud, the License allows 2 activations http://www.adobe.com/legal/licenses-terms.html
    -Install on a 2nd computer http://forums.adobe.com/thread/1452292?tstart=0
    -Windows or Mac does not matter... 2 on the same operating system, or 1 on each

  • Some apps crash out when I close their window and switch to the Finder

    It has been doing this since day one.  I'm a college student and bought a laptop to replace another really old mac system, to use as my main system.  The issue I'm noting is that on some apps, if I close out their window and switch to the Finder, by either click on the desktop, or by command tabbing.  The application seems to crash.  I say 'seems' becuase I'm not certain it's crashing.  It does this in Text Edit along with pages.  I'm trying to find out if it's supposed to this or if it's supposed to be a new feature.  There is never a crash log made that I know of, nor a dialog box stating the app crashed.  However, it does this by itself, without my quiting out the app by command q nor file>quit.
    This has been relatively minor and hasn't caused any large problems.  To me it's an annoyance and inconviencning.  Which is why I waited until summer break at school to investigate.  Other classmates with older mac book pros but the same OS version have not had this problem.  Wondering if I have a botched isntall of OS X from the factory.  I've already had it in for service for the motherboard.  The cooling system was not correctly attached to teh CPU at the factory and cooked itself.
    I'm tempted to do a reload of the OS from the diagnostics partition the system came with.  I haven't transferred much of anything from the previous system that this one is replacing.  Now would be an ideal time to do anything of this nature rather than say in the middle of next semester.
    The issue occurs in TextEdit, Pages, and that's it so far.  I really have almost nothing loaded on the system.  I dual boot into another OS for using Maya and other various software apps.  The issue does not occur with Safari nor FireFox nor Preview.  It seems confined to Pages and TextEdit.  It can be extremely annoying however when typing an essay in Pages.  Perhaps it's a feature that was introduced that I can turn off?  Going from a 5 year old Mac Mini to a MBP, LOTS has changed.

    Sorry for taking so long to reply.  It's still doing it.  I'm kind of wondering if something like a preferences file is corrupted, however, I have to do a total system reload to begin with to eliminate any potential corrupt data on the windows 7 install.
    Back story.  When I first got this thing it was running super ridiculously hot.  It's the first laptop I've ever owned however so I had nothign to use for reference.  After about two months of it getting brutally hot, it did a BSOD in the windows 7 install I did via bootcamp.  It never turned back on.  Took it to the Apple store in Novi MI and they stated it somehow ran so brutally hot the CPU did a solder reflow and the whole motherboard shorted out.  Even worse though, I had gotten this hot before rendering stuff in Maya and Vue.  I had done burn in tests when I first received the system, it had passed, or so I thought.  They couldn't even get the system to turn on at the Apple Store.
    The tech at the apple store told me that one of the heat sink pins on the CPU just plan broke off and another wasn't attached correctly.  Essentially the system kept overheating as I was consisently completely maxxing out the system doing CGI test renders for my junior animated short film.  The cooling system was never fully connected at the factory according to the Apple Tech.  I don't know how literate everyone reading this is on computer engineering but, when you overheat an IC, whether it's an ASIC or CPU, they dont' immediately crash, they corrupt data.  To further complicate the mess and increase teh chances of data corruption, with the 4th gen Intel i series CPUs (which the MBP uses), they moved the northbridge directly into the CPU die.  So if teh CPU is overheating, the chances of data corruption inadvertantly go up even higher.  I'm suspecting that happened in the first few days of owning the system but that it was minor at that point.  It can take months for the effects of corrupted data to propagate out and be visible to the user.
    I would assume that they did a diagnostic test on the SSD when it was in for service, to ensure the SSD didn't overheat.  The tech did state that if the drive failed the diagnostics, they would have ot replace the drive and henceforth all my data would be gone.  Not really a way around it.
    Currently under the windows 7 install with Maya and Vue, later iterations of the scene file, from Maya, for my animated short film, have a reproduceable glitch involving a gamma shift and camera selection.  Part of the scene files seem to be corrupt and were saved that way.
    Reloading the OS from the recovery partition did not fix the original problem I've been having that I initially asked for help with.  I'm considering wiping out the recovery partition in addition to reinstalling windows 7 and OS X again, it would be the only way to completely eliminate the possibility of any corrupted data floating around on either partition.  I don't have a way of knowing if corrupted data was written to the SSD beyond the corrupted Maya scene files.  The only way I can be sure that it's 'contained' or eliminated, is if I completely wipe the drive and start from scratch.  Now would be a great time rather than in the middle of working on my senior thesis for my BFA degree.
    I'm wondering if you could point me to documentation showing how to wipe out all the partitions, including the recovery one.  My understanding is that there is a way to do a 'net boot' or 'net recovery' over a broadband connection using Apples servers.  The idea of doing a Live boot from a Ubuntu distro to run fsck is appealing but it would be pointless.  The file system shoul be fine, it's the data the file system points to that I suspect is corrupted at somepoint.  Unless you recommend otherwise and or formatting.
    The overheating also corrupted my journal but there is no way to recover it, I overwrote the earlier file(it looks like uncompiled C++ and jibberished text) when I saved it after completing an entry.  This was many months ago.  Though the idea of attempting a restore with Ubuntu Remix or other recovery Linux distros is appealing I'm doubtful I'd get far, though it's an SSD not a traditional harddrive and they don't work the same.
    Back to the main point though, I suspect the overheating corrupted a prefs file which is causing the glitch I'm seeing, and reloading the OS did not fix it.

  • After several years of use very satisfied with Firefox, recently loaded version (4.0.1) severely slows my browsing, and even my system, especially when there are pictures or videos. I said that this was not the case before and my system is Windows XP SP3.

    After several years of use very satisfied with Firefox, recently loaded version (4.0.1) severely slows my browsing, and even my system, especially when there are pictures or videos. I said that this was not the case before and my system is Windows XP SP3.

    I have had a similar problem with my system. I just recently (within a week of this post) built a brand new desktop. I installed Windows 7 64-bit Home and had a clean install, no problems. Using IE downloaded an anti-virus program, and then, because it was the latest version, downloaded and installed Firefox 4.0. As I began to search the internet for other programs to install after about maybe 10-15 minutes my computer crashes. Blank screen (yet monitor was still receiving a signal from computer) and completely frozen (couldn't even change the caps and num lock on keyboard). I thought I perhaps forgot to reboot after an update so I did a manual reboot and it started up fine.
    When ever I got on the internet (still using firefox) it would crash after anywhere between 5-15 minutes. Since I've had good experience with FF in the past I thought it must be either the drivers or a hardware problem. So in-between crashes I updated all the drivers. Still had the same problem. Took the computer to a friend who knows more about computers than I do, made sure all the drivers were updated, same problem. We thought that it might be a hardware problem (bad video card, chipset, overheating issues, etc.), but after my friend played around with my computer for a day he found that when he didn't start FF at all it worked fine, even after watching a movie, or going through a playlist on Youtube.
    At the time of this posting I'm going to try to uninstall FF 4.0 and download and install FF 3.6.16 which is currently on my laptop and works like a dream. Hopefully that will do the trick, because I love using FF and would hate to have to switch to another browser. Hopefully Mozilla will work out the kinks with FF 4 so I can continue to use it.
    I apologize for the lengthy post. Any feedback would be appreciated, but is not necessary. I will try and post back after I try FF 3.16.6.

  • V2P Virtual Machine to physical Server migration on IBM x3650 M4 and switch from BIOS to UEFI Boot environment

    Hi there,
    just wanted to share my experience with a manual P2V Migration. The VM became to ressource hungry and it was decided to move it off an ESX 5 Cluster to a dedicated physical Machine.
    V2P Virtual Machine to physical Server IBM x3650 M4 and switch from BIOS to UEFI Boot environment
    Task:
    V2P Migrate a VMware virtual machine to a IBM x3650 M4 with a ServeRAID 5110e RAID Controller or any other LSI RAID Controller without 3rd Party tools.
    This should also work with other RAID Controllers or Servers but be sure to pick the right drivers then.
    Extra Task:
    The VM's boot environment/virtual BIOS is BIOS, not UEFI (as per default VMware Setting). The physical Server is running in UEFI mode.
    The Challenge:
    After restore the Server won't boot or get into a BSOD (7B), because the RAID drivers are missing.
    After restore the VM won't boot because the boot environment has changed from BIOS to UEFI
    Preparations:
    An existing physical Server of the same type and with the same RAID controller and same OS would be nice for troubleshooting and checking the registry.
    An existing DHCP server will make networking things easier.
    Connect the new physical server x3650 M4 to power and network
        create a virtual drive that has at least the size of the existing VM plus the size of the full backup (.vhd). Should be about twice the size of the original vmdk.
    Get a USB Flash stick (I used a 8GB modell so no problem with larger sticks)
    Download and extract LSI MegaRAID Driver on that USB media (I used 6.705.05.00-MR_Windows_Driver directly from LSI website)
    Download and extract INTEL Network Adapter Driver on that USB media (I used 12.11.97.0 of e1r62x64.inf from 19.5 driver release from 2014.09.26 directly from LSI website)
    Step by Step:
    if you have an other physical Server of the same type and same Controller and same OS:
    1.    open regedit and export everything related to SCSIAdapter and megasas2 to .reg files or skip this step and use my files below
        some of this (sub)keys may not be accesible - you will then first take ownership and/or modify permissions to read them
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4D36E97B-E325-11CE-BFC1-08002BE10318}
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\PCI\VEN_1000&DEV_005B&SUBSYS_04121014&REV_05
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\megasas2
        this one is more complicated:
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase (only relevant are those devices where the service name is megasas2 - export the whole subkey and get the filtering done with tools like notepad++)
        Make a copy of the following files/folders:
        c:\programdata\LSI\
        c:\windows\inf\megasas2.INF
        c:\windows\inf\megasas2.PNF
        c:\windows\system32\drivers\megasas2.SYS
    on the existing VM:
    1.    create a full backup (image) with the built-in Windows Backup Utility and save it in an accessible network location (you will need this one, if anything goes wrong or you want to come back to this point.
        Alternatively you could create a VMware snapshot.
    2.    import the .reg files you created earlier or import my files below.
        Attention: This will make the VM unbootable!
        But it is required to prepare the VM for the new RAID controller when it will be restored on the physical server.
        Do NOT reboot now as this will make the VM unbootable!
    4.    Copy the LSI folder and the megasas2.INF/PNF/SYS files to the appropriate destination folders on the VM.
    3.    again create a full backup (image) with the built-in Windows Backup Utility and save it in an other accessible network location but not where you safed the first backup.
        This will be the "golden" backup if you want, where the RAID controller is prepares. We will rebuild the new machine with this second backup.
    4.    Optional: you could use the Backuputility now to restore the Systemstate of the first backup and reboot or restore the VMware snapshot.
        This will undo the changes we made to the VM.
    on the new physical server:
    1.    boot the physical server from Windows Server 2008 R2 SP1 DVD
    2.    when it is ready to install, press shift+F10 to get command prompt and do not click to install Server 2008
    3.    check driveletter of the USB stick with diskpart list vol (was C: at my Server, so don't wonder about that letter)
    3.    load drivers for ServeRAID SAS controller (this is mandatory to see the volume in diskpart)
        drvload c:\srv_2008_x64\megasas2.inf
    4.    load drivers for INTEL I350 Gigabit NIC's (you will need this to access the backup that is on the network)
        drvload c:\PRO1000\NDIS62\e1r62x64.inf
    5.    wpeinit (will start network. wait ~15 sec to let it start and get IP address)
        check if you have IP connectivity an address with ipconfig, if not, use an other NIC driver and repeat steps 4+5
    6.    create the EFI and BCD
        diskpart
        list disk
        select disk x (where x is the number of the disk to convert)
        clean
        convert gpt
        create partition EFI size=128
        format fs=fat32 quick label=EFI
        assign letter=i or any other free drive letter
        create partition MSR size=128
    6.1    Copy EFI bootloader to EFI partition
        i: (where i is the letter of your EFI partition)
        mkdir EFI\Boot
        mkdir EFI\Microsoft\Boot
        copy x:\Windows\Boot\EFI\bootmgfw.efi i:\EFI\Microsoft\Boot (where x ist the default letter of the current Windows PE environment)
        copy x:\Windows\Boot\EFI\bootmgfw.efi i:\EFI\Boot\bootx64.efi (note that the file will be renamed to bootx64.efi)
    7.    create the new partitions
        diskpart
        create partition primary size=100000 (edit the size to your needs. this will later become the system drive of your server)
        format fs=ntfs quick label=Windows
        assign letter=Y or any other free drive letter
        create partition primary size=990000 (this will temporarily store your backup and we need it for the restore process)
        format fs=ntfs quick label=Backup
        assign letter=B or any other free drive letter
        exit
    8.    map network drive and copy the backup .vhd  to the local disk
        net use L: \\networklocation\where\you\saved\the\backup (enter the credentials when asked)
            copy the .vhd file that contains the OS of your VM to the local Backup Partition B. The relevant vhd file is usually the largest file in that fileset.
            Note that the names are very similarly - be sure to get the correct file!
        copy "L:\WindowsImageBackup\VMNAME\Backup 2015-02-03 123456\00e767c6-xxxx-xxxx-xxxxxxxxxxxx.vhd" B:\
            give it time, this is slow and will take some minutes/hours and you will not see any progress! Look at the disk-LED's to see if anything is still happening
    9.    mount the .vhd and copy it's contents to the new system partition
            Note that you can only mount a locally stored .vhd. You cannot mount a .vhd in a network location.
        diskpart
        select vdisk file=B:\00e767c6-xxxx-xxxx-xxxxxxxxxxxx.vhd
        attach vdisk
        select vol 5 (where 5 is the number of the mounted vdisk)
        assign letter=Z or any other free drive letter
        exit
    10. Restore the files from the image
        z: (where z is the letter of your mounted .vhd)
        xcopy * Y:\ /e /c /h /k /o /b /q /y (where Y: is the letter of your new partition with the label "Windows")
            several "Access denied" messages appear, ignore them. Those are SystemVolumeInformation folders.
    11.    Create Boot Configuration Data (BCD)
        bootrec /RebuildBcd
            this will try to repair the missing BCD on the second of the two small partitions we created earlier in and should normally work, otherwise you'll have to create BCD manually (search google for that procedure)
            Note that it may find more than one Windows installation and ask which sould be added to the boot list. Be sure to select only the one that is in the correct Volume (Y:\)
        that's it - exit the DOS command box and close the "Install Windows" Window, after a prompt it will reboot.
        Select "Start Windows Normally", if Windows Error Recovery appears.    
    12. Preparing Windows
        When Windows boots for the first time, DO NOT reboot if you are asked, it won't come back at this stage!
        Install Intel chipset drivers for the Server (I used "intc_dd_inteldp_9.4.0.1026_windows_32-64.exe" from IBM website)
        Open Device Manager, uninstall the "RAID-Controller" with the exclamation mark. You cannot install the correct driver for this Device at this point, it will bring you the error: "Cannot create a stable subkey under a volatile
    parent key"
        Once again, DO NOT reboot!
        In Device Manager select Action>Add Legacy Hardware
        click Next
        select Hardware manually
        select Storage Controller as Type
        LSI should be listed, select "LSI MegaRAID SAS 9281-8E"
        click Next, ignore the error "Code 10" Message.
        Click Done.
        Rightclick the LSI MegaRAID SAS 9281-8E device with the exclamation mark in Device Manager
        select Update driver
        select Browse my computer for driver software
        select let me pick from a list of device drivers on my computer
        select "Have Disk"
        browse to the folder where the extracted RAID driver 6.705.05.00-MR_Windows_Driver is located (e.g. USB Flash stick E:\6.705.05.00-MR_Windows_Driver\srv_2008_x64)
        then unselect "Show Compatible Hardware"
        on the right side, scroll up and select "IBM ServeRAID M5110e SAS/SSATA Controller"
        ignore the Update Driver Warning and click Yes
        click Next, ignore the error "Code 10" Message.
        ignore the exclamation mark on "IBM ServeRAID M5110e SAS/SSATA Controller" in Device Manager but be sure that there is only this controller and no other RAID-Controller or LSI SAS Controller listed under "Other Devices"
    or "Storage Controllers"
        NOW you are safe to reboot
        After reboot you will find two "IBM ServeRAID M5110e SAS/SSATA Controller" in Device Manager
        Rightclick and uninstall the one with the exclamation mark. Do not tick the checkbox to remove the driver as well!
    You're done!! (hopefully)

    Windows Registry Editor Version 5.00
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase]
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0060&SUBSYS_C31115D9]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0060&SUBSYS_C38015D9]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0060&SUBSYS_C41115D9]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0060&SUBSYS_C48015D9]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0060&SUBSYS_C51115D9]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0060&SUBSYS_C58015D9]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0060&SUBSYS_C61115D9]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0060&SUBSYS_C68015D9]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0060&SUBSYS_C71115D9]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0060&SUBSYS_C78015D9]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0060&SUBSYS_C81115D9]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0060&SUBSYS_C88015D9]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0060&SUBSYS_C91115D9]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0060&SUBSYS_C98015D9]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0060&SUBSYS_D20219E5]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0060&SUBSYS_D20319E5]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0071&SUBSYS_00721137]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_00011BD4]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_00721137]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_00731137]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_008F1137]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_00B01137]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_00B11137]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_00B61137]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_00B71137]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_00C21137]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_00C31137]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_03B11014]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_040015D9]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_040D1014]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_10541000]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_11771734]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_14581002]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_1F201462]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_30351054]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_350C8086]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_350D8086]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_822910F1]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_843B1043]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_84711043]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_92211000]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_92401000]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_92408086]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_92411000]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_92418086]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_92421000]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_92431000]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_92441000]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_92A01000]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_92A11000]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0078&SUBSYS_92501000]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0078&SUBSYS_92511000]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0078&SUBSYS_92701000]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_00011BAA]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_00021BD4]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_00791137]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_02001AE3]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_03B21014]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_03B31014]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_03C71014]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_070015D9]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_11761734]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_11B31734]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_30361054]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_350B8086]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_84731043]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_84801043]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_8985152D]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_92551000]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_92561000]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_92568086]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_92601000]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_92608086]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_92611000]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_92618086]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_92621000]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_92631000]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_92641000]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_92648086]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_92671000]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_92678086]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_92681000]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_92688086]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_92751000]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_92758086]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_92761000]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_92768086]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_92771000]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_92801000]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_92808086]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_92811000]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_92821000]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_92828086]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_92841000]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_92881000]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_92891000]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_92901000]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_92908086]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_D20819E5]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_D20919E5]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0409&SUBSYS_10091000]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0411&SUBSYS_10011000]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0411&SUBSYS_10018086]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0411&SUBSYS_10021000]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0411&SUBSYS_10031000]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0411&SUBSYS_10038086]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0411&SUBSYS_10041000]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0411&SUBSYS_10081000]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0411&SUBSYS_10088086]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0411&SUBSYS_100C1000]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0411&SUBSYS_100D1000]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0411&SUBSYS_10811734]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0411&SUBSYS_10a31734]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0411&SUBSYS_20041000]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0411&SUBSYS_20051000]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0411&SUBSYS_30161054]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0411&SUBSYS_34908086]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0411&SUBSYS_35008086]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0411&SUBSYS_35018086]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0411&SUBSYS_35048086]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0411&SUBSYS_35078086]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0411&SUBSYS_82871033]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0413&SUBSYS_10051000]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"

  • Use of Business Systems and Technical Systems

    Hi
    What is the use of having business systems and technical systems in SAP XI. I don't see any configuration details needed to create these. I understand that it logically divides the interfaces into different business systems but is that the only use? The only place I see the real configuration done is in the adapter configuration.
    Vijay

    Vijay,
    The technical system actually works better for our non-SAP systems than the SAP systems. Here is our scenario:
    We have an AS400 business system that uses a file adapter to send files to XI and then uploaded to SAP ECC. The file adapter does not ask for the system information so we can switch between dev and test by changing the DNS address in the technical system entry (dynamic reference like a property file lookup). The communication channel settings do not have to change.
    The receiver is SAP using an RFC adapter which requires the system ID, and client (hard coded).  Everytime we change clients, we have to change the settings in the RFC adapter. This is more to your point of why do we have a technical system if we have to provide the settings in the adapter as well. The RFC adapter should read the application server and client values from it's parent business system so the changes don't have to be made everytime we point to a new client( such as QA). This is irritating.
    So maybe the theory is good but the implementation could be better in this case.
    Thanks,
    Troy

  • New Mac Mini Server, two Hard drives, Can I install an older Mac OS on the second drive and switch start up disks to run PowerPc applications?

    New Mac Mini Server, has two Hard drives, could I install an older Mac OS on the second drive and switch start up disks to run PowerPc applications?

    I haven't purchased a Mac Mini at this time and I may not if I can't use it as a non server. I need to update my system I would be better off buying a new Mac with Snow Leopard the last app that will run Rosetta. The Mac Mini Server has a quad 2.0 processor and 4 GB RAM and two internal hard drives and should out perform my dual 1.25 G4. I can run PPC apps on my G4 but it is 8+ years old and seems to be getting noisy. I don't want to tie myself to another old machine. I want a machine that will work with Intel Apps I was hoping that the two hard drives would allow me to boot from the second with Snow Leopard and use Lion on the first drive to be able to keep up to date with all my other universal apps and Mac OS up grades. The application I use the most is my CanvasX app with drawing & vector effects, text & typography, sprite technology, painting, image editing, and multimedia tools are all in this one app but will not be updated to run Intel apps. I am frozen in time because my most valuable Application won't be updated and Apple has cut me off by not supporting PPC in Lion and onward; Apple used to backward support but I guess that they are no longer as user friendly and concerned with a happy user. I have always been a loyal Mac user and I will not migrate to Windows under any circumstance; I hate windows!
    Thanks for your prompt response,
    Dick Deaton

Maybe you are looking for