Audio device won't work correctly

I have a plug in called Real Guitar 2. It has always worked in the past but now it has vanished from my list of audio devices. It appears in my dock and It's in my applications folder. I can get it to play but when I record with it, it records all the other tracks!! It's driving me mad! Why are all the tracks bleeding into the track I'm recording on? The other strange thing is that I can't make the internal mic stop recording. I even used headphones and still the internal mic is recording!! (I also turned the monitor off) When I try to shut off the mic, the plug-in doesn't make a sound and cannot be recorded at all. What is going on? Has the company that makes the plug in turned it off? Why doesn't the computer recognize the plug-in as it always has in the past? I'm assuming that is the reason for the problem. How do I fix this? In general, why is the internal mic always ON, even when it's not being used? When I switch to "LINE IN", the plug in won't work. I'm baffled.

It was a dumb mistake! After trying many options I finally realized that I was inadvertently trying to use the plug in as a "real instrument" instead of a "software instrument". It had been several months since I used it and I guess I forgot about those little details.

Similar Messages

  • [SOLVED] Default audio device no longer works after reboot

    After today's reboot, the audio device no longer works. E.g., VLC says:
    Audio output failed:
    The audio device "default" could not be used:
    No such file or directory.
    This is the console log:
    [0x1394138] main libvlc: Running vlc with the default interface. Use 'cvlc' to use vlc without interface.
    Fontconfig warning: "/etc/fonts/conf.d/50-user.conf", line 9: reading configurations from ~/.fonts.conf is deprecated.
    [0x7fac180069c8] pulse audio output error: PulseAudio server connection failure: Connection refused
    ALSA lib pcm_dmix.c:1018:(snd_pcm_dmix_open) unable to open slave
    [0x7fac180069c8] alsa audio output error: cannot open ALSA device "default": No such file or directory
    [0x7fac180069c8] jack audio output error: failed to connect to JACK server
    [0x7fac180069c8] oss audio output error: cannot open audio device (/dev/dsp)
    [0x7fac180069c8] main audio output error: no suitable audio output module
    [0x7fac40fa4db8] main decoder error: failed to create audio output
    [0x7fac180069c8] pulse audio output error: PulseAudio server connection failure: Connection refused
    ALSA lib pcm_dmix.c:1018:(snd_pcm_dmix_open) unable to open slave
    [0x7fac180069c8] alsa audio output error: cannot open ALSA device "default": No such file or directory
    [0x7fac180069c8] jack audio output error: failed to connect to JACK server
    [0x7fac180069c8] oss audio output error: cannot open audio device (/dev/dsp)
    [0x7fac180069c8] main audio output error: no suitable audio output module
    [0x7fac41055118] main decoder error: failed to create audio output
    The strange thing is that the sound card does in fact work; e.g. the sound test for "HDA Intel PCH", the first entry in my KDE Audio Settings, works. But the entry "default" does not and I suppose that is also the device that VLC is complaining about.
    I've tried blacklisting the HDMI driver and switched to the other audio output modules in VLC. I've also checked I'm still member of the "audio" group.
    Edit:
    P.S. Solved this myself. I had a USB-to-MIDI adapter cable plugged in during boot, which seems to have been causing these problems. I suppose systemd thought it was a USB sound card? I was wondering why dmesg said something about USB sound when the computer doesn't have any USB sound devices. Hardware detection epic fail. Although I guess the cable counts as a MIDI device at least, so in a way it's correct.
    So it looks like I'll always have to unplug the MIDI cable before rebooting.
    Last edited by Morn (2012-11-23 19:24:00)

    You might get. Ore assistance in a different forum area. Maybe try Using pad. This is the forum for iPhoto for iOS.

  • Audio device is not working, i have installed proper drivers, but audio device is not working

    hi,
    I have installed registery mechanic last week and made a system run in my laptop. After re starting my laptop, my audio devices are not working fine. I have installed the drives correctly and they are reflecting in program lists, how ever the audio device is not working. If I am reinstalled the system,  My audio device is working fine, I have installed a fresh OS, but sitll its not working fine, could you help me to fix this one.

    Tecra A8
    Model No = PTA83L-04C02N
    Can you please tell me from where I need driver so that my "Fn" key will be operation? Right now I tried to use "Fn" with F6 and F7 which suppose to change screen resolutions but nothing is happening.
    Can you please tell me if I reinstall New OS (Windows XP - Sp2) then in which order which driver and Toshiba software I should install?
    Hard to find XP drivers and utilities for that machine, Manoj. But you're in luck because the Asian part-number family PTA83L corresponds to the European PTA83E.
    Go to the European download site and look up the Tecra A8 with Short Model No. PTA83E. You'll find 40 XP drivers, utilities, and BIOS updates.
    Install the Chip Set Utility first, then the Display Driver, and then the other major drivers. Install the Common Module prior to Toshiba utilities and other programs.
    Good luck!
    -Jerry

  • My audio device is not working

     hello
            I don't know the reasone behind it but my audio device is not working but I rember accedentally i uninstail my IDT audio device.

    Hello rasfunkey,
    Welcome to the HP Forums, I hope you enjoy your experience! To help you get the most out of the HP Forums I would like to direct your attention to the HP Forums Guide First Time Here? Learn How to Post and More.
    I understand that you have uninstalled your audio drivers and require assistance. I would be happy to assist you, but first I would encourage you to post your product number for your computer. I am linking an HP Support document below that will show you how to find your product number. As well, if you could indicate which operating system you are using. And whether your operating system is 32-bit or 64-bit as with this and the product number I can provide you with accurate information.
    How Do I Find My Model Number or Product Number?
    Which Windows operating system am I running?
    Is the Windows Version on My Computer 32-bit or 64-bit?
    Please re-post with the requested information and I would be happy to provide you with assistance. Thank you for posting on the HP Forums. Have a great day!
    Please click the "Thumbs Up" on the bottom right of this post to say thank you if you appreciate the support I provide!
    Also be sure to mark my post as “Accept as Solution" if you feel my post solved your issue, it will help others who face the same challenge find the same solution.
    Dunidar
    I work on behalf of HP
    Find out a bit more about me by checking out my profile!
    "Customers don’t expect you to be perfect. They do expect you to fix things when they go wrong." ~ Donald Porter

  • USB audio device is not working (code 10)

    USB audio device is not working (code 10)

    dominichristine wrote:
    USB audio device is not working (code 10)
    where do you get this error code? do you see this when you plug in
    a USB device or does it show up with out anything plugged in?

  • I recently upgrade to OS X Yosemite. Now, My M_Audio Blackbox audio interface won't work. Any suggestions?

    Recently I upgraded my OS to Yosemite 10.10.2 from Mavericks. Now, my M-Audio Black Box Audio interface won't work and I can't find it in the Logic Pro 9 software. Can someone suggest a fix? Thanks.

    Do a backup, preferably 2 separate ones on 2 separate drives.
    Revert to a Previous OS X - Yosemite
    Revert Yosemite to Mavericks
    If you do revert, I'd use Setup Assistant to restore your data. This process takes a while, so do it when you won't need the computer for several hours, based on my experience.
    If you don't have a Time Machine backup, you will need a backup of some kind.

  • Flash Pro CC Debug won't work correctly

    Hello. I am using trial version of Flash Pro CC and I think it's a glitch.
    If there are multiple layers that have own frame script and run Debut(ctrl + alt + enter ), debug won't work correctly.
    for example there are 2 layers on main stage Layer A and Layer B..
    Layer A has  this one trace script,
    trace("1");
    Layer B has those 2 trace scripts.
    trace("2");
    trace("3);
    And I put breakpoint  on trace("1"); of Layer A, and run Debug and use "Step In"  to run all scripts manually.
    And if trace("1");  is finished, you are supposed to  get to trace("2"); but instead you will get to trace("3"); in this case.
    I mean little yellow arrow, which tells me what script is running right now, is marked on trace("3");.. not on trace("2");
    It seems Flash pro CC thinks Layer A's trace("1");  == Layer B's trace("2"). He can't recognize Layer A and Layer B are different.
    I think it's a glitch. Does anybody notice this glitch?

    Does anybody notice this glitch?  I want to check if it's really a glitch or not before using newest version of Flash CC.
    If it's a glitch, I will stick with CS6.

  • Maintain Audio Pitch doesn't work correctly.

    Ok,
    After a long series of issues and tech support calls with CS4 I have a new gremlin to deal with. Maintain Audio Pitch, which previously worked great on my XP Pro with premiere Pro 2.0 now just heavily distorts the audio. This problem is on my new Vista Ultimate 64-bit power house of a computer using CS4. What actually happens, is hard to explain this accurately. Imagine talking into a tin can then add a kind of vibrato distortion and then degrade it's over all quality. What once would come out damn near perfect is now heavily unacceptably distorted. The source doesn't seem to matter. It messes up both Microsoft DV AVI audio as well as WAV files. The current issue has to do with me trying to pitch correct a file at 97% speed. That's 97%! In Pro 2.0 I could correct down to around 78% without too much distortion. This just doesn't make any since. All my drivers are updated, yes I uninstalled and reinstalled QuickTime (that's what was crashing media encoder a while back) and yes I have the update 4.0.1
    If anyone has any ideas on how to fix this, please let me know. I'm confused and have no idea how to approach this. I've done multiple searches expecting someone else to have this issue and have thus far (4+ hours in) have come up empty handed.
    Signed,
    William A. McDonald

    I'm looking at possibly buying Premiere and this feature is very important to me.  Was this problem ever corrected?

  • SB X-fi Xtreme Audio PCI-E Not working correctly help please

    Hi i have a SB X-fi Xtreme Audio PCI-E card on my pc , i have currently installed windows 7 and for months now i am trying to make the card work .. I have a poor sound especially when there is bass, the card is not detected by windows 7, its detected as a high definition audio device , when i plug my mic is not found..and i cant use the creative applications because is says its not supported or i have no creative poroducts on my pc ... I have tried all the latest drivers and stil have the same problem.. HELP PLEASE !!

    First, uninstall all creative drivers, console, from add/remove. Restart computer install: . X-Fi Xtreme Audio Series Driver .04.0000 from creative website. 2.X-Fi Xtreme Audio Pack .03.0002 from creative website. 3. install Creative Console from here: http://forums.creative.com/t5/Sound-Blaster/PAX-Console-Launcher-V-0/td-p/549970 * PAX Console, Modded Original Console, but newer then Creative) or this creative console: CSL_PCAPP_LB_2_6_09.exe ( it creative original console) With this console you will have bass, treble, etc, BUT you need to open ConsoLCu.exe from Program Files/Creative/Console Launcher. ConsoLCu.exe have all the options you need. Creative forget about thier sound board, thier drivers, bass, treble, etc, about customers. If you install thier drivers from their website you will not have BASS, and also an crappy sound. You need to install Creative Console from google, or from http://forums.creative.com/t5/Sound-Blaster/PAX-Console-Launcher-V-0/td-p/549970 to have bass, crystalizer, etc. I also have Creative Audio PCI-e board..... crappy chipset, just like Sb Li've 24 biti PCI.

  • Help on my s10: missing audio device and non working built in camera

    According to Lenovo, XP Home has a conflict with the built in camera of some S10 and they have a Bison patch to solve it. 
    I already downloaded the bison update and realtek audio driver. Still it didnt work!
    I checked the audio folder. No audio device found! What could be the problem? Checked the Device manager only bluetooth related devices were found.
    Please help. Ty!
    -Mike
    Newbie
    S10 w/6 cell battery, 160G hard disk, WindowsXP Home, etc.
    Message Edited by msdelr on 01-12-2009 05:49 PM

    brilami,
    Here is the link to the S10 support site with all applicable drivers.  
    You should be able to download theRealtek audio driver from that page.
    Best regards,
    Mark
    ThinkPads: S30, T43, X60t, X1, W700ds, IdeaPad Y710, IdeaCentre: A300, IdeaPad K1
    Mark Hopkins
    Program Manager, Lenovo Social Media (Services)
    twitter @lenovoforums
    English Community   Deutsche Community   Comunidad en Español   Русскоязычное Сообщество

  • Spry Menu Bar won't work correctly.

    This is an image of what the overall menu bar layout should be like-all of the links and sublinks.
    I have a few problems that I am having all relating to the spry menu bar.
    I ran my code through w3c validation service but it came up with alot of errors which when corrected didn't make sense or work either.
    I made this menu bar in a widget called spry menu bar 2.0.  I then edited it to place in the correct names and it doesn't work correctly and the w3c validation code seems to have 43 errors with the spry bar. I am been over it a dozen times and I can't seem to figure it out.  Here is the code.
    Also, have I made the links correctly?
    I would appreciate any help you could offer! thank you
    Dreamweaver cs 5.5
    <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
    <html xmlns="http://www.w3.org/1999/xhtml">
    <head>
    <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
    <!-- TemplateBeginEditable name="doctitle" -->
    <title>Untitled Document</title>
    <!-- TemplateEndEditable -->
    <!-- TemplateBeginEditable name="head" -->
    <!-- TemplateEndEditable -->
    <style type="text/css">
    #container {
        width: 1000px;
    #header {
        width: 1000px;
    </style>
    <link href="../Stylesheet_Unicorn_main_layout_template.css" rel="stylesheet" type="text/css" />
    <link href="../Spry-UI-1.7/css/Menu/basic/SpryMenuBasic.css" rel="stylesheet" type="text/css" />
    <script src="../Spry-UI-1.7/includes/SpryDOMUtils.js" type="text/javascript"></script>
    <script src="../Spry-UI-1.7/includes/SpryDOMEffects.js" type="text/javascript"></script>
    <script src="../Spry-UI-1.7/includes/SpryWidget.js" type="text/javascript"></script>
    <script src="../Spry-UI-1.7/includes/SpryMenu.js" type="text/javascript"></script>
    <script src="../Spry-UI-1.7/includes/plugins/MenuBar2/SpryMenuBarKeyNavigationPlugin.js" type="text/javascript"></script>
    <script src="../Spry-UI-1.7/includes/plugins/MenuBar2/SpryMenuBarIEWorkaroundsPlugin.js" type="text/javascript"></script>
    <style type="text/css">
    /* BeginOAWidget_Instance_2141544: #MenuBar */
    /* Settable values for skinning a Basic menu via presets. If presets are not sufficient, most skinning should be done in
        these rules, with the exception of the images used for down or right pointing arrows, which are in the file SpryMenuBasic.css
         These assume the following widget classes for menu layout (set in a preset)
        .MenuBar - Applies to all menubars - default is horizontal bar, all submenus are vertical - 2nd level subs and beyond are pull-right.
        .MenuBarVertical - vertical main bar; all submenus are pull-right.
        You can also pass in extra classnames to set your desired top level menu bar layout. Normally, these are set by using a preset.
        They only apply to horizontal menu bars:
            MenuBarLeftShrink - The menu bar will be horizontally 'shrinkwrapped' to be just large enough to hold its items, and left aligned
            MenuBarRightShrink - Just like MenuBarLeftShrink, but right aligned
            MenuBarFixedLeft - Fixed at a specified width set in the rule '.MenuBarFixedLeft', and left aligned. 
            MenuBarFixedCentered -  - Fixed at a specified width set in the rule '.MenuBarFixedCentered',
                            and centered in its parent container.
            MenuBarFullwidth - Grows to fill its parent container width.
        In general, all rules specified in this file are prefixed by #MenuBar so they only apply to instances of the widget inserted along
        with the rules. This permits use of multiple MenuBarBasic widgets on the same page with different layouts. Because of IE6 limitations,
        there are a few rules where this was not possible. Those rules are so noted in comments.
    #MenuBar  {
        background-color:#000000;   
        font-family: "Comic Sans MS", cursive; /* Specify fonts on on MenuBar and subMenu MenuItemContainer, so MenuItemContainer,
                                                    MenuItem, and MenuItemLabel
                                                    at a given level all use same definition for ems.
                                                    Note that this means the size is also inherited to child submenus,
                                                    so use caution in using relative sizes other than
                                                    100% on submenu fonts. */
        font-weight: normal;
        font-size: 18px;
        font-style: normal;
        padding:0;   
        border-color: #ffffff #ffffff #ffffff #ffffff;
        border-width:0px;
        border-style: none none none none;
    /* Caution: because ID+class selectors do not work properly in IE6, but we want to restrict these rules to just this
    widget instance, we have used string-concatenated classnames for our selectors for the layout type of the menubar
    in this section. These have very low specificity, so be careful not to accidentally override them. */
    .MenuBar br { /* using just a class so it has same specificity as the ".MenuBarFixedCentered br" rule bleow */
        display:none;
    .MenuBarLeftShrink {
        float: left; /* shrink to content, as well as float the MenuBar */
        width: auto;
    .MenuBarRightShrink {
        float: right; /* shrink to content, as well as float the MenuBar */
        width: auto;
    .MenuBarFixedLeft {
        float: left;
        width: 80em;
    .MenuBarFixedCentered {
        float: none;
        width: 80em;
        margin-left:auto;
        margin-right:auto;
    .MenuBarFixedCentered br {
        clear:both;
        display:block;
    .MenuBarFixedCentered .SubMenu br {
        display:none;
    .MenuBarFullwidth {
        float: left;
        width: 100%;
    /* Top level menubar items - these actually apply to all items, and get overridden for 1st or successive level submenus */
    #MenuBar  .MenuItemContainer {
        padding: 0px 0px 0px 0px;
        margin: 0;     /* Zero out margin  on the item containers. The MenuItem is the active hover area.
                    For most items, we have to do top or bottom padding or borders only on the MenuItem
                    or a child so we keep the entire submenu tiled with items.
                    Setting this to 0 avoids "dead spots" for hovering. */
    #MenuBar  .MenuItem {
        padding: 0px 10px 0px 0px;
        background-color:#000000;   
        border-width:1px;
        border-color: #cccccc #ffffff #cccccc #ffffff;
        border-style: none solid none solid;
    #MenuBar  .MenuItemFirst {
        border-style: none none none none;
    #MenuBar .MenuItemLast {
        border-style: none solid none none;
    #MenuBar  .MenuItem  .MenuItemLabel{
        text-align:left;
        line-height:1.4em;
        color:#ff00ff;
        background-color:#000000;
        padding: 3px 3px 3px 3px;
        width: 10em;
        width:auto;
    .SpryIsIE6 #MenuBar  .MenuItem  .MenuItemLabel{
        width:1em; /* Equivalent to min-width in modern browsers */
    /* First level submenu items */
    #MenuBar .SubMenu  .MenuItem {
        font-family: Arial, Helvetica, sans-serif;
        font-weight: normal;
        font-size: 16px;
        font-style: normal;
        background-color:#000000;
        padding:0px 2px 0px 0px;
        border-width:1px;
        border-color: #cccccc #cccccc #cccccc #cccccc;
        /* Border styles are overriden by first and last items */
        border-style: solid solid none solid;
    #MenuBar  .SubMenu .MenuItemFirst {
        border-style: solid solid none solid;
    #MenuBar  .SubMenu .MenuItemFirst .MenuItemLabel{
        padding-top: 6px;
    #MenuBar .SubMenu .MenuItemLast {
        border-style: solid solid solid solid;
    #MenuBar .SubMenu .MenuItemLast .MenuItemLabel{
        padding-bottom: 6px;
    #MenuBar .SubMenu .MenuItem .MenuItemLabel{
        text-align:left;
        line-height:1em;   
        background-color:#000033;
        color:#ff00ff;
        padding: 6px 12px 6px 5px;
        width: 7em;
    /* Hover states for containers, items and labels */
    #MenuBar .MenuItemHover {
        background-color: #999999;
        border-color: #cccccc #cccccc #cccccc #cccccc;
    #MenuBar .MenuItemWithSubMenu.MenuItemHover .MenuItemLabel{
        background-color: #999999; /* consider exposing this prop separately*/
        color: #ff0000;
    #MenuBar .MenuItemHover .MenuItemLabel{
        background-color: #999999;
        color: #ff0000;
    #MenuBar .SubMenu .MenuItemHover {
        background-color: #cccccc;
        border-color: #cccccc #cccccc #cccccc #cccccc;
    #MenuBar .SubMenu .MenuItemHover .MenuItemLabel{
        background-color: #cccccc;
        color: #ff0000;
    /* Submenu properties -- First level of submenus */
    #MenuBar .SubMenuVisible {
        background-color: #000000;
        min-width:0%;  /* This keeps the menu from being skinnier than the parent MenuItemContainer - nice to have but not available on ie6 */
        border-color: #ffffff #ffffff #ffffff #ffffff;
        border-width:0px;
        border-style: none none none none;
    #MenuBar.MenuBar .SubMenuVisible {/* For Horizontal menubar only */
        top: 100%;    /* 100% is at the bottom of parent menuItemContainer */
        left:0px; /* 'left' may need tuning depending upon borders or padding applied to menubar MenuItemContainer or MenuItem,
                        and your personal taste.
                        0px will left align the dropdown with the content area of the MenuItemContainer. Assuming you keep the margins 0
                        on MenuItemContainer and MenuItem on the parent
                        menubar, making this equal the sum of the MenuItemContainer &amp; MenuItem padding-left will align
                        the dropdown with the left of the menu item label.*/
        z-index:10;
    #MenuBar.MenuBarVertical .SubMenuVisible {
        top: 0px;   
        left:100%;
        min-width:0px; /* Do not neeed to match width to parent MenuItemContainer - items will prevent total collapse */
    /* Submenu properties -- Second level submenu and beyond - these are visible descendents of .MenuLevel1 */
    #MenuBar .MenuLevel1 .SubMenuVisible {
        background-color: #000000;
        min-width:0px; /* Do not neeed to match width to parent MenuItemContainer - items will prevent total collapse*/
        top: 0px;    /* If desired, you can move this down a smidge to separate top item''s submenu from menubar -
                    that is really only needed for submenu on first item of MenuLevel1, or you can make it negative to make submenu more
                    vertically 'centered' on its invoking item */
        left:100%; /* If you want to shift the submenu left to partially cover its invoking item, you can add a margin-left with a
                    negative value to this rule. Alternatively, if you use fixed-width items, you can change this left value
                    to use px or ems to get the offset you want. */
    /* IE6 rules - you can delete these if you do not want to support IE6 */
    /* A note about multiple classes in IE6.
    * Some of the rules above use multiple class names on an element for selection, such as "hover" (MenuItemHover) and "has a subMenu" (MenuItemWithSubMenu),
    * giving the selector '.MenuItemWithSubMenu.MenuItemHover'.
    * Unfortunately IE6 does not support using mutiple classnames in a selector for an element. For a selector such as '.foo.bar.baz', IE6 ignores
    * all but the final classname (here, '.baz'), and sets the specificity accordingly, counting just one of those classs as significant. To get around this
    * problem, we use the plugin in SpryMenuBarIEWorkaroundsPlugin.js to generate compound classnames for IE6, such as 'MenuItemWithSubMenuHover'.
    * Since there are a lot of these needed, the plugin does not generate the extra classes for modern browsers, and we use the CSS2 style mutltiple class
    * syntax for that. Since IE6 both applies rules where
    * it should not, and gets the specificity wrong too, we have to order rules carefully, so the rule misapplied in IE6 can be overridden.
    * So, we put the multiple class rule first. IE6 will mistakenly apply this rule.  We follow this with the single-class rule that it would
    * mistakenly override, making sure the  misinterpreted IE6 specificity is the same as the single-class selector, so the latter wins.
    * We then create a copy of the multiple class rule, adding a '.SpryIsIE6' class as context, and making sure the specificity for
    * the selector is high enough to beat the single-class rule in the "both classes match" case. We place the IE6 rule at the end of the
    * css style block to make it easy to delete if you want to drop IE6 support.
    * If you decide you do not need IE6 support, you can get rid of these, as well as the inclusion of the SpryMenuBarIEWorkaroundsPlugin.js script.
    * The 'SpryIsIE6' class is placed on the HTML element by  the script in SpryMenuBarIEWorkaroundsPlugin.js if the browser is Internet Explorer 6. This avoids the necessity of IE conditional comments for these rules.
    .SpryIsIE6 #MenuBar .MenuBarView .MenuItemWithSubMenuHover .MenuItemLabel /* IE6 selector  */{
        background-color: #999999; /* consider exposing this prop separately*/
        color: #ff0000;
    .SpryIsIE6 #MenuBar .MenuBarView .SubMenu .MenuItemWithSubMenuHover .MenuItemLabel/* IE6 selector  */{
        background-color: #cccccc; /* consider exposing this prop separately*/
        color: #ff0000;
    .SpryIsIE6 #MenuBar .SubMenu .SubMenu  /* IE6 selector  */{
        margin-left: -0px; /* Compensates for at least part of an IE6 "double padding" version of the "double margin" bug */
    /* EndOAWidget_Instance_2141544 */
    </style>
    <script type="text/xml">
    <!--
    <oa:widgets>
      <oa:widget wid="2141544" binding="#MenuBar" />
    </oa:widgets>
    -->
    </script>
    </head>
    <body>
    <div id="container"><!-- TemplateBeginEditable name="header_editable" -->
      <div id="header">Unicorn Writers Conference</div>
    <!-- TemplateEndEditable -->
      <div id="menubar_left">
        <ul id="MenuBar">
          <li> <a href= "../Pages/home.html">Home</a></li>
          <li> <a href="#">Events</a>
          <li> <a href="#">Mission Statement</a>
          <li> <a href="#">Resources</a>
            <ul>
              <li> <a href="#">Advanced networking</a></li>
              <li> <a href="#">Query Review</a>
              <li> <a href="#">Ms Review Sessions</a>
              <li> <a href="#">1-1 Sessions</a>
              <li> <a href="#">Workshops</a>
              <li> <a href="#">Genre Chart</a>
              <li> <a href="#">Writers Links</a>
                   </ul></li>
                      <li> <a href="#">Key Presenters</a>
                          <ul>
                            <li> <a href="#">Speakers</a>
                                <ul>
                                    <li> <a href="../Pages/2013_speakers_page.html">Speakers 2013</a></li>
                                    <li> <a href="#">Speakers 2012</a>
                                </ul>
                            <li> <a href="#">Editors</a>
                                <ul>
                                    <li> <a href="#">Editors 2013</a></li>
                                    <li> <a href="../Pages/2012_editors.html">Editors 2012</a>
                                </ul>
                            <li> <a href="#">Literary Agents</a>
                                <ul>
                                    <li> <a href="../Pages/2013_L_agents.html">Literary Agents 2013</a></li>
                                    <li> <a href="../Pages/2012_editors.html">Literary Agents 2012</a>
                              </ul>
                         </ul>
                      <li> <a href="#">Information</a>
                          <ul>
                            <li> <a href="#">St. Clements</a></li>
                            <li> <a href="#">Directions</a></li>
                            <li> <a href="#">Hotels</a></li>
                            <li> <a href="#">Menu</a></li>
                            <li> <a href="#">Unicorn Photo Gallery</a></li>
                            <li> <a href="#">Day Schedule</a></li>
                            <li> <a href="#">FAQ</a></li>
                            <li> <a href="#">Staff</a></li>
                            <li> <a href="#">Contact</a></li>
                          </ul>
                      <li> <a href="#">Registration</a></li>
                      <li> <a href="#">Acclaim</a>
                          <ul>
                              <li> <a href="#">Spotlights</a></li>
                              <li> <a href="#">Testamonials</a>
                            <li> <a href="#">Sponsorship</a>
                        </ul>   
                      <li> <a href="#">Classifieds</a>
                          <ul>
                            <li> <a href="#">View</a></li>
                            <li> <a href="#">Place</a></li>
                        </ul>
                      <li> <li> <a href="#">Merchandise</a></li>
                    </ul>
                  </li>
              </li>
            </ul>
          </li>
        </ul>
        <script type="text/javascript">
    // BeginOAWidget_Instance_2141544: #MenuBar
    var MenuBar = new Spry.Widget.MenuBar2("#MenuBar", {
          widgetID: "MenuBar",
          widgetClass: "MenuBar MenuBarVertical MenuBarMenuBarVerticalLeftShrink",
          insertMenuBarBreak: true,
          mainMenuShowDelay: 100,
          mainMenuHideDelay: 200,
          subMenuShowDelay: 200,
          subMenuHideDelay: 200
    // EndOAWidget_Instance_2141544
        </script>
      </div>
      <!-- TemplateBeginEditable name="main_content_editable" -->
      <div id="main_content">Content for New Div Tag Goes Here</div>
      <!-- TemplateEndEditable --></div>
    <div id="footer">Content for  id "footer" Goes Here</div>
    </body>
    </html>

    These Spry support files are all 404 Not found on server.
    <link href="../Spry-UI-1.7/css/Menu/basic/SpryMenuBasic.css" rel="stylesheet" type="text/css" />
    <script src="../Spry-UI-1.7/includes/SpryDOMUtils.js" type="text/javascript"></script>
    <script src="../Spry-UI-1.7/includes/SpryDOMEffects.js" type="text/javascript"></script>
    <script src="../Spry-UI-1.7/includes/SpryWidget.js" type="text/javascript"></script>
    <script src="../Spry-UI-1.7/includes/SpryMenu.js" type="text/javascript"></script>
    <script src="../Spry-UI-1.7/includes/plugins/MenuBar2/SpryMenuBarKeyNavigationPlugin.js" type="text/javascript"></script>
    <script src="../Spry-UI-1.7/includes/plugins/MenuBar2/SpryMenuBarIEWorkaroundsPlugin.js" type="text/javascript"></script>
    Nancy O.

  • My home button won't work correctly after I plug the charger in

    My iPhone 5s's home button doesn't respond correctly after i plug in the charger. I'm not sure what's wrong.
    At first, it wouldn't charge so i had to find a different charger that i had ordered from amazon (not from apple) and it only worked when i plugged it in with one side. the other chargers that i have from apple do not work. the home button sometimes works correctly, but im sure that it starts to not respond correctly after i plug the charger in. i have tried almost everything i could find on the internet. im not sure if its a hardware or software problem. please help. thank you

    Sorry but I'm not clear. Do you have more than one charger from Amazon? Did this problem start after you used the charger(s) you got from Amazon and now using the Apple brand chargers it doesn't work either? I'm wondering if the Amazon charger damaged the phone.

  • F7 and F8 Keyboard shortcuts won't work correctly.

    I've just recently installed LR3.6 and it's my first experience with LR.  I've been following Lynda.com tutorials and all of a sudden the F7 and F8 function keys won't work.
    The F7 just does nothing and the F8 opens iTunes every time I press it.  I've tried everthing I know (not being much of a Techie) without success.  I installed one upgrade download since I installed the original CD software. Should I just delete the program and re-install the program?  I believe the F-keys were woking originally.  I'm sorry, but I was going thru the tutorials and not being as observant as I should.  All I know for certain is that they do not work now.
    I'm using an iMac 27 with the wireless keyboard. OSX 10.6.8.
    Thanks for any help. - John, Vancouver, WA

    Yes: why not post in the apropriate Photoshop forum, which you can find here?
    http://forums.adobe.com/community/photoshop
    This is the Acrobat Macintosh forum.

  • Aggregate Audio Devices Don't Work

    Hi,
    I'm trying to create an aggregate audio device from my Macbook's on-board audio devices. The device does not appear in any application, including sound preferences, AU lab, and Jackpilot.

    I, too, am having this problem with two MOTU firewire devices (828mkII and Traveler). The article referred to simply walks one through the steps to create an aggregate device in the Audio MIDI Setup. I have done this, but the aggregate device still does not appear in the Sound pane of System Preferences OR Logic Pro. If I close the Audio MIDI Setup application and restart it, the aggregate device is gone!
    This is more than just a "how to set up an aggregate device" problem. Any ideas about what's happening or how to fix it? I've tried re-installing drivers, resetting devices to factory defaults, rebooting, etc. Nothing seems to help. I'm about ready to wipe out my hard drive and install everything from scratch…

  • 1.3G left on comp hardd-is that why fcp won't work correctly

    Ok. I'm at work and My bosses G5 only has 1.3 of space left on it. I save all of my projects( scratch disks, etc to another hard drive) but when I try to play my sequences back it will get stuck, freeze frame, not play properly. Is it because there is too little disk space on the comp harddrive to work correctly? It seems like it's working really hard and has quit on me quite a few times. My external harddrive has 33G left on it. Help!

    JenL,
    Anything less than 10% free space on any hard drive and you're going to start experiencing slowdowns.
    The fuller (?) a hard drive gets, the more work the operating system has to do to write new information to disk, and the more spaced out the files its writing to disk have to be. When a file is split up over a larger area of the disk, it takes the operating system longer to read the whole file later on when it wants to.
    I would clean up some space on the system drive and try again.

Maybe you are looking for

  • 500 Internal Server Error running SRList.jsp from ADFBC_tutorial (OTN)

    Hello! I am running through the JDeveloper totorial (ADFBC_tutorial) posted on OTN. I have gone as far as Chapter 5 but when I run the SRList.jsp page, I get the 500 Internal Server Error: I have had no issues running through the tutorial in the desi

  • Washed out Color in Mountain Lion

    Has anybody else noticed, after upgrading to Mountain Lion, that an exported slice from Fireworks (CS5 in my case) is very washed out, with colors much less saturated? It is driving me crazy, I'm having to workaround by taking screenshots of my work

  • Installing CS3 as a demo

    Can I use the real Install DVDs for Creative Suite Standard (CS3) to run as a 30day demo. Or do I have to download a special demo dmg? I've just got a new intel mac so would like to do this until I can upgrade a different license CS2 to CS3 with a fr

  • Why is my question deleted?

    Hi , I have only one profile and posted the question on ALV caming back problem? Why did I get a message like this ? Double posting under different user ID's => Thread locked and marked for deletion. Thanks, Manjula.S

  • OCompany.Connect Error

    Hello! I trying connect to Company but "Connect" methot return code -> 107 All Company parametrs are correct (dbUser, dbPassword, dbType...) -107: SQL statement not allowed for this instance SQL statement not allowed for this instance Please tell me