BT transcieving Key & W2003 / MSI support sucks!

What kind of a f*cked up company is this, no support, no replies, on website it's IMPOSSIBLE to find anything but motherboards in other owrds, they don't give a damn about customers.
I bought Bluetooh Transceiving Key and driver won't work under Windows Server 2003 (worked fine under 2000 and even there this software sucks). It asks me for some key?! What does it have to do with me what kind of license MSI bought from Widcomm? Okay, if it doesn't work under 2003 fine, it's totaly lame and stupid, but at least make a statement saying "Our hardware doesn't work under Windows Server 2003".

If this is user2user, where is their support? Nowhere. It's hard to find anything at all on their website since their webmaster obviously doesn't know anything about navigation. Beside, look at this crappy forum: you can't edit your messages, there are only forums for motherboards and some VGA cards, that's all.
What beta software? Windows Server 2003 is final, we have a licensed copy and all. Besides, beta software is out so companies can test their new drivers and software on it but MSI obviously doesn't do that. And what do they care which OS I have? It's XP based so XP drivers should work but since some smarta55 included OS version checking, it doesn't work. Pure lamers. If they were any good they'd at least update their compatibility list if they are too lasy to update their drivers.
I guess they need to learn a thing or two about customers care..it's okay when we bring them money but when you need support they just plain ignore you. Best support imho was from Diamond, they replied very quickly + they had live IRC support.

Similar Messages

  • How do I contact MSI Support in the UK?

    How do I contact MSI Support in the UK?
    The email address I used previously ended up going to Accelrys support team! DOH!
    Cheers
    BB

    Read Here First  - MSI Locations WorldWide

  • 8 is rejecting my key code.  Support indicates it is a valid code and I need to reinstall.  I did and it is still rejecting.  What should I do next.

    Thank you for considering my question.  That is very generous.
    8 is rejecting my key code.  Support indicates it is a valid code and I need to re install.  I did and it is still rejecting.  What should I do next.

    Acrobat 8 ?
    Standard (sn:1016...) or Pro (sn:1118...) ?
    Do you install from CD/DVD or download?
    If it's a download, what's the size of the install file and where did you download it?
    Is it a full version or an upgrade?
    What's the operation System (Win, Mac) ?

  • What's with the MSI support?

    I bought a MSI-K8N Platinum about 6 weeks ago and since that day I've had nothing but trouble with my wireless network. As I'm not one of those who gives up instantly I figured that I might solve the (what seems to be software)-problems on my own or at worst with the guidance of MSI:s cunning support. It seems that I was severly mistaken though.. I've posted in two threads in this very forum without any answer and I've mailed the MSI support concerning my issue without any luck. Now it seems that my hard work has payed off with a mainboard that it's too late to reship and with an useless wireless network that cost me another 200$ of my hard earned student-salary.
    When can I hope to get an answer to my questions? Or any response at all for that sake?
    Here's links to the threads concerning this issue:
    https://forum-en.msi.com/index.php?topic=66928.0
    https://forum-en.msi.com/index.php?topic=25278.0
    Furthermore I'm still waiting for the support to contact me. I would very much like to get to use my high-end equipment before it's yesterdays news...
    Sorry if this thread makes me come of as a b**ch, but it seems that I'm not getting attention with this matter of mine. I'm sure the support and this forum is an excellent node for other concerns.
    // Klab0

    In Reply to syar 2003:
    I've already had my wireless network for a while and it (still) works perfectly with my old Abit m0b0. It consists of a D-link DWL-G520, D-link DWL-G650 and a D-link DI-624 accesspoint.
    In Reply in general:
    I've tried with belkin for my workstation but it seems to be in conflict with my other D-link products. Hence I don't want to mix network brands because as you say, they usually has quite poor compability, and for another thing I would like to be able to use the "boost"-functions available when using all D-link Etreme G products (Extended range and "108Mbs"). It seems quite odd to me that pretty much every D-link product except my DWL-G520 is supported by my mainboard, and since I know for a fact that there's nothing wrong with the card I'm led to beleive that the problem has something to do with my software configuration.
    Problem specifics:
    I've updated to the latest mainboard and ethernet drivers for my mainboard, I have NOT installed digicell though since I figured it would be messy with two separate programs trying to configure my wireless network. I've deactivated the firewire, GbLAN and ethernet in the BIOS without any result. I've tried with the PCI-card in PCI-slot 5 and 4 (the orange one optimized for wireless networks and the one next to it.) The system seems to find the card with the right drivers and it seems to work perfectly except for one thing: I can't achieve contact with the acesspoint.
    In one of the threads i hijacked the person who made the thread said that he solved the problem, so I'm still hoping to work this thing out somehow. What I'm really wondering is if there's some basic mistake (a BIOS-setting etc) that often comes up as a problem for lamers like me when setting up a wireless network with this mainboard. I will try with the MSI wireless PCI-card that came with the mainboard if I can't solve it with my existing DWL-G520, but it is really a pain in the a** since I suppose it will only lead to compabilityproblems with the acesspoint instead.
    If anyone has a slightest clue, please don't hesitate to mention it. It might as well be something very basic that has been overlooked. Thanks guys.

  • Really Close to dumping Mozilla Thunderbird. The slowness is just not worth the hassle and the support sucks.

    I have been using Mozilla Thunderbird for many years. It has always been a good system. Now, I get so when I hit delete, it takes a minute or two to delete the e-mail. I have tried to follow all the instructions on the help system and have turned off Mcafee each time I try to read my mail.
    I am not a expert in computers but can usually follow directions fairly well. The fact that Mazilla's help system rely on asking questions of a group does not make it any easier to fix these issues. I see the same questions being asked by multiple people without clear answers to why this is happening.
    Unfortunately, if this issue is not resolved shortly, I am going to have to dump Mozilla for another system..
    Bruce Cunha
    [email protected]

    Saying The support sucks is not exactly being polite towards those whom you expect some free help. I prefer to think that you are just frustrated and the offensive remark was unintentional.
    It would be useful if you could provide some information about your situation, system etc
    You have McAfee and say you ''turn it off'' when reading emails, you do not need to turn it off entirely, just stop it scanning emails. This will mean you do not have to keep switching it on and off.
    Here are the instructions for doing this.
    * https://wiki.mozilla.org/Thunderbird:Testing:Antivirus_Related_Performance_Issues#McAfee
    Please provide the following information, so that it is possible to get an understanding of your situation and setup:
    * What OS do you use?
    * What version of Thunderbird?
    * Is this an IMAP or POP mail account which has the issue?
    * If IMAP- is it a gmail account?
    * Do you have one or more mail accounts?
    * How frequently do you compact your folders?
    * When did last empty and compact your Deleted folder?
    * Do you have many folders?
    re: the Inbox
    * Is this folder used as an Inbox for new incoming mail with only a few emails in it or is it used to store a load of emails?
    * Have you set up Archive Options to archive by month and retain folder structure?
    * Do you Archive emails older than eg: a month, two months?
    Please answer the above queries, so the forum understands your current situation.

  • How to find your BIOS without reboot - for MSI support

    When sending in a question to the MSI support team, they will not only ask for your computer model but also for your BIOS.
    Usually this means a reboot, a reboot in which you may miss the BIOS information...
    Here is the easy way to do it without restarting your computer.
    1: Right click on Start and then Run.
    2: In the text box in the Run window, type msinfo32 and click OK. This will open the System Information program.
    3: When System Information first opens, it defaults to the System Summary, a short list with some of the most important information about your computer system listed.
    4: On the right side of the program, locate the BIOS Version/Date entry.
    5: This field contains the BIOS version that is currently running on your motherboard. This field may also contain additional information such as the BIOS date, BIOS manufacturer, motherboard manufacturer and the motherboard model number.
    6: Write down the numbers in your support window and close System Information.
    Thats it.
    Best Regards
    /Lucas

    Also, here is the email to MSI support: [email protected]
    Cheers

  • Touch keys (on MSI GX70)

    Hello
    My touchkeys don't work anymore (cooler booster, keyboard lighting...) after having updated my vbios, which MSI support
    told me to do because I had a performance issue. (MSI GX70 Destroyer)
    Does anyone know what to do? I'm not getting a reply from MSI.
    If the touchkeys are broken, is there any other way to launch the cooler booster?

    Hi, thanks for replying!
    Dear customer,
    Please update VBIOS via our website:
    http://www.msi.com/support/nb/GX70-3CC-Destroyer.html#down-firmware
    This was the first email I got from MSI, the link leads to the MSI page where you can update your Firmware.
    I updated to 176KEMS1.507 which I believe is correct.
    After a week I got a new reply from them, telling my to 1. Reinstall SCM 2. Restore system
    Did both, didn't work.

  • MSI "support" is non-existent

    So, how long on average does it take for MSI support to reply?  1 month, 2 months, 3 years?  I only thought ASUS had the worst support.  MSI has set a new low-water mark for indifference toward the customer.
    Thanks a bunch.

    In any ways, can I know which "support" are you implying on? Forum support or Direct support...  ?(
    If it's Forum Support, I can tell you that our team have proved you wrong as I've reply u in less than 24hours regarding your Qn... whereas for Direct Technical Support, I guess I'm in no position to say anything but to sit on the fence to be fair   .

  • MSI Support

    I have emailed the MSI support people 3 times and each time I get no reply.  X(  Has anybody here ever had any replies off them?
    All I wanted to know was if there was an improved BIOS coming out for my mainboard (746F-Ultra). Nothing too taxing for a support service, it would only take someone a couple of minutes.
    You'd think that a new board like this would have its problems sorted out quickly, as bad reports would effect sales. but the problems that I have asked about are just ignored!
    Maybe next time i will buy another brand.
    Whats your experiences?

    i never recieved word back from them, and the techie told me that the mobo was bad, becuase i couldnt get it to post after clearing cmos.
    THIS IS THE LAST TIME I BUY FROM MSI.
    took three hours to get ahold of anyone after the tech support office was "open".

  • MSI Support in Finland, VGA-Card RX4870-T2D512-OC

    Hi,
    I was wondering that do i get any kind of help from here because from MSI Support to EU customer seems to be non-existent.
    I have posted an issue to MSI Online Customer Service over an 1,5 month ago and it is still in "New Inquire" state. How long i have to wait to get my message answered.
    Here is my original message
    MSI RX4870-T2D512-OC
    Hi,
    I was wondering do i have any kind of change to get my graphic card to warranty even if its over 2 year old since i bought it. There is a malfunction in other dvi-port and s-video port. Neither of them don´t show any picture at all and windows 7 recognizes 2 display monitor and 1 TV even that i have just one monitor plugged in. I have re-installed all drivers and even formatted the whole computer and the problem is still on so its not a software malfunction. A clear hardware problem. I hope there is still a change to get this in warranty because it was expensive and I do not think that it should breakdown in less than two years
    I have the original receipt and the bought day was 14.08.2008
    Serial number for the card is:
    SN:912-V803-2660807000305
    Best Regards
    Joni Mustonen
    "

    Quote from: AaronYuri on 09-August-08, 02:00:37
    Do it through hardware settings, not driver level.
    Thanks for helping!
    I solved the problem. I was forgotten to connect an extra powercable to my graphics card. Trying all the settings in Windows XP instead of Vista, the message popped up that my card its power was to low... Now I'm able to downclock my gpu Thanks again for helping!!
    Stefaan

  • My P67A-GD80 (B3) - Asking about MSI Support

    Hello, Sorry if i'm posting this in the wrong section but i don't know where else to go..
    I had a technical problem with my P67A-GD80 (B3) board.. so i tried to contact msi support 40 days ago by sending the the problem details on the main world wide website but they didn't answer me until now.. I can find my question in my support history.. but no answer.. so am i doing it right??! what shall i do to get an answer from them? I just want to know if i have to get a new board or not :\
    Thank you for your time

    and this is the problem as i described to them:
    "First I want to thank you regarding your all good quality product. I have a small question to ask; Last year (20th March 2012) I bought a MSI motherboard from Amazon.com this is the link of the product and buyer info: http://www.amazon.com/gp/product/B004QGJV8Q/ref=oh_details_o01_s00_i01?ie=UTF8&psc=1 So 2 days ago i had a problem with the board, i tried to power it on, but i couldn't, i kept trying then i heard something exploded behind the processor socket and smoke went out of it... I don't know what caused that.. I'm using water cooling system for the cpu, so it is possible that it leaked water into the board? and is it a fixable problem? I'm not sure if i can ask about any warranty but if there is please tell me.. I don't want to loose my board.. its the best board !"

  • KEY and KEYREFs support on XML DB

    First of all, sorry for my english but I am a spanish researcher who have not been abroad too much :-).
    I�m trying to use XML DB to store XML documents that represents UML models and the way I've choosed to map relationships in my schema is using KEY and KEYREFs. The fact is that It seems to me that XML DB does not use them whem it creates the different objects that results on the schema's load. Does XMLDB support the definitons of KEYs and KEYREFs in the schema?? If so, how does it do?? Defining constraints oon the objects created?? I suppose no, because the KEYs and KEYREFs are defined on 'complexTypes' and the Oracle's constraints goes to tables (not to object types).
    I'm worling with the next schema:
    <?xml version="1.0" encoding="UTF-8"?>
    <xsd:schema xmlns="Kybele/MetaModel_Schema_All" targetNamespace="Kybele/MetaModel_Schema_All" xmlns:xdb="http://xmlns.oracle.com/xdb" xmlns:xsd="http://www.w3.org/2001/XMLSchema" version="1.0" elementFormDefault="qualified" attributeFormDefault="unqualified">
    <!-- En esta version, representaremos las relaciones usando atributos KEYs y KEYREFs
    Ademas, en esta version mapeamos el metamodelo de UML por completo-->
    <!-- En las anotaciones para XML DB usaremos el prefijo MMALL(MetaModelo Completo) -->
    <!--******************** DECLARACION DE LOS ELEMENTOS DEL METAMODELO *********************-->
    <xsd:element name="MetaModel" xdb:defaultTable="MMALL_METAMODELS_TABLE">
    <xsd:complexType xdb:SQLType="MMALL_METAMODELS_TYPE">
    <xsd:sequence>
    <xsd:element name="ModelElements" type="ModelElement" maxOccurs="unbounded"/>
    <xsd:element name="Dependencies" type="Dependency" maxOccurs="unbounded"/>
    </xsd:sequence>
    </xsd:complexType>
    <!-- Es en este punto donde definiremos las "PRIMARYKEYS"(KEYs) Y "FOREIGNKEYS"(KEYREFs) para simular relaciones -->
    <!-- ************************************************************************************************* *-->
    <!-- RELACIONES ModelElement - Dependency -->
    <xsd:key name="Dependency_PK">
    <xsd:selector xpath="Dependencies"/>
    <xsd:field xpath="Nombre"/>
    </xsd:key>
    <xsd:key name="ModelElement_PK">
    <xsd:selector xpath="ModelElements"/>
    <xsd:field xpath="Nombre"/>
    </xsd:key>
    <xsd:keyref name="Requirement_FK" refer="Dependency_PK">
    <xsd:selector xpath="ModelElements"/>
    <xsd:field xpath="requirement"/>
    </xsd:keyref>
    <xsd:keyref name="Provision_FK" refer="Dependency_PK">
    <xsd:selector xpath="ModelElements"/>
    <xsd:field xpath="provision"/>
    </xsd:keyref>
    <xsd:keyref name="Client_FK" refer="ModelElement_PK">
    <xsd:selector xpath="Dependencies"/>
    <xsd:field xpath="client"/>
    </xsd:keyref>
    <xsd:keyref name="Supplier_FK" refer="ModelElement_PK">
    <xsd:selector xpath="Dependencies"/>
    <xsd:field xpath="supplier"/>
    </xsd:keyref>
    <!-- RELACIONES Generalization - GeneralizableElement -->
    <xsd:key name="Generalization_PK">
    <xsd:selector xpath="Generalization"/>
    <xsd:field xpath="Nombre"/>
    </xsd:key>
    <xsd:key name="GeneralizableElement_PK">
    <xsd:selector xpath="GeneralizableElement"/>
    <xsd:field xpath="Nombre"/>
    </xsd:key>
    <xsd:keyref name="Subtype_FK" refer="GeneralizableElement_PK">
    <xsd:selector xpath="Generalization"/>
    <xsd:field xpath="subtype"/>
    </xsd:keyref>
    <xsd:keyref name="Type_FK" refer="GeneralizableElement_PK">
    <xsd:selector xpath="Generalization"/>
    <xsd:field xpath="type"/>
    </xsd:keyref>
    <xsd:keyref name="Generalization_FK" refer="GeneralizableElement_PK">
    <xsd:selector xpath="GeneralizableElement"/>
    <xsd:field xpath="generalization"/>
    </xsd:keyref>
    <xsd:keyref name="Specilization_FK" refer="GeneralizableElement_PK">
    <xsd:selector xpath="GeneralizableElement"/>
    <xsd:field xpath="specialization"/>
    </xsd:keyref>
    <!-- RELACIONES Classifier - AssociationEnd -->
    <xsd:key name="Classifier_PK">
    <xsd:selector xpath="Classifier"/>
    <xsd:field xpath="Nombre"/>
    </xsd:key>
    <xsd:key name="AssociationEnd_PK">
    <xsd:selector xpath="AssociationEnd"/>
    <xsd:field xpath="Nombre"/>
    </xsd:key>
    <xsd:keyref name="AssociationEnd_FK" refer="AssociationEnd_PK">
    <xsd:selector xpath="Classifier"/>
    <xsd:field xpath="associationEnd"/>
    </xsd:keyref>
    <xsd:keyref name="Participant_FK" refer="AssociationEnd_PK">
    <xsd:selector xpath="Classifier"/>
    <xsd:field xpath="participant"/>
    </xsd:keyref>
    <xsd:keyref name="AssociationEnd_Type_FK" refer="Classifier_PK">
    <xsd:selector xpath="AssociationEnd"/>
    <xsd:field xpath="type"/>
    </xsd:keyref>
    <xsd:keyref name="AssociationEnd_Specification_FK" refer="Classifier_PK">
    <xsd:selector xpath="AssociationEnd"/>
    <xsd:field xpath="specification"/>
    </xsd:keyref>
    <!-- RELACIONES AssociatioEnd - Attribute -->
    <xsd:keyref name="AttributeCompose_FK" refer="AssociationEnd_PK">
    <xsd:selector xpath="Attribute"/>
    <xsd:field xpath="associationEnd_member"/>
    </xsd:keyref>
    <!-- RELACIONES AssociatioEnd - Association -->
    <xsd:keyref name="AssociationEndCompose_FK" refer="Association_PK">
    <xsd:selector xpath="Association"/>
    <xsd:field xpath="Association_member"/>
    </xsd:keyref>
    </xsd:element>
    <!--***************************** DEFINICION DE TIPOS SIMPLES *****************************-->
    <!-- TIPO ENUMERADO AGGREGATIONTYPE -->
    <xsd:simpleType name="AggregationType">
    <xsd:restriction base="xsd:string">
    <xsd:enumeration value="none"/>
    <xsd:enumeration value="aggregate"/>
    <xsd:enumeration value="composite"/>
    </xsd:restriction>
    </xsd:simpleType>
    <!-- TIPO ENUMERADO SCOPETYPE -->
    <xsd:simpleType name="ScopeType">
    <xsd:restriction base="xsd:string">
    <xsd:enumeration value="instance"/>
    <xsd:enumeration value="classifier"/>
    </xsd:restriction>
    </xsd:simpleType>
    <!-- TIPO ENUMERADO MULTIPLICITYTYPE -->
    <xsd:simpleType name="MultiplicityType">
    <xsd:restriction base="xsd:string">
    <xsd:enumeration value="0..1"/>
    <xsd:enumeration value="1..1"/>
    <xsd:enumeration value="0..N"/>
    <xsd:enumeration value="1..N"/>
    </xsd:restriction>
    </xsd:simpleType>
    <!-- TIPO ENUMERADO CHANGEABLETYPE -->
    <xsd:simpleType name="ChangeableType">
    <xsd:restriction base="xsd:string">
    <xsd:enumeration value="none"/>
    <xsd:enumeration value="frozen"/>
    <xsd:enumeration value="add_only"/>
    </xsd:restriction>
    </xsd:simpleType>
    <!--**************************** DEFINICION DE TIPOS COMPLEJOS **********************************************-->
    <!-- TIPO COMPLEJO MODELELEMENT -->
    <xsd:complexType name="ModelElement" xdb:SQLType="MMALL_ModelElement_Type">
    <xsd:sequence>
    <xsd:element name="nombre" type="xsd:string"/>
    <!-- Subelementos para representar sus relaciones -->
    <xsd:element name="requirement" type="xsd:string" minOccurs="0" maxOccurs="unbounded"/>
    <xsd:element name="provision" type="xsd:string" minOccurs="0" maxOccurs="unbounded"/>
    </xsd:sequence>
    </xsd:complexType>
    <!-- TIPO COMPLEJO DEPENDENCY -->
    <xsd:complexType name="Dependency" xdb:SQLType="MMALL_Dependency_Type">
    <xsd:complexContent>
    <xsd:extension base="ModelElement">
    <xsd:sequence>
    <xsd:element name="description" type="xsd:string"/>
    <!-- Subelementos para representar sus relaciones -->
    <xsd:element name="client" type="xsd:string" minOccurs="0" maxOccurs="unbounded"/>
    <xsd:element name="supplier" type="xsd:string" minOccurs="0" maxOccurs="unbounded"/>
    </xsd:sequence>
    </xsd:extension>
    </xsd:complexContent>
    </xsd:complexType>
    <!-- TIPO COMPLEJO GENERALIZATION -->
    <xsd:complexType name="Generalization" xdb:SQLType="MMALL_Generalization_Type">
    <xsd:complexContent>
    <xsd:extension base="ModelElement">
    <xsd:sequence>
    <xsd:element name="discriminator" type="xsd:string"/>
    <!-- Subelementos para representar sus relaciones -->
    <xsd:element name="subtype" type="xsd:string"/>
    <xsd:element name="supertype" type="xsd:string"/>
    <!-- Al quitar minOccurs y maxOccurs obligamos a que siempre haya un (Y SOLO UNO)
    subelemento 'subtype' y 'supertype' -->
    </xsd:sequence>
    </xsd:extension>
    </xsd:complexContent>
    </xsd:complexType>
    <!-- TIPO COMPLEJO NAMESPACE -->
    <xsd:complexType name="NameSpace" xdb:SQLType="MMALL_NameSpace_Type">
    <xsd:complexContent>
    <xsd:extension base="ModelElement"/>
    </xsd:complexContent>
    </xsd:complexType>
    <!-- TIPO COMPLEJO GENERALIZABLEELEMENT -->
    <xsd:complexType name="GeneralizableElement" xdb:SQLType="MMALL_GeneralizableElement_Type">
    <xsd:complexContent>
    <xsd:extension base="NameSpace">
    <xsd:sequence>
    <xsd:element name="isRoot" type="xsd:boolean"/>
    <xsd:element name="isLeaf" type="xsd:boolean"/>
    <xsd:element name="isAbstract" type="xsd:boolean"/>
    <!-- Subelementos para representar sus relaciones -->
    <xsd:element name="generalization" type="xsd:string"/>
    <xsd:element name="specification" type="xsd:string"/>
    </xsd:sequence>
    </xsd:extension>
    </xsd:complexContent>
    </xsd:complexType>
    <!-- TIPO COMPLEJO: ASSOCIATIONEND -->
    <xsd:complexType name="AssociationEnd" xdb:SQLType="MMALL_ASSOCIATIONEND_TYPE">
    <xsd:complexContent>
    <xsd:extension base="ModelElement">
    <xsd:sequence>
    <xsd:element name="IsNavigable" type="xsd:boolean"/>
    <xsd:element name="IsOrdered" type="xsd:boolean"/>
    <xsd:element name="Aggregation" type="AggregationType"/>
    <xsd:element name="Multiplicity" type="MultiplicityType" minOccurs="0"/>
    <xsd:element name="Changeable" type="ChangeableType"/>
    <xsd:element name="TargetScope" type="ScopeType"/>
    <!-- Subelementos para representar las relaciones -->
    <xsd:element name="Qualifier" type="Attribute" minOccurs="0" maxOccurs="unbounded"/>
    <xsd:element name="Association_member" type="xsd:string"/>
    <xsd:element name="Type" type="xsd:string"/>
    <xsd:element name="Specification" type="xsd:string" minOccurs="0" maxOccurs="unbounded"/>
    </xsd:sequence>
    </xsd:extension>
    </xsd:complexContent>
    </xsd:complexType>
    <!-- TIPO COMPLEJO CLASSIFIER -->
    <xsd:complexType name="Classifier" xdb:SQLType="MMALL_CLASSIFIER_TYPE">
    <xsd:complexContent>
    <xsd:restriction base="GeneralizableElement">
    <xsd:sequence>
    <!-- Subelementos para representar las relaciones -->
    <xsd:element name="AssociationEnd" type="xsd:string" minOccurs="0" maxOccurs="unbounded"/>
    <xsd:element name="Participant" type="xsd:string" minOccurs="0" maxOccurs="unbounded"/>
    </xsd:sequence>
    </xsd:restriction>
    </xsd:complexContent>
    </xsd:complexType>
    <!-- TIPO COMPLEJO CLASS -->
    <xsd:complexType name="Class" xdb:SQLType="MMALL_CLASS_TYPE">
    <xsd:complexContent>
    <xsd:extension base="Classifier"/>
    </xsd:complexContent>
    </xsd:complexType>
    <!-- TIPO COMPLEJO ATTRIBUTE -->
    <xsd:complexType name="Attribute" xdb:SQLType="MMALL_ATTRIBUTE_TYPE">
    <xsd:sequence>
    <xsd:element name="associationEnd_member" type="xsd:string" minOccurs="0" maxOccurs="1"/>
    </xsd:sequence>
    </xsd:complexType>
    <!-- TIPO COMPLEJO ASSOCIATION -->
    <xsd:complexType name="Association" xdb:SQLType="MMALL_ASSOCIATION_TYPE">
    <xsd:complexContent>
    <xsd:restriction base="GeneralizableElement">
    <xsd:sequence>
    <xsd:element name="connection" type="AssociationEnd" minOccurs="2" maxOccurs="unbounded"/>
    </xsd:sequence>
    </xsd:restriction>
    </xsd:complexContent>
    </xsd:complexType>
    </xsd:schema>
    and when I try to load it into XMLDB it fails:
    SQL> @registerSchema oe oe /home/OE/Metamodel_Schema_All.xsd "http://kybele.escet.urjc.es/ejemplos/x
    ml_schema/Metamodel_Schema_All.xsd"
    SQL> set echo on
    SQL> connect &1/&[email protected]
    Conectado.
    SQL> alter session set events='31098 trace name context forever';
    Sesi�n modificada.
    SQL> begin
    2 dbms_xmlschema.registeruri(
    3 '&4',
    4 '&3',
    5 TRUE,TRUE,FALSE,TRUE);
    6 end;
    7 /
    antiguo 3: '&4',
    nuevo 3: 'http://kybele.escet.urjc.es/ejemplos/xml_schema/Metamodel_Schema_All.xsd',
    antiguo 4: '&3',
    nuevo 4: '/home/OE/Metamodel_Schema_All.xsd',
    begin
    ERROR en l�nea 1:
    ORA-31154: invalid XML document
    ORA-19202: Se ha producido un error en el procesamiento
    LPX-00217: invalid character 0 (\u0000) de XML
    ORA-06512: en "XDB.DBMS_XMLSCHEMA_INT", l�nea 0
    ORA-06512: en "XDB.DBMS_XMLSCHEMA", l�nea 166
    ORA-06512: en l�nea 2
    it says.
    I have done several attempts, deleting and including just some of the KEYs/KEYREFs in the schema and it seems to me that the problem is that it let me include so much keys as I want but it fails when the number of KEYREFs that I include increase.
    Help!!!
    Thanks on advance for spare your time helping us.

    Looks like known bug 2831302 fixed in (forthcoming) 10g release. In the mean time I would simply comment the key/keyref out of the schema

  • KEY and KEYREF support in Oracle XML DB

    First of all, sorry for my english but I am a spanish researcher who have not been abroad too much :-).
    I�m trying to use XML DB to store XML documents that represents UML models and the way I've choosed to map relationships in my schema is using KEY and KEYREFs. The fact is that It seems to me that XML DB does not use them whem it creates the different objects that results on the schema's load. Does XMLDB support the definitons of KEYs and KEYREFs in the schema?? If so, how does it do?? Defining constraints oon the objects created?? I suppose no, because the KEYs and KEYREFs are defined on 'complexTypes' and the Oracle's constraints goes to tables (not to object types).
    I'm worling with the next schema:
    <?xml version="1.0" encoding="UTF-8"?>
    <xsd:schema xmlns="Kybele/MetaModel_Schema_All" targetNamespace="Kybele/MetaModel_Schema_All" xmlns:xdb="http://xmlns.oracle.com/xdb" xmlns:xsd="http://www.w3.org/2001/XMLSchema" version="1.0" elementFormDefault="qualified" attributeFormDefault="unqualified">
         <!-- En esta version, representaremos las relaciones usando atributos KEYs y KEYREFs
         Ademas, en esta version mapeamos el metamodelo de UML por completo-->
         <!-- En las anotaciones para XML DB usaremos el prefijo MMALL(MetaModelo Completo) -->
         <!--******************** DECLARACION DE LOS ELEMENTOS DEL METAMODELO *********************-->
         <xsd:element name="MetaModel" xdb:defaultTable="MMALL_METAMODELS_TABLE">
              <xsd:complexType xdb:SQLType="MMALL_METAMODELS_TYPE">
                   <xsd:sequence>
                        <xsd:element name="ModelElements" type="ModelElement" maxOccurs="unbounded"/>
                        <xsd:element name="Dependencies" type="Dependency" maxOccurs="unbounded"/>
                   </xsd:sequence>
              </xsd:complexType>
         <!-- Es en este punto donde definiremos las "PRIMARYKEYS"(KEYs) Y "FOREIGNKEYS"(KEYREFs) para simular relaciones -->
         <!-- ************************************************************************************************* *-->
              <!-- RELACIONES ModelElement - Dependency -->
              <xsd:key name="Dependency_PK">
                   <xsd:selector xpath="Dependencies"/>
                   <xsd:field xpath="Nombre"/>
              </xsd:key>
              <xsd:key name="ModelElement_PK">
                   <xsd:selector xpath="ModelElements"/>
                   <xsd:field xpath="Nombre"/>
              </xsd:key>
              <xsd:keyref name="Requirement_FK" refer="Dependency_PK">
                   <xsd:selector xpath="ModelElements"/>
                   <xsd:field xpath="requirement"/>
              </xsd:keyref>
              <xsd:keyref name="Provision_FK" refer="Dependency_PK">
                   <xsd:selector xpath="ModelElements"/>
                   <xsd:field xpath="provision"/>
              </xsd:keyref>
              <xsd:keyref name="Client_FK" refer="ModelElement_PK">
                   <xsd:selector xpath="Dependencies"/>
                   <xsd:field xpath="client"/>
              </xsd:keyref>
              <xsd:keyref name="Supplier_FK" refer="ModelElement_PK">
                   <xsd:selector xpath="Dependencies"/>
                   <xsd:field xpath="supplier"/>
              </xsd:keyref>
              <!-- RELACIONES Generalization - GeneralizableElement -->
              <xsd:key name="Generalization_PK">
                   <xsd:selector xpath="Generalization"/>
                   <xsd:field xpath="Nombre"/>
              </xsd:key>
              <xsd:key name="GeneralizableElement_PK">
                   <xsd:selector xpath="GeneralizableElement"/>
                   <xsd:field xpath="Nombre"/>
              </xsd:key>
              <xsd:keyref name="Subtype_FK" refer="GeneralizableElement_PK">
                   <xsd:selector xpath="Generalization"/>
                   <xsd:field xpath="subtype"/>
              </xsd:keyref>
              <xsd:keyref name="Type_FK" refer="GeneralizableElement_PK">
                   <xsd:selector xpath="Generalization"/>
                   <xsd:field xpath="type"/>
              </xsd:keyref>
              <xsd:keyref name="Generalization_FK" refer="GeneralizableElement_PK">
                   <xsd:selector xpath="GeneralizableElement"/>
                   <xsd:field xpath="generalization"/>
              </xsd:keyref>
              <xsd:keyref name="Specilization_FK" refer="GeneralizableElement_PK">
                   <xsd:selector xpath="GeneralizableElement"/>
                   <xsd:field xpath="specialization"/>
              </xsd:keyref>
              <!-- RELACIONES Classifier - AssociationEnd -->
              <xsd:key name="Classifier_PK">
                   <xsd:selector xpath="Classifier"/>
                   <xsd:field xpath="Nombre"/>
              </xsd:key>
              <xsd:key name="AssociationEnd_PK">
                   <xsd:selector xpath="AssociationEnd"/>
                   <xsd:field xpath="Nombre"/>
              </xsd:key>
              <xsd:keyref name="AssociationEnd_FK" refer="AssociationEnd_PK">
                   <xsd:selector xpath="Classifier"/>
                   <xsd:field xpath="associationEnd"/>
              </xsd:keyref>
              <xsd:keyref name="Participant_FK" refer="AssociationEnd_PK">
                   <xsd:selector xpath="Classifier"/>
                   <xsd:field xpath="participant"/>
              </xsd:keyref>
              <xsd:keyref name="AssociationEnd_Type_FK" refer="Classifier_PK">
                   <xsd:selector xpath="AssociationEnd"/>
                   <xsd:field xpath="type"/>
              </xsd:keyref>
              <xsd:keyref name="AssociationEnd_Specification_FK" refer="Classifier_PK">
                   <xsd:selector xpath="AssociationEnd"/>
                   <xsd:field xpath="specification"/>
              </xsd:keyref>
              <!-- RELACIONES AssociatioEnd - Attribute -->
              <xsd:keyref name="AttributeCompose_FK" refer="AssociationEnd_PK">
                   <xsd:selector xpath="Attribute"/>
                   <xsd:field xpath="associationEnd_member"/>
              </xsd:keyref>
              <!-- RELACIONES AssociatioEnd - Association -->
              <xsd:keyref name="AssociationEndCompose_FK" refer="Association_PK">
                   <xsd:selector xpath="Association"/>
                   <xsd:field xpath="Association_member"/>
              </xsd:keyref>
         </xsd:element>
         <!--***************************** DEFINICION DE TIPOS SIMPLES *****************************-->
         <!-- TIPO ENUMERADO AGGREGATIONTYPE -->
         <xsd:simpleType name="AggregationType">
              <xsd:restriction base="xsd:string">
                   <xsd:enumeration value="none"/>
                   <xsd:enumeration value="aggregate"/>
                   <xsd:enumeration value="composite"/>
              </xsd:restriction>
         </xsd:simpleType>
         <!-- TIPO ENUMERADO SCOPETYPE -->
         <xsd:simpleType name="ScopeType">
              <xsd:restriction base="xsd:string">
                   <xsd:enumeration value="instance"/>
                   <xsd:enumeration value="classifier"/>
              </xsd:restriction>
         </xsd:simpleType>
         <!-- TIPO ENUMERADO MULTIPLICITYTYPE -->
         <xsd:simpleType name="MultiplicityType">
              <xsd:restriction base="xsd:string">
                   <xsd:enumeration value="0..1"/>
                   <xsd:enumeration value="1..1"/>
                   <xsd:enumeration value="0..N"/>
                   <xsd:enumeration value="1..N"/>
              </xsd:restriction>
         </xsd:simpleType>
         <!-- TIPO ENUMERADO CHANGEABLETYPE -->
         <xsd:simpleType name="ChangeableType">
              <xsd:restriction base="xsd:string">
                   <xsd:enumeration value="none"/>
                   <xsd:enumeration value="frozen"/>
                   <xsd:enumeration value="add_only"/>
              </xsd:restriction>
         </xsd:simpleType>
         <!--**************************** DEFINICION DE TIPOS COMPLEJOS **********************************************-->
         <!-- TIPO COMPLEJO MODELELEMENT -->
         <xsd:complexType name="ModelElement" xdb:SQLType="MMALL_ModelElement_Type">
              <xsd:sequence>
                   <xsd:element name="nombre" type="xsd:string"/>
                   <!-- Subelementos para representar sus relaciones -->
                   <xsd:element name="requirement" type="xsd:string" minOccurs="0" maxOccurs="unbounded"/>
                   <xsd:element name="provision" type="xsd:string" minOccurs="0" maxOccurs="unbounded"/>
              </xsd:sequence>
         </xsd:complexType>
         <!-- TIPO COMPLEJO DEPENDENCY -->
         <xsd:complexType name="Dependency" xdb:SQLType="MMALL_Dependency_Type">
              <xsd:complexContent>
                   <xsd:extension base="ModelElement">
                        <xsd:sequence>
                             <xsd:element name="description" type="xsd:string"/>
                             <!-- Subelementos para representar sus relaciones -->
                             <xsd:element name="client" type="xsd:string" minOccurs="0" maxOccurs="unbounded"/>
                             <xsd:element name="supplier" type="xsd:string" minOccurs="0" maxOccurs="unbounded"/>
                        </xsd:sequence>
                   </xsd:extension>
              </xsd:complexContent>
         </xsd:complexType>
         <!-- TIPO COMPLEJO GENERALIZATION -->
         <xsd:complexType name="Generalization" xdb:SQLType="MMALL_Generalization_Type">
              <xsd:complexContent>
                   <xsd:extension base="ModelElement">
                        <xsd:sequence>
                             <xsd:element name="discriminator" type="xsd:string"/>
                             <!-- Subelementos para representar sus relaciones -->
                             <xsd:element name="subtype" type="xsd:string"/>
                             <xsd:element name="supertype" type="xsd:string"/>
                             <!-- Al quitar minOccurs y maxOccurs obligamos a que siempre haya un (Y SOLO UNO)
                                  subelemento 'subtype' y 'supertype' -->
                        </xsd:sequence>
                   </xsd:extension>
              </xsd:complexContent>
         </xsd:complexType>
         <!-- TIPO COMPLEJO NAMESPACE -->
         <xsd:complexType name="NameSpace" xdb:SQLType="MMALL_NameSpace_Type">
              <xsd:complexContent>
                   <xsd:extension base="ModelElement"/>
              </xsd:complexContent>
         </xsd:complexType>
         <!-- TIPO COMPLEJO GENERALIZABLEELEMENT -->
         <xsd:complexType name="GeneralizableElement" xdb:SQLType="MMALL_GeneralizableElement_Type">
              <xsd:complexContent>
                   <xsd:extension base="NameSpace">
                        <xsd:sequence>
                             <xsd:element name="isRoot" type="xsd:boolean"/>
                             <xsd:element name="isLeaf" type="xsd:boolean"/>
                             <xsd:element name="isAbstract" type="xsd:boolean"/>
                             <!-- Subelementos para representar sus relaciones -->
                             <xsd:element name="generalization" type="xsd:string"/>
                             <xsd:element name="specification" type="xsd:string"/>          
                        </xsd:sequence>
                   </xsd:extension>
              </xsd:complexContent>
         </xsd:complexType>
         <!-- TIPO COMPLEJO: ASSOCIATIONEND -->
         <xsd:complexType name="AssociationEnd" xdb:SQLType="MMALL_ASSOCIATIONEND_TYPE">
         <xsd:complexContent>
              <xsd:extension base="ModelElement">
                   <xsd:sequence>
                        <xsd:element name="IsNavigable" type="xsd:boolean"/>
                        <xsd:element name="IsOrdered" type="xsd:boolean"/>
                        <xsd:element name="Aggregation" type="AggregationType"/>
                        <xsd:element name="Multiplicity" type="MultiplicityType" minOccurs="0"/>
                        <xsd:element name="Changeable" type="ChangeableType"/>
                        <xsd:element name="TargetScope" type="ScopeType"/>
                        <!-- Subelementos para representar las relaciones -->
                        <xsd:element name="Qualifier" type="Attribute" minOccurs="0" maxOccurs="unbounded"/>
                        <xsd:element name="Association_member" type="xsd:string"/>
                        <xsd:element name="Type" type="xsd:string"/>
                        <xsd:element name="Specification" type="xsd:string" minOccurs="0" maxOccurs="unbounded"/>
                   </xsd:sequence>
              </xsd:extension>
         </xsd:complexContent>          
         </xsd:complexType>
         <!-- TIPO COMPLEJO CLASSIFIER -->
         <xsd:complexType name="Classifier" xdb:SQLType="MMALL_CLASSIFIER_TYPE">
              <xsd:complexContent>
                   <xsd:restriction base="GeneralizableElement">
                        <xsd:sequence>
                             <!-- Subelementos para representar las relaciones -->
                             <xsd:element name="AssociationEnd" type="xsd:string" minOccurs="0" maxOccurs="unbounded"/>
                             <xsd:element name="Participant" type="xsd:string" minOccurs="0" maxOccurs="unbounded"/>
                        </xsd:sequence>
                   </xsd:restriction>
              </xsd:complexContent>
         </xsd:complexType>
         <!-- TIPO COMPLEJO CLASS -->
         <xsd:complexType name="Class" xdb:SQLType="MMALL_CLASS_TYPE">
              <xsd:complexContent>
                   <xsd:extension base="Classifier"/>
              </xsd:complexContent>
         </xsd:complexType>
         <!-- TIPO COMPLEJO ATTRIBUTE -->
         <xsd:complexType name="Attribute" xdb:SQLType="MMALL_ATTRIBUTE_TYPE">
              <xsd:sequence>
                   <xsd:element name="associationEnd_member" type="xsd:string" minOccurs="0" maxOccurs="1"/>
              </xsd:sequence>
         </xsd:complexType>
         <!-- TIPO COMPLEJO ASSOCIATION -->
         <xsd:complexType name="Association" xdb:SQLType="MMALL_ASSOCIATION_TYPE">
              <xsd:complexContent>
                   <xsd:restriction base="GeneralizableElement">
                        <xsd:sequence>
                             <xsd:element name="connection" type="AssociationEnd" minOccurs="2" maxOccurs="unbounded"/>
                        </xsd:sequence>
                   </xsd:restriction>
              </xsd:complexContent>
         </xsd:complexType>
    </xsd:schema>
    and when I try to load it into XMLDB it fails:
    SQL> @registerSchema oe oe /home/OE/Metamodel_Schema_All.xsd "http://kybele.escet.urjc.es/ejemplos/x
    ml_schema/Metamodel_Schema_All.xsd"
    SQL> set echo on
    SQL> connect &1/&[email protected]
    Conectado.
    SQL> alter session set events='31098 trace name context forever';
    Sesi�n modificada.
    SQL> begin
    2 dbms_xmlschema.registeruri(
    3 '&4',
    4 '&3',
    5 TRUE,TRUE,FALSE,TRUE);
    6 end;
    7 /
    antiguo 3: '&4',
    nuevo 3: 'http://kybele.escet.urjc.es/ejemplos/xml_schema/Metamodel_Schema_All.xsd',
    antiguo 4: '&3',
    nuevo 4: '/home/OE/Metamodel_Schema_All.xsd',
    begin
    ERROR en l�nea 1:
    ORA-31154: invalid XML document
    ORA-19202: Se ha producido un error en el procesamiento
    LPX-00217: invalid character 0 (\u0000) de XML
    ORA-06512: en "XDB.DBMS_XMLSCHEMA_INT", l�nea 0
    ORA-06512: en "XDB.DBMS_XMLSCHEMA", l�nea 166
    ORA-06512: en l�nea 2
    it says.
    I have done several attempts, deleting and including just some of the KEYs/KEYREFs in the schema and it seems to me that the problem is that it let me include so much keys as I want but it fails when the number of KEYREFs that I include increase.
    Help!!!
    Thanks on advance for spare your time helping us.

    Please post this message at:
    Forums Home » Oracle Technology Network (OTN) » Products » Database » XML DB

  • Life keying no longer supported by Adobe?

    I am looking for software that provides life chroma keying for a Flash based videobroadcasting. Currently an IEEE 1394 connected video source is streamed by FMLE.
    CS3 Ultra obviously had life keying capability, but it is no longer available.
    Can anybody recommend  a software, hardware or appliance that provides life keying for blue box / green box applications?

    As far as I have heard/read, there has been nothing indiicated by Adobe that Flash will no longer be supported by them in the near future.  So far there just seem to be alot of people that are misreading the articles that have come out.
    1.  Flash player has never been supported on the iStuff.  Apparently that is not going to change.  The recent articles by non-Adobe writers say that Adobe will no longer be pursuing development for the Flash player on any mobile devices.  That is supposedly just for the Flash Player, and just for mobile devices.
    2.  You should contact customer support.  I don't think they have a rent-to-own option... as far as I understand, when you rent you are kept updated on the latest versions released, so if CS6 came out tomorrow, you're already in the lineup to get upgraded to it.  The best people to ask are the ones that sell it.

  • Adobe Support Sucks!

    Adobe support for Elements 12 issues SUCKS!

    I looked into the FAQ's and followed the "Sharede Technologies" install errors for the OOBE renaming directions as well as the "run" the AAM and Support Advisor, and CC Cleaner tools, I received the same error, over an over again.
    I actually did not use the forum, as I used the support track as recommended if problems continued. 
    After spending 3 hours with a tech one night, changing/renaming the OOBE, running the  AAM, the CC Cleaner tool and reinstalling three times and ending at 2:00am, to no avail, I was then asked to do all of this over again and again, as he obviously did not know what he was doing.
    After dto the same thing for the third time, I told him I hadd spent way too much time getting nowhere with him and his continual requesting that I do the same thing over to get the same result (definition of insanity) I told him that we were done and he needed to escalate this.  To that he responded with another request to change the OOBE directory in Program Files (86) again and in User directories and use Task Manager to shut down all Adobe services, which I did, for some indiotic reason, and the same result, again, he finally escalated it to the "next level" of ineptitude.
    I then received an email to follow another set of lame directions, which on the face looked like it was the same instructions with the addition of running the  CC Cleaner tool.  Which I did on the 20th od December and sent the results back that there was no change and the same error came back about shared technologies.
    I have been working through this since November 5th, reinstalled, or tried to over 14 times now, with their assistance, on my own trying to use the FAQ's and to this day, still no help, nothing that brings me any closer.
    When I read the forum I see so many users having issues with Elements 12 and Premiere 12 it seems Adobe created a poor version and it has been a lot of trouble for a lot of people. 
    THis is simply rediculous for a software company that likes to tout how great they are.  I have been a very longtime fan of the Photoshop product but this particulare experience has dampened my confidence in Adobe

Maybe you are looking for

  • Audio CD's won't show in Finder, Disk Utility or iTunes

    The last few months represent a downward spiral for importing music or audiobooks on CD. If I pop in a dad CD or DVD the Finder immediately shows it on the desktop. Same with movie DVD's and blank media. But put in an audio disk and its like Mac OS 1

  • How to get the user wheel back on sharing permissions on Mac HD

    I have accidety deleted the user wheel and now I need to know how I can get it back?

  • I can't decline or accept Invitations on iCal

    I use i cal at work to have an idea about the things my co-workers are doing, to attend meetings, go to events etc. i use my private mac at work. When there are meetings or events i get invitations for them. this part is normal. however, for some rea

  • Export sales Scenario in OEM Manufacturing Company

    In Indai Process: Example:  Customer- MGC0001 Material No-4303673 Quantity- 5000 No Documents Required Exporting: Commercial Invoice No -1000 (Date 30/10/2007) Packing List Annexure C-1 Excise Invoice No – 1500   (Date 30/10/2007) ARE-1 No-100   (Dat

  • Uploading from backup disks, iTunes 8.2.1.6

    I uploaded smoothly from 2 of my 3 backup disks: the third would stick on one particular song which was identified and iTunes would give an error message and eject the disk, not uploading anything, and leaving me at risk of losing all the contents of