Interrupt handler

hi all,
i want to model an interrupt handler
i have a class that is working it's job and when it receive the interruption it should cancel it's job and execute the interrupt handler

You could add a wrapper to you job e.g.
final Callable job = ...
Callable called = new Callable () {
   public Object call() {
       try {
           return job.call();
       } catch (InterruptedException ie) {
           // handle interrupt.
};

Similar Messages

  • Solaris 8 (INTEL) - Interrupt handler

    We are developing a device driver for a PCI card. The interrupt level assigned is 10 and the priority level is 6.
    In the interrupt handler, we first check whether our device has generated the interrupt and if not return with DDI_INTR_UNCLAIMED otherwise we proceed to clear the interrupt status and do the appropriate action and return DDI_INTR_CLAIMED.
    we have observed that while returning from the Interrupt handler, the control is going into a function "LOOP2", and our interrupt handler is invoked again from "LOOP2" and this goes into a loop. ( We use kadb to debug ).
    Kindly clarify.

    Hi!
    I also had the same exact problem during the install. The only way that I could procede was to tell it that I didn't want to install networking. Now when I boot, it tries to load the elx0 driver (for my 3Com 3c509b) and brings the following message, "SIOCSLIFFFLAGS cannot assigm requested address." I have checked the Irq/IO setting in the hardware configuration agent and everything seems to be correct. To top it all off, once I logon if I enter "ifconfig elx0 192.168.1.2 up" then everything works fine. I tried to forceload the elx0 module in /etc/system to see if the module just wasn't loaded early enough but this did not help. Any ideas of what else I should check?
    TIA

  • High-level interrupt handler

    Why can I decide to support a high-level interrupt or not? Under what condition does the Solaris kernel will map my hw interrupt (INTA from PCI bus) to a high-level interrupt? When should I refuse to support a high-level interrupt? Why? Can I force my hw interrupt to be a high- level interrupt?
    Also think about that, most hw interrupts indicate something important such as the case buffers are full. If they are assigned below the scheduler's, it really does not make sense.
    Is it possible to block any hw interrupts? Or I'd put it this way can I prioritize hw interrupts in Solaris?
    Thanks
    tyh

    Hi,
    On x86 each IRQ has a software priority assigned to it implicitly by the bus driver, although I think you could override it in the driver.conf. Unlike SPARC, the processor doesn't support a PIL so software priorities are implemented by masking all lower-priority IRQs and re-enabling interrupts.
    High priority interrupts, above dispatcher level, run in the context of the current thread on the cpu, normal level interrupts are handled by interrupt threads.
    The interrupt threads are the highest priority threads on the system, so will preempt any other running threads. In addition mutexes in Solaris use priority inheritance, so the interrupt threads will get to run.
    In general, high level interrupts are allocated to devices with small buffers such as serial or floppy, so that their buffers get serviced in the fastest possible time. Others can afford to wait for just a bit.
    Your driver should check to see if its device has been allocated a high level interrupt. If this is the case, the high level handler should clear the interrupt and save the data/status (in the driver state structure perhaps) and trigger your soft level interrupt handler (which will run as a thread).
    Blocking of interrupts is done for you when you acquire a spin mutex (ie initialised with an iblock cookie). Such a mutex is required to synchronise access to data shared with a high level handler in your driver.
    Please take a look at the Intel Driver writers orientation at:
    http://soldc.sun.com/developer/support/driver/docs/Solaris_driver_models/index.html
    Hope that helps,
    Ralph
    SUN DTS

  • Interrupt Handling

    My problem is that I am using a third party API provided by a Vendor in order to access their DAM (Digital Asset Management) system. This API is used by a Swing application. I provide the user with a way to interrupt long running operations, but sometimes, if the interrupt is fired when the API code is executing, the interrupts get swallowed up and then I am unable to stop the thread.
    Any suggestions for working around this problem?
    If I were to paraphrase the question: What is the best way to catch interrupts if making calls to third party code that does not implement interrupt handling properly?

    Don't know nothing great comes to mind. Only other thing I think you could try is thread.kill

  • Kernel BUG at skbuff.c.... In interrupt handler - not syncing

    Hello,
    VERSION: ZENWorks Imaging Server v6.50
    I am trying to create an image of a workstation. After I boot up with the
    Boot CD and input the proper settings (prompts by SETTINGS.TXT) the
    workstation gets an IP and everything works fine. At the moment when I try
    to create the image:
    img mp <IP address of imaging server> <//path/imagefilename>
    I get the following error:
    ~~~~~~~~~~~~
    Kernel BUG at skbuff.c :92!
    invalid operand: 0000
    <0> Kernel panic: Aiee, killing interrupt handler!
    In interrupt handler - not syncing
    ~~~~~~~~~~~~~
    The error is much bigger, but I only included the first two and last two
    lines of it.
    I am not sure how to resolve this. If I made a mistake with the commands
    please let me know, although I think they are correct. I also tried
    creating an image through the user interface but I got the same error.
    Any solution, recommendation, or advice is greatly appreciated.
    Sincerely,
    Steve O.

    Marcus,
    Thank you for the response.
    Sorry to ask again, I am new to Novell. I simply want to make sure. Do you
    mean downloading and installing the following patch for ZENWorks 6.5
    desktop management?
    zen65sp2.exe
    I found this file from the "Download - patches" website.
    Thanks for the help.
    Steve O.
    > [email protected] wrote:
    >
    > > I am not sure how to resolve this. If I made a mistake with the commands
    > > please let me know, although I think they are correct. I also tried
    > > creating an image through the user interface but I got the same error.
    > >
    > try the iso from sp2..
    > --
    > If you have already compiled drivers or have linux.2 please put them on
    > http://forge.novell.com/modules/xfmo...ect/?zfdimgdrv
    > Live BootCd and USB Disk from Mike Charles
    > http://forge.novell.com/modules/xfmod/project/?imagingx
    > eZie http://forge.novell.com/modules/xfmod/project/?ezie
    >
    > Marcus Breiden
    >
    > If you are asked to email me information please change -- to - in my e-mail
    > address.
    > The content of this mail is my private and personal opinion.
    > http://www.edu-magic.net

  • Labview Interrupt Handler

    Hi folks,
    I am doing a project using labview to capture some signal timing with
    DIO. Does there anybody have this experience can share with me? Where
    can I get the labview interrupt handler program code example?
    Thanks,
    Johnson

    I have two years experience with LabVIEW and twelve years experience
    with control and data acquisition. I guess, it's a wrong way to
    "capture some signal timing with DIO". It's too unreliable and it not
    ensures any reasonable precision. Think about using general purpose
    counters. Almost all DAQ board includes this hardware. They are
    dedicated to implement such a tasks.
    Yevgeni Tunik
    In article <[email protected]>,
    Johnson wrote:
    > Hi folks,
    > I am doing a project using labview to capture some signal timing with
    > DIO. Does there anybody have this experience can share with me? Where
    > can I get the labview interrupt handler program code example?
    > Thanks,
    > Johnson
    >
    >
    Sent via Deja.com http://www.deja.com/
    Share what you
    know. Learn what you don't.

  • Interruption handling in Flashlite

    Hi
    I am new to flash lite. I am basically more on the j2me side in j2me application we have options like hidenotify shownotify for handling event like call interruption and we can pause the game. In flashlite I think the application will get automatically paused. I want to know know we can implement something like this so that i can implement a pause menu. For example I have a game which on receiving a call interruption or any other action will move the flashlite application to background. On resuming the game i need to show the pause menu is it possible to detect these device events

    Hi,
    FL does not support such event reporting via API.
    You can use the following trick, but please not i have not tested it yet. Its just my theory
    Use the getTimer() function to save the time on regular intervals. Then when application is returned by FL from call event or menu navigation. Check the getInterval returned time difference is more than your application normally have.
    If the difference is more than regular, your application has just got back focus.
    The other way is to use PyS60 and listen for call events / application switching. It have API for these. And you can communicate with a PyS60 script to check for these events.
    Hope this is helpfull.
    FL is difficult and tricky world
    // chall3ng3r //

  • Changes in VISA interrupt handling?

    Hello all,
    I'm grasping at straws here, so I'm looking for a shoulder to cry on.
    I wrote a USB acquisition prog with CVI a decade ago for a custom board. It worked fine for a few years and then was turned off. We are trying to use it again but it's not working properly.
    We don't have the original PC, so we are using it with the lastest CVI on Win7 or XP, with latest VISA driver (regenerated .inf file).
    Communication with USB works fine... except for the interrupt routine. Instead of receiving one interrupt with 3 bytes of data (say 'ABC'), I receive TWO interrupts, the first with 0x1, the 2nd one with 'BC'. There are different types of interrupt frames of different lengths, all have the same split in two, with the 1st as 0x1, the 2nd with valid data.
    Anybody has any idea why there could be such a change in the way my interrupt routine works ?Has VISA changed its handling of interrupts in this time period ?
    Short of a PC-side solution we are ready to reflash the card, hoping that we have the most recent version of the firmware !!!
    If it can be useful, here's a dump of USB VISA parameters (I'm not familiar with most of them):
    VI_ATTR_RSRC_IMPL_VERSION: 0x500400
    VI_ATTR_RSRC_SPEC_VERSION: 0x500100
    VI_ATTR_RSRC_MANF_ID: 4086
    VI_ATTR_RSRC_MANF_NAME: National Instruments
    VI_ATTR_INTF_TYPE: 7
    VI_ATTR_INTF_NUM: 0
    VI_ATTR_INTF_PARENT_NUM error: L'attribut spécifié n'est pas défini ou supporté par la ressource référencée.
    VI_ATTR_INTF_INST_NAME: USB0
    VI_ATTR_MAX_QUEUE_LENGTH: 50
    VI_ATTR_RSRC_LOCK_STATE: 0
    VI_ATTR_RSRC_CLASS: RAW
    VI_ATTR_DMA_ALLOW_EN error: L'attribut spécifié n'est pas défini ou supporté par la ressource référencée.
    VI_ATTR_TMO_VALUE: 2000
    VI_ATTR_TRIG_ID error: L'attribut spécifié n'est pas défini ou supporté par la ressource référencée.
    VI_ATTR_IO_PROT: 1
    VI_ATTR_TERMCHAR: 10
    VI_ATTR_TERMCHAR_EN: 0
    VI_ATTR_SEND_END_EN error: L'attribut spécifié n'est pas défini ou supporté par la ressource référencée.
    VI_ATTR_SUPPRESS_END_EN: 0
    VI_ATTR_RD_BUF_OPER_MODE: 3
    VI_ATTR_WR_BUF_OPER_MODE: 2
    VI_ATTR_RD_BUF_SIZE: 4096
    VI_ATTR_WR_BUF_SIZE: 4096
    VI_ATTR_USB_SERIAL_NUM: 1240332
    VI_ATTR_USB_INTFC_NUM: 0
    VI_ATTR_USB_PROTOCOL: 0
    VI_ATTR_USB_MAX_INTR_SIZE: 64
    VI_ATTR_USB_CLASS: 0
    VI_ATTR_USB_SUBCLASS: 0
    VI_ATTR_USB_ALT_SETTING: 0
    VI_ATTR_USB_NUM_INTFCS: 1
    VI_ATTR_USB_NUM_PIPES: 2
    VI_ATTR_USB_CTRL_PIPE: 0
    VI_ATTR_USB_BULK_OUT_PIPE: 1
    VI_ATTR_USB_BULK_IN_PIPE: -1
    VI_ATTR_USB_INTR_IN_PIPE: 129
    VI_ATTR_USB_BULK_OUT_STATUS: 0
    VI_ATTR_USB_BULK_IN_STATUS error: La référence d'objet spécifiée n'est pas initialisée.
    VI_ATTR_USB_INTR_IN_STATUS: 1
    VI_ATTR_USB_END_IN: 5
    Solved!
    Go to Solution.

    Hi,
    I have a few questions that may help clarify the problem:
    1. What Operating System were you originally using?
    2. What version of CVI and VISA was originally used when this was working?
    3. If you revert back to the old machine/system, do you recieve the same error?
    It sounds like it could be a firmware issue. Another thought, since this is a custom device, it is possible that it was using a USB RAW Driver, which supports Bulk, Interrupt, and Control communication protocols. I have included some general information about USB instrument Control below, including the required changes for setting the communication protocols for USB RAW.
    http://www.ni.com/white-paper/4478/en/
    I would recommend reading through this. Best of luck!
    R. Brill
    Applications Engineer
    National Instruments

  • VISA Event / Interrupt Handler

    I have a VXI chassis with a MXI controller card in slot 0.  I have connected MXI controller card to a dell computer with a MXI-2 PCI card in it.  I am running RHEL4. I am able to get the comparator card to generate a trigger on TTLTRIG0 line (VXI P2 pin 23 RowA).  I have verified via an oscope that the TTLTRIG0 line goes low for approx 2us.  So I believe I am generating the trigger correctly.
    I want my C program using VISA to call my handler when the TTLTRIG0 lines goes low.  I am using the following program AsyncTrig.c as a guide. http://zone.ni.com/devzone/cda/epd/p/id/1935
    But the C code handler routine never gets called.  Is there something I am missing?  MXI controller board setup? PCI card setup?  Do I need to use IRQ lines instead of TRIG lines?
    Any info / help would be greatly appreciated.

    Hi,
    It sounds like you are generating the trigger correctly in the code.  There should not be anything you have to change on the hardware to send/receive the trigger.
    Have you tried using a different trigger line besides 0? Triggers 0-7 should be available to use on your system.
    What version of Linux kernel build are you running? 
    Are you using ECL, TTL, synchronous, or asynchronous for triggering?
    Also attached below are several articles that discuss VXI triggering in more detail.
    VXI Trigger Tutorial
    Triggering with NI-VXI
    Regards,
    Andy L.
    Applications Engineer
    National Instruments

  • How do I determine the interrupt detection sequences for an HP 82350A PCI GPIB card?

    I am trying to install an HP 82350A PCI GPIB card in CentOS 6.4. I have installed NI-VISA 5.4.
    I tinkered around and found driverwizard in /usr/local/bin. It creates an ini file to control the PCI GPIB card.
    I had somehow succeeded in detecting the card (PXI3::0::INSTR). My driverwizard output looks like this
    [Module]
    ModuleName = "PLX PCI <-> IOBus Bridge"
    ModuleVendor = "PLX Technology, Inc."
    ModelCode = 0x9050
    ManufCode = 0x10B5
    SubsystemModelCode = 0x10B0
    SubsystemManufCode = 0x103C
    VISARegistration = Simple
    As you can see, it does not have interrupt handling built into it, so I cannot access it properly.
    How do I set up interrupt handling for this card? What are the specifications for the following fields?
    Interrupt Detection:
    Access Type
    Access Width
    Address Space
    Space Offset
    Compare Mask
    Write/Compare Value
    Interrupt Removal:
    Access Type
    Access Width
    Address Space
    Space Offset
    Compare Mask
    Write/Compare Value
    Interrupt Disarm:
    Access Type
    Access Width
    Address Space
    Space Offset
    Compare Mask
    Write/Compare Value
    This is the first time I have tried hacking at the PCI interrupt level. At the very least, how do I find out the values for the above parameters? Or at best, straight away what are the values for those parameters?

    Their IO Libraries Suite supports only Windows. Our lab probably used Windows before. This 82350A card is quite ancient. I need to use this because we also have ancient instruments that do not have Ethernet.

  • How to generate an interrupt using DI change detection on m-series card

    Hi,
    I want to generate an interrupt on the positive edge of a digital input signal on the IO connector.
    Does anybody know how to configure an m-series card (PXI-6224) for this use through RLP programming?
    Thanks in advance,
    Richard

    Richard vl wrote:
    I want to generate an interrupt on the positive edge of a digital input signal on the IO connector.
    Does anybody know how to configure an m-series card (PXI-6224) for this use through RLP programming?
    RuthC wrote:
    I also want to generate an external interrupt on an M- series pci-6229, and on a pci-6602.
    1. Is there an exampe how to configure the registers?
    2. which external signals can genarate interrupts on those cards?
    Hi Richard, hi Ruth,
    Let me address your questions together: first for 662x (part of M Series) digital change detection and then for 6602 (part of 660x).
    622x (M Series)
    Digital change detection has not been released in the DDK for M Series devices. If you must use an M Series device, please ask your field engineer to contact NI support so we can discuss options. On the other hand, digital change detection has been released in the DDK for X Series devices (63xx) [1].
    If you can use one from that family, then your programming will be much easier -- the RLP manual discusses change detection as well as interrupts (Chapter 1: Interrupts, beginning on PDF page 48), and the example distribution demonstrates how to configure change detection on the device (dioex3). The last piece is data transfer: the example's data transfer mechanism is DMA, so you would need to supply your own interrupt handler to move data to the host (or alert the host that a DMA transfer has completed).
    6602 (660x family)
    Moving to the 6602, change detection is not possible. The 660x device family only supports polling for transfering data read on the digital lines [2].
    Please let me know if I overlooked anything in your questions.
    [1] NI Measurement Hardware Driver Development Kit
    http://sine.ni.com/nips/cds/view/p/lang/en/nid/11737
    [2] NI 660x Specifications
    http://digital.ni.com/manuals.nsf/websearch/57893F11B0C0687F862579330064FF6F
    Joe Friedchicken
    NI VirtualBench Application Software
    Get with your fellow hardware users :: [ NI's VirtualBench User Group ]
    Get with your fellow OS users :: [ NI's Linux User Group ] [ NI's OS X User Group ]
    Get with your fellow developers :: [ NI's DAQmx Base User Group ] [ NI's DDK User Group ]
    Senior Software Engineer :: Multifunction Instruments Applications Group
    Software Engineer :: Measurements RLP Group (until Mar 2014)
    Applications Engineer :: High Speed Product Group (until Sep 2008)

  • Using ioctl to wait for hardware interrupt in user space in Petalinux

    I have a custom Network device driver for a device that generates two hardware interrupts, one every 20 ms and another every second. I have a separate interrupt handler registered for each interrupt. Each interrupt handler does nothing more than call "up" on a semaphore. There is a different semaphore associated with each interrupt.
    I want a user-space program to be notified when the interrupt occurs, so I have an ioctl defined with two commands. One is a command to wait for the 20 ms  interrupt and the other is a command to wait for the 1 second interrupt. In each case, the ioctl routine simply calls down_interruptible on the corresonding semaphore (the same semaphore modified by the interrupt handlers).
    In my user-space program, I create two pthreads. Each has an infinite loop to call each of the two ioctls described above.
    I am seeing that the user-space thread that waits for the 1 second interrupt is going to sleep and seems to be blocking the overall process. When the 1 second interrupt comes in, the thread wakes up and, in the process of handling the interrupt, allows the other thread to be tasked. The result is that exactly one 20 ms interrupt is handled each second, whenever a 1 second interrupt fires.
    I have tried enabling the O_NONBLOCK mode on the socket, but this did not make any difference. I'm not sure how to allow the second thread to continue to run, even while the first thread is asleep. Seems like this is the whole point of using pthreads.
    Any help would be appreciated.

    So, the issue was that I was trying to implement the ioctl in a network device. When you call ioctl on a socket, it apparently blocks the process until the ioctl completes.
    I implemented a character device inside my network driver and used this to handle the ioctls instead. Once I did this, I found that only the calling thread blocked on ioctl, not the entire process.

  • X Series DDK: Configure Interrupt on DMA Channel's total transfer count

    Hello,
    In the DAQ-STC3 X Series DDK Reference Manual, Chapter 1: Theroy of Operation, Section Interrupts, Subsection Special Considerations: Maximizing Throughput in Low-Latency Situations (p41), it is said:
    "for X Series devices, the CHInCh can interrupt on the DMA channel’s total transfer count, which occurs once the data has been completely transferred to the host memory. The order of programming for this situation (and output operations) is as follows:
    1. Program the DMA channel’s Total_Transfer_Count_Compare_Register (CHTTCCR) with the number of Bytes in a single input/output sample.
    2. Set the DMA channel’s Notify on Total Count flag in the CHCR.
    3. Set the DMA channel’s Arm Total Count Interrupt flag in the CHOR.
    4. Start data transfer (through the DMA controller and the subsystem’s Stream Circuit).
    5. Receive total transfer count interrupt.
    6. Increase the CHTTCCR by the number of Bytes in a single input/output sample.
    7. Re-arm the total transfer count interrupt in the CHOR.
    Using the X Series DDK, I don't manage to perform such a configuration.
    Can you please provide me code sample to do so ?
    Thanks in advance for your support.
    Sincerely
    Bertrand

    Hello Steve,
    Weeks ago, we developed a Linux application that configure NI acquisition board (serie X) to send an interrupt when FIFO count reach a given number. At this stage we manage to prove that our board configuration was good and that the problem was due to INtime. TenAsys (INtime developers) fix this issue few weeks ago.
    We just come back from holidays, apply the modifications created by TenAsys and manage to get interrupt inside INtime.
    We still have two problems.
    Reading DMA
    ===========
    From the interrupt handler, when we access to the DMA to get samples stored in the FIFO, we manage to get the samples inside the first interrupt handler. With the following interrupts, when accessing DMA with the tCHInChDMAChannel structure, it said that there is no available bytes. But when we read the Channel_Total_Transfer_Count_Status_Register from the DMA channel, we see that we have the desired numbers of samples.
    In the interrupt handler, during the interrupt aknowledgement, instead of only reading the Volatile_Interrupt_Status_Register to ackowledge the interrupt, if I increase the Channel_Total_Transfer_Count_Compare_Register_LSW by a given number (X) then I got X samples to read in the following interrupt. Problem with this solution is that the delay between two interrupts is not constant.
    It seems that we mis-configured the DMA channel. But don't manage to find the error.
    Two interrupts generated
    ====================
    Moreover, we always get 2 FIFO_Count interrupts. Even configuring conversion, sampling and interrupt frequencies at very low value (conversion 1KHz, sampling 1Hz, interrupt generation: 1Hz). The delay between the two interrupts is about few nano seconds.
    Source code
    ============
    I attach to this post the source code we use to play/test this configuration. There is a Visual Studio workspace that we used to play with INtime and a CMake configuration file that we used to manage our Linux tests. You can find all the informations you need to build the binary in the README file.
    Thanks in advance for your help with these issues.
    Sincerely
    Bertrand Cachet
    Attachments:
    IOMonitoring.zip ‏355 KB

  • How to count interrupts of a specific driver / HW

    I am using Perfmon to get #interrupts/sec.
    I can also drill down to single core resolution (e.g. core0, 1, 2, 3 in a 4 core CPU)
    This is good, but i would like to get interrupts/sec for a specific source (e.g. network interface card) or all interrupts handled by a specific driver.
    Couldn't find this capability in Perfmon.
    does anyone have an idea?
    Thanks,
    Ami

    No version of Reader offers word counting or word auditing.

  • AT-MIO16-E interrupts on Dos 6.22

     Trying to generate an interrupt on the AT-MIO16-E pnp card by using counter G0.
     I'm able to program the base address and read port address for the card. I call a InitTimer function
     to setup the G0 counter and associated interrupt control logical (Inttst.c). By running the code I can see that
    an interrupt is being generated because the Interrupt_A_St bit goes high. However, my interrupt handler
    is not being called.
    PNP_util.c contains code to initialize the AT-MIO16-E board and IntTst.c is the demo program to
    setup the timer and interrupt control logic. I trying to use IRQ5 in the demo code. I setup the pnp by
    calling Setup_PNP_Board( 0x240, //board address
                                                0x273, //read port address
                                                 5 ) ; //irq
    Any help would be apprieated
    Thanks
    Roland
    Attachments:
    PNP_UTIL.C ‏6 KB
    INTTST.C ‏11 KB

    Hi,
    Question 1) Why in the world would the TechNet version of MS-DOS be an UPGRADE version??? That makes absolutely no sense at all. Is a "non-upgrade" DOS 6.22 installer available?
    >> First of all, MS-DOS is out of life. For the further research on MS-DOS upgrade version, I recommend that you Contact a representative so that you can get the most qualified pool of respondents. Thanks for your understanding.
    Contact a Representative to Order by Phone
    http://technet.microsoft.com/en-us/subscriptions/bb856399.aspx
    Question 2) I read that Hyper-V doesn't support MS-DOS. Is this just because there are no integration services for it? I really don't need them for this test.
    >> As I mentioned, MS-DOS is too old, it doesn’t make sense to support it on Hyper-V.
    Virtualization with Hyper-V: Supported Guest Operating Systems
    http://www.microsoft.com/windowsserver2008/en/us/hyperv-supported-guest-os.aspx
    Best Regards,
    Vincent Hu

Maybe you are looking for

  • Help! V04 message, can't view on demand programs

    Hi there, I know this is a common problem, but we are having trouble with the above error message. I think it is our broadband speed, which at the last test was around 1100kbps download speed, which I think is too slow? I have phoned tech support and

  • Creating a print button to print a page from another document - is this possible?

    Hello, My company is designing an interactive pdf with indesign with some great navigation on a side-bar. We've made the dimensions of the navigation pages larger than 8.5 x 11. We are constructing a pdf portfolio that contains a printable version of

  • Illustrator CS4 wont save files, please help?

    You can edit a file, go to save, close it down, then when you re-open it the changes made have not been saved?? No error message or warning pops up, and it all looks ok like it has saved properly, until you open it up again. This also happens when yo

  • Correct part number for G4 MDD power supply

    I am in the process of replacing my old Power Mac G4/350 with a G4 MDD 1.0 ghz DP. The power supply is missing from the MDD unit. Does anyone know what the correct part number for this power supply? 

  • 0x80070522

    When trying to upgrade to 10049 I get the error: There were some problems installing updates, but we'll try again later.  If you keep seeing this and want to search the web or contact support for information, this may help - (0x80070522) Keep in mind